draft-ietf-l2vpn-vpls-mib-06.txt   draft-ietf-l2vpn-vpls-mib-07.txt 
Internet Draft Thomas D. Nadeau (Ed.) L2VPN Working Group Thomas D. Nadeau (Ed.)
Intended status: Standards Track CA Technologies Inc. Internet Draft Juniper Networks
Expires: Apr 2012 Intended status: Standards Track
A S Kiran Koushik (Ed.) Expires: April 2013 A S Kiran Koushik (Ed.)
Cisco Systems, Inc. Cisco Systems, Inc.
Rohit Mediratta (Ed.) Rohit Mediratta (Ed.)
Alcatel-Lucent Alcatel-Lucent
Creation Date: October 27, 2011 September 29, 2012
Virtual Private Lan Services (VPLS) Management Information Base Virtual Private Lan Services (VPLS) Management Information Base
draft-ietf-l2vpn-vpls-mib-06.txt draft-ietf-l2vpn-vpls-mib-07.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
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 Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six
and may be updated, replaced, or obsoleted by other documents at any months and may be updated, replaced, or obsoleted by other documents
time. It is inappropriate to use Internet-Drafts as reference at any time. It is inappropriate to use Internet-Drafts as
material or to cite them other than as "work in progress." reference 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 Apr 27, 2012.
Abstract
This memo defines an experimental portion of the Management This Internet-Draft will expire on April 2, 2013.
Information Base for use with network management protocols in the
Internet community. In particular, it describes managed objects
for modeling of Virtual Private LAN services. It needs to be used
in conjunction with Pseudo Wire (PW) Management Information Base
[RFC5601].
Table of Contents Copyright Notice
Abstract........................................................1 Copyright (c) 2012 IETF Trust and the persons identified as the
1 Introduction................................................2 document authors. All rights reserved.
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
2 Terminology..................................................4 This document is subject to BCP 78 and the IETF Trust's Legal
3 The Internet-Standard Management Framework...................4 Provisions Relating to IETF Documents
4 VPLS MIB Module Architecture.................................4 (http://trustee.ietf.org/license-info) in effect on the date of
4.1 VPLS-GENERIC-DRAFT-01-MIB Module Usage......................4 publication of this document. Please review these documents
4.2 VPLS-LDP-DRAFT-01-MIB Module Usage..........................5 carefully, as they describe your rights and restrictions with
4.3 VPLS-BGP-DRAFT-01-MIB Module Usage..........................5 respect to this document. Code Components extracted from this
4.4 Relations to other MIB modules..............................5 document must include Simplified BSD License text as described in
5 Example of the VPLS MIB modules usage........................6 Section 4.e of the Trust Legal Provisions and are provided without
6 Object definitions...........................................6 warranty as described in the Simplified BSD License.
6.1 VPLS-GENERIC-DRAFT-01-MIB...................................7
6.2 VPLS-LDP-DRAFT-01-MIB Object definitions..................27
6.3 VPLS-BGP-DRAFT-01-MIB Object definitions...................33
7. Security Considerations.....................................41
8. IANA Considerations.........................................41
9. References..................................................42
9.1 Normative References.......................................42
9.2 Informative References.....................................42
10 Acknowledgement.............................................43
11 Authors' Addresses..........................................43
12 Full Copyright Statement....................................45
1 Introduction Abstract
This memo defines a portion of the Management Information Base This memo defines an experimental portion of the Management
(MIB) for use with network management protocols in the Internet Information Base for use with network management protocols in the
community. In particular, it defines a MIB module that can be Internet community. In particular, it describes managed objects for
used to manage VPLS(Virtual Private LAN Services for transmission modeling of Virtual Private LAN services. It needs to be used in
over a packet Switched Network (PSN) using LDP [RFC4762] or conjunction with Pseudowire (PW) Management Information Base
BGP[RFC4761] signalling. This MIB module provides generic [RFC5601].
management of VPLS services as defined by the IETF L2VPN Working
Group.
Comments should be made directly to the L2VPN mailing list at Table of Contents
l2vpn@ietf.org.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 1. Introduction...................................................3
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 2. Terminology....................................................3
"OPTIONAL" in this document are to be interpreted as described in 2.1. Conventions used in this document.........................3
[RFC2119]. 3. The Internet-Standard Management Framework.....................4
4. VPLS MIB Module Architecture...................................4
4.1. VPLS-GENERIC-MIB Module Usage.............................5
4.2. VPLS-LDP-MIB Module Usage.................................5
4.3. VPLS-BGP-MIB Module Usage.................................5
4.4. Relations to other MIB modules............................6
5. Example of the VPLS MIB modules usage..........................6
6. Object definitions.............................................7
6.1. VPLS-GENERIC-MIB..........................................7
6.2. VPLS-LDP-MIB Object definitions..........................28
6.3. VPLS-BGP-MIB Object definitions..........................34
7. Security Considerations.......................................42
8. IANA Considerations...........................................43
9. References....................................................43
9.1. Normative References.....................................43
9.2. Informative References...................................44
10. Acknowledgments..............................................45
11. Authors' Addresses...........................................45
12. Full Copyright Statement.....................................45
Conventions used in this document 1. Introduction
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL This memo defines a portion of the Management Information
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011 Base(MIB) for use with network management protocols in the Internet
community. In particular, it defines a MIB module that can be used
to manage VPLS (Virtual Private LAN Services) for transmission over
a packet Switched Network (PSN) using LDP [RFC4762] or BGP [RFC4761]
signalling. This MIB module provides generic management of VPLS
services as defined by the IETF L2VPN Working Group. Additional MIB
modules are also defined for management of LDP VPLS and BGP VPLS
services as defined by they IETF L2VPN Working Group.
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 2. Terminology
"OPTIONAL" in this document are to be interpreted as described in
RFC-2119 [RFC2119].
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011 This document adopts the definitions, acronyms and mechanisms
described in [RFC3985]. Unless otherwise stated, the mechanisms of
[RFC3985] apply and will not be re-described here.
2 Terminology 2.1. Conventions used in this document
This document adopts the definitions, acronyms and mechanisms The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
described in [RFC3985]. Unless otherwise stated, the mechanisms of "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
[RFC3985] apply and will not be re-described here. document are to be interpreted as described in RFC-2119 [RFC2119].
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
of RFC 3410 [RFC3410]. of RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. MIB objects are termed the Management Information Base or MIB. MIB objects are
generally accessed through the Simple Network Management Protocol generally accessed through the Simple Network Management Protocol
(SNMP). Objects in the MIB are defined using the mechanisms (SNMP). Objects in the MIB are defined using the mechanisms
defined in the Structure of Management Information (SMI). This defined in the Structure of Management Information (SMI). This
memo specifies a MIB module that is compliant to the SMIv2, which memo specifies a set of MIB modules that are compliant to the SMIv2,
is described in STD 58,[RFC2578], STD 58, [RFC2579] and STD 58, which 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
types of MIB modules. three MIB modules.
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011 The first is the VPLS-GENERIC-MIB module, which configures general
parameters of the VPLS service that are common to all types of VPLS
services.
The first type is the VPLS-GENERIC-DRAFT-01-MIB module, which The second is the VPLS-LDP-MIB module, which configures VPLS-LDP
configures general parameters of the VPLS service that are common [RFC4762] specific parameters of the VPLS service.
to all types of emulated services.
The second type is the VPLS-LDP-DRAFT-01-MIB module, which The third is the VPLS-BGP-MIB module, which configures VPLS-BGP
configures VPLS-LDP[RFC4762] specific parameters of the [RFC4761] specific parameters of the VPLS service.
VPLS service.
The third type is the VPLS-BGP-DRAFT-01-MIB module, which configures -------- -----------------
VPLS-BGP[RFC4761] specific parameters of the PW Mapping | | | |
VPLS service. -----> | PW-MIB |-->|PW-ENET/MPLS-MIB |
__________ / | | | |
| | / -------- -----------------
| VPLS MIB | / ------------
| |----------------------> | |
---------- MAC addr. mapping using | BRIDGE-MIB |
[SNMP-CONTEXT-MAP-MIB] | |
------------
The fourth type of modules are service-specific modules, which are Additionally service-specific modules may be defined in other
defined in other documents. documents.
-------- ----------------- 4.1. VPLS-GENERIC-MIB Module Usage
PW Mapping | | | |
-----> | PW-MIB |-->|PW-ENET/MPLS-MIB |
__________ / | | | |
| | / -------- -----------------
| VPLS MIB | / ------------
| |----------------------> | |
----------- MAC addr. mapping using | BRIDGE-MIB |
[SNMP-CONTEXT-MAP-MIB] | |
------------
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 signaled 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
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-06 L2-VPN-MIB Oct 27, 2011 pseudowires (defined in [RFC5601]). Each pseudowire may
pseudo wires (defined in [RFC5601]). 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.
The agent than creates the rows in the (locally supported) The agent then creates the rows in the (locally supported)
performance tables and reverse mapping tables in performance tables and reverse mapping tables in
VPLS-GENERIC-DRAFT-01-MIB module. VPLS-GENERIC-MIB module.
4.2 VPLS-LDP-DRAFT-01-MIB Module Usage 4.2. VPLS-LDP-MIB Module Usage
An entry in the vplsLdpConfigTable MUST be created by the agent An entry in the vplsLdpConfigTable MUST be created by the agent
for a VPLS service signalled using LDP. for a VPLS service signaled using LDP.
4.3 VPLS-BGP-DRAFT-01-MIB Module Usage 4.3. VPLS-BGP-MIB Module Usage
An entry in the vplsBgpConfigTable MUST be created by the agent An entry in the vplsBgpConfigTable MUST be created by the agent
for a VPLS service signalled using BGP. for a VPLS service signaled 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 the pwTable in
the [RFC5601] the [RFC5601]
- The association of MAC addresses to VPLS entries is possible - The association of MAC addresses to VPLS entries is possible
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 vplsConfigRowStatus should report
'notReady'.
- Statistics can be gathered from the [RFC5601] - TBD - Statistics can be gathered from the Pseudowire performance
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011 tables in [RFC5601]
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.
In this example a vpls service (VPLS-A) is setup using Ldp for
signaling the pseudowire. The binding between the Vpls service and
the pseudowire is reflected in the VplsPwBindTable.
The pseudowire configuration is defined in RFC 5601.
In the VPLS-GENERIC-DRAFT-01-MIB module: In the VPLS-GENERIC-MIB module:
In vplsConfigTable: In vplsConfigTable:
{ {
vplsConfigIndex 10, vplsConfigIndex 10,
vplsConfigName "VPLS-A" vplsConfigName "VPLS-A"
vplsConfigAdminStatus 1(up), vplsConfigAdminStatus 1(up),
vplsConfigMacLearning 1(true), vplsConfigMacLearning 1(true),
vplsConfigDiscardUnknownDest 2(false), vplsConfigDiscardUnknownDest 2(false),
vplsConfigMacAging 1(true), vplsConfigMacAging 1(true),
vplsConfigVpnId "100:10" vplsConfigVpnId "100:10"
vplsConfigRowStatus 1(active) vplsConfigRowStatus 1(active)
} }
In vplsStatusTable: In vplsStatusTable:
{ {
vplsStatusOperStatus 1(up), vplsStatusOperStatus 1(up),
} }
In the VPLS-LDP-DRAFT-01-MIB module: In VplsPwBindTable :
{
vplsPwBindConfigType manual,
vplsPwBindType spoke,
vplsPwBindRowStatus 1(active),
vplsPwBindStorageType volatile
}
In the VPLS-LDP-MIB module:
In vplsLdpConfigTable: In vplsLdpConfigTable:
{ {
vplsLdpConfigMacAddrWithdraw 1(true), vplsLdpConfigMacAddrWithdraw 1(true),
} }
In vplsLdpPwBindTable: In vplsLdpPwBindTable:
{ {
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-MIB
This MIB module makes references to the following documents. This MIB module makes references to the following documents.
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
[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-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, Counter32, 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
PwIndexType pwIndex
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 Auto-Discovery 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 [RFC4364]. definition of a route distinguisher, see [RFC4364].
For more details on use of a route distinguisher For more details on use of a route distinguisher
for a VPLS service, see [RFC4761]" for a VPLS service, see [RFC4761]"
REFERENCE REFERENCE
"[RFC4364]" "[RFC4364]"
SYNTAX OCTET STRING(SIZE (0..256)) SYNTAX OCTET STRING(SIZE (0..256))
VplsBgpRouteTarget ::= TEXTUAL-CONVENTION VplsBgpRouteTarget ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Syntax for a route target. For a complete "Syntax for a route target. For a complete
definition of a route target, see [RFC4364]." definition of a route target, see [RFC4364]."
REFERENCE REFERENCE
"[RFC4364]" "[RFC4364]"
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-06 L2-VPN-MIB Oct 27, 2011
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 [RFC4364]." route target, see [RFC4364]."
REFERENCE REFERENCE
"[RFC4364]" "[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 "201208261200Z" -- 26 Aug 2012 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@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 (2011). The initial "Copyright (C) The IETF Trust (2012). 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 [RFC4762] and for Virtual Private LAN Services as define in [RFC4762] and
[RFC4761] [RFC4761]
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
"201209291200Z" -- 29 September 2012 12:00:00 GMT
DESCRIPTION
1) Changed the OID for vplsBgpRteTargetTable from vplsObjects.6 to
vplsObjects.5
2) Index to VplsPwBindTable is now pwIndex, not vplsPwBindIndex.
3) vplsConfigMtu increased to upto 9192
4) Default value for vplsConfigStorageType changed to nonvolatile.
5) vplsConfigServiceType should be a property of each PW. Deleting
this object and adjusting the corresponding object indexes.
"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-MIB
2) Created the vplsStatusTable to store status information. 2) Created the vplsStatusTable to store status information.
3) 3)
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
" "
REVISION REVISION
"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 assigned value, and
-- delete this note. -- delete this note.
-- Top-level components of this MIB. -- Top-level components of this MIB.
-- Notifications -- Notifications
vplsNotifications OBJECT IDENTIFIER vplsNotifications OBJECT IDENTIFIER
::= { vplsGenericDraft01MIB 0 } ::= { vplsGenericDraft01MIB 0 }
-- Tables, Scalars -- Tables, Scalars
vplsObjects OBJECT IDENTIFIER vplsObjects OBJECT IDENTIFIER
::= { vplsGenericDraft01MIB 1 } ::= { vplsGenericDraft01MIB 1 }
skipping to change at page 11, line 4 skipping to change at page 11, line 19
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-06 L2-VPN-MIB Oct 27, 2011
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).
" "
::= { vplsObjects 2 } ::= { vplsObjects 2 }
skipping to change at page 11, line 26 skipping to change at page 11, line 40
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.
A row is created by the operator or by the agent if a A row is created by the operator or by the agent if a
VPLS service is created by non-SNMP application or VPLS service is created by a non-SNMP application or
due to autodiscovery process. due to the Auto-Discovery process.
None of the read-create objects values can be None of the read-create objects values can be
changed when vplsConfigRowStatus is in the active(1) changed when vplsConfigRowStatus is in the active(1)
state. Changes are allowed when the vplsConfigRowStatus state. Changes are allowed when the vplsConfigRowStatus
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 needs 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 then be changed, and finally the vplsConfigRowStatus
re-initiate the signaling process with the new should be changed to active(1) in order to re-initiate
values in effect. the signaling process with the new values in effect.
" "
INDEX { vplsConfigIndex } INDEX { vplsConfigIndex }
::= { vplsConfigTable 1 } ::= { vplsConfigTable 1 }
VplsConfigEntry ::= VplsConfigEntry ::=
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-06 L2-VPN-MIB Oct 27, 2011 vplsConfigRowStatus RowStatus,
vplsConfigMtu Unsigned32,
vplsConfigRowStatus RowStatus, vplsConfigVpnId VPNIdOrZero,
vplsConfigMtu Unsigned32, vplsConfigStorageType StorageType
vplsConfigVpnId VPNIdOrZero,
vplsConfigServiceType INTEGER,
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."
::= { vplsConfigEntry 1 } ::= { vplsConfigEntry 1 }
vplsConfigName OBJECT-TYPE vplsConfigName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 13, line 4 skipping to change at page 13, line 22
::= { 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-06 L2-VPN-MIB Oct 27, 2011
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 enabled then this
service is able to utilize the pseudo wire to service is able to utilize pseudowires 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
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 14, line 5 skipping to change at page 14, line 23
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-06 L2-VPN-MIB Oct 27, 2011
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 14, line 45 skipping to change at page 15, line 14
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For creating, modifying, and deleting this row. "For creating, modifying, and deleting this row.
None of the read-create objects in the None of the read-create objects in the
conceptual rows may be changed when this conceptual rows may be changed when this
object is in the active(1) state." object is in the active(1) state."
::= { vplsConfigEntry 12 } ::= { vplsConfigEntry 12 }
vplsConfigMtu OBJECT-TYPE vplsConfigMtu OBJECT-TYPE
SYNTAX Unsigned32 (64..1518) SYNTAX Unsigned32 (64..9192)
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. This can be used to limit the MTU to a
value lower than the MTU supported by the associated
Pseudowires"
DEFVAL { 1518 } DEFVAL { 1518 }
::= { vplsConfigEntry 13 } ::= { vplsConfigEntry 13 }
vplsConfigVpnId OBJECT-TYPE vplsConfigVpnId OBJECT-TYPE
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
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."
::= { vplsConfigEntry 14 } ::= { vplsConfigEntry 14 }
vplsConfigServiceType OBJECT-TYPE
SYNTAX INTEGER {
vlan (1),
ethernet (2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object specifies the type of
service emulated by this vpls instance."
DEFVAL { vlan }
::= { 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 { nonVolatile }
::= { vplsConfigEntry 16 } ::= { vplsConfigEntry 15 }
-- 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-06 L2-VPN-MIB Oct 27, 2011
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 16, line 42 skipping to change at page 16, line 48
DESCRIPTION DESCRIPTION
"The current operational state of this VPLS Service." "The current operational state of this VPLS Service."
::= { 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." (pseudowires) present in this VPLS instance."
::= { vplsStatusEntry 2 } ::= { vplsStatusEntry 2 }
-- 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 pseudowires.
A service can have more than one pseudowire
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011 association. Pseudowires are defined in
Wires. A service can have more than one Pseudo
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
"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 pseudowires
defined in the pwTable. Each index is unique defined in the pwTable. Each index is unique
in describing an entry in this table. However in describing an entry in this table. However
both indexes are required to define the one both indexes are required to define the one
to many association of service to to many association of service to
pseudowire." pseudowire."
INDEX { vplsConfigIndex, vplsPwBindIndex } INDEX { vplsConfigIndex, pwIndex }
::= { vplsPwBindTable 1 } ::= { vplsPwBindTable 1 }
VplsPwBindEntry ::= VplsPwBindEntry ::=
SEQUENCE { SEQUENCE {
vplsPwBindConfigType INTEGER, vplsPwBindConfigType INTEGER,
vplsPwBindType INTEGER, vplsPwBindType INTEGER,
vplsPwBindRowStatus RowStatus, vplsPwBindRowStatus RowStatus,
vplsPwBindStorageType StorageType vplsPwBindStorageType StorageType
} }
vplsPwBindConfigType OBJECT-TYPE vplsPwBindConfigType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
manual (1), manual (1),
autodiscovery (2) autodiscovery (2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object indicates "The value of this object indicates
whether the Pseudo Wire binding was created whether the Pseudo Wire binding was created
manually or via autodiscovery. manually or via Auto-Discovery.
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 }
vplsPwBindType OBJECT-TYPE vplsPwBindType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
mesh (1), mesh (1),
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
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 pseudowire binding is of
type mesh or spoke. type mesh or spoke.
The value of this object must be The value of this object must be
specifed when the row is created and cannot specified when the row is created and cannot
be changed while the row status is active(1)" be changed while the row status is active(1)"
::= { vplsPwBindEntry 2 } ::= { vplsPwBindEntry 2 }
vplsPwBindRowStatus OBJECT-TYPE vplsPwBindRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For creating, modifying, and deleting this row. "For creating, modifying, and deleting this row.
None of the read-create objects in the None of the read-create objects in the
skipping to change at page 18, line 42 skipping to change at page 19, line 4
vplsPwBindStorageType OBJECT-TYPE vplsPwBindStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this row." "This variable indicates the storage type for this row."
DEFVAL { volatile } DEFVAL { volatile }
::= { vplsPwBindEntry 4 } ::= { vplsPwBindEntry 4 }
-- vplsBgpADConfigTable -- vplsBgpADConfigTable
vplsBgpADConfigTable OBJECT-TYPE vplsBgpADConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsBgpADEntry SYNTAX SEQUENCE OF VplsBgpADEntry
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-06 L2-VPN-MIB Oct 27, 2011
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row in this table represents BGP based autodiscovery "A row in this table indicates that BGP based Auto-
is in use for this instance of Vpls. Discovery 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.
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 need to change one of the values If the operator needs 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 then be changed, and finally the vplsConfigRowStatus
should be changed to active(1) in order to
re-initiate the signaling process with the new re-initiate the signaling process with the new
values in effect. values in effect.
" "
INDEX { vplsConfigIndex } INDEX { vplsConfigIndex }
::= { vplsBgpADConfigTable 1 } ::= { vplsBgpADConfigTable 1 }
VplsBgpADConfigEntry ::= VplsBgpADConfigEntry ::=
SEQUENCE { SEQUENCE {
vplsBgpADConfigRouteDistinguisher VplsBgpRouteDistinguisher, vplsBgpADConfigRouteDistinguisher VplsBgpRouteDistinguisher,
vplsBgpADConfigPrefix Unsigned32, 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 [RFC4364] " The route distinguisher for this VPLS. See [RFC4364]
for a complete definition of a route distinguisher. for a complete definition of a route distinguisher.
for more details on use of a route distinguisher for more details on use of a route distinguisher
for a VPLS service, see [RFC4761] for a VPLS service, see [RFC4761]. When not configured, the
value is derived from the lower 6 bytes of
vplsBgpADConfigVplsId.
" "
::= { 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
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
to override the loopback address, vplsBgpADConfigPrefix to override the loopback address, vplsBgpADConfigPrefix
should be set. When this value if non-zero it is used should be set. When this value is non-zero this value is
as the advertised IP address in the NLRI. used along with vplsBgpADConfigRouteDistinguisher in the
NLRI, see [RFC 6074]
" "
DEFVAL { 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.
" "
::= { 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 5 } ::= { vplsObjects 6 }
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
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011 of vplsBgpRteTargetType a Route Target might be exported or
imported or both. Every VPLS which
Route Target being used by BGP. Depending on the value uses auto-discovery for finding peer nodes can import and
of vplsBgpRteTargetType an RT might be exported or export multiple Route Targets. This representation allows
imported or both. Every VPLS which support for hierarchical VPLS.
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
in the vplsBgpRteTargetTable. By keeping vplsConfigIndex entry in the vplsBgpRteTargetTable. By keeping
constant and using new value of vplsBgpRteTargetIndex user vplsConfigIndex constant and using new value of
can configure multiple Route Targets for the same Vpls. vplsBgpRteTargetIndex users 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,
skipping to change at page 22, line 4 skipping to change at page 22, line 24
route target, see [RFC4364]." route target, see [RFC4364]."
" "
::= { 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-06 L2-VPN-MIB Oct 27, 2011
For more details on use of route targets For more details on use of route targets
for a VPLS service, see [RFC4761] for a VPLS service, see [RFC4761]
" "
::= { 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
skipping to change at page 23, line 4 skipping to change at page 23, line 24
DESCRIPTION DESCRIPTION
"This object indicates the maximum number of "This object indicates the maximum number of
notifications issued per second. If events occur notifications issued per second. If events occur
more rapidly, the implementation may simply fail to more rapidly, the implementation may simply fail to
emit these notifications during that period, or may emit these notifications during that period, or may
queue them until an appropriate time. A value of 0 queue them until an appropriate time. A value of 0
means no throttling is applied and events may be means no throttling is applied and events may be
notified at the rate at which they occur." notified at the rate at which they occur."
DEFVAL { 0 } DEFVAL { 0 }
::= { vplsObjects 8 } ::= { vplsObjects 8 }
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
-- 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
skipping to change at page 23, line 50 skipping to change at page 24, line 21
vplsConfigFwdFullLowWatermark vplsConfigFwdFullLowWatermark
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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. -- Conformance Section
vplsCompliances vplsCompliances
OBJECT IDENTIFIER ::= { vplsConformance 1 } OBJECT IDENTIFIER ::= { vplsConformance 1 }
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011 -- Compliance requirement for fully compliant implementations
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-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,
vplsNotificationGroup vplsNotificationGroup
} }
::= { vplsCompliances 1 } ::= { vplsCompliances 1 }
-- Compliance requirement for read-only implementations.
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-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 {
vplsGroup, vplsGroup,
vplsPwBindGroup, vplsPwBindGroup,
vplsNotificationGroup vplsNotificationGroup
} }
skipping to change at page 25, line 5 skipping to change at page 25, line 28
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-06 L2-VPN-MIB Oct 27, 2011
"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 26, line 5 skipping to change at page 26, line 30
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-06 L2-VPN-MIB Oct 27, 2011
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."
skipping to change at page 26, line 38 skipping to change at page 27, line 15
vplsConfigAdminStatus, vplsConfigAdminStatus,
vplsConfigMacLearning, vplsConfigMacLearning,
vplsConfigDiscardUnknownDest, vplsConfigDiscardUnknownDest,
vplsConfigMacAging, vplsConfigMacAging,
vplsConfigVpnId, vplsConfigVpnId,
vplsConfigFwdFullHighWatermark, vplsConfigFwdFullHighWatermark,
vplsConfigFwdFullLowWatermark, vplsConfigFwdFullLowWatermark,
vplsConfigRowStatus, vplsConfigRowStatus,
vplsConfigIndexNext, vplsConfigIndexNext,
vplsConfigMtu, vplsConfigMtu,
vplsConfigServiceType,
vplsConfigStorageType, vplsConfigStorageType,
vplsStatusOperStatus, vplsStatusOperStatus,
vplsStatusPeerCount, vplsStatusPeerCount,
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
skipping to change at page 27, line 4 skipping to change at page 27, line 28
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-06 L2-VPN-MIB Oct 27, 2011
OBJECTS { OBJECTS {
vplsPwBindConfigType, vplsPwBindConfigType,
vplsPwBindType, vplsPwBindType,
vplsPwBindRowStatus, vplsPwBindRowStatus,
vplsPwBindStorageType vplsPwBindStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects supporting "The group of objects supporting
management of management of
skipping to change at page 27, line 34 skipping to change at page 28, line 9
} }
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 3 } ::= { vplsGroups 3 }
END END
6.2 VPLS-LDP-DRAFT-01-MIB Object definitions 6.2. VPLS-LDP-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-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-06 L2-VPN-MIB Oct 27, 2011 pwIndex
FROM PW-TC-STD-MIB
vplsConfigIndex, vplsPwBindIndex vplsConfigIndex
FROM VPLS-GENERIC-DRAFT-01-MIB; FROM VPLS-GENERIC-MIB;
vplsLdpDraft01MIB MODULE-IDENTITY vplsLdpDraft01MIB MODULE-IDENTITY
LAST-UPDATED "200608301200Z" -- 20 August 2006 12:00:00 GMT LAST-UPDATED "201208201200Z" -- 20 August 2012 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 Rohit Mediratta
Email: tnadeau@cisco.com Email: Rohit.mediratta@alcatel-lucent.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 (2011). The initial "Copyright (C) The IETF Trust (2012). 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 signaled Virtual Private LAN Services as in
[RFC4762] [RFC4762]
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 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 assigned 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-06 L2-VPN-MIB Oct 27, 2011
-- Notifications -- Notifications
vplsLdpNotifications OBJECT IDENTIFIER vplsLdpNotifications OBJECT IDENTIFIER
::= { vplsLdpDraft01MIB 0 } ::= { 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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies information for configuring "This table specifies information for configuring
and monitoring LDP specific parameters for and monitoring LDP specific parameters for
Virtual Private Lan Services(VPLS)." Virtual Private Lan Services (VPLS)."
::= { vplsLdpObjects 1 } ::= { vplsLdpObjects 1 }
vplsLdpConfigEntry OBJECT-TYPE vplsLdpConfigEntry OBJECT-TYPE
SYNTAX VplsLdpConfigEntry SYNTAX VplsLdpConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row in this table represents LDP specific information "A row in this table represents LDP specific information
for Virtual Private Lan Service(VPLS) in a packet network. for Virtual Private Lan Services (VPLS) in a packet network.
It is indexed by vplsConfigIndex, which uniquely It is indexed by vplsConfigIndex, which uniquely
identifies a single VPLS. identifies a single VPLS.
A row is automatically created when a VPLS service is A row is automatically created when a VPLS service is
configured using LDP signalling. configured using LDP signaling.
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 needs 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 then be changed, and finally the vplsConfigRowStatus
re-initiate the signaling process with the new should be changed to active(1) in order to
values in effect. re-initiate the signaling process with the new
" values in effect.
"
INDEX { vplsConfigIndex } INDEX { vplsConfigIndex }
::= { vplsLdpConfigTable 1 } ::= { vplsLdpConfigTable 1 }
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
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
"This object specifies if MAC address withdrawal "This object specifies if MAC address withdrawal
is enabled in this service. If this object is true then is enabled in this service. If this object is true then
Mac address withdrawl Learning is enabled. If false, MAC address withdrawal is enabled. If false,
then Mac Learning is disabled." then MAC address withdrawal is disabled."
DEFVAL { true } DEFVAL { true }
::= { vplsLdpConfigEntry 1 } ::= { vplsLdpConfigEntry 1 }
-- VPLS LDP PW Binding Table -- VPLS LDP PW Binding Table
vplsLdpPwBindTable OBJECT-TYPE vplsLdpPwBindTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsLdpPwBindEntry SYNTAX SEQUENCE OF VplsLdpPwBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides LDP specific information for "This table provides LDP specific information for
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 pseudowires. A service can have more
than one Pseudo Wire association. Pseudo Wires are than one pseudowire association. Pseudowires are
defined in the pwTable." defined in the pwTable."
::= { vplsLdpObjects 2 } ::= { vplsLdpObjects 2 }
vplsLdpPwBindEntry OBJECT-TYPE vplsLdpPwBindEntry OBJECT-TYPE
SYNTAX VplsLdpPwBindEntry SYNTAX VplsLdpPwBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
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 pseudowires
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 signaling 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-06 L2-VPN-MIB Oct 27, 2011
vplsConfigIndex." vplsConfigIndex."
INDEX { vplsConfigIndex, vplsPwBindIndex } INDEX { vplsConfigIndex, pwIndex }
::= { 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 -- VPLS LDP Service Notifications
vplsLdpPwBindMacTableFull NOTIFICATION-TYPE vplsLdpPwBindMacTableFull NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vplsConfigIndex, vplsConfigIndex,
vplsPwBindIndex pwIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vplsLdpPwBindMacTableFull notification is generated "The vplsLdpPwBindMacTableFull notification is generated
when the number of learned MAC-Addresses increases to when the number of learned MAC-Addresses increases to
the value specified in vplsLdpPwBindMacAddressLimit." the value specified in vplsLdpPwBindMacAddressLimit."
::= { vplsLdpNotifications 1 } ::= { vplsLdpNotifications 1 }
-- Compliance requirement for read-only implementations. -- Conformance Section
vplsLdpCompliances vplsLdpCompliances
OBJECT IDENTIFIER ::= { vplsLdpConformance 1 } OBJECT IDENTIFIER ::= { vplsLdpConformance 1 }
-- Compliance requirement for fully compliant implementations
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-MIB.
Such devices can then be monitored and configured using Such devices can then be monitored and configured using
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
this MIB module." this MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
vplsLdpGroup, vplsLdpGroup,
vplsLdpNotificationGroup vplsLdpNotificationGroup
} }
::= { vplsLdpCompliances 1 } ::= { vplsLdpCompliances 1 }
-- Compliance requirement for read-only implementations.
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-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 vplsLdpNotificationGroup
} }
skipping to change at page 33, line 4 skipping to change at page 33, line 41
-- 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-06 L2-VPN-MIB Oct 27, 2011
} }
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 vplsLdpNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
vplsLdpPwBindMacTableFull vplsLdpPwBindMacTableFull
skipping to change at page 33, line 27 skipping to change at page 34, line 15
} }
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 Ldp Service" VPLS Ldp Service"
::= { vplsLdpGroups 2 } ::= { vplsLdpGroups 2 }
END END
6.3 VPLS-BGP-DRAFT-01-MIB Object definitions 6.3. VPLS-BGP-MIB Object definitions
VPLS-BGP-DRAFT-01-MIB DEFINITIONS ::= BEGIN VPLS-BGP-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
RowStatus, StorageType, TEXTUAL-CONVENTION RowStatus, StorageType, TEXTUAL-CONVENTION
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC2579
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC3411 FROM SNMP-FRAMEWORK-MIB -- RFC3411
vplsConfigIndex, vplsPwBindIndex vplsConfigIndex
FROM VPLS-GENERIC-DRAFT-01-MIB FROM VPLS-GENERIC-MIB
; ;
vplsBgpDraft01MIB MODULE-IDENTITY vplsBgpDraft01MIB MODULE-IDENTITY
LAST-UPDATED "200612061200Z" -- 06 Dec 2006 12:00:00 GMT LAST-UPDATED "201208201200Z" -- 20 Aug 2012 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-06 L2-VPN-MIB Oct 27, 2011
" "
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 (2011). The initial "Copyright (C) The IETF Trust (2012). 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 signaled Virtual Private LAN Services as in
[RFC4761] [RFC4761]
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 "201208201200Z" -- 20 Aug 2012 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 assigned value, and
-- delete this note. -- delete this note.
-- VPLS BGP specific Textual Conventions. -- VPLS BGP specific Textual Conventions.
VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Syntax for a route distinguisher. For a complete "Syntax for a route distinguisher. For a complete
definition of a route distinguisher, see [RFC4364]. definition of a route distinguisher, see [RFC4364].
For more details on use of a route distinguisher For more details on use of a route distinguisher
for a VPLS service, see [RFC4761]" for a VPLS service, see [RFC4761]"
REFERENCE REFERENCE
"[RFC4364]" "[RFC4364]"
SYNTAX OCTET STRING(SIZE (0..256)) SYNTAX OCTET STRING(SIZE (0..256))
VplsBgpRouteTarget ::= TEXTUAL-CONVENTION VplsBgpRouteTarget ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
"Syntax for a route target. For a complete "Syntax for a route target. For a complete
definition of a route target, see [RFC4364]." definition of a route target, see [RFC4364]."
REFERENCE REFERENCE
"[RFC4364]" "[RFC4364]"
SYNTAX OCTET STRING(SIZE (0..256)) SYNTAX OCTET STRING(SIZE (0..256))
-- Top-level components of this MIB. -- Top-level components of this MIB.
-- Tables, Scalars -- Tables, Scalars
vplsBgpObjects OBJECT IDENTIFIER vplsBgpObjects OBJECT IDENTIFIER
::= { vplsBgpDraft01MIB 1 } ::= { vplsBgpDraft01MIB 1 }
-- Conformance -- Conformance
vplsBgpConformance OBJECT IDENTIFIER vplsBgpConformance OBJECT IDENTIFIER
::= { vplsBgpDraft01MIB 2 } ::= { vplsBgpDraft01MIB 2 }
-- Vpls Bgp Config Table -- Vpls Bgp Config Table
vplsBgpConfigTable OBJECT-TYPE vplsBgpConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsBgpConfigEntry SYNTAX SEQUENCE OF VplsBgpConfigEntry
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 BGP specific parameters for and monitoring BGP specific parameters for
Virtual Private Lan Services(VPLS)." Virtual Private LAN Services (VPLS)."
::= { vplsBgpObjects 1 } ::= { vplsBgpObjects 1 }
vplsBgpConfigEntry OBJECT-TYPE vplsBgpConfigEntry OBJECT-TYPE
SYNTAX VplsBgpConfigEntry SYNTAX VplsBgpConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row in this table represents BGP specific information "A row in this table represents BGP specific information
for Virtual Private Lan Service(VPLS) in a packet network. for Virtual Private LAN Services (VPLS) in a packet network.
It is indexed by vplsConfigIndex, which uniquely It is indexed by vplsConfigIndex, which uniquely
identifies a single instance of a VPLS service. identifies a single instance of a VPLS service.
A row is automatically created when a VPLS service is
configured using BGP signalling.
None of the read-create objects values can be
changed when vplsRowStatus is in the active(1)
state. Changes are allowed when the vplsRowStatus
is in notInService(2) or notReady(3) states only.
If the operator need to change one of the values
for an active row the vplsConfigRowStatus should be
first changed to notInService(2), the objects may
be changed now, and later to active(1) in order to
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
re-initiate the signaling process with the new A row is automatically created when a VPLS service is
values in effect. configured using BGP signaling.
None of the read-create objects values can be
changed when vplsRowStatus is in the active(1)
state. Changes are allowed when the vplsRowStatus
is in notInService(2) or notReady(3) states only.
If the operator needs to change one of the values
for an active row the vplsConfigRowStatus should be
first changed to notInService(2), the objects may
then be changed, and finally the vplsConfigRowSTatus
should be changed to active(1) in order to
re-initiate the signaling process with the new
values in effect.
" "
INDEX { vplsConfigIndex } INDEX { vplsConfigIndex }
::= { vplsBgpConfigTable 1 } ::= { vplsBgpConfigTable 1 }
VplsBgpConfigEntry ::= VplsBgpConfigEntry ::=
SEQUENCE { SEQUENCE {
vplsBgpConfigVERangeSize Unsigned32 vplsBgpConfigVERangeSize Unsigned32
} }
vplsBgpConfigVERangeSize OBJECT-TYPE vplsBgpConfigVERangeSize OBJECT-TYPE
skipping to change at page 37, line 4 skipping to change at page 37, line 47
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-06 L2-VPN-MIB Oct 27, 2011
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 }
skipping to change at page 37, line 27 skipping to change at page 38, line 21
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 }
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 associated with
this VE Id." this VE Id."
DEFVAL { "" } DEFVAL { "" }
::= { vplsBgpVEEntry 2 } ::= { vplsBgpVEEntry 2 }
vplsBgpVEPreference OBJECT-TYPE vplsBgpVEPreference OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the preference of the VE Id on this PE "Specifies the preference of the VE Id on this PE
skipping to change at page 38, line 4 skipping to change at page 38, line 49
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-06 L2-VPN-MIB Oct 27, 2011
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 pseudowires. A service can have more
than one Pseudo Wire association. Pseudo Wires are than one pseudowire association. Pseudowires are
defined in the pwTable." defined in the pwTable."
::= { vplsBgpObjects 3 } ::= { vplsBgpObjects 3 }
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 Pseudowires
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
BGP signalling is used to configure VPLS service. BGP signaling is used to configure VPLS service.
Each entry in this table provides BGP specific Each entry in this table provides BGP specific
information for the VPlS represented by information for the VPlS represented by
vplsConfigIndex." vplsConfigIndex."
INDEX { vplsConfigIndex, vplsPwBindIndex } INDEX { vplsConfigIndex, pwIndex }
::= { vplsBgpPwBindTable 1 } ::= { vplsBgpPwBindTable 1 }
VplsBgpPwBindEntry ::= VplsBgpPwBindEntry ::=
SEQUENCE { SEQUENCE {
vplsBgpPwBindLocalVEId Unsigned32, vplsBgpPwBindLocalVEId Unsigned32,
vplsBgpPwBindRemoteVEId Unsigned32 vplsBgpPwBindRemoteVEId Unsigned32
} }
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
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 pseudowire
is associated with." is associated with."
::= { vplsBgpPwBindEntry 1 } ::= { vplsBgpPwBindEntry 1 }
vplsBgpPwBindRemoteVEId OBJECT-TYPE vplsBgpPwBindRemoteVEId 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 remote VE that this Pseudo Wire "Identifies the remote VE that this pseudowire
is associated with." is associated with."
::= { vplsBgpPwBindEntry 2 } ::= { vplsBgpPwBindEntry 2 }
-- Compliance requirement for read-only implementations. -- Conformance Section
-- Compliance requirement for fully compliant implementations
vplsBgpCompliances vplsBgpCompliances
OBJECT IDENTIFIER ::= { vplsBgpConformance 1 } OBJECT IDENTIFIER ::= { vplsBgpConformance 1 }
vplsBgpModuleFullCompliance MODULE-COMPLIANCE vplsBgpModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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-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,
vplsBgpPwBindGroup vplsBgpPwBindGroup
} }
::= { vplsBgpCompliances 1 } ::= { vplsBgpCompliances 1 }
-- Compliance requirement for read-only implementations.
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-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-06 L2-VPN-MIB Oct 27, 2011
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 41, line 4 skipping to change at page 41, line 47
::= { vplsBgpCompliances 2 } ::= { vplsBgpCompliances 2 }
-- Units of conformance. -- Units of conformance.
vplsBgpGroups vplsBgpGroups
OBJECT IDENTIFIER ::= { vplsBgpConformance 2 } OBJECT IDENTIFIER ::= { vplsBgpConformance 2 }
vplsBgpConfigGroup OBJECT-GROUP vplsBgpConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
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 41, line 45 skipping to change at page 42, line 39
"The group of objects supporting management of "The group of objects supporting management of
Pseudo Wires for L2VPN VPLS services using BGP" Pseudo Wires for L2VPN VPLS services using BGP"
::= { vplsBgpGroups 3 } ::= { vplsBgpGroups 3 }
END END
7. Security Considerations 7. Security Considerations
It is clear that the MIB modules described in this document in It is clear that the MIB modules described in this document in
association with the PW-STD-MIB [RFC5601] are potentially association with the PW-STD-MIB [RFC5601] are potentially
useful for monitoring of GMPLS LSRs. These MIB modules can also be useful for monitoring of VPLS capable LERs. These MIB modules can
used for configuration of certain objects, and anything that can be also be used for configuration of certain objects, and anything that
configured can be incorrectly configured, with potentially disastrous can be configured can be incorrectly configured, with potentially
results. disastrous results.
There are a number of management objects defined in these MIB modules There are a number of management objects defined in these MIB
with a MAX-ACCESS clause of read-write and/or read-create. Such modules with a MAX-ACCESS clause of read-write and/or read-create.
objects may be considered sensitive or vulnerable in some network Such objects may be considered sensitive or vulnerable in some
environments. The support for SET operations in a non-secure network 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-06 L2-VPN-MIB Oct 27, 2011 network operation.
network operations. These are the tables and objects and their
sensitivity/vulnerability:
8. IANA Considerations 8. IANA Considerations
-- (Note to RFC-Editor:) -- (Note to RFC-Editor:)
-- IANA is requested to root the MIB modules
-- 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
[RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, March 1997. Requirement Levels", RFC 2119, BCP 14, March 1997.
[RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network
Management Protocol (SNMP) Applications", STD 62, RFC Management Protocol (SNMP) Applications", STD 62, RFC
3413, December 2002. 3413, December 2002.
skipping to change at page 42, line 49 skipping to change at page 43, line 44
RFC 3813, June 2004 RFC 3813, June 2004
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, Feb 2005. Addresses", RFC 4001, Feb 2005.
[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.
[RFC4265] Schliesser, B. and T. Nadeau, "Definition of Textual [RFC4265] Schliesser, B. and T. Nadeau, "Definition of Textual
Conventions for Virtual Private Network (VPN) Management", Conventions for Virtual Private Network (VPN)
RFC 4265, November 2005. Management", RFC 4265, November 2005.
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, February 2006. Networks (VPNs)", RFC 4364, February 2006.
[RFC4761] Kompella, K. and Y. Rekhter, "Virtual Private LAN Service [RFC4761] Kompella, K. and Y. Rekhter, "Virtual Private LAN Service
(VPLS) Using BGP for Auto-Discovery and Signaling",RFC (VPLS) Using BGP for Auto-Discovery and Signaling",RFC
4761, January 2007. 4761, January 2007.
[RFC4762] Lasserre, M. and Kompella, V. (Editors), "Virtual Private [RFC4762] Lasserre, M. and Kompella, V. (Editors), "Virtual Private
LAN Service (VPLS) Using Label Distribution Protocol (LDP) LAN Service (VPLS) Using Label Distribution Protocol (LDP)
Signaling", RFC 4762, January 2007. Signaling", RFC 4762, January 2007.
[RFC5601] T. Nadeau, Ed., D. Zelig, Ed., "Pseudowire (PW) [RFC5601] T. Nadeau, Ed., D. Zelig, Ed., "Pseudowire (PW)
Management Information Base (MIB)", RFC 5601, July 2009. Management Information Base (MIB)", RFC 5601, July 2009.
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,
skipping to change at page 44, line 5 skipping to change at page 45, line 5
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002. December 2002.
[RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to-
Edge (PWE3) Architecture", RFC 3985, March 2005. Edge (PWE3) Architecture", RFC 3985, March 2005.
[SNMP-CONTEXT-MAP-MIB] SNMP Context Mapping MIB, AS, Kiran Koushik, [SNMP-CONTEXT-MAP-MIB] SNMP Context Mapping MIB, AS, Kiran Koushik,
Nadeau, T, draft-kkoushik-snmp-context-map-mib. Nadeau, T, draft-kkoushik-snmp-context-map-mib.
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011 10. Acknowledgments
10 Acknowledgement
We wish to thank Marcelo Mourier and Reva Bailey for their
valuable feedback. Some portion of the work has been referenced
from their original Timetra Enterprise MIB work.
11 Authors' Addresses
Thomas D. Nadeau
CA Technologies Inc.
Email: tnadeau@lucidvision.com
A S Kiran Koushik
Cisco Systems Inc.
12515 Research Blvd, Bldg 4,
Austin, TX 78759
Email: kkoushik@cisco.com
Rohit Mediratta
Alcatel-Lucent,
701 E Middlefield Rd.
Mountain View, CA 94040
Email: rohit.mediratta@alcatel-lucent.com
Praveen Muley
Alcatel-Lucent
Email: praveen.muley@alcatel-lucent.com
Reva Bailey
Alcatel-Lucent
Email: reva.bailey@alcatel-lucent.com
VJ Shah We wish to thank Marcelo Mourier and Reva Bailey for their
Juniper Networks valuable feedback. Some portion of the work has been referenced
Email: vshah@juniper.net from their original Timetra Enterprise MIB work.
draft-ietf-l2vpn-vpls-mib-06 L2-VPN-MIB Oct 27, 2011
Li Wentao We wish to thank Praveen Muley, VJ Shah, Li Wentao, Kong Yong, Luo
ZTE Inc. Jian, Feng Jun, Takeshi Usui for their feedback.
CHINA
Email: li.wentao@zte.com.cn
Kong Yong 11. Authors' Addresses
ZTE Inc.
CHINA
Email: kong.yong@zte.com.cn
Luo Jian Thomas D. Nadeau
ZTE Inc. Juniper Networks
CHINA Email: tnadeau@juniper.net
Email: luo.jian@zte.com.cn
Feng Jun A S Kiran Koushik
ZTE Inc. Cisco Systems Inc.
CHINA 12515 Research Blvd, Bldg 4,
Email: Feng.jun99@zte.com.cn Austin, TX 78759
Email: kkoushik@cisco.com
Takeshi Usui Rohit Mediratta
KDDI Corpration Alcatel-Lucent,
Japan 701 E Middlefield Rd.
Email:ta-usui@kddi.com Mountain View, CA 94040
Email: rohit.mediratta@alcatel-lucent.com
12 Full Copyright Statement 12. Full Copyright Statement
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with
to this document. Code Components extracted from this document must respect to this document. Code Components extracted from this
include Simplified BSD License text as described in Section 4.e of document must include Simplified BSD License text as described in
the Trust Legal Provisions and are provided without warranty as Section 4.e of the Trust Legal Provisions and are provided without
described in the Simplified BSD License. warranty as described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) Without obtaining an adequate license from the person(s)
controlling the copyright in such materials, this document may not controlling the copyright in such materials, this document may not
be modified outside the IETF Standards Process, and derivative be modified outside the IETF Standards Process, and derivative
works of it may not be created outside the IETF Standards Process, works of it may not be created outside the IETF Standards Process,
 End of changes. 212 change blocks. 
502 lines changed or deleted 405 lines changed or added

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