CISCO-LISP-EXT-MIB
This MIB is an extension to the IETF LISP-MIB module defined
in RFC 7052. It contains Cisco defined managed objects and
traps to support monitoring devices that support the Locator/ID
Separation Protocol (LISP).
- Source file
CISCO-LISP-EXT-MIB- Last revised
- Identity
ciscoLispExtMIB- Base OID
1.3.6.1.4.1.9.9.825
Imported Objects
| CISCO-SMI | ciscoMgmt |
| IANA-ADDRESS-FAMILY-NUMBERS-MIB | AddressFamilyNumbers |
| INET-ADDRESS-MIB | InetPortNumber |
| LISP-MIB | LispAddressType lispEidRegistrationSiteName lispFeaturesEntry lispFeaturesMapCacheLimit lispGlobalStatsEntry lispMappingDatabaseTimeStamp lispUseMapResolverState lispUseMapServerState lispUseProxyEtrState |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Counter64 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | 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-LISP-EXT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LISP-EXT-MIB::ciscoLispExtMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LISP-EXT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LISP-EXT-MIB::ciscoLispExtMIB'
Objects (54)
Showing 54 of 54 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.9.825 |
||
.1.3.6.1.4.1.9.9.825.0 |
||
.1.3.6.1.4.1.9.9.825.1 |
||
.1.3.6.1.4.1.9.9.825.1.1 |
||
.1.3.6.1.4.1.9.9.825.1.1.1 |
||
|
Unsigned32
|
.1.3.6.1.4.1.9.9.825.1.1.1.1 |
|
.1.3.6.1.4.1.9.9.825.1.1.1.2 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.825.1.1.1.3 |
|
.1.3.6.1.4.1.9.9.825.1.1.1.4 |
||
.1.3.6.1.4.1.9.9.825.1.1.1.5 |
||
.1.3.6.1.4.1.9.9.825.1.1.1.6 |
||
.1.3.6.1.4.1.9.9.825.1.1.1.7 |
||
.1.3.6.1.4.1.9.9.825.1.2 |
||
.1.3.6.1.4.1.9.9.825.1.2.1 |
||
|
Unsigned32
|
.1.3.6.1.4.1.9.9.825.1.2.1.1 |
|
.1.3.6.1.4.1.9.9.825.1.2.1.2 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.825.1.2.1.3 |
|
.1.3.6.1.4.1.9.9.825.1.2.1.4 |
||
.1.3.6.1.4.1.9.9.825.1.2.1.5 |
||
.1.3.6.1.4.1.9.9.825.1.2.1.6 |
||
.1.3.6.1.4.1.9.9.825.1.2.1.7 |
||
.1.3.6.1.4.1.9.9.825.1.3 |
||
.1.3.6.1.4.1.9.9.825.1.3.1 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.825.1.3.1.1 |
|
.1.3.6.1.4.1.9.9.825.1.3.1.10 |
||
.1.3.6.1.4.1.9.9.825.1.3.1.11 |
||
.1.3.6.1.4.1.9.9.825.1.3.1.12 |
||
.1.3.6.1.4.1.9.9.825.1.3.1.13 |
||
.1.3.6.1.4.1.9.9.825.1.3.1.2 |
||
.1.3.6.1.4.1.9.9.825.1.3.1.3 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.825.1.3.1.4 |
|
.1.3.6.1.4.1.9.9.825.1.3.1.5 |
||
.1.3.6.1.4.1.9.9.825.1.3.1.6 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.825.1.3.1.7 |
|
.1.3.6.1.4.1.9.9.825.1.3.1.8 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.825.1.3.1.9 |
|
.1.3.6.1.4.1.9.9.825.1.4 |
||
.1.3.6.1.4.1.9.9.825.1.4.1 |
||
.1.3.6.1.4.1.9.9.825.1.4.1.1 |
||
.1.3.6.1.4.1.9.9.825.1.5 |
||
.1.3.6.1.4.1.9.9.825.1.5.1 |
||
.1.3.6.1.4.1.9.9.825.1.5.1.1 |
||
.1.3.6.1.4.1.9.9.825.1.5.1.2 |
||
.1.3.6.1.4.1.9.9.825.1.5.1.3 |
||
.1.3.6.1.4.1.9.9.825.1.6 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.825.1.6.1 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.825.1.6.2 |
|
.1.3.6.1.4.1.9.9.825.1.7 |
||
.1.3.6.1.4.1.9.9.825.1.7.1 |
||
.1.3.6.1.4.1.9.9.825.1.7.2 |
||
.1.3.6.1.4.1.9.9.825.1.7.3 |
||
.1.3.6.1.4.1.9.9.825.2 |
||
.1.3.6.1.4.1.9.9.825.2.1 |
||
.1.3.6.1.4.1.9.9.825.2.2 |
Dependencies (16) 7 direct · 9 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
- IANA-ADDRESS-FAMILY-NUMBERS-MIBrfc
- INET-ADDRESS-MIBrfc
- IANA-RTPROTO-MIBrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- MPLS-TC-STD-MIBrfc
- MPLS-LSR-STD-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- VPN-TC-STD-MIBrfc
- MPLS-L3VPN-STD-MIBrfc
- LISP-MIBrfc
- CISCO-LISP-EXT-MIBciscoselected
Conformance Groups (8)
Compliance Statements (2)
OID
.1.3.6.1.4.1.9.9.825.2.1.1Compliance requirement for implementations of CISCO-LISP-EXT-MIB
by all LISP (P)xTR devices. Map-server database of gleaned RLOC
addresses only need to be supported on LISP Map Server.
by all LISP (P)xTR devices. Map-server database of gleaned RLOC
addresses only need to be supported on LISP Map Server.
Required groups
| mandatory | clispExtRlocMembershipGroup | |
| mandatory | clispExtReliableTransportSessionGroup | |
| mandatory | clispExtNotificationsGroup | |
| mandatory | clispExtGlobalStatsGroup | |
| mandatory | clispExtFeaturesGroup | |
| mandatory | clispExtNotificationSupportGroup | |
| mandatory | clispExtEidRegMoreSpecificValuesGroup |
OID
.1.3.6.1.4.1.9.9.825.2.1.2Compliance requirement for implementations of CISCO-LISP-EXT-MIB
by LISP Map Server devices.
by LISP Map Server devices.
Required groups
| mandatory | clispExtEidRegRlocMembershipGroup | |
| mandatory | clispExtReliableTransportSessionGroup | |
| mandatory | clispExtNotificationsGroup | |
| mandatory | clispExtGlobalStatsGroup | |
| mandatory | clispExtFeaturesGroup | |
| mandatory | clispExtNotificationSupportGroup | |
| mandatory | clispExtEidRegMoreSpecificValuesGroup |
Notifications / Traps (14)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.9.9.825.0.1 |
The device generates this notification when the map-resolver
reachability state changes. The lispUseMapResolverAddressLength and lispUseMapResolverAddress values are attached to the notification object ID. |
|
.1.3.6.1.4.1.9.9.825.0.10 |
The device generates this notification when the map-resolver
drops a map-request because the map-request does not conform to configured policy. The lispEidRegistrationEidLength and lispEidRegistrationEid values are attached to the notification object ID. |
|
.1.3.6.1.4.1.9.9.825.0.11 |
The device generates this notification when the map-server has
reached the limit of the number of map registrations it can accept as a result of the accept-more-specific configuration. This notification is router LISP instance specific. |
|
.1.3.6.1.4.1.9.9.825.0.12 |
The device generates this notification when the map-server has
reached the threshold of the number of map registrations it can accept as a result of accept-more-specific configuration. This notification is router LISP instance specific. |
|
.1.3.6.1.4.1.9.9.825.0.13 |
The device generates this notification when the xTR has reached
the limit of the number of map-cache it can create. This notification is instance specific. The lispFeaturesInstanceID and lispFeaturesAddressFamily values are attached to the notification object ID. |
|
.1.3.6.1.4.1.9.9.825.0.14 |
The device generates this notification when the xTR has reached
the threshold of the number of map-cache it can create. This notification is instance specific. The lispFeaturesInstanceID and lispFeaturesAddressFamily values are attached to the notification object ID. |
|
.1.3.6.1.4.1.9.9.825.0.2 |
The device generates this notification when the reliable transport
session state changes. The clispReliableTransportSessionPeerAddressLength, clispReliableTransportSessionPeerAddress, clispReliableTransportSessionPeerPort, clispReliableTransportSessionLocalAddressLength, clispReliableTransportSessionLocalAddress, clispReliableTransportSessionLocalPort values are attached to the notification object ID. |
|
.1.3.6.1.4.1.9.9.825.0.3 |
The device generates this notification when the xTR fails to
register a database mapping with the map-server. The lispMappingDatabaseEidLength, lispMappingDatabaseEid, lispUseMapServerAddressLength, lispUseMapServerAddress values are attached to the notification object ID. |
|
.1.3.6.1.4.1.9.9.825.0.4 |
The device generates this notification when the map-server
reachability state changes. The lispUseMapServerAddressLength and lispUseMapServerAddress values are attached to the notification object ID. |
|
.1.3.6.1.4.1.9.9.825.0.5 |
The device generates this notification when the proxy ETR
reachability state changes. The lispUseProxyEtrAddressLength and lispUseProxyEtrAddress values are attached to the notification object ID. |
|
.1.3.6.1.4.1.9.9.825.0.6 |
The device generates this notification when all the registration
for a site expires on the map-server. The lispEidRegistrationEidLength and lispEidRegistrationEid values are attached to the notification object ID. |
|
.1.3.6.1.4.1.9.9.825.0.7 |
The device generates this notification when the map-server fails
to accept a map registration. The lispEidRegistrationEidLength and lispEidRegistrationEid values are attached to the notification object ID. If clispExtEidRegFailureCause value is noEidPrefixConfiguration(1) the lispEidRegistrationSiteName object in the notification will be empty. |
|
.1.3.6.1.4.1.9.9.825.0.8 |
The device generates this notification when the map-server has
reached the limit of the number of map registrations it can accept as a result of the accept-more-specific configuration. This notification is instance specific. The lispFeaturesInstanceID and lispFeaturesAddressFamily values are attached to the notification object ID. |
|
.1.3.6.1.4.1.9.9.825.0.9 |
The device generates this notification when the map-server has
reached the threshold of the number of map registrations it can accept as a result of accept-more-specific configuration. This notification is instance specific. The lispFeaturesInstanceID and lispFeaturesAddressFamily values are attached to the notification object ID. |