draft-ietf-l2vpn-vpls-mib-01.txt   draft-ietf-l2vpn-vpls-mib-02.txt 
Internet Draft Thomas D. Nadeau (Ed.) Internet Draft Thomas D. Nadeau (Ed.)
Intended status: Standards Track A S Kiran Koushik (Ed.) Intended status: Standards Track A S Kiran Koushik (Ed.)
Expires: Aug 2008 Cisco Systems, Inc. Expires: Feb 2009 Cisco Systems, Inc.
Rohit Mediratta (Ed.) Rohit Mediratta (Ed.)
Alcatel Alcatel-Lucent
Virtual Private Lan Services (VPLS) Management Information Base Virtual Private Lan Services (VPLS) Management Information Base
draft-ietf-l2vpn-vpls-mib-01.txt draft-ietf-l2vpn-vpls-mib-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 42 skipping to change at page 1, line 43
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines an experimental portion of the Management
Information Base for use with network management protocols in the Information Base for use with network management protocols in the
Internet community. In particular, it describes managed objects Internet community. In particular, it describes managed objects
for modeling of Virtual Private LAN services. It needs to be used for modeling of Virtual Private LAN services. It needs to be used
in conjunction with Pswudo Wire (PW) Management Information Base in conjunction with Pseudo Wire (PW) Management Information Base
[PWE3-PW-MIB]. [PWE3-PW-MIB].
Table of Contents Table of Contents
Abstract............................................................1 Abstract............................................................1
1 Introduction...................................................2 1 Introduction.....................................................2
1.1 Changes from version 00 to 01..................................3 1.1 Changes from version 00 to 01 (individual submission)..........2
1.2 Changes from version 01 to 02..................................3 1.2 Changes from version 01 to 02 (individual submission)..........3
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008 1.3 Changes from version 02 to 03 (individual submission)..........3
1.4 Changes from version 03 to 04 (individual submission)..........3
1.5 Changes from version 00 to 01 (Standards track).................3
1.6 Changes from version 01 to 02 (Standards track).................3
1.3 Changes from version 02 to 03..................................3 draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
1.3 Changes from version 03 to 04..................................3
1.4 Changes from version 00 to 01(standards track) ................3 2 Terminology......................................................4
2 Terminology....................................................4 3 The Internet-Standard Management Framework.......................4
3 The Internet-Standard Management Framework.....................4 4 VPLS MIB Module Architecture.....................................4
4 VPLS MIB modules Architecture..................................4 4.1 VPLS-GENERIC-DRAFT-01-MIB Module Usage..........................5
4.1 VPLS-GENERIC-DRAFT-01-MIB Module Usage.........................5 4.2 VPLS-LDP-DRAFT-01-MIB Module Usage..............................5
4.2 VPLS-LDP-DRAFT-01-MIB Module Usage.............................5 4.3 VPLS-BGP-DRAFT-01-MIB Module Usage..............................5
4.3 VPLS-BGP-DRAFT-01-MIB Module Usage.............................5 4.4 Relations to other MIB modules..................................5
4.4 Relations to other MIB modules.................................5 5 Example of the VPLS MIB modules usage............................6
5 Example of the VPLS MIB modules usage .........................6 6 Object definitions...............................................7
6 Object definitions.............................................7 6.1 VPLS-GENERIC-DRAFT-01-MIB.......................................7
6.1 VPLS-GENERIC-DRAFT-01-MIB......................................7 6.2 VPLS-LDP-DRAFT-01-MIB Object definitions......................26
6.2 VPLS-LDP-DRAFT-01-MIB Object definitions......................23 6.3 VPLS-BGP-DRAFT-01-MIB Object definitions.......................30
6.3 VPLS-BGP-DRAFT-01-MIB Object definitions......................23 7. Security Considerations.........................................37
7 Security considerations.......................................37 8. IANA Considerations.............................................38
8 IANA Considerations...........................................37 9. References......................................................38
9 References....................................................37 9.1 Normative References...........................................38
9.1 Normative References..........................................37 9.2 Informative References.........................................38
9.2 Informative References........................................37 10 Acknowledgement.................................................39
10 Acknowledgement ..............................................38 11 Authors' Addresses..............................................39
11 Author's Addresses............................................38 12 Intellectual Property Notice....................................40
12 Intellectual Property Notice..................................39 13 Full Copyright Statement........................................41
13 Full Copyright Statement......................................40
1 Introduction 1 Introduction
This memo defines a portion of the Management Information Base This memo defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, it defines a MIB module that can be community. In particular, it defines a MIB module that can be
used to manage VPLS(Virtual Private LAN Services for transmission used to manage VPLS(Virtual Private LAN Services for transmission
over a packet Switched Network (PSN) using LDP [L2VPN-VPLS-LDP] or over a packet Switched Network (PSN) using LDP [RFC 4762] or
BGP[L2VPN-VPLS-BGP] signalling. This MIB module provides generic BGP[RFC 4761] signalling. This MIB module provides generic
management of VPLS services as defined by the IETF L2VPN Working management of VPLS services as defined by the IETF L2VPN Working
Group. Group.
Comments should be made directly to the L2VPN mailing list at Comments should be made directly to the L2VPN mailing list at
l2vpn@ietf.org. l2vpn@ietf.org.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
RFC-2119 [BCP14]. RFC-2119 [BCP14].
1.1. Changes from version 00 to 01 (individual submission) 1.1 Changes from version 00 to 01 (individual submission)
[NOTE to RFC Editor: this section is to be removed before [NOTE to RFC Editor: this section is to be removed before
publication.] publication.]
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
1.1.1. Split the MIB modules into VPLS-GENERIC-DRAFT-01-MIB, 1.1.1. Split the MIB modules into VPLS-GENERIC-DRAFT-01-MIB,
VPLS-LDP-DRAFT-01-MIB, VPLS-BGP-DRAFT-01-MIB. VPLS-LDP-DRAFT-01-MIB, VPLS-BGP-DRAFT-01-MIB.
The generic MIB Module will contain information common The generic MIB Module will contain information common
to both LDP and BGP signalled VPLS. to both LDP and BGP signalled VPLS.
1.1.2. Moved certain objects from vplsConfigTable to 1.1.2. Moved certain objects from vplsConfigTable to
vplsStatusTable. vplsStatusTable.
1.1.3. Added new objects to the vplsLdpPwBindTable. 1.1.3. Added new objects to the vplsLdpPwBindTable.
1.1.4. Retained MAC related objects since there is specific 1.1.4. Retained MAC related objects since there is specific
reference in [L2VPN-VPLS-LDP] and [L2VPN-VPLS-BGP]. reference in [RFC 4762] and [RFC 4761].
1.2. Changes from version 01 to 02 (individual submission) 1.2 Changes from version 01 to 02 (individual submission)
[NOTE to RFC Editor: this section is to be removed before [NOTE to RFC Editor: this section is to be removed before
publication.] publication.]
1.2.1. Added new objects to the vplsConfigTable. 1.2.1. Added new objects to the vplsConfigTable.
1.2.2. Editorial changes. 1.2.2. Editorial changes.
1.3. Changes from version 02 to 03 (individual submission) 1.3 Changes from version 02 to 03 (individual submission)
[NOTE to RFC Editor: this section is to be removed before [NOTE to RFC Editor: this section is to be removed before
publication.] publication.]
1.3.1. Added the VPLS-BGP-DRAFT-01-MIB module. 1.3.1. Added the VPLS-BGP-DRAFT-01-MIB module.
1.4. Changes from version 03 to 04 (individual submission) 1.4 Changes from version 03 to 04 (individual submission)
[NOTE to RFC Editor: this section is to be removed before [NOTE to RFC Editor: this section is to be removed before
publication.] publication.]
1.4 Published as a Standards Track document. 1.4 Published as a Standards Track document.
1.5 Changes from version 00 to 01 (Standards track) 1.5 Changes from version 00 to 01 (Standards track)
[NOTE to RFC Editor: this section is to be removed before [NOTE to RFC Editor: this section is to be removed before
publication.] publication.]
1.5.1 Added the mechanism to associate VPLS MIB Mac address 1.5.1 Added the mechanism to associate VPLS MIB Mac address
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
entries into BRIDGE-MIB. entries into BRIDGE-MIB.
1.5.2 Added Rohit Mediratta as a co-editor. 1.5.2 Added Rohit Mediratta as a co-editor.
1.6 Changes from version 01 to 02 (Standards track)
[NOTE to RFC Editor: this section is to be removed before
publication.]
1.6.1 Added support for BGP based Autodiscovery for Ldp and Bgp
flavours of Vpls.
1.6.2 Created separate table for RouteTarget to allow representation
of hierarchical Vpls.
1.6.3 Moved configuration of Route Distinguisher and Route Target
to the Vpls-MIB from the VPLS-BGP-MIB
1.6.4 Removed extra defintion of pwIndex from vplsPwBindTable
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
1.6.5 Index for vplsBgpObjects were incorrect, fixed.
2 Terminology 2 Terminology
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms and mechanisms
described in [RFC3985]. Unless otherwise stated, the mechanisms of described in [RFC3985]. Unless otherwise stated, the mechanisms of
[RFC3985] apply and will not be re-described here. [RFC3985] apply and will not be re-described here.
3 The Internet-Standard Management Framework 3 The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 Internet-Standard Management Framework, please refer to section 7
skipping to change at page 4, line 30 skipping to change at page 4, line 29
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. MIB objects are termed the Management Information Base or MIB. MIB objects are
generally accessed through the Simple Network Management Protocol generally accessed through the Simple Network Management Protocol
(SNMP). Objects in the MIB are defined using the mechanisms (SNMP). Objects in the MIB are defined using the mechanisms
defined in the Structure of Management Information (SMI). This defined in the Structure of Management Information (SMI). This
memo specifies a MIB module that is compliant to the SMIv2, which memo specifies a MIB module that is compliant to the SMIv2, which
is described in STD 58,[RFC2578], STD 58, [RFC2579] and STD 58, is described in STD 58,[RFC2578], STD 58, [RFC2579] and STD 58,
[RFC2580]. [RFC2580].
4. VPLS MIB Module Architecture 4 VPLS MIB Module Architecture
The MIB structure for defining a VPLS service is composed from four The MIB structure for defining a VPLS service is composed from four
types of MIB modules. types of MIB modules.
The first type is the VPLS-GENERIC-DRAFT-01-MIB module, which The first type is the VPLS-GENERIC-DRAFT-01-MIB module, which
configures general parameters of the VPLS service that are common configures general parameters of the VPLS service that are common
to all types of emulated services. to all types of emulated services.
The second type is the VPLS-LDP-DRAFT-01-MIB module, which The second type is the VPLS-LDP-DRAFT-01-MIB module, which
configures VPLS-LDP[L2VPN-VPLS-LDP] specific parameters of the configures VPLS-LDP[RFC 4762] specific parameters of the
VPLS service. VPLS service.
The third type is the VPLS-BGP-DRAFT-01-MIB module, which configures The third type is the VPLS-BGP-DRAFT-01-MIB module, which configures
VPLS-BGP[L2VPN-VPLS-BGP] specific parameters of the VPLS-BGP[RFC 4761] specific parameters of the
VPLS service. VPLS service.
The fourth type of modules are service-specific modules, which are The fourth type of modules are service-specific modules, which are
defined in other documents. defined in other documents.
-------- ----------------- -------- -----------------
PW Mapping | | | | PW Mapping | | | |
-----> | PW-MIB |-->|PW-ENET/MPLS-MIB | -----> | PW-MIB |-->|PW-ENET/MPLS-MIB |
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
__________ / | | | | __________ / | | | |
| | / -------- ----------------- | | / -------- -----------------
| VPLS MIB | / ------------ | VPLS MIB | / ------------
| |----------------------> | | | |----------------------> | |
----------- MAC addr. mapping using | BRIDGE-MIB | ----------- MAC addr. mapping using | BRIDGE-MIB |
[SNMP-CONTEXT-MAP-MIB] | | [SNMP-CONTEXT-MAP-MIB] | |
------------ ------------
4.1. VPLS-GENERIC-DRAFT-01-MIB Module Usage draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
4.1 VPLS-GENERIC-DRAFT-01-MIB Module Usage
An entry in the vplsConfigTable MUST exist for a VPLS service. An entry in the vplsConfigTable MUST exist for a VPLS service.
This table holds generic parameters which apply to a VPLS service This table holds generic parameters which apply to a VPLS service
which can be signalled via LDP or BGP. which can be signalled via LDP or BGP.
A conceptual row can be created in the vplsConfigTable in one of A conceptual row can be created in the vplsConfigTable in one of
the following ways: the following ways:
1) The operator creates a row in the vplsConfigTable when 1) The operator creates a row in the vplsConfigTable when
configuring the node for a new service. This mode MUST be configuring the node for a new service. This mode MUST be
supported by the agent, and MUST be used when creating a supported by the agent, and MUST be used when creating a
skipping to change at page 5, line 37 skipping to change at page 5, line 31
2) The agent MAY create a row in the vplsConfigTable automatically 2) The agent MAY create a row in the vplsConfigTable automatically
due to some auto discovery application, or based on due to some auto discovery application, or based on
configuration that is done through non-SNMP applications. configuration that is done through non-SNMP applications.
This mode is OPTIONAL. This mode is OPTIONAL.
An entry in the vplsPwBindTable MUST exist for a VPLS service. An entry in the vplsPwBindTable MUST exist for a VPLS service.
This binding table links one VPLS service with one or many This binding table links one VPLS service with one or many
pseudo wires (defined in [PWE3-PW-MIB]). The pseudo wire may pseudo wires (defined in [PWE3-PW-MIB]). The pseudo wire may
be used as a spoke or a mesh based on the parameters defined be used as a spoke or a mesh based on the parameters defined
in this table. in this table.
An entry in the vplsBgpAdConfigTable MUST exist if
Auto-discovery has been enabled on this service. This table
stores the information required for auto-discovery.
An entry in the vplsBgpRteTargetTable MUST exist if auto-discovery
has been configured on this service. One service can import
and export multiple Route targets.
The agent than creates the rows in the (locally supported) The agent than creates the rows in the (locally supported)
performance tables and reverse mapping tables in performance tables and reverse mapping tables in
VPLS-GENERIC-DRAFT-01-MIB module. VPLS-GENERIC-DRAFT-01-MIB module.
4.2. VPLS-LDP-DRAFT-01-MIB Module Usage 4.2 VPLS-LDP-DRAFT-01-MIB Module Usage
An entry in the vplsLdpConfigTable MUST be created by the agent An entry in the vplsLdpConfigTable MUST be created by the agent
for a VPLS service signalled using LDP. for a VPLS service signalled using LDP.
4.3. VPLS-BGP-DRAFT-01-MIB Module Usage 4.3 VPLS-BGP-DRAFT-01-MIB Module Usage
An entry in the vplsBgpConfigTable MUST be created by the agent An entry in the vplsBgpConfigTable MUST be created by the agent
for a VPLS service signalled using LDP. for a VPLS service signalled using BGP.
4.4. Relations to other MIB modules 4.4 Relations to other MIB modules
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
- The vplsPwBindTable links the VPLS entry to various entries in - The vplsPwBindTable links the VPLS entry to various entries in
the [PWE3-PW-MIB] the [PWE3-PW-MIB]
- The association of MAC addresses to VPLS entries is possible - The association of MAC addresses to VPLS entries is possible
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
by adding a turnstile function to interpret the entries in by adding a turnstile function to interpret the entries in
[SNMP-CONTEXT-MAP-MIB]. In [SNMP-CONTEXT-MAP-MIB] there is [SNMP-CONTEXT-MAP-MIB]. In [SNMP-CONTEXT-MAP-MIB] there is
a mapping between the vacmContextName[RFC3415] to a mapping between the vacmContextName[RFC3415] to
dot1dBasePort[RFC4188] and vplsConfigIndex. This mapping can dot1dBasePort[RFC4188] and vplsConfigIndex. This mapping can
be used to map the vplsConfigIndex to a dot1dBasePort be used to map the vplsConfigIndex to a dot1dBasePort
in the BRIDGE-MIB. This resulting value of dot1dBasePort in the BRIDGE-MIB. This resulting value of dot1dBasePort
can be used to access corresponding MAC addresses that belong can be used to access corresponding MAC addresses that belong
to a particular vplsConfigIndex. to a particular vplsConfigIndex.
- Unless all the necessary entries in the applicable tables have - Unless all the necessary entries in the applicable tables have
skipping to change at page 7, line 4 skipping to change at page 6, line 49
vplsConfigMacLearning 1(true), vplsConfigMacLearning 1(true),
vplsConfigDiscardUnknownDest 2(false), vplsConfigDiscardUnknownDest 2(false),
vplsConfigMacAging 1(true), vplsConfigMacAging 1(true),
vplsConfigVpnId "100:10" vplsConfigVpnId "100:10"
vplsConfigRowStatus 1(active) vplsConfigRowStatus 1(active)
} }
In vplsStatusTable: In vplsStatusTable:
{ {
vplsStatusOperStatus 1(up), vplsStatusOperStatus 1(up),
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
} }
In the VPLS-LDP-DRAFT-01-MIB module: In the VPLS-LDP-DRAFT-01-MIB module:
In vplsLdpConfigTable: In vplsLdpConfigTable:
{ {
vplsLdpConfigMacAddrWithdraw 1(true), vplsLdpConfigMacAddrWithdraw 1(true),
} }
In vplsLdpPwBindTable: In vplsLdpPwBindTable:
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
{ {
vplsLdpPwBindType 1(mesh), vplsLdpPwBindType 1(mesh),
vplsLdpPwBindMacAddressLimit 100 vplsLdpPwBindMacAddressLimit 100
} }
6 Object definitions 6 Object definitions
6.1 VPLS-GENERIC-DRAFT-01-MIB 6.1 VPLS-GENERIC-DRAFT-01-MIB
This MIB module makes references to the following documents. This MIB module makes references to the following documents.
[RFC2578], [RFC2579], [RFC2580], [RFC2571], [RFC3411], [RFC2578], [RFC2579], [RFC2580], [RFC3411],
[RFC2863], [RFC4001], [RFC4265] and [RFC3813]. [RFC2863], [RFC4001], [RFC4265] and [RFC3813].
VPLS-GENERIC-DRAFT-01-MIB DEFINITIONS ::= BEGIN VPLS-GENERIC-DRAFT-01-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, Counter32, transmission Unsigned32, Counter32, IpAddress, transmission
FROM SNMPv2-SMI -- RFC2578 FROM SNMPv2-SMI -- RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC2580 FROM SNMPv2-CONF -- RFC2580
TruthValue, RowStatus, StorageType TruthValue, RowStatus, StorageType
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC2579
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC3411 FROM SNMP-FRAMEWORK-MIB -- RFC3411
PwIndexType PwIndexType
FROM PW-TC-STD-MIB FROM PW-TC-STD-MIB
VPNIdOrZero VPNIdOrZero
FROM VPN-TC-STD-MIB -- RFC4265 FROM VPN-TC-STD-MIB -- RFC4265
-- Vpls BGP Autodiscovery specific Textual Convention
VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Syntax for a route distinguisher. For a complete
definition of a route distinguisher, see [RFC 4364].
For more details on use of a route distinguisher
for a VPLS service, see [RFC 4761]"
REFERENCE
"[RFC 4364]"
SYNTAX OCTET STRING(SIZE (0..256))
VplsBgpRouteTarget ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Syntax for a route target. For a complete
definition of a route target, see [RFC 4364]."
REFERENCE
"[RFC 4364]"
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
SYNTAX OCTET STRING(SIZE (0..256))
VplsBgpRouteTargetType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Used to define the type of a route target usage.
Route targets can be specified to be imported,
exported, or both. For a complete definition of a
route target, see [RFC 4364]."
REFERENCE
"[RFC 4364]"
SYNTAX INTEGER { import(1), export(2), both(3) }
; ;
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
vplsGenericDraft01MIB MODULE-IDENTITY vplsGenericDraft01MIB MODULE-IDENTITY
LAST-UPDATED "200608301200Z" -- 30 Aug 2006 12:00:00 GMT LAST-UPDATED "200608301200Z" -- 30 Aug 2006 12:00:00 GMT
ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" "
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
skipping to change at page 8, line 29 skipping to change at page 8, line 45
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2008). The initial "Copyright (C) The IETF Trust (2008). The initial
version of this MIB module was published in RFC XXXX. version of this MIB module was published in RFC XXXX.
-- RFC Editor: Please replace XXXX with RFC number & remove -- RFC Editor: Please replace XXXX with RFC number & remove
-- this note. -- this note.
For full legal notices see the RFC itself or see: For full legal notices see the RFC itself or see:
http://www.ietf.org/copyrights/ianamib.html http://www.ietf.org/copyrights/ianamib.html
This MIB module contains generic managed object definitions This MIB module contains generic managed object definitions
for Virtual Private LAN Services as in [L2VPN-VPLS-LDP] and for Virtual Private LAN Services as in [RFC 4762] and
[L2VPN-VPLS-BGP] [RFC 4761]
This MIB module enables the use of any underlying Pseudo Wire This MIB module enables the use of any underlying Pseudo Wire
network." network."
-- Revision history. -- Revision history.
REVISION REVISION
"200608301200Z" -- 30 August 2006 12:00:00 GMT "200608301200Z" -- 30 August 2006 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Changes from previous version: "Changes from previous version:
1) Moved LDP Specific information to VPLS-LDP-DRAFT-01-MIB 1) Moved LDP Specific information to VPLS-LDP-DRAFT-01-MIB
2) Created the vplsStatusTable to store status information. 2) Created the vplsStatusTable to store status information.
3) 3)
" "
REVISION REVISION
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
"200606041200Z" -- 4 June 2006 12:00:00 GMT "200606041200Z" -- 4 June 2006 12:00:00 GMT
DESCRIPTION "Initial version published as part of RFC YYYY." DESCRIPTION "Initial version published as part of RFC YYYY."
-- RFC Editor: please replace YYYY with IANA assigned value, and -- RFC Editor: please replace YYYY with IANA assigned value, and
-- delete this note. -- delete this note.
::= { transmission XXXX } ::= { transmission XXXX }
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
-- RFC Editor: please replace XXXX with IANA assigne value, and -- RFC Editor: please replace XXXX with IANA assigne value, and
-- delete this note. -- delete this note.
-- Top-level components of this MIB. -- Top-level components of this MIB.
-- Notifications -- Notifications
vplsNotifications OBJECT IDENTIFIER vplsNotifications OBJECT IDENTIFIER
::= { vplsGenericDraft01MIB 0 } ::= { vplsGenericDraft01MIB 0 }
-- Tables, Scalars -- Tables, Scalars
skipping to change at page 9, line 51 skipping to change at page 10, line 4
::= { vplsObjects 1 } ::= { vplsObjects 1 }
vplsConfigTable OBJECT-TYPE vplsConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsConfigEntry SYNTAX SEQUENCE OF VplsConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies information for configuring "This table specifies information for configuring
and monitoring Virtual Private Lan Services(VPLS). and monitoring Virtual Private Lan Services(VPLS).
" "
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
::= { vplsObjects 2 } ::= { vplsObjects 2 }
vplsConfigEntry OBJECT-TYPE vplsConfigEntry OBJECT-TYPE
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
SYNTAX VplsConfigEntry SYNTAX VplsConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row in this table represents a Virtual Private Lan "A row in this table represents a Virtual Private Lan
Service(VPLS) in a packet network. It is indexed by Service(VPLS) in a packet network. It is indexed by
vplsConfigIndex, which uniquely identifies a single VPLS. vplsConfigIndex, which uniquely identifies a single VPLS.
A row is created by the operator or by the agent if a A row is created by the operator or by the agent if a
VPLS service is created by non-SNMP application or VPLS service is created by non-SNMP application or
skipping to change at page 11, line 4 skipping to change at page 10, line 56
vplsConfigFwdFullLowWatermark Unsigned32, vplsConfigFwdFullLowWatermark Unsigned32,
vplsConfigRowStatus RowStatus, vplsConfigRowStatus RowStatus,
vplsConfigMtu Unsigned32, vplsConfigMtu Unsigned32,
vplsConfigVpnId VPNIdOrZero, vplsConfigVpnId VPNIdOrZero,
vplsConfigServiceType INTEGER, vplsConfigServiceType INTEGER,
vplsConfigStorageType StorageType vplsConfigStorageType StorageType
} }
vplsConfigIndex OBJECT-TYPE vplsConfigIndex OBJECT-TYPE
SYNTAX Unsigned32 (1.. 2147483647) SYNTAX Unsigned32 (1.. 2147483647)
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Unique index for the conceptual row identifying "Unique index for the conceptual row identifying
a VPLS service." a VPLS service."
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
::= { vplsConfigEntry 1 } ::= { vplsConfigEntry 1 }
vplsConfigName OBJECT-TYPE vplsConfigName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual name of the VPLS. "A textual name of the VPLS.
If there is no local name, or this object is If there is no local name, or this object is
otherwise not applicable, then this object MUST otherwise not applicable, then this object MUST
skipping to change at page 12, line 4 skipping to change at page 11, line 50
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired administrative state of the VPLS "The desired administrative state of the VPLS
service. If the administrative status of the service. If the administrative status of the
Vpls service is changed to enable then this Vpls service is changed to enable then this
service is able to utilize the pseudo wire to service is able to utilize the pseudo wire to
perform the tasks of a VPLS service. perform the tasks of a VPLS service.
The testing(3) state indicates that no operational The testing(3) state indicates that no operational
packets can be passed. " packets can be passed. "
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
DEFVAL { down } DEFVAL { down }
::= { vplsConfigEntry 4 } ::= { vplsConfigEntry 4 }
vplsConfigMacLearning OBJECT-TYPE vplsConfigMacLearning OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies if MAC Learning is enabled "This object specifies if MAC Learning is enabled
in this service. If this object is true then Mac in this service. If this object is true then Mac
Learning is enabled. If false, then Mac Learning is Learning is enabled. If false, then Mac Learning is
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
disabled." disabled."
DEFVAL { true } DEFVAL { true }
::= { vplsConfigEntry 6 } ::= { vplsConfigEntry 6 }
vplsConfigDiscardUnknownDest OBJECT-TYPE vplsConfigDiscardUnknownDest OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the value of this object is 'true', then frames "If the value of this object is 'true', then frames
skipping to change at page 13, line 4 skipping to change at page 12, line 41
is disabled" is disabled"
DEFVAL { true } DEFVAL { true }
::= { vplsConfigEntry 8 } ::= { vplsConfigEntry 8 }
vplsConfigFwdFullHighWatermark OBJECT-TYPE vplsConfigFwdFullHighWatermark OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..100)
UNITS "percentage" UNITS "percentage"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
"This object specifies the utilization of the "This object specifies the utilization of the
forwarding database for this VPLS instance at forwarding database for this VPLS instance at
which the vplsFwdFullAlarmRaised notification which the vplsFwdFullAlarmRaised notification
will be sent." will be sent."
DEFVAL { 95 } DEFVAL { 95 }
::= { vplsConfigEntry 10 } ::= { vplsConfigEntry 10 }
vplsConfigFwdFullLowWatermark OBJECT-TYPE vplsConfigFwdFullLowWatermark OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..100)
UNITS "percentage" UNITS "percentage"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the utilization of the "This object specifies the utilization of the
forwarding database for this VPLS instance forwarding database for this VPLS instance
at which the vplsFwdFullAlarmCleared at which the vplsFwdFullAlarmCleared
notification will be sent." notification will be sent."
DEFVAL { 90 } DEFVAL { 90 }
::= { vplsConfigEntry 11 } ::= { vplsConfigEntry 11 }
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
vplsConfigRowStatus OBJECT-TYPE vplsConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For creating, modifying, and deleting this row. "For creating, modifying, and deleting this row.
None of the read-create objects in the None of the read-create objects in the
conceptual rows may be changed when this conceptual rows may be changed when this
object is in the active(1) state." object is in the active(1) state."
::= { vplsConfigEntry 12 } ::= { vplsConfigEntry 12 }
skipping to change at page 14, line 4 skipping to change at page 13, line 34
vpls instance." vpls instance."
DEFVAL { 1518 } DEFVAL { 1518 }
::= { vplsConfigEntry 13 } ::= { vplsConfigEntry 13 }
vplsConfigVpnId OBJECT-TYPE vplsConfigVpnId OBJECT-TYPE
SYNTAX VPNIdOrZero SYNTAX VPNIdOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This objects indicates the IEEE 802-1990 "This objects indicates the IEEE 802-1990
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
VPN ID of the associated VPLS service." VPN ID of the associated VPLS service."
-- Ed note: Should we import the VPNIdOrZero TC or -- Ed note: Should we import the VPNIdOrZero TC or
-- define a new TC? -- define a new TC?
::= { vplsConfigEntry 14 } ::= { vplsConfigEntry 14 }
vplsConfigServiceType OBJECT-TYPE vplsConfigServiceType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
vlan (1), vlan (1),
ethernet (2) ethernet (2)
} }
skipping to change at page 14, line 33 skipping to change at page 14, line 5
vplsConfigStorageType OBJECT-TYPE vplsConfigStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this row." "This variable indicates the storage type for this row."
DEFVAL { volatile } DEFVAL { volatile }
::= { vplsConfigEntry 16 } ::= { vplsConfigEntry 16 }
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
-- VPLS Status table -- VPLS Status table
vplsStatusTable OBJECT-TYPE vplsStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsStatusEntry SYNTAX SEQUENCE OF VplsStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides information for monitoring "This table provides information for monitoring
Virtual Private Lan Services(VPLS). Virtual Private Lan Services(VPLS).
" "
::= { vplsObjects 3 } ::= { vplsObjects 3 }
vplsStatusEntry OBJECT-TYPE vplsStatusEntry OBJECT-TYPE
SYNTAX VplsStatusEntry SYNTAX VplsStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 15, line 4 skipping to change at page 14, line 26
" "
::= { vplsObjects 3 } ::= { vplsObjects 3 }
vplsStatusEntry OBJECT-TYPE vplsStatusEntry OBJECT-TYPE
SYNTAX VplsStatusEntry SYNTAX VplsStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row in this table represents a Virtual Private Lan "A row in this table represents a Virtual Private Lan
Service(VPLS) in a packet network. It is indexed by Service(VPLS) in a packet network. It is indexed by
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
vplsConfigIndex, which uniquely identifies a single VPLS. vplsConfigIndex, which uniquely identifies a single VPLS.
A row in this table is automatically created by the agent A row in this table is automatically created by the agent
when a VPLS service is configured. when a VPLS service is configured.
" "
INDEX { vplsConfigIndex } INDEX { vplsConfigIndex }
::= { vplsStatusTable 1 } ::= { vplsStatusTable 1 }
VplsStatusEntry ::= VplsStatusEntry ::=
SEQUENCE { SEQUENCE {
skipping to change at page 15, line 41 skipping to change at page 15, line 5
vplsStatusPeerCount OBJECT-TYPE vplsStatusPeerCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This objects specifies the number of peers "This objects specifies the number of peers
present in this vpls instance." present in this vpls instance."
::= { vplsStatusEntry 2 } ::= { vplsStatusEntry 2 }
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
-- VPLS PW Binding Table -- VPLS PW Binding Table
vplsPwBindTable OBJECT-TYPE vplsPwBindTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsPwBindEntry SYNTAX SEQUENCE OF VplsPwBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides an association between a "This table provides an association between a
VPLS service and the corresponding Pseudo VPLS service and the corresponding Pseudo
Wires. A service can have more than one Pseudo Wires. A service can have more than one Pseudo
Wire association. Pseudo Wires are defined in Wire association. Pseudo Wires are defined in
the pwTable" the pwTable"
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
::= { vplsObjects 4 } ::= { vplsObjects 4 }
vplsPwBindEntry OBJECT-TYPE vplsPwBindEntry OBJECT-TYPE
SYNTAX VplsPwBindEntry SYNTAX VplsPwBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each row represents an association between a "Each row represents an association between a
VPLS instance and one or more Pseudo Wires VPLS instance and one or more Pseudo Wires
defined in the pwTable. Each index is unique defined in the pwTable. Each index is unique
in describing an entry in this table. However in describing an entry in this table. However
both indexes are required to define the one both indexes are required to define the one
to many association of service to to many association of service to
pseudowire." pseudowire."
INDEX { vplsConfigIndex, vplsPwBindIndex } INDEX { vplsConfigIndex, vplsPwBindIndex }
::= { vplsPwBindTable 1 } ::= { vplsPwBindTable 1 }
VplsPwBindEntry ::= VplsPwBindEntry ::=
SEQUENCE { SEQUENCE {
vplsPwBindIndex PwIndexType,
vplsPwBindConfigType INTEGER, vplsPwBindConfigType INTEGER,
vplsPwBindType INTEGER, vplsPwBindType INTEGER,
vplsPwBindRowStatus RowStatus, vplsPwBindRowStatus RowStatus,
vplsPwBindStorageType StorageType vplsPwBindStorageType StorageType
} }
vplsPwBindIndex OBJECT-TYPE
SYNTAX PwIndexType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Secondary Index for the conceptual row identifying
a pseudowire within the PwEntry which MUST
match an entry from the PW-STD-MIB's PwTable
which represents an already-provisioned
pseuwowire that is then associated with this
VPLS instance."
::= { vplsPwBindEntry 1 }
vplsPwBindConfigType OBJECT-TYPE vplsPwBindConfigType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
manual (1), manual (1),
autodiscovery (2) autodiscovery (2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object indicates "The value of this object indicates
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
whether the Pseudo Wire binding was created whether the Pseudo Wire binding was created
manually or via autodiscovery. manually or via autodiscovery.
The value of this object must be The value of this object must be
specifed when the row is created and cannot specifed when the row is created and cannot
be changed while the row status is active(1)" be changed while the row status is active(1)"
::= { vplsPwBindEntry 2 } ::= { vplsPwBindEntry 1 }
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
vplsPwBindType OBJECT-TYPE vplsPwBindType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
mesh (1), mesh (1),
spoke (2) spoke (2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object indicates "The value of this object indicates
whether the Pseudo Wire binding is of whether the Pseudo Wire binding is of
type mesh or spoke. type mesh or spoke.
The value of this object must be The value of this object must be
specifed when the row is created and cannot specifed when the row is created and cannot
be changed while the row status is active(1)" be changed while the row status is active(1)"
::= { vplsPwBindEntry 3 } ::= { vplsPwBindEntry 2 }
vplsPwBindRowStatus OBJECT-TYPE vplsPwBindRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For creating, modifying, and deleting this row. "For creating, modifying, and deleting this row.
None of the read-create objects in the None of the read-create objects in the
conceptual rows may be changed when this conceptual rows may be changed when this
object is in the active(1) state" object is in the active(1) state"
::= { vplsPwBindEntry 4 } ::= { vplsPwBindEntry 3 }
vplsPwBindStorageType OBJECT-TYPE vplsPwBindStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this row." "This variable indicates the storage type for this row."
DEFVAL { volatile } DEFVAL { volatile }
::= { vplsPwBindEntry 5 } ::= { vplsPwBindEntry 4 }
-- vplsBgpADConfigTable
vplsBgpADConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsBgpADEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies information for configuring
BGP Auto-discovery parameters for a given Vpls service.
"
::= { vplsObjects 5 }
vplsBgpADConfigEntry OBJECT-TYPE
SYNTAX VplsBgpADConfigEntry
MAX-ACCESS not-accessible
STATUS current
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
DESCRIPTION
"The creation of a row in this table represents that BGP
based autodiscovery is in use for this instance of Vpls.
A row in this table is indexed by vplsConfigIndex, which
uniquely identifies a single VPLS.
A row is created by the operator or agent prior
to autodiscovery.
None of the read-create objects can be changed when
vplsBGPADConfigRowStatus is in active(1) state. Changes
are allowed when the vplsBGPADConfigRowStatus is in
notInService(2) or notReady(3) states only.
If the operator needs to change one of the values
for an active row, vplsBGPADConfigRowStatus should be
changed to notInService(2). The objects may then
be modified. Change the rowStatus back to active(1) in
order to re-initiate the signaling process with the new
values in effect.
"
INDEX { vplsConfigIndex }
::= { vplsBgpADConfigTable 1 }
VplsBgpADConfigEntry ::=
SEQUENCE {
vplsBgpADConfigRouteDistinguisher VplsBgpRouteDistinguisher,
vplsBgpADConfigPrefix IpAddress,
vplsBgpADConfigVplsId VplsBgpRouteDistinguisher,
vplsBgpADConfigRowStatus RowStatus
}
vplsBgpADConfigRouteDistinguisher OBJECT-TYPE
SYNTAX VplsBgpRouteDistinguisher
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" " The route distinguisher for this VPLS. See [RFC 4364]
for a complete definition of a route distinguisher.
See [RFC 4761] for more details on use of a route
distinguisher for a VPLS service.
"
DEFVAL { "" }
::= { vplsBgpADConfigEntry 1 }
vplsBgpADConfigPrefix OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" In case of auto-discovery, the default prefix advertised
is the IP address of the loopback. In case the user wants
to override the loopback address, vplsBgpADConfigPrefix
should be set to a value other than 0.0.0.0. This value
will then be used as the advertised IP address in the NLRI.
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
"
DEFVAL { 0.0.0.0 }
::= { vplsBgpADConfigEntry 2 }
vplsBgpADConfigVplsId OBJECT-TYPE
SYNTAX VplsBgpRouteDistinguisher
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" VplsId is a unique identifier for all VSIs belonging to
the same VPLS. It is advertised as an extended community
"
DEFVAL { "" }
::= { vplsBgpADConfigEntry 3 }
vplsBgpADConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" For creating, modifying, and deleting this row.
None of the read-create objects in the
conceptual rows may be changed when this
object is in the active(1) state.
"
::= { vplsBgpADConfigEntry 4 }
-- vplsBgpRteTargetTable
vplsBgpRteTargetTable OBJECT-TYPE
SYNTAX SEQUENCE Of VplsBgpRteTargetEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" This table specifies the list of Route Targets
imported or exported by BGP during auto-discovery of VPLS.
"
::= { vplsObjects 6 }
vplsBgpRteTargetEntry OBJECT-TYPE
SYNTAX VplsBgpRteTargetEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" An entry in this table specifies the value of the
Route Target being used by BGP. Depending on the value
of vplsBgpRteTargetType, an RT might be exported or
imported or both. Every VPLS, which uses auto-discovery
for finding peer nodes, can import and export multiple
Route Targets. This representation allows
support for hierarchical VPLS.
A row is created by the operator or agent prior
to autodiscovery.
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
"
INDEX { vplsConfigIndex, vplsBgpRteTargetIndex }
::= { vpsBgpRteTargetTable 1 }
VplsBgpRteTargetEntry ::=
SEQUENCE {
vplsBgpRteTargetIndex Unsigned32,
vplsBgpRteTargetRTType VplsBgpRouteTargetType,
vplsBgpRteTargetRT VplsBgpRouteTarget,
vplsBgpRteTargetRTRowStatus RowStatus
}
vplsBgpRteTargetIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This index along with vplsConfigIndex,identifies one entry
in the vplsBgpRteTargetTable. Multiple Route Targets may be
associated with a single VPLS service.
"
::= { vplsBgpADConfigEntry 1 }
vplsBgpRteTargetRTType OBJECT-TYPE
SYNTAX VplsBgpRouteTargetType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" Used to define the type of a route target usage.
Route targets can be specified to be imported,
exported, or both. For a complete definition of a
route target, see [RFC 4364]."
"
DEFVAL { "" }
::= { vplsBgpADConfigEntry 2 }
vplsBgpRteTargetRT OBJECT-TYPE
SYNTAX VplsBgpRouteTarget
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" The route target associated with the VPLS service.
For more details on use of route targets
for a VPLS service, see [RFC 4761]
"
::= { vplsBgpADConfigEntry 3 }
vplsBgpRteTargetRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table. When a row in this
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
table is in active(1) state, no objects in that row
can be modified.
"
::= { vplsBgpADConfigEntry 4 }
vplsStatusNotifEnable OBJECT-TYPE vplsStatusNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is set to true(1), then it enables "If this object is set to true(1), then it enables
the emission of vplsStatusChanged the emission of vplsStatusChanged
notification; otherwise this notification is not notification; otherwise this notification is not
emitted." emitted."
REFERENCE REFERENCE
"See also [RFC3413] for explanation that "See also [RFC3413] for explanation that
notifications are under the ultimate control of the notifications are under the ultimate control of the
MIB module in this document." MIB module in this document."
DEFVAL { false } DEFVAL { false }
::= { vplsObjects 5 } ::= { vplsObjects 7 }
vplsNotificationMaxRate OBJECT-TYPE vplsNotificationMaxRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum number of "This object indicates the maximum number of
notifications issued per second. If events occur notifications issued per second. If events occur
more rapidly, the implementation may simply fail to more rapidly, the implementation may simply fail to
emit these notifications during that period, or may emit these notifications during that period, or may
queue them until an appropriate time. A value of 0 queue them until an appropriate time. A value of 0
means no throttling is applied and events may be means no throttling is applied and events may be
notified at the rate at which they occur." notified at the rate at which they occur."
DEFVAL { 0 } DEFVAL { 0 }
::= { vplsObjects 6 } ::= { vplsObjects 8 }
-- VPLS Service Notifications -- VPLS Service Notifications
vplsStatusChanged NOTIFICATION-TYPE vplsStatusChanged NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vplsConfigVpnId, vplsConfigVpnId,
vplsConfigAdminStatus, vplsConfigAdminStatus,
vplsStatusOperStatus vplsStatusOperStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vplsStatusChanged notification is generated "The vplsStatusChanged notification is generated
when there is a change in the administrative or when there is a change in the administrative or
operating status of a VPLS service." operating status of a VPLS service."
::= { vplsNotifications 1 } ::= { vplsNotifications 1 }
vplsFwdFullAlarmRaised NOTIFICATION-TYPE vplsFwdFullAlarmRaised NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vplsConfigVpnId, vplsConfigVpnId,
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
vplsConfigFwdFullHighWatermark, vplsConfigFwdFullHighWatermark,
vplsConfigFwdFullLowWatermark vplsConfigFwdFullLowWatermark
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vplsFwdFullAlarmRaised notification is "The vplsFwdFullAlarmRaised notification is
generated when the utilization of the Forwarding generated when the utilization of the Forwarding
database is above the value specified by database is above the value specified by
vplsConfigFwdFullHighWatermark." vplsConfigFwdFullHighWatermark."
::= { vplsNotifications 2 } ::= { vplsNotifications 2 }
vplsFwdFullAlarmCleared NOTIFICATION-TYPE vplsFwdFullAlarmCleared NOTIFICATION-TYPE
skipping to change at page 19, line 46 skipping to change at page 21, line 49
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations that "Compliance requirement for implementations that
provide full support for VPLS-GENERIC-DRAFT-01-MIB. provide full support for VPLS-GENERIC-DRAFT-01-MIB.
Such devices can then be monitored and configured using Such devices can then be monitored and configured using
this MIB module." this MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
vplsGroup, vplsGroup,
vplsPwBindGroup, vplsPwBindGroup,
VplsBgpADConfigGroup,
VplsBgpRteTargetGroup,
vplsNotificationGroup vplsNotificationGroup
} }
::= { vplsCompliances 1 } ::= { vplsCompliances 1 }
vplsModuleReadOnlyCompliance MODULE-COMPLIANCE vplsModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations that only "Compliance requirement for implementations that only
provide read-only support for VPLS-GENERIC-DRAFT-01-MIB. provide read-only support for VPLS-GENERIC-DRAFT-01-MIB.
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
Such devices can then be monitored but cannot be Such devices can then be monitored but cannot be
configured using this MIB modules." configured using this MIB modules."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
vplsGroup, vplsGroup,
vplsPwBindGroup, vplsPwBindGroup,
VplsBgpADConfigGroup,
VplsBgpRteTargetGroup,
vplsNotificationGroup vplsNotificationGroup
} }
OBJECT vplsConfigName OBJECT vplsConfigName
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsConfigDescr OBJECT vplsConfigDescr
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 21, line 4 skipping to change at page 22, line 53
"Write access is not required." "Write access is not required."
OBJECT vplsConfigMacAging OBJECT vplsConfigMacAging
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsConfigFwdFullHighWatermark OBJECT vplsConfigFwdFullHighWatermark
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
"Write access is not required." "Write access is not required."
OBJECT vplsConfigFwdFullLowWatermark OBJECT vplsConfigFwdFullLowWatermark
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
OBJECT vplsConfigRowStatus OBJECT vplsConfigRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsConfigMtu OBJECT vplsConfigMtu
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 21, line 43 skipping to change at page 23, line 37
OBJECT vplsPwBindType OBJECT vplsPwBindType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsPwBindRowStatus OBJECT vplsPwBindRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsBgpADConfigRouteDistinguisher
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT vplsBgpADConfigPrefix
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT vplsBgpADConfigVplsId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT vplsBgpADConfigRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT vplsBgpRteTargetRTType
MIN-ACCESS read-only
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
DESCRIPTION
"Write access is not required."
OBJECT vplsBgpRteTargetRT
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT vplsBgpRteTargetRTRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { vplsCompliances 2 } ::= { vplsCompliances 2 }
-- Units of conformance. -- Units of conformance.
vplsGroups vplsGroups
OBJECT IDENTIFIER ::= { vplsConformance 2 } OBJECT IDENTIFIER ::= { vplsConformance 2 }
vplsGroup OBJECT-GROUP vplsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
vplsConfigName, vplsConfigName,
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
vplsConfigDescr, vplsConfigDescr,
vplsConfigAdminStatus, vplsConfigAdminStatus,
vplsConfigMacLearning, vplsConfigMacLearning,
vplsConfigDiscardUnknownDest, vplsConfigDiscardUnknownDest,
vplsConfigMacAging, vplsConfigMacAging,
vplsConfigVpnId, vplsConfigVpnId,
vplsConfigFwdFullHighWatermark, vplsConfigFwdFullHighWatermark,
vplsConfigFwdFullLowWatermark, vplsConfigFwdFullLowWatermark,
vplsConfigRowStatus, vplsConfigRowStatus,
vplsConfigIndexNext, vplsConfigIndexNext,
skipping to change at page 22, line 36 skipping to change at page 25, line 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects supporting "The group of objects supporting
management of L2VPN VPLS services" management of L2VPN VPLS services"
::= { vplsGroups 1 } ::= { vplsGroups 1 }
vplsPwBindGroup OBJECT-GROUP vplsPwBindGroup OBJECT-GROUP
OBJECTS { OBJECTS {
vplsPwBindConfigType, vplsPwBindConfigType,
vplsPwBindType, vplsPwBindType,
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
vplsPwBindRowStatus, vplsPwBindRowStatus,
vplsPwBindStorageType vplsPwBindStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects supporting "The group of objects supporting
management of management of
Pseudo Wire (PW) Binding to VPLS." Pseudo Wire (PW) Binding to VPLS."
::= { vplsGroups 2 } ::= { vplsGroups 2 }
VplsBgpADConfigGroup OBJECT-GROUP
OBJECTS {
vplsBgpADConfigRouteDistinguisher,
vplsBgpADConfigPrefix,
vplsBgpADConfigVplsId,
vplsBgpADConfigRowStatus
}
STATUS current
DESCRIPTION
"The group of objects supporting
management of BGP-Autodiscovery for VPLS."
::= { vplsGroups 3 }
VplsBgpRteTargetGroup OBJECT-GROUP
OBJECTS {
vplsBgpRteTargetRTType,
vplsBgpRteTargetRT,
vplsBgpRteTargetRTRowStatus
}
STATUS current
DESCRIPTION
"The group of objects supporting
management of Route Targets during
BGP-Autodiscovery for VPLS."
::= { vplsGroups 4 }
vplsNotificationGroup NOTIFICATION-GROUP vplsNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
vplsStatusChanged, vplsStatusChanged,
vplsFwdFullAlarmRaised, vplsFwdFullAlarmRaised,
vplsFwdFullAlarmCleared vplsFwdFullAlarmCleared
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
"The group of notifications supporting "The group of notifications supporting
the Notifications generated for the Notifications generated for
VPLS Services" VPLS Services"
::= { vplsGroups 3 } ::= { vplsGroups 5 }
END END
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
6.2 VPLS-LDP-DRAFT-01-MIB Object definitions 6.2 VPLS-LDP-DRAFT-01-MIB Object definitions
This MIB module makes references to the following documents. This MIB module makes references to the following documents.
[RFC2578], [RFC2579], [RFC2580], [RFC2571], [RFC3411], [RFC2578], [RFC2579], [RFC2580], [RFC3411],
[RFC2863], [RFC4001], [RFC4265] and [RFC3813]. [RFC2863], [RFC4001], [RFC4265] and [RFC3813].
VPLS-LDP-DRAFT-01-MIB DEFINITIONS ::= BEGIN VPLS-LDP-DRAFT-01-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, transmission Unsigned32, transmission
FROM SNMPv2-SMI -- RFC2578 FROM SNMPv2-SMI -- RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
skipping to change at page 24, line 5 skipping to change at page 26, line 47
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
The L2VPN Working Group (email distribution l2vpn@ietf.org, The L2VPN Working Group (email distribution l2vpn@ietf.org,
http://www.ietf.org/html.charters/l2vpn-charter.html) http://www.ietf.org/html.charters/l2vpn-charter.html)
" "
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2008). The initial "Copyright (C) The IETF Trust (2008). The initial
version of this MIB module was published in RFC XXXX. version of this MIB module was published in RFC XXXX.
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
-- RFC Editor: Please replace XXXX with RFC number & remove -- RFC Editor: Please replace XXXX with RFC number & remove
-- this note. -- this note.
For full legal notices see the RFC itself or see: For full legal notices see the RFC itself or see:
http://www.ietf.org/copyrights/ianamib.html http://www.ietf.org/copyrights/ianamib.html
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
LDP signalled Virtual Private LAN Services as in LDP signalled Virtual Private LAN Services as in
[L2VPN-VPLS-LDP] [RFC 4762]
This MIB module enables the use of any underlying Pseudo Wire This MIB module enables the use of any underlying Pseudo Wire
network. " network. "
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
-- Revision history. -- Revision history.
REVISION REVISION
"200608301200Z" -- 30 Aug 2006 12:00:00 GMT "200608301200Z" -- 30 Aug 2006 12:00:00 GMT
DESCRIPTION "Initial version published as part of RFC YYYY." DESCRIPTION "Initial version published as part of RFC YYYY."
-- RFC Editor: please replace YYYY with IANA assigned value, and -- RFC Editor: please replace YYYY with IANA assigned value, and
-- delete this note. -- delete this note.
::= { transmission XXXX } ::= { transmission XXXX }
-- RFC Editor: please replace XXXX with IANA assigne value, and -- RFC Editor: please replace XXXX with IANA assigne value, and
skipping to change at page 25, line 4 skipping to change at page 27, line 42
DESCRIPTION DESCRIPTION
"This table specifies information for configuring "This table specifies information for configuring
and monitoring LDP specific parameters for and monitoring LDP specific parameters for
Virtual Private Lan Services(VPLS)." Virtual Private Lan Services(VPLS)."
::= { vplsLdpObjects 1 } ::= { vplsLdpObjects 1 }
vplsLdpConfigEntry OBJECT-TYPE vplsLdpConfigEntry OBJECT-TYPE
SYNTAX VplsLdpConfigEntry SYNTAX VplsLdpConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
DESCRIPTION DESCRIPTION
"A row in this table represents LDP specific information "A row in this table represents LDP specific information
for Virtual Private Lan Service(VPLS) in a packet network. for Virtual Private Lan Service(VPLS) in a packet network.
It is indexed by vplsConfigIndex, which uniquely It is indexed by vplsConfigIndex, which uniquely
identifies a single VPLS. identifies a single VPLS.
A row is automatically created when a VPLS service is A row is automatically created when a VPLS service is
configured using LDP signalling. configured using LDP signalling.
None of the read-create objects values can be None of the read-create objects values can be
changed when vplsRowStatus is in the active(1) changed when vplsRowStatus is in the active(1)
state. Changes are allowed when the vplsRowStatus state. Changes are allowed when the vplsRowStatus
is in notInService(2) or notReady(3) states only. is in notInService(2) or notReady(3) states only.
If the operator need to change one of the values If the operator need to change one of the values
for an active row the vplsConfigRowStatus should be for an active row the vplsConfigRowStatus should be
first changed to notInService(2), the objects may first changed to notInService(2), the objects may
be changed now, and later to active(1) in order to be changed now, and later to active(1) in order to
re-initiate the signaling process with the new re-initiate the signaling process with the new
values in effect. values in effect.
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
" "
INDEX { vplsConfigIndex } INDEX { vplsConfigIndex }
::= { vplsLdpConfigTable 1 } ::= { vplsLdpConfigTable 1 }
VplsLdpConfigEntry ::= VplsLdpConfigEntry ::=
SEQUENCE { SEQUENCE {
vplsLdpConfigMacAddrWithdraw TruthValue vplsLdpConfigMacAddrWithdraw TruthValue
} }
vplsLdpConfigMacAddrWithdraw OBJECT-TYPE vplsLdpConfigMacAddrWithdraw OBJECT-TYPE
skipping to change at page 26, line 4 skipping to change at page 28, line 36
::= { vplsLdpConfigEntry 1 } ::= { vplsLdpConfigEntry 1 }
-- VPLS LDP PW Binding Table -- VPLS LDP PW Binding Table
vplsLdpPwBindTable OBJECT-TYPE vplsLdpPwBindTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsLdpPwBindEntry SYNTAX SEQUENCE OF VplsLdpPwBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides LDP specific information for "This table provides LDP specific information for
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
an association between a VPLS service and the an association between a VPLS service and the
corresponding Pseudo Wires. A service can have more corresponding Pseudo Wires. A service can have more
than one Pseudo Wire association. Pseudo Wires are than one Pseudo Wire association. Pseudo Wires are
defined in the pwTable." defined in the pwTable."
::= { vplsLdpObjects 2 } ::= { vplsLdpObjects 2 }
vplsLdpPwBindEntry OBJECT-TYPE vplsLdpPwBindEntry OBJECT-TYPE
SYNTAX VplsLdpPwBindEntry SYNTAX VplsLdpPwBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 26, line 31 skipping to change at page 29, line 4
both indexes are required to define the one both indexes are required to define the one
to many association of service to pseudowire. to many association of service to pseudowire.
An entry in this table in instantiated only when An entry in this table in instantiated only when
LDP signalling is used to configure VPLS service. LDP signalling is used to configure VPLS service.
Each entry in this table provides LDP specific Each entry in this table provides LDP specific
information for the VPlS represented by information for the VPlS represented by
vplsConfigIndex." vplsConfigIndex."
INDEX { vplsConfigIndex, vplsPwBindIndex } INDEX { vplsConfigIndex, vplsPwBindIndex }
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
::= { vplsLdpPwBindTable 1 } ::= { vplsLdpPwBindTable 1 }
VplsLdpPwBindEntry ::= VplsLdpPwBindEntry ::=
SEQUENCE { SEQUENCE {
vplsLdpPwBindMacAddressLimit Unsigned32 vplsLdpPwBindMacAddressLimit Unsigned32
} }
vplsLdpPwBindMacAddressLimit OBJECT-TYPE vplsLdpPwBindMacAddressLimit OBJECT-TYPE
SYNTAX Unsigned32 (0.. 4294967295) SYNTAX Unsigned32 (0.. 4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 27, line 4 skipping to change at page 29, line 30
of learned and static entries allowed in the of learned and static entries allowed in the
Forwarding database for this PW Binding. The value 0 Forwarding database for this PW Binding. The value 0
means there is no limit for this PW Binding." means there is no limit for this PW Binding."
DEFVAL { 0 } DEFVAL { 0 }
::= { vplsLdpPwBindEntry 1 } ::= { vplsLdpPwBindEntry 1 }
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
vplsLdpCompliances vplsLdpCompliances
OBJECT IDENTIFIER ::= { vplsLdpConformance 1 } OBJECT IDENTIFIER ::= { vplsLdpConformance 1 }
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
vplsLdpModuleFullCompliance MODULE-COMPLIANCE vplsLdpModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations that "Compliance requirement for implementations that
provide full support for VPLS-LDP-DRAFT-01-MIB. provide full support for VPLS-LDP-DRAFT-01-MIB.
Such devices can then be monitored and configured using Such devices can then be monitored and configured using
this MIB module." this MIB module."
MODULE -- this module MODULE -- this module
skipping to change at page 27, line 36 skipping to change at page 30, line 5
provide read-only support for VPLS-LDP-DRAFT-01-MIB. provide read-only support for VPLS-LDP-DRAFT-01-MIB.
Such devices can then be monitored but cannot be Such devices can then be monitored but cannot be
configured using this MIB modules." configured using this MIB modules."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
vplsLdpGroup vplsLdpGroup
} }
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
OBJECT vplsLdpConfigMacAddrWithdraw OBJECT vplsLdpConfigMacAddrWithdraw
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsLdpPwBindMacAddressLimit OBJECT vplsLdpPwBindMacAddressLimit
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { vplsLdpCompliances 2 } ::= { vplsLdpCompliances 2 }
-- Units of conformance. -- Units of conformance.
vplsLdpGroups vplsLdpGroups
OBJECT IDENTIFIER ::= { vplsLdpConformance 2 } OBJECT IDENTIFIER ::= { vplsLdpConformance 2 }
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
vplsLdpGroup OBJECT-GROUP vplsLdpGroup OBJECT-GROUP
OBJECTS { OBJECTS {
vplsLdpConfigMacAddrWithdraw, vplsLdpConfigMacAddrWithdraw,
vplsLdpPwBindMacAddressLimit vplsLdpPwBindMacAddressLimit
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects supporting "The group of objects supporting
management of L2VPN VPLS services using LDP." management of L2VPN VPLS services using LDP."
skipping to change at page 28, line 42 skipping to change at page 31, line 4
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC2579
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC3411 FROM SNMP-FRAMEWORK-MIB -- RFC3411
vplsConfigIndex, vplsPwBindIndex vplsConfigIndex, vplsPwBindIndex
FROM VPLS-GENERIC-DRAFT-01-MIB FROM VPLS-GENERIC-DRAFT-01-MIB
; ;
vplsBgpDraft01MIB MODULE-IDENTITY vplsBgpDraft01MIB MODULE-IDENTITY
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
LAST-UPDATED "200612061200Z" -- 06 Dec 2006 12:00:00 GMT LAST-UPDATED "200612061200Z" -- 06 Dec 2006 12:00:00 GMT
ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" "
V. J. Shah V. J. Shah
Email: vshah@juniper.net Email: vshah@juniper.net
The L2VPN Working Group (email distribution l2vpn@ietf.org, The L2VPN Working Group (email distribution l2vpn@ietf.org,
http://www.ietf.org/html.charters/l2vpn-charter.html) http://www.ietf.org/html.charters/l2vpn-charter.html)
" "
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2008). The initial "Copyright (C) The IETF Trust (2008). The initial
version of this MIB module was published in RFC XXXX. version of this MIB module was published in RFC XXXX.
-- RFC Editor: Please replace XXXX with RFC number & remove -- RFC Editor: Please replace XXXX with RFC number & remove
-- this note. -- this note.
For full legal notices see the RFC itself or see: For full legal notices see the RFC itself or see:
http://www.ietf.org/copyrights/ianamib.html http://www.ietf.org/copyrights/ianamib.html
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
BGP signalled Virtual Private LAN Services as in BGP signalled Virtual Private LAN Services as in
[L2VPN-VPLS-BGP] [RFC 4761]
This MIB module enables the use of any underlying Pseudo Wire This MIB module enables the use of any underlying Pseudo Wire
network. " network. "
-- Revision history. -- Revision history.
REVISION REVISION
"200612061200Z" -- 06 Dec 2006 12:00:00 GMT "200612061200Z" -- 06 Dec 2006 12:00:00 GMT
DESCRIPTION "Initial version published as part of RFC YYYY." DESCRIPTION "Initial version published as part of RFC YYYY."
-- RFC Editor: please replace YYYY with IANA assigned value, and -- RFC Editor: please replace YYYY with IANA assigned value, and
-- delete this note. -- delete this note.
skipping to change at page 29, line 39 skipping to change at page 31, line 51
-- RFC Editor: please replace XXXX with IANA assigne value, and -- RFC Editor: please replace XXXX with IANA assigne value, and
-- delete this note. -- delete this note.
-- VPLS BGP specific Textual Conventions. -- VPLS BGP specific Textual Conventions.
VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Syntax for a route distinguisher. For a complete "Syntax for a route distinguisher. For a complete
definition of a route distinguisher, see [RFC4364]. definition of a route distinguisher, see [RFC4364].
For more details on use of a route distinguisher For more details on use of a route distinguisher
for a VPLS service, see [L2VPN-VPLS-BGP]" for a VPLS service, see [RFC 4761]"
REFERENCE REFERENCE
"[RFC4364]" "[RFC4364]"
SYNTAX OCTET STRING(SIZE (0..256)) SYNTAX OCTET STRING(SIZE (0..256))
VplsBgpRouteTarget ::= TEXTUAL-CONVENTION VplsBgpRouteTarget ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Syntax for a route target. For a complete "Syntax for a route target. For a complete
definition of a route target, see [RFC4364]." definition of a route target, see [RFC4364]."
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
REFERENCE REFERENCE
"[RFC4364]" "[RFC4364]"
SYNTAX OCTET STRING(SIZE (0..256)) SYNTAX OCTET STRING(SIZE (0..256))
-- Top-level components of this MIB. -- Top-level components of this MIB.
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
-- Tables, Scalars -- Tables, Scalars
vplsBgpObjects OBJECT IDENTIFIER vplsBgpObjects OBJECT IDENTIFIER
::= { vplsBgpDraft01MIB 1 } ::= { vplsBgpDraft01MIB 1 }
-- Conformance -- Conformance
vplsBgpConformance OBJECT IDENTIFIER vplsBgpConformance OBJECT IDENTIFIER
::= { vplsBgpDraft01MIB 2 } ::= { vplsBgpDraft01MIB 2 }
-- Vpls Bgp Config Table -- Vpls Bgp Config Table
vplsBgpConfigTable OBJECT-TYPE vplsBgpConfigTable OBJECT-TYPE
skipping to change at page 31, line 4 skipping to change at page 32, line 60
for an active row the vplsConfigRowStatus should be for an active row the vplsConfigRowStatus should be
first changed to notInService(2), the objects may first changed to notInService(2), the objects may
be changed now, and later to active(1) in order to be changed now, and later to active(1) in order to
re-initiate the signaling process with the new re-initiate the signaling process with the new
values in effect. values in effect.
" "
INDEX { vplsConfigIndex } INDEX { vplsConfigIndex }
::= { vplsBgpConfigTable 1 } ::= { vplsBgpConfigTable 1 }
VplsBgpConfigEntry ::= VplsBgpConfigEntry ::=
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
SEQUENCE { SEQUENCE {
vplsBgpConfigRouteDistinguisher VplsBgpRouteDistinguisher,
vplsBgpConfigRouteTarget VplsBgpRouteTarget,
vplsBgpConfigVERangeSize Unsigned32
}
vplsBgpConfigRouteDistinguisher OBJECT-TYPE draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
SYNTAX VplsBgpRouteDistinguisher
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The route distinguisher for this VPLS. See [RFC4364]
for a complete definition of a route distinguisher.
For more details on use of a route distinguisher
for a VPLS service, see [L2VPN-VPLS-BGP]"
DEFVAL { "" }
::= { vplsBgpConfigEntry 1 }
vplsBgpConfigRouteTarget OBJECT-TYPE vplsBgpConfigVERangeSize Unsigned32
SYNTAX VplsBgpRouteTarget }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The route target associated with the VPLS service.
For more details on use of route targets
for a VPLS service, see [L2VPN-VPLS-BGP]"
DEFVAL { "" }
::= { vplsBgpConfigEntry 2 }
vplsBgpConfigVERangeSize OBJECT-TYPE vplsBgpConfigVERangeSize OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the size of the range of VE ids in this "Specifies the size of the range of VE ids in this
VPLS service. This number controls the size of the VPLS service. This number controls the size of the
label block advertised for this VE by the PE. label block advertised for this VE by the PE.
A value of 0 indicates that the range is not A value of 0 indicates that the range is not
configured and the PE derives the range value configured and the PE derives the range value
from received advertisements from other PEs." from received advertisements from other PEs."
DEFVAL { 0 } DEFVAL { 0 }
::= { vplsBgpConfigEntry 3 } ::= { vplsBgpConfigEntry 1 }
-- Vpls Edge Device (VE) Identifier Table -- Vpls Edge Device (VE) Identifier Table
vplsBgpVETable OBJECT-TYPE vplsBgpVETable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsBgpVEEntry SYNTAX SEQUENCE OF VplsBgpVEEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table associates VPLS Edge devices to a VPLS service" "This table associates VPLS Edge devices to a VPLS service"
::= { vplsBgpObjects 3 } ::= { vplsBgpObjects 2 }
vplsBgpVEEntry OBJECT-TYPE vplsBgpVEEntry OBJECT-TYPE
SYNTAX VplsBgpVEEntry SYNTAX VplsBgpVEEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created for each VE Id "An entry in this table is created for each VE Id
configured on a PE for a particular VPLS service configured on a PE for a particular VPLS service
instance." instance."
INDEX { vplsConfigIndex, vplsBgpVEId } INDEX { vplsConfigIndex, vplsBgpVEId }
skipping to change at page 32, line 39 skipping to change at page 34, line 5
vplsBgpVEId OBJECT-TYPE vplsBgpVEId OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A secondary index identifying a VE within an "A secondary index identifying a VE within an
instance of a VPLS service." instance of a VPLS service."
::= { vplsBgpVEEntry 1 } ::= { vplsBgpVEEntry 1 }
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
vplsBgpVEName OBJECT-TYPE vplsBgpVEName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Descriptive name for the site or u-PE assciated with "Descriptive name for the site or u-PE assciated with
this VE Id." this VE Id."
DEFVAL { "" } DEFVAL { "" }
::= { vplsBgpVEEntry 2 } ::= { vplsBgpVEEntry 2 }
vplsBgpVEPreference OBJECT-TYPE vplsBgpVEPreference OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
"Specifies the preference of the VE Id on this PE "Specifies the preference of the VE Id on this PE
if the site is multi-homed and VE Id is re-used." if the site is multi-homed and VE Id is re-used."
DEFVAL { 0 } DEFVAL { 0 }
::= { vplsBgpVEEntry 3 } ::= { vplsBgpVEEntry 3 }
vplsBgpVERowStatus OBJECT-TYPE vplsBgpVERowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 33, line 43 skipping to change at page 34, line 59
vplsBgpPwBindTable OBJECT-TYPE vplsBgpPwBindTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsBgpPwBindEntry SYNTAX SEQUENCE OF VplsBgpPwBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides BGP specific information for "This table provides BGP specific information for
an association between a VPLS service and the an association between a VPLS service and the
corresponding Pseudo Wires. A service can have more corresponding Pseudo Wires. A service can have more
than one Pseudo Wire association. Pseudo Wires are than one Pseudo Wire association. Pseudo Wires are
defined in the pwTable." defined in the pwTable."
::= { vplsBgpObjects 4 } ::= { vplsBgpObjects 3 }
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
vplsBgpPwBindEntry OBJECT-TYPE vplsBgpPwBindEntry OBJECT-TYPE
SYNTAX VplsBgpPwBindEntry SYNTAX VplsBgpPwBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each row represents an association between a "Each row represents an association between a
VPLS instance and one or more Pseudo Wires VPLS instance and one or more Pseudo Wires
defined in the pwTable. Each index is unique defined in the pwTable. Each index is unique
in describing an entry in this table. However in describing an entry in this table. However
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
both indexes are required to define the one both indexes are required to define the one
to many association of service to pseudowire. to many association of service to pseudowire.
An entry in this table in instantiated only when An entry in this table in instantiated only when
BGP signalling is used to configure VPLS service. BGP signalling is used to configure VPLS service.
Each entry in this table provides BGP specific Each entry in this table provides BGP specific
information for the VPlS represented by information for the VPlS represented by
vplsConfigIndex." vplsConfigIndex."
INDEX { vplsConfigIndex, vplsPwBindIndex } INDEX { vplsConfigIndex, vplsPwBindIndex }
skipping to change at page 34, line 50 skipping to change at page 36, line 4
::= { vplsBgpPwBindEntry 2 } ::= { vplsBgpPwBindEntry 2 }
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
vplsBgpCompliances vplsBgpCompliances
OBJECT IDENTIFIER ::= { vplsBgpConformance 1 } OBJECT IDENTIFIER ::= { vplsBgpConformance 1 }
vplsBgpModuleFullCompliance MODULE-COMPLIANCE vplsBgpModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
"Compliance requirement for implementations that "Compliance requirement for implementations that
provide full support for VPLS-BGP-DRAFT-01-MIB. provide full support for VPLS-BGP-DRAFT-01-MIB.
Such devices can then be monitored and configured using Such devices can then be monitored and configured using
this MIB module." this MIB module."
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
vplsBgpConfigGroup, vplsBgpConfigGroup,
vplsBgpVEGroup, vplsBgpVEGroup,
vplsBgpPwBindGroup vplsBgpPwBindGroup
} }
::= { vplsBgpCompliances 1 } ::= { vplsBgpCompliances 1 }
skipping to change at page 35, line 31 skipping to change at page 36, line 37
configured using this MIB modules." configured using this MIB modules."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
vplsBgpConfigGroup, vplsBgpConfigGroup,
vplsBgpVEGroup, vplsBgpVEGroup,
vplsBgpPwBindGroup vplsBgpPwBindGroup
} }
OBJECT vplsBgpConfigRouteDistinguisher
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT vplsBgpConfigRouteTarget
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT vplsBgpConfigVERangeSize OBJECT vplsBgpConfigVERangeSize
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsBgpVEName OBJECT vplsBgpVEName
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsBgpVEPreference OBJECT vplsBgpVEPreference
MIN-ACCESS read-only MIN-ACCESS read-only
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsBgpVERowStatus OBJECT vplsBgpVERowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { vplsBgpCompliances 2 } ::= { vplsBgpCompliances 2 }
-- Units of conformance. -- Units of conformance.
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
vplsBgpGroups vplsBgpGroups
OBJECT IDENTIFIER ::= { vplsBgpConformance 2 } OBJECT IDENTIFIER ::= { vplsBgpConformance 2 }
vplsBgpConfigGroup OBJECT-GROUP vplsBgpConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
vplsBgpConfigRouteDistinguisher,
vplsBgpConfigRouteTarget,
vplsBgpConfigVERangeSize vplsBgpConfigVERangeSize
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects supporting configuration "The group of objects supporting configuration
of L2VPN VPLS services using BGP" of L2VPN VPLS services using BGP"
::= { vplsBgpGroups 1 } ::= { vplsBgpGroups 1 }
vplsBgpVEGroup OBJECT-GROUP vplsBgpVEGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 37, line 4 skipping to change at page 37, line 41
::= { vplsBgpGroups 2 } ::= { vplsBgpGroups 2 }
vplsBgpPwBindGroup OBJECT-GROUP vplsBgpPwBindGroup OBJECT-GROUP
OBJECTS { OBJECTS {
vplsBgpPwBindLocalVEId, vplsBgpPwBindLocalVEId,
vplsBgpPwBindRemoteVEId vplsBgpPwBindRemoteVEId
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects supporting management of "The group of objects supporting management of
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
Pseudo Wires for L2VPN VPLS services using BGP" Pseudo Wires for L2VPN VPLS services using BGP"
::= { vplsBgpGroups 3 } ::= { vplsBgpGroups 3 }
END END
7. Security Considerations 7. Security Considerations
It is clear that the MIB modules described in this document in It is clear that the MIB modules described in this document in
association with the PW-STD-MIB [PW-STD-MIB] are potentially association with the PW-STD-MIB [PW-STD-MIB] are potentially
useful for monitoring of GMPLS LSRs. These MIB modules can also be useful for monitoring of GMPLS LSRs. These MIB modules can also be
used for configuration of certain objects, and anything that can be used for configuration of certain objects, and anything that can be
configured can be incorrectly configured, with potentially disastrous configured can be incorrectly configured, with potentially disastrous
results. results.
There are a number of management objects defined in these MIB modules There are a number of management objects defined in these MIB modules
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
8. IANA Considerations 8. IANA Considerations
-- (Note to RFC-Editor:) -- (Note to RFC-Editor:)
-- We request that you assign contiguous RFC numbers to the -- We request that you assign contiguous RFC numbers to the
-- IANA is requested to root MIB objects in the MIB module -- IANA is requested to root MIB objects in the MIB module
-- contained in this document under the transmission subtree. -- contained in this document under the transmission subtree.
-- --
9. References 9. References
9.1 Normative References 9.1 Normative References
[PWE3-PW-MIB] Pseudo Wire (PW) Management Information Base. [PWE3-PW-MIB] Pseudo Wire (PW) Management Information Base.
David Zelig, Thomas D. Nadeau. David Zelig, Thomas D. Nadeau.
[L2VPN-VPLS-LDP] Virtual Private LAN Services over MPLS, [RFC 4762] Virtual Private LAN Services over MPLS,
Marc Lasserre, Vach Kompella. Marc Lasserre, Vach Kompella.
[L2VPN-VPLS-BGP] Virtual Private LAN Service (VPLS) Using BGP [RFC 4761] Virtual Private LAN Service (VPLS) Using BGP
for Auto-discovery and Signaling, for Auto-discovery and Signaling,
K. Kompella, Y. Rekhter. K. Kompella, Y. Rekhter.
[SNMP-CONTEXT-MAP-MIB] SNMP Context Mapping MIB, AS, Kiran Koushik, [SNMP-CONTEXT-MAP-MIB] SNMP Context Mapping MIB, AS, Kiran Koushik,
Nadeau, T, draft-kkoushik-snmp-context-map-mib. Nadeau, T, draft-kkoushik-snmp-context-map-mib.
[RFC4188] Norseth, K., and Bell, E., "Definitions of Managed [RFC4188] Norseth, K., and Bell, E., "Definitions of Managed
Objects for Bridges", RFC 4188, Sept 2006. Objects for Bridges", RFC 4188, Sept 2006.
[RFC 4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, February 2006.
9.2. Informative References 9.2 Informative References
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of J., Rose, M., and S. Waldbusser, "Structure of
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance Statements J., Rose, M., and S. Waldbusser, "Conformance
for SMIv2", STD 58, RFC 2580, April 1999. Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002. December 2002.
10. Acknowledgement 10 Acknowledgement
We wish to thank Marcelo Mourier and Reva Bailey for their We wish to thank Marcelo Mourier and Reva Bailey for their
valuable feedback. Some portion of the work has been referenced valuable feedback. Some portion of the work has been referenced
from their original Timetra Enterprise MIB work. from their original Timetra Enterprise MIB work.
11. Authors' Addresses 11 Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
Boxborough, MA 01719 Boxborough, MA 01719
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
A S Kiran Koushik A S Kiran Koushik
Cisco Systems Inc. Cisco Systems Inc.
12515 Research Blvd, Bldg 4, 12515 Research Blvd, Bldg 4,
Austin, TX 78759 Austin, TX 78759
Email: kkoushik@cisco.com Email: kkoushik@cisco.com
Rohit Mediratta Rohit Mediratta
Alcatel Alcatel-Lucent,
Email: rohit.mediratta@alcatel.com 701 E Middlefield Rd.
Mountain View, CA 94040
Email: rohit.mediratta@alcatel-lucent.com
Praveen Muley Praveen Muley
Alcatel Alcatel-Lucent
Email: praveen.muley@alcatel.com Email: praveen.muley@alcatel-lucent.com
Reva Bailey Reva Bailey
Alcatel Alcatel-Lucent
Email: reva.bailey@alcatel.com Email: reva.bailey@alcatel-lucent.com
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
VJ Shah VJ Shah
Juniper Networks Juniper Networks
Email: vshah@juniper.net Email: vshah@juniper.net
Li Wentao Li Wentao
ZTE Inc. ZTE Inc.
CHINA CHINA
Email: li.wentao@zte.com.cn Email: li.wentao@zte.com.cn
Kong Yong Kong Yong
ZTE Inc. ZTE Inc.
CHINA CHINA
Email: kong.yong@zte.com.cn Email: kong.yong@zte.com.cn
Luo Jian Luo Jian
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
ZTE Inc. ZTE Inc.
CHINA CHINA
Email: luo.jian@zte.com.cn Email: luo.jian@zte.com.cn
Feng Jun Feng Jun
ZTE Inc. ZTE Inc.
CHINA CHINA
Email: Feng.jun99@zte.com.cn Email: Feng.jun99@zte.com.cn
Takeshi Usui Takeshi Usui
KDDI Corpration KDDI Corpration
Japan Japan
Email:ta-usui@kddi.com Email:ta-usui@kddi.com
draft-ietf-l2vpn-vpls-mib-01 L2-VPN-MIB Feb 22, 2008
12. Intellectual Property Notice 12 Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed
pertain to the implementation or use of the technology described in to pertain to the implementation or use of the technology described
this document or the extent to which any license under such rights in this document or the extent to which any license under such
might or might not be available; nor does it represent that it has rights might or might not be available; nor does it represent that
made any independent effort to identify any such rights. Information it has made any independent effort to identify any such rights.
on the procedures with respect to rights in RFC documents can be Information on the procedures with respect to rights in RFC
found in BCP 78 and BCP 79. documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use
such proprietary rights by implementers or users of this of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository
http://www.ietf.org/ipr. at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
Disclaimer of Validity Disclaimer of Validity
This document and the information contained herein are provided This document and the information contained herein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. FOR A PARTICULAR PURPOSE.
13. Full Copyright Statement draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008
13 Full Copyright Statement
Copyright (C) The IETF Trust (2008). This document is subject Copyright (C) The IETF Trust (2008). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
 End of changes. 132 change blocks. 
212 lines changed or deleted 501 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/