--- 1/draft-ietf-bess-mvpn-mib-06.txt 2018-07-23 05:13:19.291204922 -0700 +++ 2/draft-ietf-bess-mvpn-mib-07.txt 2018-07-23 05:13:19.387207230 -0700 @@ -1,142 +1,127 @@ -Network Working Group Z. Zhang, Ed. -Internet-Draft Juniper -Intended status: Standards Track S. Asif -Expires: November 1, 2018 AT&T - A. Green - BT - S. Gulranjani - Cisco - P. Jain - Alcatel-Lucent - H. Tsunoda, Ed. - Tohoku Institute of Technology - April 30, 2018 +Network Working Group H. Tsunoda +Internet-Draft Tohoku Institute of Technology +Intended status: Standards Track July 23, 2018 +Expires: January 24, 2019 BGP/MPLS Layer 3 VPN Multicast Management Information Base - draft-ietf-bess-mvpn-mib-06 + draft-ietf-bess-mvpn-mib-07 Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects to configure and/or - monitor MVPN, Multicast in MultiProtocol Label Switching/Border - Gateway Protocol (MPLS/BGP) IP Virtual Private Networks (VPNs) on a - Provider Edge router. + monitor Multicast communication over IP Virtual Private Networks + (VPNs) supported by MultiProtocol Label Switching/Border Gateway + Protcol (MPLS/BGP) on a Provider Edge router. Status of This Memo This Internet-Draft is submitted in full conformance with the 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on November 1, 2018. + This Internet-Draft will expire on January 24, 2019. Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 - 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 - 2. The Internet-Standard Management Framework . . . . . . . . . 4 - 3. MCAST-VPN-MIB . . . . . . . . . . . . . . . . . . . . . . . . 4 + 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 + 2. The Internet-Standard Management Framework . . . . . . . . . 3 + 3. MCAST-VPN-MIB . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. Summary of MIB Module . . . . . . . . . . . . . . . . . . 4 - 3.2. MIB Module Definitions . . . . . . . . . . . . . . . . . 6 - 4. Security Considerations . . . . . . . . . . . . . . . . . . . 62 - 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 - 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 64 - 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 64 - 7.1. Normative References . . . . . . . . . . . . . . . . . . 64 - 7.2. Informative References . . . . . . . . . . . . . . . . . 66 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 66 + 3.2. MIB Module Definitions . . . . . . . . . . . . . . . . . 5 + 4. Security Considerations . . . . . . . . . . . . . . . . . . . 50 + 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52 + 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 53 + 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 53 + 7.1. Normative References . . . . . . . . . . . . . . . . . . 53 + 7.2. Informative References . . . . . . . . . . . . . . . . . 55 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 55 1. Introduction [RFC6513], [RFC6514], and [RFC6625] specify procedures for supporting multicast in Border Gateway Protocol/MultiProtocol Label Switching - (BGP/MPLS) Layer 3 (IP) Virtual Private Network (VPN). Throughout - this document, we will use the term "Multicast VPN (MVPN)" [RFC6513] + (BGP/MPLS) Layer 3 (IP) Virtual Private Networks (VPNs). Throughout + this document, we will use the term "Multicast VPN" (MVPN) [RFC6513] to refer to a BGP/MPLS IP VPN that supports multicast. - Provider Edge routers (PEs) exchange the VPN customer multicast - (C-multicast) routing information with each other. In [RFC6513], two - basic methods for exchanging C-multicast routing information are - defined (1) Protocol Independent Multicast (PIM) [RFC7761] and (2) - BGP. + Provider Edge routers (PEs) attaching to a particular MVPN exchange + customer multicast (C-multicast) routing information with neighboring + PEs. In [RFC6513], two basic methods for exchanging C-multicast + routing information are defined (1) Protocol Independent Multicast + (PIM) [RFC7761] and (2) BGP. In the rest of this document we will use the term "PIM-MVPN" to refer - to PIM being used for exchanging C-multicast routing information, and - "BGP-MVPN" to refer to BGP being used for exchanging C-multicast - routing information. + to the case where PIM is used for exchanging C-multicast routing + information, and "BGP-MVPN" to refer to the case where BGP is used + for exchanging C-multicast routing information. This document describes managed objects to configure and/or monitor - MVPN. The managed objects are common to both PIM-MVPN and BGP-MVPN. - - Comments should be made directly to the BESS WG at bess@ietf.org. + MVPNs. Most of the managed objects are common to both PIM-MVPN and + BGP-MVPN, and some managed objects are BGP-MVPN specific. 1.1. Terminology This document adopts the definitions, acronyms and mechanisms - described in [RFC6513] and other documents that [RFC6513] refers to. - Familiarity with Multicast, MPLS, Layer 3 (L3) VPN, MVPN concepts - and/or mechanisms is assumed. Some terms specifically related to - this document are explained below. + described in [RFC4364], [RFC6513], and [RFC6514]. Familiarity with + Multicast, MPLS, Layer 3 (L3) VPN, MVPN concepts and/or mechanisms is + assumed. Some terms specifically related to this document are + explained below. - MVPN can be achieved by using various kinds of transport mechanisms - for forwarding a packet to all or a subset of PEs across service - provider networks. Such transport mechanisms are referred to as - provider tunnels (P-tunnels). + An MVPN can be realized by using various kinds of transport + mechanisms for forwarding a packet to all or a subset of PEs across + service provider networks. Such transport mechanisms are referred to + as provider tunnels (P-tunnels). - "Provider Multicast Service Interface (PMSI)" [RFC6513] is a - conceptual interface instantiated by a provider tunnel (P-tunnel), a - transport mechanism used to deliver multicast traffic. A PE uses to + A "Provider Multicast Service Interface" (PMSI) [RFC6513] is a + 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. - There are two kinds of PMSI: "Inclusive PMSI (I-PMSI)" and "Selective - PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that enables a PE - attached to a particular MVPN to transmit a message to all PEs in the - same VPN. An S-PMSI is a PMSI that enables a PE attached to a - particular MVPN to transmit a message to some of the PEs in the same - VPN. - - As described in [RFC4382], each PE router maintains one default - forwarding table and "Virtual Routing and Forwarding tables", or - "VRFs". Throughout this document, we will use the term "multicast - VRF (MVRF)" to refer a VRF that is configured to contain the - multicast routing information. + There are two kinds of PMSI: "Inclusive PMSI" (I-PMSI) and "Selective + 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. + An S-PMSI enables a PE to transmit a message to a selected set of PEs + in the same MVPN. - Interchangeably, the term MVRF and MVPN are used to refer to a - particular Multicast VPN instantiation on a particular PE. + As described in [RFC4382], each PE maintains one default forwarding + table and zero or more "Virtual Routing and Forwarding tables" + (VRFs). Throughout this document, we will use the term "multicast + VRF" (MVRF) to refer to a VRF that contains multicast routing + information. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. @@ -146,240 +131,171 @@ accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. MCAST-VPN-MIB This document defines MCAST-VPN-MIB, a MIB module for monitoring and/ - or configuring MVPNs on PEs. + or configuring MVPNs on PEs. This MIB module will be used in + conjunction with MPLS-L3VPN-STD-MIB [RFC4382] and IPMCAST-MIB + [RFC5132]. 3.1. Summary of MIB Module - MCAST-VPN-MIB provides the following functionalities for monitoring - and configuring MVPN. + MCAST-VPN-MIB provides the following functionalities. - o Monitoring attribute informations of MVRFs of MVPNs presented on a - PE + o Monitoring attributes of MVPNs on a PE - o Configuring some timers related to a MVRF + o Configuring timers and thresholds related to an MVPN on a PE o Notifying creation, deletion, and modification of MVRFs on a PE - o Monitoring attribute informations of PMSIs on a PE - - o Monitoring advertisement exchanged by a PE - - o Monitoring routing entries in an MVRF + o Monitoring PMSI attributes - o Monitoring information on next-hops in an MVRF + o Monitoring statistics of advertisements exchanged by a PE - o Notifying events that a PE joins or leaves a multicast group + o Monitoring routing information for multicast destinations - To provide these functionalities, MCAST-VPN-MIB defines nine tables: - mvpnGenericTable, mvpnBgpGenericlTable, mvpnPmsiTable, - mvpnSpmsiTable, mvpnIpmsiAdvtTable, mvpnInterAsIpmsiAdvtTable, - mvpnSpmsiAdvtTable, mvpnMrouteTable, and mvpnMrouteNextHopTable. + o Monitoring next-hops for each multicast destination - The following two tables contain information of MVRFs of MVPNs - configured on a PE. + To provide these functionalities, MCAST-VPN-MIB defines following + tables. o mvpnGenericTable - This table specifies the generic information about MVRFs present - in a PE. Each entry in this table is created for each MVRF - representing an instance of MVPN. The entry represetns general - configuration/states of the MVRF, including Inclusive PMSI - (I-PMSI) configuration. An MVRF represented by the entry in this - table must have a corresponding VRF in MPLS-L3VPN-STD-MIB - [RFC4382]. - - o mvpnBgpGenericTable + 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 + contains generic information related to the MVPN. For each entry + in this table there MUST be a corresponding VRF in MPLS-L3VPN-STD- + MIB [RFC4382]. - This table specifies the specific information of MVRFs of MVPNs - that use BGP for exchanging C-Multicast routing information - present in a PE. Each MVRF of an MVPN that use BGP for exchanging - C-Multicast routing information will have an entry in this table. - The MVRF represented by this entry will have a corresponding entry - in the mvpnGenericTable. + o mvpnBgpTable - The following two tables contain information of PMSIs configured on a - PE. + This table contains information specific to BGP-MVPNs. Each BGP- + MVPN on a PE will have an entry in this table. o mvpnPmsiTable - This table contains common managed objects representing attribute - information of both I-PMSI and Selective PMSI (S-PMSI) configured - on a PE. Both I-PMSI information (in the entry in - mvpnGeneralTable) and S-PMSI information (in the entry in - mvpnSpmsiConfigTable) refer to an entry in this table. + This table contains managed objects representing attribute + information that is common to I-PMSIs and S-PMSIs on a PE. o mvpnSpmsiTable This table contains managed objects representing attribute - information that is specific for S-PMSI associated with an MVRF on - a PE. - - The following three tables are designed for monitoring advertisements - that is advertised/received by a PE. - - o mvpnIpmsiAdvtTable - - This table contains managed objects representing advertisements of - Intra-AS I-PMSIs advertised/received by a PE. - - o mvpnInterAsIpmsiAdvtTable - This table contains managed objects representing advertisements of - Inter-AS I-PMSIs advertised/received by a PE. - - o mvpnSpmsiAdvtTable + information specific to S-PMSIs. An S-PMSI represented in this + table will have a corresponding entry in mvpnPmsiTable. - This table contains managed objects representing advertisements of - S-PMSIs advertised/received by a PE. + o mvpnAdvtStatsTable - The following two tables are designed for handling routing - information that is advertised/received by a PE. + This table contains statistics pertaining to I-PMSI and S-PMSI + advertisements sent/received. o mvpnMrouteTable - This table contains multicast routing information in MVRFs present - in a PE. + This table contains multicast routing information in MVRFs on a + PE. o mvpnMrouteNextHopTable - The table contains information on the next-hops on outgoing - interfaces for routing IP multicast datagrams in MVPNs present on - a PE. + This table contains information on the next-hops for routing IP + multicast datagrams in MVPNs on a PE. 3.2. MIB Module Definitions MCAST-VPN-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Counter64, Gauge32, Unsigned32, TimeTicks, - zeroDotZero, mib-2 + mib-2 FROM SNMPv2-SMI -- [RFC2578] MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] - RowPointer, TimeStamp, TimeInterval + RowPointer, TimeStamp, DateAndTime FROM SNMPv2-TC -- [RFC2579] - CounterBasedGauge64 - FROM HCNUM-TC -- [RFC2856] - InterfaceIndex, InterfaceIndexOrZero FROM IF-MIB -- [RFC2863] - InetAddress, InetAddressType, InetAddressPrefixLength, - InetAutonomousSystemNumber + InetAddress, InetAddressType, InetAddressPrefixLength FROM INET-ADDRESS-MIB -- [RFC2851] mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher FROM MPLS-L3VPN-STD-MIB -- [RFC4382] IANAipRouteProtocol, IANAipMRouteProtocol FROM IANA-RTPROTO-MIB -- [RTPROTO] L2L3VpnMcastProviderTunnelType FROM L2L3-VPN-MCAST-TC-MIB; mvpnMIB MODULE-IDENTITY - LAST-UPDATED "201804301200Z" -- 30th April 2018 12:00:00 GMT + LAST-UPDATED "201807231200Z" -- 23th July 2018 12:00:00 GMT ORGANIZATION "IETF BESS Working Group." CONTACT-INFO - " Zhaohui Zhang - Juniper Networks, Inc. - 10 Technology Park Drive - Westford, MA 01886 - USA - Email: zzhang@juniper.net - - Saud Asif - AT&T - C5-3D30 200 South Laurel Avenue - Middletown, NJ 07748 - USA - Email: sasif@att.com - - Andy Green - BT Design 21CN Converged Core IP & Data - 01473 629360 Adastral Park, Martlesham Heath, - Ipswich IP5 3RE - UK - Email: andy.da.green@bt.com - - Sameer Gulrajani - Cisco Systems - Tasman Drive San Jose, CA 95134 - USA - Email: sameerg@cisco.com - - Pradeep G. Jain - Alcatel-Lucent Inc - 701 E Middlefield road Mountain view, CA 94043 - USA - Email: pradeep.jain@alcatel-lucent.com - - Hiroshi Tsunoda + " Hiroshi Tsunoda Tohoku Institute of Technology 35-1, Yagiyama Kasumi-cho Taihaku-ku, Sendai, 982-8577 Japan Email: tsuno@m.ieice.org Comments and discussion to bess@ietf.org" DESCRIPTION - "This MIB contains managed object definitions for - multicast in BGP/MPLS IP VPNs defined by [RFC6513]. - Copyright (C) The Internet Society (2018)." + "This MIB module contains managed object definitions to + configure and/or monitor Multicast communication over IP + Virtual Private Networks (VPNs) supported by MultiProtocol + Label Switching/Border Gateway Protcol (MPLS/BGP) on a + Provider Edge router (PE). + Copyright (C) The Internet Society (2018). + " -- Revision history. - REVISION "201804301200Z" -- 30th April, 2018 + REVISION "201807231200Z" -- 23th July, 2018 DESCRIPTION "Initial version, published as RFC XXXX." - -- RFC Ed. replace XXXX with actual RFC number and remove this note + -- RFC Ed. replace XXXX with the actual RFC number and + -- remove this note ::= { mib-2 YYYY } -- IANA Reg.: Please assign a value for "YYYY" under the -- 'mib-2' subtree and record the assignment in the SMI -- Numbers registry. -- RFC Ed.: When the above assignment has been made, please -- remove the above note -- replace "YYYY" here with the assigned value and -- remove this note. - -- Top level components of this MIB. + -- Top level components of this MIB module. mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 } - -- tables, scalars + -- scalars, tables mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 } -- conformance information mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 } -- mvpn Objects mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 } - mvpnGeneric OBJECT IDENTIFIER ::= { mvpnObjects 2 } - mvpnConfig OBJECT IDENTIFIER ::= { mvpnObjects 3 } - mvpnStates OBJECT IDENTIFIER ::= { mvpnObjects 4 } -- Scalar Objects + mvpnMvrfs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of Multicast Virtual Routing and Forwarding tables (MVRFs) that are present on this Provider Edge router (PE). This includes MVRFs for IPv4, IPv6, and mLDP C-Multicast. " @@ -383,2622 +299,2171 @@ this Provider Edge router (PE). This includes MVRFs for IPv4, IPv6, and mLDP C-Multicast. " ::= { mvpnScalars 1 } mvpnV4Mvrfs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of MVRFs for IPv4 C-Multicast that are - present in this PE. + "The number of MVRFs for IPv4 C-Multicast on this PE. " ::= { mvpnScalars 2 } mvpnV6Mvrfs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of MVRFs for IPv6 C-Multicast that are - present in this PE. + "The number of MVRFs for IPv6 C-Multicast on this PE. " ::= { mvpnScalars 3 } - mvpnPimV4Mvrfs OBJECT-TYPE + mvpnMldpMvrfs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of MVRFs of MVPNs that use PIM for - exchanging IPv4 C-Multicast routing information - present in this PE. + "The number of MVRFs on this PE that use BGP for + exchanging Multipoint Label Distribution Protocol (mLDP) + C-Multicast routing information. " ::= { mvpnScalars 4 } - mvpnPimV6Mvrfs OBJECT-TYPE + mvpnPimV4Mvrfs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of MVRFs of MVPNs that use PIM for - exchanging IPv6 C-Multicast routing information - present in this PE. + "The number of MVRFs on this PE that use Provider + Independent Multicast (PIM) for exchanging IPv4 + C-Multicast routing information. " ::= { mvpnScalars 5 } - mvpnBgpV4Mvrfs OBJECT-TYPE + mvpnPimV6Mvrfs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of MVRFs of MVPNs that use BGP for - exchanging IPv4 C-Multicast routing information - present in this PE. + "The number of MVRFs on this PE that use PIM for + exchanging IPv6 C-Multicast routing information. " ::= { mvpnScalars 6 } - mvpnBgpV6Mvrfs OBJECT-TYPE + mvpnBgpV4Mvrfs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of MVRFs of MVPNs that use BGP for - exchanging IPv6 C-Multicast routing information - present in this PE. + "The number of MVRFs on this PE that use BGP for + exchanging IPv4 C-Multicast routing information. " ::= { mvpnScalars 7 } - mvpnMldpMvrfs OBJECT-TYPE + mvpnBgpV6Mvrfs OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of MVRFs of MVPNs that use BGP for - exchanging mLDP C-Multicast routing information - present in this PE. + "The number of MVRFs on this PE that use BGP for + exchanging IPv6 C-Multicast routing information. " ::= { mvpnScalars 8 } + mvpnSPTunnelLimit OBJECT-TYPE + SYNTAX Unsigned32 (1..4294967295) + MAX-ACCESS read-write + STATUS current + DESCRIPTION + "The maximum number of selective provider tunnels that + this PE allows for a particular MVPN on this PE. + + " + REFERENCE + "RFC6513, Section 13" + ::= { mvpnScalars 9 } + + mvpnBgpCmcastRouteWithdrawalTimer OBJECT-TYPE + SYNTAX Unsigned32 + UNITS "milliseconds" + MAX-ACCESS read-write + STATUS current + DESCRIPTION + "A configurable timer to control the delay + of C-multicast route withdrawal advertisements. + " + REFERENCE + "RFC6514, Section 16.1.1" + ::= { mvpnScalars 10 } + + mvpnBgpSrcSharedTreeJoinTimer OBJECT-TYPE + SYNTAX Unsigned32 + UNITS "milliseconds" + MAX-ACCESS read-write + STATUS current + DESCRIPTION + "A configurable timer to control the delay + of Source/Shared Tree Join C-multicast route + advertisements. + " + REFERENCE + "RFC6514, Section 16.1.2" + ::= { mvpnScalars 11 } + -- Generic MVRF Information Table mvpnGenericTable OBJECT-TYPE SYNTAX SEQUENCE OF MvpnGenericEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "This table specifies the generic information about the MVRFs - present in this PE. - - Entries in this table are not required to survive a reboot - of the managed entity. + "A conceptual table containing generic information about MVPNs + on this PE. " - ::= { mvpnGeneric 1 } + ::= { mvpnObjects 2 } mvpnGenericEntry OBJECT-TYPE SYNTAX MvpnGenericEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "This entry represents a conceptual row in the mvpnGenericTable. - Each MVRF serviced by the PE will have an entry in this table. - The MVRF represented by this entry will have one or more + "A conceptual row that represents an MVPN on this PE. + The MVPN represented by this entry will have one or more corresponding P-Multicast Service Interfaces (PMSIs) and a corresponding VRF in MPLS-L3VPN-STD-MIB [RFC4382]. " INDEX { - mplsL3VpnVrfName, - mvpnGenAddressFamily + mplsL3VpnVrfName } ::= { mvpnGenericTable 1 } MvpnGenericEntry ::= SEQUENCE { - mvpnGenAddressFamily INTEGER, - mvpnGenMvrfLastOperation INTEGER, - mvpnGenMvrfLastOperationTime TimeStamp, + mvpnGenMvrfLastAction INTEGER, + mvpnGenMvrfLastActionTime DateAndTime, + mvpnGenMvrfCreationTime DateAndTime, mvpnGenCmcastRouteProtocol INTEGER, mvpnGenIpmsiInfo RowPointer, mvpnGenInterAsPmsiInfo RowPointer, mvpnGenUmhSelection INTEGER, - mvpnGenCustomerSiteType INTEGER, - mvpnGenSPTunnelLimit Unsigned32 - } - - mvpnGenAddressFamily OBJECT-TYPE - SYNTAX INTEGER { - ipv4(1), - ipv6(2) + mvpnGenCustomerSiteType INTEGER } - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The Address Family of the MVRF represented by this entry" - REFERENCE - "RFC6513, Section 1 - " - ::= { mvpnGenericEntry 1 } - mvpnGenMvrfLastOperation OBJECT-TYPE + mvpnGenMvrfLastAction OBJECT-TYPE SYNTAX INTEGER { createdMvrf(1), deletedMvrf(2), modifiedMvrfIpmsiConfig(3), modifiedMvrfSpmsiConfig(4) } MAX-ACCESS read-only STATUS current DESCRIPTION - "This object describes the last operation pertaining - to the MVRF represented by this entry. + "This object describes the last action pertaining + to the MVPN represented by this entry. - createdMvrf(1): - the MVRF was created in the PE. + The enumerated action types and the corresponding + descriptions are as follows: - deletedMvrf(2): - the MVRF was deleted from the PE. - A row in this table will never have - mvpnGenMvrfLastOperation equal to deletedMvrf(2), - because in that case the row itself will be deleted - from the table. - This value for mvpnGenMvrfLastOperation is defined - mainly for use in mvpnMvrfOperationChange notification. + createdMvrf: + MVRF was created for this MVPN on the PE. - modifiedMvrfIpmsiConfig(3): - an I-PMSI for the MVRF was configured, - deleted or changed. + deletedMvrf: + MVRF for this MVPN was deleted from the PE. + A conceptual row in this table will never have + mvpnGenMvrfLastAction equal to deletedMvrf, + because in that case the row itself will not exist + in the table. + This value for mvpnGenMvrfLastAction is defined + solely for use in mvpnMvrfActionChange notification. - modifiedMvrfSpmsiConfig(4): - an S-PMSI for the MVRF was configured, - deleted or changed. + modifiedMvrfIpmsiConfig: + an I-PMSI for this MVPN was configured, deleted or + changed. + + modifiedMvrfSpmsiConfig: + an S-PMSI for this MVPN was configured, deleted or + changed. " - DEFVAL { createdMvrf } ::= { mvpnGenericEntry 2 } - mvpnGenMvrfLastOperationTime OBJECT-TYPE - SYNTAX TimeStamp + mvpnGenMvrfLastActionTime OBJECT-TYPE + SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION - "The time at which the last operation for the MVRF in - question took place. The last operational change is specified - by mvpnGenMvrfLastOperation. - The time at which the last operation, specifed - in mvpnGenMvrfLastOperation, for the MVRF - represented by this entry was carried out. + "The timestamp when the last action, given in + the corresponding mvpnGenMvrfLastAction object, + was carried out. " - ::= { mvpnGenericEntry 3 } + mvpnGenMvrfCreationTime OBJECT-TYPE + SYNTAX DateAndTime + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The timestamp when the MVRF was created for + the MVPN represented by this entry. + " + ::= { mvpnGenericEntry 4 } + mvpnGenCmcastRouteProtocol OBJECT-TYPE SYNTAX INTEGER { pim (1), bgp (2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The protocol used to signal C-multicast routing - information across the provider core. - PIM (PIM-MVPN): pim(1) - BGP (BGP-MVPN): bgp(2) + information across the provider core for the MVPN + represented by this entry. + + The enumerated protocols and the corresponding + descriptions are as follows: + + pim : PIM (PIM-MVPN) + bgp : BGP (BGP-MVPN) " REFERENCE "RFC6513, Section 5" - ::= { mvpnGenericEntry 4 } + ::= { mvpnGenericEntry 5 } mvpnGenIpmsiInfo OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION - "This points to a conceptual row representing + "A pointer to a conceptual row representing the corresponding I-PMSI in mvpnPmsiTable. - If there is no I-PMSI for the MVRF, the + If there is no I-PMSI for the MVPN + represented by this entry, the value of this object will be zeroDotZero. " - DEFVAL { zeroDotZero } - ::= { mvpnGenericEntry 5 } + ::= { mvpnGenericEntry 6 } mvpnGenInterAsPmsiInfo OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION - "This points to a conceptual row representing - the corresponding Inter-AS I-PMSI in mvpnPmsiTable, - in case of segmented Inter-AS provider tunnels. - If there is no segmented Inter-AS I-PMSI for the MVRF, + "A pointer to a conceptual row representing + the corresponding segmented Inter-AS I-PMSI in mvpnPmsiTable. + If there is no segmented Inter-AS I-PMSI for the MVPN, the value of this object will be zeroDotZero. " - DEFVAL { zeroDotZero } - ::= { mvpnGenericEntry 6 } + ::= { mvpnGenericEntry 7 } mvpnGenUmhSelection OBJECT-TYPE SYNTAX INTEGER { highestPeAddress (1), cRootGroupHashing (2), ucastUmhRoute (3) } MAX-ACCESS read-only STATUS current DESCRIPTION - "The UMH selection method for this mvpn, as specified in - section 5.1.3 of [RFC6513]: - PE with the highest address: highestPeAddress (1) - hashing based on (c-root, c-group): cRootGroupHashing (2) - per ucast route towards c-root: ucastUmhRoute (3) + "The Upstream Multicast Hop (UMH) selection method for the MVPN + represented by this entry. + + The enumerated methods and the corresponding + descriptions are as follows: + + highestPeAddress : PE with the highest address + (see RFC6513, Section 5.1.3) + cRootGroupHashing : hashing based on (c-root, c-group) + ucastUmhRoute : per unicast route towards c-root " REFERENCE "RFC6513, Section 5.1" - ::= { mvpnGenericEntry 7 } + ::= { mvpnGenericEntry 8 } mvpnGenCustomerSiteType OBJECT-TYPE SYNTAX INTEGER { senderReceiver (1), receiverOnly (2), senderOnly (3) } MAX-ACCESS read-only STATUS current DESCRIPTION - "The type of a customer site, which is connected to - this PE, in the MVPN which has the MVRF represented - by this entry. + "The type of the customer site, connected to + the MVPN represented by this entry. - Site is both sender and receiver: senderReceiver (1) - Site is receiver-only : receiverOnly (2) - Site is sender-only : senderOnly (3) - " - REFERENCE - "RFC6513, Section 2.3" - ::= { mvpnGenericEntry 8 } + The enumerated types and the corresponding + descriptions are as follows: - mvpnGenSPTunnelLimit OBJECT-TYPE - SYNTAX Unsigned32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The maximum number of selective provider tunnels that - this PE allows for this MVPN. + senderReceiver : Site is both sender and receiver + receiverOnly : Site is receiver-only + senderOnly : Site is sender-only " REFERENCE - "RFC6513, Section 13" - + "RFC6513, Section 2.3" ::= { mvpnGenericEntry 9 } -- Generic BGP-MVPN table - mvpnBgpGenericTable OBJECT-TYPE - SYNTAX SEQUENCE OF MvpnBgpGenericEntry + mvpnBgpTable OBJECT-TYPE + SYNTAX SEQUENCE OF MvpnBgpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "This table specifies the specific information of MVRFs of MVPNs - that use BGP for exchanging C-Multicast routing information - present in this PE. + "A conceptual table that supplements mvpnGenericTable + with BGP-MVPN specific information for BGP-MVPNs on this PE. " - ::= { mvpnGeneric 2 } + ::= { mvpnObjects 3 } - mvpnBgpGenericEntry OBJECT-TYPE - SYNTAX MvpnBgpGenericEntry + mvpnBgpEntry OBJECT-TYPE + SYNTAX MvpnBgpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "This entry represents a conceptual row in the mvpnBgpGenericTable. - Each MVRF of an MVPN that use BGP for exchanging C-Multicast - routing information will have an entry in this table. - The MVRF represented by this entry will have - a corresponding entry in the mvpnGenericTable. + "A conceptual row corresponding to a BGP-MVPN on this PE. " INDEX { - mplsL3VpnVrfName, - mvpnGenAddressFamily + mplsL3VpnVrfName } - ::= { mvpnBgpGenericTable 1 } + ::= { mvpnBgpTable 1 } - MvpnBgpGenericEntry ::= SEQUENCE { - mvpnBgpGenMode INTEGER, - mvpnBgpGenVrfRouteImport MplsL3VpnRouteDistinguisher, - mvpnBgpGenSrcAs InetAutonomousSystemNumber, - mvpnBgpGenCmcastRouteWithdrawalTimer Unsigned32, - mvpnBgpGenSrcSharedTreeJoinTimer Unsigned32, - mvpnBgpGenMsgRateLimit Unsigned32, - mvpnBgpGenMaxSpmsiAdRoutes Unsigned32, - mvpnBgpGenMaxSpmsiAdRouteFreq Unsigned32, - mvpnBgpGenMaxSrcActiveAdRoutes Unsigned32, - mvpnBgpGenMaxSrcActiveAdRouteFreq Unsigned32 + MvpnBgpEntry ::= SEQUENCE { + mvpnBgpMode INTEGER, + mvpnBgpVrfRouteImportExtendedCommunity MplsL3VpnRouteDistinguisher, + mvpnBgpSrcASExtendedCommunity Unsigned32, + mvpnBgpMsgRateLimit Unsigned32, + mvpnBgpMaxSpmsiAdRoutes Unsigned32, + mvpnBgpMaxSpmsiAdRouteFreq Unsigned32, + mvpnBgpMaxSrcActiveAdRoutes Unsigned32, + mvpnBgpMaxSrcActiveAdRouteFreq Unsigned32 } - mvpnBgpGenMode OBJECT-TYPE + mvpnBgpMode OBJECT-TYPE SYNTAX INTEGER { + other (0), rptSpt (1), sptOnly (2) } MAX-ACCESS read-only STATUS current DESCRIPTION - "For two different BGP-MVPN modes: - rptSpt(1): inter-site shared tree mode - sptOnly(2): inter-site source-only tree mode. + "The inter-site C-tree mode used by the BGP-MVPN + represented by this entry. + + other : none of the following + rptSpt : inter-site shared tree mode + (Rendezvous Point Tree (RPT) and + source-specific shortest-path tree (SPT)) + sptOnly : inter-site source-only tree mode " REFERENCE "RFC6513, Section 9.3.1" - ::= { mvpnBgpGenericEntry 1 } + ::= { mvpnBgpEntry 1 } - mvpnBgpGenVrfRouteImport OBJECT-TYPE + mvpnBgpVrfRouteImportExtendedCommunity OBJECT-TYPE SYNTAX MplsL3VpnRouteDistinguisher MAX-ACCESS read-only STATUS current DESCRIPTION - "The VRF Route Import Extended Community that this PE - adds to unicast VPN routes that it advertises for this MVPN. + "The VRF Route Import Extended Community added by this PE + to unicast VPN routes that it advertises for the BGP-MVPN + corresponding to this entry. + " REFERENCE "RFC6514, Section 7 " - ::= { mvpnBgpGenericEntry 2 } + ::= { mvpnBgpEntry 2 } - mvpnBgpGenSrcAs OBJECT-TYPE - SYNTAX InetAutonomousSystemNumber + mvpnBgpSrcASExtendedCommunity OBJECT-TYPE + SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The Source AS number in Source AS Extended Community that this - PE adds to the unicast VPN routes that it advertises for - this MVPN. + "The Source AS Extended Community added by this PE + to the unicast VPN routes that it advertises for + the BGP-MVPN represented by this entry. " REFERENCE "RFC6514, Section 6 " - ::= { mvpnBgpGenericEntry 3 } - - mvpnBgpGenCmcastRouteWithdrawalTimer OBJECT-TYPE - SYNTAX Unsigned32 - MAX-ACCESS read-write - STATUS current - DESCRIPTION - "The configurable timer to control the delay - for the advertisement of withdrawals of - C-multicast routes. - - " - REFERENCE - "RFC6514, Section 16.1.1" - ::= { mvpnBgpGenericEntry 4 } - - mvpnBgpGenSrcSharedTreeJoinTimer OBJECT-TYPE - SYNTAX Unsigned32 - MAX-ACCESS read-write - STATUS current - DESCRIPTION - "The configurable timer to control the delay - for the advertisement of Source/Shared Tree Join - C-multicast routes. - " - REFERENCE - "RFC6514, Section 16.1.2" - ::= { mvpnBgpGenericEntry 5 } + ::= { mvpnBgpEntry 3 } - mvpnBgpGenMsgRateLimit OBJECT-TYPE - SYNTAX Unsigned32 + mvpnBgpMsgRateLimit OBJECT-TYPE + SYNTAX Unsigned32 (0..4294967295) + UNITS "messages per second" MAX-ACCESS read-write STATUS current DESCRIPTION - "The upper bounds on rate of BGP message exchange among PEs - for exchanging C-multicast routing information + "The configurable upper bound for the rate of BGP C-multicast + routing information message exchange between this PE and other + PEs in the BGP-MVPN corresponding to this entry. " REFERENCE "RFC6514, Section 17" - ::= { mvpnBgpGenericEntry 6 } + ::= { mvpnBgpEntry 4 } - mvpnBgpGenMaxSpmsiAdRoutes OBJECT-TYPE - SYNTAX Unsigned32 + mvpnBgpMaxSpmsiAdRoutes OBJECT-TYPE + SYNTAX Unsigned32 (0..4294967295) MAX-ACCESS read-write STATUS current DESCRIPTION - "The upper bound on the number of S-PMSI A-D routes. + "The configurable upper bound for the number of + S-PMSI A-D routes for the BGP-MVPN corresponding to + this entry. " REFERENCE "RFC6514, Section 17" - ::= { mvpnBgpGenericEntry 7 } + ::= { mvpnBgpEntry 5 } - mvpnBgpGenMaxSpmsiAdRouteFreq OBJECT-TYPE - SYNTAX Unsigned32 + mvpnBgpMaxSpmsiAdRouteFreq OBJECT-TYPE + SYNTAX Unsigned32 (0..4294967295) + UNITS "routes per second" MAX-ACCESS read-write STATUS current DESCRIPTION - "The upper bound on how frequently S-PMSI A-D routes - may be generated. - + "The configurable upper bound for the frequency of + S-PMSI A-D route generation for the BGP-MVPN corresponding + to this entry. " REFERENCE "RFC6514, Section 17" - ::= { mvpnBgpGenericEntry 8 } + ::= { mvpnBgpEntry 6 } - mvpnBgpGenMaxSrcActiveAdRoutes OBJECT-TYPE - SYNTAX Unsigned32 + mvpnBgpMaxSrcActiveAdRoutes OBJECT-TYPE + SYNTAX Unsigned32 (0..4294967295) MAX-ACCESS read-write STATUS current DESCRIPTION - "The upper bound on the number of Source Active A-D routes. + "The configurable upper bound for the number of + Source Active A-D routes for the BGP-MVPN corresponding + to this entry. " REFERENCE "RFC6514, Section 17" - ::= { mvpnBgpGenericEntry 9 } + ::= { mvpnBgpEntry 7 } - mvpnBgpGenMaxSrcActiveAdRouteFreq OBJECT-TYPE - SYNTAX Unsigned32 + mvpnBgpMaxSrcActiveAdRouteFreq OBJECT-TYPE + SYNTAX Unsigned32 (0..4294967295) + UNITS "routes per second" MAX-ACCESS read-write STATUS current DESCRIPTION - "The upper bound on how frequently Source Active A-D routes - may be generated. + "The configurable upper bound for the frequency of Source + Active A-D route generation for the BGP-MVPN corresponding + to this entry. " REFERENCE "RFC6514, Section 17" - ::= { mvpnBgpGenericEntry 10 } + ::= { mvpnBgpEntry 8 } - -- PMSI Configuration Table + -- Table of PMSI information mvpnPmsiTable OBJECT-TYPE SYNTAX SEQUENCE OF MvpnPmsiEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "An entry in this table corresponds to - the attribute information of a specific - PMSI configured on a PE router. + "A conceptual table containing information related + to PMSIs on this PE. " - ::= { mvpnConfig 1 } + ::= { mvpnObjects 4 } mvpnPmsiEntry OBJECT-TYPE SYNTAX MvpnPmsiEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A conceptual row corresponding to a specific - PMSI on this router. - + "A conceptual row corresponding to a + PMSI on this PE. " INDEX { mvpnPmsiTunnelIfIndex } ::= { mvpnPmsiTable 1 } MvpnPmsiEntry ::= SEQUENCE { mvpnPmsiTunnelIfIndex InterfaceIndex, + mvpnPmsiRD MplsL3VpnRouteDistinguisher, mvpnPmsiTunnelType L2L3VpnMcastProviderTunnelType, + mvpnPmsiTunnelAttribute RowPointer, mvpnPmsiTunnelPimGroupAddrType InetAddressType, mvpnPmsiTunnelPimGroupAddr InetAddress, mvpnPmsiEncapsulationType INTEGER } mvpnPmsiTunnelIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION - "This is a unique index for an entry in the - mvpnPmsiTable. A non-zero index for an - entry indicates the ifIndex for the corresponding - entry of PMSI in the ifTable. + "A unique value for this conceptual row. Its value + will be the same as that of the ifIndex object instance + for the corresponding PMSI in ifTable. " REFERENCE - "RFC2863 + "RFC2863 Sec. 3.1.5 " ::= { mvpnPmsiEntry 1 } + mvpnPmsiRD OBJECT-TYPE + SYNTAX MplsL3VpnRouteDistinguisher + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The Route Distinguisher for this I-PMSI." + ::= { mvpnPmsiEntry 3 } + mvpnPmsiTunnelType OBJECT-TYPE SYNTAX L2L3VpnMcastProviderTunnelType - MAX-ACCESS not-accessible + MAX-ACCESS read-only STATUS current DESCRIPTION - "This object indicates the type of tunnel used to - instantiate the PMSI corresponding to this entry" + "The type of tunnel used to + instantiate the PMSI corresponding to this entry. + " REFERENCE - "RFC6513 Sec. 2.6 + "RFC6513, Sec. 2.6 " - ::= { mvpnPmsiEntry 2 } + ::= { mvpnPmsiEntry 4 } + + mvpnPmsiTunnelAttribute OBJECT-TYPE + SYNTAX RowPointer + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "A pointer to a conceptual row representing + the P-tunnel used by the PMSI in + l2L3VpnMcastPmsiTunnelAttributeTable. + " + ::= { mvpnPmsiEntry 5 } mvpnPmsiTunnelPimGroupAddrType OBJECT-TYPE SYNTAX InetAddressType - MAX-ACCESS not-accessible + MAX-ACCESS read-only STATUS current DESCRIPTION - "When the PIM provider tunnel is used for instantiating - the PMSI corresponding to this entry, i.e., - the value of mvpnPmsiTunnelType is + "The InetAddressType of the mvpnPmsiTunnelPimGroupAddr object + that follows. + When the PMSI corresponding to this entry does not use + the PIM provider tunnel, i.e., + the value of mvpnPmsiTunnelType is not one of pimSsm(3), pimAsm(4), or pimBidir(5), - this object indicates the type of tunnel address. - Otherwise, the value of this object will be - unknown(0). + this object should be unknown(0). " - ::= { mvpnPmsiEntry 3 } + ::= { mvpnPmsiEntry 6 } mvpnPmsiTunnelPimGroupAddr OBJECT-TYPE SYNTAX InetAddress - MAX-ACCESS not-accessible + MAX-ACCESS read-only STATUS current DESCRIPTION - "When the PIM provider tunnel is used for instantiating - the PMSI corresponding to this entry, i.e., - the value of mvpnPmsiTunnelType is + "The tunnel address which is used by the PMSI + corresponding to this entry. + When the PMSI corresponding to this entry does not + use PIM provider tunnel, i.e., + the value of mvpnPmsiTunnelType is not one of pimSsm(3), pimAsm(4), or pimBidir(5), - this object indicates the tunnel address. - Otherwise, the value of this object will be - a string of length zero. + this object should be a zero-length octet string. " - ::= { mvpnPmsiEntry 4 } + ::= { mvpnPmsiEntry 7 } mvpnPmsiEncapsulationType OBJECT-TYPE SYNTAX INTEGER { greIp (1), ipIp (2), mpls (3) } MAX-ACCESS read-only STATUS current DESCRIPTION - "The encapsulation type to be used for sending - packets through a P-tunnel. + "The encapsulation type used for sending + packets through the PMSI corresponding to this entry. - The enumerated values and the corresponding - encapsulation types are as follows: + The enumerated encapsulation types and the corresponding + descriptions are as follows: - greIp (0) : GRE (Generic Routing Encapsulation) encapsulation [RFC2784] - ipIp (1) : IP-in-IP encapsulation [RFC2003] - mpls (2) : MPLS encapsulation [RFC3032] + greIp : GRE (Generic Routing Encapsulation) + encapsulation [RFC2784] + ipIp : IP-in-IP encapsulation [RFC2003] + mpls : MPLS encapsulation [RFC3032] " REFERENCE "RFC2003 RFC2784 RFC3032 - RFC6513 Sec. 12.1 + RFC6513, Sec. 12.1 " + ::= { mvpnPmsiEntry 8 } - ::= { mvpnPmsiEntry 5 } - - -- S-PMSI configuration table + -- Table of S-PMSI specific information mvpnSpmsiTable OBJECT-TYPE SYNTAX SEQUENCE OF MvpnSpmsiEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "An entry in this table corresponds to - a specific S-PMSI configured on a PE router. - This table stores only S-PMSI specific - attribute information and generic attribute - information of the S-PMSI is stored in - mvpnPmsiTable. - Therefore, there MUST be corresponding entry - that pertains to the S-PMSI, in mvpnPmsiTable. + "A conceptual table containing information related + to S-PMSIs on this PE. + This table stores only S-PMSI specific attribute + information. Generic PMSI attribute information of + S-PMSIs is stored in mvpnPmsiTable. " - ::= { mvpnConfig 2 } + ::= { mvpnObjects 5 } mvpnSpmsiEntry OBJECT-TYPE SYNTAX MvpnSpmsiEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A conceptual row corresponding to a specific - S-PMSI on this router. - - Implementers need to be aware that there are quite a few - index objects that together can exceed the size allowed - for an Object Identifier (OID). So implementers must make - sure that OIDs of column instances in this table will have - no more than 128 sub-identifiers, otherwise they cannot be - accessed using SNMPv1, SNMPv2c, or SNMPv3. + "A conceptual row corresponding to an S-PMSI on this PE. + Implementers need to be aware that if the total number of + octets in mplsL3VpnVrfName, mvpnSpmsiCmcastGroupAddr and + mvpnSpmsiCmcastSourceAddr exceeds 113, the OIDs of column + instances in this row will have more than 128 sub-identifiers + and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. " INDEX { mplsL3VpnVrfName, - mvpnSpmsiCmcastAddrType, + mvpnSpmsiCmcastGroupAddrType, mvpnSpmsiCmcastGroupAddr, mvpnSpmsiCmcastGroupPrefixLen, + mvpnSpmsiCmcastSourceAddrType, mvpnSpmsiCmcastSourceAddr, mvpnSpmsiCmcastSourcePrefixLen } ::= { mvpnSpmsiTable 1 } MvpnSpmsiEntry ::= SEQUENCE { - mvpnSpmsiCmcastAddrType InetAddressType, + mvpnSpmsiCmcastGroupAddrType InetAddressType, mvpnSpmsiCmcastGroupAddr InetAddress, mvpnSpmsiCmcastGroupPrefixLen InetAddressPrefixLength, + mvpnSpmsiCmcastSourceAddrType InetAddressType, mvpnSpmsiCmcastSourceAddr InetAddress, mvpnSpmsiCmcastSourcePrefixLen InetAddressPrefixLength, - mvpnSpmsiThreshold Unsigned32, mvpnSpmsiPmsiPointer RowPointer } - mvpnSpmsiCmcastAddrType OBJECT-TYPE + mvpnSpmsiCmcastGroupAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION - "Type of C-multicast source and group addresses of - a particular C-flow which is assigned to an S-PMSI - corresponding to this entry." + "The InetAddressType of the mvpnSpmsiCmcastGroupAddr object + that follows. + " ::= { mvpnSpmsiEntry 1 } mvpnSpmsiCmcastGroupAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A group address of a particular C-flow which is - assigned to an S-PMSI corresponding to this entry." + "The group address of the C-flow assigned to the + S-PMSI corresponding to this entry." + REFERENCE + "RFC6513, Sec. 3.1" ::= { mvpnSpmsiEntry 2 } mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A prefix length of mvpnSpmsiCmcastGroupAddr. - A group 0 (or ::0) with prefix length 32 (or 128) - indicates wildcard group, while a group 0 (or ::0) - with prefix length 0 indicates any group. + "The prefix length of the corresponding + mvpnSpmsiCmcastGroupAddr object. " ::= { mvpnSpmsiEntry 3 } - mvpnSpmsiCmcastSourceAddr OBJECT-TYPE - SYNTAX InetAddress + mvpnSpmsiCmcastSourceAddrType OBJECT-TYPE + SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A source address of a particular C-flow which is - assigned to an S-PMSI corresponding to this entry." + "The InetAddressType of the mvpnSpmsiCmcastSourceAddr object + that follows. + " ::= { mvpnSpmsiEntry 4 } - mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE - SYNTAX InetAddressPrefixLength + mvpnSpmsiCmcastSourceAddr OBJECT-TYPE + SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A prefix length of mvpnSpmsiCmcastSourceAddr. - A source 0 (or ::0) with prefix length 32 (or 128) - indicates a wildcard source, while a source 0 (or ::0) - with prefix length 0 indicates any source. - " + "The source address of the C-flow assigned to the + S-PMSI corresponding to this entry." ::= { mvpnSpmsiEntry 5 } - mvpnSpmsiThreshold OBJECT-TYPE - SYNTAX Unsigned32 (0..4294967295) - UNITS "kilobits per second" - MAX-ACCESS read-write + mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE + SYNTAX InetAddressPrefixLength + MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The bandwidth threshold value which when exceeded for a - multicast routing entry in the given MVRF, triggers usage - of S-PMSI. + "The prefix length of the corresponding + mvpnSpmsiCmcastSourceAddr object. " - REFERENCE - "RFC6513 Sec. 7.2" ::= { mvpnSpmsiEntry 6 } mvpnSpmsiPmsiPointer OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION - "This points to a row in mvpnPmsiTable, - to specify tunnel attributes. + "A pointer to a conceptual row representing + generic information of this S-PMSI in mvpnPmsiTable. " ::= { mvpnSpmsiEntry 7 } - -- Table of intra-as I-PMSIs advertised/received + -- Table of statistics pertaining to + -- advertisements sent/received - mvpnIpmsiAdvtTable OBJECT-TYPE - SYNTAX SEQUENCE OF MvpnIpmsiAdvtEntry + mvpnAdvtStatsTable OBJECT-TYPE + SYNTAX SEQUENCE OF MvpnAdvtStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "This table is for all advertised/received I-PMSI - advertisements. + "A conceptual table containing statistics pertaining to + I-PMSI and S-PMSI advertisements sent/received by this PE. " - ::= { mvpnStates 1 } + ::= { mvpnObjects 6 } - mvpnIpmsiAdvtEntry OBJECT-TYPE - SYNTAX MvpnIpmsiAdvtEntry + mvpnAdvtStatsEntry OBJECT-TYPE + SYNTAX MvpnAdvtStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "An entry in this table corresponds to an I-PMSI - advertisement that is advertised/received by this router. - This represents all the sender PEs in the MVPN, - with the provider tunnel they use to send traffic. + "A conceptual row corresponding to statistics + pertaining to advertisements sent/received + for a particular MVPN on this PE. - Implementers need to be aware that there are quite a few - index objects that together can exceed the size allowed - for an Object Identifier (OID). So implementers must make - sure that OIDs of column instances in this table will have - no more than 128 sub-identifiers, otherwise they cannot be - accessed using SNMPv1, SNMPv2c, or SNMPv3. + Implementers need to be aware that if the total number of + octets in mplsL3VpnVrfName and mvpnAdvtPeerAddr exceeds 115, + then OIDs of column instances in this row will have more than + 128 sub-identifiers and cannot be accessed using SNMPv1, + SNMPv2c, or SNMPv3. " INDEX { mplsL3VpnVrfName, - mvpnIpmsiAdvtAfi, - mvpnIpmsiAdvtRD, - mvpnIpmsiAdvtOrigAddrType, - mvpnIpmsiAdvtOrigAddr + mvpnAdvtType, + mvpnAdvtPeerAddrType, + mvpnAdvtPeerAddr } - ::= { mvpnIpmsiAdvtTable 1 } + ::= { mvpnAdvtStatsTable 1 } - MvpnIpmsiAdvtEntry ::= SEQUENCE { - mvpnIpmsiAdvtAfi INTEGER, - mvpnIpmsiAdvtRD MplsL3VpnRouteDistinguisher, - mvpnIpmsiAdvtOrigAddrType InetAddressType, - mvpnIpmsiAdvtOrigAddr InetAddress, - mvpnIpmsiAdvtTunnelAttribute RowPointer, - mvpnIpmsiAdvtReceived Counter32, - mvpnIpmsiAdvtReceivedError Counter32, - mvpnIpmsiAdvtMalformedTunnelType Counter32, - mvpnIpmsiAdvtMalformedTunnelId Counter32, - mvpnIpmsiAdvtLastReceivedTime TimeStamp, - mvpnIpmsiAdvtCounterDiscontinuityTime TimeStamp + MvpnAdvtStatsEntry ::= SEQUENCE { + mvpnAdvtType INTEGER, + mvpnAdvtPeerAddrType InetAddressType, + mvpnAdvtPeerAddr InetAddress, + mvpnAdvtSent Counter32, + mvpnAdvtReceived Counter32, + mvpnAdvtReceivedError Counter32, + mvpnAdvtReceivedMalformedTunnelType Counter32, + mvpnAdvtReceivedMalformedTunnelId Counter32, + mvpnAdvtLastSentTime DateAndTime, + mvpnAdvtLastReceivedTime DateAndTime, + mvpnAdvtCounterDiscontinuityTime TimeStamp } - mvpnIpmsiAdvtAfi OBJECT-TYPE + mvpnAdvtType OBJECT-TYPE SYNTAX INTEGER { - ipv4(1), - ipv6(2) + intraAsIpmsi (0), + interAsIpmsi (1), + sPmsi (2) } MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The address family this I-PMSI is for." + "The PMSI type. - ::= { mvpnIpmsiAdvtEntry 1 } + The enumerated PMSI types and corresponding + descriptions are as follows: - mvpnIpmsiAdvtRD OBJECT-TYPE - SYNTAX MplsL3VpnRouteDistinguisher - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The Route Distinguisher in this I-PMSI." - ::= { mvpnIpmsiAdvtEntry 2 } + intraAsIpmsi : Intra-AS Inclusive PMSI + interAsIpmsi : Inter-AS Inclusive PMSI + sPmsi : Selective PMSI + " + REFERENCE + "RFC6513, Sec. 3.2.1" + ::= { mvpnAdvtStatsEntry 1 } - mvpnIpmsiAdvtOrigAddrType OBJECT-TYPE + mvpnAdvtPeerAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The Internet address type of mvpnIpmsiAdvtOrigAddr." - ::= { mvpnIpmsiAdvtEntry 3 } + "The InternetAddressType of the mvpnAdvtPeerAddr object + that follows. + " + ::= { mvpnAdvtStatsEntry 2 } - mvpnIpmsiAdvtOrigAddr OBJECT-TYPE + mvpnAdvtPeerAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The BGP address of the PE that originated the I-PMSI." - ::= { mvpnIpmsiAdvtEntry 4 } - - mvpnIpmsiAdvtTunnelAttribute OBJECT-TYPE - SYNTAX RowPointer - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Points to a row in the l2L3VpnMcastPmsiTunnelAttributeTable." - ::= { mvpnIpmsiAdvtEntry 5 } - - mvpnIpmsiAdvtReceived OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of I-PMSI advertisements received by the PE router. - This includes advertisements that were discarded. - Discontinuities in the value of this counter can - occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnIpmsiAdvtCounterDiscontinuityTime. - " - ::= { mvpnIpmsiAdvtEntry 6 } - - mvpnIpmsiAdvtReceivedError OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of errors in the I-PMSI advertisements - received by the PE router. - The value of this object is the sum of - the values of mvpnIpmsiAdvtMalformedTunnelType and - mvpnIpmsiAdvtMalformedTunnelId. - Discontinuities in the value of this counter can - occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnIpmsiAdvtCounterDiscontinuityTime. + "The address of a peer PE that exchanges advertisement with + this PE. " - ::= { mvpnIpmsiAdvtEntry 7 } + ::= { mvpnAdvtStatsEntry 3 } - mvpnIpmsiAdvtMalformedTunnelType OBJECT-TYPE + mvpnAdvtSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of received I-PMSI advertisements that - contain a PMSI Tunnel attribute whose Tunnel - Type field has an undefined tunnel type. - Discontinuities in the value of this counter can - occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnIpmsiAdvtCounterDiscontinuityTime. - " - REFERENCE - "RFC6514 Sec.5" - ::= { mvpnIpmsiAdvtEntry 8 } + "The number of advertisements successfully + sent to the peer PE specified by the corresponding + mvpnAdvtPeerAddr. - mvpnIpmsiAdvtMalformedTunnelId OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of received I-PMSI advertisements that - contain a PMSI Tunnel attribute whose Tunnel - Identifier field cannot be parsed as a - tunnel identifier of the tunnel types specified in - the Tunnel type field of the attribute. Discontinuities in the value of this counter can occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnIpmsiAdvtCounterDiscontinuityTime. - - " - REFERENCE - "RFC6514 Sec.5" - ::= { mvpnIpmsiAdvtEntry 9 } - - mvpnIpmsiAdvtLastReceivedTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime when the last I-PMSI - advertisement was received by the PE router. - " - ::= { mvpnIpmsiAdvtEntry 10 } - - mvpnIpmsiAdvtCounterDiscontinuityTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime on the most recent occasion - at which any one or more of this syslog application's - counters, viz., counters with OID prefix - 'mvpnIpmsiAdvtReceived' or - 'mvpnIpmsiAdvtReceivedError' or - 'mvpnIpmsiAdvtMalformedTunnelType' or - 'mvpnIpmsiAdvtMalformedTunnelId' suffered a - discontinuity. - If no such discontinuities have occurred since the - last re-initialization of the local management - subsystem, then this object will have a zero value. - " - ::= { mvpnIpmsiAdvtEntry 11 } - - -- Table of inter-as I-PMSIs advertised/received - - mvpnInterAsIpmsiAdvtTable OBJECT-TYPE - SYNTAX SEQUENCE OF MvpnInterAsIpmsiAdvtEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "This table is for all advertised/received inter-as I-PMSI - advertisements." - ::= { mvpnStates 2 } - - mvpnInterAsIpmsiAdvtEntry OBJECT-TYPE - SYNTAX MvpnInterAsIpmsiAdvtEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "An entry in this table corresponds to an inter-as I-PMSI - advertisement that is advertised/received by this router. - This represents all the ASes in the MVPN, - with the provider tunnel used to send traffic to. - - Implementers need to be aware that there are quite a few - index objects that together can exceed the size allowed - for an Object Identifier (OID). So implementers must make - sure that OIDs of column instances in this table will have - no more than 128 sub-identifiers, otherwise they cannot be - accessed using SNMPv1, SNMPv2c, or SNMPv3. + and at other times as indicated by the corresponding + mvpnAdvtCounterDiscontinuityTime object. " - INDEX { - mplsL3VpnVrfName, - mvpnInterAsIpmsiAdvtAfi, - mvpnInterAsIpmsiAdvtRD, - mvpnInterAsIpmsiAdvtSrcAs - } - ::= { mvpnInterAsIpmsiAdvtTable 1 } - - MvpnInterAsIpmsiAdvtEntry ::= SEQUENCE { - mvpnInterAsIpmsiAdvtAfi INTEGER, - mvpnInterAsIpmsiAdvtRD MplsL3VpnRouteDistinguisher, - mvpnInterAsIpmsiAdvtSrcAs InetAutonomousSystemNumber, - mvpnInterAsIpmsiAdvtTunnelAttribute RowPointer, - mvpnInterAsIpmsiAdvtReceived Counter32, - mvpnInterAsIpmsiAdvtReceivedError Counter32, - mvpnInterAsIpmsiAdvtMalformedTunnelType Counter32, - mvpnInterAsIpmsiAdvtMalformedTunnelId Counter32, - mvpnInterAsIpmsiAdvtLastReceivedTime TimeStamp, - mvpnInterAsIpmsiAdvtCounterDiscontinuityTime TimeStamp - } - - mvpnInterAsIpmsiAdvtAfi OBJECT-TYPE - SYNTAX INTEGER { - ipv4(1), - ipv6(2) - } - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The address family this I-PMSI is for." - ::= { mvpnInterAsIpmsiAdvtEntry 1 } - - mvpnInterAsIpmsiAdvtRD OBJECT-TYPE - SYNTAX MplsL3VpnRouteDistinguisher - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The Route Distinguisher in this inter-as I-PMSI." - ::= { mvpnInterAsIpmsiAdvtEntry 2 } - - mvpnInterAsIpmsiAdvtSrcAs OBJECT-TYPE - SYNTAX InetAutonomousSystemNumber - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The source-as in this inter-as I-PMSI." - ::= { mvpnInterAsIpmsiAdvtEntry 3 } - - mvpnInterAsIpmsiAdvtTunnelAttribute OBJECT-TYPE - SYNTAX RowPointer - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Points to a row in the l2L3VpnMcastPmsiTunnelAttributeTable." - ::= { mvpnInterAsIpmsiAdvtEntry 4 } + ::= { mvpnAdvtStatsEntry 4 } - mvpnInterAsIpmsiAdvtReceived OBJECT-TYPE + mvpnAdvtReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of Inter-AS I-PMSI advertisements received - by the PE router. + "The number of advertisements received from the peer PE + specified by the corresponding mvpnAdvtPeerAddr object. This includes advertisements that were discarded. - Discontinuities in the value of this counter can - occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnInterAsIpmsiAdvtCounterDiscontinuityTime. - " - ::= { mvpnInterAsIpmsiAdvtEntry 5 } - mvpnInterAsIpmsiAdvtReceivedError OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of errors in the Inter-AS I-PMSI - advertisements received by the PE router. - The value of this object is the sum of - the values of mvpnInterAsIpmsiAdvtMalformedTunnelType and - mvpnInterAsIpmsiAdvtMalformedTunnelId. Discontinuities in the value of this counter can occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnInterAsIpmsiAdvtCounterDiscontinuityTime. + and at other times as indicated by the corresponding + mvpnAdvtCounterDiscontinuityTime object. " - ::= { mvpnInterAsIpmsiAdvtEntry 6 } + ::= { mvpnAdvtStatsEntry 5 } - mvpnInterAsIpmsiAdvtMalformedTunnelType OBJECT-TYPE + mvpnAdvtReceivedError OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of received Inter-AS I-PMSI advertisements that - contain a PMSI Tunnel attribute whose Tunnel - Type field has an undefined tunnel type. - Discontinuities in the value of this counter can - occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnInterAsIpmsiAdvtCounterDiscontinuityTime. - " - REFERENCE - "RFC6514 Sec.5" - ::= { mvpnInterAsIpmsiAdvtEntry 7 } + "The total number of advertisements received from a peer PE, + specified by the corresponding mvpnAdvtPeerAddr object, + that were rejected due to error(s) in the advertisement. + The value of this object includes + the error cases counted in the corresponding + mvpnAdvtReceivedMalformedTunnelType and + mvpnAdvtReceivedMalformedTunnelId objects. - mvpnInterAsIpmsiAdvtMalformedTunnelId OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of received Inter-AS I-PMSI advertisements that - contain a PMSI Tunnel attribute whose Tunnel - Identifier field cannot be parsed as a - tunnel identifier of the tunnel types specified in - the Tunnel type field of the attribute. Discontinuities in the value of this counter can occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnInterAsIpmsiAdvtCounterDiscontinuityTime. - " - REFERENCE - "RFC6514 Sec.5" - ::= { mvpnInterAsIpmsiAdvtEntry 8 } - - mvpnInterAsIpmsiAdvtLastReceivedTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime when the last Inter-AS I-PMSI - advertisement was received by the PE router. - " - ::= { mvpnInterAsIpmsiAdvtEntry 9 } - - mvpnInterAsIpmsiAdvtCounterDiscontinuityTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime on the most recent occasion - at which any one or more of this syslog application's - counters, viz., counters with OID prefix - 'mvpnInterAsIpmsiAdvtReceived' or - 'mvpnInterAsIpmsiAdvtReceivedError' or - 'mvpnInterAsIpmsiAdvtMalformedTunnelType' or - 'mvpnInterAsIpmsiAdvtMalformedTunnelId' suffered a - discontinuity. - If no such discontinuities have occurred since the - last re-initialization of the local management - subsystem, then this object will have a zero value. - " - ::= { mvpnInterAsIpmsiAdvtEntry 10 } - - -- Table of S-PMSIs advertised/received - - mvpnSpmsiAdvtTable OBJECT-TYPE - SYNTAX SEQUENCE OF MvpnSpmsiAdvtEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "This table has information about the S-PMSIs sent/received - by a PE. - " - ::= { mvpnStates 3 } - - mvpnSpmsiAdvtEntry OBJECT-TYPE - SYNTAX MvpnSpmsiAdvtEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "An entry in this table is created or updated for each S-PMSI - advertised/received in a particular MVRF. - - Implementers need to be aware that there are quite a few - index objects that together can exceed the size allowed - for an Object Identifier (OID). So implementers must make - sure that OIDs of column instances in this table will have - no more than 128 sub-identifiers, otherwise they cannot be - accessed using SNMPv1, SNMPv2c, or SNMPv3. - " - INDEX { - mplsL3VpnVrfName, - mvpnSpmsiAdvtCmcastAddrType, - mvpnSpmsiAdvtCmcastGroupAddr, - mvpnSpmsiAdvtCmcastGroupPrefixLen, - mvpnSpmsiAdvtCmcastSourceAddr, - mvpnSpmsiAdvtCmcastSourcePrefixLen, - mvpnSpmsiAdvtOrigAddrType, - mvpnSpmsiAdvtOrigAddr - } - ::= { mvpnSpmsiAdvtTable 1 } - - MvpnSpmsiAdvtEntry ::= SEQUENCE { - mvpnSpmsiAdvtCmcastAddrType InetAddressType, - mvpnSpmsiAdvtCmcastGroupAddr InetAddress, - mvpnSpmsiAdvtCmcastGroupPrefixLen InetAddressPrefixLength, - mvpnSpmsiAdvtCmcastSourceAddr InetAddress, - mvpnSpmsiAdvtCmcastSourcePrefixLen InetAddressPrefixLength, - mvpnSpmsiAdvtOrigAddrType InetAddressType, - mvpnSpmsiAdvtOrigAddr InetAddress, - mvpnSpmsiAdvtTunnelAttribute RowPointer, - mvpnSpmsiAdvtExpTime TimeInterval, - mvpnSpmsiAdvtRefCnt Unsigned32, - mvpnSpmsiAdvtReceived Counter32, - mvpnSpmsiAdvtReceivedError Counter32, - mvpnSpmsiAdvtMalformedTunnelType Counter32, - mvpnSpmsiAdvtMalformedTunnelId Counter32, - mvpnSpmsiAdvtLastReceivedTime TimeStamp, - mvpnSpmsiAdvtCounterDiscontinuityTime TimeStamp - } - - mvpnSpmsiAdvtCmcastAddrType OBJECT-TYPE - SYNTAX InetAddressType - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The Internet address type of mvpnSpmsiAdvtCmcastGroup/Source." - ::= { mvpnSpmsiAdvtEntry 1 } - - mvpnSpmsiAdvtCmcastGroupAddr OBJECT-TYPE - SYNTAX InetAddress - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "S-PMSI C-multicast group address. - - If it is 0 (or ::0), this is a wildcard group, - and mvpnSpmsiAdvtCmcastGroupPrefixLen must be 32 (or 128). - " - ::= { mvpnSpmsiAdvtEntry 2 } - - mvpnSpmsiAdvtCmcastGroupPrefixLen OBJECT-TYPE - SYNTAX InetAddressPrefixLength - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "S-PMSI C-multicast group address prefix length." - ::= { mvpnSpmsiAdvtEntry 3 } - - mvpnSpmsiAdvtCmcastSourceAddr OBJECT-TYPE - SYNTAX InetAddress - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "S-PMSI C-multicast source address - If it is 0 (or ::0), this is a wildcard source, - and mvpnSpmsiAdvtCmcastSourcePrefixLen must be 32 (or 128). - " - ::= { mvpnSpmsiAdvtEntry 4 } - - mvpnSpmsiAdvtCmcastSourcePrefixLen OBJECT-TYPE - SYNTAX InetAddressPrefixLength - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "S-PMSI C-multicast source address prefix length." - ::= { mvpnSpmsiAdvtEntry 5 } - - mvpnSpmsiAdvtOrigAddrType OBJECT-TYPE - SYNTAX InetAddressType - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The Internet address type of mvpnSpmsiAdvtOrigAddr." - ::= { mvpnSpmsiAdvtEntry 6 } - - mvpnSpmsiAdvtOrigAddr OBJECT-TYPE - SYNTAX InetAddress - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The BGP address of the PE that originated the S-PMSI." - ::= { mvpnSpmsiAdvtEntry 7 } - - mvpnSpmsiAdvtTunnelAttribute OBJECT-TYPE - SYNTAX RowPointer - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "A row pointer to the l2L3VpnMcastPmsiTunnelAttributeTable" - ::= { mvpnSpmsiAdvtEntry 8 } - - mvpnSpmsiAdvtExpTime OBJECT-TYPE - SYNTAX TimeInterval - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "For UDP-based S-PMSI signaling for PIM-MVPN, - the amount of time remaining before this - received S-PMSI Join Message expires, - or the next S-PMSI Join Message refresh is to be - advertised again from the PE. - Otherwise, it is 0. - " - ::= { mvpnSpmsiAdvtEntry 9 } - - mvpnSpmsiAdvtRefCnt OBJECT-TYPE - SYNTAX Unsigned32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of c-multicast routes that are mapped to - this S-PMSI. + and at other times as indicated by the corresponding + mvpnAdvtCounterDiscontinuityTime object. " - ::= { mvpnSpmsiAdvtEntry 10 } + ::= { mvpnAdvtStatsEntry 6 } - mvpnSpmsiAdvtReceived OBJECT-TYPE + mvpnAdvtReceivedMalformedTunnelType OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of S-PMSI advertisements received by the PE router. - This includes advertisements that were discarded. - Discontinuities in the value of this counter can - occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnIpmsiAdvtCounterDiscontinuityTime. - " - ::= { mvpnSpmsiAdvtEntry 11 } + "The total number of advertisements received from the peer PE + specified by the corresponding mvpnAdvtPeerAddr object, + that were rejected due to malformed Tunnel Type + in the PMSI Tunnel attribute. - mvpnSpmsiAdvtReceivedError OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of errors in the S-PMSI advertisements - received by the PE router. - The value of this object is the sum of - the values of mvpnSpmsiAdvtMalformedTunnelType and - mvpnSpmsiAdvtMalformedTunnelId. Discontinuities in the value of this counter can occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnSpmsiAdvtCounterDiscontinuityTime. + and at other times as indicated by the corresponding + mvpnAdvtCounterDiscontinuityTime object. " - ::= { mvpnSpmsiAdvtEntry 12 } + REFERENCE + "RFC6514 Sec.5" + ::= { mvpnAdvtStatsEntry 7 } - mvpnSpmsiAdvtMalformedTunnelType OBJECT-TYPE + mvpnAdvtReceivedMalformedTunnelId OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of received S-PMSI advertisements that - contain a PMSI Tunnel attribute whose Tunnel - Type field has an undefined tunnel type. + "The total number of advertisements received from the peer PE + specified by the corresponding mvpnAdvtPeerAddr object, + that were rejected due to malformed Tunnel Identifier + in the PMSI Tunnel attribute. Discontinuities in the value of this counter can occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnSpmsiAdvtCounterDiscontinuityTime. + and at other times as indicated by the corresponding + mvpnAdvtCounterDiscontinuityTime object. " REFERENCE "RFC6514 Sec.5" - ::= { mvpnSpmsiAdvtEntry 13 } + ::= { mvpnAdvtStatsEntry 8 } - mvpnSpmsiAdvtMalformedTunnelId OBJECT-TYPE - SYNTAX Counter32 + mvpnAdvtLastSentTime OBJECT-TYPE + SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of received S-PMSI advertisements that - contain a PMSI Tunnel attribute whose Tunnel - Identifier field cannot be parsed as a - tunnel identifier of the tunnel types specified in - the Tunnel type field of the attribute. - Discontinuities in the value of this counter can - occur at re-initialization of the management system, - and at other times as indicated by the value of - mvpnSpmsiAdvtCounterDiscontinuityTime. + "The timestamp when the last advertisement + was successfully sent by this PE. + If no advertisement has been sent since the + last re-initialization of this PE, then this + object will have a zero-length string. " - REFERENCE - "RFC6514 Sec.5" - ::= { mvpnSpmsiAdvtEntry 14 } + ::= { mvpnAdvtStatsEntry 9 } - mvpnSpmsiAdvtLastReceivedTime OBJECT-TYPE - SYNTAX TimeStamp + mvpnAdvtLastReceivedTime OBJECT-TYPE + SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION - "The value of sysUpTime when the last S-PMSI - advertisement was received by the PE router. + "The timestamp when the last advertisement + was successfully received from the peer PE specified + by the corresponding mvpnAdvtPeerAddr object and + processed by this PE. + If no advertisement has been received since the + last re-initialization of this PE, then this + object will have a zero-length string. " - ::= { mvpnSpmsiAdvtEntry 15 } + ::= { mvpnAdvtStatsEntry 10 } - mvpnSpmsiAdvtCounterDiscontinuityTime OBJECT-TYPE + mvpnAdvtCounterDiscontinuityTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime on the most recent occasion - at which any one or more of this syslog application's + at which any one or more of this application's counters, viz., counters with OID prefix - 'mvpnSpmsiAdvtReceived' or - 'mvpnSpmsiAdvtReceivedError' or - 'mvpnSpmsiAdvtMalformedTunnelType' or - 'mvpnSpmsiAdvtMalformedTunnelId' suffered a + 'mvpnAdvtSent' or + 'mvpnAdvtReceived' or + 'mvpnAdvtReceivedError' or + 'mvpnAdvtReceivedMalformedTunnelType' or + 'mvpnAdvtReceivedMalformedTunnelId' suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object will have a zero value. " - ::= { mvpnSpmsiAdvtEntry 16 } + ::= { mvpnAdvtStatsEntry 11 } -- Table of multicast routes in an MVPN mvpnMrouteTable OBJECT-TYPE SYNTAX SEQUENCE OF MvpnMrouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "This table contains multicast routing information - in MVRFs present in the PE. + "A conceptual table containing multicast routing information + corresponding to the MVRFs present on the PE. " - ::= { mvpnStates 4 } + ::= { mvpnObjects 7 } mvpnMrouteEntry OBJECT-TYPE SYNTAX MvpnMrouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "This entry corresponds to each of multicast routing - information components for IP datagrams - from a particular source and addressed to a particular - IP multicast group address. + "A conceptual row corresponding to a route for IP datagrams + from a particular source and addressed to a particular IP + multicast group address. - OIDs are limited to 128 sub-identifiers, but this limit - is not enforced by the syntax of this entry. In practice, - this does not present a problem, because IP address types - allowed by conformance statements do not exceed this limit. + Implementers need to be aware that if the total number of + octets in mplsL3VpnVrfName, mvpnMrouteCmcastGroupAddr and + mvpnMrouteCmcastSourceAddrs exceeds 113, the OIDs of column + instances in this row will have more than 128 sub-identifiers + and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. " INDEX { mplsL3VpnVrfName, mvpnMrouteCmcastGroupAddrType, mvpnMrouteCmcastGroupAddr, mvpnMrouteCmcastGroupPrefixLength, mvpnMrouteCmcastSourceAddrType, - mvpnMrouteCmcastSourceAddr, + mvpnMrouteCmcastSourceAddrs, mvpnMrouteCmcastSourcePrefixLength } ::= { mvpnMrouteTable 1 } MvpnMrouteEntry ::= SEQUENCE { mvpnMrouteCmcastGroupAddrType InetAddressType, mvpnMrouteCmcastGroupAddr InetAddress, mvpnMrouteCmcastGroupPrefixLength InetAddressPrefixLength, mvpnMrouteCmcastSourceAddrType InetAddressType, - mvpnMrouteCmcastSourceAddr InetAddress, + mvpnMrouteCmcastSourceAddrs InetAddress, mvpnMrouteCmcastSourcePrefixLength InetAddressPrefixLength, mvpnMrouteUpstreamNeighborAddrType InetAddressType, mvpnMrouteUpstreamNeighborAddr InetAddress, mvpnMrouteInIfIndex InterfaceIndexOrZero, - mvpnMrouteTimeStamp TimeStamp, mvpnMrouteExpiryTime TimeTicks, mvpnMrouteProtocol IANAipMRouteProtocol, mvpnMrouteRtProtocol IANAipRouteProtocol, mvpnMrouteRtAddrType InetAddressType, mvpnMrouteRtAddr InetAddress, mvpnMrouteRtPrefixLength InetAddressPrefixLength, mvpnMrouteRtType INTEGER, mvpnMrouteOctets Counter64, mvpnMroutePkts Counter64, - mvpnMrouteTtlDropOctets Counter64, - mvpnMrouteTtlDropPackets Counter64, - mvpnMrouteDifferentInIfOctets Counter64, - mvpnMrouteDifferentInIfPackets Counter64, - mvpnMrouteBps CounterBasedGauge64, + mvpnMrouteTtlDroppedOctets Counter64, + mvpnMrouteTtlDroppedPackets Counter64, + mvpnMrouteDroppedInOctets Counter64, + mvpnMrouteDroppedInPackets Counter64, mvpnMroutePmsiPointer RowPointer, mvpnMrouteNumberOfLocalReplication Unsigned32, - mvpnMrouteNumberOfRemoteReplication Unsigned32 + mvpnMrouteNumberOfRemoteReplication Unsigned32, + mvpnMrouteCounterDiscontinuityTime TimeStamp } mvpnMrouteCmcastGroupAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A value indicating the address family of the address - contained in mvpnMrouteGroupAddr. Legal values correspond to - the subset of address families for which multicast - forwarding is supported." + "The InetAddressType of the mvpnMrouteCmcastGroupAddr object + that follows. + " ::= { mvpnMrouteEntry 1 } mvpnMrouteCmcastGroupAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The IP multicast group address which, when combined with - the corresponding value specified in - mvpnMrouteGroupPrefixLength, identifies the groups for - which this entry contains multicast routing information. + "The IP multicast group address which, along with + the corresponding mvpnMrouteCmcastGroupPrefixLength object, + identifies destinations for which this entry contains + multicast routing information. This address object is only significant up to - mvpnMrouteGroupPrefixLength bits. The remaining address - bits are set to zero. This is especially important for this - index field, which is part of the index of this entry. Any - non-zero bits would signify an entirely different entry. + mvpnMrouteCmcastGroupPrefixLength bits. 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 length. The use of these address types indicate that this 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 } mvpnMrouteCmcastGroupPrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The length in bits of the mask which, when combined with - the corresponding value of mvpnMrouteGroupAddr, identifies the - groups for which this entry contains multicast routing - information. + "The length in bits of the mask which, along with + the corresponding mvpnMrouteCmcastGroupAddr object, + identifies destinations for which this entry contains + multicast routing information. - The InetAddressType is given by - mvpnMrouteGroupAddrType. For values 'ipv4' and - 'ipv4z', this object must be in the range 4..32. For values - 'ipv6' and 'ipv6z', this object must be in the range - 8..128. + If the corresponding InetAddressType is 'ipv4' or 'ipv4z', + this object must be in the range 4..32. + If the corresponding InetAddressType is 'ipv6' or 'ipv6z', + this object must be in the range 8..128. " ::= { mvpnMrouteEntry 3 } mvpnMrouteCmcastSourceAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A value indicating the address family of the address - contained in mvpnMrouteSourceAddr. + "The InetAddressType of the mvpnMrouteCmcastSourceAddrs object + that follows. A value of unknown(0) indicates a non-source-specific entry, corresponding to all sources in the group. Otherwise, the value MUST be the same as the value of - mvpnMrouteGroupAddrType. + mvpnMrouteCmcastGroupAddrType. " ::= { mvpnMrouteEntry 4 } - mvpnMrouteCmcastSourceAddr OBJECT-TYPE + mvpnMrouteCmcastSourceAddrs OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The network address which, when combined with the - corresponding value of mvpnMrouteSourcePrefixLength, + "The network address which, along with the + corresponding mvpnMrouteCmcastSourcePrefixLength object, identifies the sources for which this entry contains multicast routing information. This address object is only significant up to - mvpnMrouteSourcePrefixLength bits. The remaining address - bits are set to zero. This is especially important for this - index field, which is part of the index of this entry. Any - non-zero bits would signify an entirely different entry. + mvpnMrouteCmcastSourcePrefixLength bits. + 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 length. The use of these address types indicate that this source address applies only within the given zone. Zone index zero is not valid in this table. " ::= { mvpnMrouteEntry 5 } mvpnMrouteCmcastSourcePrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The length in bits of the mask which, when combined with - the corresponding value of mvpnMrouteSource, identifies - the sources for which this entry contains multicast routing - information. + "The length in bits of the mask which, along with + the corresponding mvpnMrouteCmcastSourceAddr object, + identifies the sources for which this entry contains + multicast routing information. - The InetAddressType is given by - mvpnMrouteSourceAddrType. For the value 'unknown', - this object must be zero. For values 'ipv4' and 'ipv4z', - this object must be in the range 4..32. For values 'ipv6' - and 'ipv6z', this object must be in the range 8..128." + If the corresponding InetAddressType is 'ipv4' or 'ipv4z', + this object must be in the range 4..32. + If the corresponding InetAddressType is 'ipv6' or 'ipv6z', + this object must be in the range 8..128. + If the corresponding InetAddressType is 'unknown', + this object must be zero. + " ::= { mvpnMrouteEntry 6 } mvpnMrouteUpstreamNeighborAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION - "A value indicating the address family of the address - contained in mvpnMrouteUpstreamNeighborAddr. + "The InetAddressType of the mvpnMrouteUpstreamNeighborAddr + object that follows. - An address type of unknown(0) indicates that the upstream + A value of unknown(0) indicates that the upstream neighbor is unknown, for example in BIDIR-PIM." - REFERENCE "RFC 5015" + REFERENCE + "RFC 5015" ::= { mvpnMrouteEntry 7 } mvpnMrouteUpstreamNeighborAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION - "The address of the upstream neighbor (for example, RPF - neighbor) from which IP datagrams from these sources to - this multicast address are received. + "The address of the upstream neighbor (for example, + Reverse Path Forwarding (RPF) neighbor) from which + IP datagrams from these sources represented by + this entry to this multicast address are received. " + ::= { mvpnMrouteEntry 8 } mvpnMrouteInIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-only STATUS current DESCRIPTION "The value of ifIndex for the interface on which IP - datagrams sent by these sources to this multicast address - are received. A value of 0 indicates that datagrams are not + datagrams sent by these sources represented by this entry to + this multicast address are received. + + A value 0 indicates that datagrams are not subject to an incoming interface check, but may be accepted on multiple interfaces (for example, in BIDIR-PIM). " REFERENCE "RFC 5015" ::= { mvpnMrouteEntry 9 } - mvpnMrouteTimeStamp OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at which the multicast routing - information represented by this entry was learned by the - router. - - If this information was present at the most recent re- - initialization of the local management subsystem, then this - object contains a zero value. - " - ::= { mvpnMrouteEntry 10 } - mvpnMrouteExpiryTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The minimum amount of time remaining before this entry will be aged out. The value 0 indicates that the entry is not - subject to aging. If mvpnMrouteNextHopState is pruned(1), - this object represents the remaining time until the prune - expires. If this timer expires, state reverts to - forwarding(2). Otherwise, this object represents the time - until this entry is removed from the table. + subject to aging. If the corresponding mvpnMrouteNextHopState + object is pruned(1), this object represents the remaining + time for the prune to expire after which the state will + return to forwarding(2). + If the corresponding mvpnMrouteNextHopState object is + forwarding(2), this object indicates the time after which + this entry will be removed from the table. " - ::= { mvpnMrouteEntry 11 } + ::= { mvpnMrouteEntry 10 } mvpnMrouteProtocol OBJECT-TYPE SYNTAX IANAipMRouteProtocol MAX-ACCESS read-only STATUS current DESCRIPTION "The multicast routing protocol via which this multicast forwarding entry was learned. " - ::= { mvpnMrouteEntry 12 } + ::= { mvpnMrouteEntry 11 } mvpnMrouteRtProtocol OBJECT-TYPE SYNTAX IANAipRouteProtocol MAX-ACCESS read-only STATUS current DESCRIPTION - "The routing mechanism via which the route used to find the + "The routing protocol via which the route used to find the upstream or parent interface for this multicast forwarding entry was learned. " - ::= { mvpnMrouteEntry 13 } + ::= { mvpnMrouteEntry 12 } mvpnMrouteRtAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION - "A value indicating the address family of the address - contained in mvpnMrouteRtAddr. + "The InetAddressType of the mvpnMrouteRtAddr object + that follows. " - ::= { mvpnMrouteEntry 14 } + ::= { mvpnMrouteEntry 13 } mvpnMrouteRtAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The address portion of the route used to find the upstream or parent interface for this multicast forwarding entry. This address object is only significant up to mvpnMrouteRtPrefixLength bits. The remaining address bits - are 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 length. The use of these address types indicate that this forwarding state applies only within the given zone. Zone index zero is not valid in this table. " - ::= { mvpnMrouteEntry 15 } + ::= { mvpnMrouteEntry 14 } mvpnMrouteRtPrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS read-only STATUS current DESCRIPTION "The length in bits of the mask associated with the route used to find the upstream or parent interface for this multicast forwarding entry. - The InetAddressType is given by mvpnMrouteRtAddressType. - For values 'ipv4' and 'ipv4z', this object must be in the - range 4..32. For values 'ipv6' and 'ipv6z', this object - must be in the range 8..128. + If the corresponding InetAddressType is 'ipv4' or 'ipv4z', + this object must be in the range 4..32. + If the corresponding InetAddressType is 'ipv6' or 'ipv6z', + this object must be in the range 8..128. " - ::= { mvpnMrouteEntry 16 } + ::= { mvpnMrouteEntry 15 } mvpnMrouteRtType OBJECT-TYPE SYNTAX INTEGER { - unicast (1), -- Unicast route used in multicast RIB - multicast (2) -- Multicast route + unicast (1), + multicast (2) } MAX-ACCESS read-only STATUS current DESCRIPTION - "The reason the given route was placed in the (logical) - multicast Routing Information Base (RIB). A value of - unicast means that the route would normally be placed only - in the unicast RIB, but was placed in the multicast RIB - due (instead or in addition) to local configuration, such as - when running PIM over RIP. A value of multicast means that - the route was explicitly added to the multicast RIB by the - routing protocol, such as the Distance Vector Multicast - Routing Protocol (DVMRP) or Multiprotocol BGP. + "The reason for placing the route in the (logical) + multicast Routing Information Base (RIB). + + The enumerated reasons and the corresponding + descriptions are as follows: + + unicast: + The route would normally be placed only in + the unicast RIB, but was placed in the multicast RIB + by local configuration, such as when running PIM over + RIP. + + multicast: + The route was explicitly added to the multicast RIB by + the routing protocol, such as the Distance Vector + Multicast Routing Protocol (DVMRP) or Multiprotocol BGP. " - ::= { mvpnMrouteEntry 17 } + ::= { mvpnMrouteEntry 16 } mvpnMrouteOctets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets contained in IP datagrams that were - received from these sources and addressed to this multicast - group address, and which were forwarded by this router. + received from sources represented by this entry and + addressed to this multicast group address, and which were + forwarded by this router. + + Discontinuities in the value of this counter can + occur at re-initialization of the management system, + and at other times as indicated by the corresponding + mvpnMrouteCounterDiscontinuityTime object. - Discontinuities in this monotonically increasing value - occur at re-initialization of the management system. - Discontinuities can also occur as a result of routes being - removed and replaced, which can be detected by observing - the value of mvpnMrouteTimeStamp. " - ::= { mvpnMrouteEntry 18 } + ::= { mvpnMrouteEntry 17 } mvpnMroutePkts OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of packets routed using this multicast route entry. - Discontinuities in this monotonically increasing value - occur at re-initialization of the management system. - Discontinuities can also occur as a result of routes being - removed and replaced, which can be detected by observing - the value of mvpnMrouteTimeStamp. + Discontinuities in the value of this counter can + occur at re-initialization of the management system, + and at other times as indicated by the corresponding + mvpnMrouteCounterDiscontinuityTime object. " - ::= { mvpnMrouteEntry 19 } + ::= { mvpnMrouteEntry 18 } - mvpnMrouteTtlDropOctets OBJECT-TYPE + mvpnMrouteTtlDroppedOctets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets contained in IP datagrams that this - router has received from these sources and addressed to this - multicast group address, which were dropped because the TTL - (IPv4) or Hop Limit (IPv6) was decremented to zero, or to a - value less than ipMcastInterfaceTtl for all next hops. - - Discontinuities in this monotonically increasing value - occur at re-initialization of the management system. - Discontinuities can also occur as a result of routes being - removed and replaced, which can be detected by observing - the value of mvpnMrouteTimeStamp. - " - ::= { mvpnMrouteEntry 20 } + router has received from sources represented by + this entry and addressed to this multicast group address, + which were dropped due to Time To Live (TTL) issues. + TTL issues occur when the TTL (IPv4) or Hop Limit (IPv6) + of the incoming packet was decremented to zero, or to a + value less than ipMcastInterfaceTtl of the corresponding + interface. - mvpnMrouteTtlDropPackets OBJECT-TYPE - SYNTAX Counter64 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of packets that this router has received from - these sources and addressed to this multicast group address, - which were dropped because the TTL (IPv4) or Hop Limit - (IPv6) was decremented to zero, or to a value less than - ipMcastInterfaceTtl for all next hops. + The ipMcastInterfaceTtl object is defined in IPMCAST-MIB + [RFC5132] and represents the datagram TTL + threshold for the interface. Any IP multicast datagrams + with a TTL (IPv4) or Hop Limit (IPv6) less than this + threshold will not be forwarded out of the interface. + The default value of 0 means all multicast packets are + forwarded out of the interface. A value of 256 means that + no multicast packets are forwarded out of the interface. - Discontinuities in this monotonically increasing value - occur at re-initialization of the management system. - Discontinuities can also occur as a result of routes being - removed and replaced, which can be detected by observing - the value of mvpnMrouteTimeStamp. + Discontinuities in the value of this counter can + occur at re-initialization of the management system, + and at other times as indicated by the corresponding + mvpnMrouteCounterDiscontinuityTime object. " - ::= { mvpnMrouteEntry 21 } + REFERENCE + "RFC5132, Sec. 6 + " + ::= { mvpnMrouteEntry 19 } - mvpnMrouteDifferentInIfOctets OBJECT-TYPE + mvpnMrouteTtlDroppedPackets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of octets contained in IP datagrams that this - router has received from these sources and addressed to this - multicast group address, which were dropped because they - were received on an unexpected interface. - - For RPF checking protocols (such as PIM-SM), these packets - arrived on interfaces other than mvpnMrouteInIfIndex, and - were dropped because of this failed RPF check. (RPF paths - are 'Reverse Path Forwarding' paths; the unicast routes to - the expected origin of multicast data flows). - Other protocols may drop packets on an incoming interface - check for different reasons (for example, BIDIR-PIM performs - a DF check on receipt of packets). All packets dropped as a - result of an incoming interface check are counted here. - - If this counter increases rapidly, this indicates a problem. - A significant quantity of multicast data is arriving at this - router on unexpected interfaces, and is not being forwarded. + "The number of packets that this router has received from + the sources represented by this entry and addressed to this + multicast group address, which were dropped due to + Time To Live (TTL) issues. TTL issues occur when the + TTL (IPv4) or Hop Limit (IPv6) of the incoming packet was + decremented to zero, or to a value less than + ipMcastInterfaceTtl of the corresponding interface. - For guidance, if the rate of increase of this counter - exceeds 1% of the rate of increase of mvpnMrouteOctets, - then there are multicast routing problems that require - investigation. + The ipMcastInterfaceTtl object is defined in IPMCAST-MIB + [RFC5132] and represents the datagram TTL + threshold for the interface. Any IP multicast datagrams + with a TTL (IPv4) or Hop Limit (IPv6) less than this + threshold will not be forwarded out of the interface. + The default value of 0 means all multicast packets are + forwarded out of the interface. A value of 256 means that + no multicast packets are forwarded out of the interface. - Discontinuities in this monotonically increasing value - occur at re-initialization of the management system. - Discontinuities can also occur as a result of routes being - removed and replaced, which can be detected by observing - the value of mvpnMrouteTimeStamp. + Discontinuities in the value of this counter can + occur at re-initialization of the management system, + and at other times as indicated by the corresponding + mvpnMrouteCounterDiscontinuityTime object. " REFERENCE - "RFC 4601 - RFC 5015 + "RFC5132, Sec. 6 " - ::= { mvpnMrouteEntry 22 } + ::= { mvpnMrouteEntry 20 } - mvpnMrouteDifferentInIfPackets OBJECT-TYPE + mvpnMrouteDroppedInOctets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of packets which this router has received from - these sources and addressed to this multicast group address, - which were dropped because they were received on an - unexpected interface. - - For RPF checking protocols (such as PIM-SM), these packets - arrived on interfaces other than mvpnMrouteInIfIndex, and - were dropped because of this failed RPF check. (RPF paths - are 'Reverse Path Forwarding' path; the unicast routes to - the expected origin of multicast data flows). - - Other protocols may drop packets on an incoming interface - check for different reasons (for example, BIDIR-PIM performs - a DF check on receipt of packets). All packets dropped as a - result of an incoming interface check are counted here. - - If this counter increases rapidly, this indicates a problem. - A significant quantity of multicast data is arriving at this - router on unexpected interfaces, and is not being forwarded. - - For guidance, if the rate of increase of this counter - exceeds 1% of the rate of increase of mvpnMroutePkts, then - there are multicast routing problems that require - investigation. + "The number of octets contained in IP datagrams that this + router has received from sources represented by + this entry and addressed to this multicast group address, + which were dropped due to error(s). + The value of this object includes the octets counted + in the corresponding mvpnMrouteTtlDroppedOctets object. - Discontinuities in this monotonically increasing value - occur at re-initialization of the management system. - Discontinuities can also occur as a result of routes being - removed and replaced, which can be detected by observing - the value of mvpnMrouteTimeStamp. - " - REFERENCE - "RFC 4601 - RFC 5015 + Discontinuities in the value of this counter can + occur at re-initialization of the management system, + and at other times as indicated by the corresponding + mvpnMrouteCounterDiscontinuityTime object. " - ::= { mvpnMrouteEntry 23 } + ::= { mvpnMrouteEntry 21 } - mvpnMrouteBps OBJECT-TYPE - SYNTAX CounterBasedGauge64 - UNITS "bits per second" + mvpnMrouteDroppedInPackets OBJECT-TYPE + SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION - "Bits per second forwarded by this router using this - multicast routing entry. - - This value is a sample; it is the number of bits forwarded - during the last whole 1 second sampling period. The value - during the current 1 second sampling period is not made - available until the period is completed. + "The number of packets which this router has received from + sources represented by this entry and addressed to this + multicast group address, which were dropped due to error(s). + The value of this object includes the number of octets + counted in the corresponding mvpnMrouteTtlDroppedPackets + object. - The quantity being sampled is the same as that measured by - mvpnMrouteOctets. The units and the sampling method are - different. + Discontinuities in the value of this counter can + occur at re-initialization of the management system, + and at other times as indicated by the corresponding + mvpnMrouteCounterDiscontinuityTime object. " - ::= { mvpnMrouteEntry 24 } + ::= { mvpnMrouteEntry 22 } mvpnMroutePmsiPointer OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION - "The I-PMSI or S-PMSI this C-multicast route is using. - This is important because an implementation may not have an - interface corresponding to a provider tunnel, - that can be used in mvpnMrouteNextHopEntry. + "A pointer to a conceptual row representing + the corresponding I-PMSI in mvpnPmsiTable or S-PMSI + in mvpnSpmsiTable, that this C-multicast route is using. " - ::= { mvpnMrouteEntry 25 } + ::= { mvpnMrouteEntry 23 } mvpnMrouteNumberOfLocalReplication OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of replications for local receivers. For example, if an ingress PE needs to send traffic out of N PE-CE interfaces, then mvpnMrouteNumberOfLocalReplication is N. " - ::= { mvpnMrouteEntry 26 } + ::= { mvpnMrouteEntry 24 } mvpnMrouteNumberOfRemoteReplication OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of local replications for remote PEs. For example, if the number of remote PEs that need to receive traffic is N, then mvpnMrouteNumberOfRemoteReplication is N in case of Ingress Replication, but may be less than N in case of RSVP-TE or mLDP P2MP tunnels, depending on the actual number of - replications the PE needs do. + replications the PE needs to do. " + ::= { mvpnMrouteEntry 25 } - ::= { mvpnMrouteEntry 27 } + mvpnMrouteCounterDiscontinuityTime OBJECT-TYPE + SYNTAX TimeStamp + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The value of sysUpTime on the most recent occasion + at which any one or more of this application's + counters, viz., counters with OID prefix + 'mvpnMrouteOctets' or 'mvpnMroutePkts' or + 'mvpnMrouteTtlDroppedOctets' or + 'mvpnMrouteTtlDroppedPackets' or + 'mvpnMrouteDroppedInOctets' or 'mvpnMrouteDroppedInPackets' + suffered a discontinuity. + If no such discontinuities have occurred since the + last re-initialization of the local management + subsystem, then this object will have a zero value. + " + ::= { mvpnMrouteEntry 26 } + + -- Table of next hops for multicast routes in an MVPN mvpnMrouteNextHopTable OBJECT-TYPE SYNTAX SEQUENCE OF MvpnMrouteNextHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The (conceptual) table containing information on the - next-hops on outgoing interfaces for routing IP multicast - datagrams. Each entry is one of a list of next-hops on - outgoing interfaces for particular sources sending to a - particular multicast group address." - ::= { mvpnStates 5 } + "A conceptual table containing information on the + next-hops for routing IP multicast datagrams. + Each entry is one of a list of next-hops for + a set of sources sending to a multicast group + address. + " + ::= { mvpnObjects 8 } mvpnMrouteNextHopEntry OBJECT-TYPE SYNTAX MvpnMrouteNextHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "An entry (conceptual row) in the list of next-hops on - outgoing interfaces to which IP multicast datagrams from - particular sources to an IP multicast group address are - routed. + "A conceptual row corresponding to a next-hop to which + IP multicast datagrams from a set of sources to + an IP multicast group address are routed. - OIDs are limited to 128 sub-identifiers, but this limit - is not enforced by the syntax of this entry. In practice, - this does not present a problem, because IP address types - allowed by conformance statements do not exceed this limit. + Implementers need to be aware that if the total number of + octets in mplsL3VpnVrfName, mvpnMrouteNextHopGroupAddr, + mvpnMrouteNextHopSourceAddrs, and mvpnMrouteNextHopAddr + exceeds 111, the OIDs of column instances in this row + will have more than 128 sub-identifiers and cannot be + accessed using SNMPv1, SNMPv2c, or SNMPv3. " INDEX { mplsL3VpnVrfName, mvpnMrouteNextHopGroupAddrType, mvpnMrouteNextHopGroupAddr, mvpnMrouteNextHopGroupPrefixLength, mvpnMrouteNextHopSourceAddrType, - mvpnMrouteNextHopSourceAddr, + mvpnMrouteNextHopSourceAddrs, mvpnMrouteNextHopSourcePrefixLength, mvpnMrouteNextHopIfIndex, mvpnMrouteNextHopAddrType, mvpnMrouteNextHopAddr } ::= { mvpnMrouteNextHopTable 1 } MvpnMrouteNextHopEntry ::= SEQUENCE { mvpnMrouteNextHopGroupAddrType InetAddressType, mvpnMrouteNextHopGroupAddr InetAddress, mvpnMrouteNextHopGroupPrefixLength InetAddressPrefixLength, mvpnMrouteNextHopSourceAddrType InetAddressType, - mvpnMrouteNextHopSourceAddr InetAddress, + mvpnMrouteNextHopSourceAddrs InetAddress, mvpnMrouteNextHopSourcePrefixLength InetAddressPrefixLength, mvpnMrouteNextHopIfIndex InterfaceIndex, mvpnMrouteNextHopAddrType InetAddressType, mvpnMrouteNextHopAddr InetAddress, mvpnMrouteNextHopState INTEGER, - mvpnMrouteNextHopTimeStamp TimeStamp, mvpnMrouteNextHopExpiryTime TimeTicks, mvpnMrouteNextHopClosestMemberHops Unsigned32, mvpnMrouteNextHopProtocol IANAipMRouteProtocol, mvpnMrouteNextHopOctets Counter64, - mvpnMrouteNextHopPkts Counter64 + mvpnMrouteNextHopPkts Counter64, + mvpnMrouteNextHopCounterDiscontinuityTime TimeStamp } - mvpnMrouteNextHopGroupAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A value indicating the address family of the address - contained in mvpnMrouteNextHopGroupAddr. Legal values - correspond to the subset of address families for which - multicast forwarding is supported. + "The InetAddressType of the mvpnMrouteNextHopGroupAddr object + that follows. " ::= { mvpnMrouteNextHopEntry 1 } mvpnMrouteNextHopGroupAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The IP multicast group address which, when combined with - the corresponding value specified in - mvpnMrouteNextHopGroupPrefixLength, identifies the groups - for which this entry contains multicast forwarding - information. + "The IP multicast group address which, along with + the corresponding mvpnMrouteNextHopGroupPrefixLength object, + identifies destinations for which this entry contains + multicast forwarding information. This address object is only significant up to mvpnMrouteNextHopGroupPrefixLength bits. The remaining - address bits are set to zero. This is especially important - for this index field, which is part of the index of this - entry. Any non-zero bits would signify an entirely - different entry. + 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 length. The use of these address types indicate that this forwarding state applies only within the given zone. Zone index zero is not valid in this table. " ::= { mvpnMrouteNextHopEntry 2 } mvpnMrouteNextHopGroupPrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The length in bits of the mask which, when combined with - the corresponding value of mvpnMrouteGroup, identifies the - groups for which this entry contains multicast routing - information. + "The length in bits of the mask which, along with + the corresponding mvpnMrouteGroupAddr object, + identifies destinations for which this entry contains + multicast routing information. - The InetAddressType is given by - mvpnMrouteNextHopGroupAddressType. For values 'ipv4' and - 'ipv4z', this object must be in the range 4..32. For values - 'ipv6' and 'ipv6z', this object must be in the range - 8..128. + If the corresponding InetAddressType is 'ipv4' or 'ipv4z', + this object must be in the range 4..32. + If the corresponding InetAddressType is 'ipv6' or 'ipv6z', + this object must be in the range 8..128. " ::= { mvpnMrouteNextHopEntry 3 } mvpnMrouteNextHopSourceAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A value indicating the address family of the address - contained in mvpnMrouteNextHopSourceAddr. + "The InetAddressType of mvpnMrouteNextHopSourceAddrs object + that follows. A value of unknown(0) indicates a non-source-specific entry, corresponding to all sources in the group. Otherwise, the value MUST be the same as the value of mvpnMrouteNextHopGroupAddrType." ::= { mvpnMrouteNextHopEntry 4 } - mvpnMrouteNextHopSourceAddr OBJECT-TYPE + mvpnMrouteNextHopSourceAddrs OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The network address which, when combined with the - corresponding value of the mask specified in - mvpnMrouteNextHopSourcePrefixLength, identifies the - sources for which this entry specifies a next-hop on an - outgoing interface. + "The network address which, along with the + corresponding mvpnMrouteNextHopSourcePrefixLength object, + identifies the sources for which this entry specifies + a next-hop. This address object is only significant up to mvpnMrouteNextHopSourcePrefixLength bits. The remaining - address bits are set to zero. This is especially important - for this index field, which is part of the index of this - entry. Any non-zero bits would signify an entirely - different entry. + 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 length. The use of these address types indicate that this source address applies only within the given zone. Zone index zero is not valid in this table. " ::= { mvpnMrouteNextHopEntry 5 } mvpnMrouteNextHopSourcePrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The length in bits of the mask which, when combined with - the corresponding value specified in - mvpnMrouteNextHopSource, identifies the sources for which - this entry specifies a next-hop on an outgoing interface. - The InetAddressType is given by - mvpnMrouteNextHopSourceAddressType. For the value - 'unknown', this object must be zero. For values 'ipv4' and - 'ipv4z', this object must be in the range 4..32. For values - 'ipv6' and 'ipv6z', this object must be in the range - 8..128. + "The length in bits of the mask which, along with + the corresponding mvpnMrouteNextHopSourceAddrs object, + identifies the sources for which this entry specifies + a next-hop. + + If the corresponding InetAddressType is 'ipv4' or 'ipv4z', + this object must be in the range 4..32. + + If the corresponding InetAddressType is 'ipv6' or 'ipv6z', + this object must be in the range 8..128. + If the corresponding InetAddressType is 'unknown', + this object must be zero. " ::= { mvpnMrouteNextHopEntry 6 } mvpnMrouteNextHopIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The ifIndex value of the interface for the outgoing - interface for this next-hop. + "The ifIndex value of the outgoing interface + for this next-hop. " ::= { mvpnMrouteNextHopEntry 7 } mvpnMrouteNextHopAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A value indicating the address family of the address - contained in mvpnMrouteNextHopAddr. + "The InetAddressType of the mvpnMrouteNextHopAddr object + that follows. " ::= { mvpnMrouteNextHopEntry 8 } mvpnMrouteNextHopAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The address of the next-hop specific to this entry. For most interfaces, this is identical to - mvpnMrouteNextHopGroup. Non-Broadcast Multi-Access - (NBMA) interfaces, however, may - have multiple next-hop addresses out a single outgoing - interface. + mvpnMrouteNextHopGroupAddr. Non-Broadcast Multi-Access + (NBMA) interfaces, however, may have multiple next-hop + addresses out of a single outgoing interface. " ::= { mvpnMrouteNextHopEntry 9 } mvpnMrouteNextHopState OBJECT-TYPE - SYNTAX INTEGER { pruned(1), forwarding(2) } + SYNTAX INTEGER { + pruned(1), + forwarding(2) + } MAX-ACCESS read-only STATUS current DESCRIPTION "An indication of whether the outgoing interface and next- hop represented by this entry is currently being used to - forward IP datagrams. The value 'forwarding' indicates it - is currently being used; the value 'pruned' indicates it is - not. - " - ::= { mvpnMrouteNextHopEntry 10 } + forward IP datagrams. - mvpnMrouteNextHopTimeStamp OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at which the multicast routing - information represented by this entry was learned by the - router. + The enumerated states and the corresponding + descriptions are as follows: - If this information was present at the most recent re- - initialization of the local management subsystem, then this - object contains a zero value. + pruned : this entry is not currently being used. + forwarding : this entry is currently being used. " - ::= { mvpnMrouteNextHopEntry 11 } + ::= { mvpnMrouteNextHopEntry 10 } mvpnMrouteNextHopExpiryTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The minimum amount of time remaining before this entry will - be aged out. If mvpnMrouteNextHopState is pruned(1), the - remaining time until the prune expires and the state reverts - to forwarding(2). Otherwise, the remaining time until this - entry is removed from the table. The time remaining may be - copied from mvpnMrouteExpiryTime if the protocol in use - for this entry does not specify next-hop timers. The value - 0 indicates that the entry is not subject to aging. + be aged out. If mvpnMrouteNextHopState is pruned(1), + this object represents the remaining time for the prune + to expire after which the state will return to forwarding(2). + If mvpnMrouteNextHopState is forwarding(2), + this object indicates the time after which this + entry will be removed from the table. + + The value of 0 indicates that the entry is not subject to + aging. " - ::= { mvpnMrouteNextHopEntry 12 } + ::= { mvpnMrouteNextHopEntry 11 } mvpnMrouteNextHopClosestMemberHops OBJECT-TYPE SYNTAX Unsigned32 (0..256) MAX-ACCESS read-only STATUS current DESCRIPTION "The minimum number of hops between this router and any member of this IP multicast group reached via this next-hop - on this outgoing interface. Any IP multicast datagrams for - the group that have a TTL (IPv4) or Hop Count (IPv6) less - than this number of hops will not be forwarded to this - next-hop. + on the corresponding outgoing interface. Any IP multicast + datagram for the group that has a TTL (IPv4) or Hop Count + (IPv6) less than mvpnMrouteNextHopClosestMemberHops will + not be forwarded through this interface. A value of 0 means all multicast datagrams are forwarded out - the interface. A value of 256 means that no multicast - datagrams are forwarded out the interface. + of the interface. A value of 256 means that no multicast + datagrams are forwarded out of the interface. This is an optimization applied by multicast routing protocols that explicitly track hop counts to downstream listeners. Multicast protocols that are not aware of hop counts to downstream listeners set this object to 0. " - ::= { mvpnMrouteNextHopEntry 13 } + ::= { mvpnMrouteNextHopEntry 12 } mvpnMrouteNextHopProtocol OBJECT-TYPE SYNTAX IANAipMRouteProtocol MAX-ACCESS read-only STATUS current DESCRIPTION - "The routing mechanism via which this next-hop was learned." - ::= { mvpnMrouteNextHopEntry 14 } + "The routing protocol via which this next-hop was learned." + ::= { mvpnMrouteNextHopEntry 13 } mvpnMrouteNextHopOctets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets of multicast packets that have been forwarded using this route. - Discontinuities in this monotonically increasing value - occur at re-initialization of the management system. - Discontinuities can also occur as a result of routes being - removed and replaced, which can be detected by observing - the value of mvpnMrouteNextHopTimeStamp." - ::= { mvpnMrouteNextHopEntry 15 } + Discontinuities in the value of this counter can + occur at re-initialization of the management system, + and at other times as indicated by the corresponding + mvpnMrouteNextHopCounterDiscontinuityTime object. + " + ::= { mvpnMrouteNextHopEntry 14 } mvpnMrouteNextHopPkts OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of packets which have been forwarded using this route. - Discontinuities in this monotonically increasing value - occur at re-initialization of the management system. - Discontinuities can also occur as a result of routes being - removed and replaced, which can be detected by observing - the value of ipMcastRouteNextHopTimeStamp." - ::= { mvpnMrouteNextHopEntry 16 } - - -- MVPN Notifications - - mvpnMvrfOperationChange NOTIFICATION-TYPE - OBJECTS { - mvpnGenMvrfLastOperation - } - STATUS current - DESCRIPTION - "A mvpnMvrfOperationChange notification signifies a change about - a MVRF in the PE. The change event can be creation of - the MVRF, deletion of the MVRF or an update on the I-PMSI - or S-PMSI information of the MVRF. The change event - is indicated by mvpnGenMvrfLastOperation embedded in - the notification. The user can then query - mvpnGenericTable, mvpnPmsiTable, and/or mvpnSpmsiTable to - get the details of the change as necessary. - - Note: Since the creation of a MVRF is often followed by - configuration of I-PMSI and/or S-PMSIs for the MVRF, - more than one (three at most) notifications for a MVRF may - be generated serially, and it is really not necessary to - generate all three of them. An agent may choose to generate a - notification for the last event only, that is for S-PMSI - configuration. - - Similarly, deletion of I-PMSI and S-PMSI configuration on a - MVRF happens before a MVRF is deleted and it is recommended - that the agent send the notification for MVRF deletion - event only. + Discontinuities in the value of this counter can + occur at re-initialization of the management system, + and at other times as indicated by the corresponding + mvpnMrouteNextHopCounterDiscontinuityTime object. " - ::= { mvpnNotifications 1 } + ::= { mvpnMrouteNextHopEntry 15 } - mvpnMvrfGroupJoined NOTIFICATION-TYPE - OBJECTS { - mvpnMrouteTimeStamp - } + mvpnMrouteNextHopCounterDiscontinuityTime OBJECT-TYPE + SYNTAX TimeStamp + MAX-ACCESS read-only STATUS current DESCRIPTION - "A mvpnMvrfGroupJoined notification signifies that - this PE has joined to a new multicast group - serviced in a particular MVPN. - The change event is indicated by mvpnMrouteTimeStamp - embedded in the notification. + "The value of sysUpTime on the most recent occasion + at which any one or more of this application's + counters, viz., counters with OID prefix + 'mvpnMrouteNextHopOctets' or 'mvpnMrouteNextHopPackets' + suffered a discontinuity. + If no such discontinuities have occurred since the + last re-initialization of the local management + subsystem, then this object will have a zero value. " - ::= { mvpnNotifications 2 } + ::= { mvpnMrouteNextHopEntry 16 } - mvpnMvrfGroupLeft NOTIFICATION-TYPE + -- MVPN Notifications + + mvpnMvrfActionTaken NOTIFICATION-TYPE OBJECTS { - mvpnMrouteTimeStamp + mvpnGenMvrfCreationTime, + mvpnGenMvrfLastAction, + mvpnGenMvrfLastActionTime, + mvpnGenMvrfCreationTime, + mvpnGenCmcastRouteProtocol, + mvpnGenUmhSelection, + mvpnGenCustomerSiteType } STATUS current DESCRIPTION - "A mvpnMvrfGroupJoined notification signifies that - this PE has left from a multicast group - serviced in a particular MVPN. - The change event is indicated by mvpnMrouteTimeStamp - embedded in the notification. + "mvpnMvrfActionTaken notifies about a change + in a MVRF on the PE. The change itself will be given by + mvpnGenMvrfLastAction. " - ::= { mvpnNotifications 3 } + ::= { mvpnNotifications 1 } -- MVPN MIB Conformance Information mvpnGroups OBJECT IDENTIFIER ::= { mvpnConformance 1 } mvpnCompliances OBJECT IDENTIFIER ::= { mvpnConformance 2 } -- Compliance Statements mvpnModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that provide full support for the MCAST-VPN-MIB " MODULE -- this module MANDATORY-GROUPS { mvpnScalarGroup, mvpnGenericGroup, mvpnPmsiGroup, - mvpnSpmsiGroup, - mvpnSpmsiAdvtGroup, + mvpnAdvtStatsGroup, mvpnMrouteGroup, mvpnMrouteNextHopGroup, mvpnNotificationGroup } - GROUP mvpnIpmsiGroup - DESCRIPTION - "This group is mandatory for systems that support - BGP signaling for I-PMSI. - " - - GROUP mvpnInterAsIpmsiGroup - DESCRIPTION - "This group is mandatory for systems that support - Inter-AS Segmented I-PMSI. - " - - GROUP mvpnBgpGenericGroup + GROUP mvpnBgpGroup DESCRIPTION "This group is mandatory for systems that support BGP-MVPN. " - GROUP mvpnOptionalGroup - DESCRIPTION - "This group is optional. - " - ::= { mvpnCompliances 1 } mvpnModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that only provide read-only support for MCAST-VPN-MIB. Such devices can then be monitored but cannot be configured using this MIB module. - " MODULE -- this module MANDATORY-GROUPS { mvpnScalarGroup, mvpnGenericGroup, mvpnPmsiGroup, - mvpnSpmsiGroup, - mvpnSpmsiAdvtGroup, + mvpnAdvtStatsGroup, mvpnMrouteGroup, mvpnMrouteNextHopGroup, mvpnNotificationGroup } - GROUP mvpnIpmsiGroup - DESCRIPTION - "This group is mandatory for systems that support - BGP signaling for I-PMSI. - " - - GROUP mvpnInterAsIpmsiGroup - DESCRIPTION - "This group is mandatory for systems that support - Inter-AS Segmented I-PMSI. - " - - GROUP mvpnBgpGenericGroup + GROUP mvpnBgpGroup DESCRIPTION "This group is mandatory for systems that support BGP-MVPN. " - GROUP mvpnOptionalGroup - DESCRIPTION - "This group is optional. - " - - OBJECT mvpnGenCmcastRouteProtocol + OBJECT mvpnSPTunnelLimit MIN-ACCESS read-only DESCRIPTION "Write access is not required." - OBJECT mvpnGenIpmsiInfo + OBJECT mvpnBgpCmcastRouteWithdrawalTimer MIN-ACCESS read-only DESCRIPTION "Write access is not required." - OBJECT mvpnGenInterAsPmsiInfo - MIN-ACCESS read-only - DESCRIPTION "Write access is not required." - OBJECT mvpnGenUmhSelection + OBJECT mvpnBgpSrcSharedTreeJoinTimer MIN-ACCESS read-only DESCRIPTION "Write access is not required." - OBJECT mvpnGenCustomerSiteType + OBJECT mvpnBgpMsgRateLimit MIN-ACCESS read-only DESCRIPTION "Write access is not required." - OBJECT mvpnGenSPTunnelLimit + OBJECT mvpnBgpMaxSpmsiAdRoutes MIN-ACCESS read-only DESCRIPTION "Write access is not required." - OBJECT mvpnPmsiEncapsulationType + OBJECT mvpnBgpMaxSpmsiAdRouteFreq MIN-ACCESS read-only DESCRIPTION "Write access is not required." - OBJECT mvpnSpmsiThreshold + OBJECT mvpnBgpMaxSrcActiveAdRoutes MIN-ACCESS read-only DESCRIPTION "Write access is not required." - OBJECT mvpnSpmsiPmsiPointer + OBJECT mvpnBgpMaxSrcActiveAdRouteFreq MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { mvpnCompliances 2 } + mvpnModuleAdvtStatsCompliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "Compliance statement for agents that support + monitoring of the statistics pertaining to + advertisements sent/received by a PE. + " + MODULE -- this module + MANDATORY-GROUPS { + mvpnAdvtStatsGroup + } + + ::= { mvpnCompliances 3 } + -- units of conformance mvpnScalarGroup OBJECT-GROUP OBJECTS { mvpnMvrfs, mvpnV4Mvrfs, mvpnV6Mvrfs, + mvpnMldpMvrfs, mvpnPimV4Mvrfs, mvpnPimV6Mvrfs, mvpnBgpV4Mvrfs, mvpnBgpV6Mvrfs, - mvpnMldpMvrfs + mvpnSPTunnelLimit } STATUS current DESCRIPTION "These objects are used to monitor/manage global MVPN parameters. " ::= { mvpnGroups 1 } mvpnGenericGroup OBJECT-GROUP OBJECTS { - mvpnGenMvrfLastOperation, - mvpnGenMvrfLastOperationTime, + mvpnGenMvrfLastAction, + mvpnGenMvrfLastActionTime, + mvpnGenMvrfCreationTime, mvpnGenCmcastRouteProtocol, mvpnGenIpmsiInfo, mvpnGenInterAsPmsiInfo, mvpnGenUmhSelection, - mvpnGenCustomerSiteType, - mvpnGenSPTunnelLimit + mvpnGenCustomerSiteType } STATUS current DESCRIPTION - "These objects are used to monitor/manage - per-VRF MVPN parameters. + "These objects are used to monitor MVPNs on a PE. " ::= { mvpnGroups 2 } - mvpnPmsiGroup OBJECT-GROUP + mvpnBgpGroup OBJECT-GROUP OBJECTS { - mvpnPmsiEncapsulationType + mvpnBgpMode, + mvpnBgpVrfRouteImportExtendedCommunity, + mvpnBgpSrcASExtendedCommunity, + mvpnBgpCmcastRouteWithdrawalTimer, + mvpnBgpSrcSharedTreeJoinTimer, + mvpnBgpMsgRateLimit, + mvpnBgpMaxSpmsiAdRoutes, + mvpnBgpMaxSpmsiAdRouteFreq, + mvpnBgpMaxSrcActiveAdRoutes, + mvpnBgpMaxSrcActiveAdRouteFreq } STATUS current DESCRIPTION - "These objects are used to monitor/manage - PMSI tunnel configurations. + "These objects are used to monitor BGP-MVPNs on + a PE and to monitor timers and thresholds related + to the BPG-MVPNs. " + ::= { mvpnGroups 3 } - mvpnSpmsiGroup OBJECT-GROUP + mvpnPmsiGroup OBJECT-GROUP OBJECTS { - mvpnSpmsiThreshold, + mvpnPmsiRD, + mvpnPmsiTunnelType, + mvpnPmsiTunnelAttribute, + mvpnPmsiTunnelPimGroupAddrType, + mvpnPmsiTunnelPimGroupAddr, + mvpnPmsiEncapsulationType, mvpnSpmsiPmsiPointer } STATUS current DESCRIPTION - "These objects are used to monitor/manage - S-PMSI configurations. + "These objects are used to monitor + I-PMSIs and S-PMSIs tunnel on a PE. " ::= { mvpnGroups 4 } - mvpnIpmsiGroup OBJECT-GROUP + mvpnAdvtStatsGroup OBJECT-GROUP OBJECTS { - mvpnIpmsiAdvtTunnelAttribute, - mvpnIpmsiAdvtReceived, - mvpnIpmsiAdvtReceivedError, - mvpnIpmsiAdvtMalformedTunnelType, - mvpnIpmsiAdvtMalformedTunnelId, - mvpnIpmsiAdvtLastReceivedTime, - mvpnIpmsiAdvtCounterDiscontinuityTime - + mvpnAdvtSent, + mvpnAdvtReceived, + mvpnAdvtReceivedError, + mvpnAdvtReceivedMalformedTunnelType, + mvpnAdvtReceivedMalformedTunnelId, + mvpnAdvtLastSentTime, + mvpnAdvtLastReceivedTime, + mvpnAdvtCounterDiscontinuityTime } STATUS current DESCRIPTION - "These objects are used to monitor/manage - Intra-AS I-PMSI attributes. + "These objects are used to monitor + the statistics pertaining to I-PMSI and S-PMSI + advertisements sent/received by a PE. " ::= { mvpnGroups 5 } - mvpnInterAsIpmsiGroup OBJECT-GROUP - OBJECTS { - mvpnInterAsIpmsiAdvtTunnelAttribute, - mvpnInterAsIpmsiAdvtReceived, - mvpnInterAsIpmsiAdvtReceivedError, - mvpnInterAsIpmsiAdvtMalformedTunnelType, - mvpnInterAsIpmsiAdvtMalformedTunnelId, - mvpnInterAsIpmsiAdvtLastReceivedTime, - mvpnInterAsIpmsiAdvtCounterDiscontinuityTime - } - STATUS current - DESCRIPTION - "These objects are used to monitor/manage - Inter-AS I-PMSI attributes. - " - ::= { mvpnGroups 6 } - - mvpnSpmsiAdvtGroup OBJECT-GROUP - OBJECTS { - mvpnSpmsiAdvtTunnelAttribute, - mvpnSpmsiAdvtExpTime, - mvpnSpmsiAdvtRefCnt, - mvpnSpmsiAdvtReceived, - mvpnSpmsiAdvtReceivedError, - mvpnSpmsiAdvtMalformedTunnelType, - mvpnSpmsiAdvtMalformedTunnelId, - mvpnSpmsiAdvtLastReceivedTime, - mvpnSpmsiAdvtCounterDiscontinuityTime - } - STATUS current - DESCRIPTION - "These objects are used to monitor/manage - S-PMSI attributes. - " - ::= { mvpnGroups 7 } - mvpnMrouteGroup OBJECT-GROUP OBJECTS { mvpnMrouteUpstreamNeighborAddrType, mvpnMrouteUpstreamNeighborAddr, mvpnMrouteInIfIndex, - mvpnMrouteTimeStamp, mvpnMrouteExpiryTime, mvpnMrouteProtocol, mvpnMrouteRtProtocol, mvpnMrouteRtAddrType, mvpnMrouteRtAddr, mvpnMrouteRtPrefixLength, mvpnMrouteRtType, mvpnMrouteOctets, mvpnMroutePkts, - mvpnMrouteTtlDropOctets, - mvpnMrouteTtlDropPackets, - mvpnMrouteDifferentInIfOctets, - mvpnMrouteDifferentInIfPackets, - mvpnMrouteBps, + mvpnMrouteTtlDroppedOctets, + mvpnMrouteTtlDroppedPackets, + mvpnMrouteDroppedInOctets, + mvpnMrouteDroppedInPackets, mvpnMroutePmsiPointer, mvpnMrouteNumberOfLocalReplication, - mvpnMrouteNumberOfRemoteReplication + mvpnMrouteNumberOfRemoteReplication, + mvpnMrouteCounterDiscontinuityTime } STATUS current DESCRIPTION - "These objects are used to monitor/manage - VPN multicast forwarding states. + "These objects are used to monitor multicast routing + information corresponding to the MVRFs on a PE. " - ::= { mvpnGroups 8 } + ::= { mvpnGroups 6 } mvpnMrouteNextHopGroup OBJECT-GROUP OBJECTS { mvpnMrouteNextHopState, - mvpnMrouteNextHopTimeStamp, mvpnMrouteNextHopExpiryTime, mvpnMrouteNextHopClosestMemberHops, mvpnMrouteNextHopProtocol, mvpnMrouteNextHopOctets, - mvpnMrouteNextHopPkts + mvpnMrouteNextHopPkts, + mvpnMrouteNextHopCounterDiscontinuityTime } STATUS current DESCRIPTION - "These objects are used to monitor/manage - next hop information of VPN multicast. + "These objects are used to monitor the information on + next-hops for routing datagrams to MVPNs on a PE. " - ::= { mvpnGroups 9 } - - mvpnBgpGenericGroup OBJECT-GROUP - OBJECTS { - mvpnBgpGenMode, - mvpnBgpGenVrfRouteImport, - mvpnBgpGenSrcAs, - mvpnBgpGenCmcastRouteWithdrawalTimer, - mvpnBgpGenSrcSharedTreeJoinTimer, - mvpnBgpGenMsgRateLimit, - mvpnBgpGenMaxSpmsiAdRoutes, - mvpnBgpGenMaxSpmsiAdRouteFreq, - mvpnBgpGenMaxSrcActiveAdRoutes, - mvpnBgpGenMaxSrcActiveAdRouteFreq - } - STATUS current - DESCRIPTION - "These objects are used to monitor/manage BGP-MVPN." - ::= { mvpnGroups 10 } - - mvpnOptionalGroup OBJECT-GROUP - OBJECTS { - mvpnMroutePmsiPointer - } - STATUS current - DESCRIPTION - "Support of these object is not required." - ::= { mvpnGroups 11 } + ::= { mvpnGroups 7 } mvpnNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { - mvpnMvrfOperationChange, - mvpnMvrfGroupJoined, - mvpnMvrfGroupLeft + mvpnMvrfActionTaken } STATUS current DESCRIPTION "Objects required for MVPN notifications." - ::= { mvpnGroups 12 } + ::= { mvpnGroups 8 } END 4. Security Considerations - This MIB contains some read-only objects that may be deemed senstive - by some though perhaps not all operators. It also contains some - read- write objects, whose setting will change the device's behavior - related to MVPN. Appropriate security procedures related to SNMP in - general but not specific to this MIB need to be implemented by - concerned operators. + This MIB module contains some read-only objects that may be deemed + senstive. It also contains some read-write objects, whose setting + will change the device's MVPN related behavior. Appropriate security + procedures related to SNMP in general but not specific to this MIB + module need to be implemented by concerned operators. There are a number of management objects defined in this MIB module - with a MAX-ACCESS clause of read-write and/or read-create. Such - objects may be considered sensitive or vulnerable in some network - environments. The support for SET operations in a non-secure - environment without proper protection opens devices to attack. These - are the tables and objects and their sensitivity/vulnerability: + with a MAX-ACCESS clause of read-write. Such objects may be + considered sensitive or vulnerable in some network environments. The + support for SET operations in a non-secure environment without proper + protection opens devices to attack. These are the tables and objects + and their sensitivity/vulnerability: - o mvpnGenCmcastRouteProtocol, mvpnGenIpmsiInfo, - mvpnGenInterAsPmsiInfo, mvpnGenUmhSelection, - mvpnGenCustomerSiteType, mvpnGenSPTunnelLimit, mvpnBgpGenMode, - mvpnBgpGenVrfRtImport, mvpnPmsiEncapsulationType, - mvpnSpmsiThreshold, mvpnSpmsiPmsiPointer + o mvpnSPTunnelLimit + + The value of this object is used to control the maximum number of + selective provider tunnels that a PE allows for a particular MVPN. + Access to this object may be abused to impact the peformance of + the PE or prevent the PE from having new selective provider + tunnels. + + o mvpnBgpCmcastRouteWithdrawalTimer + + The value of this object is used to control the delay for the + advertisement of withdrawals of C-multicast routes. Access to + this object may be abused to impact the peformance of a PE. + + o mvpnBgpSrcSharedTreeJoinTimer + + The value of this object is used to control the delay for the + advertisement of Source/Shared Tree Join C-multicast routes. + Access to this object may be abused to impact the propagation of + C-multicast routing information. + + o mvpnBgpMsgRateLimit + + The value of this object is used to control the upper bound for + the rate of BGP C-multicast routing information message exchange + among PEs. Access to this object may be abused to impact the + peformance of the PE or disrupt the C-multicast routing + information message exchange using BGP. + + o mvpnBgpMaxSpmsiAdRoutes + + The value of this object is used to control the upper bound for + the number of S-PMSI A-D routes. Access to this object may be + abused to impact the peformance of the PE or prevent the PE from + receiving S-PMSI A-D routes. + + o mvpnBgpMaxSpmsiAdRouteFreq + + The value of this object is used to control the upper bound for + the frequency of S-PMSI A-D route generation. Access to this + object may be abused to impact the peformance of the PE or prevent + the PE from generating new S-PMSI A-D routes. + + o mvpnBgpMaxSrcActiveAdRoutes + + The value of this object is used to control the upper bound for + the number of Source Active A-D routes. Access to this object may + be abused to impact the peformance of the PE or prevent the PE + from receiving Source Active A-D routes. + + o mvpnBgpMaxSrcActiveAdRouteFreq + + The value of this object is used to control the upper bound for + the frequency of Source Active A-D route generation. Access to + this object may be abused to impact the peformance of the PE or + prevent the PE from generating new Source Active A-D routes. Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability: - o [TBD] + o The address-related objects in this MIB module may have impact on + privacy and security. These objects may reveal the locations of + senders and recipients. + + * mvpnPmsiTunnelPimGroupAddr + + * mvpnSpmsiCmcastGroupAddr + + * mvpnSpmsiCmcastSourceAddr + + * mvpnAdvtPeerAddr + + * mvpnMrouteCmcastGroupAddr + + * mvpnMrouteCmcastSourceAddrs + * mvpnMrouteUpstreamNeighborAddr + + * mvpnMrouteNextHopGroupAddr + + * mvpnMrouteNextHopSourceAddrs + + * mvpnMrouteNextHopAddr SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. Implementations SHOULD provide the security features described by the SNMPv3 framework (see [RFC3410]), and implementations claiming compliance to the SNMPv3 standard MUST include full support for @@ -3011,28 +2476,49 @@ Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 5. IANA Considerations + The MIB module in this document uses the following IANA-assigned + OBJECT IDENTIFIER values recorded in the SMI Numbers registry: + + Descriptor OBJECT IDENTIFIER value + ---------- ----------------------- + mvpnMIB { mib-2 YYYY } + + Editor's Note (to be removed prior to publication): the IANA is + requested to assign a value for "YYYY" 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 "YYYY" + (here and in the MIB module) with the assigned value and to remove + this note. + IANA is requested to root MIB objects in the MIB module contained in this document under the mib-2 subtree. 6. Acknowledgement - This document borrowed some text from Cisco PIM-MVPN MIB - [I-D.svaidya-mcast-vpn-mib]. We would like to thank Yakov Rekhter, - Jeffrey Haas, Huajin Jeng, Durga Prasad Velamuri for their helpful + 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 borrowed 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 7.1. Normative References [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, DOI 10.17487/RFC2003, October 1996, . @@ -3076,30 +2562,38 @@ Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ RFC3414, December 2002, . [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model", RFC 3826, DOI 10.17487/ RFC3826, June 2004, . + [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private + Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February + 2006, . + [RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base", RFC 4382, DOI 10.17487/RFC4382, February 2006, . [RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur, "BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN", RFC 4659, DOI 10.17487/RFC4659, September 2006, . + [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast + MIB", RFC 5132, DOI 10.17487/RFC5132, December 2007, + . + [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, . [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 2009, . @@ -3126,67 +2620,25 @@ Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March 2016, . [RTPROTO] IANA, "IP Route Protocol MIB", 2016, . 7.2. Informative References - [I-D.svaidya-mcast-vpn-mib] - Vaidya, S., "Multicast in BGP/MPLS IP VPNs Management - Information Base", draft-svaidya-mcast-vpn-mib-02 (work in - progress), March 2005. - [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, DOI 10.17487/ RFC3410, December 2002, . -Authors' Addresses - - Zhaohui (Jeffrey) Zhang (editor) - Juniper Networks, Inc. - 10 Technology Park Drive - Westford, MA 01886 - USA - - Email: zzhang@juniper.net - Saud Asif - AT&T - C5-3D30 200 South Laurel Avenue - Middletown, NJ 07748 - USA - - Email: sasif@att.com - - Andy Green - BT Design 21CN Converged Core IP & Data - 01473 629360 Adastral Park, Martlesham Heath, Ipswich IP5 3RE - UK - - Email: andy.da.green@bt.com - - Sameer Gulrajani - Cisco Systems - Tasman Drive San Jose, CA 95134 - USA - - Email: sameerg@cisco.com - - Pradeep G. Jain - Alcatel-Lucent Inc - 701 E Middlefield road Mountain view, CA 94043 - USA - - Email: pradeep.jain@alcatel-lucent.com - - Hiroshi Tsunoda (editor) +Author's Address + Hiroshi Tsunoda Tohoku Institute of Technology 35-1, Yagiyama Kasumi-cho, Taihaku-ku Sendai 982-8577 Japan Phone: +81-22-305-3411 Email: tsuno@m.ieice.org