draft-ietf-l2vpn-vpls-mib-14.txt   draft-ietf-l2vpn-vpls-mib-15.txt 
L2VPN Working Group Thomas D. Nadeau (Ed.) L2VPN Working Group Thomas D. Nadeau (Ed.)
Internet Draft Lucid Vision Internet Draft Lucid Vision
Intended status: Standards Track Intended status: Standards Track
Expires: July 2014 A S Kiran Koushik (Ed.) Expires: Aug 2014 Agrahara S Kiran Koushik (Ed.)
Cisco Systems, Inc. Cisco Systems, Inc.
Rohit Mediratta (Ed.) Rohit Mediratta (Ed.)
Alcatel-Lucent Alcatel-Lucent
January 30, 2014 Feburary 19, 2014
Virtual Private Lan Services (VPLS) Management Information Base Virtual Private Lan Services (VPLS) Management Information Base
draft-ietf-l2vpn-vpls-mib-14.txt draft-ietf-l2vpn-vpls-mib-15.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted 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 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
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference 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
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
This Internet-Draft will expire on July 30, 2014. This Internet-Draft will expire on July 30, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 3, line 4 skipping to change at page 3, line 4
4. VPLS MIB Module Architecture...................................4 4. VPLS MIB Module Architecture...................................4
4.1. VPLS-GENERIC-MIB Module Usage.............................5 4.1. VPLS-GENERIC-MIB Module Usage.............................5
4.2. VPLS-LDP-MIB Module Usage.................................5 4.2. VPLS-LDP-MIB Module Usage.................................5
4.3. VPLS-BGP-MIB Module Usage.................................5 4.3. VPLS-BGP-MIB Module Usage.................................5
4.4. Relations to other MIB modules............................6 4.4. Relations to other MIB modules............................6
5. Example of the VPLS MIB modules usage..........................6 5. Example of the VPLS MIB modules usage..........................6
6. Object definitions.............................................7 6. Object definitions.............................................7
6.1. VPLS-GENERIC-MIB..........................................7 6.1. VPLS-GENERIC-MIB..........................................7
6.2. VPLS-LDP-MIB Object definitions..........................28 6.2. VPLS-LDP-MIB Object definitions..........................28
6.3. VPLS-BGP-MIB Object definitions..........................34 6.3. VPLS-BGP-MIB Object definitions..........................34
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
7. Security Considerations.......................................42 7. Security Considerations.......................................42
8. IANA Considerations...........................................43 8. IANA Considerations...........................................43
9. References....................................................43 9. References....................................................43
9.1. Normative References.....................................43 9.1. Normative References.....................................43
9.2. Informative References...................................44 9.2. Informative References...................................44
10. Acknowledgments..............................................45 10. Acknowledgments..............................................45
11. Authors' Addresses...........................................45 11. Authors' Addresses...........................................45
12. Full Copyright Statement.....................................45 12. Full Copyright Statement.....................................45
1. Introduction 1. Introduction
This memo defines a portion of the Management Information This memo defines a portion of the Management Information
Base (MIB) for use with network management protocols in the Internet Base (MIB) for use with network management protocols in the Internet
community. In particular, it defines a MIB module that can be used community. In particular, it defines three MIB modules that can be
to manage VPLS (Virtual Private LAN Services) for transmission over used to manage VPLS (Virtual Private LAN Services) for transmission
a packet Switched Network (PSN) using LDP [RFC4762] or BGP [RFC4761] over a packet Switched Network (PSN) using LDP [RFC4762] or
signaling. This MIB module provides generic management of VPLS BGP [RFC4761] signaling. This MIB module provides generic management
services as defined by the IETF L2VPN Working Group. Additional MIB of VPLS services as defined by the IETF L2VPN Working Group.
modules are also defined for management of LDP VPLS and BGP VPLS Additional MIB modules are also defined for management of LDP VPLS
services as defined by the IETF L2VPN Working Group. and BGP VPLS services as defined by the IETF L2VPN Working Group.
2. Terminology 2. Terminology
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms and mechanisms
described in [RFC3985]. Unless otherwise stated, the mechanisms of described in [RFC3985]. Unless otherwise stated, the mechanisms of
[RFC3985] apply and will not be re-described here. [RFC3985] apply and will not be re-described here.
2.1. Conventions used in this document 2.1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 4, line 4 skipping to change at page 4, line 4
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 set of MIB modules that are compliant to the SMIv2, memo specifies a set of MIB modules that are compliant to the SMIv2,
which is described in STD 58 [RFC2578][RFC2579][RFC2580]. which is described in STD 58 [RFC2578][RFC2579][RFC2580].
4. VPLS MIB Module Architecture 4. VPLS MIB Module Architecture
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
The MIB structure for defining a VPLS service is composed from The MIB structure for defining a VPLS service is composed from
three MIB modules. three MIB modules.
The first is the VPLS-GENERIC-MIB module, which configures general The first is the VPLS-GENERIC-MIB module, which configures
parameters of the VPLS service that are common to all types of VPLS general parameters of the VPLS service that are common to all
services. types of VPLS services.
The second is the VPLS-LDP-MIB module, which configures VPLS-LDP The second is the VPLS-LDP-MIB module, which configures
[RFC4762] specific parameters of the VPLS service. VPLS-LDP [RFC4762] specific parameters of the VPLS service.
The third is the VPLS-BGP-MIB module, which configures VPLS-BGP The third is the VPLS-BGP-MIB module, which configures
[RFC4761] specific parameters of the VPLS service. VPLS-BGP [RFC4761] specific parameters of the VPLS service.
The arrows in Figure A indicate whether we can map data from
one module into another.
-------- ----------------- -------- -----------------
PW Mapping | | | | PW Mapping | | | |
-----> | PW-MIB |-->|PW-ENET/MPLS-MIB | -----> | PW-MIB |-->|PW-ENET/MPLS-MIB |
__________ / | | | | __________ / | | | |
| | / -------- ----------------- | | / -------- -----------------
| VPLS MIB | / ------------ | VPLS MIB | / ------------
| |----------------------> | | | |----------------------> | |
---------- MAC addr. mapping using | BRIDGE-MIB | ---------- MAC addr. mapping using | BRIDGE-MIB |
[SNMP-CONTEXT-MAP-MIB] | | [SNMP-CONTEXT-MAP-MIB] | |
skipping to change at page 5, line 4 skipping to change at page 5, line 4
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) An NMS creates a row in the vplsConfigTable using SNMP Set 1) An NMS creates a row in the vplsConfigTable using SNMP Set
requests which causes the node to create and start a new VPLS requests which causes the node to create and start a new VPLS
service. The agent MUST support the creation of VPLS service. The agent MUST support the creation of VPLS
services in this way. services in this way.
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
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
configuration that is done through non-SNMP applications. configuration that is done through non-SNMP applications.
This mode is OPTIONAL. This mode is OPTIONAL.
At least one entry in the vplsPwBindTable MUST exist for At least one entry in the vplsPwBindTable MUST exist for
each VPLS service. each VPLS service.
This binding table links one VPLS service with one or many This binding table links one VPLS service with one or many
pseudowires (defined in [RFC5601]). Each pseudowire may pseudowires (defined in [RFC5601]). Each pseudowire may
be used as a spoke or as part of a mesh based on the parameters be used as a spoke or as part of a mesh based on the parameters
defined in this table. defined in this table.
skipping to change at page 6, line 4 skipping to change at page 6, line 4
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
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
from the local node, and the vplsConfigRowStatus should report from the local node, and the vplsConfigRowStatus should report
'notReady'. 'notReady'.
- Statistics can be gathered from the Pseudowire performance - Statistics can be gathered from the Pseudowire performance
tables in [RFC5601] 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 In this example a VPLS service (VPLS-A) is setup using LDP for
signaling the pseudowire. The binding between the VPLS service and signaling the pseudowire. The binding between the VPLS service
the pseudowire is reflected in the VplsPwBindTable. and the pseudowire is reflected in the VplsPwBindTable.
The pseudowire configuration is defined in RFC 5601. The pseudowire configuration is defined in RFC 5601.
In the VPLS-GENERIC-MIB module: In the VPLS-GENERIC-MIB module:
Row in vplsConfigTable: Row in vplsConfigTable:
{ {
vplsConfigIndex 10, vplsConfigIndex 10,
vplsConfigName "VPLS-A" vplsConfigName "VPLS-A"
vplsConfigAdminStatus 1(up), vplsConfigAdminStatus 1(up),
vplsConfigMacLearning 1(true), vplsConfigMacLearning 1(true),
skipping to change at page 7, line 4 skipping to change at page 7, line 4
vplsStatusPeerCount 1 vplsStatusPeerCount 1
} }
Row in VplsPwBindTable : Row in VplsPwBindTable :
{ {
vplsPwBindConfigType manual, vplsPwBindConfigType manual,
vplsPwBindType spoke, vplsPwBindType spoke,
vplsPwBindRowStatus 1(active), vplsPwBindRowStatus 1(active),
vplsPwBindStorageType volatile vplsPwBindStorageType volatile
} }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
In the VPLS-LDP-MIB module: In the VPLS-LDP-MIB module:
Row in vplsLdpConfigTable: Row in vplsLdpConfigTable:
{ {
vplsLdpConfigMacAddrWithdraw 1(true), vplsLdpConfigMacAddrWithdraw 1(true),
} }
Row in vplsLdpPwBindTable: Row in vplsLdpPwBindTable:
skipping to change at page 8, line 5 skipping to change at page 8, line 5
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC3411 FROM SNMP-FRAMEWORK-MIB -- RFC3411
pwIndex pwIndex
FROM PW-STD-MIB FROM PW-STD-MIB
VPNIdOrZero VPNIdOrZero
FROM VPN-TC-STD-MIB -- RFC4265 FROM VPN-TC-STD-MIB -- RFC4265
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
; ;
vplsGenericDraft01MIB MODULE-IDENTITY vplsGenericDraft01MIB MODULE-IDENTITY
-- RFC Editor: Please replace vplsGenericDraft01MIB with -- RFC Editor: Please replace vplsGenericDraft01MIB with
-- vplsGenericMIB throughout the MIB and remove -- vplsGenericMIB throughout the MIB and remove
-- this note. -- this note.
LAST-UPDATED "201401301200Z" -- 30 Jan 2014 12:00:00 GMT LAST-UPDATED "201401301200Z" -- 30 Jan 2014 12:00:00 GMT
ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN)
Working Group" Working Group"
skipping to change at page 8, line 34 skipping to change at page 8, line 34
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2014). The initial "Copyright (C) The IETF Trust (2014). 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 define 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
"201401301200Z" -- 30 Jan 2014 12:00:00 GMT "201401301200Z" -- 30 Jan 2014 12:00:00 GMT
VPLS Management Information Base Feb, 2014
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 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."
REVISION
VPLS Management Information Base Jan, 2014
"200608301200Z" -- 30 August 2006 12:00:00 GMT
DESCRIPTION
"Changes from previous version:
1) Moved LDP Specific information to VPLS-LDP-MIB
2) Created the vplsStatusTable to store status information.
"
REVISION
"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 AAA }
-- RFC Editor: please replace XXXX with IANA assigned value, and -- RFC Editor: please replace AAA with IANA assigned value, and
-- delete this note. -- delete this note.
-- VPLS BGP Auto-Discovery 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 that matches the
definition of a route distinguisher, see [RFC4364]. definition in RFC4364. For a complete
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 that matches the
definition of a route target, see [RFC4364]." definition in RFC4364. For a complete
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
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
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
"[RFC4364]" "RFC4364"
SYNTAX INTEGER { import(1), export(2), both(3) } SYNTAX INTEGER { import(1), export(2), both(3) }
-- 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 4
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 }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
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 via SNMP or by the agent if a A row is created via SNMP or by the agent if a
VPLS service is created by a non-SNMP application or VPLS service is created by a non-SNMP application or
due to the Auto-Discovery process. due to the Auto-Discovery process.
All of the read-create objects values except All of the read-create objects values except
vplsConfigSignalingType can be changed when vplsConfigSignalingType can be changed when
vplsConfigRowStatus is in the active(1) vplsConfigRowStatus is in the active(1)
state. Changes for vplsConfigSignalingType are only allowed state. Changes for vplsConfigSignalingType are only
when the vplsConfigRowStatus is in notInService(2) or allowed when the vplsConfigRowStatus is in
notReady(3) states. notInService(2) or notReady(3) states.
" "
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,
skipping to change at page 12, line 4 skipping to change at page 12, line 4
vplsConfigRowStatus RowStatus, vplsConfigRowStatus RowStatus,
vplsConfigMtu Unsigned32, vplsConfigMtu Unsigned32,
vplsConfigVpnId VPNIdOrZero, vplsConfigVpnId VPNIdOrZero,
vplsConfigStorageType StorageType, vplsConfigStorageType StorageType,
vplsConfigSignalingType INTEGER vplsConfigSignalingType INTEGER
} }
vplsConfigIndex OBJECT-TYPE vplsConfigIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
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 4
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 enabled then this VPLS service is changed to enabled then this
service is able to utilize pseudowires 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 }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
::= { 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
skipping to change at page 13, line 53 skipping to change at page 13, line 53
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. The value of this object must
be higher than vplsConfigFwdFullLowWatermark."
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
DEFVAL { 95 } DEFVAL { 95 }
::= { vplsConfigEntry 10 } ::= { vplsConfigEntry 10 }
vplsConfigFwdFullLowWatermark OBJECT-TYPE vplsConfigFwdFullLowWatermark OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..99)
UNITS "percentage" UNITS "percentage"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the utilization of the "This object specifies the utilization of the
forwarding database for this VPLS instance forwarding database for this VPLS instance
at which the vplsFwdFullAlarmCleared at which the vplsFwdFullAlarmCleared
notification will be sent." notification will be sent. The value of this
object must be less than
vplsConfigFwdFullHighWatermark"
DEFVAL { 90 } DEFVAL { 90 }
::= { vplsConfigEntry 11 } ::= { vplsConfigEntry 11 }
vplsConfigRowStatus OBJECT-TYPE vplsConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For creating, modifying, and deleting this row. "For creating, modifying, and deleting this row.
skipping to change at page 15, line 4 skipping to change at page 15, line 4
SYNTAX Unsigned32 (64..9192) 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. This can be used to limit the MTU to a vpls instance. This can be used to limit the MTU to a
value lower than the MTU supported by the associated value lower than the MTU supported by the associated
Pseudowires" Pseudowires"
DEFVAL { 1518 } DEFVAL { 1518 }
::= { vplsConfigEntry 13 } ::= { vplsConfigEntry 13 }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
vplsConfigVpnId OBJECT-TYPE vplsConfigVpnId OBJECT-TYPE
SYNTAX VPNIdOrZero SYNTAX VPNIdOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
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 }
skipping to change at page 16, line 4 skipping to change at page 16, line 4
indicates a static configuration of PW labels." indicates a static configuration of PW labels."
DEFVAL { none } DEFVAL { none }
::= { vplsConfigEntry 16 } ::= { vplsConfigEntry 16 }
-- 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
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
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
skipping to change at page 17, line 4 skipping to change at page 17, line 4
::= { 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
(pseudowires) present in this VPLS instance." (pseudowires) present in this VPLS instance."
::= { vplsStatusEntry 2 } ::= { vplsStatusEntry 2 }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
-- 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 pseudowires. VPLS service and the corresponding pseudowires.
skipping to change at page 18, line 4 skipping to change at page 18, line 4
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 {
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
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
via SNMP/Console or via Auto-Discovery. via SNMP/Console or via Auto-Discovery.
skipping to change at page 19, line 5 skipping to change at page 19, line 5
All other objects in this row must be set to valid All other objects in this row must be set to valid
values before this object can be set to active(1). values before this object can be set to active(1).
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.
If autodiscovered entries are deleted they would If autodiscovered entries are deleted they would
likely re-appear in the next autodiscovery interval." likely re-appear in the next autodiscovery interval."
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
::= { vplsPwBindEntry 3 } ::= { vplsPwBindEntry 3 }
vplsPwBindStorageType OBJECT-TYPE vplsPwBindStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this row." "This variable indicates the storage type for this row."
DEFVAL { volatile } DEFVAL { volatile }
skipping to change at page 20, line 4 skipping to change at page 20, line 4
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.
Entries in this table may be created or deleted Entries in this table may be created or deleted
through SNMP, as side-effects of console or other through SNMP, as side-effects of console or other
non-SNMP management commands, or upon learning via non-SNMP management commands, or upon learning via
autodiscovery. autodiscovery.
All of the read-create objects can be changed when All of the read-create objects can be changed when
vplsBGPADConfigRowStatus is in active(1) state." vplsBGPADConfigRowStatus is in active(1) state."
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
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,
vplsBgpADConfigStorageType StorageType vplsBgpADConfigStorageType StorageType
} }
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]. When not configured, the for a VPLS service, see RFC4761. When not configured, the
value is derived from the lower 6 bytes of value is derived from the lower 6 bytes of
vplsBgpADConfigVplsId. 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
to override the loopback address, vplsBgpADConfigPrefix to override the loopback address, vplsBgpADConfigPrefix
should be set. When this value is non-zero this value is should be set. When this value is non-zero this value is
used along with vplsBgpADConfigRouteDistinguisher in the used along with vplsBgpADConfigRouteDistinguisher in the
NLRI, see [RFC6074] NLRI, see RFC6074
" "
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
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
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
skipping to change at page 21, line 42 skipping to change at page 21, line 42
::= { vplsBgpADConfigEntry 5 } ::= { vplsBgpADConfigEntry 5 }
-- vplsBgpRteTargetTable -- vplsBgpRteTargetTable
vplsBgpRteTargetTable OBJECT-TYPE vplsBgpRteTargetTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsBgpRteTargetEntry SYNTAX SEQUENCE OF VplsBgpRteTargetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This table specifies the list of Route Targets " This table specifies the list of Route Targets
imported or exported by BGP during auto-discovery of VPLS. imported or exported by BGP during
auto-discovery of VPLS.
" "
::= { vplsObjects 6 } ::= { vplsObjects 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 Route Target being used by BGP. Depending on the value
of vplsBgpRteTargetType a Route Target might be exported or of vplsBgpRteTargetType a Route Target might be
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
imported or both. Every VPLS which exported or imported or both. Every VPLS which
uses auto-discovery for finding peer nodes can import and uses auto-discovery for finding peer nodes can
export multiple Route Targets. This representation allows import and export multiple Route Targets. This
support for hierarchical VPLS. representation allows support for hierarchical VPLS.
Entries in this table may be created or deleted Entries in this table may be created or deleted
through SNMP, as side-effects of console or other through SNMP, as side-effects of console or other
non-SNMP management commands, or upon learning via non-SNMP management commands, or upon learning via
autodiscovery. autodiscovery.
It is optional for the agent to allow entries to be It is optional for the agent to allow entries to be
created that point to non-existent entries in created that point to non-existent entries in
vplsConfigTable." vplsConfigTable."
INDEX { vplsConfigIndex, vplsBgpRteTargetIndex } INDEX { vplsConfigIndex, vplsBgpRteTargetIndex }
skipping to change at page 22, line 39 skipping to change at page 22, line 39
} }
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 "This index along with vplsConfigIndex, identifies one
entry in the vplsBgpRteTargetTable. By keeping entry in the vplsBgpRteTargetTable. By keeping
vplsConfigIndex constant and using new value of vplsConfigIndex constant and using new value of
vplsBgpRteTargetIndex users can configure multiple Route vplsBgpRteTargetIndex users can configure multiple
Targets for the same VPLS. Route Targets for the same VPLS.
" "
::= { vplsBgpRteTargetEntry 1 } ::= { vplsBgpRteTargetEntry 1 }
vplsBgpRteTargetRTType OBJECT-TYPE vplsBgpRteTargetRTType OBJECT-TYPE
SYNTAX VplsBgpRouteTargetType SYNTAX VplsBgpRouteTargetType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Used to define the type of a route target usage. " Used to define the type of a route target usage.
Route targets can be specified to be imported, Route targets can be specified to be imported,
exported, or both. For a complete definition of a exported, or both. For a complete definition of a
route target, see [RFC4364]." route target, see RFC4364."
::= { vplsBgpRteTargetEntry 2 } ::= { vplsBgpRteTargetEntry 2 }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
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.
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.
" "
::= { vplsBgpRteTargetEntry 3 } ::= { vplsBgpRteTargetEntry 3 }
vplsBgpRteTargetRowStatus OBJECT-TYPE vplsBgpRteTargetRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. delete a row in this table.
skipping to change at page 24, line 4 skipping to change at page 24, line 4
::= { vplsBgpRteTargetEntry 5 } ::= { vplsBgpRteTargetEntry 5 }
vplsStatusNotifEnable OBJECT-TYPE vplsStatusNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is set to true(1), then it enables "If this object is set to true(1), then it enables
the emission of vplsStatusChanged the emission of vplsStatusChanged
notification, otherwise this notification is not notification, otherwise this notification is not
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
emitted." emitted."
REFERENCE REFERENCE
"See also [RFC3413] for explanation that "See also RFC3413 for explanation that
notifications are under the ultimate control of the notifications are under the ultimate control of the
MIB module in this document." MIB module in this document."
DEFVAL { false } DEFVAL { false }
::= { vplsObjects 7 } ::= { vplsObjects 7 }
vplsNotificationMaxRate OBJECT-TYPE vplsNotificationMaxRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 24, line 42 skipping to change at page 24, line 42
vplsConfigVpnId, vplsConfigVpnId,
vplsConfigAdminStatus, vplsConfigAdminStatus,
vplsStatusOperStatus vplsStatusOperStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vplsStatusChanged notification is generated "The vplsStatusChanged notification is generated
when there is a change in the administrative or when there is a change in the administrative or
operating status of a VPLS service. operating status of a VPLS service.
The object instances included in the notification are The object instances included in the notification
the ones associated with the VPLS service whose are the ones associated with the VPLS service
status has changed." whose status has changed."
::= { vplsNotifications 1 } ::= { vplsNotifications 1 }
vplsFwdFullAlarmRaised NOTIFICATION-TYPE vplsFwdFullAlarmRaised NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vplsConfigVpnId, vplsConfigVpnId,
vplsConfigFwdFullHighWatermark, vplsConfigFwdFullHighWatermark,
vplsConfigFwdFullLowWatermark vplsConfigFwdFullLowWatermark
} }
STATUS current STATUS current
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
DESCRIPTION DESCRIPTION
"The vplsFwdFullAlarmRaised notification is "The vplsFwdFullAlarmRaised notification is
generated when the utilization of the Forwarding generated when the utilization of the Forwarding
database is above the value specified by database is above the value specified by
vplsConfigFwdFullHighWatermark. vplsConfigFwdFullHighWatermark.
The object instances included in the notification are The object instances included in the notification
the ones associated with the VPLS service which has are the ones associated with the VPLS service
exceeded the threshold." which has exceeded the threshold."
::= { vplsNotifications 2 } ::= { vplsNotifications 2 }
vplsFwdFullAlarmCleared NOTIFICATION-TYPE vplsFwdFullAlarmCleared NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vplsConfigVpnId, vplsConfigVpnId,
vplsConfigFwdFullHighWatermark, vplsConfigFwdFullHighWatermark,
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.
The object instances included in the notification are The object instances included in the notification
the ones associated with the VPLS service which has are the ones associated with the VPLS service
fallen below the threshold." which has fallen below the threshold."
::= { vplsNotifications 3 } ::= { vplsNotifications 3 }
-- Conformance Section -- Conformance Section
vplsCompliances vplsCompliances
OBJECT IDENTIFIER ::= { vplsConformance 1 } OBJECT IDENTIFIER ::= { vplsConformance 1 }
-- Compliance requirement for fully compliant implementations -- Compliance requirement for fully compliant implementations
vplsModuleFullCompliance MODULE-COMPLIANCE vplsModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
skipping to change at page 26, line 4 skipping to change at page 26, line 4
provide full support for VPLS-GENERIC-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
} }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
::= { vplsCompliances 1 } ::= { vplsCompliances 1 }
-- Compliance requirement for read-only implementations. -- 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-MIB. provide read-only support for VPLS-GENERIC-MIB.
skipping to change at page 27, line 5 skipping to change at page 27, line 5
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
"Write access is not required." "Write access is not required."
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
OBJECT vplsConfigMacAging OBJECT vplsConfigMacAging
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsConfigFwdFullHighWatermark OBJECT vplsConfigFwdFullHighWatermark
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 28, line 4 skipping to change at page 28, line 4
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { vplsCompliances 2 } ::= { vplsCompliances 2 }
-- Units of conformance. -- Units of conformance.
vplsGroups vplsGroups
OBJECT IDENTIFIER ::= { vplsConformance 2 } OBJECT IDENTIFIER ::= { vplsConformance 2 }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
vplsGroup OBJECT-GROUP vplsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
vplsConfigName, vplsConfigName,
vplsBgpADConfigRouteDistinguisher, vplsBgpADConfigRouteDistinguisher,
vplsBgpRteTargetRTType, vplsBgpRteTargetRTType,
vplsBgpRteTargetRT, vplsBgpRteTargetRT,
vplsBgpRteTargetRowStatus, vplsBgpRteTargetRowStatus,
vplsBgpRteTargetStorageType, vplsBgpRteTargetStorageType,
vplsBgpADConfigPrefix, vplsBgpADConfigPrefix,
skipping to change at page 29, line 5 skipping to change at page 29, line 5
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
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
Pseudo Wire (PW) Binding to VPLS." Pseudo Wire (PW) Binding to VPLS."
::= { vplsGroups 2 } ::= { vplsGroups 2 }
vplsNotificationGroup NOTIFICATION-GROUP vplsNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
vplsStatusChanged, vplsStatusChanged,
vplsFwdFullAlarmRaised, vplsFwdFullAlarmRaised,
vplsFwdFullAlarmCleared vplsFwdFullAlarmCleared
} }
skipping to change at page 30, line 5 skipping to change at page 30, line 5
FROM PW-STD-MIB FROM PW-STD-MIB
vplsConfigIndex, vplsConfigName vplsConfigIndex, vplsConfigName
FROM VPLS-GENERIC-MIB; FROM VPLS-GENERIC-MIB;
vplsLdpDraft01MIB MODULE-IDENTITY vplsLdpDraft01MIB MODULE-IDENTITY
-- RFC Editor: Please replace vplsLdpDraft01MIB with -- RFC Editor: Please replace vplsLdpDraft01MIB with
-- vplsLdpMIB throughout the MIB and remove -- vplsLdpMIB throughout the MIB and remove
-- this note. -- this note.
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
LAST-UPDATED "201401301200Z" -- 30 Jan 2014 12:00:00 GMT LAST-UPDATED "201401301200Z" -- 30 Jan 2014 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
" "
Rohit Mediratta Rohit Mediratta
Email: Rohit.mediratta@alcatel-lucent.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 (2014). The initial "Copyright (C) The IETF Trust (2014). 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 signaled 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
network. " underlying pseudowire network. "
-- Revision history. -- Revision history.
REVISION REVISION
"201401230200Z" -- 30 Jan 2014 12:00:00 GMT "201401230200Z" -- 30 Jan 2014 12:00:00 GMT
DESCRIPTION "Editorial changes."
REVISION
"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 BBB }
-- RFC Editor: please replace XXXX with IANA assigned value, and -- RFC Editor: please replace BBB 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
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
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 }
skipping to change at page 31, line 32 skipping to change at page 31, line 32
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 Services (VPLS) in a packet network. for Virtual Private Lan Services (VPLS) in a packet
It is indexed by vplsConfigIndex, which uniquely network. 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 signaling. configured using LDP signaling.
All of the writable objects values can be All of the writable objects values can be
changed when vplsConfigRowStatus is in the active(1) changed when vplsConfigRowStatus is in the active(1)
state. state.
" "
INDEX { vplsConfigIndex } INDEX { vplsConfigIndex }
::= { vplsLdpConfigTable 1 } ::= { vplsLdpConfigTable 1 }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
VplsLdpConfigEntry ::= VplsLdpConfigEntry ::=
SEQUENCE { SEQUENCE {
vplsLdpConfigMacAddrWithdraw TruthValue vplsLdpConfigMacAddrWithdraw TruthValue
} }
vplsLdpConfigMacAddrWithdraw OBJECT-TYPE vplsLdpConfigMacAddrWithdraw OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
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
MAC address withdrawal is enabled. If false, then MAC address withdrawal is enabled. If false,
then MAC address withdrawal 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
skipping to change at page 33, line 5 skipping to change at page 33, line 5
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 signaling 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
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
vplsConfigIndex." vplsConfigIndex."
INDEX { vplsConfigIndex, pwIndex } 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-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object specifies the maximum number "The value of this object specifies the maximum
of learned and static entries allowed in the number 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 {
vplsConfigName, vplsConfigName,
skipping to change at page 34, line 4 skipping to change at page 34, line 4
vplsLdpCompliances vplsLdpCompliances
OBJECT IDENTIFIER ::= { vplsLdpConformance 1 } OBJECT IDENTIFIER ::= { vplsLdpConformance 1 }
-- Compliance requirement for fully compliant implementations -- 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
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
provide full support for VPLS-LDP-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
this MIB module." this MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
vplsLdpGroup, vplsLdpGroup,
vplsLdpNotificationGroup vplsLdpNotificationGroup
skipping to change at page 35, line 4 skipping to change at page 35, line 4
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { vplsLdpCompliances 2 } ::= { vplsLdpCompliances 2 }
-- Units of conformance. -- Units of conformance.
vplsLdpGroups vplsLdpGroups
OBJECT IDENTIFIER ::= { vplsLdpConformance 2 } OBJECT IDENTIFIER ::= { vplsLdpConformance 2 }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
vplsLdpGroup OBJECT-GROUP vplsLdpGroup OBJECT-GROUP
OBJECTS { OBJECTS {
vplsLdpConfigMacAddrWithdraw, vplsLdpConfigMacAddrWithdraw,
vplsLdpPwBindMacAddressLimit vplsLdpPwBindMacAddressLimit
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects supporting "The group of objects supporting
management of L2VPN VPLS services using LDP." management of L2VPN VPLS services using LDP."
skipping to change at page 36, line 4 skipping to change at page 36, line 4
RowStatus, StorageType RowStatus, StorageType
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC2579
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC3411 FROM SNMP-FRAMEWORK-MIB -- RFC3411
pwIndex pwIndex
FROM PW-STD-MIB -- RFC5601 FROM PW-STD-MIB -- RFC5601
vplsConfigIndex vplsConfigIndex
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
FROM VPLS-GENERIC-MIB FROM VPLS-GENERIC-MIB
; ;
vplsBgpDraft01MIB MODULE-IDENTITY vplsBgpDraft01MIB MODULE-IDENTITY
-- RFC Editor: Please replace vplsBgpDraft01MIB with -- RFC Editor: Please replace vplsBgpDraft01MIB with
-- vplsBgpMIB throughout the MIB and remove -- vplsBgpMIB throughout the MIB and remove
-- this note. -- this note.
LAST-UPDATED "201401301200Z" -- 30 Jan 2014 12:00:00 GMT LAST-UPDATED "201401301200Z" -- 30 Jan 2014 12:00:00 GMT
ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN)
skipping to change at page 36, line 37 skipping to change at page 36, line 37
"Copyright (C) The IETF Trust (2014). The initial "Copyright (C) The IETF Trust (2014). 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 signaled 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
network. " pseudowire network. "
-- Revision history. -- Revision history.
REVISION REVISION
"201401301200Z" -- 30 Jan 2014 12:00:00 GMT "201401301200Z" -- 30 Jan 2014 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 CCC }
-- RFC Editor: please replace XXXX with IANA assigned value, and -- RFC Editor: please replace CCC with IANA assigned value, and
-- delete this note. -- delete this note.
-- Top-level components of this MIB. -- Top-level components of this MIB.
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
-- 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
skipping to change at page 37, line 32 skipping to change at page 37, line 32
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 Services (VPLS) in a packet network. for Virtual Private LAN Services (VPLS) in a packet
It is indexed by vplsConfigIndex, which uniquely network. 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 A row is automatically created when a VPLS service is
created that is configured to use BGP signaling. created that is configured to use BGP signaling.
All of the writable objects values can be All of the writable objects values can be
changed when vplsConfigRowStatus is in the active(1) changed when vplsConfigRowStatus is in the active(1)
state. state.
" "
INDEX { vplsConfigIndex } INDEX { vplsConfigIndex }
::= { vplsBgpConfigTable 1 } ::= { vplsBgpConfigTable 1 }
VplsBgpConfigEntry ::= VplsBgpConfigEntry ::=
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
SEQUENCE { SEQUENCE {
vplsBgpConfigVERangeSize Unsigned32 vplsBgpConfigVERangeSize Unsigned32
} }
vplsBgpConfigVERangeSize OBJECT-TYPE vplsBgpConfigVERangeSize OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the size of the range of VE ids in this "Specifies the size of the range of VE ID in this
VPLS service. This number controls the size of the VPLS service. This number controls the size of the
label block advertised for this VE by the PE. label block advertised for this VE by the PE.
A value of 0 indicates that the range is not A value of 0 indicates that the range is not
configured and the PE derives the range value configured and the PE derives the range value
from received advertisements from other PEs." from received advertisements from other PEs.
The VE ID takes 2 octets in VPLS BGP NLRI according
to RFC 4761. Hence we have limited the the range of
this object to 65535."
DEFVAL { 0 } DEFVAL { 0 }
::= { vplsBgpConfigEntry 1 } ::= { vplsBgpConfigEntry 1 }
-- Vpls Edge Device (VE) Identifier Table -- Vpls Edge Device (VE) Identifier Table
vplsBgpVETable OBJECT-TYPE vplsBgpVETable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsBgpVEEntry SYNTAX SEQUENCE OF VplsBgpVEEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 39, line 4 skipping to change at page 39, line 4
Entries in this table may be created or deleted Entries in this table may be created or deleted
through SNMP, as side-effects of console or other through SNMP, as side-effects of console or other
non-SNMP management commands, or upon learning via non-SNMP management commands, or upon learning via
autodiscovery. autodiscovery.
It is optional for the agent to allow entries to be It is optional for the agent to allow entries to be
created that point to non-existent entries in created that point to non-existent entries in
vplsConfigTable." vplsConfigTable."
INDEX { vplsConfigIndex, vplsBgpVEId } INDEX { vplsConfigIndex, vplsBgpVEId }
::= { vplsBgpVETable 1 } ::= { vplsBgpVETable 1 }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
VplsBgpVEEntry ::= SEQUENCE { VplsBgpVEEntry ::= SEQUENCE {
vplsBgpVEId Unsigned32, vplsBgpVEId Unsigned32,
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.
The VE ID takes 2 octets in VPLS BGP NLRI according
to RFC 4761. Hence we have limited the the range of
this object to 65535."
::= { 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 associated with "Descriptive name for the site or u-PE associated with
this VE Id." this VE Id."
DEFVAL { "" } DEFVAL { "" }
skipping to change at page 40, line 5 skipping to change at page 40, line 5
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. delete a row in this table.
All other objects in this row must be set to valid All other objects in this row must be set to valid
values before this object can be set to active(1). values before this object can be set to active(1).
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
When a row in this table is in active(1) state, no When a row in this table is in active(1) state, no
objects in that row can be modified except objects in that row can be modified except
vplsBgpSiteRowStatus." vplsBgpSiteRowStatus."
::= { vplsBgpVEEntry 5 } ::= { vplsBgpVEEntry 5 }
vplsBgpVEStorageType OBJECT-TYPE vplsBgpVEStorageType 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 }
::= { 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
skipping to change at page 41, line 4 skipping to change at page 41, line 4
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 signaling 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, pwIndex } INDEX { vplsConfigIndex, pwIndex }
::= { vplsBgpPwBindTable 1 } ::= { vplsBgpPwBindTable 1 }
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
VplsBgpPwBindEntry ::= VplsBgpPwBindEntry ::=
SEQUENCE { SEQUENCE {
vplsBgpPwBindLocalVEId Unsigned32, vplsBgpPwBindLocalVEId Unsigned32,
vplsBgpPwBindRemoteVEId Unsigned32 vplsBgpPwBindRemoteVEId Unsigned32
} }
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 pseudowire "Identifies the local VE that this pseudowire
is associated with." is associated with.
The VE ID takes 2 octets in VPLS BGP NLRI according
to RFC 4761. Hence we have limited the the range of
this object to 65535."
::= { 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 pseudowire "Identifies the remote VE that this pseudowire
is associated with." is associated with.
The VE ID takes 2 octets in VPLS BGP NLRI according
to RFC 4761. Hence we have limited the the range of
this object to 65535."
::= { vplsBgpPwBindEntry 2 } ::= { vplsBgpPwBindEntry 2 }
-- Conformance Section -- Conformance Section
-- Compliance requirement for fully compliant implementations -- Compliance requirement for fully compliant implementations
vplsBgpCompliances vplsBgpCompliances
OBJECT IDENTIFIER ::= { vplsBgpConformance 1 } OBJECT IDENTIFIER ::= { vplsBgpConformance 1 }
vplsBgpModuleFullCompliance MODULE-COMPLIANCE vplsBgpModuleFullCompliance MODULE-COMPLIANCE
skipping to change at page 42, line 5 skipping to change at page 42, line 5
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
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
} }
::= { vplsBgpCompliances 1 } ::= { vplsBgpCompliances 1 }
-- Compliance requirement for read-only implementations. -- 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
skipping to change at page 43, line 4 skipping to change at page 43, line 4
OBJECT vplsBgpVERowStatus OBJECT vplsBgpVERowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { vplsBgpCompliances 2 } ::= { vplsBgpCompliances 2 }
-- Units of conformance. -- Units of conformance.
vplsBgpGroups vplsBgpGroups
VPLS Management Information Base Jan, 2014 VPLS Management Information Base Feb, 2014
OBJECT IDENTIFIER ::= { vplsBgpConformance 2 } OBJECT IDENTIFIER ::= { vplsBgpConformance 2 }
vplsBgpConfigGroup OBJECT-GROUP vplsBgpConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
vplsBgpConfigVERangeSize vplsBgpConfigVERangeSize
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects supporting configuration "The group of objects supporting configuration
skipping to change at page 43, line 46 skipping to change at page 43, line 46
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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 There are a number of management objects defined in this MIB
association with the PW-STD-MIB [RFC5601] are potentially module with a MAX-ACCESS clause of read-write and/or read-create.
useful for monitoring of VPLS capable LERs. These MIB modules can Such objects may be considered sensitive or vulnerable in some
also be used for configuration of certain objects, and anything that network environments.The support for SET operations in a
can be configured can be incorrectly configured, with potentially non-secure environment without proper protection can have a
undesirable results. negative effect on network operations. These are the tables
and their sensitivity/vulnerability:
While the read-write and read-create objects must be protected by VPLS Management Information Base Feb, 2014
VPLS Management Information Base Jan, 2014 o vplsConfigTable:
o vplsPwBindTable:
o vplsBgpADConfigTable:
o vplsBgpRteTargetTable:
o vplsLdpPwBindTable:
o vplsLdpConfigTable:
o vplsBgpConfigTable:
o vplsBgpVETable:
These tables contain read-create/read-write objects which
can be used to configure or modify a LDP/BGP VPLS service.
Any improper configuration or modification of objects in
these tables can disrupt VPLS services.
The use of stronger mechanisms such as SNMPv3 security
should be considered where possible for configuring these
objects. Specifically, SNMPv3 VACM and USM MUST be used
with any v3 agent which provides SET access to these tables.
secure SNMP, none of them are especially disruptive. Similarly, o vplsNotificationMaxRate
while the read-only objects might present privacy concerns and due Setting of a very high value to this object can cause a
consideration should be given to protecting them with secure SNMP, notification storm which may disrupt network service.
none of these objects contain especially sensitive information.
Most of the readable objects in this MIB module (i.e., objects
with a MAX-ACCESS other than not-accessible) may be considered
sensitive or vulnerable in some network environments.It is
thus important to control even GET and/or NOTIFY access to these
objects and possibly to even encrypt the values of these objects
when sending them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using
IPsec), there is no control as to who on the secure network
is allowed to access and GET/SET (read/change/create/delete)
the objects in this MIB module.
Implementations SHOULD provide the security features described
by the SNMPv3 framework (see [RFC3410]), and implementations
claiming compliance to the SNMPv3 standard MUST include full
support for authentication and privacy via the User-based Security
Model (USM) [RFC3414] with the AES cipher algorithm [RFC3826].
Implementations MAY also provide support for the Transport Security
Model (TSM) [RFC5591] in combination with a secure transport such
as SSH [RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access
to the objects only to those principals (users) that have
legitimate rights to indeed GET or SET (change/create/delete) them.
VPLS Management Information Base Feb, 2014
8. IANA Considerations 8. IANA Considerations
The MIB modules in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
8.1. IANA Considerations for VPLS-GENERIC-MIB
The IANA is requested to assign { transmission AAA } to the
VPLS-GENERIC-MIB module specified in this document.
8.2. IANA Considerations for VPLS-LDP-MIB
The IANA is requested to assign { transmission BBB } to the
VPLS-LDP-MIB module specified in this document.
8.3. IANA Considerations for VPLS-BGP-MIB
The IANA is requested to assign { transmission CCC } to the
VPLS-BGP-MIB MIB module specified in this document.
-- Editor's Note (to be removed prior to publication): the IANA is
-- requested to assign a value for "AAA", "BBB" and "CCC" under
-- the transmission subtree and to record the assignments in the
-- SMI Numbers registry. When the assignments have been made, the
-- RFC Editor is asked to replace "AAA", "BBB" and "CCC" (here and
-- in the MIB modules) with the assigned values and to remove this
-- note.
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.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999. Statements for SMIv2", STD 58, RFC 2580, April 1999.
VPLS Management Information Base Feb, 2014
[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.
[RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View- [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-
based Access Control Model (VACM) for the Simple based Access Control Model (VACM) for the Simple
Network Management Protocol (SNMP)", STD 62, RFC Network Management Protocol (SNMP)", STD 62, RFC
3415, December 2002. 3415, December 2002.
[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) Conventions for Virtual Private Network (VPN)
Management", RFC 4265, November 2005. Management", RFC 4265, November 2005.
VPLS Management Information Base Jan, 2014
[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
[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.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, VPLS Management Information Base Feb, 2014
"Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Architecture for Describing Simple Network Management "Introduction and Applicability Statements for
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC3813] Srinivasan, C., Viswanathan, A. and Nadeau, T., [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
"Multiprotocol Label Switching (MPLS) Label Switching Architecture for Describing Simple Network Management
Router (LSR) Management Information Base", Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
RFC 3813, June 2004 December 2002.
[RFC3813] Srinivasan, C., Viswanathan, A. and Nadeau, T.,
"Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base",
RFC 3813, June 2004
[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.
[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.
[RFC6074] E. Rosen et. al., "Provisioning, Autodiscovery, and [RFC6074] E. Rosen et. al., "Provisioning, Autodiscovery, and
Signaling in L2VPNs", RFC 6074, January 2011. Signaling in L2VPNs", RFC 6074, January 2011.
10. Acknowledgments 10. Acknowledgments
VPLS Management Information Base Jan, 2014
We wish to thank Marcelo Mourier and Reva Bailey for their We wish to thank Marcelo Mourier and Reva Bailey for their
valuable feedback. Some portion of the work has been referenced valuable feedback. Some portion of the work has been referenced
from their original Timetra Enterprise MIB work. from their original Timetra Enterprise MIB work.
We wish to thank Praveen Muley, VJ Shah, Li Wentao, Kong Yong, Luo We wish to thank Praveen Muley, VJ Shah, Li Wentao, Kong Yong, Luo
Jian, Feng Jun, Takeshi Usui for their feedback. Jian, Feng Jun, Takeshi Usui for their feedback.
11. Authors' Addresses 11. Authors' Addresses
skipping to change at page 46, line 30 skipping to change at page 48, line 4
Cisco Systems Inc. Cisco Systems Inc.
12515 Research Blvd, Bldg 4, 12515 Research Blvd, Bldg 4,
Austin, TX 78759 Austin, TX 78759
Email: kkoushik@cisco.com Email: kkoushik@cisco.com
Rohit Mediratta Rohit Mediratta
Alcatel-Lucent, Alcatel-Lucent,
701 E Middlefield Rd. 701 E Middlefield Rd.
Mountain View, CA 94040 Mountain View, CA 94040
Email: rohit.mediratta@alcatel-lucent.com Email: rohit.mediratta@alcatel-lucent.com
VPLS Management Information Base Feb, 2014
12. Full Copyright Statement 12. Full Copyright Statement
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as 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
VPLS Management Information Base Jan, 2014
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,
except to format it for publication as an RFC or to translate it except to format it for publication as an RFC or to translate it
into languages other than English. into languages other than English.
 End of changes. 111 change blocks. 
195 lines changed or deleted 260 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/