draft-ietf-bess-mvpn-mib-12.txt   rfc8503.txt 
Network Working Group H. Tsunoda Internet Engineering Task Force (IETF) H. Tsunoda
Internet-Draft Tohoku Institute of Technology Request for Comments: 8503 Tohoku Institute of Technology
Intended status: Standards Track September 17, 2018 Category: Standards Track December 2018
Expires: March 21, 2019 ISSN: 2070-1721
BGP/MPLS Layer 3 VPN Multicast Management Information Base BGP/MPLS Layer 3 VPN Multicast Management Information Base
draft-ietf-bess-mvpn-mib-12
Abstract Abstract
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 to configure and/or In particular, it describes managed objects to configure and/or
monitor Multicast communication over IP Virtual Private Networks monitor Multicast communication over IP Virtual Private Networks
(VPNs) supported by MultiProtocol Label Switching/Border Gateway (VPNs) supported by the Multiprotocol Label Switching/Border Gateway
Protcol (MPLS/BGP) on a Provider Edge router. Protocol (MPLS/BGP) on a Provider Edge (PE) router.
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.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on March 21, 2019. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8503.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . 3
3. BGP-MPLS-LAYER3-VPN-MULTICAST-MIB . . . . . . . . . . . . . . 4 3. BGP-MPLS-LAYER3-VPN-MULTICAST-MIB . . . . . . . . . . . . . . 3
3.1. Summary of MIB Module . . . . . . . . . . . . . . . . . . 4 3.1. Summary of the MIB Module . . . . . . . . . . . . . . . . 4
3.2. MIB Module Definitions . . . . . . . . . . . . . . . . . 5 3.2. MIB Module Definitions . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 50 4. Security Considerations . . . . . . . . . . . . . . . . . . . 51
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53
6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 53 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 54
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 54 6.1. Normative References . . . . . . . . . . . . . . . . . . 54
7.1. Normative References . . . . . . . . . . . . . . . . . . 54 6.2. Informative References . . . . . . . . . . . . . . . . . 56
7.2. Informative References . . . . . . . . . . . . . . . . . 56 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 57
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 57
1. Introduction 1. Introduction
[RFC6513], [RFC6514], and [RFC6625] specify procedures for supporting [RFC6513], [RFC6514], and [RFC6625] specify procedures for supporting
multicast in Border Gateway Protocol/MultiProtocol Label Switching multicast in Multiprotocol Label Switching/Border Gateway Protocol
(BGP/MPLS) Layer 3 (IP) Virtual Private Networks (VPNs). Throughout (MPLS/BGP) Layer 3 (IP) Virtual Private Networks (VPNs). Throughout
this document, we will use the term "Multicast VPN" (MVPN) [RFC6513] this document, we will use the term "MVPN" (for "multicast VPN")
to refer to a BGP/MPLS IP VPN that supports multicast. [RFC6513] to refer to a BGP/MPLS IP VPN that supports multicast.
Provider Edge routers (PEs) attaching to a particular MVPN exchange Provider Edge (PE) routers that attach to a particular MVPN exchange
customer multicast (C-multicast) routing information with neighboring customer multicast (C-multicast) routing information with neighboring
PEs. In [RFC6513], two basic methods for exchanging C-multicast PEs. In [RFC6513], two basic methods for exchanging C-multicast
routing information are defined (1) Protocol Independent Multicast routing information are defined: (1) Protocol Independent Multicast
(PIM) [RFC7761] and (2) BGP. (PIM) [RFC7761] and (2) BGP.
In the rest of this document we will use the term "PIM-MVPN" to refer In the rest of this document, we will use the term "PIM-MVPN" to
to the case where PIM is used for exchanging C-multicast routing refer to the case where PIM is used for exchanging C-multicast
information, and "BGP-MVPN" to refer to the case where BGP is used routing information and "BGP-MVPN" to refer to the case where BGP is
for exchanging C-multicast routing information. used for exchanging C-multicast routing information.
This document describes managed objects to configure and/or monitor This document describes managed objects to configure and/or monitor
MVPNs. Most of the managed objects are common to both PIM-MVPN and MVPNs. Most of the managed objects are common to both PIM-MVPN and
BGP-MVPN, and some managed objects are BGP-MVPN specific. BGP-MVPN, and some managed objects are BGP-MVPN specific.
1.1. Terminology 1.1. Terminology
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, abbreviations, and mechanisms
described in [RFC4364], [RFC6513], and [RFC6514]. Familiarity with described in [RFC4364], [RFC6513], and [RFC6514]. Familiarity with
Multicast, MPLS, Layer 3 (L3) VPN, MVPN concepts and/or mechanisms is multicast, MPLS, Layer 3 (L3) VPN, and MVPN concepts and/or
assumed. Some terms specifically related to this document are mechanisms is assumed. Some terms specifically related to this
explained below. document are explained below.
An MVPN can be realized by using various kinds of transport An MVPN can be realized by using various kinds of transport
mechanisms for forwarding a packet to all or a subset of PEs across mechanisms for forwarding a packet to all or a subset of PEs across
service provider networks. Such transport mechanisms are referred to service provider networks. Such transport mechanisms are referred to
as provider tunnels (P-tunnels). as provider tunnels (P-tunnels).
A "Provider Multicast Service Interface" (PMSI) [RFC6513] is a A Provider Multicast Service Interface (PMSI) [RFC6513] is a
conceptual interface instantiated by a P-tunnel. A PE uses a PMSI to conceptual interface instantiated by a P-tunnel. A PE uses a PMSI to
send customer multicast traffic to all or some PEs in the same VPN. send customer multicast traffic to all or some PEs in the same VPN.
There are two kinds of PMSI: "Inclusive PMSI" (I-PMSI) and "Selective There are two kinds of PMSIs: Inclusive PMSI (I-PMSI) and Selective
PMSI" (S-PMSI) [RFC6513]. An I-PMSI enables a PE attached to a PMSI (S-PMSI) [RFC6513]. An I-PMSI enables a PE attached to a
particular MVPN to transmit a message to all PEs in the same MVPN. particular MVPN to transmit a message to all PEs in the same MVPN.
An S-PMSI enables a PE to transmit a message to a selected set of PEs An S-PMSI enables a PE to transmit a message to a selected set of PEs
in the same MVPN. in the same MVPN.
As described in [RFC4382], each PE maintains one default forwarding As described in [RFC4382], each PE maintains one default forwarding
table and zero or more "Virtual Routing and Forwarding tables" table and zero or more Virtual Routing and Forwarding (VRF) tables.
(VRFs). Throughout this document, we will use the term "multicast Throughout this document, we will use the term "MVRF" (for "multicast
VRF" (MVRF) to refer to a VRF that contains multicast routing VRF") to refer to a VRF that contains multicast routing information.
information.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in
14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. The Internet-Standard Management Framework 2. 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 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
skipping to change at page 4, line 12 skipping to change at page 4, line 5
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. BGP-MPLS-LAYER3-VPN-MULTICAST-MIB 3. BGP-MPLS-LAYER3-VPN-MULTICAST-MIB
This document defines BGP-MPLS-LAYER3-VPN-MULTICAST-MIB, a MIB module This document defines BGP-MPLS-LAYER3-VPN-MULTICAST-MIB, a MIB module
for monitoring and/or configuring MVPNs on PEs. This MIB module will for monitoring and/or configuring MVPNs on PEs. This MIB module will
be used in conjunction with MPLS-L3VPN-STD-MIB [RFC4382] and IPMCAST- be used in conjunction with MPLS-L3VPN-STD-MIB [RFC4382] and IPMCAST-
MIB [RFC5132]. MIB [RFC5132].
3.1. Summary of MIB Module 3.1. Summary of the MIB Module
BGP-MPLS-LAYER3-VPN-MULTICAST-MIB provides the following BGP-MPLS-LAYER3-VPN-MULTICAST-MIB provides the following
functionalities. functionalities.
o Monitoring attributes of MVPNs on a PE o Monitoring attributes of MVPNs on a PE
o Configuring timers and thresholds related to an MVPN on a PE o Configuring timers and thresholds related to an MVPN on a PE
o Notifying creation, deletion, and modification of MVRFs on a PE o Notifying creation, deletion, and modification of MVRFs on a PE
o Monitoring PMSI attributes o Monitoring PMSI attributes
o Monitoring statistics of advertisements exchanged by a PE o Monitoring statistics of advertisements exchanged by a PE
o Monitoring routing information for multicast destinations o Monitoring routing information for multicast destinations
o Monitoring next-hops for each multicast destination o Monitoring next hops for each multicast destination
To provide these functionalities, BGP-MPLS-LAYER3-VPN-MULTICAST-MIB To provide these functionalities, BGP-MPLS-LAYER3-VPN-MULTICAST-MIB
defines following tables. defines the following tables.
o mvpnGenericTable o mvpnGenericTable
This table contains generic information about MVPNs on a PE. Each This table contains generic information about MVPNs on a PE. Each
entry in this table represents an instance of an MVPN on a PE and entry in this table represents an instance of an MVPN on a PE and
contains generic information related to the MVPN. For each entry contains generic information related to the MVPN. For each entry
in this table there MUST be a corresponding VRF in MPLS-L3VPN-STD- in this table, there MUST be a corresponding VRF in MPLS-L3VPN-
MIB [RFC4382]. STD-MIB [RFC4382].
o mvpnBgpTable o mvpnBgpTable
This table contains information specific to BGP-MVPNs. Each BGP- This table contains information specific to BGP-MVPNs. Each BGP-
MVPN on a PE will have an entry in this table. MVPN on a PE will have an entry in this table.
o mvpnPmsiTable o mvpnPmsiTable
This table contains managed objects representing attribute This table contains managed objects representing attribute
information that is common to I-PMSIs and S-PMSIs on a PE. information that is common to I-PMSIs and S-PMSIs on a PE.
skipping to change at page 5, line 20 skipping to change at page 5, line 17
This table contains statistics pertaining to I-PMSI and S-PMSI This table contains statistics pertaining to I-PMSI and S-PMSI
advertisements sent/received. advertisements sent/received.
o mvpnMrouteTable o mvpnMrouteTable
This table contains multicast routing information in MVRFs on a This table contains multicast routing information in MVRFs on a
PE. PE.
o mvpnMrouteNextHopTable o mvpnMrouteNextHopTable
This table contains information on the next-hops for routing IP This table contains information on the next hops for routing IP
multicast datagrams in MVPNs on a PE. multicast datagrams in MVPNs on a PE.
3.2. MIB Module Definitions 3.2. MIB Module Definitions
This MIB module makes reference to the following documents:
[RFC2003], [RFC2784], [RFC2863], [RFC3032], [RFC4001], and [RFC8502].
BGP-MPLS-LAYER3-VPN-MULTICAST-MIB DEFINITIONS ::= BEGIN BGP-MPLS-LAYER3-VPN-MULTICAST-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Counter64, Gauge32, Unsigned32, TimeTicks, Counter32, Counter64, Gauge32, Unsigned32, TimeTicks,
mib-2 mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- RFC 2578
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- RFC 2580
RowPointer, TimeStamp, DateAndTime RowPointer, TimeStamp, DateAndTime
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- RFC 2579
InterfaceIndex, InterfaceIndexOrZero InterfaceIndex, InterfaceIndexOrZero
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- RFC 2863
InetAddress, InetAddressType, InetAddressPrefixLength InetAddress, InetAddressType, InetAddressPrefixLength
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB -- RFC 4001
mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher
FROM MPLS-L3VPN-STD-MIB -- [RFC4382] FROM MPLS-L3VPN-STD-MIB -- RFC 4382
IANAipRouteProtocol, IANAipMRouteProtocol IANAipRouteProtocol, IANAipMRouteProtocol
FROM IANA-RTPROTO-MIB -- [RTPROTO] FROM IANA-RTPROTO-MIB
-- http://www.iana.org/assignments/ianaiprouteprotocol-mib
L2L3VpnMcastProviderTunnelType L2L3VpnMcastProviderTunnelType
FROM L2L3-VPN-MULTICAST-TC-MIB; -- [RFCXXXX] FROM L2L3-VPN-MULTICAST-TC-MIB; -- RFC 8502
-- RFC Ed.: replace XXXX here and in the References Section
-- with the actual RFC number assigned to
-- I-D ietf-bess-l2l3-vpn-mcast-mib and remove this note.
mvpnMIB MODULE-IDENTITY mvpnMIB MODULE-IDENTITY
LAST-UPDATED "201809071200Z" -- 7th September 2018 12:00:00 GMT LAST-UPDATED "201812140000Z" -- 14 December 2018
ORGANIZATION "IETF BESS Working Group." ORGANIZATION "IETF BESS Working Group"
CONTACT-INFO CONTACT-INFO
" Hiroshi Tsunoda "Hiroshi Tsunoda
Tohoku Institute of Technology Tohoku Institute of Technology
35-1, Yagiyama Kasumi-cho 35-1, Yagiyama Kasumi-cho
Taihaku-ku, Sendai, 982-8577 Taihaku-ku, Sendai, 982-8577
Japan Japan
Email: tsuno@m.ieice.org Email: tsuno@m.ieice.org"
Comments and discussion to bess@ietf.org"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions to "This MIB module contains managed object definitions to
configure and/or monitor Multicast communication over IP configure and/or monitor Multicast communication over IP
Virtual Private Networks (VPNs) supported by MultiProtocol Virtual Private Networks (VPNs) supported by the
Label Switching/Border Gateway Protocol (MPLS/BGP) on a Multiprotocol Label Switching/Border Gateway Protocol
Provider Edge router (PE). (MPLS/BGP) on a Provider Edge (PE) router.
Copyright (C) The Internet Society (2018).
"
-- Revision history.
REVISION "201809071200Z" -- 7th September, 2018 Copyright (c) 2018 IETF Trust and the persons identified
DESCRIPTION as authors of the code. All rights reserved.
"Initial version, published as RFC YYYY."
-- RFC Ed.: replace YYYY with the actual RFC number and Redistribution and use in source and binary forms, with or
-- remove this note 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).
"
::= { mib-2 AAAA } -- Revision History
-- IANA Reg.: Please assign a value for "AAAA" under the REVISION "201812140000Z" -- 14 December 2018
-- 'mib-2' subtree and record the assignment in the SMI DESCRIPTION
-- Numbers registry. "Initial version, published as RFC 8503."
-- RFC Ed.: When the above assignment has been made, please ::= { mib-2 243 }
-- remove the above note
-- replace "AAAA" here with the assigned value and
-- remove this note.
-- Top level components of this MIB module. -- Top-level components of this MIB module.
mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 } mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 }
-- scalars, tables -- Scalars, Tables
mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 } mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 }
-- conformance information -- Conformance Information
mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 } mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 }
-- MVPN Objects
-- mvpn Objects
mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 } mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 }
-- Scalar Objects -- Scalar Objects
mvpnMvrfs OBJECT-TYPE mvpnMvrfs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of Multicast Virtual Routing and "The total number of Multicast Virtual Routing and
Forwarding tables (MVRFs) that are present on Forwarding (MVRF) tables that are present on
this Provider Edge router (PE). This includes MVRFs this Provider Edge (PE) router. This includes MVRFs
for IPv4, IPv6, and mLDP C-Multicast. for IPv4, IPv6, and Multipoint LDP (mLDP) C-multicast.
" "
::= { mvpnScalars 1 } ::= { mvpnScalars 1 }
mvpnV4Mvrfs OBJECT-TYPE mvpnV4Mvrfs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of MVRFs for IPv4 C-Multicast on this PE. "The number of MVRFs for IPv4 C-multicast on this PE.
" "
::= { mvpnScalars 2 } ::= { mvpnScalars 2 }
mvpnV6Mvrfs OBJECT-TYPE mvpnV6Mvrfs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of MVRFs for IPv6 C-Multicast on this PE. "The number of MVRFs for IPv6 C-multicast on this PE.
" "
::= { mvpnScalars 3 } ::= { mvpnScalars 3 }
mvpnMldpMvrfs OBJECT-TYPE mvpnMldpMvrfs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of MVRFs on this PE that use BGP for "The number of MVRFs on this PE that use BGP for
exchanging Multipoint Label Distribution Protocol (mLDP) exchanging mLDP C-multicast routing information.
C-Multicast routing information.
" "
::= { mvpnScalars 4 } ::= { mvpnScalars 4 }
mvpnPimV4Mvrfs OBJECT-TYPE mvpnPimV4Mvrfs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of MVRFs on this PE that use Provider "The number of MVRFs on this PE that use Provider
Independent Multicast (PIM) for exchanging IPv4 Independent Multicast (PIM) for exchanging IPv4
C-Multicast routing information. C-multicast routing information.
" "
::= { mvpnScalars 5 } ::= { mvpnScalars 5 }
mvpnPimV6Mvrfs OBJECT-TYPE mvpnPimV6Mvrfs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of MVRFs on this PE that use PIM for "The number of MVRFs on this PE that use PIM for
exchanging IPv6 C-Multicast routing information. exchanging IPv6 C-multicast routing information.
" "
::= { mvpnScalars 6 } ::= { mvpnScalars 6 }
mvpnBgpV4Mvrfs OBJECT-TYPE mvpnBgpV4Mvrfs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of MVRFs on this PE that use BGP for "The number of MVRFs on this PE that use BGP for
exchanging IPv4 C-Multicast routing information. exchanging IPv4 C-multicast routing information.
" "
::= { mvpnScalars 7 } ::= { mvpnScalars 7 }
mvpnBgpV6Mvrfs OBJECT-TYPE mvpnBgpV6Mvrfs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of MVRFs on this PE that use BGP for "The number of MVRFs on this PE that use BGP for
exchanging IPv6 C-Multicast routing information. exchanging IPv6 C-multicast routing information.
" "
::= { mvpnScalars 8 } ::= { mvpnScalars 8 }
mvpnSPTunnelLimit OBJECT-TYPE mvpnSPTunnelLimit OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of selective provider tunnels that "The maximum number of selective provider tunnels that
this PE allows for a particular MVPN on this PE. are allowed for a particular MVPN on this PE.
" "
REFERENCE REFERENCE
"RFC6513, Section 13" "RFC 6513, Section 13"
::= { mvpnScalars 9 } ::= { mvpnScalars 9 }
mvpnBgpCmcastRouteWithdrawalTimer OBJECT-TYPE mvpnBgpCmcastRouteWithdrawalTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A configurable timer to control the delay "A configurable timer to control the delay
of C-multicast route withdrawal advertisements. of C-multicast route withdrawal advertisements.
" "
REFERENCE REFERENCE
"RFC6514, Section 16.1.1" "RFC 6514, Section 16.1.1"
::= { mvpnScalars 10 } ::= { mvpnScalars 10 }
mvpnBgpSrcSharedTreeJoinTimer OBJECT-TYPE mvpnBgpSrcSharedTreeJoinTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A configurable timer to control the delay "A configurable timer to control the delay
of Source/Shared Tree Join C-multicast route of Source/Shared Tree Join C-multicast route
advertisements. advertisements.
" "
REFERENCE REFERENCE
"RFC6514, Section 16.1.2" "RFC 6514, Section 16.1.2"
::= { mvpnScalars 11 } ::= { mvpnScalars 11 }
-- Generic MVRF Information Table -- Generic MVRF Information Table
mvpnGenericTable OBJECT-TYPE mvpnGenericTable OBJECT-TYPE
SYNTAX SEQUENCE OF MvpnGenericEntry SYNTAX SEQUENCE OF MvpnGenericEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual table containing generic information about MVPNs "A conceptual table containing generic information about
on this PE. MVPNs on this PE.
" "
::= { mvpnObjects 2 } ::= { mvpnObjects 2 }
mvpnGenericEntry OBJECT-TYPE mvpnGenericEntry OBJECT-TYPE
SYNTAX MvpnGenericEntry SYNTAX MvpnGenericEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row that represents an MVPN on this PE. "A conceptual row that represents an MVPN on this PE.
The MVPN represented by this entry will have one or more The MVPN represented by this entry will have one or more
corresponding P-Multicast Service Interfaces (PMSIs) corresponding P-Multicast Service Interfaces (PMSIs)
and a corresponding VRF in MPLS-L3VPN-STD-MIB [RFC4382]. and a corresponding VRF in MPLS-L3VPN-STD-MIB (RFC 4382).
" "
INDEX { INDEX {
mplsL3VpnVrfName mplsL3VpnVrfName
} }
::= { mvpnGenericTable 1 } ::= { mvpnGenericTable 1 }
MvpnGenericEntry ::= SEQUENCE { MvpnGenericEntry ::= SEQUENCE {
mvpnGenMvrfLastAction INTEGER, mvpnGenMvrfLastAction INTEGER,
mvpnGenMvrfLastActionTime DateAndTime, mvpnGenMvrfLastActionTime DateAndTime,
mvpnGenMvrfCreationTime DateAndTime, mvpnGenMvrfCreationTime DateAndTime,
skipping to change at page 11, line 9 skipping to change at page 10, line 49
The enumerated action types and the corresponding The enumerated action types and the corresponding
descriptions are as follows: descriptions are as follows:
createdMvrf: createdMvrf:
MVRF was created for this MVPN on the PE. MVRF was created for this MVPN on the PE.
deletedMvrf: deletedMvrf:
MVRF for this MVPN was deleted from the PE. MVRF for this MVPN was deleted from the PE.
A conceptual row in this table will never have A conceptual row in this table will never have
mvpnGenMvrfLastAction equal to deletedMvrf, mvpnGenMvrfLastAction equal to deletedMvrf,
because in that case the row itself will not exist because in that case, the row itself will not exist
in the table. in the table.
This value for mvpnGenMvrfLastAction is defined This value for mvpnGenMvrfLastAction is defined
solely for use in mvpnMvrfActionChange notification. solely for use in the mvpnMvrfActionChange
notification.
modifiedMvrfIpmsiConfig: modifiedMvrfIpmsiConfig:
an I-PMSI for this MVPN was configured, deleted or An I-PMSI for this MVPN was configured, deleted,
changed. or changed.
modifiedMvrfSpmsiConfig: modifiedMvrfSpmsiConfig:
an S-PMSI for this MVPN was configured, deleted or An S-PMSI for this MVPN was configured, deleted,
changed. or changed.
" "
::= { mvpnGenericEntry 2 } ::= { mvpnGenericEntry 2 }
mvpnGenMvrfLastActionTime OBJECT-TYPE mvpnGenMvrfLastActionTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The timestamp when the last action, given in "The timestamp when the last action, given in
the corresponding mvpnGenMvrfLastAction object, the corresponding mvpnGenMvrfLastAction object,
skipping to change at page 12, line 15 skipping to change at page 12, line 12
information across the provider core for the MVPN information across the provider core for the MVPN
represented by this entry. represented by this entry.
The enumerated protocols and the corresponding The enumerated protocols and the corresponding
descriptions are as follows: descriptions are as follows:
pim : PIM (PIM-MVPN) pim : PIM (PIM-MVPN)
bgp : BGP (BGP-MVPN) bgp : BGP (BGP-MVPN)
" "
REFERENCE REFERENCE
"RFC6513, Section 5" "RFC 6513, Section 5"
::= { mvpnGenericEntry 5 } ::= { mvpnGenericEntry 5 }
mvpnGenIpmsiInfo OBJECT-TYPE mvpnGenIpmsiInfo OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pointer to a conceptual row representing "A pointer to a conceptual row representing
the corresponding I-PMSI in mvpnPmsiTable. the corresponding I-PMSI in mvpnPmsiTable.
If there is no I-PMSI for the MVPN If there is no I-PMSI for the MVPN
skipping to change at page 13, line 4 skipping to change at page 12, line 49
mvpnGenUmhSelection OBJECT-TYPE mvpnGenUmhSelection OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
highestPeAddress (1), highestPeAddress (1),
cRootGroupHashing (2), cRootGroupHashing (2),
ucastUmhRoute (3) ucastUmhRoute (3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Upstream Multicast Hop (UMH) selection method for the MVPN "The Upstream Multicast Hop (UMH) selection method for the
represented by this entry. MVPN represented by this entry.
The enumerated methods and the corresponding The enumerated methods and the corresponding
descriptions are as follows: descriptions are as follows:
highestPeAddress : PE with the highest address highestPeAddress : PE with the highest address
(see RFC6513, Section 5.1.3) (see RFC 6513, Section 5.1.3)
cRootGroupHashing : hashing based on (c-root, c-group) cRootGroupHashing : hashing based on (c-root, c-group)
ucastUmhRoute : per unicast route towards c-root ucastUmhRoute : per-unicast route towards c-root
" "
REFERENCE REFERENCE
"RFC6513, Section 5.1" "RFC 6513, Section 5.1"
::= { mvpnGenericEntry 8 } ::= { mvpnGenericEntry 8 }
mvpnGenCustomerSiteType OBJECT-TYPE mvpnGenCustomerSiteType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
senderReceiver (1), senderReceiver (1),
receiverOnly (2), receiverOnly (2),
senderOnly (3) senderOnly (3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the customer site, connected to "The type of the customer site, connected to
the MVPN represented by this entry. the MVPN represented by this entry.
The enumerated types and the corresponding The enumerated types and the corresponding
descriptions are as follows: descriptions are as follows:
senderReceiver : Site is both sender and receiver senderReceiver : Site is both sender and receiver
receiverOnly : Site is receiver-only receiverOnly : Site is receiver only
senderOnly : Site is sender-only senderOnly : Site is sender only
" "
REFERENCE REFERENCE
"RFC6513, Section 2.3" "RFC 6513, Section 2.3"
::= { mvpnGenericEntry 9 } ::= { mvpnGenericEntry 9 }
-- Generic BGP-MVPN table -- Generic BGP-MVPN Table
mvpnBgpTable OBJECT-TYPE mvpnBgpTable OBJECT-TYPE
SYNTAX SEQUENCE OF MvpnBgpEntry SYNTAX SEQUENCE OF MvpnBgpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual table that supplements mvpnGenericTable "A conceptual table that supplements mvpnGenericTable
with BGP-MVPN specific information for BGP-MVPNs on this PE. with BGP-MVPN-specific information for BGP-MVPNs on this PE.
" "
::= { mvpnObjects 3 } ::= { mvpnObjects 3 }
mvpnBgpEntry OBJECT-TYPE mvpnBgpEntry OBJECT-TYPE
SYNTAX MvpnBgpEntry SYNTAX MvpnBgpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row corresponding to a BGP-MVPN on this PE. "A conceptual row corresponding to a BGP-MVPN on this PE.
" "
INDEX { INDEX {
skipping to change at page 14, line 45 skipping to change at page 14, line 43
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The inter-site C-tree mode used by the BGP-MVPN "The inter-site C-tree mode used by the BGP-MVPN
represented by this entry. represented by this entry.
other : none of the following other : none of the following
rptSpt : inter-site shared tree mode rptSpt : inter-site shared tree mode
(Rendezvous Point Tree (RPT) and (Rendezvous Point Tree (RPT) and
source-specific shortest-path tree (SPT)) source-specific shortest-path tree (SPT))
sptOnly : inter-site source-only tree mode sptOnly : inter-site source-only tree mode
" "
REFERENCE REFERENCE
"RFC6513, Section 9.3.1" "RFC 6513, Section 9.3.1"
::= { mvpnBgpEntry 1 } ::= { mvpnBgpEntry 1 }
mvpnBgpVrfRouteImportExtendedCommunity OBJECT-TYPE mvpnBgpVrfRouteImportExtendedCommunity OBJECT-TYPE
SYNTAX MplsL3VpnRouteDistinguisher SYNTAX MplsL3VpnRouteDistinguisher
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VRF Route Import Extended Community added by this PE "The VRF Route Import Extended Community added by this PE
to unicast VPN routes that it advertises for the BGP-MVPN to unicast VPN routes that it advertises for the BGP-MVPN
corresponding to this entry. corresponding to this entry.
" "
REFERENCE REFERENCE
"RFC6514, Section 7 "RFC 6514, Section 7
" "
::= { mvpnBgpEntry 2 } ::= { mvpnBgpEntry 2 }
mvpnBgpSrcASExtendedCommunity OBJECT-TYPE mvpnBgpSrcASExtendedCommunity OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Source AS Extended Community added by this PE "The Source AS Extended Community added by this PE
to the unicast VPN routes that it advertises for to the unicast VPN routes that it advertises for
the BGP-MVPN represented by this entry. the BGP-MVPN represented by this entry.
" "
REFERENCE REFERENCE
"RFC6514, Section 6 "RFC 6514, Section 6
" "
::= { mvpnBgpEntry 3 } ::= { mvpnBgpEntry 3 }
mvpnBgpMsgRateLimit OBJECT-TYPE mvpnBgpMsgRateLimit OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "messages per second" UNITS "messages per second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configurable upper bound for the rate of BGP C-multicast "The configurable upper bound for the rate of the BGP
routing information message exchange between this PE and other C-multicast routing information message exchange between
PEs in the BGP-MVPN corresponding to this entry. this PE and other PEs in the BGP-MVPN corresponding to
this entry.
" "
REFERENCE REFERENCE
"RFC6514, Section 17" "RFC 6514, Section 17"
::= { mvpnBgpEntry 4 } ::= { mvpnBgpEntry 4 }
mvpnBgpMaxSpmsiAdRoutes OBJECT-TYPE mvpnBgpMaxSpmsiAdRoutes 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 configurable upper bound for the number of "The configurable upper bound for the number of S-PMSI
S-PMSI A-D routes for the BGP-MVPN corresponding to auto-discovery (A-D) routes for the BGP-MVPN
this entry. corresponding to this entry.
" "
REFERENCE REFERENCE
"RFC6514, Section 17" "RFC 6514, Section 17"
::= { mvpnBgpEntry 5 } ::= { mvpnBgpEntry 5 }
mvpnBgpMaxSpmsiAdRouteFreq OBJECT-TYPE mvpnBgpMaxSpmsiAdRouteFreq OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "routes per second" UNITS "routes per second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configurable upper bound for the frequency of "The configurable upper bound for the frequency of
S-PMSI A-D route generation for the BGP-MVPN corresponding S-PMSI A-D route generation for the BGP-MVPN
to this entry. corresponding to this entry.
" "
REFERENCE REFERENCE
"RFC6514, Section 17" "RFC 6514, Section 17"
::= { mvpnBgpEntry 6 } ::= { mvpnBgpEntry 6 }
mvpnBgpMaxSrcActiveAdRoutes OBJECT-TYPE mvpnBgpMaxSrcActiveAdRoutes 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 configurable upper bound for the number of "The configurable upper bound for the number of
Source Active A-D routes for the BGP-MVPN corresponding Source Active A-D routes for the BGP-MVPN corresponding
to this entry. to this entry.
" "
REFERENCE REFERENCE
"RFC6514, Section 17" "RFC 6514, Section 17"
::= { mvpnBgpEntry 7 } ::= { mvpnBgpEntry 7 }
mvpnBgpMaxSrcActiveAdRouteFreq OBJECT-TYPE mvpnBgpMaxSrcActiveAdRouteFreq OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "routes per second" UNITS "routes per second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configurable upper bound for the frequency of Source "The configurable upper bound for the frequency of Source
Active A-D route generation for the BGP-MVPN corresponding Active A-D route generation for the BGP-MVPN corresponding
to this entry. to this entry.
" "
REFERENCE REFERENCE
"RFC6514, Section 17" "RFC 6514, Section 17"
::= { mvpnBgpEntry 8 } ::= { mvpnBgpEntry 8 }
-- Table of PMSI information -- Table of PMSI Information
mvpnPmsiTable OBJECT-TYPE mvpnPmsiTable OBJECT-TYPE
SYNTAX SEQUENCE OF MvpnPmsiEntry SYNTAX SEQUENCE OF MvpnPmsiEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual table containing information related "A conceptual table containing information related
to PMSIs on this PE. to PMSIs on this PE.
" "
::= { mvpnObjects 4 } ::= { mvpnObjects 4 }
skipping to change at page 17, line 42 skipping to change at page 17, line 45
mvpnPmsiTunnelPimGroupAddrType InetAddressType, mvpnPmsiTunnelPimGroupAddrType InetAddressType,
mvpnPmsiTunnelPimGroupAddr InetAddress, mvpnPmsiTunnelPimGroupAddr InetAddress,
mvpnPmsiEncapsulationType INTEGER mvpnPmsiEncapsulationType INTEGER
} }
mvpnPmsiTunnelIfIndex OBJECT-TYPE mvpnPmsiTunnelIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique value for this conceptual row. Its value "A unique value for this conceptual row. Its value
will be the same as that of the ifIndex object instance will be the same as that of the ifIndex object instance
for the corresponding PMSI in ifTable. for the corresponding PMSI in ifTable.
" "
REFERENCE REFERENCE
"RFC2863 Sec. 3.1.5 "RFC 2863, Section 3.1.5
" "
::= { mvpnPmsiEntry 1 } ::= { mvpnPmsiEntry 1 }
mvpnPmsiRD OBJECT-TYPE mvpnPmsiRD OBJECT-TYPE
SYNTAX MplsL3VpnRouteDistinguisher SYNTAX MplsL3VpnRouteDistinguisher
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Route Distinguisher for this I-PMSI." "The Route Distinguisher for this I-PMSI.
"
::= { mvpnPmsiEntry 3 } ::= { mvpnPmsiEntry 3 }
mvpnPmsiTunnelType OBJECT-TYPE mvpnPmsiTunnelType OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelType SYNTAX L2L3VpnMcastProviderTunnelType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of tunnel used to "The type of tunnel used to
instantiate the PMSI corresponding to this entry. instantiate the PMSI corresponding to this entry.
" "
REFERENCE REFERENCE
"RFC6513, Sec. 2.6 "RFC 6513, Section 2.6
" "
::= { mvpnPmsiEntry 4 } ::= { mvpnPmsiEntry 4 }
mvpnPmsiTunnelAttribute OBJECT-TYPE mvpnPmsiTunnelAttribute OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pointer to a conceptual row representing "A pointer to a conceptual row representing
the P-tunnel used by the PMSI in the P-tunnel used by the PMSI in
l2L3VpnMcastPmsiTunnelAttributeTable. l2L3VpnMcastPmsiTunnelAttributeTable.
" "
::= { mvpnPmsiEntry 5 } ::= { mvpnPmsiEntry 5 }
mvpnPmsiTunnelPimGroupAddrType OBJECT-TYPE mvpnPmsiTunnelPimGroupAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the mvpnPmsiTunnelPimGroupAddr object "The InetAddressType of the mvpnPmsiTunnelPimGroupAddr object
that follows. that follows. When the PMSI corresponding to this entry
When the PMSI corresponding to this entry does not use does not use the PIM provider tunnel, i.e., the value of
the PIM provider tunnel, i.e., mvpnPmsiTunnelType is not one of pimSsm(3), pimAsm(4), or
the value of mvpnPmsiTunnelType is not one of pimBidir(5), this object should be unknown(0).
pimSsm(3), pimAsm(4), or pimBidir(5),
this object should be unknown(0).
" "
::= { mvpnPmsiEntry 6 } ::= { mvpnPmsiEntry 6 }
mvpnPmsiTunnelPimGroupAddr OBJECT-TYPE mvpnPmsiTunnelPimGroupAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tunnel address which is used by the PMSI "The tunnel address that is used by the PMSI
corresponding to this entry. corresponding to this entry. When the PMSI
When the PMSI corresponding to this entry does not corresponding to this entry does not use
use PIM provider tunnel, i.e., the PIM provider tunnel, i.e., the value of
the value of mvpnPmsiTunnelType is not one of mvpnPmsiTunnelType is not one of pimSsm(3),
pimSsm(3), pimAsm(4), or pimBidir(5), pimAsm(4), or pimBidir(5), this
this object should be a zero-length octet string. object should be a zero-length octet string.
" "
::= { mvpnPmsiEntry 7 } ::= { mvpnPmsiEntry 7 }
mvpnPmsiEncapsulationType OBJECT-TYPE mvpnPmsiEncapsulationType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
greIp (1), greIp (1),
ipIp (2), ipIp (2),
mpls (3) mpls (3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The encapsulation type used for sending "The encapsulation type used for sending
packets through the PMSI corresponding to this entry. packets through the PMSI corresponding to this entry.
The enumerated encapsulation types and the corresponding The enumerated encapsulation types and the corresponding
descriptions are as follows: descriptions are as follows:
greIp : GRE (Generic Routing Encapsulation) greIp : Generic Routing Encapsulation (GRE)
encapsulation [RFC2784] (RFC 2784)
ipIp : IP-in-IP encapsulation [RFC2003] ipIp : IP-in-IP encapsulation (RFC 2003)
mpls : MPLS encapsulation [RFC3032] mpls : MPLS encapsulation (RFC 3032)
" "
REFERENCE REFERENCE
"RFC2003 "RFC 2003
RFC2784 RFC 2784
RFC3032 RFC 3032
RFC6513, Sec. 12.1 RFC 6513, Section 12.1
" "
::= { mvpnPmsiEntry 8 } ::= { mvpnPmsiEntry 8 }
-- Table of S-PMSI specific information -- Table of S-PMSI-Specific Information
mvpnSpmsiTable OBJECT-TYPE mvpnSpmsiTable OBJECT-TYPE
SYNTAX SEQUENCE OF MvpnSpmsiEntry SYNTAX SEQUENCE OF MvpnSpmsiEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual table containing information related "A conceptual table containing information related
to S-PMSIs on this PE. to S-PMSIs on this PE.
This table stores only S-PMSI specific attribute This table stores only S-PMSI-specific attribute
information. Generic PMSI attribute information of information. Generic PMSI attribute information of
S-PMSIs is stored in mvpnPmsiTable. S-PMSIs is stored in mvpnPmsiTable.
" "
::= { mvpnObjects 5 } ::= { mvpnObjects 5 }
mvpnSpmsiEntry OBJECT-TYPE mvpnSpmsiEntry OBJECT-TYPE
SYNTAX MvpnSpmsiEntry SYNTAX MvpnSpmsiEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row corresponding to an S-PMSI on this PE. "A conceptual row corresponding to an S-PMSI on this PE.
Implementers need to be aware that if the total number of Implementers need to be aware that if the total number of
octets in mplsL3VpnVrfName, mvpnSpmsiCmcastGroupAddr and octets in mplsL3VpnVrfName, mvpnSpmsiCmcastGroupAddr, and
mvpnSpmsiCmcastSourceAddr exceeds 113, the OIDs of column mvpnSpmsiCmcastSourceAddr exceeds 113, the OIDs of column
instances in this row will have more than 128 sub-identifiers instances in this row will have more than 128 sub-identifiers
and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
" "
INDEX { INDEX {
mplsL3VpnVrfName, mplsL3VpnVrfName,
mvpnSpmsiCmcastGroupAddrType, mvpnSpmsiCmcastGroupAddrType,
mvpnSpmsiCmcastGroupAddr, mvpnSpmsiCmcastGroupAddr,
mvpnSpmsiCmcastGroupPrefixLen, mvpnSpmsiCmcastGroupPrefixLen,
mvpnSpmsiCmcastSourceAddrType, mvpnSpmsiCmcastSourceAddrType,
skipping to change at page 21, line 4 skipping to change at page 21, line 7
mvpnSpmsiPmsiPointer RowPointer mvpnSpmsiPmsiPointer RowPointer
} }
mvpnSpmsiCmcastGroupAddrType OBJECT-TYPE mvpnSpmsiCmcastGroupAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the mvpnSpmsiCmcastGroupAddr object "The InetAddressType of the mvpnSpmsiCmcastGroupAddr object
that follows. that follows.
" "
::= { mvpnSpmsiEntry 1 } ::= { mvpnSpmsiEntry 1 }
mvpnSpmsiCmcastGroupAddr OBJECT-TYPE mvpnSpmsiCmcastGroupAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group address of the C-flow assigned to the "The group address of the C-flow assigned to the
S-PMSI corresponding to this entry." S-PMSI corresponding to this entry.
"
REFERENCE REFERENCE
"RFC6513, Sec. 3.1" "RFC 6513, Section 3.1"
::= { mvpnSpmsiEntry 2 } ::= { mvpnSpmsiEntry 2 }
mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The prefix length of the corresponding "The prefix length of the corresponding
mvpnSpmsiCmcastGroupAddr object. mvpnSpmsiCmcastGroupAddr object.
" "
skipping to change at page 21, line 45 skipping to change at page 21, line 48
that follows. that follows.
" "
::= { mvpnSpmsiEntry 4 } ::= { mvpnSpmsiEntry 4 }
mvpnSpmsiCmcastSourceAddr OBJECT-TYPE mvpnSpmsiCmcastSourceAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The source address of the C-flow assigned to the "The source address of the C-flow assigned to the
S-PMSI corresponding to this entry." S-PMSI corresponding to this entry.
"
::= { mvpnSpmsiEntry 5 } ::= { mvpnSpmsiEntry 5 }
mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The prefix length of the corresponding "The prefix length of the corresponding
mvpnSpmsiCmcastSourceAddr object. mvpnSpmsiCmcastSourceAddr object.
" "
skipping to change at page 22, line 19 skipping to change at page 22, line 25
mvpnSpmsiPmsiPointer OBJECT-TYPE mvpnSpmsiPmsiPointer OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pointer to a conceptual row representing "A pointer to a conceptual row representing
generic information of this S-PMSI in mvpnPmsiTable. generic information of this S-PMSI in mvpnPmsiTable.
" "
::= { mvpnSpmsiEntry 7 } ::= { mvpnSpmsiEntry 7 }
-- Table of statistics pertaining to -- Table of Statistics Pertaining to
-- advertisements sent/received -- Advertisements Sent/Received
mvpnAdvtStatsTable OBJECT-TYPE mvpnAdvtStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF MvpnAdvtStatsEntry SYNTAX SEQUENCE OF MvpnAdvtStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual table containing statistics pertaining to "A conceptual table containing statistics pertaining to
I-PMSI and S-PMSI advertisements sent/received by this PE. I-PMSI and S-PMSI advertisements sent/received by this PE.
" "
::= { mvpnObjects 6 } ::= { mvpnObjects 6 }
skipping to change at page 23, line 41 skipping to change at page 23, line 46
"The PMSI type. "The PMSI type.
The enumerated PMSI types and corresponding The enumerated PMSI types and corresponding
descriptions are as follows: descriptions are as follows:
intraAsIpmsi : Intra-AS Inclusive PMSI intraAsIpmsi : Intra-AS Inclusive PMSI
interAsIpmsi : Inter-AS Inclusive PMSI interAsIpmsi : Inter-AS Inclusive PMSI
sPmsi : Selective PMSI sPmsi : Selective PMSI
" "
REFERENCE REFERENCE
"RFC6513, Sec. 3.2.1" "RFC 6513, Sec. 3.2.1"
::= { mvpnAdvtStatsEntry 1 } ::= { mvpnAdvtStatsEntry 1 }
mvpnAdvtPeerAddrType OBJECT-TYPE mvpnAdvtPeerAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InternetAddressType of the mvpnAdvtPeerAddr object "The InternetAddressType of the mvpnAdvtPeerAddr object
that follows. that follows.
" "
skipping to change at page 24, line 27 skipping to change at page 24, line 30
mvpnAdvtSent OBJECT-TYPE mvpnAdvtSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of advertisements successfully "The number of advertisements successfully
sent to the peer PE specified by the corresponding sent to the peer PE specified by the corresponding
mvpnAdvtPeerAddr. mvpnAdvtPeerAddr.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnAdvtCounterDiscontinuityTime object. mvpnAdvtCounterDiscontinuityTime object.
" "
::= { mvpnAdvtStatsEntry 4 } ::= { mvpnAdvtStatsEntry 4 }
mvpnAdvtReceived OBJECT-TYPE mvpnAdvtReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of advertisements received from the peer PE "The number of advertisements received from the peer PE
specified by the corresponding mvpnAdvtPeerAddr object. specified by the corresponding mvpnAdvtPeerAddr object.
This includes advertisements that were discarded. This includes advertisements that were discarded.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnAdvtCounterDiscontinuityTime object. mvpnAdvtCounterDiscontinuityTime object.
" "
::= { mvpnAdvtStatsEntry 5 } ::= { mvpnAdvtStatsEntry 5 }
mvpnAdvtReceivedError OBJECT-TYPE mvpnAdvtReceivedError OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of advertisements received from a peer PE, "The total number of advertisements received from a peer PE,
specified by the corresponding mvpnAdvtPeerAddr object, specified by the corresponding mvpnAdvtPeerAddr object,
that were rejected due to error(s) in the advertisement. that were rejected due to an error(s) in the advertisement.
The value of this object includes The value of this object includes
the error cases counted in the corresponding the error cases counted in the corresponding
mvpnAdvtReceivedMalformedTunnelType and mvpnAdvtReceivedMalformedTunnelType and
mvpnAdvtReceivedMalformedTunnelId objects. mvpnAdvtReceivedMalformedTunnelId objects.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnAdvtCounterDiscontinuityTime object. mvpnAdvtCounterDiscontinuityTime object.
" "
::= { mvpnAdvtStatsEntry 6 } ::= { mvpnAdvtStatsEntry 6 }
mvpnAdvtReceivedMalformedTunnelType OBJECT-TYPE mvpnAdvtReceivedMalformedTunnelType OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of advertisements received from the peer PE "The total number of advertisements received from the peer PE,
specified by the corresponding mvpnAdvtPeerAddr object, specified by the corresponding mvpnAdvtPeerAddr object,
that were rejected due to malformed Tunnel Type that were rejected due to a malformed Tunnel Type
in the PMSI Tunnel attribute. in the PMSI Tunnel attribute.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnAdvtCounterDiscontinuityTime object. mvpnAdvtCounterDiscontinuityTime object.
" "
REFERENCE REFERENCE
"RFC6514 Sec.5" "RFC 6514, Section 5"
::= { mvpnAdvtStatsEntry 7 } ::= { mvpnAdvtStatsEntry 7 }
mvpnAdvtReceivedMalformedTunnelId OBJECT-TYPE mvpnAdvtReceivedMalformedTunnelId OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of advertisements received from the peer PE "The total number of advertisements received from the peer PE,
specified by the corresponding mvpnAdvtPeerAddr object, specified by the corresponding mvpnAdvtPeerAddr object,
that were rejected due to malformed Tunnel Identifier that were rejected due to a malformed Tunnel Identifier
in the PMSI Tunnel attribute. in the PMSI Tunnel attribute. Discontinuities in the value
Discontinuities in the value of this counter can of this counter can occur at re-initialization of the
occur at re-initialization of the management system, management system and at other times as indicated by the
and at other times as indicated by the corresponding corresponding mvpnAdvtCounterDiscontinuityTime object.
mvpnAdvtCounterDiscontinuityTime object.
" "
REFERENCE REFERENCE
"RFC6514 Sec.5" "RFC 6514, Section 5"
::= { mvpnAdvtStatsEntry 8 } ::= { mvpnAdvtStatsEntry 8 }
mvpnAdvtLastSentTime OBJECT-TYPE mvpnAdvtLastSentTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The timestamp when the last advertisement "The timestamp when the last advertisement
was successfully sent by this PE. was successfully sent by this PE. If no
If no advertisement has been sent since the advertisement has been sent since the
last re-initialization of this PE, then this last re-initialization of this PE, this
object will have a zero-length string. object will have a zero-length string.
" "
::= { mvpnAdvtStatsEntry 9 } ::= { mvpnAdvtStatsEntry 9 }
mvpnAdvtLastReceivedTime OBJECT-TYPE mvpnAdvtLastReceivedTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The timestamp when the last advertisement "The timestamp when the last advertisement
was successfully received from the peer PE specified was successfully received from the peer PE specified
by the corresponding mvpnAdvtPeerAddr object and by the corresponding mvpnAdvtPeerAddr object and
processed by this PE. processed by this PE.
If no advertisement has been received since the If no advertisement has been received since the
last re-initialization of this PE, then this last re-initialization of this PE, this object
object will have a zero-length string. will have a zero-length string.
" "
::= { mvpnAdvtStatsEntry 10 } ::= { mvpnAdvtStatsEntry 10 }
mvpnAdvtCounterDiscontinuityTime OBJECT-TYPE mvpnAdvtCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion "The value of sysUpTime on the most recent occasion
at which any one or more of this application's at which any one or more of this application's
counters, viz., counters with OID prefix counters, viz., counters with the OID prefix
'mvpnAdvtSent' or 'mvpnAdvtSent', 'mvpnAdvtReceived',
'mvpnAdvtReceived' or 'mvpnAdvtReceivedError',
'mvpnAdvtReceivedError' or 'mvpnAdvtReceivedMalformedTunnelType', or
'mvpnAdvtReceivedMalformedTunnelType' or 'mvpnAdvtReceivedMalformedTunnelId', suffered a
'mvpnAdvtReceivedMalformedTunnelId' suffered a
discontinuity. discontinuity.
If no such discontinuities have occurred since the If no such discontinuities have occurred since the
last re-initialization of the local management last re-initialization of the local management
subsystem, then this object will have a zero value. subsystem, this object will have a zero value.
" "
::= { mvpnAdvtStatsEntry 11 } ::= { mvpnAdvtStatsEntry 11 }
-- Table of multicast routes in an MVPN -- Table of Multicast Routes in an MVPN
mvpnMrouteTable OBJECT-TYPE mvpnMrouteTable OBJECT-TYPE
SYNTAX SEQUENCE OF MvpnMrouteEntry SYNTAX SEQUENCE OF MvpnMrouteEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual table containing multicast routing information "A conceptual table containing multicast routing information
corresponding to the MVRFs present on the PE. corresponding to the MVRFs present on the PE.
" "
::= { mvpnObjects 7 } ::= { mvpnObjects 7 }
mvpnMrouteEntry OBJECT-TYPE mvpnMrouteEntry OBJECT-TYPE
SYNTAX MvpnMrouteEntry SYNTAX MvpnMrouteEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row corresponding to a route for IP datagrams "A conceptual row corresponding to a route for IP datagrams
from a particular source and addressed to a particular IP from a particular source and addressed to a particular
multicast group address. IP multicast group address.
Implementers need to be aware that if the total number of Implementers need to be aware that if the total number of
octets in mplsL3VpnVrfName, mvpnMrouteCmcastGroupAddr and octets in mplsL3VpnVrfName, mvpnMrouteCmcastGroupAddr, and
mvpnMrouteCmcastSourceAddrs exceeds 113, the OIDs of column mvpnMrouteCmcastSourceAddrs exceeds 113, the OIDs of column
instances in this row will have more than 128 sub-identifiers instances in this row will have more than 128 sub-identifiers
and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
" "
INDEX { INDEX {
mplsL3VpnVrfName, mplsL3VpnVrfName,
mvpnMrouteCmcastGroupAddrType, mvpnMrouteCmcastGroupAddrType,
mvpnMrouteCmcastGroupAddr, mvpnMrouteCmcastGroupAddr,
mvpnMrouteCmcastGroupPrefixLength, mvpnMrouteCmcastGroupPrefixLength,
mvpnMrouteCmcastSourceAddrType, mvpnMrouteCmcastSourceAddrType,
skipping to change at page 28, line 43 skipping to change at page 28, line 49
"The InetAddressType of the mvpnMrouteCmcastGroupAddr object "The InetAddressType of the mvpnMrouteCmcastGroupAddr object
that follows. that follows.
" "
::= { mvpnMrouteEntry 1 } ::= { mvpnMrouteEntry 1 }
mvpnMrouteCmcastGroupAddr OBJECT-TYPE mvpnMrouteCmcastGroupAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP multicast group address which, along with "The IP multicast group address that, along with
the corresponding mvpnMrouteCmcastGroupPrefixLength object, the corresponding mvpnMrouteCmcastGroupPrefixLength object,
identifies destinations for which this entry contains identifies destinations for which this entry contains
multicast routing information. multicast routing information.
This address object is only significant up to This address object is only significant up to
mvpnMrouteCmcastGroupPrefixLength bits. The remaining address mvpnMrouteCmcastGroupPrefixLength bits. The remaining
bits MUST be set to zero. address bits MUST be set to zero.
For addresses of type 'ipv4z' or 'ipv6z', the appended zone For addresses of type 'ipv4z' or 'ipv6z', the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicates that this
forwarding state applies only within the given zone. Zone forwarding state applies only within the given zone. Zone
index zero is not valid in this table. index zero is not valid in this table.
" "
::= { mvpnMrouteEntry 2 } ::= { mvpnMrouteEntry 2 }
mvpnMrouteCmcastGroupPrefixLength OBJECT-TYPE mvpnMrouteCmcastGroupPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which, along with "The length in bits of the mask that, along with
the corresponding mvpnMrouteCmcastGroupAddr object, the corresponding mvpnMrouteCmcastGroupAddr object,
identifies destinations for which this entry contains identifies destinations for which this entry contains
multicast routing information. multicast routing information.
If the corresponding InetAddressType is 'ipv4' or 'ipv4z', If the corresponding InetAddressType is 'ipv4' or 'ipv4z',
this object must be in the range 4..32. this object must be in the range 4..32.
If the corresponding InetAddressType is 'ipv6' or 'ipv6z', If the corresponding InetAddressType is 'ipv6' or 'ipv6z',
this object must be in the range 8..128. this object must be in the range 8..128.
" "
::= { mvpnMrouteEntry 3 } ::= { mvpnMrouteEntry 3 }
mvpnMrouteCmcastSourceAddrType OBJECT-TYPE mvpnMrouteCmcastSourceAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the mvpnMrouteCmcastSourceAddrs object "The InetAddressType of the mvpnMrouteCmcastSourceAddrs object
that follows. that follows.
A value of unknown(0) indicates a non-source-specific entry, A value of unknown(0) indicates a non-source-specific entry,
corresponding to all sources in the group. Otherwise, the corresponding to all sources in the group. Otherwise, the
value MUST be the same as the value of value MUST be the same as the value of
mvpnMrouteCmcastGroupAddrType. mvpnMrouteCmcastGroupAddrType.
" "
::= { mvpnMrouteEntry 4 } ::= { mvpnMrouteEntry 4 }
mvpnMrouteCmcastSourceAddrs OBJECT-TYPE mvpnMrouteCmcastSourceAddrs OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network address which, along with the "The network address that, along with the
corresponding mvpnMrouteCmcastSourcePrefixLength object, corresponding mvpnMrouteCmcastSourcePrefixLength object,
identifies the sources for which this entry contains identifies the sources for which this entry contains
multicast routing information. multicast routing information.
This address object is only significant up to This address object is only significant up to
mvpnMrouteCmcastSourcePrefixLength bits. mvpnMrouteCmcastSourcePrefixLength bits.
The remaining address bits MUST be set to zero. The remaining address bits MUST be set to zero.
For addresses of type 'ipv4z' or 'ipv6z', the appended zone For addresses of type 'ipv4z' or 'ipv6z', the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicates that this
source address applies only within the given zone. Zone source address applies only within the given zone. Zone
index zero is not valid in this table. index zero is not valid in this table.
" "
::= { mvpnMrouteEntry 5 } ::= { mvpnMrouteEntry 5 }
mvpnMrouteCmcastSourcePrefixLength OBJECT-TYPE mvpnMrouteCmcastSourcePrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which, along with "The length in bits of the mask that, along with
the corresponding mvpnMrouteCmcastSourceAddr object, the corresponding mvpnMrouteCmcastSourceAddr object,
identifies the sources for which this entry contains identifies the sources for which this entry contains
multicast routing information. multicast routing information.
If the corresponding InetAddressType is 'ipv4' or 'ipv4z', If the corresponding InetAddressType is 'ipv4' or 'ipv4z',
this object must be in the range 4..32. this object must be in the range 4..32.
If the corresponding InetAddressType is 'ipv6' or 'ipv6z', If the corresponding InetAddressType is 'ipv6' or 'ipv6z',
this object must be in the range 8..128. this object must be in the range 8..128.
If the corresponding InetAddressType is 'unknown', If the corresponding InetAddressType is 'unknown',
this object must be zero. this object must be zero.
skipping to change at page 30, line 46 skipping to change at page 30, line 50
mvpnMrouteUpstreamNeighborAddrType OBJECT-TYPE mvpnMrouteUpstreamNeighborAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the mvpnMrouteUpstreamNeighborAddr "The InetAddressType of the mvpnMrouteUpstreamNeighborAddr
object that follows. object that follows.
A value of unknown(0) indicates that the upstream A value of unknown(0) indicates that the upstream
neighbor is unknown, for example in BIDIR-PIM." neighbor is unknown, for example, in
Bidirectional PIM (BIDIR-PIM).
"
REFERENCE REFERENCE
"RFC 5015" "RFC 5015"
::= { mvpnMrouteEntry 7 } ::= { mvpnMrouteEntry 7 }
mvpnMrouteUpstreamNeighborAddr OBJECT-TYPE mvpnMrouteUpstreamNeighborAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the upstream neighbor (for example, "The address of the upstream neighbor (for example,
Reverse Path Forwarding (RPF) neighbor) from which the Reverse Path Forwarding (RPF) neighbor) from
IP datagrams from these sources represented by which IP datagrams from these sources represented
this entry to this multicast address are received. by this entry to this multicast address are received.
" "
::= { mvpnMrouteEntry 8 } ::= { mvpnMrouteEntry 8 }
mvpnMrouteInIfIndex OBJECT-TYPE mvpnMrouteInIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of ifIndex for the interface on which IP "The value of ifIndex for the interface on which IP
datagrams sent by these sources represented by this entry to datagrams sent by these sources represented by this entry to
this multicast address are received. this multicast address are received.
A value 0 indicates that datagrams are not A value of zero indicates that datagrams are not
subject to an incoming interface check, but may be accepted subject to an incoming interface check but may be accepted
on multiple interfaces (for example, in BIDIR-PIM). on multiple interfaces (for example, in BIDIR-PIM).
" "
REFERENCE REFERENCE
"RFC 5015" "RFC 5015"
::= { mvpnMrouteEntry 9 } ::= { mvpnMrouteEntry 9 }
mvpnMrouteExpiryTime OBJECT-TYPE mvpnMrouteExpiryTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum amount of time remaining before this entry will "The minimum amount of time remaining before this entry will
be aged out. The value 0 indicates that the entry is not be aged out. The value zero indicates that the entry is not
subject to aging. If the corresponding mvpnMrouteNextHopState subject to aging. If the corresponding mvpnMrouteNextHopState
object is pruned(1), this object represents the remaining object is pruned(1), this object represents the remaining
time for the prune to expire after which the state will time for the prune to expire after which the state will
return to forwarding(2). return to forwarding(2).
If the corresponding mvpnMrouteNextHopState object is If the corresponding mvpnMrouteNextHopState object is
forwarding(2), this object indicates the time after which forwarding(2), this object indicates the time after which
this entry will be removed from the table. this entry will be removed from the table.
" "
::= { mvpnMrouteEntry 10 } ::= { mvpnMrouteEntry 10 }
mvpnMrouteProtocol OBJECT-TYPE mvpnMrouteProtocol OBJECT-TYPE
SYNTAX IANAipMRouteProtocol SYNTAX IANAipMRouteProtocol
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast routing protocol via which this multicast "The multicast routing protocol via which this multicast
forwarding entry was learned. forwarding entry was learned.
skipping to change at page 32, line 46 skipping to change at page 33, line 4
DESCRIPTION DESCRIPTION
"The address portion of the route used to find the upstream "The address portion of the route used to find the upstream
or parent interface for this multicast forwarding entry. or parent interface for this multicast forwarding entry.
This address object is only significant up to This address object is only significant up to
mvpnMrouteRtPrefixLength bits. The remaining address bits mvpnMrouteRtPrefixLength bits. The remaining address bits
MUST be set to zero. MUST be set to zero.
For addresses of type 'ipv4z' or 'ipv6z', the appended zone For addresses of type 'ipv4z' or 'ipv6z', the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicates that this
forwarding state applies only within the given zone. Zone forwarding state applies only within the given zone. Zone
index zero is not valid in this table. index zero is not valid in this table.
" "
::= { mvpnMrouteEntry 14 } ::= { mvpnMrouteEntry 14 }
mvpnMrouteRtPrefixLength OBJECT-TYPE mvpnMrouteRtPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 33, line 37 skipping to change at page 33, line 42
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The reason for placing the route in the (logical) "The reason for placing the route in the (logical)
multicast Routing Information Base (RIB). multicast Routing Information Base (RIB).
The enumerated reasons and the corresponding The enumerated reasons and the corresponding
descriptions are as follows: descriptions are as follows:
unicast: unicast:
The route would normally be placed only in The route would normally be placed only in
the unicast RIB, but was placed in the multicast RIB the unicast RIB, but it was placed in the multicast
by local configuration, such as when running PIM over RIB by local configuration, such as when running
RIP. PIM over RIP.
multicast: multicast:
The route was explicitly added to the multicast RIB by The route was explicitly added to the multicast RIB by
the routing protocol, such as the Distance Vector the routing protocol, such as the Distance Vector
Multicast Routing Protocol (DVMRP) or Multiprotocol BGP. Multicast Routing Protocol (DVMRP) or Multiprotocol BGP.
" "
::= { mvpnMrouteEntry 16 } ::= { mvpnMrouteEntry 16 }
mvpnMrouteOctets OBJECT-TYPE mvpnMrouteOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets contained in IP datagrams that were "The number of octets contained in IP datagrams that were
received from sources represented by this entry and received from sources represented by this entry and
addressed to this multicast group address, and which were addressed to this multicast group address and that were
forwarded by this router. forwarded by this router.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnMrouteCounterDiscontinuityTime object. mvpnMrouteCounterDiscontinuityTime object.
" "
::= { mvpnMrouteEntry 17 } ::= { mvpnMrouteEntry 17 }
mvpnMroutePkts OBJECT-TYPE mvpnMroutePkts OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets routed using this multicast route "The number of packets routed using this multicast route
entry. entry.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnMrouteCounterDiscontinuityTime object. mvpnMrouteCounterDiscontinuityTime object.
" "
::= { mvpnMrouteEntry 18 } ::= { mvpnMrouteEntry 18 }
mvpnMrouteTtlDroppedOctets OBJECT-TYPE mvpnMrouteTtlDroppedOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets contained in IP datagrams that this "The number of octets contained in IP datagrams that this
router has received from sources represented by router has received from sources represented by
this entry and addressed to this multicast group address, this entry and addressed to this multicast group address,
which were dropped due to Time To Live (TTL) issues. which were dropped due to Time To Live (TTL) issues.
TTL issues occur when the TTL (IPv4) or Hop Limit (IPv6) TTL issues occur when the TTL (IPv4) or Hop Limit (IPv6)
of the incoming packet was decremented to zero, or to a of the incoming packet was decremented to zero or to a
value less than ipMcastInterfaceTtl of the corresponding value less than ipMcastInterfaceTtl of the corresponding
interface. interface.
The ipMcastInterfaceTtl object is defined in IPMCAST-MIB The ipMcastInterfaceTtl object is defined in IPMCAST-MIB
[RFC5132] and represents the datagram TTL (RFC 5132) and represents the datagram TTL
threshold for the interface. Any IP multicast datagrams threshold for the interface. Any IP multicast datagrams
with a TTL (IPv4) or Hop Limit (IPv6) less than this with a TTL (IPv4) or Hop Limit (IPv6) less than this
threshold will not be forwarded out of the interface. threshold will not be forwarded out of the interface.
The default value of 0 means all multicast packets are The default value of zero means all multicast packets are
forwarded out of the interface. A value of 256 means that forwarded out of the interface. A value of 256 means that
no multicast packets are forwarded out of the interface. no multicast packets are forwarded out of the interface.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnMrouteCounterDiscontinuityTime object. mvpnMrouteCounterDiscontinuityTime object.
" "
REFERENCE REFERENCE
"RFC5132, Sec. 6 "RFC 5132, Section 6
" "
::= { mvpnMrouteEntry 19 } ::= { mvpnMrouteEntry 19 }
mvpnMrouteTtlDroppedPackets OBJECT-TYPE mvpnMrouteTtlDroppedPackets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets that this router has received from "The number of packets that this router has received from
the sources represented by this entry and addressed to this the sources represented by this entry and addressed to this
multicast group address, which were dropped due to multicast group address, which were dropped due to
Time To Live (TTL) issues. TTL issues occur when the Time To Live (TTL) issues. TTL issues occur when the
TTL (IPv4) or Hop Limit (IPv6) of the incoming packet was TTL (IPv4) or Hop Limit (IPv6) of the incoming packet was
decremented to zero, or to a value less than decremented to zero or to a value less than
ipMcastInterfaceTtl of the corresponding interface. ipMcastInterfaceTtl of the corresponding interface.
The ipMcastInterfaceTtl object is defined in IPMCAST-MIB The ipMcastInterfaceTtl object is defined in IPMCAST-MIB
[RFC5132] and represents the datagram TTL (RFC 5132) and represents the datagram TTL
threshold for the interface. Any IP multicast datagrams threshold for the interface. Any IP multicast datagrams
with a TTL (IPv4) or Hop Limit (IPv6) less than this with a TTL (IPv4) or Hop Limit (IPv6) less than this
threshold will not be forwarded out of the interface. threshold will not be forwarded out of the interface.
The default value of 0 means all multicast packets are The default value of zero means all multicast packets are
forwarded out of the interface. A value of 256 means that forwarded out of the interface. A value of 256 means that
no multicast packets are forwarded out of the interface. no multicast packets are forwarded out of the interface.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnMrouteCounterDiscontinuityTime object. mvpnMrouteCounterDiscontinuityTime object.
" "
REFERENCE REFERENCE
"RFC5132, Sec. 6 "RFC 5132, Section 6
" "
::= { mvpnMrouteEntry 20 } ::= { mvpnMrouteEntry 20 }
mvpnMrouteDroppedInOctets OBJECT-TYPE mvpnMrouteDroppedInOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets contained in IP datagrams that this "The number of octets contained in IP datagrams that this
router has received from sources represented by router has received from sources represented by
this entry and addressed to this multicast group address, this entry and addressed to this multicast group address,
which were dropped due to error(s). which were dropped due to an error(s).
The value of this object includes the octets counted The value of this object includes the octets counted
in the corresponding mvpnMrouteTtlDroppedOctets object. in the corresponding mvpnMrouteTtlDroppedOctets object.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnMrouteCounterDiscontinuityTime object. mvpnMrouteCounterDiscontinuityTime object.
" "
::= { mvpnMrouteEntry 21 } ::= { mvpnMrouteEntry 21 }
mvpnMrouteDroppedInPackets OBJECT-TYPE mvpnMrouteDroppedInPackets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets which this router has received from "The number of packets that this router has received from
sources represented by this entry and addressed to this sources represented by this entry and addressed to this
multicast group address, which were dropped due to error(s). multicast group address, which were dropped due to an
The value of this object includes the number of octets error(s). The value of this object includes the number
counted in the corresponding mvpnMrouteTtlDroppedPackets of octets counted in the corresponding
object. mvpnMrouteTtlDroppedPackets object.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnMrouteCounterDiscontinuityTime object. mvpnMrouteCounterDiscontinuityTime object.
" "
::= { mvpnMrouteEntry 22 } ::= { mvpnMrouteEntry 22 }
mvpnMroutePmsiPointer OBJECT-TYPE mvpnMroutePmsiPointer OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pointer to a conceptual row representing "A pointer to a conceptual row representing
the corresponding I-PMSI in mvpnPmsiTable or S-PMSI the corresponding I-PMSI in mvpnPmsiTable or S-PMSI
in mvpnSpmsiTable, that this C-multicast route is using. in mvpnSpmsiTable that this C-multicast route is using.
" "
::= { mvpnMrouteEntry 23 } ::= { mvpnMrouteEntry 23 }
mvpnMrouteNumberOfLocalReplication OBJECT-TYPE mvpnMrouteNumberOfLocalReplication OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of replications for local receivers. "Number of replications for local receivers.
For example, if an ingress PE needs to send traffic out of For example, if an ingress PE needs to send traffic out of
N PE-CE interfaces, then mvpnMrouteNumberOfLocalReplication N PE-CE interfaces, then mvpnMrouteNumberOfLocalReplication
is N. is N.
" "
::= { mvpnMrouteEntry 24 } ::= { mvpnMrouteEntry 24 }
mvpnMrouteNumberOfRemoteReplication OBJECT-TYPE mvpnMrouteNumberOfRemoteReplication OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of local replications for remote PEs. For example, "Number of local replications for remote PEs. For example,
if the number of remote PEs that need to receive traffic is N, if the number of remote PEs that need to receive traffic is N,
then mvpnMrouteNumberOfRemoteReplication is N in case of then mvpnMrouteNumberOfRemoteReplication is N in case of
Ingress Replication, but may be less than N in case of RSVP-TE Ingress Replication, but it may be less than N in case of
or mLDP P2MP tunnels, depending on the actual number of RSVP-TE or mLDP Point-to-Multipoint (P2MP) tunnels, depending
replications the PE needs to do. on the actual number of replications the PE needs to do.
" "
::= { mvpnMrouteEntry 25 } ::= { mvpnMrouteEntry 25 }
mvpnMrouteCounterDiscontinuityTime OBJECT-TYPE mvpnMrouteCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion "The value of sysUpTime on the most recent occasion
at which any one or more of this application's at which any one or more of this application's
counters, viz., counters with OID prefix counters, viz., counters with the OID prefix
'mvpnMrouteOctets' or 'mvpnMroutePkts' or 'mvpnMrouteOctets', 'mvpnMroutePkts',
'mvpnMrouteTtlDroppedOctets' or 'mvpnMrouteTtlDroppedOctets',
'mvpnMrouteTtlDroppedPackets' or 'mvpnMrouteTtlDroppedPackets',
'mvpnMrouteDroppedInOctets' or 'mvpnMrouteDroppedInPackets' 'mvpnMrouteDroppedInOctets', or 'mvpnMrouteDroppedInPackets',
suffered a discontinuity. suffered a discontinuity.
If no such discontinuities have occurred since the If no such discontinuities have occurred since the
last re-initialization of the local management last re-initialization of the local management
subsystem, then this object will have a zero value. subsystem, this object will have a zero value.
" "
::= { mvpnMrouteEntry 26 } ::= { mvpnMrouteEntry 26 }
-- Table of next hops for multicast routes in an MVPN -- Table of Next Hops for Multicast Routes in an MVPN
mvpnMrouteNextHopTable OBJECT-TYPE mvpnMrouteNextHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF MvpnMrouteNextHopEntry SYNTAX SEQUENCE OF MvpnMrouteNextHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual table containing information on the "A conceptual table containing information on the
next-hops for routing IP multicast datagrams. next hops for routing IP multicast datagrams.
Each entry is one of a list of next-hops for Each entry is one of a list of next hops for
a set of sources sending to a multicast group a set of sources sending to a multicast group
address. address.
" "
::= { mvpnObjects 8 } ::= { mvpnObjects 8 }
mvpnMrouteNextHopEntry OBJECT-TYPE mvpnMrouteNextHopEntry OBJECT-TYPE
SYNTAX MvpnMrouteNextHopEntry SYNTAX MvpnMrouteNextHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row corresponding to a next-hop to which "A conceptual row corresponding to a next hop to which
IP multicast datagrams from a set of sources to IP multicast datagrams from a set of sources to
an IP multicast group address are routed. an IP multicast group address are routed.
Implementers need to be aware that if the total number of Implementers need to be aware that if the total number of
octets in mplsL3VpnVrfName, mvpnMrouteNextHopGroupAddr, octets in mplsL3VpnVrfName, mvpnMrouteNextHopGroupAddr,
mvpnMrouteNextHopSourceAddrs, and mvpnMrouteNextHopAddr mvpnMrouteNextHopSourceAddrs, and mvpnMrouteNextHopAddr
exceeds 111, the OIDs of column instances in this row exceeds 111, the OIDs of column instances in this row
will have more than 128 sub-identifiers and cannot be will have more than 128 sub-identifiers and cannot be
accessed using SNMPv1, SNMPv2c, or SNMPv3. accessed using SNMPv1, SNMPv2c, or SNMPv3.
" "
skipping to change at page 39, line 29 skipping to change at page 39, line 35
"The InetAddressType of the mvpnMrouteNextHopGroupAddr object "The InetAddressType of the mvpnMrouteNextHopGroupAddr object
that follows. that follows.
" "
::= { mvpnMrouteNextHopEntry 1 } ::= { mvpnMrouteNextHopEntry 1 }
mvpnMrouteNextHopGroupAddr OBJECT-TYPE mvpnMrouteNextHopGroupAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP multicast group address which, along with "The IP multicast group address that, along with
the corresponding mvpnMrouteNextHopGroupPrefixLength object, the corresponding mvpnMrouteNextHopGroupPrefixLength object,
identifies destinations for which this entry contains identifies destinations for which this entry contains
multicast forwarding information. multicast forwarding information.
This address object is only significant up to This address object is only significant up to
mvpnMrouteNextHopGroupPrefixLength bits. The remaining mvpnMrouteNextHopGroupPrefixLength bits. The remaining
address bits MUST be set to zero. address bits MUST be set to zero.
For addresses of type 'ipv4z' or 'ipv6z', the appended zone For addresses of type 'ipv4z' or 'ipv6z', the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicates that this
forwarding state applies only within the given zone. Zone forwarding state applies only within the given zone. Zone
index zero is not valid in this table. index zero is not valid in this table.
" "
::= { mvpnMrouteNextHopEntry 2 } ::= { mvpnMrouteNextHopEntry 2 }
mvpnMrouteNextHopGroupPrefixLength OBJECT-TYPE mvpnMrouteNextHopGroupPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which, along with "The length in bits of the mask that, along with
the corresponding mvpnMrouteGroupAddr object, the corresponding mvpnMrouteGroupAddr object,
identifies destinations for which this entry contains identifies destinations for which this entry contains
multicast routing information. multicast routing information.
If the corresponding InetAddressType is 'ipv4' or 'ipv4z', If the corresponding InetAddressType is 'ipv4' or 'ipv4z',
this object must be in the range 4..32. this object must be in the range 4..32.
If the corresponding InetAddressType is 'ipv6' or 'ipv6z', If the corresponding InetAddressType is 'ipv6' or 'ipv6z',
this object must be in the range 8..128. this object must be in the range 8..128.
" "
::= { mvpnMrouteNextHopEntry 3 } ::= { mvpnMrouteNextHopEntry 3 }
mvpnMrouteNextHopSourceAddrType OBJECT-TYPE mvpnMrouteNextHopSourceAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of mvpnMrouteNextHopSourceAddrs object "The InetAddressType of the mvpnMrouteNextHopSourceAddrs
that follows. object that follows.
A value of unknown(0) indicates a non-source-specific entry, A value of unknown(0) indicates a non-source-specific entry,
corresponding to all sources in the group. Otherwise, the corresponding to all sources in the group. Otherwise, the
value MUST be the same as the value of value MUST be the same as the value of
mvpnMrouteNextHopGroupAddrType." mvpnMrouteNextHopGroupAddrType.
"
::= { mvpnMrouteNextHopEntry 4 } ::= { mvpnMrouteNextHopEntry 4 }
mvpnMrouteNextHopSourceAddrs OBJECT-TYPE mvpnMrouteNextHopSourceAddrs OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network address which, along with the "The network address that, along with the
corresponding mvpnMrouteNextHopSourcePrefixLength object, corresponding mvpnMrouteNextHopSourcePrefixLength object,
identifies the sources for which this entry specifies identifies the sources for which this entry specifies
a next-hop. a next hop.
This address object is only significant up to This address object is only significant up to
mvpnMrouteNextHopSourcePrefixLength bits. The remaining mvpnMrouteNextHopSourcePrefixLength bits. The remaining
address bits MUST be set to zero. address bits MUST be set to zero.
For addresses of type 'ipv4z' or 'ipv6z', the appended zone For addresses of type 'ipv4z' or 'ipv6z', the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicates that this
source address applies only within the given zone. Zone source address applies only within the given zone. Zone
index zero is not valid in this table. index zero is not valid in this table.
" "
::= { mvpnMrouteNextHopEntry 5 } ::= { mvpnMrouteNextHopEntry 5 }
mvpnMrouteNextHopSourcePrefixLength OBJECT-TYPE mvpnMrouteNextHopSourcePrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which, along with "The length in bits of the mask that, along with
the corresponding mvpnMrouteNextHopSourceAddrs object, the corresponding mvpnMrouteNextHopSourceAddrs object,
identifies the sources for which this entry specifies identifies the sources for which this entry specifies
a next-hop. a next hop.
If the corresponding InetAddressType is 'ipv4' or 'ipv4z', If the corresponding InetAddressType is 'ipv4' or 'ipv4z',
this object must be in the range 4..32. this object must be in the range 4..32.
If the corresponding InetAddressType is 'ipv6' or 'ipv6z', If the corresponding InetAddressType is 'ipv6' or 'ipv6z',
this object must be in the range 8..128. this object must be in the range 8..128.
If the corresponding InetAddressType is 'unknown', If the corresponding InetAddressType is 'unknown',
this object must be zero. this object must be zero.
" "
::= { mvpnMrouteNextHopEntry 6 } ::= { mvpnMrouteNextHopEntry 6 }
mvpnMrouteNextHopIfIndex OBJECT-TYPE mvpnMrouteNextHopIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value of the outgoing interface "The ifIndex value of the outgoing interface
for this next-hop. for this next hop.
" "
::= { mvpnMrouteNextHopEntry 7 } ::= { mvpnMrouteNextHopEntry 7 }
mvpnMrouteNextHopAddrType OBJECT-TYPE mvpnMrouteNextHopAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the mvpnMrouteNextHopAddr object "The InetAddressType of the mvpnMrouteNextHopAddr object
that follows. that follows.
" "
::= { mvpnMrouteNextHopEntry 8 } ::= { mvpnMrouteNextHopEntry 8 }
mvpnMrouteNextHopAddr OBJECT-TYPE mvpnMrouteNextHopAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the next-hop specific to this entry. For "The address of the next hop specific to this entry. For
most interfaces, this is identical to most interfaces, this is identical to
mvpnMrouteNextHopGroupAddr. Non-Broadcast Multi-Access mvpnMrouteNextHopGroupAddr. Non-Broadcast Multi-Access
(NBMA) interfaces, however, may have multiple next-hop (NBMA) interfaces, however, may have multiple next-hop
addresses out of a single outgoing interface. addresses out of a single outgoing interface.
" "
::= { mvpnMrouteNextHopEntry 9 } ::= { mvpnMrouteNextHopEntry 9 }
mvpnMrouteNextHopState OBJECT-TYPE mvpnMrouteNextHopState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
pruned(1), pruned(1),
forwarding(2) forwarding(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 42, line 16 skipping to change at page 42, line 22
::= { mvpnMrouteNextHopEntry 9 } ::= { mvpnMrouteNextHopEntry 9 }
mvpnMrouteNextHopState OBJECT-TYPE mvpnMrouteNextHopState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
pruned(1), pruned(1),
forwarding(2) forwarding(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of whether the outgoing interface and next- "An indication of whether the outgoing interface and next
hop represented by this entry is currently being used to hop represented by this entry is currently being used to
forward IP datagrams. forward IP datagrams.
The enumerated states and the corresponding The enumerated states and the corresponding
descriptions are as follows: descriptions are as follows:
pruned : this entry is not currently being used. pruned : this entry is not currently being used.
forwarding : this entry is currently being used. forwarding : this entry is currently being used.
" "
::= { mvpnMrouteNextHopEntry 10 } ::= { mvpnMrouteNextHopEntry 10 }
mvpnMrouteNextHopExpiryTime OBJECT-TYPE mvpnMrouteNextHopExpiryTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum amount of time remaining before this entry will "The minimum amount of time remaining before this entry will
be aged out. If mvpnMrouteNextHopState is pruned(1), be aged out. If mvpnMrouteNextHopState is pruned(1),
this object represents the remaining time for the prune this object represents the remaining time for the prune
to expire after which the state will return to forwarding(2). to expire after which the state will return to forwarding(2).
If mvpnMrouteNextHopState is forwarding(2), If mvpnMrouteNextHopState is forwarding(2),
this object indicates the time after which this this object indicates the time after which this
entry will be removed from the table. entry will be removed from the table.
The value of 0 indicates that the entry is not subject to The value of zero indicates that the entry is not subject to
aging. aging.
" "
::= { mvpnMrouteNextHopEntry 11 } ::= { mvpnMrouteNextHopEntry 11 }
mvpnMrouteNextHopClosestMemberHops OBJECT-TYPE mvpnMrouteNextHopClosestMemberHops OBJECT-TYPE
SYNTAX Unsigned32 (0..256) SYNTAX Unsigned32 (0..256)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum number of hops between this router and any "The minimum number of hops between this router and any
member of this IP multicast group reached via this next-hop member of this IP multicast group reached via this next hop
on the corresponding outgoing interface. Any IP multicast on the corresponding outgoing interface. Any IP multicast
datagram for the group that has a TTL (IPv4) or Hop Count datagram for the group that has a TTL (IPv4) or a Hop Count
(IPv6) less than mvpnMrouteNextHopClosestMemberHops will (IPv6) less than mvpnMrouteNextHopClosestMemberHops will
not be forwarded through this interface. not be forwarded through this interface.
A value of 0 means all multicast datagrams are forwarded out A value of zero means all multicast datagrams are forwarded
of the interface. A value of 256 means that no multicast out of the interface. A value of 256 means that no multicast
datagrams are forwarded out of the interface. datagrams are forwarded out of the interface.
This is an optimization applied by multicast routing This is an optimization applied by multicast routing
protocols that explicitly track hop counts to downstream protocols that explicitly track hop counts to downstream
listeners. Multicast protocols that are not aware of hop listeners. Multicast protocols that are not aware of hop
counts to downstream listeners set this object to 0. counts to downstream listeners set this object to zero.
" "
::= { mvpnMrouteNextHopEntry 12 } ::= { mvpnMrouteNextHopEntry 12 }
mvpnMrouteNextHopProtocol OBJECT-TYPE mvpnMrouteNextHopProtocol OBJECT-TYPE
SYNTAX IANAipMRouteProtocol SYNTAX IANAipMRouteProtocol
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The routing protocol via which this next-hop was learned." "The routing protocol via which this next hop was learned.
"
::= { mvpnMrouteNextHopEntry 13 } ::= { mvpnMrouteNextHopEntry 13 }
mvpnMrouteNextHopOctets OBJECT-TYPE mvpnMrouteNextHopOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of multicast packets that have been "The number of octets of multicast packets that have been
forwarded using this route. forwarded using this route.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnMrouteNextHopCounterDiscontinuityTime object. mvpnMrouteNextHopCounterDiscontinuityTime object.
" "
::= { mvpnMrouteNextHopEntry 14 } ::= { mvpnMrouteNextHopEntry 14 }
mvpnMrouteNextHopPkts OBJECT-TYPE mvpnMrouteNextHopPkts OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets which have been forwarded using this "The number of packets that have been forwarded using this
route. route.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system
and at other times as indicated by the corresponding and at other times as indicated by the corresponding
mvpnMrouteNextHopCounterDiscontinuityTime object. mvpnMrouteNextHopCounterDiscontinuityTime object.
" "
::= { mvpnMrouteNextHopEntry 15 } ::= { mvpnMrouteNextHopEntry 15 }
mvpnMrouteNextHopCounterDiscontinuityTime OBJECT-TYPE mvpnMrouteNextHopCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion "The value of sysUpTime on the most recent occasion
at which any one or more of this application's at which any one or more of this application's
counters, viz., counters with OID prefix counters, viz., counters with the OID prefix
'mvpnMrouteNextHopOctets' or 'mvpnMrouteNextHopPackets' 'mvpnMrouteNextHopOctets' or 'mvpnMrouteNextHopPackets',
suffered a discontinuity. suffered a discontinuity.
If no such discontinuities have occurred since the If no such discontinuities have occurred since the
last re-initialization of the local management last re-initialization of the local management
subsystem, then this object will have a zero value. subsystem, this object will have a zero value.
" "
::= { mvpnMrouteNextHopEntry 16 } ::= { mvpnMrouteNextHopEntry 16 }
-- MVPN Notifications -- MVPN Notifications
mvpnMvrfActionTaken NOTIFICATION-TYPE mvpnMvrfActionTaken NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mvpnGenMvrfCreationTime, mvpnGenMvrfCreationTime,
mvpnGenMvrfLastAction, mvpnGenMvrfLastAction,
mvpnGenMvrfLastActionTime, mvpnGenMvrfLastActionTime,
mvpnGenMvrfCreationTime, mvpnGenMvrfCreationTime,
mvpnGenCmcastRouteProtocol, mvpnGenCmcastRouteProtocol,
mvpnGenUmhSelection, mvpnGenUmhSelection,
mvpnGenCustomerSiteType mvpnGenCustomerSiteType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"mvpnMvrfActionTaken notifies about a change "mvpnMvrfActionTaken notifies about a change
in a MVRF on the PE. The change itself will be given by in an MVRF on the PE. The change itself will be given by
mvpnGenMvrfLastAction. mvpnGenMvrfLastAction.
" "
::= { mvpnNotifications 1 } ::= { mvpnNotifications 1 }
-- MVPN MIB Conformance Information -- MVPN MIB Conformance Information
mvpnGroups OBJECT IDENTIFIER ::= { mvpnConformance 1 } mvpnGroups OBJECT IDENTIFIER ::= { mvpnConformance 1 }
mvpnCompliances OBJECT IDENTIFIER ::= { mvpnConformance 2 } mvpnCompliances OBJECT IDENTIFIER ::= { mvpnConformance 2 }
-- Compliance Statements -- Compliance Statements
mvpnModuleFullCompliance MODULE-COMPLIANCE mvpnModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full support "Compliance statement for agents that provide full support
for the BGP-MPLS-LAYER3-VPN-MULTICAST-MIB for BGP-MPLS-LAYER3-VPN-MULTICAST-MIB.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mvpnScalarGroup, mvpnScalarGroup,
mvpnGenericGroup, mvpnGenericGroup,
mvpnPmsiGroup, mvpnPmsiGroup,
mvpnAdvtStatsGroup, mvpnAdvtStatsGroup,
mvpnMrouteGroup, mvpnMrouteGroup,
mvpnMrouteNextHopGroup, mvpnMrouteNextHopGroup,
mvpnNotificationGroup mvpnNotificationGroup
skipping to change at page 45, line 39 skipping to change at page 45, line 50
"This group is mandatory for systems that support "This group is mandatory for systems that support
BGP-MVPN. BGP-MVPN.
" "
::= { mvpnCompliances 1 } ::= { mvpnCompliances 1 }
mvpnModuleReadOnlyCompliance MODULE-COMPLIANCE mvpnModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "Compliance requirement for implementations that DESCRIPTION "Compliance requirement for implementations that
only provide read-only support for only provide read-only support for
BGP-MPLS-LAYER3-VPN-MULTICAST-MIB. Such devices BGP-MPLS-LAYER3-VPN-MULTICAST-MIB. Such devices
can then be monitored but cannot be configured can then be monitored but cannot be configured
using this MIB module. using this MIB module.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mvpnScalarGroup, mvpnScalarGroup,
mvpnGenericGroup, mvpnGenericGroup,
mvpnPmsiGroup, mvpnPmsiGroup,
mvpnAdvtStatsGroup, mvpnAdvtStatsGroup,
mvpnMrouteGroup, mvpnMrouteGroup,
mvpnMrouteNextHopGroup, mvpnMrouteNextHopGroup,
mvpnNotificationGroup mvpnNotificationGroup
skipping to change at page 47, line 9 skipping to change at page 47, line 17
OBJECT mvpnBgpMaxSrcActiveAdRouteFreq OBJECT mvpnBgpMaxSrcActiveAdRouteFreq
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
::= { mvpnCompliances 2 } ::= { mvpnCompliances 2 }
mvpnModuleAdvtStatsCompliance MODULE-COMPLIANCE mvpnModuleAdvtStatsCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support "Compliance statement for agents that support
monitoring of the statistics pertaining to the monitoring of the statistics pertaining
advertisements sent/received by a PE. to advertisements sent/received by a PE.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mvpnAdvtStatsGroup mvpnAdvtStatsGroup
} }
::= { mvpnCompliances 3 } ::= { mvpnCompliances 3 }
-- units of conformance -- Units of Conformance
mvpnScalarGroup OBJECT-GROUP mvpnScalarGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mvpnMvrfs, mvpnMvrfs,
mvpnV4Mvrfs, mvpnV4Mvrfs,
mvpnV6Mvrfs, mvpnV6Mvrfs,
mvpnPimV4Mvrfs, mvpnPimV4Mvrfs,
mvpnPimV6Mvrfs, mvpnPimV6Mvrfs,
mvpnSPTunnelLimit mvpnSPTunnelLimit
} }
skipping to change at page 47, line 48 skipping to change at page 48, line 9
OBJECTS { OBJECTS {
mvpnMldpMvrfs, mvpnMldpMvrfs,
mvpnBgpV4Mvrfs, mvpnBgpV4Mvrfs,
mvpnBgpV6Mvrfs, mvpnBgpV6Mvrfs,
mvpnBgpCmcastRouteWithdrawalTimer, mvpnBgpCmcastRouteWithdrawalTimer,
mvpnBgpSrcSharedTreeJoinTimer mvpnBgpSrcSharedTreeJoinTimer
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are used to monitor/manage "These objects are used to monitor/manage
BGP-MVPN specific global parameters. BGP-MVPN-specific global parameters.
" "
::= { mvpnGroups 2 } ::= { mvpnGroups 2 }
mvpnGenericGroup OBJECT-GROUP mvpnGenericGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mvpnGenMvrfLastAction, mvpnGenMvrfLastAction,
mvpnGenMvrfLastActionTime, mvpnGenMvrfLastActionTime,
mvpnGenMvrfCreationTime, mvpnGenMvrfCreationTime,
mvpnGenCmcastRouteProtocol, mvpnGenCmcastRouteProtocol,
mvpnGenIpmsiInfo, mvpnGenIpmsiInfo,
skipping to change at page 48, line 34 skipping to change at page 48, line 44
mvpnBgpSrcASExtendedCommunity, mvpnBgpSrcASExtendedCommunity,
mvpnBgpMsgRateLimit, mvpnBgpMsgRateLimit,
mvpnBgpMaxSpmsiAdRoutes, mvpnBgpMaxSpmsiAdRoutes,
mvpnBgpMaxSpmsiAdRouteFreq, mvpnBgpMaxSpmsiAdRouteFreq,
mvpnBgpMaxSrcActiveAdRoutes, mvpnBgpMaxSrcActiveAdRoutes,
mvpnBgpMaxSrcActiveAdRouteFreq mvpnBgpMaxSrcActiveAdRouteFreq
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are used to monitor/manage "These objects are used to monitor/manage
the MVPN-wise BGP specific parameters. MVPN-wise BGP-specific parameters.
" "
::= { mvpnGroups 4 } ::= { mvpnGroups 4 }
mvpnPmsiGroup OBJECT-GROUP mvpnPmsiGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mvpnPmsiRD, mvpnPmsiRD,
mvpnPmsiTunnelType, mvpnPmsiTunnelType,
mvpnPmsiTunnelAttribute, mvpnPmsiTunnelAttribute,
mvpnPmsiTunnelPimGroupAddrType, mvpnPmsiTunnelPimGroupAddrType,
mvpnPmsiTunnelPimGroupAddr, mvpnPmsiTunnelPimGroupAddr,
mvpnPmsiEncapsulationType, mvpnPmsiEncapsulationType,
mvpnSpmsiPmsiPointer mvpnSpmsiPmsiPointer
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are used to monitor "These objects are used to monitor
I-PMSIs and S-PMSIs tunnel on a PE. I-PMSI and S-PMSI tunnels on a PE.
" "
::= { mvpnGroups 5 } ::= { mvpnGroups 5 }
mvpnAdvtStatsGroup OBJECT-GROUP mvpnAdvtStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mvpnAdvtSent, mvpnAdvtSent,
mvpnAdvtReceived, mvpnAdvtReceived,
mvpnAdvtReceivedError, mvpnAdvtReceivedError,
mvpnAdvtReceivedMalformedTunnelType, mvpnAdvtReceivedMalformedTunnelType,
mvpnAdvtReceivedMalformedTunnelId, mvpnAdvtReceivedMalformedTunnelId,
skipping to change at page 50, line 21 skipping to change at page 50, line 31
mvpnMrouteNextHopExpiryTime, mvpnMrouteNextHopExpiryTime,
mvpnMrouteNextHopClosestMemberHops, mvpnMrouteNextHopClosestMemberHops,
mvpnMrouteNextHopProtocol, mvpnMrouteNextHopProtocol,
mvpnMrouteNextHopOctets, mvpnMrouteNextHopOctets,
mvpnMrouteNextHopPkts, mvpnMrouteNextHopPkts,
mvpnMrouteNextHopCounterDiscontinuityTime mvpnMrouteNextHopCounterDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are used to monitor the information on "These objects are used to monitor the information on
next-hops for routing datagrams to MVPNs on a PE. next hops for routing datagrams to MVPNs on a PE.
" "
::= { mvpnGroups 8 } ::= { mvpnGroups 8 }
mvpnNotificationGroup NOTIFICATION-GROUP mvpnNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
mvpnMvrfActionTaken mvpnMvrfActionTaken
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects required for MVPN notifications." "Objects required for MVPN notifications."
::= { mvpnGroups 9 } ::= { mvpnGroups 9 }
END END
4. Security Considerations 4. Security Considerations
This MIB module contains some read-only objects that may be deemed This MIB module contains some read-only objects that may be deemed
sensitive. It also contains some read-write objects, whose setting sensitive. It also contains some read-write objects whose settings
will change the device's MVPN related behavior. Appropriate security will change the device's MVPN-related behavior. Appropriate security
procedures related to SNMP in general but not specific to this MIB procedures that are related to SNMP in general but are not specific
module need to be implemented by concerned operators. to this MIB module need to be implemented by concerned operators.
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write. Such objects may be with a MAX-ACCESS clause of read-write. Such objects may be
considered sensitive or vulnerable in some network environments. The considered sensitive or vulnerable in some network environments. The
support for SET operations in a non-secure environment without proper support for SET operations in a non-secure environment without proper
protection opens devices to attack. These are the tables and objects protection opens devices to attack. These are the tables and objects
and their sensitivity/vulnerability: and their sensitivity/vulnerability:
o mvpnSPTunnelLimit o mvpnSPTunnelLimit
The value of this object is used to control the maximum number of The value of this object is used to control the maximum number of
selective provider tunnels that a PE allows for a particular MVPN. selective provider tunnels that a PE allows for a particular MVPN.
Access to this object may be abused to impact the performance of Access to this object may be abused to impact the performance of
the PE or prevent the PE from having new selective provider the PE or prevent the PE from having new selective provider
tunnels. tunnels.
o mvpnBgpCmcastRouteWithdrawalTimer o mvpnBgpCmcastRouteWithdrawalTimer
The value of this object is used to control the delay for the The value of this object is used to control the delay for the
advertisement of withdrawals of C-multicast routes. Access to advertisement of withdrawals of C-multicast routes. Access to
skipping to change at page 52, line 12 skipping to change at page 52, line 33
be abused to impact the performance of the PE or prevent the PE be abused to impact the performance of the PE or prevent the PE
from receiving Source Active A-D routes. from receiving Source Active A-D routes.
o mvpnBgpMaxSrcActiveAdRouteFreq o mvpnBgpMaxSrcActiveAdRouteFreq
The value of this object is used to control the upper bound for The value of this object is used to control the upper bound for
the frequency of Source Active A-D route generation. Access to the frequency of Source Active A-D route generation. Access to
this object may be abused to impact the performance of the PE or this object may be abused to impact the performance of the PE or
prevent the PE from generating new Source Active A-D routes. prevent the PE from generating new Source Active A-D routes.
Some of the readable objects in this MIB module (e.g., objects with a Some of the objects in this MIB module may be considered sensitive or
MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. This includes INDEX objects
vulnerable in some network environments. It is thus important to with a MAX-ACCESS of not-accessible, and any indices from other
control even GET and/or NOTIFY access to these objects and possibly modules exposed via AUGMENTS. It is thus important to control even
to even encrypt the values of these objects when sending them over GET and/or NOTIFY access to these objects and possibly to even
the network via SNMP. These are the tables and objects and their encrypt the values of these objects when sending them over the
network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o The address-related objects in this MIB module may have impact on o The address-related objects in this MIB module may have impact on
privacy and security. These objects may reveal the locations of privacy and security. These objects may reveal the locations of
senders and recipients. senders and recipients.
* mvpnPmsiTunnelPimGroupAddr * mvpnPmsiTunnelPimGroupAddr
* mvpnSpmsiCmcastGroupAddr * mvpnSpmsiCmcastGroupAddr
skipping to change at page 53, line 25 skipping to change at page 53, line 44
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 to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
5. IANA Considerations 5. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER value recorded in the "SMI Network Management MGMT
Codes Internet-standard MIB" registry:
Name Description OBJECT IDENTIFIER value Name Description OBJECT IDENTIFIER value
------- --------------------------------- ---------------------- ------- --------------------------------- ----------------------
mvpnMIB BGP-MPLS-LAYER3-VPN-MULTICAST-MIB { mib-2 AAAA } mvpnMIB BGP-MPLS-LAYER3-VPN-MULTICAST-MIB { mib-2 243 }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "AAAA" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "AAAA"
(here and in the MIB module) with the assigned value and to remove
this note.
6. Acknowledgement
An earlier draft version of this document was coauthored by Zhaohui
(Jeffrey) Zhang, Saud Asif, Andy Green, Sameer Gulrajani, and Pradeep
G. Jain, based on an earlier draft written by Susheela Vaidya,
Thomas D. Nadeau, and Harmen Van der Linde.
This document also borrows heavily from the design and descriptions
of ipMcastRouteTable and ipMcastRouteNextHopTable from IPMCAST-
MIB[RFC5132].
Glenn Mansfield Keeni did the MIB Doctor review and provided valuable
comments.
7. References 6. References
7.1. Normative References 6.1. Normative References
[RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, DOI [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003,
10.17487/RFC2003, October 1996, <https://www.rfc- DOI 10.17487/RFC2003, October 1996,
editor.org/info/rfc2003>. <https://www.rfc-editor.org/info/rfc2003>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC2119, March 1997,
rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and
Schoenwaelder, Ed., "Structure of Management Information J. Schoenwaelder, Ed., "Structure of Management
Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ Information Version 2 (SMIv2)", STD 58, RFC 2578,
RFC2578, April 1999, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC2578, April 1999,
rfc2578>. <https://www.rfc-editor.org/info/rfc2578>.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and
Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD J. Schoenwaelder, Ed., "Textual Conventions for SMIv2",
58, RFC 2579, DOI 10.17487/RFC2579, April 1999, STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999,
<https://www.rfc-editor.org/info/rfc2579>. <https://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and
Schoenwaelder, Ed., "Conformance Statements for SMIv2", J. Schoenwaelder, Ed., "Conformance Statements for SMIv2",
STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999,
<https://www.rfc-editor.org/info/rfc2580>. <https://www.rfc-editor.org/info/rfc2580>.
[RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and
Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, P. Traina, "Generic Routing Encapsulation (GRE)",
DOI 10.17487/RFC2784, March 2000, <https://www.rfc- RFC 2784, DOI 10.17487/RFC2784, March 2000,
editor.org/info/rfc2784>. <https://www.rfc-editor.org/info/rfc2784>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,
<https://www.rfc-editor.org/info/rfc2863>. <https://www.rfc-editor.org/info/rfc2863>.
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001,
<https://www.rfc-editor.org/info/rfc3032>. <https://www.rfc-editor.org/info/rfc3032>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ Protocol (SNMPv3)", STD 62, RFC 3414,
RFC3414, December 2002, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC3414, December 2002,
rfc3414>. <https://www.rfc-editor.org/info/rfc3414>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, DOI 10.17487/ SNMP User-based Security Model", RFC 3826,
RFC3826, June 2004, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC3826, June 2004,
rfc3826>. <https://www.rfc-editor.org/info/rfc3826>.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and
Schoenwaelder, "Textual Conventions for Internet Network J. Schoenwaelder, "Textual Conventions for Internet
Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005, Network Addresses", RFC 4001, DOI 10.17487/RFC4001,
<https://www.rfc-editor.org/info/rfc4001>. February 2005, <https://www.rfc-editor.org/info/rfc4001>.
[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, DOI 10.17487/RFC4364, February Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <https://www.rfc-editor.org/info/rfc4364>. 2006, <https://www.rfc-editor.org/info/rfc4364>.
[RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer [RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer
3 Virtual Private Network (VPN) Management Information 3 Virtual Private Network (VPN) Management Information
Base", RFC 4382, DOI 10.17487/RFC4382, February 2006, Base", RFC 4382, DOI 10.17487/RFC4382, February 2006,
<https://www.rfc-editor.org/info/rfc4382>. <https://www.rfc-editor.org/info/rfc4382>.
[RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast
MIB", RFC 5132, DOI 10.17487/RFC5132, December 2007, MIB", RFC 5132, DOI 10.17487/RFC5132, December 2007,
<https://www.rfc-editor.org/info/rfc5132>. <https://www.rfc-editor.org/info/rfc5132>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", STD for the Simple Network Management Protocol (SNMP)",
78, RFC 5591, DOI 10.17487/RFC5591, June 2009, STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009,
<https://www.rfc-editor.org/info/rfc5591>. <https://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June
2009, <https://www.rfc-editor.org/info/rfc5592>. 2009, <https://www.rfc-editor.org/info/rfc5592>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)", Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011,
skipping to change at page 56, line 5 skipping to change at page 56, line 5
[RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
2012, <https://www.rfc-editor.org/info/rfc6513>. 2012, <https://www.rfc-editor.org/info/rfc6513>.
[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
Encodings and Procedures for Multicast in MPLS/BGP IP Encodings and Procedures for Multicast in MPLS/BGP IP
VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,
<https://www.rfc-editor.org/info/rfc6514>. <https://www.rfc-editor.org/info/rfc6514>.
[RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R. [RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and
Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes", R. Qiu, "Wildcards in Multicast VPN Auto-Discovery
RFC 6625, DOI 10.17487/RFC6625, May 2012, Routes", RFC 6625, DOI 10.17487/RFC6625, May 2012,
<https://www.rfc-editor.org/info/rfc6625>. <https://www.rfc-editor.org/info/rfc6625>.
[RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
Multicast - Sparse Mode (PIM-SM): Protocol Specification Multicast - Sparse Mode (PIM-SM): Protocol Specification
(Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March
2016, <https://www.rfc-editor.org/info/rfc7761>. 2016, <https://www.rfc-editor.org/info/rfc7761>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFCXXXX] Zhang, Z. and H. Tsunoda, "L2L3 VPN Multicast MIB", draft- [RFC8502] Zhang, Z. and H. Tsunoda, "L2L3 VPN Multicast MIB",
ietf-bess-l2l3-vpn-mcast-mib-16 (work in progress), RFC 8502, DOI 10.17487/RFC8502, December 2018,
September 2018. <https://www.rfc-editor.org/info/rfc8502>.
[RTPROTO] IANA, "IP Route Protocol MIB", 2016,
<http://www.iana.org/assignments/ianaiprouteprotocol-mib>.
7.2. Informative References 6.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, DOI 10.17487/ Standard Management Framework", RFC 3410,
RFC3410, December 2002, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC3410, December 2002,
rfc3410>. <https://www.rfc-editor.org/info/rfc3410>.
Acknowledgements
An earlier draft version of this document was coauthored by Zhaohui
(Jeffrey) Zhang, Saud Asif, Andy Green, Sameer Gulrajani, and Pradeep
G. Jain. That document, in turn, was based on an earlier document
written by Susheela Vaidya, Thomas D. Nadeau, and Harmen Van der
Linde.
This document also borrows heavily from the design and descriptions
of ipMcastRouteTable and ipMcastRouteNextHopTable from IPMCAST-MIB
[RFC5132].
Glenn Mansfield Keeni did the MIB Doctor review and provided valuable
comments.
Author's Address Author's Address
Hiroshi Tsunoda Hiroshi Tsunoda
Tohoku Institute of Technology Tohoku Institute of Technology
35-1, Yagiyama Kasumi-cho, Taihaku-ku 35-1, Yagiyama Kasumi-cho, Taihaku-ku
Sendai 982-8577 Sendai 982-8577
Japan Japan
Phone: +81-22-305-3411 Phone: +81-22-305-3411
 End of changes. 227 change blocks. 
402 lines changed or deleted 393 lines changed or added

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