draft-ietf-l2vpn-vpls-mib-02.txt | draft-ietf-l2vpn-vpls-mib-03.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: Feb 2009 Cisco Systems, Inc. | Expires: Nov 2010 Cisco Systems, Inc. | |||
Rohit Mediratta (Ed.) | Rohit Mediratta (Ed.) | |||
Alcatel-Lucent | Alcatel-Lucent | |||
Virtual Private Lan Services (VPLS) Management Information Base | Virtual Private Lan Services (VPLS) Management Information Base | |||
draft-ietf-l2vpn-vpls-mib-02.txt | draft-ietf-l2vpn-vpls-mib-03.txt | |||
Status of this Memo | Status of this Memo | |||
By submitting this Internet-Draft, each author represents that any | This Internet-Draft is submitted to IETF in full conformance with the | |||
applicable patent or other IPR claims of which he or she is aware | provisions of BCP 78 and BCP 79. | |||
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. | ||||
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 | |||
other groups may also distribute working documents as | other groups may also distribute working documents as Internet- | |||
Internet-Drafts. | Drafts. | |||
Internet-Drafts are draft documents valid for a maximum of six | Internet-Drafts are draft documents valid for a maximum of six months | |||
months and may be updated, replaced, or obsoleted by other documents | and may be updated, replaced, or obsoleted by other documents at any | |||
at any time. It is inappropriate to use Internet-Drafts as | time. It is inappropriate to use Internet-Drafts as reference | |||
reference material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
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. | |||
This Internet-Draft will expire on November 07, 2010. | ||||
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 Pseudo 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 (individual submission)..........2 | 1.1 Changes from version 00 to 01 (individual submission)......2 | |||
1.2 Changes from version 01 to 02 (individual submission)..........3 | 1.2 Changes from version 01 to 02 (individual submission)......3 | |||
1.3 Changes from version 02 to 03 (individual submission)..........3 | 1.3 Changes from version 02 to 03 (individual submission)......3 | |||
1.4 Changes from version 03 to 04 (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 | draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | |||
1.6 Changes from version 01 to 02 (Standards track).................3 | ||||
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008 | ||||
2 Terminology......................................................4 | 1.5 Changes from version 00 to 01 (Standards track).............3 | |||
3 The Internet-Standard Management Framework.......................4 | 1.6 Changes from version 01 to 02 (Standards track).............3 | |||
4 VPLS MIB Module Architecture.....................................4 | 1.7 Changes from version 02 to 03 (Standards track).............3 | |||
4.1 VPLS-GENERIC-DRAFT-01-MIB Module Usage..........................5 | 2 Terminology..................................................4 | |||
4.2 VPLS-LDP-DRAFT-01-MIB Module Usage..............................5 | 3 The Internet-Standard Management Framework...................4 | |||
4.3 VPLS-BGP-DRAFT-01-MIB Module Usage..............................5 | 4 VPLS MIB Module Architecture.................................4 | |||
4.4 Relations to other MIB modules..................................5 | 4.1 VPLS-GENERIC-DRAFT-01-MIB Module Usage......................4 | |||
5 Example of the VPLS MIB modules usage............................6 | 4.2 VPLS-LDP-DRAFT-01-MIB Module Usage..........................5 | |||
6 Object definitions...............................................7 | 4.3 VPLS-BGP-DRAFT-01-MIB Module Usage..........................5 | |||
6.1 VPLS-GENERIC-DRAFT-01-MIB.......................................7 | 4.4 Relations to other MIB modules..............................5 | |||
6.2 VPLS-LDP-DRAFT-01-MIB Object definitions......................26 | 5 Example of the VPLS MIB modules usage........................6 | |||
6.3 VPLS-BGP-DRAFT-01-MIB Object definitions.......................30 | 6 Object definitions...........................................6 | |||
7. Security Considerations.........................................37 | 6.1 VPLS-GENERIC-DRAFT-01-MIB...................................7 | |||
8. IANA Considerations.............................................38 | 6.2 VPLS-LDP-DRAFT-01-MIB Object definitions..................27 | |||
9. References......................................................38 | 6.3 VPLS-BGP-DRAFT-01-MIB Object definitions...................33 | |||
9.1 Normative References...........................................38 | 7. Security Considerations.....................................41 | |||
9.2 Informative References.........................................38 | 8. IANA Considerations.........................................41 | |||
10 Acknowledgement.................................................39 | 9. References..................................................42 | |||
11 Authors' Addresses..............................................39 | 9.1 Normative References.......................................42 | |||
12 Intellectual Property Notice....................................40 | 9.2 Informative References.....................................42 | |||
13 Full Copyright Statement........................................41 | 10 Acknowledgement.............................................43 | |||
11 Authors' Addresses..........................................43 | ||||
12 Full Copyright Statement....................................45 | ||||
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 [RFC 4762] or | over a packet Switched Network (PSN) using LDP [L2VPN-VPLS-LDP] or | |||
BGP[RFC 4761] signalling. This MIB module provides generic | BGP[L2VPN-VPLS-BGP] 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 | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 | |||
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 [RFC 4762] and [RFC 4761]. | reference in [L2VPN-VPLS-LDP] and [L2VPN-VPLS-BGP]. | |||
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) | |||
skipping to change at page 3, line 42 | skipping to change at page 4, line 4 | |||
[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.] | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
1.5.1 Added the mechanism to associate VPLS MIB Mac address | 1.5.1 Added the mechanism to associate VPLS MIB Mac address | |||
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) | 1.6 Changes from version 01 to 02 (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.6.1 Added support for BGP based Autodiscovery for Ldp and Bgp | 1.6.1 Added support for BGP based Autodiscovery for Ldp and Bgp | |||
flavours of Vpls. | flavours of Vpls. | |||
1.6.2 Created separate table for RouteTarget to allow representation | 1.6.2 Created separate table for RouteTarget to allow representation | |||
of hierarchical Vpls. | of hierarchical Vpls. | |||
1.6.3 Moved configuration of Route Distinguisher and Route Target | 1.6.3 Moved configuration of Route Distinguisher and Route Target | |||
to the Vpls-MIB from the VPLS-BGP-MIB | to the Vpls-MIB from the VPLS-BGP-MIB | |||
1.6.4 Removed extra defintion of pwIndex from vplsPwBindTable | 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. | 1.6.5 Index for vplsBgpObjects were incorrect, fixed. | |||
1.7 Changes from version 02 to 03 (Standards track) | ||||
1.7.1 Added Notification for vplsLdpPwBindMacTableFull. | ||||
1.7.2 Attachment Circuit being a PW is now incorporated in the | ||||
[SNMP-CONTEXT-MAPPING-MIB] | ||||
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 33 | skipping to change at page 5, line 5 | |||
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. | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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[RFC 4762] specific parameters of the | configures VPLS-LDP[L2VPN-VPLS-LDP] 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[RFC 4761] specific parameters of the | VPLS-BGP[L2VPN-VPLS-BGP] 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 | | |||
__________ / | | | | | __________ / | | | | | |||
| | / -------- ----------------- | | | / -------- ----------------- | |||
| VPLS MIB | / ------------ | | VPLS MIB | / ------------ | |||
| |----------------------> | | | | |----------------------> | | | |||
----------- MAC addr. mapping using | BRIDGE-MIB | | ----------- MAC addr. mapping using | BRIDGE-MIB | | |||
[SNMP-CONTEXT-MAP-MIB] | | | [SNMP-CONTEXT-MAP-MIB] | | | |||
------------ | ------------ | |||
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008 | ||||
4.1 VPLS-GENERIC-DRAFT-01-MIB Module Usage | 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 27 | skipping to change at page 6, line 4 | |||
supported by the agent, and MUST be used when creating a | supported by the agent, and MUST be used when creating a | |||
manually assigned VPLS service. | manually assigned VPLS service. | |||
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 | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 | An entry in the vplsBgpAdConfigTable MUST exist if | |||
Auto-discovery has been enabled on this service. This table | Auto-discovery has been enabled on this service. This table | |||
stores the information required for auto-discovery. | stores the information required for auto-discovery. | |||
An entry in the vplsBgpRteTargetTable MUST exist if auto-discovery | An entry in the vplsBgpRteTargetTable MUST exist if auto-discovery | |||
has been configured on this service. One service can import | has been configured on this service. One service can import | |||
and export multiple Route targets. | and export multiple Route targets. | |||
skipping to change at page 6, line 4 | skipping to change at page 6, line 37 | |||
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 BGP. | for a VPLS service signalled using BGP. | |||
4.4 Relations to other MIB modules | 4.4 Relations to other MIB modules | |||
- 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 | |||
been created and all the parameters have been consistently | been created and all the parameters have been consistently | |||
configured in those tables, signaling cannot be performed | configured in those tables, signaling cannot be performed | |||
from the local node, and the ??? should report 'notPresent'. | from the local node, and the ??? should report 'notPresent'. | |||
- Statistics can be gathered from the [PWE3-PW-MIB] - TBD | - Statistics can be gathered from the [PWE3-PW-MIB] - TBD | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
5 Example of the VPLS MIB modules usage | 5 Example of the VPLS MIB modules usage | |||
In this section we provide an example of using the MIB objects | In this section we provide an example of using the MIB objects | |||
described in section 7 to set up a VPLS service over MPLS. While | described in section 7 to set up a VPLS service over MPLS. While | |||
this example is not meant to illustrate every permutation of the | this example is not meant to illustrate every permutation of the | |||
MIB, it is intended as an aid to understanding some of the key | MIB, it is intended as an aid to understanding some of the key | |||
concepts. It is meant to be read after going through the MIB | concepts. It is meant to be read after going through the MIB | |||
itself. | itself. | |||
skipping to change at page 7, line 4 | skipping to change at page 7, line 43 | |||
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. | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
[RFC2578], [RFC2579], [RFC2580], [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, IpAddress, transmission | Unsigned32, Counter32, 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 | |||
skipping to change at page 7, line 47 | skipping to change at page 8, line 37 | |||
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 | -- Vpls BGP Autodiscovery specific Textual Convention | |||
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 [RFC 4364]. | 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 [RFC 4761]" | for a VPLS service, see [L2VPN-VPLS-BGP]" | |||
REFERENCE | REFERENCE | |||
"[RFC 4364]" | "[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 [RFC 4364]." | definition of a route target, see [RFC4364]." | |||
REFERENCE | REFERENCE | |||
"[RFC 4364]" | "[RFC4364]" | |||
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008 | ||||
SYNTAX OCTET STRING(SIZE (0..256)) | SYNTAX OCTET STRING(SIZE (0..256)) | |||
VplsBgpRouteTargetType ::= TEXTUAL-CONVENTION | VplsBgpRouteTargetType ::= TEXTUAL-CONVENTION | |||
STATUS current | STATUS current | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
DESCRIPTION | DESCRIPTION | |||
"Used to define the type of a route target usage. | "Used to define the type of a route target usage. | |||
Route targets can be specified to be imported, | Route targets can be specified to be imported, | |||
exported, or both. For a complete definition of a | exported, or both. For a complete definition of a | |||
route target, see [RFC 4364]." | route target, see [RFC4364]." | |||
REFERENCE | REFERENCE | |||
"[RFC 4364]" | "[RFC4364]" | |||
SYNTAX INTEGER { import(1), export(2), both(3) } | SYNTAX INTEGER { import(1), export(2), both(3) } | |||
; | ; | |||
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 | |||
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 (2010). 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 [RFC 4762] and | for Virtual Private LAN Services as in [L2VPN-VPLS-LDP] and | |||
[RFC 4761] | [L2VPN-VPLS-BGP] | |||
This MIB module enables the use of any underlying PseudoWire | This MIB module enables the use of any underlying PseudoWire | |||
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) | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
" | " | |||
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 } | |||
-- 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. | |||
skipping to change at page 9, line 50 | skipping to change at page 11, line 4 | |||
value of vplsConfigIndex for a new entry in the | value of vplsConfigIndex for a new entry in the | |||
vplsConfigTable, the manager issues a management | vplsConfigTable, the manager issues a management | |||
protocol retrieval operation to obtain the current | protocol retrieval operation to obtain the current | |||
value of vplsConfigIndex. After each retrieval | value of vplsConfigIndex. After each retrieval | |||
operation, the agent should modify the value to | operation, the agent should modify the value to | |||
reflect the next unassigned index. After a manager | reflect the next unassigned index. After a manager | |||
retrieves a value the agent will determine through | retrieves a value the agent will determine through | |||
its local policy when this index value will be made | its local policy when this index value will be made | |||
available for reuse." | available for reuse." | |||
::= { vplsObjects 1 } | ::= { vplsObjects 1 } | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 | |||
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. | |||
skipping to change at page 10, line 46 | skipping to change at page 12, line 4 | |||
SEQUENCE { | SEQUENCE { | |||
vplsConfigIndex Unsigned32, | vplsConfigIndex Unsigned32, | |||
vplsConfigName SnmpAdminString, | vplsConfigName SnmpAdminString, | |||
vplsConfigDescr SnmpAdminString, | vplsConfigDescr SnmpAdminString, | |||
vplsConfigAdminStatus INTEGER, | vplsConfigAdminStatus INTEGER, | |||
vplsConfigMacLearning TruthValue, | vplsConfigMacLearning TruthValue, | |||
vplsConfigDiscardUnknownDest TruthValue, | vplsConfigDiscardUnknownDest TruthValue, | |||
vplsConfigMacAging TruthValue, | vplsConfigMacAging TruthValue, | |||
vplsConfigFwdFullHighWatermark Unsigned32, | vplsConfigFwdFullHighWatermark Unsigned32, | |||
vplsConfigFwdFullLowWatermark Unsigned32, | vplsConfigFwdFullLowWatermark Unsigned32, | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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) | |||
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 11, line 40 | skipping to change at page 13, line 4 | |||
::= { vplsConfigEntry 3 } | ::= { vplsConfigEntry 3 } | |||
vplsConfigAdminStatus OBJECT-TYPE | vplsConfigAdminStatus OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
up(1), | up(1), | |||
down(2), | down(2), | |||
testing(3) -- in some test mode | testing(3) -- in some test mode | |||
} | } | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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. " | |||
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 12, line 34 | skipping to change at page 14, line 5 | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"If the value of this object is 'true' | "If the value of this object is 'true' | |||
then the MAC ageing process is enabled in | then the MAC ageing process is enabled in | |||
this VPLS. If 'false', then the MAC ageing process | this VPLS. If 'false', then the MAC ageing process | |||
is disabled" | is disabled" | |||
DEFVAL { true } | DEFVAL { true } | |||
::= { vplsConfigEntry 8 } | ::= { vplsConfigEntry 8 } | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 | |||
"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." | |||
skipping to change at page 13, line 4 | skipping to change at page 14, line 32 | |||
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." | |||
skipping to change at page 13, line 28 | skipping to change at page 15, line 4 | |||
SYNTAX Unsigned32 (64..1518) | SYNTAX Unsigned32 (64..1518) | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The value of this object specifies the MTU of this | "The value of this object specifies the MTU of this | |||
vpls instance." | vpls instance." | |||
DEFVAL { 1518 } | DEFVAL { 1518 } | |||
::= { vplsConfigEntry 13 } | ::= { vplsConfigEntry 13 } | |||
vplsConfigVpnId OBJECT-TYPE | vplsConfigVpnId OBJECT-TYPE | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 | |||
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 } | |||
skipping to change at page 14, line 4 | skipping to change at page 15, line 37 | |||
::= { vplsConfigEntry 15 } | ::= { vplsConfigEntry 15 } | |||
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 | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 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 } | |||
skipping to change at page 15, line 4 | skipping to change at page 16, line 44 | |||
::= { vplsStatusEntry 1 } | ::= { vplsStatusEntry 1 } | |||
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 | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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" | |||
::= { 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 | |||
skipping to change at page 16, line 4 | skipping to change at page 17, line 51 | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The value of this object indicates | "The value of this object indicates | |||
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 1 } | ::= { 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), | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 | |||
skipping to change at page 16, line 57 | skipping to change at page 19, line 4 | |||
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 | |||
BGP Auto-discovery parameters for a given Vpls service. | BGP Auto-discovery parameters for a given Vpls service. | |||
" | " | |||
::= { vplsObjects 5 } | ::= { vplsObjects 5 } | |||
vplsBgpADConfigEntry OBJECT-TYPE | vplsBgpADConfigEntry OBJECT-TYPE | |||
SYNTAX VplsBgpADConfigEntry | SYNTAX VplsBgpADConfigEntry | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008 | ||||
DESCRIPTION | DESCRIPTION | |||
"The creation of a row in this table represents that BGP | "A row in this table represents BGP based autodiscovery | |||
based autodiscovery is in use for this instance of Vpls. | is in use for this instance of Vpls. | |||
A row in this table is indexed by vplsConfigIndex, which | A row in this table is indexed by vplsConfigIndex, which | |||
uniquely identifies a single VPLS. | 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 | None of the read-create objects can be changed when | |||
vplsBGPADConfigRowStatus is in active(1) state. Changes | vplsBGPADConfigRowStatus is in active(1) state. Changes | |||
are allowed when the vplsBGPADConfigRowStatus is in | are allowed when the vplsBGPADConfigRowStatus is in | |||
notInService(2) or notReady(3) states only. | notInService(2) or notReady(3) states only. | |||
If the operator needs to change one of the values | If the operator need to change one of the values | |||
for an active row, vplsBGPADConfigRowStatus should be | for an active row the vplsConfigRowStatus should be | |||
changed to notInService(2). The objects may then | first changed to notInService(2), the objects may | |||
be modified. Change the rowStatus back to active(1) in | be changed now, and later to active(1) in order to | |||
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 } | |||
::= { vplsBgpADConfigTable 1 } | ::= { vplsBgpADConfigTable 1 } | |||
VplsBgpADConfigEntry ::= | VplsBgpADConfigEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
vplsBgpADConfigRouteDistinguisher VplsBgpRouteDistinguisher, | vplsBgpADConfigRouteDistinguisher VplsBgpRouteDistinguisher, | |||
vplsBgpADConfigPrefix IpAddress, | vplsBgpADConfigPrefix Unsigned32, | |||
vplsBgpADConfigVplsId VplsBgpRouteDistinguisher, | vplsBgpADConfigVplsId VplsBgpRouteDistinguisher, | |||
vplsBgpADConfigRowStatus RowStatus | vplsBgpADConfigRowStatus RowStatus | |||
} | } | |||
vplsBgpADConfigRouteDistinguisher OBJECT-TYPE | vplsBgpADConfigRouteDistinguisher OBJECT-TYPE | |||
SYNTAX VplsBgpRouteDistinguisher | SYNTAX VplsBgpRouteDistinguisher | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" " The route distinguisher for this VPLS. See [RFC 4364] | " The route distinguisher for this VPLS. See [RFC4364] | |||
for a complete definition of a route distinguisher. | for a complete definition of a route distinguisher. | |||
See [RFC 4761] for more details on use of a route | for more details on use of a route distinguisher | |||
distinguisher for a VPLS service. | for a VPLS service, see [L2VPN-VPLS-BGP] | |||
" | " | |||
DEFVAL { "" } | ||||
::= { vplsBgpADConfigEntry 1 } | ::= { vplsBgpADConfigEntry 1 } | |||
vplsBgpADConfigPrefix OBJECT-TYPE | vplsBgpADConfigPrefix OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" In case of auto-discovery, the default prefix advertised | " In case of auto-discovery the default prefix advertised | |||
is the IP address of the loopback. In case the user wants | 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 | draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | |||
to override the loopback address, vplsBgpADConfigPrefix | ||||
should be set. When this value if non-zero it is used | ||||
as the advertised IP address in the NLRI. | ||||
" | " | |||
DEFVAL { 0.0.0.0 } | DEFVAL { 0 } | |||
::= { vplsBgpADConfigEntry 2 } | ::= { vplsBgpADConfigEntry 2 } | |||
vplsBgpADConfigVplsId OBJECT-TYPE | vplsBgpADConfigVplsId OBJECT-TYPE | |||
SYNTAX VplsBgpRouteDistinguisher | SYNTAX VplsBgpRouteDistinguisher | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" VplsId is a unique identifier for all VSIs belonging to | " VplsId is a unique identifier for all VSIs belonging to | |||
the same VPLS. It is advertised as an extended community | the same VPLS. It is advertised as an extended community | |||
" | " | |||
DEFVAL { "" } | ||||
::= { vplsBgpADConfigEntry 3 } | ::= { vplsBgpADConfigEntry 3 } | |||
vplsBgpADConfigRowStatus OBJECT-TYPE | vplsBgpADConfigRowStatus 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. | |||
" | " | |||
::= { vplsBgpADConfigEntry 4 } | ::= { vplsBgpADConfigEntry 4 } | |||
-- vplsBgpRteTargetTable | -- vplsBgpRteTargetTable | |||
vplsBgpRteTargetTable OBJECT-TYPE | vplsBgpRteTargetTable OBJECT-TYPE | |||
SYNTAX SEQUENCE Of VplsBgpRteTargetEntry | SYNTAX SEQUENCE Of VplsBgpRteTargetEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" This table specifies the list of Route Targets | " This table specifies the list of Route Targets | |||
imported or exported by BGP during auto-discovery of VPLS. | imported or exported by BGP during auto-discovery of VPLS. | |||
" | " | |||
::= { vplsObjects 6 } | ::= { vplsObjects 5 } | |||
vplsBgpRteTargetEntry OBJECT-TYPE | vplsBgpRteTargetEntry OBJECT-TYPE | |||
SYNTAX VplsBgpRteTargetEntry | SYNTAX VplsBgpRteTargetEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" An entry in this table specifies the value of the | "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 | draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | |||
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. | ||||
" | " | |||
INDEX { vplsConfigIndex, vplsBgpRteTargetIndex } | INDEX { vplsConfigIndex, vplsBgpRteTargetIndex } | |||
::= { vpsBgpRteTargetTable 1 } | ::= { vpsBgpRteTargetTable 1 } | |||
VplsBgpRteTargetEntry ::= | VplsBgpRteTargetEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
vplsBgpRteTargetIndex Unsigned32, | vplsBgpRteTargetIndex Unsigned32, | |||
vplsBgpRteTargetRTType VplsBgpRouteTargetType, | vplsBgpRteTargetRTType VplsBgpRouteTargetType, | |||
vplsBgpRteTargetRT VplsBgpRouteTarget, | vplsBgpRteTargetRT VplsBgpRouteTarget, | |||
vplsBgpRteTargetRTRowStatus RowStatus | vplsBgpRteTargetRTRowStatus RowStatus | |||
} | } | |||
vplsBgpRteTargetIndex OBJECT-TYPE | vplsBgpRteTargetIndex OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This index along with vplsConfigIndex,identifies one entry | "This index along with vplsConfigIndex,identifies one entry | |||
in the vplsBgpRteTargetTable. Multiple Route Targets may be | in the vplsBgpRteTargetTable. By keeping vplsConfigIndex | |||
associated with a single VPLS service. | constant and using new value of vplsBgpRteTargetIndex user | |||
can configure multiple Route Targets for the same Vpls. | ||||
" | " | |||
::= { vplsBgpADConfigEntry 1 } | ::= { vplsBgpADConfigEntry 1 } | |||
vplsBgpRteTargetRTType OBJECT-TYPE | vplsBgpRteTargetRTType OBJECT-TYPE | |||
SYNTAX VplsBgpRouteTargetType | SYNTAX VplsBgpRouteTargetType | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" Used to define the type of a route target usage. | " Used to define the type of a route target usage. | |||
Route targets can be specified to be imported, | Route targets can be specified to be imported, | |||
exported, or both. For a complete definition of a | exported, or both. For a complete definition of a | |||
route target, see [RFC 4364]." | route target, see [RFC4364]." | |||
" | " | |||
DEFVAL { "" } | ||||
::= { vplsBgpADConfigEntry 2 } | ::= { vplsBgpADConfigEntry 2 } | |||
vplsBgpRteTargetRT OBJECT-TYPE | vplsBgpRteTargetRT OBJECT-TYPE | |||
SYNTAX VplsBgpRouteTarget | SYNTAX VplsBgpRouteTarget | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" The route target associated with the VPLS service. | " The route target associated with the VPLS service. | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
For more details on use of route targets | For more details on use of route targets | |||
for a VPLS service, see [RFC 4761] | for a VPLS service, see [L2VPN-VPLS-BGP] | |||
" | " | |||
::= { vplsBgpADConfigEntry 3 } | ::= { vplsBgpADConfigEntry 3 } | |||
vplsBgpRteTargetRowStatus OBJECT-TYPE | vplsBgpRteTargetRowStatus OBJECT-TYPE | |||
SYNTAX RowStatus | SYNTAX RowStatus | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable is used to create, modify, and/or | "This variable is used to create, modify, and/or | |||
delete a row in this table. When a row in this | 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 | table is in active(1) state, no objects in that row | |||
can be modified. | can be modified | |||
" | " | |||
::= { vplsBgpADConfigEntry 4 } | ::= { vplsBgpADConfigEntry 4 } | |||
vplsStatusNotifEnable OBJECT-TYPE | vplsStatusNotifEnable OBJECT-TYPE | |||
SYNTAX TruthValue | SYNTAX TruthValue | |||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
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 | |||
skipping to change at page 20, line 42 | skipping to change at page 23, line 5 | |||
"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 8 } | ::= { vplsObjects 8 } | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
-- 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 | |||
} | } | |||
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 } | |||
skipping to change at page 21, line 35 | skipping to change at page 24, line 4 | |||
"The vplsFwdFullAlarmCleared notification is | "The vplsFwdFullAlarmCleared notification is | |||
generated when the utilization of the Forwarding | generated when the utilization of the Forwarding | |||
database is below the value specified by | database is below the value specified by | |||
vplsConfigFwdFullLowWatermark." | vplsConfigFwdFullLowWatermark." | |||
::= { vplsNotifications 3 } | ::= { vplsNotifications 3 } | |||
-- Compliance requirement for read-only implementations. | -- Compliance requirement for read-only implementations. | |||
vplsCompliances | vplsCompliances | |||
OBJECT IDENTIFIER ::= { vplsConformance 1 } | OBJECT IDENTIFIER ::= { vplsConformance 1 } | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
vplsModuleFullCompliance MODULE-COMPLIANCE | vplsModuleFullCompliance MODULE-COMPLIANCE | |||
STATUS current | STATUS current | |||
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 | |||
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 | |||
DESCRIPTION | DESCRIPTION | |||
"Write access is not required." | "Write access is not required." | |||
OBJECT vplsConfigAdminStatus | OBJECT vplsConfigAdminStatus | |||
MIN-ACCESS read-only | MIN-ACCESS read-only | |||
DESCRIPTION | DESCRIPTION | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
"Write access is not required." | "Write access is not required." | |||
OBJECT vplsConfigMacLearning | OBJECT vplsConfigMacLearning | |||
MIN-ACCESS read-only | MIN-ACCESS read-only | |||
DESCRIPTION | DESCRIPTION | |||
"Write access is not required." | "Write access is not required." | |||
OBJECT vplsConfigDiscardUnknownDest | OBJECT vplsConfigDiscardUnknownDest | |||
MIN-ACCESS read-only | MIN-ACCESS read-only | |||
DESCRIPTION | DESCRIPTION | |||
skipping to change at page 23, line 4 | skipping to change at page 25, line 34 | |||
OBJECT vplsConfigFwdFullHighWatermark | OBJECT vplsConfigFwdFullHighWatermark | |||
MIN-ACCESS read-only | MIN-ACCESS read-only | |||
DESCRIPTION | DESCRIPTION | |||
"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 23, line 26 | skipping to change at page 26, line 5 | |||
OBJECT vplsConfigServiceType | OBJECT vplsConfigServiceType | |||
MIN-ACCESS read-only | MIN-ACCESS read-only | |||
DESCRIPTION | DESCRIPTION | |||
"Write access is not required." | "Write access is not required." | |||
OBJECT vplsPwBindConfigType | OBJECT vplsPwBindConfigType | |||
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-03 L2-VPN-MIB Mar 07, 2010 | ||||
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, | |||
skipping to change at page 24, line 56 | skipping to change at page 27, line 4 | |||
vplsStatusNotifEnable, | vplsStatusNotifEnable, | |||
vplsNotificationMaxRate | vplsNotificationMaxRate | |||
} | } | |||
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 | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 | |||
"The group of notifications supporting | "The group of notifications supporting | |||
the Notifications generated for | the Notifications generated for | |||
VPLS Services" | VPLS Services" | |||
::= { vplsGroups 5 } | ::= { vplsGroups 3 } | |||
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], [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 | |||
FROM SNMPv2-CONF -- RFC2580 | FROM SNMPv2-CONF -- RFC2580 | |||
TruthValue | TruthValue | |||
FROM SNMPv2-TC -- RFC2579 | FROM SNMPv2-TC -- RFC2579 | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
vplsConfigIndex, vplsPwBindIndex | vplsConfigIndex, vplsPwBindIndex | |||
FROM VPLS-GENERIC-DRAFT-01-MIB | FROM VPLS-GENERIC-DRAFT-01-MIB; | |||
; | ||||
vplsLdpDraft01MIB MODULE-IDENTITY | vplsLdpDraft01MIB MODULE-IDENTITY | |||
LAST-UPDATED "200608301200Z" -- 20 August 2006 12:00:00 GMT | LAST-UPDATED "200608301200Z" -- 20 August 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 | |||
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 (2010). 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 | |||
LDP signalled Virtual Private LAN Services as in | LDP signalled Virtual Private LAN Services as in | |||
[RFC 4762] | [L2VPN-VPLS-LDP] | |||
This MIB module enables the use of any underlying PseudoWire | This MIB module enables the use of any underlying PseudoWire | |||
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 | |||
-- delete this note. | -- delete this note. | |||
-- Top-level components of this MIB. | -- Top-level components of this MIB. | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
-- Notifications | ||||
vplsLdpNotifications OBJECT IDENTIFIER | ||||
::= { vplsLdpDraft01MIB 0 } | ||||
-- Tables, Scalars | -- Tables, Scalars | |||
vplsLdpObjects OBJECT IDENTIFIER | vplsLdpObjects OBJECT IDENTIFIER | |||
::= { vplsLdpDraft01MIB 1 } | ::= { vplsLdpDraft01MIB 1 } | |||
-- Conformance | -- Conformance | |||
vplsLdpConformance OBJECT IDENTIFIER | vplsLdpConformance OBJECT IDENTIFIER | |||
::= { vplsLdpDraft01MIB 2 } | ::= { vplsLdpDraft01MIB 2 } | |||
vplsLdpConfigTable OBJECT-TYPE | vplsLdpConfigTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF VplsLdpConfigEntry | SYNTAX SEQUENCE OF VplsLdpConfigEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
skipping to change at page 28, line 4 | skipping to change at page 29, line 51 | |||
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 } | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
VplsLdpConfigEntry ::= | VplsLdpConfigEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
vplsLdpConfigMacAddrWithdraw TruthValue | vplsLdpConfigMacAddrWithdraw TruthValue | |||
} | } | |||
vplsLdpConfigMacAddrWithdraw OBJECT-TYPE | vplsLdpConfigMacAddrWithdraw OBJECT-TYPE | |||
SYNTAX TruthValue | SYNTAX TruthValue | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
skipping to change at page 28, line 59 | skipping to change at page 31, line 4 | |||
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 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 | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The value of this object specifies the maximum number | "The value of this object specifies the maximum number | |||
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 } | |||
-- VPLS Ldp Service Notifications | ||||
vplsLdpPwBindMacTableFull NOTIFICATION-TYPE | ||||
OBJECTS { | ||||
vplsConfigIndex, | ||||
vplsPwBindIndex | ||||
} | ||||
STATUS current | ||||
DESCRIPTION | ||||
"The vplsLdpPwBindMacTableFull notification is generated | ||||
when the number of learned MAC-Addresses increases to | ||||
the value specified in vplsLdpPwBindMacAddressLimit." | ||||
::= { vplsLdpNotifications 1 } | ||||
-- Compliance requirement for read-only implementations. | -- Compliance requirement for read-only implementations. | |||
vplsLdpCompliances | vplsLdpCompliances | |||
OBJECT IDENTIFIER ::= { vplsLdpConformance 1 } | OBJECT IDENTIFIER ::= { vplsLdpConformance 1 } | |||
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 | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
this MIB module." | this MIB module." | |||
MODULE -- this module | MODULE -- this module | |||
MANDATORY-GROUPS { | MANDATORY-GROUPS { | |||
vplsLdpGroup | vplsLdpGroup, | |||
vplsLdpNotificationGroup | ||||
} | } | |||
::= { vplsLdpCompliances 1 } | ::= { vplsLdpCompliances 1 } | |||
vplsLdpModuleReadOnlyCompliance MODULE-COMPLIANCE | vplsLdpModuleReadOnlyCompliance MODULE-COMPLIANCE | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Compliance requirement for implementations that only | "Compliance requirement for implementations that only | |||
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, | |||
vplsLdpNotificationGroup | ||||
} | } | |||
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." | |||
skipping to change at page 30, line 27 | skipping to change at page 33, line 4 | |||
-- Units of conformance. | -- Units of conformance. | |||
vplsLdpGroups | vplsLdpGroups | |||
OBJECT IDENTIFIER ::= { vplsLdpConformance 2 } | OBJECT IDENTIFIER ::= { vplsLdpConformance 2 } | |||
vplsLdpGroup OBJECT-GROUP | vplsLdpGroup OBJECT-GROUP | |||
OBJECTS { | OBJECTS { | |||
vplsLdpConfigMacAddrWithdraw, | vplsLdpConfigMacAddrWithdraw, | |||
vplsLdpPwBindMacAddressLimit | vplsLdpPwBindMacAddressLimit | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
} | } | |||
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." | |||
::= { vplsLdpGroups 1 } | ::= { vplsLdpGroups 1 } | |||
vplsLdpNotificationGroup NOTIFICATION-GROUP | ||||
NOTIFICATIONS { | ||||
vplsLdpPwBindMacTableFull | ||||
} | ||||
STATUS current | ||||
DESCRIPTION | ||||
"The group of notifications supporting | ||||
the Notifications generated for | ||||
VPLS Ldp Service" | ||||
::= { vplsLdpGroups 2 } | ||||
END | END | |||
6.3 VPLS-BGP-DRAFT-01-MIB Object definitions | 6.3 VPLS-BGP-DRAFT-01-MIB Object definitions | |||
VPLS-BGP-DRAFT-01-MIB DEFINITIONS ::= BEGIN | VPLS-BGP-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 | |||
skipping to change at page 31, line 4 | skipping to change at page 33, line 50 | |||
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 | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
" | " | |||
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) | |||
" | " | |||
DESCRIPTION | DESCRIPTION | |||
"Copyright (C) The IETF Trust (2008). The initial | "Copyright (C) The IETF Trust (2010). 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 | |||
[RFC 4761] | [L2VPN-VPLS-BGP] | |||
This MIB module enables the use of any underlying PseudoWire | This MIB module enables the use of any underlying PseudoWire | |||
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. | |||
::= { transmission XXXX } | ::= { transmission XXXX } | |||
-- 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 [RFC 4364]. | 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 [RFC 4761]" | for a VPLS service, see [L2VPN-VPLS-BGP]" | |||
REFERENCE | REFERENCE | |||
"[RFC 4364]" | "[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 | draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | |||
definition of a route target, see [RFC 4364]." | ||||
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008 | ||||
"Syntax for a route target. For a complete | ||||
definition of a route target, see [RFC4364]." | ||||
REFERENCE | REFERENCE | |||
"[RFC 4364]" | "[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. | |||
-- 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 } | |||
skipping to change at page 32, line 52 | skipping to change at page 36, line 4 | |||
configured using BGP signalling. | configured using BGP 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 | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 ::= | |||
SEQUENCE { | SEQUENCE { | |||
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008 | ||||
vplsBgpConfigVERangeSize Unsigned32 | vplsBgpConfigVERangeSize Unsigned32 | |||
} | } | |||
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 | |||
skipping to change at page 33, line 46 | skipping to change at page 37, line 4 | |||
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 } | |||
::= { vplsBgpVETable 1 } | ::= { vplsBgpVETable 1 } | |||
VplsBgpVEEntry ::= SEQUENCE { | VplsBgpVEEntry ::= SEQUENCE { | |||
vplsBgpVEId Unsigned32, | vplsBgpVEId Unsigned32, | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
vplsBgpVEName SnmpAdminString, | vplsBgpVEName SnmpAdminString, | |||
vplsBgpVEPreference Unsigned32, | vplsBgpVEPreference Unsigned32, | |||
vplsBgpVERowStatus RowStatus, | vplsBgpVERowStatus RowStatus, | |||
vplsBgpVEStorageType StorageType | vplsBgpVEStorageType StorageType | |||
} | } | |||
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 } | |||
skipping to change at page 34, line 39 | skipping to change at page 38, line 4 | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable is used to create, modify, and/or | "This variable is used to create, modify, and/or | |||
delete a row in this table. When a row in this | delete a row in this table. When a row in this | |||
table is in active(1) state, no objects in that row | table is in active(1) state, no objects in that row | |||
can be modified except vplsBgpSiteRowStatus." | can be modified except vplsBgpSiteRowStatus." | |||
::= { vplsBgpVEEntry 5 } | ::= { vplsBgpVEEntry 5 } | |||
vplsBgpVEStorageType OBJECT-TYPE | vplsBgpVEStorageType OBJECT-TYPE | |||
SYNTAX StorageType | SYNTAX StorageType | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 } | |||
::= { vplsBgpVEEntry 6 } | ::= { vplsBgpVEEntry 6 } | |||
-- VPLS BGP PW Binding Table | -- VPLS BGP PW Binding Table | |||
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 3 } | ::= { 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 | |||
skipping to change at page 35, line 33 | skipping to change at page 39, line 5 | |||
vplsConfigIndex." | vplsConfigIndex." | |||
INDEX { vplsConfigIndex, vplsPwBindIndex } | INDEX { vplsConfigIndex, vplsPwBindIndex } | |||
::= { vplsBgpPwBindTable 1 } | ::= { vplsBgpPwBindTable 1 } | |||
VplsBgpPwBindEntry ::= | VplsBgpPwBindEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
vplsBgpPwBindLocalVEId Unsigned32, | vplsBgpPwBindLocalVEId Unsigned32, | |||
vplsBgpPwBindRemoteVEId Unsigned32 | vplsBgpPwBindRemoteVEId Unsigned32 | |||
} | } | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
vplsBgpPwBindLocalVEId OBJECT-TYPE | vplsBgpPwBindLocalVEId OBJECT-TYPE | |||
SYNTAX Unsigned32 (1..65535) | SYNTAX Unsigned32 (1..65535) | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Identifies the local VE that this Pseudo Wire | "Identifies the local VE that this Pseudo Wire | |||
is associated with." | is associated with." | |||
::= { vplsBgpPwBindEntry 1 } | ::= { vplsBgpPwBindEntry 1 } | |||
vplsBgpPwBindRemoteVEId OBJECT-TYPE | vplsBgpPwBindRemoteVEId OBJECT-TYPE | |||
skipping to change at page 36, line 4 | skipping to change at page 39, line 33 | |||
::= { 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." | |||
MODULE -- this module | MODULE -- this module | |||
MANDATORY-GROUPS { | MANDATORY-GROUPS { | |||
vplsBgpConfigGroup, | vplsBgpConfigGroup, | |||
vplsBgpVEGroup, | vplsBgpVEGroup, | |||
skipping to change at page 36, line 28 | skipping to change at page 40, line 5 | |||
::= { vplsBgpCompliances 1 } | ::= { vplsBgpCompliances 1 } | |||
vplsBgpModuleReadOnlyCompliance MODULE-COMPLIANCE | vplsBgpModuleReadOnlyCompliance MODULE-COMPLIANCE | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Compliance requirement for implementations that only | "Compliance requirement for implementations that only | |||
provide read-only support for VPLS-BGP-DRAFT-01-MIB. | provide read-only support for VPLS-BGP-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." | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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." | |||
skipping to change at page 37, line 5 | skipping to change at page 40, line 49 | |||
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 { | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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 38, line 4 | skipping to change at page 42, line 4 | |||
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 | draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | |||
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. | |||
[RFC 4762] Virtual Private LAN Services over MPLS, | [L2VPN-VPLS-LDP] Virtual Private LAN Services over MPLS, | |||
Marc Lasserre, Vach Kompella. | Marc Lasserre, Vach Kompella. | |||
[RFC 4761] Virtual Private LAN Service (VPLS) Using BGP | [L2VPN-VPLS-BGP] 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, | ||||
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 | |||
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 | J., Rose, M., and S. Waldbusser, "Conformance | |||
Statements 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. | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
[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. | |||
[SNMP-CONTEXT-MAP-MIB] SNMP Context Mapping MIB, AS, Kiran Koushik, | ||||
Nadeau, T, draft-kkoushik-snmp-context-map-mib. | ||||
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. | |||
skipping to change at page 39, line 49 | skipping to change at page 44, line 4 | |||
Reva Bailey | Reva Bailey | |||
Alcatel-Lucent | Alcatel-Lucent | |||
Email: reva.bailey@alcatel-lucent.com | Email: reva.bailey@alcatel-lucent.com | |||
VJ Shah | VJ Shah | |||
Juniper Networks | Juniper Networks | |||
Email: vshah@juniper.net | Email: vshah@juniper.net | |||
Li Wentao | Li Wentao | |||
ZTE Inc. | ZTE Inc. | |||
draft-ietf-l2vpn-vpls-mib-03 L2-VPN-MIB Mar 07, 2010 | ||||
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-03 L2-VPN-MIB Mar 07, 2010 | ||||
12 Intellectual Property Notice | 12 Full Copyright Statement | |||
The IETF takes no position regarding the validity or scope of any | ||||
Intellectual Property Rights or other rights that might be claimed | ||||
to pertain to the implementation or use of the technology described | ||||
in this document or the extent to which any license under such | ||||
rights might or might not be available; nor does it represent that | ||||
it has made any independent effort to identify any such rights. | ||||
Information on the procedures with respect to rights in RFC | ||||
documents can be found in BCP 78 and BCP 79. | ||||
Copies of IPR disclosures made to the IETF Secretariat and any | ||||
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 such proprietary rights by implementers or users of this | ||||
specification can be obtained from the IETF on-line IPR repository | ||||
at http://www.ietf.org/ipr. | ||||
The IETF invites any interested party to bring to its attention any | ||||
copyrights, patents or patent applications, or other proprietary | ||||
rights that may cover technology that may be required to implement | ||||
this standard. Please address the information to the IETF at ietf- | ||||
ipr@ietf.org. | ||||
Disclaimer of Validity | ||||
This document and the information contained herein are provided | ||||
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE | ||||
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE | ||||
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL | ||||
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY | ||||
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE | ||||
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS | ||||
FOR A PARTICULAR PURPOSE. | ||||
draft-ietf-l2vpn-vpls-mib-02 L2-VPN-MIB July 14, 2008 | ||||
13 Full Copyright Statement | Copyright (c) 2010 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | ||||
Copyright (C) The IETF Trust (2008). This document is subject | This document is subject to BCP 78 and the IETF Trust's Legal | |||
to the rights, licenses and restrictions contained in BCP 78, and | Provisions Relating to IETF Documents | |||
except as set forth therein, the authors retain all their rights. | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | ||||
carefully, as they describe your rights and restrictions with respect | ||||
to this document. Code Components extracted from this document must | ||||
include Simplified BSD License text as described in Section 4.e of | ||||
the Trust Legal Provisions and are provided without warranty as | ||||
described in the Simplified BSD License. | ||||
End of changes. 151 change blocks. | ||||
289 lines changed or deleted | 257 lines changed or added | |||
This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |