Internet Draft David Zelig
Expires: April 2004 Corrigent Systems
Thomas D. Nadeau
Cisco Systems, Inc.
Editors
October 2003
Pseudo Wire (PW) Management Information Base
draft-ietf-pwe3-pw-mib-02.txt
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in
progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright (C) The Internet Society (2001). All rights reserved.
1 Abstract
This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
the Internet community. In particular, it describes managed
objects for modeling of Pseudo Wire (PW) services on a general
Packet Switched Net (PSN).
Table of Contents
1 Abstract 1
2 Introduction 2
3 Terminology 3
4 The SNMP Management Framework 3
4.1 Object Definitions 4
5 Feature Checklist 4
6 PW-MIB usage 4
6.1 PW-MIB usage 5
6.2 Relations to the ifTable 5
6.3 Example of MIB usage 6
7 Object definitions 8
8 Security Considerations 34
9 References 35
10 Author's Addresses 37
11 Full Copyright Statement 38
2 Introduction
This document describes a model for managing pseudo wire services
for transmission over a packet Switched Network (PSN). This MIB
module is generic and common to all types of PSN and PW services.
This document is closely related to [FRARCH], describing the
transport and encapsulation of L1 and L2 services over any type of
PSN and MPLS respectively, creating a Pseudo Wire (PW) service.
This document describes the MIB objects that define the generic
pseudo wire association to the PSN and pseudo wire configurations
that are not specific to the carried service. A PW type field will
be used to point to the relevant service MIB tables, described in
other documents, and a similar PSN type field will point to PSN
specific modules, for example [PWMPLSMIB].
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC-2119
[BCP14].
3
Terminology
This document uses terminology from the document describing the PW
architecture [PWARCH].
4 The SNMP Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
4.1 Object Definitions
Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the MIB
are defined using the subset of Abstract Syntax Notation One
(ASN.1) defined in the SMI. In particular, an OBJECT IDENTIFIER, an
administratively assigned name, names each object type. The object
type together with an object instance serves to uniquely identify a
specific instantiation of the object. For human convenience, we
often use a textual string, termed the descriptor, to also refer to
the object type.
5 Feature Checklist
The PW MIB module (PW-MIB) is designed to satisfy the following
requirements and constraints:
- The MIB is designed to be extensible to all types of PSNs. PSNs
specific MIB modules will be defined in additional documents.
- The MIB enables the use of any emulated service. Emulated
service specific MIB modules will be defined in additional
documents.
- The MIB module supports manually configured PWs.
- The MIB module supports the PW ID and Group ID.
- The MIB module supports point-to-point PW connections. Point-to-
multipoint connections are for future study.
6 PW-MIB usage
The MIB module structure for defining a PW service is composed from
three types of modules.
The first type is the PW-MIB module, which configures general
parameters of the VC that are common to all types of emulated
services and PSNs.
The second type of modules is per PSN module. There is a different
module for each type of PSN. These modules associate the PW with
one or more "tunnels" that carry the service over the PSN. These
modules are defined in other documents; see for example
[PWMPLSMIB].
The third type of modules is service-specific module, which is
emulated signal type dependent. These modules are defined in other
documents; see for example [CEPMIB].
[PWTC] defines some of the object types used in these modules.
6.1 PW-MIB usage
- The PW table (pwVcTable) is used for all PW types (ATM, FR,
Ethernet, SONET, etc.). This table contains high level generic
parameters related to the VC creation. A row is created by the
operator for each PW service.
- Based on the PSN type defined for the PW, rows are created in
PSN specific module (for example [PWMPLSMIB]) and associated to
the PW table by the common PW index.
- Based on the PW type defined for the PW, rows are created in
service-specific module (for example [CEPMIB]) and associated to
the PW table by the common PW index.
- The MIB includes performance parameters collection common to all
types of PW.
- Reverse mapping tables allow an EMS to quickly order PWs based
on their type and PW ID or based on the peer nodes addresses.
6.2 Relations to the ifTable
The PW itself is in general not an ifIndex as it's own, from agent
scalability reasons. In many cases the PW is associated via the MIB
tables to an ifIndex the VC is emulating. This ifIndex may
represent a physical entity - for example a PW emulating a SONET
path as in CEP: The PW itself is not an ifIndex, however the MIB
associate the PW to the ifIndex of the path to be emulated. In some
cases, the PW will be associated to an ifIndex representing a
virtual interface. An example is VPLS service where the PW
emulates a logical interface of a (logical) bridge. The physical
ports association to the VPLS service instance is defined in non-PW
MIBs in this case.
Exception to the above may exist in some services, where it is
convenient to use the PW as an ifIndex in the ifTable. A special
ifType to represent a PW virtual interface (exact number to be
assigned by IANA) will be used in the ifTable in this case.
Note that the ifIndex that carry the PW toward the PSN is in
general not explicitly configured via PW MIB modules except in rare
cases. In most cases the PW is carried inside a PSN tunnel, and the
interfaces carrying the tunnel are specified in the related MIBs
that control the PSN tunnels.
6.3 Example of the PW MIB modules usage
In this section we provide an example of using the MIB objects
described in section 8 to set up a CEP PW over MPLS PSN. While this
example is not meant to illustrate every permutation of the MIB, it
is intended as an aid to understanding some of the key concepts. It
is meant to be read after going through the MIB itself.
In this example a PW service for CEP is configured over an MPLS PSN
(MPLS-TE tunnel). It uses LDP as in [PWCNTRL] for service set-up.
In PW-MIB:
In pwVcTable:
{
pwVcIndex 5,
pwVcType CEP,
pwVcOwner signaling,
pwVcPsnType mpls,
pwVcSetUpPriority 0, -- Highest
pwVcHoldingPriority 0, -- Highest
pwVcInboundMode loose,
pwVcPeerAddrType ipv4,
pwVcPeerAddr 1.4.3.2, -- In this case equal to the
-- peer LDP entity IP addr
pwVcID 10,
pwVcLocalGroupID 12,
pwVcControlWord false, -- Control word not to be sent
pwVcLocalIfMtu 0, -- Do not send ifMtu parameter
pwVcLocalIfString false, -- Do not signal if string
pwVcRemoteGroupID 0xFFFF, -- Will be received by
-- maintenance protocol
pwVcRemoteControlWord notKnownYet,
pwVcRemoteIfMtu 0,
pwVcRemoteIfString "",
pwVcOutboundVcLabel 0xFFFF, -- Will be received by
-- maintenance protocol
pwVcInboundVcLabel 0xFFFF, -- Will be set by maintenance
-- protocol
pwVcName "Example of CEP VC",
pwVcDescr "",
..
pwVcAdminStatus up,
..
..
}
The agent now create a row in pwVcMplsTable [PWMPLS] based on the
VcIndex, that is configured with MPLS specific values:
In pwVcMplsTable:
{
pwVcMplsMplsType mplsTe,
pwVcMplsExpBitsMode outerTunnel,
pwVcMplsExpBits 0, -- Not applicable
pwVcMplsTtl 2,
...
}
The operator now associates the VC with an outgoing TE tunnel:
In pwVcMplsOutboundTable:
{
pwVcMplsOutboundIndex 0, -- The first row
-- for this VcIndex
pwVcMplsOutBoundLsrXcIndex 0, -- MPLS-TE
pwVcMplsOutboundTunnelIndex 500,
pwVcMplsOutboundTunnelInstance 0,
pwVcMplsOutboundTunnelLclLSR 1.2.3.4, -- Always
-- the LSR ID of the current node.
pwVcMplsOutboundTunnelPeerLSR 1.4.3.2
pwVcMplsOutboundIfIndex 0, -- MPLS-TE
..
}
pwVcMplsInboundTable is not used because loose LDP set-up is used.
A row in pwVcIdMappingTable and in pwVcPeerMappingTable will be
created by the agent and will enable easy lookup for the VcIndex
from knowledge of the VC type/VC ID or peer IP address
respectively.
A row in pwVcMplsTeMappingTable will be created by the agent and
will enable easy lookup for the VcIndex from knowledge of the outer
tunnel.
7 Object definitions
PW-MPLS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
experimental, Unsigned32
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
RowStatus, StorageType
FROM SNMPv2-TC
InterfaceIndexOrZero
FROM IF-MIB
MplsTunnelIndex, MplsTunnelInstanceIndex,
MplsLdpIdentifier, MplsLsrIdentifier
FROM MPLS-TC-MIB
PwVcIndexType
FROM PW-TC-MIB
pwVcIndex
FROM PW-MIB
;
pwVcMplsMIB MODULE-IDENTITY
LAST-UPDATED "200307291200Z" -- 29 July 2003 12:00:00 EST
ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working
Group"
CONTACT-INFO
"
David Zelig
Postal: Corrigent Systems
126, Yigal Alon St.
Tel Aviv, ISRAEL
Phone: +972-3-6945273
E-mail: davidz@corrigent.com
Thomas D. Nadeau
Postal: Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-497-3051
Email: tnadeau@cisco.com
Dave Danenberg
Postal: Litchfield Communications, Inc.
76 Westbury Park Rd
Princeton Building East
Watertown, CT 06795
Tel: +1-860-945-1573 x3180
Email: dave_danenberg@litchfieldcomm.com
Sharon Mantin
Postal: AxONLink (Israel) Ltd
9 Bareket St.
Petah Tikva 49517, Israel
Tel: +972-3-9263972
Email: sharon.mantin@axonlink.com
The PWE3 Working Group (email distribution pwe3@ietf.org) "
DESCRIPTION
"This MIB complements the PW-MIB for PW operation over MPLS.
"
-- Revision history.
REVISION
"200307291200Z" -- 29 July 2003 12:00:00 EST
DESCRIPTION
"Draft-ietf-pwe3-pw-mpls-mib-02 version. Changes from
previous version:
1) Removing inbound table (no srict mode and no knowledge
of inbound tunnel).
2) Provisoning (i.e. RowCreate) done via mapping tables.
Outbound table is now read only for sorted search for
pwVcIndex.
"
REVISION
"0206021200Z" -- 02 June 2002 12:00:00 EST
DESCRIPTION
"Draft-ietf-pwe3-pw-mpls-mib-00 version. Changes from
previous version:
1) Spliting the mapping table into two tables, one for
Non TE application and one for TE application.
2) Object types alignment with MPLS MIBs.
"
REVISION
"0201291200Z" -- 29 January 2002 12:00:00 EST
DESCRIPTION
"Changes from previous version:
1) Add LDP entity association.
2) Clarify inbound/outbound directions.
3) Simplify indexing of outbound and inbound tables
and providing get next variables.
"
REVISION
"0107111200Z" -- 7 November 2001 12:00:00 EST
DESCRIPTION
"Changes from previous version:
1) Remove Vc instance from table indexing.
2) Update descriptions of indexing and protection.
3) Remove the need for MPLS-LSR in case of VC only.
4) Change pwVcMplsMplsType to BITS in order to enable
multiple types of outer tunnel.
5) Add ifindex to outer tunnel tables to support vcOnly
option.
6) change naming of outbound, inbound and mapping tables to
reflect addition of VC only port ifindexes.
7) Adapt order of items in mapping table to SNMP convention.
"
REVISION
"0107111200Z" -- July 11 2001 12:00:00 EST
DESCRIPTION
"draft-zelig-pw-mib-00.txt - initial version"
::= { experimental 888 } -- To be assigned by IANA
-- Top-level components of this MIB.
-- Traps
pwVcMplsNotifications OBJECT IDENTIFIER
::= { pwVcMplsMIB 0 }
pwVcMplsNotifyPrefix OBJECT IDENTIFIER
::= { pwVcMplsNotifications 0 }
-- Tables, Scalars
pwVcMplsObjects OBJECT IDENTIFIER
::= { pwVcMplsMIB 1 }
-- Conformance
pwVcMplsConformance OBJECT IDENTIFIER
::= { pwVcMplsMIB 2 }
-- PW VC MPLS table
pwVcMplsTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwVcMplsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies information for VC to be carried over
MPLS PSN."
::= { pwVcMplsObjects 1 }
pwVcMplsEntry OBJECT-TYPE
SYNTAX PwVcMplsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in this table represents parameters specific to MPLS
PSN for a pseudo wire connection (VC). The row is created
automatically by the local agent if the pwVcPsnType is
MPLS. It is indexed by pwVcIndex, which uniquely
identifying a singular connection.
"
INDEX { pwVcIndex }
::= { pwVcMplsTable 1 }
PwVcMplsEntry ::= SEQUENCE {
pwVcMplsMplsType BITS,
pwVcMplsExpBitsMode INTEGER,
pwVcMplsExpBits Unsigned32,
pwVcMplsTtl Unsigned32,
pwVcMplsLocalLdpID MplsLdpIdentifier,
pwVcMplsLocalLdpEntityID Unsigned32,
pwVcMplsPeerLdpID MplsLdpIdentifier,
pwVcMplsStorageType StorageType
}
pwVcMplsMplsType OBJECT-TYPE
SYNTAX BITS {
mplsTe (0),
mplsNonTe (1),
vcOnly (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Set by the operator to indicate the outer tunnel types, if
exists. mplsTe is used if the outer tunnel was set-up by
MPLS-TE, and mplsNonTe is used the outer tunnel was set up
by LDP or manually. Combination of mplsTe and mplsNonTe
may exist in case of outer tunnel protection.
vcOnly is used if there is no outer tunnel label. vcOnly
cannot be combined with mplsNonTe or mplsTe."
::= { pwVcMplsEntry 1 }
pwVcMplsExpBitsMode OBJECT-TYPE
SYNTAX INTEGER {
outerTunnel (1),
specifiedValue (2),
serviceDependant (3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Set by the operator to indicate the way the VC shim label
EXP bits are to be determined. The value of outerTunnel(1)
is used where there is an outer tunnel - pwVcMplsMplsType
is mplsTe or mplsNonTe. Note that in this case there is no
need to mark the VC label with the EXP bits since the VC
label is not visible to the intermediate nodes.
If there is no outer tunnel, specifiedValue(2) indicate
that the value is specified by pwVcMplsExpBits, and
serviceDependant(3) indicate that the EXP bits are setup
based on a rule specified in the emulated service specific
tables, for example when the EXP bits are a function of
802.1p marking for Ethernet emulated service."
REFERENCE
"martini et al, <draft-martini-l2circuit-encap-mpls.txt>"
DEFVAL { outerTunnel }
::= { pwVcMplsEntry 2 }
pwVcMplsExpBits OBJECT-TYPE
SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Set by the operator to indicate the MPLS EXP bits to be
used on the VC shim label if pwVcMplsExpBitsMode is
specifiedValue(2), zero otherwise."
DEFVAL { 0 }
::= { pwVcMplsEntry 3 }
pwVcMplsTtl OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Set by the operator to indicate the VC TTL bits to be used
on the VC shim label."
REFERENCE
"martini et al, <draft-martini-l2circuit-encap-mpls> "
DEFVAL { 2 }
::= { pwVcMplsEntry 4 }
pwVcMplsLocalLdpID OBJECT-TYPE
SYNTAX MplsLdpIdentifier
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The local LDP identifier of the LDP entity creating
this VC in the local node. As the VC labels are always
set from the per platform label space, the last two octets
in the LDP ID MUST be always both zeros."
REFERENCE
"<draft-ietf-ldp-mib>,
<draft-martini-l2circuit-encap-mpls>.
"
::= { pwVcMplsEntry 5 }
pwVcMplsLocalLdpEntityID OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The local LDP Entity index of the LDP entity to be used
for this VC on the local node. Should be set to all zeros
if not used."
REFERENCE
"<draft-ietf-ldp-mib>
"
::= { pwVcMplsEntry 6 }
pwVcMplsPeerLdpID OBJECT-TYPE
SYNTAX MplsLdpIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The peer LDP identifier as identified from the LDP
session. Should be zero if not relevant or not known yet."
REFERENCE
"<draft-ietf-ldp-mib>,
<draft-martini-l2circuit-encap-mpls>.
"
::= { pwVcMplsEntry 7 }
pwVcMplsStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the storage type for this row."
::= { pwVcMplsEntry 8 }
-- End of PW MPLS VC table
-- Pseudo Wire VC MPLS Outbound Tunnel table
pwVcMplsOutboundTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwVcMplsOutboundEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table associates VCs using MPLS PSN with the outbound
MPLS tunnels (i.e. toward the PSN) or the physical
interface in case of VC only."
::= { pwVcMplsObjects 2 }
pwVcMplsOutboundEntry OBJECT-TYPE
SYNTAX PwVcMplsOutboundEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in this table represents a link between PW VC (that
require MPLS tunnels) and MPLS tunnel toward the PSN.
In the case of VC only, it associate the VC with the
interface that shall carry the VC.
This table is indexed by the pwVcIndex and an additional
index enabling multiple rows for the same VC index.
At least one entry is created in this table by the agent
for each PW VC that requires MPLS PSN. Note that the first
entry for each VC can be indexed by pwVcMplsOutboundIndex
equal zero without a need for retrieval of
pwVcMplsOutboundIndexNext.
This table points to the appropriate MPLS MIB. In the case
of MPLS-TE, the 4 variables relevant to the indexing of
a TE MPLS tunnel are set as in Srinivasan, et al, <draft-
ietf-mpls-te-mib>.
In case of Non-TE MPLS (an outer tunnel label assigned by
LDP or manually) the table points to the XC entry in the
LSR MIB as in Srinivasan, et al, <draft-ietf-mpls-lsr-mib>.
In case of VC only (no outer tunnel) the ifIndex of the
port to carry the VC is configured.
Each VC may have multiple rows in this tables if protection
is available at the outer tunnel level, each row may be of
different type except for VC only, on which only rows with
ifIndex of the port are allowed.
"
INDEX { pwVcIndex, pwVcMplsOutboundIndex }
::= { pwVcMplsOutboundTable 1 }
PwVcMplsOutboundEntry ::= SEQUENCE {
pwVcMplsOutboundIndex Unsigned32,
pwVcMplsOutboundLsrXcIndex Unsigned32,
pwVcMplsOutboundTunnelIndex MplsTunnelIndex,
pwVcMplsOutboundTunnelInstance MplsTunnelInstanceIndex,
pwVcMplsOutboundTunnelLclLSR MplsLsrIdentifier,
pwVcMplsOutboundTunnelPeerLSR MplsLsrIdentifier,
pwVcMplsOutboundIfIndex InterfaceIndexOrZero
}
pwVcMplsOutboundIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Arbitrary index for enabling multiple rows per VC in
this table. Next available free index can be retrieved
using pwVcMplsOutboundIndexNext.
"
::= { pwVcMplsOutboundEntry 1 }
pwVcMplsOutboundLsrXcIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object will be set by the operator. If the outer
label is defined in the MPL-LSR-MIB, i.e. set by LDP
or manually, this object points to the XC index
of the outer tunnel. Otherwise, it is set to zero."
::= { pwVcMplsOutboundEntry 2 }
pwVcMplsOutboundTunnelIndex OBJECT-TYPE
SYNTAX MplsTunnelIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Part of set of indexes for outbound tunnel in the case of
MPLS-TE outer tunnel, otherwise set to zero."
::= { pwVcMplsOutboundEntry 3 }
pwVcMplsOutboundTunnelInstance OBJECT-TYPE
SYNTAX MplsTunnelInstanceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Part of set of indexes for outbound tunnel in the case of
MPLS-TE outer tunnel, otherwise set to zero."
::= { pwVcMplsOutboundEntry 4 }
pwVcMplsOutboundTunnelLclLSR OBJECT-TYPE
SYNTAX MplsLsrIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Part of set of indexes for outbound tunnel in the case of
MPLS-TE outer tunnel, otherwise set to zero."
::= { pwVcMplsOutboundEntry 5 }
pwVcMplsOutboundTunnelPeerLSR OBJECT-TYPE
SYNTAX MplsLsrIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Part of set of indexes for outbound tunnel in the case of
MPLS-TE outer tunnel, otherwise set to zero."
::= { pwVcMplsOutboundEntry 6 }
pwVcMplsOutboundIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"In case of VC only (no outer tunnel), this object holds
the ifIndex of the outbound port, otherwise set to zero."
::= { pwVcMplsOutboundEntry 7 }
-- End of Pseudo Wire VC MPLS Outbound Tunnel table
-- MPLS to VC Mapping Tables.
pwVcMplsNonTeMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwVcMplsNonTeMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table maps an outbound Tunnel to a VC in non-
TE applications."
::= { pwVcMplsObjects 3 }
pwVcMplsNonTeMappingEntry OBJECT-TYPE
SYNTAX PwVcMplsNonTeMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in this table represents the association
between the PW VC and it's non TE MPLS outer Tunnel
it's physical interface if there is no outer tunnel
(VC only).
If the operator (or the agent, based on local policy)
want to associate the PW with a non TE tunnel, it
create
a row in this table with the tunnel parameters and the
relevant pwVcIndex.
An application can use this table to quickly retrieve the
PW carried over specific non-TE MPLS outer tunnel or
physical interface.
The table in indexed by the XC index for MPLS Non-TE
tunnel, or ifIndex of the port in VC only case, the
direction of the VC in the specific entry and the VCIndex.
"
INDEX { pwVcMplsNonTeMappingXcTunnelIndex,
pwVcMplsNonTeMappingIfIndex,
pwVcMplsNonTeMappingVcIndex }
::= { pwVcMplsNonTeMappingTable 1 }
PwVcMplsNonTeMappingEntry ::= SEQUENCE {
pwVcMplsNonTeMappingXcTunnelIndex Unsigned32,
pwVcMplsNonTeMappingIfIndex
InterfaceIndexOrZero,
pwVcMplsNonTeMappingVcIndex PwVcIndexType,
pwVcMplsNonTeMappingRowStatus RowStatus,
pwVcMplsNonTeMappingStorageType StorageType
}
pwVcMplsNonTeMappingXcTunnelIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index for the conceptual XC row identifying Tunnel to VC
mappings when the outer tunnel is created by the MPLS-LSR-
MIB, Zero otherwise."
::= { pwVcMplsNonTeMappingEntry 1 }
pwVcMplsNonTeMappingIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"In cases where there is only VC label without outer tunnel,
this item indicate the ifIndex of the interface this VC
would use. In all other cases, this object shgould be set to
zero."
::= { pwVcMplsNonTeMappingEntry 2 }
pwVcMplsNonTeMappingVcIndex OBJECT-TYPE
SYNTAX PwVcIndexType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value that represent the VC in the pwVcTable."
::= { pwVcMplsNonTeMappingEntry 3 }
pwVcMplsNonTeMappingRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For creating, modifying, and deleting this row."
::= { pwVcMplsNonTeMappingEntry 4 }
pwVcMplsNonTeMappingStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this object."
::= { pwVcMplsNonTeMappingEntry 5 }
-- End of Non-TE MPLS Tunnel to VC Mapping Table
pwVcMplsTeMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwVcMplsTeMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table maps an inbound/outbound Tunnel to a VC in
MPLS-TE applications."
::= { pwVcMplsObjects 4 }
pwVcMplsTeMappingEntry OBJECT-TYPE
SYNTAX PwVcMplsTeMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in this table represents the association
between a PW VC and it's MPLS-TE outer Tunnel.
If the operator (or the agent, based on local policy)
want to associate the PW with a non TE tunnel, it
create
a row in this table with the tunnel parameters and the
relevant pwVcIndex.
An application can use this table to quickly retrieve the
PW carried over specific TE MPLS outer tunnel.
The table in indexed by the 4 indexes of a TE tunnel,
the direction of the VC specific entry and the VcIndex.
"
INDEX { pwVcMplsTeMappingTunnelIndex,
pwVcMplsTeMappingTunnelInstance,
pwVcMplsTeMappingTunnelPeerLsrID,
pwVcMplsTeMappingTunnelLocalLsrID,
pwVcMplsTeMappingVcIndex }
::= { pwVcMplsTeMappingTable 1 }
PwVcMplsTeMappingEntry ::= SEQUENCE {
pwVcMplsTeMappingTunnelIndex MplsTunnelIndex,
pwVcMplsTeMappingTunnelInstance MplsTunnelInstanceIndex,
pwVcMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier,
pwVcMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier,
pwVcMplsTeMappingVcIndex PwVcIndexType,
pwVcMplsTeMappingRowStatus RowStatus,
pwVcMplsTeMappingStorageType StorageType
}
pwVcMplsTeMappingTunnelIndex OBJECT-TYPE
SYNTAX MplsTunnelIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Primary index for the conceptual row identifying the
MPLS-TE tunnel."
::= { pwVcMplsTeMappingEntry 1 }
pwVcMplsTeMappingTunnelInstance OBJECT-TYPE
SYNTAX MplsTunnelInstanceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Identifies an instance of the MPLS-TE tunnel."
::= { pwVcMplsTeMappingEntry 2 }
pwVcMplsTeMappingTunnelPeerLsrID OBJECT-TYPE
SYNTAX MplsLsrIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Identifies an Peer LSR when the outer tunnel is MPLS-TE
based."
::= { pwVcMplsTeMappingEntry 3 }
pwVcMplsTeMappingTunnelLocalLsrID OBJECT-TYPE
SYNTAX MplsLsrIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Identifies the local LSR."
::= { pwVcMplsTeMappingEntry 4 }
pwVcMplsTeMappingVcIndex OBJECT-TYPE
SYNTAX PwVcIndexType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value that represent the VC in the pwVcTable."
::= { pwVcMplsTeMappingEntry 5 }
pwVcMplsTeMappingRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For creating, modifying, and deleting this row."
::= { pwVcMplsTeMappingEntry 6 }
pwVcMplsTeMappingStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this object."
::= { pwVcMplsTeMappingEntry 7 }
-- End of TE MPLS Tunnel to VC Mapping Table
-- conformance information
-- Note: Conformance at the object access and values level is
-- still FFS, therefore current conformance is defined at the
-- object existence level only.
pwVcMplsGroups OBJECT IDENTIFIER ::= { pwVcMplsConformance 1 }
pwVcMplsCompliances OBJECT IDENTIFIER ::= { pwVcMplsConformance 2 }
pwMplsModuleCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for agent that support PW
over MPLS PSN operation."
MODULE -- this module
MANDATORY-GROUPS { pwVcMplsGroup,
pwVcMplsOutboundGroup,
pwVcMplsMappingGroup
}
::= { pwVcMplsCompliances 1 }
-- Units of conformance.
pwVcMplsGroup OBJECT-GROUP
OBJECTS {
pwVcMplsMplsType,
pwVcMplsExpBitsMode,
pwVcMplsExpBits,
pwVcMplsTtl,
pwVcMplsLocalLdpID,
pwVcMplsLocalLdpEntityID,
pwVcMplsPeerLdpID,
pwVcMplsStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for PW VC
over MPLS PSN configuration."
::= { pwVcMplsGroups 1 }
pwVcMplsOutboundGroup OBJECT-GROUP
OBJECTS {
pwVcMplsOutboundLsrXcIndex,
pwVcMplsOutboundTunnelIndex,
pwVcMplsOutboundTunnelInstance,
pwVcMplsOutboundTunnelLclLSR,
pwVcMplsOutboundTunnelPeerLSR,
pwVcMplsOutboundIfIndex
}
STATUS current
DESCRIPTION
"Collection of objects needed for outbound association of
VC and MPLS tunnel."
::= { pwVcMplsGroups 2 }
pwVcMplsMappingGroup OBJECT-GROUP
OBJECTS {
pwVcMplsNonTeMappingVcIndex,
pwVcMplsNonTeMappingRowStatus,
pwVcMplsNonTeMappingStorageType,
pwVcMplsTeMappingVcIndex,
pwVcMplsTeMappingRowStatus,
pwVcMplsTeMappingStorageType
}
STATUS current
DESCRIPTION
"Collection of objects used for mapping of tunnels and VC
labels to VC index."
::= { pwVcMplsGroups 4 }
END -- of PW-MPLS-MIB
8 Security Considerations
There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is
no control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the
use of the User-based Security Model RFC 2574 [RFC2574] and the
View-based Access Control Model RFC 2575 [RFC2575] is recommended.
It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET
(change/create/delete) them.
9 References
[PWARCH] Bryant et al, "PWE3 Architecture", work-in-progress.
[PWREQ] Xiao et al, "Requirements for Pseudo Wire Emulation
Edge-to-Edge (PWE3)", work-in-progress.
[L2TPv3] Townsley, et al., "Layer Two Tunneling Protocol
(Version 3) "L2TPv3"", work-in-progress
[PWCNTRL] Martini et al, "Pseudowire Setup and Maintenance using
LDP", work-in-progress.
[PWFRAG] Malis, A. et al, "PWE3 Fragmentation and Reassembly",
work-in-progress.
[PWTC] Nadeau, T., et al, "Definitions for Textual
Conventions and OBJECT-IDENTITIES for Pseudo-Wires
Management", work-in-progress
[PWMPLSMIB] Zelig et al, "Pseudo Wire (PW) Over MPLS PSN Management
Information Base", work-in-progress.
[CEP] Malis, A., et al, "SONET/SDH Circuit Emulation over
Packet (CEP)", work-in-progress.
[ENETPW] Martini et al, " Encapsulation Methods for Transport of
Ethernet Frames Over IP/MPLS Networks", work-in-
progress.
[CEPMIB] Danenberg et al, "SONET/SDH Circuit Emulation Service
Over MPLS (CEM) Management Information Base Using
SMIv2", work-in-progress.
[LSRMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. "MPLS
Label Switch Router Management Information Base Using
SMIv2", work-in-progress.
[TEMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. "MPLS
Traffic
Engineering Management Information Base Using SMIv2",
work-in-
progress.
[LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,
Federokow, G., Li, T., and A. Conta, "MPLS Label Stack
Encoding", RFC 3032, January 2001.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", RFC
1700, October 1994. See also: http://www.isi.edu/in-
notes/iana/assignments/smi-numbers
[IANAFamily]Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS,(http://www.isi.edu/in-
notes/iana/assignements/address-family-numbers), for
MIB see:
ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib
[IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces
Group MIB using SMIv2", RFC 2863, June 2000.
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate
requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management
Frameworks", RFC 2571, April 1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP-
based Internets", STD 16, RFC 1155, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions",
STD 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J, Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J, Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J, Rose, M., and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, April
1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905,
January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999.
10 Author's Addresses
David Zelig
Corrigent Systems
126, Yigal Alon st.
Tel Aviv, ISRAEL
Phone: +972-3-6945273
Email: davidz@corrigent.com
Thomas D. Nadeau
Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Email: tnadeau@cisco.com
Dave Danenberg
Litchfield Communications, Inc.
76 Westbury Park Rd
Princeton Building East
Watertown, CT 06795
Email: dave_danenberg@litchfieldcomm.com
Sharon Mantin
AxONLink (Israel) Ltd
9 Bareket St.
Petah Tikva 49517, Israel
Phone: +972-3-9263972
Email: sharon.mantin@axonlink.com
11 Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain
it or assist in its implementation may be prepared, copied,
published and distributed, in whole or in part, without restriction
of any kind, provided that the above copyright notice and this
paragraph are included on all such copies and derivative works.
However, this document itself may not be modified in any way, such
as by removing the copyright notice or references to the Internet
Society or other Internet organizations, except as needed for the
purpose of developing Internet standards in which case the
procedures for copyrights defined in the Internet Standards process
must be followed, or as required to translate it into languages
other than English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. This
document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.