CISCO-MVPN-MIB
This MIB contains managed object definitions for
Cisco implementation of multicast in VPNs defined
by the Internet draft: draft-rosen-vpn-mcast-05.txt.
Note that this MIB works along with the
L3VPN-MPLS-VPN-MIB.
- Source file
CISCO-MVPN-MIB- Last revised
- Identity
ciscoMvpnMIB- Base OID
1.3.6.1.4.1.9.10.113
Imported Objects
| CISCO-SMI | ciscoExperiment |
| IF-MIB | ifIndex |
| INET-ADDRESS-MIB | InetAddress InetAddressType |
| MPLS-VPN-MIB | MplsVpnRouteDistinguisher mplsVpnVrfName |
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | DisplayString RowStatus TimeInterval TimeStamp TruthValue |
Net-SNMP examples using the cisco MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-MVPN-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-MVPN-MIB::ciscoMvpnMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-MVPN-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-MVPN-MIB::ciscoMvpnMIB'
Objects (74)
Showing 74 of 74 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.9.10.113 |
||
.1.3.6.1.4.1.9.10.113.0 |
||
.1.3.6.1.4.1.9.10.113.1 |
||
.1.3.6.1.4.1.9.10.113.1.1 |
||
.1.3.6.1.4.1.9.10.113.1.1.1 |
||
.1.3.6.1.4.1.9.10.113.1.1.2 |
||
.1.3.6.1.4.1.9.10.113.1.2 |
||
.1.3.6.1.4.1.9.10.113.1.2.1 |
||
.1.3.6.1.4.1.9.10.113.1.2.1.1 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.10.113.1.2.1.1.1 |
|
.1.3.6.1.4.1.9.10.113.1.2.1.1.2 |
||
.1.3.6.1.4.1.9.10.113.1.2.1.1.3 |
||
.1.3.6.1.4.1.9.10.113.1.2.1.1.4 |
||
.1.3.6.1.4.1.9.10.113.1.3 |
||
.1.3.6.1.4.1.9.10.113.1.3.1 |
||
.1.3.6.1.4.1.9.10.113.1.3.1.1 |
||
.1.3.6.1.4.1.9.10.113.1.3.1.1.1 |
||
.1.3.6.1.4.1.9.10.113.1.3.1.1.2 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.10.113.1.3.1.1.3 |
|
.1.3.6.1.4.1.9.10.113.1.3.1.1.4 |
||
.1.3.6.1.4.1.9.10.113.1.3.2 |
||
.1.3.6.1.4.1.9.10.113.1.3.2.1 |
||
.1.3.6.1.4.1.9.10.113.1.3.2.1.1 |
||
.1.3.6.1.4.1.9.10.113.1.3.2.1.2 |
||
.1.3.6.1.4.1.9.10.113.1.3.2.1.3 |
||
.1.3.6.1.4.1.9.10.113.1.3.2.1.4 |
||
|
kilobits per secondUnsigned32
|
.1.3.6.1.4.1.9.10.113.1.3.2.1.5 |
|
.1.3.6.1.4.1.9.10.113.1.3.2.1.6 |
||
.1.3.6.1.4.1.9.10.113.1.4 |
||
.1.3.6.1.4.1.9.10.113.1.4.1 |
||
.1.3.6.1.4.1.9.10.113.1.4.1.1 |
||
.1.3.6.1.4.1.9.10.113.1.4.1.1.1 |
||
|
OctetString
|
.1.3.6.1.4.1.9.10.113.1.4.1.1.2 |
|
.1.3.6.1.4.1.9.10.113.1.4.1.1.3 |
||
|
OctetString
|
.1.3.6.1.4.1.9.10.113.1.4.1.1.4 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.10.113.1.4.1.1.5 |
|
.1.3.6.1.4.1.9.10.113.1.4.1.1.6 |
||
.1.3.6.1.4.1.9.10.113.1.4.1.1.7 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.10.113.1.4.1.1.8 |
|
.1.3.6.1.4.1.9.10.113.1.4.2 |
||
.1.3.6.1.4.1.9.10.113.1.4.2.1 |
||
.1.3.6.1.4.1.9.10.113.1.4.2.1.1 |
||
|
OctetString
|
.1.3.6.1.4.1.9.10.113.1.4.2.1.2 |
|
.1.3.6.1.4.1.9.10.113.1.4.2.1.3 |
||
.1.3.6.1.4.1.9.10.113.1.4.2.1.4 |
||
|
OctetString
|
.1.3.6.1.4.1.9.10.113.1.4.2.1.5 |
|
.1.3.6.1.4.1.9.10.113.1.4.2.1.6 |
||
.1.3.6.1.4.1.9.10.113.1.4.2.1.7 |
||
.1.3.6.1.4.1.9.10.113.1.4.2.1.8 |
||
.1.3.6.1.4.1.9.10.113.1.4.2.1.9 |
||
.1.3.6.1.4.1.9.10.113.1.4.3 |
||
.1.3.6.1.4.1.9.10.113.1.4.3.1 |
||
.1.3.6.1.4.1.9.10.113.1.4.3.1.1 |
||
|
OctetString
|
.1.3.6.1.4.1.9.10.113.1.4.3.1.2 |
|
.1.3.6.1.4.1.9.10.113.1.4.3.1.3 |
||
|
OctetString
|
.1.3.6.1.4.1.9.10.113.1.4.3.1.4 |
|
.1.3.6.1.4.1.9.10.113.1.4.3.1.5 |
||
.1.3.6.1.4.1.9.10.113.1.4.3.1.6 |
||
.1.3.6.1.4.1.9.10.113.1.4.4 |
||
.1.3.6.1.4.1.9.10.113.1.4.4.1 |
||
.1.3.6.1.4.1.9.10.113.1.4.4.1.1 |
||
|
OctetString
|
.1.3.6.1.4.1.9.10.113.1.4.4.1.2 |
|
.1.3.6.1.4.1.9.10.113.1.4.4.1.3 |
||
|
OctetString
|
.1.3.6.1.4.1.9.10.113.1.4.4.1.4 |
|
.1.3.6.1.4.1.9.10.113.1.4.4.1.5 |
||
.1.3.6.1.4.1.9.10.113.1.4.4.1.6 |
||
|
Unsigned32
|
.1.3.6.1.4.1.9.10.113.1.4.4.1.7 |
|
.1.3.6.1.4.1.9.10.113.1.4.5 |
||
.1.3.6.1.4.1.9.10.113.1.4.5.1 |
||
.1.3.6.1.4.1.9.10.113.1.4.5.1.1 |
||
.1.3.6.1.4.1.9.10.113.1.4.5.1.2 |
||
.1.3.6.1.4.1.9.10.113.2 |
||
.1.3.6.1.4.1.9.10.113.2.1 |
||
.1.3.6.1.4.1.9.10.113.2.2 |
Dependencies (10) 8 direct · 2 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- CISCO-SMIcisco
- SNMPv2-TCrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- INET-ADDRESS-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- MPLS-VPN-MIBcisco
- CISCO-MVPN-MIBciscoselected
Conformance Groups (10)
|
Collection of scalar objects required for MVPN management.
|
.1.3.6.1.4.1.9.10.113.2.1.1
|
|
|
ciscoMvpnGenOperStatusChange ciscoMvpnGenOperChangeTime ciscoMvpnGenAssociatedInterfaces ciscoMvpnGenRowStatus
Collection of objects needed for MVPN MVRF management.
|
.1.3.6.1.4.1.9.10.113.2.1.2
|
|
|
ciscoMvpnMdtDefaultAddrType ciscoMvpnMdtDefaultAddress ciscoMvpnMdtEncapsType ciscoMvpnMdtDefaultRowStatus
Collection of objects needed for MVPN default MDT group
management. |
.1.3.6.1.4.1.9.10.113.2.1.3
|
|
|
ciscoMvpnMdtDataRangeAddrType ciscoMvpnMdtDataRangeAddress ciscoMvpnMdtDataWildcardType ciscoMvpnMdtDataWildcardBits ciscoMvpnMdtDataThreshold ciscoMvpnMdtDataRowStatus
Collection of objects needed for MVPN data MDT group
management. |
.1.3.6.1.4.1.9.10.113.2.1.4
|
|
|
Collection of objects that list sources in a MVRF
and the corresponding MDT groups. |
.1.3.6.1.4.1.9.10.113.2.1.5
|
|
|
ciscoMvpnBgpMdtUpdateRd ciscoMvpnBgpMdtUpdOrigAddrType ciscoMvpnBgpMdtUpdateOriginator ciscoMvpnBgpMdtUpdNhAddrType ciscoMvpnBgpMdtUpdateNexthop
Collection of objects needed for MVPN BGP MDT updates
related information. |
.1.3.6.1.4.1.9.10.113.2.1.6
|
|
|
Collection of objects needed for management of MVPN MDT
data joins received by a device. |
.1.3.6.1.4.1.9.10.113.2.1.7
|
|
|
Collection of objects needed for management of MVPN MDT
data joins received by a device. |
.1.3.6.1.4.1.9.10.113.2.1.8
|
|
|
Objects required for MDT tunnel interface management.
|
.1.3.6.1.4.1.9.10.113.2.1.9
|
|
|
A collection of MVPN notifications.
|
.1.3.6.1.4.1.9.10.113.2.1.10
|
Compliance Statements (2)
OID
.1.3.6.1.4.1.9.10.113.2.2.1Compliance statement for agents that support read-create
so that both configuration and monitoring can be
accomplished via this MIB module.
so that both configuration and monitoring can be
accomplished via this MIB module.
Required groups
| mandatory | ciscoMvpnScalarGroup | |
| mandatory | ciscoMvpnMIBGenericGroup | |
| mandatory | ciscoMvpnMIBMdtDefaultGroup | |
| mandatory | ciscoMvpnMIBMdtDataGroup | |
| mandatory | ciscoMvpnMIBMrouteMdtGroup | |
| mandatory | ciscoMvpnMIBBgpMdtUpdateGroup | |
| mandatory | ciscoMvpnMIBMdtJnRcvGroup | |
| mandatory | ciscoMvpnMIBMdtJnSendGroup | |
| mandatory | ciscoMvpnTunnelGroup | |
| mandatory | ciscoMvpnNotificationGroup |
Object refinements
| Object | Access | Syntax | Description |
|---|---|---|---|
| ciscoMvpnGenRowStatus | Support for notReady(3) and createAndWait(5) is not required. |
||
| ciscoMvpnMdtDefaultAddrType | Not all Internet address types need to be supported. | ||
| ciscoMvpnMdtEncapsType | Not all encapsulation types defined need to be supported. Only one type may be supported by default. |
||
| ciscoMvpnMdtDefaultRowStatus | Support for notReady(3) and createAndWait(5) is not required. |
||
| ciscoMvpnMdtDataRangeAddrType | Not all Internet address types need to be supported. | ||
| ciscoMvpnMdtDataWildcardType | Not all Internet address types need to be supported. | ||
| ciscoMvpnMdtDataRowStatus | Support for notReady(3) and createAndWait(5) is not required. |
||
| ciscoMvpnMrouteMdtGrpAddrType | Not all Internet address types need to be supported. | ||
| ciscoMvpnBgpMdtUpdOrigAddrType | Not all Internet address types need to be supported. | ||
| ciscoMvpnBgpMdtUpdNhAddrType | Not all Internet address types need to be supported. | ||
| ciscoMvpnMdtJnSendMdtGrpAddrType | Not all Internet address types need to be supported. |
OID
.1.3.6.1.4.1.9.10.113.2.2.2Compliance statement for agents that support the
monitoring of MVRFs via this MIB module.
monitoring of MVRFs via this MIB module.
Required groups
| mandatory | ciscoMvpnScalarGroup | |
| mandatory | ciscoMvpnMIBGenericGroup | |
| mandatory | ciscoMvpnMIBMdtDefaultGroup | |
| mandatory | ciscoMvpnMIBMdtDataGroup | |
| mandatory | ciscoMvpnMIBMrouteMdtGroup | |
| mandatory | ciscoMvpnMIBBgpMdtUpdateGroup | |
| mandatory | ciscoMvpnMIBMdtJnRcvGroup | |
| mandatory | ciscoMvpnMIBMdtJnSendGroup | |
| mandatory | ciscoMvpnTunnelGroup | |
| mandatory | ciscoMvpnNotificationGroup |
Object refinements
| Object | Access | Syntax | Description |
|---|---|---|---|
| ciscoMvpnGenRowStatus | readonly | Write access is not required and active(1) is the only status that needs to be supported. |
|
| ciscoMvpnMdtDefaultAddrType | readonly | Not all Internet address types need to be supported. Write access is not required. |
|
| ciscoMvpnMdtDefaultAddress | readonly | Write access is not required. | |
| ciscoMvpnMdtEncapsType | readonly | Not all encapsulation types defined need to be supported. Only one type may be supported by default. Write access is not required. |
|
| ciscoMvpnMdtDefaultRowStatus | readonly | Write access is not required and active(1) is the only status that needs to be supported. |
|
| ciscoMvpnMdtDataRangeAddrType | readonly | Not all Internet address types need to be supported. Write access is not required. |
|
| ciscoMvpnMdtDataRangeAddress | readonly | Write access is not required. | |
| ciscoMvpnMdtDataWildcardType | readonly | Not all Internet address types need to be supported. Write access is not required. |
|
| ciscoMvpnMdtDataWildcardBits | readonly | Write access is not required. | |
| ciscoMvpnMdtDataThreshold | readonly | Write access is not required. | |
| ciscoMvpnMdtDataRowStatus | readonly | Write access is not required and active(1) is the only status that needs to be supported. |
|
| ciscoMvpnMrouteMdtGrpAddrType | Not all Internet address types need to be supported. | ||
| ciscoMvpnBgpMdtUpdOrigAddrType | Not all Internet address types need to be supported. | ||
| ciscoMvpnBgpMdtUpdNhAddrType | Not all Internet address types need to be supported. | ||
| ciscoMvpnMdtJnSendMdtGrpAddrType | Not all Internet address types need to be supported. |
Notifications / Traps (1)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.9.10.113.0.2 |
A ciscoMvpnMvrfChange notification signifies a change about
a MVRF in the device. The change event can be creation of the MVRF, deletion of the MVRF or an update on the default or data MDT configuration of the MVRF. The change event is indicated by ciscoMvpnGenOperStatusChange embedded in the notification. The user can then query ciscoMvpnGenericTable, ciscoMvpnMdtDefaultTable and/or ciscoMvpnMdtDataTable to get the details of the change as necessary. Note: Since the creation of a MVRF is often followed by configuration of default and data MDT groups 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 data MDT configuration. Similarly, deletion of default or data MDT configuration on a MVRF happens before a MVRF is deleted, it is recommended that the agent send the notification for MVRF deletion event only. |