draft-ietf-l2vpn-vpls-mib-15.txt   rfc7257.txt 
L2VPN Working Group Thomas D. Nadeau (Ed.)
Internet Draft Lucid Vision
Intended status: Standards Track
Expires: Aug 2014 Agrahara S Kiran Koushik (Ed.)
Cisco Systems, Inc.
Rohit Mediratta (Ed.) Internet Engineering Task Force (IETF) T. Nadeau, Ed.
Alcatel-Lucent Request for Comments: 7257 Lucid Vision
Category: Standards Track A. Kiran Koushik, Ed.
ISSN: 2070-1721 Brocade
R. Mediratta, Ed.
Cisco Systems, Inc.
July 2014
Feburary 19, 2014 Virtual Private LAN Service (VPLS) Management Information Base
Virtual Private Lan Services (VPLS) Management Information Base Abstract
draft-ietf-l2vpn-vpls-mib-15.txt This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects to configure and/or
monitor Virtual Private LAN services. It needs to be used in
conjunction with the Pseudowire (PW) Management Information Base
(PW-STD-MIB from RFC 5601).
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7257.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
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) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Internet-Drafts are working documents of the Internet Engineering Table of Contents
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
VPLS Management Information Base Feb, 2014
This Internet-Draft will expire on July 30, 2014.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal 1. Introduction ....................................................3
Provisions Relating to IETF Documents 2. Terminology .....................................................3
(http://trustee.ietf.org/license-info) in effect on the date of 2.1. Conventions Used in This Document ..........................4
publication of this document. Please review these documents 3. The Internet-Standard Management Framework ......................4
carefully, as they describe your rights and restrictions with 4. VPLS MIB Module Architecture ....................................4
respect to this document. Code Components extracted from this 4.1. VPLS-GENERIC-MIB Module Usage ..............................5
document must include Simplified BSD License text as described in 4.2. VPLS-LDP-MIB Module Usage ..................................6
Section 4.e of the Trust Legal Provisions and are provided without 4.3. VPLS-BGP-MIB Module Usage ..................................6
warranty as described in the Simplified BSD License. 4.4. Relations to Other MIB Modules .............................6
5. Example of the VPLS MIB Modules Usage ...........................6
6. Object Definitions ..............................................8
6.1. VPLS-GENERIC-MIB Object Definitions ........................8
6.2. VPLS-LDP-MIB Object Definitions ...........................29
6.3. VPLS-BGP-MIB Object Definitions ...........................35
7. Security Considerations ........................................44
8. IANA Considerations ............................................45
8.1. IANA Considerations for VPLS-GENERIC-MIB ..................45
8.2. IANA Considerations for VPLS-LDP-MIB ......................45
8.3. IANA Considerations for VPLS-BGP-MIB ......................45
9. References .....................................................46
9.1. Normative References ......................................46
9.2. Informative References ....................................47
10. Acknowledgments ...............................................48
Abstract 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for to configure and/or In particular, it defines three MIB modules that can be used to
monitor Virtual Private LAN services. It needs to be used in manage VPLS (Virtual Private LAN Service) for transmission over a
conjunction with The Pseudowire (PW) Management Information Base. Packet Switched Network (PSN) using LDP [RFC4762] or BGP [RFC4761]
signaling. This MIB module provides generic management of VPLS
Table of Contents services as defined by the IETF L2VPN Working Group. Additional MIB
modules are also defined for management of LDP VPLS and BGP VPLS
1. Introduction...................................................3 services by the IETF L2VPN Working Group.
2. Terminology....................................................3
2.1. Conventions used in this document.........................3
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
VPLS Management Information Base Feb, 2014
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
1. Introduction
This memo defines a portion of the Management Information
Base (MIB) for use with network management protocols in the Internet
community. In particular, it defines three MIB modules 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] signaling. 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 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 described again 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",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [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
of RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store, termed
termed the Management Information Base or MIB. MIB objects are the Management Information Base or MIB. MIB objects are generally
generally accessed through the Simple Network Management Protocol accessed through the Simple Network Management Protocol (SNMP).
(SNMP). Objects in the MIB are defined using the mechanisms Objects in the MIB are defined using the mechanisms defined in the
defined in the Structure of Management Information (SMI). This Structure of Management Information (SMI). This memo specifies MIB
memo specifies a set of MIB modules that are compliant to the SMIv2, modules that are compliant to the SMIv2, which is described in STD
which is described in STD 58 [RFC2578][RFC2579][RFC2580]. 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
2580 [RFC2580].
4. VPLS MIB Module Architecture 4. VPLS MIB Module Architecture
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
three MIB modules. MIB modules. (They are referred to as "VPLS MIB" in the figure
below.)
The first is the VPLS-GENERIC-MIB module, which configures The first is the VPLS-GENERIC-MIB module, which configures general
general parameters of the VPLS service that are common to all parameters of the VPLS service that are common to all types of VPLS
types of VPLS services. services.
The second is the VPLS-LDP-MIB module, which configures The second is the VPLS-LDP-MIB module, which configures VPLS-LDP
VPLS-LDP [RFC4762] specific parameters of the VPLS service. [RFC4762] specific parameters of the VPLS service.
The third is the VPLS-BGP-MIB module, which configures The third is the VPLS-BGP-MIB module, which configures VPLS-BGP
VPLS-BGP [RFC4761] specific parameters of the VPLS service. [RFC4761] specific parameters of the VPLS service.
The arrows in Figure A indicate whether we can map data from The arrows in Figure 1 indicate whether we can map data from one
one module into another. module into another.
-------- ----------------- ---------- -----------------
PW Mapping | | | | PW Mapping | | | PW-ENET-STD-MIB |
-----> | PW-MIB |-->|PW-ENET/MPLS-MIB | ----->|PW-STD-MIB|-->| or |
__________ / | | | | __________ / | | | PW-MPLS-STD-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] | |
------------ ------------
Figure A Figure 1
--------
Additionally service-specific modules may be defined in other Additionally, service-specific modules may be defined in other
documents. documents.
4.1. VPLS-GENERIC-MIB Module Usage 4.1. VPLS-GENERIC-MIB Module Usage
An entry in the vplsConfigTable MUST exist for every VPLS service. An entry in the vplsConfigTable MUST exist for every VPLS service.
This table holds generic parameters which apply to a VPLS service This table holds generic parameters that apply to a VPLS service
which can be signaled via LDP or BGP. which can be signaled 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
the following ways: following ways:
1) An NMS creates a row in the vplsConfigTable using SNMP Set 1) A Network Management System (NMS) creates a row in the
requests which causes the node to create and start a new VPLS vplsConfigTable using Simple Network Management Protocol (SNMP)
service. The agent MUST support the creation of VPLS Set requests, which causes the node to create and start a new VPLS
services in this way. service. The agent MUST support the creation of VPLS 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 configuration
VPLS Management Information Base Feb, 2014 that is done through non-SNMP applications. This mode is
OPTIONAL.
configuration that is done through non-SNMP applications. At least one entry in the vplsPwBindTable MUST exist for each VPLS
This mode is OPTIONAL. service.
At least one entry in the vplsPwBindTable MUST exist for This Binding table links one VPLS service with one or many
each VPLS service. pseudowires (defined in [RFC5601]). Each pseudowire may be used as a
This binding table links one VPLS service with one or many spoke or as part of a mesh based on the parameters defined in this
pseudowires (defined in [RFC5601]). Each pseudowire may table.
be used as a spoke or as part of a mesh based on the parameters
defined in this table.
For each VPLS service, an entry in the vplsBgpAdConfigTable MUST For each VPLS service, an entry in the vplsBgpAdConfigTable MUST
exist if Auto-discovery has been enabled for that service. exist if Auto-discovery has been enabled for that service. This
This table stores the information required for auto-discovery. table stores the information required for auto-discovery.
For each VPLS service, at least one entry in the For each VPLS service, at least one entry in the
vplsBgpRteTargetTable MUST exist if auto-discovery vplsBgpRteTargetTable MUST exist if auto-discovery has been
has been configured for that service. One service can import configured for that service. One service can import and export
and export multiple Route Targets. multiple Route Targets.
4.2. VPLS-LDP-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
for a VPLS service signaled using LDP. VPLS service signaled using LDP.
4.3. VPLS-BGP-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
for a VPLS service signaled using BGP. 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 the pwTable in - The vplsPwBindTable links the VPLS entry to the pwTable in
[RFC5601] [RFC5601].
- The association of MAC addresses to VPLS entries is possible - The association of Media Access Control (MAC) addresses to VPLS
by adding a turnstile function to interpret the entries in entries is possible by adding a turnstile function to interpret the
[SNMP-CONTEXT-MAP-MIB]. In [SNMP-CONTEXT-MAP-MIB] there is entries in [SNMP-CONTEXT-MAP-MIB]. In [SNMP-CONTEXT-MAP-MIB],
a mapping between the vacmContextName [RFC3415] to there is a mapping from the vacmContextName [RFC3415] to
dot1dBasePort [RFC4188] and vplsConfigIndex. This mapping can dot1dBasePort [RFC4188] and vplsConfigIndex. This mapping can be
be used to map the vplsConfigIndex to a dot1dBasePort used to map the vplsConfigIndex to a dot1dBasePort in the BRIDGE-
in the BRIDGE-MIB. This resulting value of dot1dBasePort MIB. This resulting value of dot1dBasePort can be used to access
can be used to access corresponding MAC addresses that belong corresponding MAC addresses that belong to a particular
to a particular vplsConfigIndex. vplsConfigIndex.
- Unless all the necessary entries in the applicable tables have - Unless all the necessary entries in the applicable tables have been
been created and all the parameters have been consistently created and all the parameters have been consistently configured in
configured in those tables, signaling cannot be performed those tables, signaling cannot be performed from the local node,
VPLS Management Information Base Feb, 2014 and the vplsConfigRowStatus should report 'notReady'.
from the local node, and the vplsConfigRowStatus should report - Statistics can be gathered from the PW Performance tables in
'notReady'. [RFC5601].
- Statistics can be gathered from the Pseudowire performance 5. Example of the VPLS MIB Modules Usage
tables in [RFC5601]
5. Example of the VPLS MIB modules usage In this section, we provide an example of the use of the MIB objects
described in Section 6 to set up a VPLS service over MPLS. While
this example is not meant to illustrate every permutation of the MIB,
it is intended as an aid to understanding some of the key concepts.
It is meant to be read after going through the MIB itself.
In this section we provide an example of using the MIB objects In this example, a VPLS service (VPLS-A) is set up using LDP for
described in section 7 to set up a VPLS service over MPLS. While signaling the pseudowire. The Binding between the VPLS service and
this example is not meant to illustrate every permutation of the the pseudowire is reflected in the VplsPwBindTable. The pseudowire
MIB, it is intended as an aid to understanding some of the key configuration is defined in RFC 5601.
concepts. It is meant to be read after going through the MIB
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-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),
vplsConfigDiscardUnknownDest 2(false), vplsConfigDiscardUnknownDest 2(false),
vplsConfigMacAging 1(true), vplsConfigMacAging 1(true),
vplsConfigVpnId "100:10" vplsConfigVpnId "100:10"
vplsConfigRowStatus 1(active) vplsConfigRowStatus 1(active)
} }
Row in vplsStatusTable: Row in vplsStatusTable:
{ {
vplsStatusOperStatus 1(up), vplsStatusOperStatus 1(up),
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 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:
{ {
vplsLdpPwBindType 1(mesh), vplsLdpPwBindType 1(mesh),
vplsLdpPwBindMacAddressLimit 100 vplsLdpPwBindMacAddressLimit 100
} }
6. Object definitions 6. Object Definitions
6.1. VPLS-GENERIC-MIB 6.1. VPLS-GENERIC-MIB Object Definitions
This MIB module makes references to the following documents. This MIB module mentions the following documents: [RFC2578],
[RFC2578], [RFC2579], [RFC2580], [RFC3411], [RFC2579], [RFC2580], [RFC3411], [RFC5601], [RFC4265], [RFC4364],
[RFC2863], [RFC4265] and [RFC3813]. [RFC4761], [RFC4762], [RFC6074], and [RFC3413].
VPLS-GENERIC-MIB DEFINITIONS ::= BEGIN VPLS-GENERIC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, Counter32, transmission
FROM SNMPv2-SMI -- RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
FROM SNMPv2-CONF -- RFC2580 Unsigned32, Counter32, transmission
FROM SNMPv2-SMI -- RFC 2578
TruthValue, RowStatus, StorageType, TEXTUAL-CONVENTION MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString TruthValue, RowStatus, StorageType, TEXTUAL-CONVENTION
FROM SNMP-FRAMEWORK-MIB -- RFC3411 FROM SNMPv2-TC -- RFC 2579
pwIndex SnmpAdminString
FROM PW-STD-MIB FROM SNMP-FRAMEWORK-MIB -- RFC 3411
VPNIdOrZero pwIndex
FROM VPN-TC-STD-MIB -- RFC4265 FROM PW-STD-MIB -- RFC 5601
VPLS Management Information Base Feb, 2014 VPNIdOrZero
FROM VPN-TC-STD-MIB -- RFC 4265
; ;
vplsGenericDraft01MIB MODULE-IDENTITY vplsGenericMIB MODULE-IDENTITY
-- RFC Editor: Please replace vplsGenericDraft01MIB with LAST-UPDATED "201405191200Z" -- 19 May 2014 12:00:00 GMT
-- vplsGenericMIB throughout the MIB and remove
-- this note.
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
" "
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@lucidvison.com Email: tnadeau@lucidvison.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/wg/l2vpn/charter)
" "
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2014). The initial "Copyright (c) 2014 IETF Trust and the persons
version of this MIB module was published in RFC XXXX. identified as authors of the code. All rights reserved.
-- RFC Editor: Please replace XXXX with RFC number & remove
-- this note. Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
The initial version of this MIB module was published in
RFC 7257; for full legal notices see the RFC itself.
For full legal notices see the RFC itself or see:
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 Service as defined in RFC 4761 and
RFC4761. RFC 4762.
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 "201405191200Z" -- 19 May 2014 12:00:00 GMT
VPLS Management Information Base Feb, 2014
DESCRIPTION "Initial version published as part of RFC YYYY." DESCRIPTION "Initial version published as part of RFC 7257."
-- RFC Editor: please replace YYYY with IANA assigned value, and ::= { transmission 274 }
-- delete this note.
::= { transmission AAA } VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Syntax for a route distinguisher that matches the
definition in RFC 4364. For a complete
definition of a route distinguisher, see RFC 4364.
For more details on use of a route distinguisher
for a VPLS service, see RFC 4761."
REFERENCE
"RFC 4364"
SYNTAX OCTET STRING(SIZE (0..256))
-- RFC Editor: please replace AAA with IANA assigned value, and VplsBgpRouteTarget ::= TEXTUAL-CONVENTION
-- delete this note.
-- VPLS BGP Auto-Discovery specific Textual Convention
VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Syntax for a route distinguisher that matches the "Syntax for a Route Target that matches the
definition in RFC4364. For a complete definition in RFC 4364. For a complete
definition of a route distinguisher, see RFC4364. definition of a Route Target, see RFC 4364."
For more details on use of a route distinguisher
for a VPLS service, see RFC4761."
REFERENCE REFERENCE
"RFC4364" "RFC 4364"
SYNTAX OCTET STRING(SIZE (0..256))
VplsBgpRouteTarget ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Syntax for a route target that matches the
definition in RFC4364. For a complete
definition of a route target, see RFC4364."
REFERENCE
"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 RFC 4364."
REFERENCE REFERENCE
VPLS Management Information Base Feb, 2014 "RFC 4364"
"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 } ::= { vplsGenericMIB 0 }
-- Tables, Scalars -- Tables, Scalars
vplsObjects OBJECT IDENTIFIER vplsObjects OBJECT IDENTIFIER
::= { vplsGenericDraft01MIB 1 } ::= { vplsGenericMIB 1 }
-- Conformance -- Conformance
vplsConformance OBJECT IDENTIFIER vplsConformance OBJECT IDENTIFIER
::= { vplsGenericDraft01MIB 2 } ::= { vplsGenericMIB 2 }
-- PW Virtual Connection Table -- PW Virtual Connection Table
vplsConfigIndexNext OBJECT-TYPE vplsConfigIndexNext OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an appropriate value to be used "This object contains an appropriate value to be used
for vplsConfigIndex when creating entries in the for vplsConfigIndex when creating entries in the
vplsConfigTable. The value 0 indicates that no vplsConfigTable. The value 0 indicates that no
unassigned entries are available. To obtain the unassigned entries are available. To obtain the
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 }
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 Service (VPLS).
" "
::= { vplsObjects 2 } ::= { vplsObjects 2 }
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 state. Changes for vplsConfigSignalingType are only
allowed when the vplsConfigRowStatus is in allowed when the vplsConfigRowStatus is in
notInService(2) or 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,
skipping to change at page 12, line 4 skipping to change at page 12, line 9
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 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
STATUS current STATUS current
skipping to change at page 12, line 30 skipping to change at page 12, line 33
contain a zero-length octet string." contain a zero-length octet string."
DEFVAL { "" } DEFVAL { "" }
::= { vplsConfigEntry 2 } ::= { vplsConfigEntry 2 }
vplsConfigDescr OBJECT-TYPE vplsConfigDescr OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about the "A textual string containing information about the
VPLS service. If there is no information for this VPLS VPLS service. If there is no information for this VPLS
service, then this object MUST contain a zero-length service, then this object MUST contain a zero-length
octet string." octet string."
DEFVAL { "" } DEFVAL { "" }
::= { 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
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 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
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
received with an unknown destination MAC are discarded received with an unknown destination MAC are discarded
in this VPLS. If 'false', then the packets are in this VPLS. If 'false', then the packets are
processed." processed."
DEFVAL { false } DEFVAL { false }
::= { vplsConfigEntry 7 } ::= { vplsConfigEntry 7 }
vplsConfigMacAging OBJECT-TYPE vplsConfigMacAging 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' "If the value of this object is 'true',
then the MAC aging process is enabled in then the MAC aging process is enabled in
this VPLS. If 'false', then the MAC aging process this VPLS. If 'false', then the MAC aging process
is disabled" is disabled."
DEFVAL { true } DEFVAL { true }
::= { vplsConfigEntry 8 } ::= { vplsConfigEntry 8 }
vplsConfigFwdFullHighWatermark OBJECT-TYPE vplsConfigFwdFullHighWatermark OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..100)
UNITS "percentage" UNITS "percentage"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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. The value of this object must will be sent. The value of this object must
be higher than vplsConfigFwdFullLowWatermark." be higher than vplsConfigFwdFullLowWatermark."
VPLS Management Information Base Feb, 2014
DEFVAL { 95 } DEFVAL { 95 }
::= { vplsConfigEntry 10 } ::= { vplsConfigEntry 10 }
vplsConfigFwdFullLowWatermark OBJECT-TYPE vplsConfigFwdFullLowWatermark OBJECT-TYPE
SYNTAX Unsigned32 (0..99) 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. The value of this notification will be sent. The value of this
object must be less than object must be less than
vplsConfigFwdFullHighWatermark" 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.
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 this object is set to destroy(6) or deleted by the If this object is set to destroy(6) or deleted by the
agent, all associated entries in the vplsPWBindTable, agent, all associated entries in the vplsPwBindTable,
vplsBGPRteTargetTable and vplsBgpVETable shall be vplsBgpRteTargetTable, and vplsBgpVETable shall be
deleted." deleted."
::= { vplsConfigEntry 12 } ::= { vplsConfigEntry 12 }
vplsConfigMtu OBJECT-TYPE vplsConfigMtu OBJECT-TYPE
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 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 15, line 47 skipping to change at page 16, line 6
corresponding entry in vplsLdpConfigTable is required. corresponding entry in vplsLdpConfigTable is required.
If the value of this object is bgp(2), then a If the value of this object is bgp(2), then a
corresponding entry in vplsBgpConfigTable is required. corresponding entry in vplsBgpConfigTable is required.
If the value of this object is none(3), then it If the value of this object is none(3), then it
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
vplsStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsStatusEntry
MAX-ACCESS not-accessible
STATUS current
VPLS Management Information Base Feb, 2014
DESCRIPTION
"This table provides information for monitoring
Virtual Private Lan Services (VPLS).
"
::= { vplsObjects 3 }
vplsStatusEntry OBJECT-TYPE
SYNTAX VplsStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in this table represents a Virtual Private Lan
Service(VPLS) in a packet network. It is indexed by
vplsConfigIndex, which uniquely identifies a single VPLS.
A row in this table is automatically created by the agent vplsStatusTable OBJECT-TYPE
when a VPLS service is first set to active. SYNTAX SEQUENCE OF VplsStatusEntry
" MAX-ACCESS not-accessible
AUGMENTS { vplsConfigEntry } STATUS current
::= { vplsStatusTable 1 } DESCRIPTION
"This table provides information for monitoring
Virtual Private LAN Service (VPLS).
"
::= { vplsObjects 3 }
VplsStatusEntry ::= vplsStatusEntry OBJECT-TYPE
SEQUENCE { SYNTAX VplsStatusEntry
vplsStatusOperStatus INTEGER, MAX-ACCESS not-accessible
vplsStatusPeerCount Counter32 STATUS current
} DESCRIPTION
"A row in this table represents a Virtual Private LAN
Service (VPLS) in a packet network. It is indexed by
vplsConfigIndex, which uniquely identifies a single VPLS.
vplsStatusOperStatus OBJECT-TYPE A row in this table is automatically created by the agent
SYNTAX INTEGER { when a VPLS service is first set to active.
other(0), "
up(1), AUGMENTS { vplsConfigEntry }
down(2) ::= { vplsStatusTable 1 }
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current operational state of this VPLS Service."
::= { vplsStatusEntry 1 }
vplsStatusPeerCount OBJECT-TYPE VplsStatusEntry ::=
SYNTAX Counter32 SEQUENCE {
MAX-ACCESS read-only vplsStatusOperStatus INTEGER,
STATUS current vplsStatusPeerCount Counter32
DESCRIPTION }
"This objects specifies the number of peers
(pseudowires) present in this VPLS instance."
::= { vplsStatusEntry 2 }
VPLS Management Information Base Feb, 2014
-- VPLS PW Binding Table vplsStatusOperStatus OBJECT-TYPE
SYNTAX INTEGER {
other(0),
up(1),
down(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current operational state of this VPLS service."
::= { vplsStatusEntry 1 }
vplsPwBindTable OBJECT-TYPE vplsStatusPeerCount OBJECT-TYPE
SYNTAX SEQUENCE OF VplsPwBindEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides an association between a "This objects specifies the number of peers
VPLS service and the corresponding pseudowires. (pseudowires) present in this VPLS instance."
A service can have more than one pseudowire ::= { vplsStatusEntry 2 }
association. Pseudowires are defined in
the pwTable"
::= { vplsObjects 4 }
vplsPwBindEntry OBJECT-TYPE -- VPLS PW Binding Table
SYNTAX VplsPwBindEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each row represents an association between a
VPLS instance and a pseudowire
defined in the pwTable. Each index is unique
in describing an entry in this table. However
both indexes are required to define the one
to many association of service to
pseudowire.
Entries in this table may be created or deleted vplsPwBindTable OBJECT-TYPE
through SNMP, as side-effects of console or other SYNTAX SEQUENCE OF VplsPwBindEntry
non-SNMP management commands, or upon learning via MAX-ACCESS not-accessible
autodiscovery. STATUS current
DESCRIPTION
"This table provides an association between a
VPLS service and the corresponding pseudowires.
A service can have more than one pseudowire
association. Pseudowires are defined in
the pwTable"
::= { vplsObjects 4 }
It is optional for the agent to allow entries to be vplsPwBindEntry OBJECT-TYPE
created that point to non-existent entries in SYNTAX VplsPwBindEntry
vplsConfigTable." MAX-ACCESS not-accessible
INDEX { vplsConfigIndex, pwIndex } STATUS current
::= { vplsPwBindTable 1 } DESCRIPTION
"Each row represents an association between a
VPLS instance and a pseudowire
defined in the pwTable. Each index is unique
in describing an entry in this table. However,
both indexes are required to define the one
to many association of service to
pseudowire.
VplsPwBindEntry ::= Entries in this table may be created or deleted
SEQUENCE { through SNMP, as side effects of console or other
vplsPwBindConfigType INTEGER, non-SNMP management commands, or upon learning via
vplsPwBindType INTEGER, autodiscovery.
vplsPwBindRowStatus RowStatus,
vplsPwBindStorageType StorageType
}
vplsPwBindConfigType OBJECT-TYPE It is optional for the agent to allow entries to be
SYNTAX INTEGER { created that point to nonexistent entries in
VPLS Management Information Base Feb, 2014 vplsConfigTable."
INDEX { vplsConfigIndex, pwIndex }
::= { vplsPwBindTable 1 }
manual (1), VplsPwBindEntry ::=
autodiscovery (2) SEQUENCE {
} vplsPwBindConfigType INTEGER,
MAX-ACCESS read-create vplsPwBindType INTEGER,
STATUS current vplsPwBindRowStatus RowStatus,
DESCRIPTION vplsPwBindStorageType StorageType
"The value of this object indicates }
whether the Pseudo Wire binding was created
via SNMP/Console or via Auto-Discovery.
The value of this object must be vplsPwBindConfigType OBJECT-TYPE
specified when the row is created and cannot SYNTAX INTEGER {
be changed while the row status is active(1)" manual (1),
::= { vplsPwBindEntry 1 } autodiscovery (2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object indicates
whether the pseudowire Binding was created
via SNMP/Console or via Auto-Discovery.
vplsPwBindType OBJECT-TYPE The value of this object must be
SYNTAX INTEGER { specified when the row is created and cannot
mesh (1), be changed while the row status is active(1)"
spoke (2) ::= { vplsPwBindEntry 1 }
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object indicates
whether the pseudowire binding is of
type mesh or spoke.
The value of this object must be vplsPwBindType OBJECT-TYPE
specified when the row is created and cannot SYNTAX INTEGER {
be changed while the row status is active(1)" mesh (1),
::= { vplsPwBindEntry 2 } spoke (2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this object indicates
whether the pseudowire Binding is of
type mesh or spoke.
vplsPwBindRowStatus OBJECT-TYPE The value of this object must be
SYNTAX RowStatus specified when the row is created and cannot
MAX-ACCESS read-create be changed while the row status is active(1)"
STATUS current ::= { vplsPwBindEntry 2 }
DESCRIPTION
"For creating, modifying, and deleting this row.
All other objects in this row must be set to valid vplsPwBindRowStatus OBJECT-TYPE
values before this object can be set to active(1). SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For creating, modifying, and deleting this row.
None of the read-create objects in the All other objects in this row must be set to valid
conceptual rows may be changed when this values before this object can be set to active(1).
object is in the active(1) state.
If autodiscovered entries are deleted they would None of the read-create objects in the
likely re-appear in the next autodiscovery interval." conceptual rows may be changed when this
object is in the active(1) state.
VPLS Management Information Base Feb, 2014 If autodiscovered entries are deleted they would
likely re-appear in the next autodiscovery interval."
::= { vplsPwBindEntry 3 }
::= { vplsPwBindEntry 3 } vplsPwBindStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this row."
DEFVAL { volatile }
::= { vplsPwBindEntry 4 }
vplsPwBindStorageType OBJECT-TYPE -- vplsBgpADConfigTable
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this row."
DEFVAL { volatile }
::= { vplsPwBindEntry 4 }
vplsBgpADConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF VplsBgpADConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies information for configuring
BGP Auto-Discovery parameters for a given VPLS service.
"
::= { vplsObjects 5 }
vplsBgpADConfigTable OBJECT-TYPE vplsBgpADConfigEntry OBJECT-TYPE
SYNTAX SEQUENCE OF VplsBgpADConfigEntry SYNTAX VplsBgpADConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies information for configuring "A row in this table indicates that BGP based Auto-
BGP Auto-Discovery parameters for a given VPLS service. Discovery is in use for this instance of VPLS.
" A row in this table is indexed by vplsConfigIndex, which
::= { vplsObjects 5 } uniquely identifies a single VPLS.
vplsBgpADConfigEntry OBJECT-TYPE Entries in this table may be created or deleted
SYNTAX VplsBgpADConfigEntry through SNMP, as side effects of console or other
MAX-ACCESS not-accessible non-SNMP management commands, or upon learning via
STATUS current autodiscovery.
DESCRIPTION
"A row in this table indicates that BGP based Auto-
Discovery is in use for this instance of VPLS.
A row in this table is indexed by vplsConfigIndex, which
uniquely identifies a single VPLS.
Entries in this table may be created or deleted All of the read-create objects can be changed when
through SNMP, as side-effects of console or other vplsBGPADConfigRowStatus is in active(1) state."
non-SNMP management commands, or upon learning via
autodiscovery.
All of the read-create objects can be changed when INDEX { vplsConfigIndex }
vplsBGPADConfigRowStatus is in active(1) state." ::= { vplsBgpADConfigTable 1 }
VPLS Management Information Base Feb, 2014
INDEX { vplsConfigIndex } VplsBgpADConfigEntry ::=
::= { vplsBgpADConfigTable 1 } SEQUENCE {
vplsBgpADConfigRouteDistinguisher VplsBgpRouteDistinguisher,
vplsBgpADConfigPrefix Unsigned32,
vplsBgpADConfigVplsId VplsBgpRouteDistinguisher,
vplsBgpADConfigRowStatus RowStatus,
vplsBgpADConfigStorageType StorageType
}
VplsBgpADConfigEntry ::= vplsBgpADConfigRouteDistinguisher OBJECT-TYPE
SEQUENCE { SYNTAX VplsBgpRouteDistinguisher
vplsBgpADConfigRouteDistinguisher VplsBgpRouteDistinguisher, MAX-ACCESS read-create
vplsBgpADConfigPrefix Unsigned32, STATUS current
vplsBgpADConfigVplsId VplsBgpRouteDistinguisher, DESCRIPTION
vplsBgpADConfigRowStatus RowStatus, "The route distinguisher for this VPLS. See RFC 4364
vplsBgpADConfigStorageType StorageType for a complete definition of a route distinguisher.
} For more details on use of a route distinguisher
for a VPLS service, see RFC 4761. When not configured, the
value is derived from the lower 6 bytes of
vplsBgpADConfigVplsId.
"
::= { vplsBgpADConfigEntry 1 }
vplsBgpADConfigRouteDistinguisher OBJECT-TYPE vplsBgpADConfigPrefix OBJECT-TYPE
SYNTAX VplsBgpRouteDistinguisher SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The route distinguisher for this VPLS. See RFC4364 "In case of auto-discovery, the default prefix advertised
for a complete definition of a route distinguisher. is the IP address of the loopback. In case the user wants
for more details on use of a route distinguisher to override the loopback address, vplsBgpADConfigPrefix
for a VPLS service, see RFC4761. When not configured, the should be set. When this value is non-zero, this value is
value is derived from the lower 6 bytes of used along with vplsBgpADConfigRouteDistinguisher in the
vplsBgpADConfigVplsId. Network Layer Reachability Information (NLRI), see RFC 6074.
" "
::= { vplsBgpADConfigEntry 1 } DEFVAL { 0 }
::= { vplsBgpADConfigEntry 2 }
vplsBgpADConfigPrefix OBJECT-TYPE vplsBgpADConfigVplsId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX VplsBgpRouteDistinguisher
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" In case of auto-discovery the default prefix advertised "VplsId is a unique identifier for all Virtual Switch
is the IP address of the loopback. In case the user wants Instances (VSIs) belonging to the same VPLS. It is
to override the loopback address, vplsBgpADConfigPrefix advertised as an extended community.
should be set. When this value is non-zero this value is "
used along with vplsBgpADConfigRouteDistinguisher in the ::= { vplsBgpADConfigEntry 3 }
NLRI, see RFC6074
"
DEFVAL { 0 }
::= { vplsBgpADConfigEntry 2 }
vplsBgpADConfigVplsId OBJECT-TYPE vplsBgpADConfigRowStatus OBJECT-TYPE
SYNTAX VplsBgpRouteDistinguisher SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" VplsId is a unique identifier for all VSIs belonging to "For creating, modifying, and deleting this row.
VPLS Management Information Base Feb, 2014
the same VPLS. It is advertised as an extended community. All other objects in this row must be set to valid
" values before this object can be set to active(1).
::= { vplsBgpADConfigEntry 3 }
vplsBgpADConfigRowStatus OBJECT-TYPE None of the read-create objects in the
SYNTAX RowStatus conceptual rows may be changed when this
MAX-ACCESS read-create object is in the active(1) state."
STATUS current ::= { vplsBgpADConfigEntry 4 }
DESCRIPTION
"For creating, modifying, and deleting this row.
All other objects in this row must be set to valid vplsBgpADConfigStorageType OBJECT-TYPE
values before this object can be set to active(1). SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this row."
DEFVAL { nonVolatile }
::= { vplsBgpADConfigEntry 5 }
None of the read-create objects in the -- vplsBgpRteTargetTable
conceptual rows may be changed when this
object is in the active(1) state."
::= { vplsBgpADConfigEntry 4 }
vplsBgpADConfigStorageType OBJECT-TYPE vplsBgpRteTargetTable OBJECT-TYPE
SYNTAX StorageType SYNTAX SEQUENCE OF VplsBgpRteTargetEntry
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this row." "This table specifies the list of Route Targets
DEFVAL { nonVolatile } imported or exported by BGP during
::= { vplsBgpADConfigEntry 5 } auto-discovery of VPLS.
"
-- vplsBgpRteTargetTable ::= { vplsObjects 6 }
vplsBgpRteTargetTable OBJECT-TYPE vplsBgpRteTargetEntry OBJECT-TYPE
SYNTAX SEQUENCE OF VplsBgpRteTargetEntry SYNTAX VplsBgpRteTargetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This table specifies the list of Route Targets "An entry in this table specifies the value of the
imported or exported by BGP during Route Target being used by BGP. Depending on the value
auto-discovery of VPLS. of vplsBgpRteTargetType, a Route Target might be
" exported, imported, or both. Every VPLS that
::= { vplsObjects 6 } uses auto-discovery for finding peer nodes can
import and export multiple Route Targets. This
representation allows support for hierarchical VPLS.
vplsBgpRteTargetEntry OBJECT-TYPE Entries in this table may be created or deleted
SYNTAX VplsBgpRteTargetEntry through SNMP, as side effects of console or other
MAX-ACCESS not-accessible non-SNMP management commands, or upon learning via
STATUS current autodiscovery.
DESCRIPTION
"An entry in this table specifies the value of the
Route Target being used by BGP. Depending on the value
of vplsBgpRteTargetType a Route Target might be
VPLS Management Information Base Feb, 2014
exported or imported or both. Every VPLS which It is optional for the agent to allow entries to be
uses auto-discovery for finding peer nodes can created that point to nonexistent entries in
import and export multiple Route Targets. This vplsConfigTable."
representation allows support for hierarchical VPLS. INDEX { vplsConfigIndex, vplsBgpRteTargetIndex }
::= { vplsBgpRteTargetTable 1 }
Entries in this table may be created or deleted VplsBgpRteTargetEntry ::=
through SNMP, as side-effects of console or other SEQUENCE {
non-SNMP management commands, or upon learning via vplsBgpRteTargetIndex Unsigned32,
autodiscovery. vplsBgpRteTargetRTType VplsBgpRouteTargetType,
vplsBgpRteTargetRT VplsBgpRouteTarget,
vplsBgpRteTargetRowStatus RowStatus,
vplsBgpRteTargetStorageType StorageType
}
It is optional for the agent to allow entries to be vplsBgpRteTargetIndex OBJECT-TYPE
created that point to non-existent entries in SYNTAX Unsigned32
vplsConfigTable." MAX-ACCESS not-accessible
INDEX { vplsConfigIndex, vplsBgpRteTargetIndex } STATUS current
::= { vplsBgpRteTargetTable 1 } DESCRIPTION
"This index, along with vplsConfigIndex, identifies one
entry in the vplsBgpRteTargetTable. By keeping
vplsConfigIndex constant and using a new value of
vplsBgpRteTargetIndex, users can configure multiple
Route Targets for the same VPLS.
"
::= { vplsBgpRteTargetEntry 1 }
VplsBgpRteTargetEntry ::= vplsBgpRteTargetRTType OBJECT-TYPE
SEQUENCE { SYNTAX VplsBgpRouteTargetType
vplsBgpRteTargetIndex Unsigned32, MAX-ACCESS read-create
vplsBgpRteTargetRTType VplsBgpRouteTargetType, STATUS current
vplsBgpRteTargetRT VplsBgpRouteTarget, DESCRIPTION
vplsBgpRteTargetRowStatus RowStatus, "Used to define the type of a Route Target usage.
vplsBgpRteTargetStorageType StorageType Route Targets can be specified to be imported,
} exported, or both. For a complete definition of a
Route Target, see RFC 4364."
vplsBgpRteTargetIndex OBJECT-TYPE ::= { vplsBgpRteTargetEntry 2 }
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This index along with vplsConfigIndex, identifies one
entry in the vplsBgpRteTargetTable. By keeping
vplsConfigIndex constant and using new value of
vplsBgpRteTargetIndex users can configure multiple
Route Targets for the same VPLS.
"
::= { vplsBgpRteTargetEntry 1 }
vplsBgpRteTargetRTType OBJECT-TYPE vplsBgpRteTargetRT OBJECT-TYPE
SYNTAX VplsBgpRouteTargetType SYNTAX VplsBgpRouteTarget
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Used to define the type of a route target usage. "The Route Target associated with the VPLS service.
Route targets can be specified to be imported, For more details on use of Route Targets
exported, or both. For a complete definition of a for a VPLS service, see RFC 4761.
route target, see RFC4364." "
::= { vplsBgpRteTargetEntry 2 } ::= { vplsBgpRteTargetEntry 3 }
VPLS Management Information Base Feb, 2014
vplsBgpRteTargetRT OBJECT-TYPE vplsBgpRteTargetRowStatus OBJECT-TYPE
SYNTAX VplsBgpRouteTarget SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The route target associated with the VPLS service. "This variable is used to create, modify, and/or
For more details on use of route targets delete a row in this table.
for a VPLS service, see RFC4761.
"
::= { vplsBgpRteTargetEntry 3 }
vplsBgpRteTargetRowStatus OBJECT-TYPE All other objects in this row must be set to valid
SYNTAX RowStatus values before this object can be set to active(1).
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table.
All other objects in this row must be set to valid When a row in this table is in active(1) state, no
values before this object can be set to active(1). objects in that row can be modified.
When a row in this table is in active(1) state, no If autodiscovered entries are deleted they would
objects in that row can be modified. likely re-appear in the next autodiscovery interval."
::= { vplsBgpRteTargetEntry 4 }
If autodiscovered entries are deleted they would vplsBgpRteTargetStorageType OBJECT-TYPE
likely re-appear in the next autodiscovery interval." SYNTAX StorageType
::= { vplsBgpRteTargetEntry 4 } MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this row."
DEFVAL { volatile }
::= { vplsBgpRteTargetEntry 5 }
vplsBgpRteTargetStorageType OBJECT-TYPE vplsStatusNotifEnable OBJECT-TYPE
SYNTAX StorageType SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this row." "If this object is set to true(1), then it enables
DEFVAL { volatile } the emission of a vplsStatusChanged
::= { vplsBgpRteTargetEntry 5 } notification; otherwise, this notification is not
emitted."
vplsStatusNotifEnable OBJECT-TYPE REFERENCE
SYNTAX TruthValue "See also RFC 3413 for explanation that
MAX-ACCESS read-write notifications are under the ultimate control of the
STATUS current MIB module in this document."
DESCRIPTION DEFVAL { false }
"If this object is set to true(1), then it enables ::= { vplsObjects 7 }
the emission of vplsStatusChanged
notification, otherwise this notification is not
VPLS Management Information Base Feb, 2014
emitted."
REFERENCE
"See also RFC3413 for explanation that
notifications are under the ultimate control of the
MIB module in this document."
DEFVAL { false }
::= { vplsObjects 7 }
vplsNotificationMaxRate OBJECT-TYPE vplsNotificationMaxRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum number of "This object indicates the maximum number of
notifications issued per second. If events occur notifications issued per second. If events occur
more rapidly, the implementation may simply fail to more rapidly, the implementation may simply fail to
emit these notifications during that period, or may emit these notifications during that period, or it 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 }
-- VPLS Service Notifications -- VPLS Service Notifications
vplsStatusChanged NOTIFICATION-TYPE vplsStatusChanged NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vplsConfigVpnId, vplsConfigVpnId,
vplsConfigAdminStatus, vplsConfigAdminStatus,
vplsStatusOperStatus vplsStatusOperStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vplsStatusChanged notification is generated "The vplsStatusChanged notification is generated
when there is a change in the administrative or when there is a change in the administrative or
operating status of a VPLS service. operating status of a VPLS service.
The object instances included in the notification The object instances included in the notification
are the ones associated with the VPLS service are the ones associated with the VPLS service
whose 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 Feb, 2014 DESCRIPTION
"The vplsFwdFullAlarmRaised notification is
generated when the utilization of the Forwarding
database is above the value specified by
vplsConfigFwdFullHighWatermark.
DESCRIPTION The object instances included in the notification
"The vplsFwdFullAlarmRaised notification is are the ones associated with the VPLS service
generated when the utilization of the Forwarding that has exceeded the threshold."
database is above the value specified by ::= { vplsNotifications 2 }
vplsConfigFwdFullHighWatermark.
The object instances included in the notification
are the ones associated with the VPLS service
which has exceeded the threshold."
::= { 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 The object instances included in the notification
are the ones associated with the VPLS service are the ones associated with the VPLS service
which has fallen below the threshold." that 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
DESCRIPTION DESCRIPTION
skipping to change at page 25, line 53 skipping to change at page 26, line 4
"Compliance requirement for implementations that "Compliance requirement for implementations that
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 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 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
"Write access is not required." "Write access is not required."
skipping to change at page 27, line 50 skipping to change at page 27, line 48
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."
::= { vplsCompliances 2 } ::= { vplsCompliances 2 }
-- Units of conformance.
vplsGroups
OBJECT IDENTIFIER ::= { vplsConformance 2 }
VPLS Management Information Base Feb, 2014
vplsGroup OBJECT-GROUP vplsGroups
OBJECTS { OBJECT IDENTIFIER ::= { vplsConformance 2 }
vplsConfigName,
vplsBgpADConfigRouteDistinguisher,
vplsBgpRteTargetRTType,
vplsBgpRteTargetRT,
vplsBgpRteTargetRowStatus,
vplsBgpRteTargetStorageType,
vplsBgpADConfigPrefix,
vplsBgpADConfigVplsId,
vplsBgpADConfigRowStatus,
vplsBgpADConfigStorageType,
vplsConfigDescr,
vplsConfigAdminStatus,
vplsConfigMacLearning,
vplsConfigDiscardUnknownDest,
vplsConfigMacAging,
vplsConfigVpnId,
vplsConfigFwdFullHighWatermark,
vplsConfigFwdFullLowWatermark,
vplsConfigRowStatus,
vplsConfigIndexNext,
vplsConfigMtu,
vplsConfigStorageType,
vplsConfigSignalingType,
vplsStatusOperStatus,
vplsStatusPeerCount,
vplsStatusNotifEnable,
vplsNotificationMaxRate
}
STATUS current
DESCRIPTION
"The group of objects supporting
management of L2VPN VPLS services"
::= { vplsGroups 1 }
vplsPwBindGroup OBJECT-GROUP vplsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
vplsPwBindConfigType, vplsConfigName,
vplsPwBindType, vplsBgpADConfigRouteDistinguisher,
vplsPwBindRowStatus, vplsBgpRteTargetRTType,
vplsPwBindStorageType vplsBgpRteTargetRT,
} vplsBgpRteTargetRowStatus,
STATUS current vplsBgpRteTargetStorageType,
DESCRIPTION vplsBgpADConfigPrefix,
"The group of objects supporting vplsBgpADConfigVplsId,
management of vplsBgpADConfigRowStatus,
vplsBgpADConfigStorageType,
vplsConfigDescr,
vplsConfigAdminStatus,
vplsConfigMacLearning,
vplsConfigDiscardUnknownDest,
vplsConfigMacAging,
vplsConfigVpnId,
vplsConfigFwdFullHighWatermark,
vplsConfigFwdFullLowWatermark,
vplsConfigRowStatus,
vplsConfigIndexNext,
vplsConfigMtu,
vplsConfigStorageType,
vplsConfigSignalingType,
vplsStatusOperStatus,
vplsStatusPeerCount,
vplsStatusNotifEnable,
vplsNotificationMaxRate
}
STATUS current
DESCRIPTION
"The group of objects supporting
management of L2VPN VPLS services"
::= { vplsGroups 1 }
VPLS Management Information Base Feb, 2014 vplsPwBindGroup OBJECT-GROUP
OBJECTS {
vplsPwBindConfigType,
vplsPwBindType,
vplsPwBindRowStatus,
vplsPwBindStorageType
}
STATUS current
DESCRIPTION
"The group of objects supporting
management of
pseudowire (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
} }
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-MIB Object definitions 6.2. VPLS-LDP-MIB Object Definitions
This MIB module makes references to the following documents. This MIB module mentions the following documents:
[RFC2578], [RFC2579], [RFC2580], [RFC3411], [RFC2578], [RFC2579], [RFC2580], [RFC5601], and [RFC4762].
[RFC2863], [RFC4265] and [RFC3813].
VPLS-LDP-MIB DEFINITIONS ::= BEGIN VPLS-LDP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32, transmission
FROM SNMPv2-SMI -- RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
FROM SNMPv2-CONF -- RFC2580 Unsigned32, transmission
FROM SNMPv2-SMI -- RFC 2578
TruthValue MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-CONF -- RFC 2580
pwIndex, pwID
FROM PW-STD-MIB
vplsConfigIndex, vplsConfigName TruthValue
FROM VPLS-GENERIC-MIB; FROM SNMPv2-TC -- RFC 2579
vplsLdpDraft01MIB MODULE-IDENTITY pwIndex, pwID
-- RFC Editor: Please replace vplsLdpDraft01MIB with FROM PW-STD-MIB -- RFC 5601
-- vplsLdpMIB throughout the MIB and remove
-- this note.
VPLS Management Information Base Feb, 2014 vplsConfigIndex, vplsConfigName
FROM VPLS-GENERIC-MIB;
LAST-UPDATED "201401301200Z" -- 30 Jan 2014 12:00:00 GMT vplsLdpMIB MODULE-IDENTITY
LAST-UPDATED "201405191200Z" -- 19 May 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: romedira@cisco.com
The L2VPN Working Group The L2VPN Working Group
(email distribution l2vpn@ietf.org, (email distribution l2vpn@ietf.org,
http://www.ietf.org/html.charters/l2vpn-charter.html) http://www.ietf.org/wg/l2vpn/charter/)
" "
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2014). The initial "Copyright (c) 2014 IETF Trust and the persons
version of this MIB module was published in RFC XXXX. identified as authors of the code. All rights reserved.
-- RFC Editor: Please replace XXXX with RFC number & remove Redistribution and use in source and binary forms, with
-- this note. or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
For full legal notices see the RFC itself or see: The initial version of this MIB module was published in
http://www.ietf.org/copyrights/ianamib.html RFC 7257; for full legal notices see the RFC itself.
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 RFC 4762.
This MIB module enables the use of any This MIB module enables the use of any
underlying pseudowire network. " underlying pseudowire network."
-- Revision history. -- Revision history.
REVISION REVISION
"201401230200Z" -- 30 Jan 2014 12:00:00 GMT "201405191200Z" -- 19 May 2014 12:00:00 GMT
DESCRIPTION "Initial version published as part of RFC YYYY."
-- RFC Editor: please replace YYYY with IANA assigned value, and
-- delete this note.
::= { transmission BBB } DESCRIPTION "Initial version published as part of RFC 7257."
-- RFC Editor: please replace BBB with IANA assigned value, and ::= { transmission 275 }
-- delete this note.
-- Top-level components of this MIB. -- Top-level components of this MIB.
-- Notifications -- Notifications
VPLS Management Information Base Feb, 2014
vplsLdpNotifications OBJECT IDENTIFIER vplsLdpNotifications OBJECT IDENTIFIER
::= { vplsLdpDraft01MIB 0 } ::= { vplsLdpMIB 0 }
-- Tables, Scalars -- Tables, Scalars
vplsLdpObjects OBJECT IDENTIFIER vplsLdpObjects OBJECT IDENTIFIER
::= { vplsLdpDraft01MIB 1 } ::= { vplsLdpMIB 1 }
-- Conformance -- Conformance
vplsLdpConformance OBJECT IDENTIFIER vplsLdpConformance OBJECT IDENTIFIER
::= { vplsLdpDraft01MIB 2 } ::= { vplsLdpMIB 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 Service (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 for Virtual Private LAN Service (VPLS) in a packet
network. 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 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 is enabled in this service. If this object is 'true',
then 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
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 pseudowires. A service can have more corresponding pseudowires. A service can have more
than one pseudowire association. Pseudowires 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 pseudowires 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
to many association of service to pseudowire. one-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 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 "The value of this object specifies the maximum
number 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,
pwID pwID
} }
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 }
-- Conformance Section -- Conformance Section
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 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 34, line 48 skipping to change at page 34, line 31
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsLdpPwBindMacAddressLimit OBJECT vplsLdpPwBindMacAddressLimit
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { vplsLdpCompliances 2 } ::= { vplsLdpCompliances 2 }
-- Units of conformance.
vplsLdpGroups vplsLdpGroups
OBJECT IDENTIFIER ::= { vplsLdpConformance 2 } OBJECT IDENTIFIER ::= { vplsLdpConformance 2 }
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."
::= { vplsLdpGroups 1 } ::= { vplsLdpGroups 1 }
vplsLdpNotificationGroup NOTIFICATION-GROUP vplsLdpNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
vplsLdpPwBindMacTableFull vplsLdpPwBindMacTableFull
} }
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-MIB Object definitions 6.3. VPLS-BGP-MIB Object Definitions
VPLS-BGP-MIB DEFINITIONS ::= BEGIN This MIB module mentions the following documents:
[RFC2578], [RFC2579], [RFC2580], [RFC3411],
[RFC5601], and [RFC4761].
IMPORTS VPLS-BGP-MIB DEFINITIONS ::= BEGIN
MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, transmission
FROM SNMPv2-SMI -- RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP IMPORTS
FROM SNMPv2-CONF -- RFC2580
RowStatus, StorageType MODULE-IDENTITY, OBJECT-TYPE,
FROM SNMPv2-TC -- RFC2579 Unsigned32, transmission
FROM SNMPv2-SMI -- RFC 2578
SnmpAdminString MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMP-FRAMEWORK-MIB -- RFC3411 FROM SNMPv2-CONF -- RFC 2580
pwIndex RowStatus, StorageType
FROM PW-STD-MIB -- RFC5601 FROM SNMPv2-TC -- RFC 2579
vplsConfigIndex SnmpAdminString
VPLS Management Information Base Feb, 2014 FROM SNMP-FRAMEWORK-MIB -- RFC 3411
FROM VPLS-GENERIC-MIB pwIndex
; FROM PW-STD-MIB -- RFC 5601
vplsConfigIndex
FROM VPLS-GENERIC-MIB
;
vplsBgpMIB MODULE-IDENTITY
LAST-UPDATED "201405191200Z" -- 19 May 2014 12:00:00 GMT
vplsBgpDraft01MIB MODULE-IDENTITY
-- RFC Editor: Please replace vplsBgpDraft01MIB with
-- vplsBgpMIB throughout the MIB and remove
-- this note.
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
" "
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/wg/l2vpn/charter/)
" "
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2014). The initial "Copyright (c) 2014 IETF Trust and the persons
version of this MIB module was published in RFC XXXX. identified as authors of the code. All rights reserved.
-- RFC Editor: Please replace XXXX with RFC number & remove
-- this note.
For full legal notices see the RFC itself or see: Redistribution and use in source and binary forms, with
http://www.ietf.org/copyrights/ianamib.html or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
The initial version of this MIB module was published in
RFC 7257; for full legal notices see the RFC itself.
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 Service as in
RFC4761 RFC 4761.
This MIB module enables the use of any underlying This MIB module enables the use of any underlying
pseudowire network. " pseudowire network."
-- Revision history. -- Revision history.
REVISION REVISION
"201401301200Z" -- 30 Jan 2014 12:00:00 GMT "201405191200Z" -- 19 May 2014 12:00:00 GMT
DESCRIPTION "Initial version published as part of RFC YYYY."
-- RFC Editor: please replace YYYY with IANA assigned value, and
-- delete this note.
::= { transmission CCC }
-- RFC Editor: please replace CCC with IANA assigned value, and
-- delete this note.
-- Top-level components of this MIB. DESCRIPTION "Initial version published as part of RFC 7257."
::= { transmission 276 }
VPLS Management Information Base Feb, 2014 -- Top-level components of this MIB.
-- Tables, Scalars -- Tables, Scalars
vplsBgpObjects OBJECT IDENTIFIER vplsBgpObjects OBJECT IDENTIFIER
::= { vplsBgpDraft01MIB 1 } ::= { vplsBgpMIB 1 }
-- Conformance -- Conformance
vplsBgpConformance OBJECT IDENTIFIER vplsBgpConformance OBJECT IDENTIFIER
::= { vplsBgpDraft01MIB 2 } ::= { vplsBgpMIB 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 Service (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 for Virtual Private LAN Service (VPLS) in a packet
network. 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 object 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 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 ID in this "Specifies the size of the range of VPLS Edge
VPLS service. This number controls the size of the Identifier (VE ID) in this VPLS service. This
label block advertised for this VE by the PE. number controls the size of the label block
A value of 0 indicates that the range is not advertised for this VE by the PE. A value of 0
configured and the PE derives the range value indicates that the range is not configured and
from received advertisements from other PEs. the PE derives the range value from received
advertisements from other PEs.
The VE ID takes 2 octets in VPLS BGP NLRI according The VE ID takes 2 octets in VPLS BGP NLRI according
to RFC 4761. Hence we have limited the the range of to RFC 4761. Hence we have limited the range of
this object to 65535." 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
"This table associates VPLS Edge devices to a VPLS service" "This table associates VPLS Edge devices to a VPLS service"
::= { vplsBgpObjects 2 } ::= { vplsBgpObjects 2 }
vplsBgpVEEntry OBJECT-TYPE vplsBgpVEEntry OBJECT-TYPE
SYNTAX VplsBgpVEEntry SYNTAX VplsBgpVEEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created for each VE Id "An entry in this table is created for each VE ID
configured on a PE for a particular VPLS service configured on a PE for a particular VPLS service
instance. instance.
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 nonexistent entries in
vplsConfigTable." vplsConfigTable."
INDEX { vplsConfigIndex, vplsBgpVEId } INDEX { vplsConfigIndex, vplsBgpVEId }
::= { vplsBgpVETable 1 } ::= { vplsBgpVETable 1 }
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
skipping to change at page 39, line 21 skipping to change at page 39, line 4
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 The VE ID takes 2 octets in VPLS BGP NLRI according
to RFC 4761. Hence we have limited the the range of to RFC 4761. Hence, we have limited the range of
this object to 65535." 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 user-facing PE
this VE Id." (U-PE) associated with 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
if the site is multi-homed and VE Id is re-used." Provider Edge (PE) if the site is multihomed
and VE ID is reused."
DEFVAL { 0 } DEFVAL { 0 }
::= { vplsBgpVEEntry 3 } ::= { vplsBgpVEEntry 3 }
vplsBgpVERowStatus OBJECT-TYPE vplsBgpVERowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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 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
skipping to change at page 40, line 29 skipping to change at page 40, line 15
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 pseudowires. A service can have more corresponding pseudowires. A service can have more
than one pseudowire association. Pseudowires 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 Pseudowires 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 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 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 with which this pseudowire
is associated with. is associated.
The VE ID takes 2 octets in VPLS BGP NLRI according The VE ID takes 2 octets in VPLS BGP NLRI according
to RFC 4761. Hence we have limited the the range of to RFC 4761. Hence, we have limited the range of
this object to 65535." 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 with which this pseudowire
is associated with. is associated.
The VE ID takes 2 octets in VPLS BGP NLRI according The VE ID takes 2 octets in VPLS BGP NLRI according
to RFC 4761. Hence we have limited the the range of to RFC 4761. Hence, we have limited the range of
this object to 65535." 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 }
skipping to change at page 41, line 47 skipping to change at page 41, line 38
-- 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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations that "Compliance requirement for implementations that
provide full support for VPLS-BGP-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
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
provide read-only support for VPLS-BGP-MIB. provide read-only support for VPLS-BGP-MIB.
skipping to change at page 42, line 50 skipping to change at page 42, line 43
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT vplsBgpVERowStatus OBJECT vplsBgpVERowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { vplsBgpCompliances 2 } ::= { vplsBgpCompliances 2 }
-- Units of conformance.
vplsBgpGroups vplsBgpGroups
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
of L2VPN VPLS services using BGP" of L2VPN VPLS services using BGP."
::= { vplsBgpGroups 1 } ::= { vplsBgpGroups 1 }
vplsBgpVEGroup OBJECT-GROUP vplsBgpVEGroup OBJECT-GROUP
OBJECTS { OBJECTS {
vplsBgpVEName, vplsBgpVEName,
vplsBgpVEPreference, vplsBgpVEPreference,
vplsBgpVERowStatus, vplsBgpVERowStatus,
vplsBgpVEStorageType vplsBgpVEStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects supporting management of VPLS "The group of objects supporting management of VPLS
Edge devices for L2VPN VPLS services using BGP" Edge devices for L2VPN VPLS services using BGP."
::= { vplsBgpGroups 2 } ::= { vplsBgpGroups 2 }
vplsBgpPwBindGroup OBJECT-GROUP vplsBgpPwBindGroup OBJECT-GROUP
OBJECTS { OBJECTS {
vplsBgpPwBindLocalVEId, vplsBgpPwBindLocalVEId,
vplsBgpPwBindRemoteVEId vplsBgpPwBindRemoteVEId
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects supporting management of "The group of objects supporting management of
Pseudo Wires for L2VPN VPLS services using BGP" pseudowires for L2VPN VPLS services using BGP."
::= { vplsBgpGroups 3 } ::= { vplsBgpGroups 3 }
END END
7. Security Considerations 7. Security Considerations
There are a number of management objects defined in this MIB There are a number of management objects defined in this MIB module
module with a MAX-ACCESS clause of read-write and/or read-create. with a MAX-ACCESS clause of read-write and/or read-create. Such
Such objects may be considered sensitive or vulnerable in some objects may be considered sensitive or vulnerable in some network
network environments.The support for SET operations in a environments. The support for SET operations in a non-secure
non-secure environment without proper protection can have a environment without proper protection can have a negative effect on
negative effect on network operations. These are the tables network operations. These are the tables and their
and their sensitivity/vulnerability: sensitivity/vulnerability:
VPLS Management Information Base Feb, 2014 o vplsConfigTable:
o vplsConfigTable: o vplsPwBindTable:
o vplsPwBindTable: o vplsBgpADConfigTable:
o vplsBgpADConfigTable: o vplsBgpRteTargetTable:
o vplsBgpRteTargetTable: o vplsLdpPwBindTable:
o vplsLdpPwBindTable: o vplsLdpConfigTable:
o vplsLdpConfigTable: o vplsBgpConfigTable:
o vplsBgpConfigTable: o vplsBgpVETable:
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.
o vplsNotificationMaxRate The tables listed above contain read-create/read-write objects
Setting of a very high value to this object can cause a that can be used to configure or modify a LDP/BGP VPLS service.
notification storm which may disrupt network service. Any improper configuration or modification of objects in these
tables can disrupt VPLS services.
Most of the readable objects in this MIB module (i.e., objects The use of stronger mechanisms such as SNMPv3 security should be
with a MAX-ACCESS other than not-accessible) may be considered considered where possible for configuring these objects.
sensitive or vulnerable in some network environments.It is Specifically, SNMPv3 View-based Access Control Model (VACM) and
thus important to control even GET and/or NOTIFY access to these User-based Security Model (USM) MUST be used with any v3 agent
objects and possibly to even encrypt the values of these objects that provides SET access to these tables.
when sending them over the network via SNMP.
o vplsNotificationMaxRate
Setting this object to a very high value can cause a notification
storm that may disrupt network service.
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. These readable objects are contained in the
following tables:
o vplsConfigTable
o vplsStatusTable
o vplsPwBindTable
o vplsBgpADConfigTable
o vplsBgpRteTargetTable
o vplsLdpPwBindTable
o vplsLdpConfigTable
o vplsBgpConfigTable
o vplsBgpVETable
o vplsBgpPwBindTable
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using Even if the network itself is secure (for example by using IPsec),
IPsec), there is no control as to who on the secure network there is no control as to who on the secure network is allowed to
is allowed to access and GET/SET (read/change/create/delete) access and GET/SET (read/change/create/delete) the objects in this
the objects in this MIB module. MIB module.
Implementations SHOULD provide the security features described Implementations SHOULD provide the security features described by the
by the SNMPv3 framework (see [RFC3410]), and implementations SNMPv3 framework (see [RFC3410]), and implementations claiming
claiming compliance to the SNMPv3 standard MUST include full compliance to the SNMPv3 standard MUST include full support for
support for authentication and privacy via the User-based Security authentication and privacy via the User-based Security Model (USM)
Model (USM) [RFC3414] with the AES cipher algorithm [RFC3826]. [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
Implementations MAY also provide support for the Transport Security MAY also provide support for the Transport Security Model (TSM)
Model (TSM) [RFC5591] in combination with a secure transport such [RFC5591] in combination with a secure transport such as SSH
as SSH [RFC5592] or TLS/DTLS [RFC6353]. [RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access instance of this MIB module is properly configured to give access to
to the objects only to those principals (users) that have the objects only to those principals (users) that have legitimate
legitimate rights to indeed GET or SET (change/create/delete) them. 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 use the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry.
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 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. The IANA has assigned { transmission 274 } to the VPLS-GENERIC-MIB
module specified in this document.
8.2. IANA Considerations for VPLS-LDP-MIB 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. The IANA has assigned { transmission 275 } to the VPLS-LDP-MIB module
specified in this document.
8.3. IANA Considerations for VPLS-BGP-MIB 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.
9. References The IANA has assigned { transmission 276 } to the VPLS-BGP-MIB module
specified in this document.
9.1. Normative References 9. References
[RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate 9.1. Normative References
Requirement Levels", RFC 2119, BCP 14, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
J., Rose, M., and S. Waldbusser, "Structure of Requirement Levels", BCP 14, RFC 2119, March 1997.
Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
J., Rose, M., and S. Waldbusser, "Textual Conventions Schoenwaelder, Ed., "Structure of Management Information
for SMIv2", STD 58, RFC 2579, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
J., Rose, M., and S. Waldbusser, "Conformance Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
Statements for SMIv2", STD 58, RFC 2580, April 1999. 58, RFC 2579, April 1999.
VPLS Management Information Base Feb, 2014 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Conformance Statements for SMIv2",
STD 58, RFC 2580, April 1999.
[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- [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
based Access Control Model (VACM) for the Simple (USM) for version 3 of the Simple Network Management
Network Management Protocol (SNMP)", STD 62, RFC Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
3415, December 2002.
[RFC4188] Norseth, K., and Bell, E., "Definitions of Managed [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Objects for Bridges", RFC 4188, Sept 2006. Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", STD 62, RFC 3415, December
2002.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, June 2004.
[RFC4188] Norseth, K., Ed., and E. Bell, Ed., "Definitions of
Managed Objects for Bridges", RFC 4188, September 2005.
[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",
Management", RFC 4265, November 2005. RFC 4265, November 2005.
[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., Ed., and Y. Rekhter, Ed., "Virtual Private
(VPLS) Using BGP for Auto-Discovery and Signaling",RFC LAN Service (VPLS) Using BGP for Auto-Discovery and
4761, January 2007. Signaling", RFC 4761, January 2007.
[RFC4762] Lasserre, M. and Kompella, V. (Editors), "Virtual Private
LAN Service (VPLS) Using Label Distribution Protocol (LDP)
Signaling", RFC 4762, January 2007.
[RFC5601] T. Nadeau, Ed., D. Zelig, Ed., "Pseudowire (PW)
Management Information Base (MIB)", RFC 5601, July 2009.
9.2. Informative References
[RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group
MIB", RFC 2863, June 2000.
VPLS Management Information Base Feb, 2014
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC4762] Lasserre, M., Ed., and V. Kompella, Ed., "Virtual Private
"Introduction and Applicability Statements for LAN Service (VPLS) Using Label Distribution Protocol (LDP)
Internet-Standard Management Framework", RFC 3410, Signaling", RFC 4762, January 2007.
December 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
Architecture for Describing Simple Network Management for the Simple Network Management Protocol (SNMP)", STD
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 78, RFC 5591, June 2009.
December 2002.
[RFC3813] Srinivasan, C., Viswanathan, A. and Nadeau, T., [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
"Multiprotocol Label Switching (MPLS) Label Switching Shell Transport Model for the Simple Network Management
Router (LSR) Management Information Base", Protocol (SNMP)", RFC 5592, June 2009.
RFC 3813, June 2004
[SNMP-CONTEXT-MAP-MIB] SNMP Context Mapping MIB, AS, Kiran Koushik, [RFC5601] Nadeau, T., Ed., and D. Zelig, Ed., "Pseudowire (PW)
Nadeau, T, draft-kkoushik-snmp-context-map-mib. Management Information Base (MIB)", RFC 5601, July 2009.
[RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Edge (PWE3) Architecture", RFC 3985, March 2005. Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, July 2011.
[RFC6074] E. Rosen et. al., "Provisioning, Autodiscovery, and 9.2. Informative References
Signaling in L2VPNs", RFC 6074, January 2011.
10. Acknowledgments [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
We wish to thank Marcelo Mourier and Reva Bailey for their [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
valuable feedback. Some portion of the work has been referenced Architecture for Describing Simple Network Management
from their original Timetra Enterprise MIB work. Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002.
We wish to thank Praveen Muley, VJ Shah, Li Wentao, Kong Yong, Luo [RFC3985] Bryant, S., Ed., and P. Pate, Ed., "Pseudo Wire Emulation
Jian, Feng Jun, Takeshi Usui for their feedback. Edge-to-Edge (PWE3) Architecture", RFC 3985, March 2005.
11. Authors' Addresses [RFC6074] Rosen, E., Davie, B., Radoaca, V., and W. Luo,
"Provisioning, Auto-Discovery, and Signaling in Layer 2
Virtual Private Networks (L2VPNs)", RFC 6074, January
2011.
Thomas D. Nadeau [SNMP-CONTEXT-MAP-MIB]
Lucid Vision Nadeau, T., and AS Kiran Koushik, "SNMP Context Mapping
Email: tnadeau@lucidvision.com MIB", Work in Progress, March 2010.
A S Kiran Koushik 10. Acknowledgments
Cisco Systems Inc.
12515 Research Blvd, Bldg 4,
Austin, TX 78759
Email: kkoushik@cisco.com
Rohit Mediratta We wish to thank Marcelo Mourier and Reva Bailey for their valuable
Alcatel-Lucent, feedback. Some portion of the work has been referenced from their
701 E Middlefield Rd. original Timetra Enterprise MIB work.
Mountain View, CA 94040
Email: rohit.mediratta@alcatel-lucent.com
VPLS Management Information Base Feb, 2014
12. Full Copyright Statement We wish to thank Praveen Muley, VJ Shah, Li Wentao, Kong Yong, Luo
Jian, Feng Jun, and Takeshi Usui for their feedback.
Copyright (c) 2014 IETF Trust and the persons identified as the Authors' Addresses
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Thomas D. Nadeau (editor)
Provisions Relating to IETF Documents Lucid Vision
(http://trustee.ietf.org/license-info) in effect on the date of US
publication of this document. Please review these documents EMail: tnadeau@lucidvision.com
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF A S Kiran Koushik (editor)
Contributions published or made publicly available before November Brocade Communications Systems, Inc.
10, 2008. The person(s) controlling the copyright in some of this 130 Holger Way
San Jose, CA 95134
US
EMail: kkoushik@brocade.com
material may not have granted the IETF Trust the right to allow Rohit Mediratta (editor)
modifications of such material outside the IETF Standards Process. Cisco Systems, Inc.
Without obtaining an adequate license from the person(s) 210 W Tasman Dr. Bldg. F,
controlling the copyright in such materials, this document may not San Jose, CA 95134
be modified outside the IETF Standards Process, and derivative US
works of it may not be created outside the IETF Standards Process, EMail: romedira@cisco.com
except to format it for publication as an RFC or to translate it
into languages other than English.
 End of changes. 318 change blocks. 
1164 lines changed or deleted 1105 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/