Cisco ASR 1000 Series Aggregation Services Routers MIB Specifications

From DocWiki

Jump to: navigation, search

This chapter describes the Management Information Base (MIB) on the Cisco ASR 1000 Series and CSR 1000v Routers. It includes the following sections:
*Cisco ASR 1000 Series Routers and CSR 1000v MIBs,
*Cisco ASR 1000 Series Routers and CSR 1000v MIB Categories,


Cisco ASR 1000 Series and CSR 1000v Routers MIBs
Each MIB description lists relevant constraints about the MIB’s implementation on the Cisco ASR 1000 Series Routers platform. Any objects not listed in a table are implemented as defined in the MIB. For detailed MIB descriptions, see the standard MIB.

Note Not all the MIBs included in a Cisco IOS software release are fully supported by the Cisco ASR 1000 Series Router. Some MIBs are not supported at all. Other MIBs might work, but they have not been tested on the router. In addition, some MIBs are deprecated, but cannot be removed from the software. When a MIB is included in the image, it does not necessarily mean that is supported by the Cisco ASR 1000 Series Router platform.
For more information about the MIBs that are included in this releases, see the “Downloading and Compiling MIBs” section on page 2-1.

Cisco ASR 1000 Series Routers and CSR 1000v MIB Categories
The subsequent tables list the following categories of MIBs in the Cisco ASR 1000 Series Routers Image on the Cisco ASR 1000 Series Routers:
• Supported and verified MIBs (tested for Cisco ASR 1000 Series Routers)—The MIBs exist in the image, the code is implemented, and Cisco has verified that all the supported objects work properly (Table 3-1).

• Supported and unverified MIBs (not tested for Cisco ASR 1000 Series and CSR 1000v Routers)—The MIBs exist in the image, the code is implemented, but Cisco has not verified if it is working properly (Table 3-2). • Unsupported MIBs (no level of support or testing on the Cisco ASR 1000 Series and CSR 1000v Routers)—The MIBs may be posted on Cisco.com, but are not present in the image and cannot be queried (Table 3-3).
The MIB version string indicates the date and time that it was most recently modified. The format is YYMMDDHHMMZ or YYYYMMDDHHMMZ, where:
• YY is the last two digits of the year (only years between 1900 and1999).
• YYYY is all four digits of the year (any year).
• MM is the month (01 through 12).
• DD is the day of the month (01 through 31).
• HH is hours (00 through 23).
• MM is minutes (00 through 59).
• Z (the ASCII character Z), denotes Coordinated Universal Time (UTC, formerly Greenwich Mean Time [GMT]). This datatype stores the date and time fields YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, TIMEZONE_HOUR, and TIMEZONE_MINUTE.


Note For example, 9502192015Z and 199502192015Z represent 8:15 GMT on 19 February 1995. Years after 1999 use the four-digit format. Years 1900-1999 may use the two-digit or four-digit format.

Note In the following tables you might see the term Unknown. This term refers to the MIB that does not have a recorded time stamp indicating the latest modification.
Supported and Verified MIBs
Table 3-1 lists the MIBs that are supported and verified in the following Cisco IOS release. The table lists the MIBs, corresponding notification name, and applicable MIB versions.


Contents

Supported and Verified Cisco ASR 1000 Series and CSR 1000v Routers MIBs

MIB Notification Name Revision ID Miscellaneous Comments
ATM-MIB 9406072245Z Not Applicable for CSR1000v
BGP4-MIB (RFC 1657) bgpEstablished
bgpBackwardTransition
9405050000Z
CISCO-AAA-SERVER-MIB casServerStateChange 200001200000Z
CISCO-AAA-SESSION-MIB 200603210000Z
CISCO-AAL5-MIB 200309220000Z Not Applicable for CSR1000v
CISCO-ATM-EXT-MIB 200301060000Z Not Applicable for CSR1000v
CISCO-ATM-PVCTRAP-EXTN-M IB

catmIntfPvcUpTrap

catmIntfPvcOAMFailureTrap

catmIntfPvcSegCCOAMFailureTrap

catmIntfPvcEndCCOAMFailureTrap

catmIntfPvcAISRDIOAMFailureTrap

catmIntfPvcAnyOAMFailureTrap

catmIntfPvcOAMRecoverTrap

catmIntfPvcSegCCOAMRecoverTrap

catmIntfPvcEndCCOAMRecoverTrap

catmIntfPvcAISRDIOAMRecoverTrap

catmIntfPvcAnyOAMRecoverTrap

catmIntfPvcUp2Trap

catmIntfPvcDownTrap

catmIntfPvcSegAISRDIFailureTrap

catmIntfPvcEndAISRDIFailureTrap

catmIntfPvcSegAISRDIRecoverTrap catmIntfPvcEndAISRDIRecoverTrap

200303240000Z Not Applicable for CSR1000v
CISCO-ATM-QOS-MIB 200206100000Z Not Applicable for CSR1000v
CISCO-BGP4-MIB cbgpFsmStateChange

cbgpBackwardTransition cbgpPrefixThresholdExceeded cbgpPrefixThresholdClear cbgpPeer2EstablishedNotification cbgpPeer2BackwardTransNotification cbgpPeer2FsmStateChange cbgpPeer2BackwardTransition cbgpPeer2PrefixThresholdExceeded cbgpPeer2PrefixThresholdClear

200302240000Z
CISCO-BULK-FILE-MIB cbfDefineFileCompletion 200108220000Z
CISCO-CBP-TARGET-MIB 200605240000Z
CISCO-CDP-MIB 200503210000Z
CISCO-CEF-MIB cefResourceFailure

cefPeerStateChange cefPeerFIBStateChange cefInconsistencyDetection

200601300000Z
CISCO-CLASS-BASED-QOS-MIB 200901260000Z
CISCO-CONFIG-COPY-MIB ccCopyCompletion 200403170000Z
CISCO-CONFIG-MAN-MIB ciscoConfigManEvent

ccmCLIRunningConfigChanged ccmCTIDRolledOver

200608220000Z
CISCO-CONTEXT-MAPPING-MIB 200503170000Z
CISCO-DATA-COLLECTION-MIB cdcVFileCollectionError

cdcFileXferComplete

200210300530Z
CISCO-DIAL-CONTROL-MIB 200505260000Z
CISCO-DYNAMIC-TEMPLATE-M IB 200709060000Z
CISCO-EIGRP-MIB 200411160000Z
CISCO-EMBEDDED-EVENT-MG R-MIB cEventMgrServerEvent

cEventMgrPolicyEvent

200304160000Z
CISCO-ENHANCED-MEMPOOL-MIB cempMemBufferNotify 200302240000Z1
CISCO-ENTITY-ALARM-MIB ceAlarmAsserted ceAlarmCleared 9907062150Z
CISCO-ENTITY-EXT-MIB 200811240000Z
CISCO-ENTITY-FRU-CONTROL-MIB cefcModuleStatusChange

cefcPowerStatusChange cefcFRUInserted cefcFRURemoved cefcUnrecognizedFRU cefcFanTrayStatusChange

201112220000Z Not Applicable for CSR1000v
CISCO-ENTITY-PERFORMANCE-MIB 201205150000Z
CISCO-ENTITY-QFP-MIB 201205150000Z
CISCO-ENTITY-SENSOR-MIB entSensorThresholdNotification 200601010000Z Not Applicable for CSR1000v
CISCO-ENTITY-VENDORTYPE-OID-MIB 200505050930Z
CISCO-ETHERLIKE-EXT-MIB 201006040000Z
CISCO-EVC-MIB cevcEvcCreationNotification

cevcEvcDeletionNotification cevcEvcStatusChangedNotification

200805010000Z
CISCO-FLASH-MIB ciscoFlashCopyCompletionTrap

ciscoFlashPartitioningCompletionTrap ciscoFlashMiscOpCompletionTrap ciscoFlashDeviceChangeTrap ciscoFlashDeviceInsertedNotif ciscoFlashDeviceRemovedNotif ciscoFlashDeviceInsertedNotifRev1 ciscoFlashDeviceRemovedNotifRev1

200403180000Z
CISCO-FRAME-RELAY-MIB 200010130000Z
CISCO-FTP-CLIENT-MIB 9710091700Z
CISCO-HSRP-EXT-MIB 9808030000Z
CISCO-HSRP-MIB cHsrpStateChange 9808030000Z
CISCO-IETF-ATM2-PVCTRAP-MIB atmIntfPvcFailuresTrap 9802030000Z Not Applicable for CSR1000v
CISCO-IETF-BFD-MIB ciscoBfdSessUp

ciscoBfdSessDown

201104160000Z
CISCO-IETF-FRR-MIB cmplsFrrProtected 200211051200Z
CISCO-IETF-ISIS-MIB ciiDatabaseOverload

ciiManualAddressDrops ciiCorruptedLSPDetected ciiAttemptToExceedMaxSequence ciiIDLenMismatch ciiMaxAreaAddressesMismatch ciiOwnLSPPurge ciiSequenceNumberSkip ciiAuthenticationTypeFailure iiAuthenticationFailure ciiVersionSkew ciiAreaM

200508161200Z
CISCO-IETF-PPVPN-MPLS-VPN-MIB cMplsNumVrfRouteMaxThreshCleared 200304171200Z
CISCO-IETF-PW-ATM-MIB 200504191200Z Not Applicable for CSR1000v
CISCO-IETF-PW-ENET-MIB 200209221200Z
CISCO-IETF-PW-MIB cpwVcDown

cpwVcUp

200403171200Z
CISCO-IETF-PW-MPLS-MIB 200302261200Z
CISCO-IF-EXTENSION-MIB 200311140000Z
CISCO-IGMP-FILTER-MIB 200111080000Z
CISCO-IMAGE-MIB 9508150000Z
CISCO-IMAGE-LICENSE-MGMT-MIB cilmBootImageLevelChanged 200710160000Z
CISCO-IP-LOCAL-POOL-MIB ciscoIpLocalPoolInUseAddrNoti 200304032000Z
CISCO-IPMROUTE-MIB ciscoIpMRouteMissingHeartBeats 200503070000Z
CISCO-IPSEC-FLOW-MONITOR-MIB cikeTunnelStart

cikeTunnelStop cikeSysFailure cikeCertCrlFailure cikeProtocolFailure cikeNoSa cipSecTunnelStart cipSecTunnelStop cipSecSysFailure cipSecSetUpFailure cipSecEarlyTunTerm cipSecProtocolFailure cipSecNoSa

200010131800Z
CISCO-IPSEC-MIB cipsIsakmpPolicyAdded

cipsIsakmpPolicyDeleted cipsCryptomapAdded cipsCryptomapDeleted cipsCryptomapSetAttached cipsCryptomapSetDetached cipsTooManySAs

200008071139Z
CISCO-IPSEC-POLICY-MAP-MIB 200008171257Z
CISCO-IP-TAP-MIB 200403110000Z
CISCO-IP-URPF-MIB cipUrpfIfDropRateNotify 200411120000Z
CISCO-LAG-MIB
CISCO-LICENSE-MGMT-MIB clmgmtLicenseExpired

clmgmtLicenseExpiryWarning clmgmtLicenseUsageCountExceeded clmgmtLicenseUsageCountAboutToExceed clmgmtLicenseInstalled clmgmtLicenseCleared clmgmtLicenseRevoked clmgmtLicenseEULAAccepted clmgmtLicenseNotEnforced clmgmtLicenseSubscriptionExpiryWarning clmgmtLicenseSubscriptionExtExpiryWarning clmgmtLicenseSubscriptionExpired clmgmtLicenseEvalRTUTransitionWarning clmgmtLicenseEvalRTUTransition

201104190000Z
CISCO-MVPN-MIB ciscoMvpnMvrfChange 200402231200Z
CISCO-NBAR-PROTOCOL-DISC OVERY-MIB 200208160000Z
CISCO-NETFLOW-MIB 200604200000Z
CISCO-NTP-MIB 200307070000Z
CISCO-OSPF-MIB

(draft-ietf-ospf-mib-update-05)

200307180000Z
CISCO-OSPF-TRAP-MIB

(draft-ietf-ospf-mib-update-05)

cospfIfConfigError

cospfVirtIfConfigError cospfTxRetransmit cospfVirtIfTxRetransmit cospfOriginateLsa cospfMaxAgeLsa cospfNssaTranslatorStatusChange cospfShamLinkStateChange cospfShamLinksStateChange cospfShamLinkNbrStateChange cospfShamLinkConfigError cospfShamLinkAuthFailure cospfShamLinkRxBadPacket cospfShamLinkTxRetransmit

200307180000Z
CISCO-PIM-MIB ciscoPimInterfaceUp

ciscoPimInterfaceDown ciscoPimRPMappingChange ciscoPimInvalidRegister ciscoPimInvalidJoinPrune

200011020000Z
CISCO-PING-MIB ciscoPingCompletion 200108280000Z
CISCO-PPPOE-MIB cPppoeSystemSessionThresholdTrap

cPppoeVcSessionThresholdTrap

200102200000Z
CISCO-PROCESS-MIB cpmCPURisingThreshold
cpmCPUFallingThreshold
201005060000Z
CISCO-PRODUCTS-MIB 200505051930Z
CISCO-QINQ-VLAN-MIB 200411290000Z
CISCO-RADIUS-EXT-MIB 201005250000Z
CISCO-RF-MIB ciscoRFSwactNotif

ciscoRFProgressionNotif ciscoRFIssuStateNotifRev1

200803180000Z Not Applicable for CSR1000v
CISCO-RTTMON-IP-EXT-MIB 200608020000Z
CISCO-RTTMON-MIB rttMonConnectionChangeNotification

rttMonTimeoutNotification rttMonThresholdNotification rttMonVerifyErrorNotification rttMonNotification rttMonLpdDiscoveryNotification rttMonLpdGrpStatusNotification

200701260000Z
CISCO-SIP-UA-MIB 200402190000Z
CISCO-SESS-BORDER-CTRLR-C ALL-STATS-MIB 200808270000Z
CISCO-SESS-BORDER-CTRLR-E VENT-MIB csbAlarmSubsystem

csbAlarmSeverity csbAlarmID csbAlarmTime csbSBCServiceName csbDynamicBlackListSubFamily csbDynamicBlackListVpnId csbDynamicBlackListAddressType csbDynamicBlackListAddress csbDynamicBlackListTransportType csbDynamicBlackListPortNumber csbDynamicBlackListSrcBlocked csbAlarmDescription

200808270000Z
CISCO-SESS-BORDER-CTRLR-S TATS-MIB 201009150000Z
CISCO-SONET-MIB ciscoSonetSectionStatusChange

ciscoSonetLineStatusChange ciscoSonetPathStatusChange

200205220000Z Not Applicable for CSR1000v
CISCO-SUBSCRIBER-SESSION-MIB csubJobFinishedNotify 200709060000Z
CISCO-SYSLOG-MIB clogMessageGenerated 9508070000Z
CISCO-TAP2-MIB ciscoTap2MIBActive

ciscoTap2MediationTimedOut ciscoTap2MediationDebug ciscoTap2StreamDebug ciscoTap2Switchover

200611270000Z
CISCO-UBE-MIB 201011290000Z
CISCO-UNIFIED-FIREWALL-MIB 200509220000Z
CISCO-USER-CONNECTION-TA P-MIB 200708090000Z
CISCO-VLAN-IFTABLE-RELATI ONSHIP-MIB 9904010530Z
CISCO-VLAN-MEMBERSHIP-MIB vmVmpsChange 200404070000Z
CISCO-VPDN-MGMT-MIB cvpdnNotifSession

cvpdnTrapDeadcacheEvent

200601200000Z
CISCO-VOICE-COMMON-DIAL-CONTROL-MIB 200903180000Z
CISCO-VOICE-DIAL-CONTROL-MIB cvdcFallbackNotification 200905070000Z
CISCO-VOIP-TAP-MIB 200910010000Z
DIAL-CONTROL-MIB (RFC 2128) dialCtlPeerCallInformation

dialCtlPeerCallSetup

9609231544Z
DS1-MIB (RFC 2495) dsx1LineStatusChange 9808011830Z Not Applicable for CSR1000v
DS3-MIB (RFC 2496) dsx3LineStatusChange 9808012130Z Not Applicable for CSR1000v
ENTITY-MIB (RFC 4133) entConfigChange 200508100000Z
ENTITY-SENSOR-MIB (RFC 3433) 200212160000Z Not Applicable for CSR1000v
ENTITY-STATE-MIB entStateOperEnabled

entStateOperDisabled

200511220000Z
ETHER-WIS (RFC 3637) 200309190000Z
ETHERLIKE-MIB (RFC 3635) 200309190000Z
EVENT-MIB (RFC 2981) mteTriggerFired

mteTriggerRising mteTriggerFalling mteTriggerFailure mteEventSetFailure

200010160000Z
EXPRESSION-MIB 9802251700Z
FRAME-RELAY-DTE-MIB (RFC1315-MIB) 9511170836Z Not Applicable for CSR1000v
IF-MIB (RFC 2863) linkDown

linkUp

9611031355Z
IGMP-STD-MIB (RFC 2933) 200009280000Z
IP-FORWARD-MIB (RFC 4292) 200602010000Z
IP-MIB (RFC 4293) 200602020000Z
IPMROUTE-STD-MIB (RFC 2932) 200009220000Z
MPLS-L3VPN-STD-MIB (RFC 4382) mplsL3VpnVrfUp
mplsL3VpnVrfDown 

mplsL3VpnVrfRouteMidThreshExceeded mplsL3VpnVrfNumVrfRouteMaxThreshExceeded mplsL3VpnNumVrfSecIllglLblThrshExcd mplsL3VpnNumVrfRouteMaxThreshCleared

200601230000Z
MPLS-LDP-GENERIC-STD-MIB (RFC 3815) 200406030000Z
MPLS-LDP-STD-MIB (RFC 3815) mplsLdpInitSessionThresholdExceeded

mplsLdpPathVectorLimitMismatch mplsLdpSessionUp mplsLdpSessionDown

200406030000Z
MPLS-LSR-STD-MIB (RFC 3813) mplsXCUp

mplsXCDown

200406030000Z
MPLS-TE-MIB mplsTunnelUp

mplsTunnelDown mplsTunnelRerouted

200011211200Z
MPLS-VPN-MIB mplsVrfIfUp

mplsVrfIfDown mplsNumVrfRouteMidThreshExceeded mplsNumVrfRouteMaxThreshExceeded mplsNumVrfSecIllegalLabelThreshExceeded

200110151200Z
MSDP-MIB msdpEstablished

msdpBackwardTransition

9912160000Z
NAT-MIB 201304260000Z
NHRP-MIB 9908260000Z
NOTIFICATION-LOG-MIB (RFC 3014) 200011270000Z
OLD-CISCO-SYS-MIB
OSPF-MIB (RFC 1850) 9501201225Z
OSPF-TRAP-MIB (RFC 1850) ospfIfStateChange

ospfVirtIfStateChange ospfNbrStateChange ospfVirtNbrStateChange ospfIfConfigError ospfVirtIfConfigError ospfIfAuthFailure ospfVirtIfAuthFailure ospfIfRxBadPacket ospfVirtIfRxBadPacket ospfTxRetransmit ospfVirtIfTxRetransmit ospfOriginate

PIM-MIB (RFC 2934) pimNeighborLoss
RFC1213-MIB
RMON-MIB (RFC 1757)
RSVP-MIB newFlow

lostFlow

SNMP-COMMUNITY-MIB (RFC 2576
SNMP-FRAMEWORK-MIB (RFC 2571)
SNMP-MPD-MIB (RFC 2572)
SNMP-NOTIFICATION-MIB (RFC 2573)
SNMP-PROXY-MIB (RFC 2573)
SNMP-TARGET-MIB (RFC 2573)
SNMPv2-MIB (RFC 1907) coldStart

warmStart linkDown linkUp authenticationFailure egpNeighborLoss

SNMP-VIEW-BASED-ACM-MIB (RFC 2575)
SONET-MIB (RFC 2558)
TCP-MIB (RFC 4022) 200502180000Z
TUNNEL-MIB (RFC 4087) 200505160000Z
UDP-MIB (RFC 4113) 200505200000Z

For Release 02.03.02, the version for CISCO-ENHANCED-MEMPOOL-MIB is 200812050000Z

Supported and Unverified MIBs

Table 3-2 lists the MIBs, notification name, and versions in the Cisco ASR 1000 Series Routers image that are supported and unverified in the following Cisco IOS release.

Supported and Unverified Cisco ASR 1000 Series Routers MIBs in the Cisco ASR 1000 Series Routers Image

MIB Notification Name Revision ID
ATM-FORUM-ADDR-REG-MIB 9606200322Z
ATM-FORUM-MIB 9606200322Z
HC-ALARM-MIB 200212160000Z
SNMP-USM-MIB (RFC 2574) 9901200000Z

Unsupported MIBs

Table 3-3 lists the MIBs, notification name, and versions in the Cisco ASR 1000 Series Routers image that are unsupported in the following Cisco IOS release.

Supported and Unverified Cisco ASR 1000 Series Routers MIBs in the Cisco ASR 1000 Series Routers Image

MIB Notification Name Revision ID
ATM-ACCOUNTING-INFORMAT ION-MIB 9711050000Z
ATM-SOFT-PVC-MIB atmSoftPvcCallFailuresTrap 9703010000Z
ATM-TRACE-MIB UNKNOWN
CISCO-802-TAP-MIB 200607100000Z
CISCO-ATM2-MIB 9803040000Z
CISCO-ATM-CONN-MIB 200108060000Z
CISCO-ATM-RM-MIB 200101290000Z
CISCO-ATM-TRAFFIC-MIB 9705290000Z
CISCO-CALL-APPLICATION-MIB 9909220000Z
CISCO-ENHANCED-IMAGE-MIB 200501060000Z
CISCO-ENTITY-ASSET-MIB 200207231600Z
CISCO-ENVMON-MIB 200312010000Z
CISCO-IETF-NAT-MIB 200103010000Z
CISCO-IETF-PW-FR-MIB 200312160000Z
CISCO-IETF-PW-TDM-MIB 200607210000Z
CISCO-LAG-MIB 200212130000Z
CISCO-SLB-EXT-MIB cslbxFtStateChange 200302111000Z
CISCO-SLB-MIB ciscoSlbVirtualStateChange

ciscoSlbRealStateChange

200203180000Z
CISCO-TAP-MIB cTapMIBActive,

cTapMediationTimedOut cTapMediationDebug cTapStreamIpDebug

200401090000Z
CISCO-VOICE-ANALOG-IF-MIB 200510030000Z
CISCO-VOICE-IF-MIB 9803060000Z
IEEE8023-LAG-MIB 200006270000Z
OLD-CISCO-CHASSIS-MIB UNKNOWN

ATM-ACCOUNTING-INFORMATION-MIB The ATM-ACCOUNTING-INFORMATION-MIB contains objects to manage accounting information applicable to ATM connections.

Note This MIB is not verified in ASR 1000 Series Routers.

ATM-FORUM-ADDR-REG-MIB The ATM-FORUM-ADDR-REG-MIB contains objects to manage information, such as ATM user-network interface (UNI) addresses and ports. This MIB also contains ATM address registration administration information.


ATM-ACCOUNTING-INFORMATION-MIB The ATM-ACCOUNTING-INFORMATION-MIB contains objects to manage accounting information applicable to ATM connections. Note This MIB is not verified in ASR 1000 Series Routers.

ATM-FORUM-ADDR-REG-MIB

The ATM-FORUM-ADDR-REG-MIB contains objects to manage information, such as ATM user-network interface (UNI) addresses and ports. This MIB also contains ATM address registration administration information. Note This MIB is not supported in ASR 1000 Series Routers.

MIB Constraints

This table lists the constraints that the Cisco ASR1000 Series Router places on the objects in the ATM-MIB.

ATM-MIB Constraints

MIB Object Notes
atmInterfaceDs3PlcpTable Not used in Cisco ASR1000.
atmInterfaceTCTable Not supported.
atmTrafficDescrParamTable

atmTrafficDescrType atmTrafficDescrParam1 atmTrafficDescrParam2 atmTrafficDescrParam3 atmTrafficDescrParam4 atmTrafficDescrParam5 atmTrafficQoSClass

Read only.

Read only. Read only. Read only. Read only. Read only. Read only.

atmVclTable

atmVclAdminStatus atmVclReceiveTrafficDescrIndex atmVclTransmitTrafficDescrIndex atmVccAalType atmVccAal5CpcsTransmitSduSize atmVccAal5CpcsReceiveSduSize • atmVccAal5EncapsType • atmVclCrossConnectIdentifier • atmVclRowStatus • atmVclCastType • atmVclConnKind

Read only.

Read only. Read only. Read only. Read only. Default value 4470. Read only. Default value 4470. Read only. Read only. Read only. Not supported. Not supported.

atmVcCrossConnectIndexNext Not supported.
atmVcCrossConnectTable Not implemented.
atmTrafficDescrParamIndexNext Not supported.
atmVpCrossConnectTable Not supported.
atmVpCrossConnectIndexNext Not supported.
atmVplTable Read only.

Ntoe The ifType for the ifIndex object should be atm(37) type.


Note Shutting down "atm .0 subinterface" will only shut the atm main interface, and not the other atm subinterfaces.


Note The ATM mode is not supported on SPA-24CHT1-CE-ATM.

ATM-SOFT-PVC-MIB The ATM-SOFT-PVC-MIB contains ATM Forum definitions of managed objects for ATM Soft Permanent Virtual Circuits. This MIB is not supported in this release.

BGP4-MIB (RFC 1657) The BGP4-MIB (RFC 1657) provides access to the implementation information for the Border Gateway Protocol (BGP). The MIB provides: • BGP configuration information • Information about BGP peers and messages exchanged within • Information about the advertised networks

CISCO-802-TAP-MIB The CISCO-802-TAP-MIB contains object to manage Cisco intercept feature for 802 streams (IEEE 802 intercept, layer 2) . This MIB is used along with CISCO-TAP2-MIB to intercept 802 traffic.

CISCO-AAA-SERVER-MIB

The CISCO-AAA-SERVER-MIB contains objects to manage information such as authentication, authorization, and accounting (AAA) servers within the router and external to the router. This MIB provides: • Configuration information for AAA servers, including identities of external AAA servers • Statistics for AAA functions • Status (state) information for AAA servers

MIB Constraints

The configuration objects in the MIB are read-only. To configure AAA servers, use the CLI commands aaa new-model, aaa authentication ppp, aaa authorization, aaa accounting, and radius-server host. Table 3-5 lists the constraints that the router places on the objects in the CISCO-AAA-SERVER-MIB.

CISCO-AAA-SERVER-MIB Constraints

MIB Object Notes
casConfigTable

• casAddress • casAuthenPort • casAcctPort • casKey • casConfigRowStatus

Read only.

Read only. Read only. The default value is 1645. Read only. The default value is1646. Read only. The value is shown as " " (null string) for security reasons.

casStatisTable

• casAuthorTable • casAuthorRequest • casAuthorRequestTimeouts • casAuthorUnexpectedResponses • casAuthorServerErrorResponses • casAuthorIncorrectResponses • casAuthorResponseTime • casAuthorTransactionSuccesses • casAuthorTransactionFailures

For RADIUS servers, the value of these attributes is

always 0. Only TACACS+ servers can have nonzero values.
Note RADIUS servers do not make authorization requests.

CISCO-AAA-SESSION-MIB The CISCO-AAA-SESSION-MIB contains information about accounting sessions based on authentication, authorization, and accounting (AAA) protocols.

CISCO-AAL5-MIB The CISCO-AAL5-MIB contains objects to manage performance statistics for adaptation layer 5 (AAL5) virtual channel connections (VCCs). This MIB also contains information such as packets and octets that are received and transmitted on the VCC, which is missing from cAal5VccTable in RFC 1695.
Note Effective from Cisco IOS Release 15.1(3)S, CISCO-AAL5-MIB is supported on SPA-2CHT3-CE-ATM.

CISCO-ATM-EXT-MIB

The CISCO-ATM-EXT-MIB contains extensions to the Cisco ATM that are used to manage ATM entities. This MIB provides additional AAL5 performance statistics for a virtual channel connection (VCC) on an ATM interface.
Note Effective from Cisco IOS Release 15.1(3)S, CISCO-ATM-EXT-MIB is supported on SPA-2CHT3-CE-ATM. MIB Constraints Table 3-6 lists the constraint that the Cisco ASR 1000 Series Router places on the objects in the CISCO-ATM-EXT-MIB:

CISCO-ATM-EXT-MIB Constraint

MIB Object Notes
catmxVclOamTable Not supported.

NoteThe CISCO-ATM-EXT-MIB has only one table, cAal5VccExtTable. This table augments the aal5VccTable of the CISCO-AAL5-MIB. The cAal5VccExtTable contains additional AAL5 performance parameters.

CISCO-ATM-PVCTRAP-EXTN-MIB

The CISCO-ATM-PVCTRAP-EXTN-MIB contains objects to extend the functionality for the ATM-MIB. This MIB provides additional notifications and traps for permanent virtual circuits (PVCs) on the CISCO ASR 1000. The CISCO-ATM-PVCTRAP-EXTN-MIB is supplemented by CISCO-IETF-ATM2-PVCTRAP-MIB.

'CISCO-ATM-QOS-MIB

The CISCO-ATM-QOS-MIB contains objects to manage the following ATM QoS information: • Traffic shaping on a per-VC basis • Traffic shaping on a per-VP basis • Per-VC queuing/buffering.

Note Effective from Cisco IOS Release 15.1(3)S, CISCO-ATM-QOS-MIB is supported on SPA-2CHT3-CE-ATM.

MIB Constraints

Table 3-7 lists the constraints that the Cisco ASR 1000 Series Router places on the objects in the CISCO-ATM-QOS-MIB:

CISCO-ATM-QOS-MIB Constraints

MIB Object Notes
caqVccParamsTable

• caqVccParamsCdv • caqVccParamsCdvt • caqVccParamsIcr • caqVccParamsTbe • caqVccParamsFrtt • caqVccParamsNrm • caqVccParamsInvTrm • caqVccParamsInvCdf • caqVccParamsAdtf

Not supported.

Not supported. Not supported. Not supported. Not supported. Not supported. Not supported. Not supported.

caqVpcParamsTable

• caqVpcParamsAvailBw

Not supported.

CISCO-ATM2-MIB

The CISCO-ATM2-MIB contains objects to supplement ATM-MIB.

Note The CISCO-ATM2-MIB is not supported for any routers.

CISCO-ATM-CONN-MIB The CISCO-ATM-CONN-MIB contains objects to extend the VPL/VCL table defined in RFC1695 for ATM switch connection management.

Note The CISCO-ATM-CONN-MIB is not supported for any routers.

CISCO-ATM-RM-MIB

The CISCO-ATM-RM-MIB contains object to provide resource management functionality. This MIB complements standard ATM MIBs for Cisco devices.

Note This CISCO-ATM-RM-MIB is not supported in this release.

CISCO-ATM-TRAFFIC-MIB

The CISCO-ATM-TRAFFIC-MIB contains objects that provide extension to traffic OIDs and variables defined in RFC1695.

Note The CISCO-ATM-TRAFFIC-MIB is not supported in this release.

CISCO-BGP4-MIB

The CISCO-BGP4-MIB provides access to information related to the implementation of the Border Gateway Protocol (BGP). The MIB provides:

• BGP configuration information • Information about BGP peers and messages exchanged with them • Information about advertised networks

Begining with Cisco IOS Release 15.2(1)S, CISCO-BGP4-MIB supports IPv6 addresses in addition to IPv4 addresses. To support IPv6-based peers, four new tables are added in the CISCO-BGP4-MIB:

• cbgpPeer2Table • cbgpPeer2CapsTable • cbgpPeer2AddrFamilyTable • cbgpPeer2AddrFamilyPrefixTable Note These four tables have flexible indexing to support both the IPv4 and IPv6 peers.

MIB Tables

Table 3-8 lists the tables in the CISCO-BGP4-MIB.

CISCO-BGP4-MIB Tables

MIB Table Description
cbgpRouteTable Contains information about the routes to the destination networks

from all the BGP4 peers.

cbgpPeerTable Contains information about the connections with the BGP peers,

one entry for each BGP peer.

cbgpPeerCapsTable Contains information about the capabilities supported by a peer.

The capabilities of a peer are received while establishing the BGP connection.

cbgpPeerAddrFamilyTable Contains information related to the address families supported by a

peer.

cbgpPeerAddrFamilyPrefixTable Contains prefix-related information for the address families

supported by a peer.

cbgpPeer2Table Contains information about the connection with the BGP peers, one

entry for each BGP peer. This table supports IPv4 and IPv6 peers.

cbgpPeer2CapsTable Contains information about the capabilities supported by a BGP

peer. The capabilities of a peer are received while establishing the BGP connection. This table supports IPv4 and IPv6 peers.

cbgpPeer2AddrFamilyTable Contains information related to the address families supported by a

BGP peer. This table supports IPv4 and IPv6 peers.

cbgpPeer2AddrFamilyPrefixTable Contains prefix-related information for the address families

supported by a peer. This table supports IPv4 and IPv6 peers.

CISCO-BGP-POLICY-ACCOUNTING-MIB

The CISCO-BGP-POLICY-ACCOUNTING-MIB contains BGP policy-based accounting information (such as ingress traffic on an interface), which can be used for billing purposes. The MIB provides support for BGP Policy Accounting, which enables you to classify IP traffic into different classes and to maintain statistics for each traffic class.

The MIB contains counts of the number of bytes and packets of each traffic type on each input interface. This information can be used to charge customers according to the route that their traffic travels.

CISCO-BULK-FILE-MIB

The CISCO-BULK-FILE-MIB contains objects to create and delete files of SNMP data for bulk-file transfer.

MIB Constraints

Table 3-9 lists the constraints that the router places on the objects in the CISCO-BULK-FILE-MIB.

CISCO-BGP4-MIB Tables

MIB Objects Notes
cbfDefineFileTable

• cbfDefinedFileStorage

Only ephemeral type of file storage is supported.

Note The ephemeral bulk file created can be moved to a remote FTP server using CISCO-FTP-CLIENT-MIB.

cbfDefinedFileFormat Only bulkBinary and bulkASCII file formats are supported.
Notes: The cbfDefineFileTable has objects that are required for defining a bulk file and for controlling its creation. The cbfDefineObjectTable has information regarding the contents (SNMP data) that go into the bulk file. When an entry in the cbfDefineFileTable and its corresponding entries in the cbfDefineObjectTable are active, then cbfDefineFileNow can then be set to create. This causes a bulkFile to be created as defined in cbfDefineFileTable and it will also create an entry in the cbfStatusFileTable.

CISCO-CALL-APPLICATION-MIB

The CISCO-CALL-APPLICATION-MIB manages the call applications on a network device. A call application is a software module that processes data, voice, video, and fax calls. Note This MIB is not supported in the ASR 1000 Series Routers.

CISCO-CBP-TARGET-MIB

The CISCO-CBP-TARGET-MIB (common class-based policy) contains objects that provide a mapping of targets to which class-based features, such as QoS are applied. These features can be enabled in a feature-specific manner or through the Class-based Policy Language (CPL). The CISCO-CBP-TARGET-MIB abstracts the knowledge of the specific types of targets from the class-based policy feature-specific MIB definitions.

MIB Constraints

The configuration objects in the MIB are read-only. To configure AAA servers, use the CLI commands aaa new-model, aaa authentication ppp, aaa authorization, aaa accounting, and radius-server host. Table 3-10 lists the constraints that the router places on the objects in the CISCO-CBP-TARGET-MIB.

CISCO-CBP-TARGET-MIB Constraints

MIB Objects Notes
CbpTargetTable

• ccbptTargetType • • ccbptTargetDir • ccbptPolicyType • ccbptPolicyId • ccbptTargetStorageType • ccbptTargetStatus

Values are:

genIf(1) • atmPvc(2) • frDlci(3) • controlPlane(4) Values are: • input(2) • output(3) Value is always ciscoCbQos(1) to indicate mapping to CLASS-BASED-QOS-MIB. Contains the cbQosPolicyIndex value for this service-policy. Value is always volatile(2). Value is always volatile(1).

ccbptPolicyMap

• ccbptPolicyInstance

Contains the OID for a cbQosPolicyMapName

instance. Contains the OID for a cbQosIfType instance.

CISCO-CDP-MIB

The CISCO-CDP-MIB contains objects to manage the Cisco Discovery Protocol (CDP) on the router.

MIB Constraints

Table 3-11 lists the constraints that the router places on the objects in the CISCO-CDP-MIB.

CISCO-CDP-MIB Constraints

MIB Objects Notes
cdpCtAddressTable Not supported.
cdpGlobalLastChange Not supported.
cdpGlobalDeviceIdFormatCpb Not supported.
cdpGlobalDeviceIdFormat Not supported.
cdpInterfaceExtTable Not Implemented.

CISCO-CEF-MIB

The CISCO-CEF-MIB contains objects that manage Cisco Express Forwarding (CEF) technology. CEF is the key data plane forwarding path for Layer 3 IP switching technology. The CISCO-CEF-MIB monitors CEF operational data and provides notification when encountering errors in CEF, through SNMP.

CISCO-CEF-MIB Constraints

MIB Objects Notes
cefCfgAdminState Read only. This object is enabled by default.
cefCCCount Read only.
cefCCPeriod Read only.
cefCCEnabled Read only.

CISCO-CLASS-BASED-QOS-MIB

The CISCO-CLASS-BASED-QOS-MIB provides only read access to quality of service (QoS) configuration information and statistics for Cisco platforms that support the modular Quality of Service command-line interface (modular QoS CLI).

To understand how to navigate the CISCO-CLASS-BASED-QOS-MIB tables, it is important to understand the relationship among different QoS objects. QoS objects consists of:

• Match Statement—The specific match criteria to identify packets for classification purposes. • Class Map—A user-defined traffic class that contains one or more match statements used to classify packets into different categories. • Feature Action—AQoS feature. Features include police, traffic shaping, queueing, random detect, and packet marking. After the traffic has been classified, apply actions to each traffic class. • Policy Map—Auser-defined policy that associates a QoS feature action to the user-defined class map. • Service Policy—Apolicy map that has been attached to an interface. The MIB uses the following indices to identify QoS features and distinguish among instances of those features: • cbQosObjectsIndex—Identifies each QoS feature on the router. • cbQoSConfigIndex—Identifies a type of QoS configuration. This index is shared by QoS objects that have identical configuration. • cbQosPolicyIndex—Uniquely identifies a service policy. QoS MIB information is stored in: • Configuration instances—includes all class maps, policy maps, match statements, and feature action configuration parameters. Might have multiple identical instances. Multiple instances of the same QoS feature share a single configuration object, which is identified by cbQosConfigIndex. • Runtime Statistics instances—Includes summary counts and rates by traffic class before and after any configured QoS policies are enforced. In addition, detailed feature-specific statistics are available for select Policy Map features. Each has a unique run-time instance. Multiple instances of a QoS feature have a separate statistics object. Run-time instances of QoS objects are each assigned a unique identifier (cbQosObjectsIndex) to distinguish among multiple objects with matching configuration.

Note The Policing, Shaping, Queuing, and WRED features are not supported for the SPA-1CHOC3-CE-ATM. Note The SNMP does not support the bandwidth remaining ratio configuration. Bandwith is displayed in kbps.

Note If a class is defined without any action and is mapped to a policy-map, this class and class-default may return incorrect values for the post policy and drop counters represented in the cbQosCMStatsTable.

Note Only the MPLS EXP Bit Setting Marking feature is supported for the SPA-1CHOC3-CE-ATM. Note Effective from Cisco IOS Release 15.1(3)S, CISCO-CLASS-BASED-QOS-MIB is supported on SPA-2CHT3-CE-ATM.

MIB Constraints

Table 3-13 lists the constraints that the Cisco ASR 1000 Series Router places on the objects in the CISCO-CLASS-BASED-QOS-MIB.

Table 3-13

CISCO-CLASS-BASED-QOS-MIB Constraints

MIB Object Notes
cbQosATMPVCPolicyTable Not implemented.
cbQosFrameRelayPolicyTable Not implemented.
cbQosInterfacePolicyTable Not implemented.
cbQosIPHCCfgTable Not implemented.
cbQosPoliceColorStatsTable Not implemented.
cbQosPoliceCfgConformColor Not implemented.
cbQosPoliceCfgExceedColor Not implemented.
cbQosQueueingCfgTable

• cbQosQueueingCfgDynamicQNumber

Not implemented.
cbQosREDCfgTable

• cbQosREDCfgECNEnabled

Not implemented.
cbQosTableMapCfgTable Not implemented.
cbQosTableMapSetCfgTable Not implemented.
cbQosQueueingClassCfgTable Not implemented.
cbQosMeasureIPSLACfgTable Not implemented.
cbQosQueueingCfgPriorityLevel Not implemented.
cbQosREDClassCfgMaxThresholdUnit Not implemented.
cbQosREDClassCfgMinThresholdUnit Not implemented.
cbQosTSCfgRate64 Not implemented.
cbQosREDECNMarkPktOverflow Not implemented.
cbQosREDECNMarkPkt Not implemented.
cbQosREDECNMarkPkt64 Not implemented.
cbQosREDECNMarkByteOverflow Not implemented.
cbQosREDECNMarkByte Not implemented.
cbQosREDECNMarkByte64 Not implemented.
cbQosREDMeanQSizeUnits Not implemented.
cbQosREDMeanQSize Not implemented.
cbQosQueueingCfgPrioBurstSize Not supported.
cbQosQueueingCfgIndividualQSize Not supported.
cbQosQueueingCfgDynamicQNumber Not supported.
cbQosQueueingMaxQDepth Not supported.
cbQosREDECNMarkPktOverflow Not supported.
cbQosREDECNMarkPkt Not supported.
cbQosREDECNMarkPkt64 Not supported.
cbQosREDECNMarkByteOverflow Not supported.
cbQosREDECNMarkByte Not supported.
cbQosREDECNMarkByte64 Not supported.
cbQosSetCfgL2CosInnerValue Not supported.
cbQosSetDscpTunnelPkt64 Not supported.
cbQosSetPrecedenceTunnelPkt64 Not supported.
cbQosPoliceCfgConformAction This object is deprecated. Refer to equivalent object in cbQosPoliceActionCfgTable.
cbQosPoliceCfgConformSetValue This object is deprecated. Refer to equivalent object in cbQosPoliceActionCfgTable.
cbQosPoliceCfgExceedAction This object is deprecated. Refer to equivalent object in cbQosPoliceActionCfgTable.
cbQosPoliceCfgExceedSetValue This object is deprecated. Refer to equivalent object in cbQosPoliceActionCfgTable.
cbQosPoliceCfgViolateAction This object is deprecated. Refer to equivalent object in cbQosPoliceActionCfgTable.
cbQosPoliceCfgViolateSetValue This object is deprecated. Refer to equivalent object in cbQosPoliceActionCfgTable.
cbQosPoliceCfgRate

cbQosPoliceCfgBurstSize cbQosPoliceCfgExtBurstSize

These objects will have zero value when cir (committed information rate) is configured as percent for policing

configuration.


CISCO-CONFIG-COPY-MIB

The CISCO-CONFIG-COPY-MIB contains objects to copy configuration files on the router. For example, the MIB enables the SNMP agent to copy: • Configuration files to and from the network • The running configuration to the startup configuration and startup to running • The startup or running configuration files to and from a local Cisco IOS file system

CISCO-CONFIG-MAN-MIB

The CISCO-CONFIG-MAN-MIB contains objects to track and save changes to the router configuration. The MIB represents a model of the configuration data that exists elsewhere in the router and in peripheral devices. Its main purpose is to report changes to the running configuration through the SNMP notification ciscoConfigManEvent.


CISCO-CONTEXT-MAPPING-MIB

The CISCO-CONTEXT-MAPPING-MIB provides mapping tables that contain the information that a single SNMP agent sometimes needs to support multiple instances of the same MIB. In such cases, network management applications need to know the specific data/identifier values in each context. This is accomplished through the use of multiple SNMP contexts.

CISCO-DATA-COLLECTION-MIB

The CISCO-DATA-COLLECTION-MIB retrieves data periodically when the data displays as a set of discontinuous rows spread across multiple tables. This MIB facilitates data retrieval of tabular objects. This MIB can be used for performance and accounting purposes, where several row instances of a set of objects are polled over a period of time.

The MIB provides the user a way to specify which objects and which instances are required. In addition the MIB provides two ways in which this data can be retrieved.

MIB Constraints

Table 3-14 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-DATA-COLLECTION-MIB. Any MIB object not listed in this table is implemented as defined in the MIB.

CISCO-DATA-COLLECTION-MIB Constraints

MIB Object Notes
cdcVFileMgmtTable Not implemented.
cdcDGTable Not implemented.
cdcDGBaseObjectTable Not implemented.
cdcDGInstanceTable Not implemented.

CISCO-DIAL-CONTROL-MIB

The CISCO-DIAL-CONTROL-MIB module is an extension of RFC 2128, and defines the callHistoryTable that stores information pertaining to earlier calls.

CISCO-DYNAMIC-TEMPLATE-MIB

The CISCO-DYNAMIC-TEMPLATE-MIB contains objects that describe the dynamic templates. A dynamic template is a set of configuration attributes that a system can dynamically apply to a target.

MIB Tables

Table 3-15 lists the tables in the CISCO-DYNAMIC-TEMPLATE-MIB.

CISCO-DYNAMIC-TEMPLATE-MIB Tables

MIB Tables Description
cdtTemplateTable Lists the dynamic templates maintained by the system, including

those that are locally configured on the system, and those that are pushed to the system by external policy servers.

cdtTemplateTargetTable Lists the targets associated with one or more dynamic templates.
cdtTemplateAssociationTable Lists the templates associated with each target.
cdtTemplateUsageTable Contains a list of targets that use each dynamic template.
cdtTemplateCommonTable Contains attributes that relate to all the dynamic templates.
cdtIfTemplateTable Contains attributes that relate to the interface configuration.
cdtPppTemplateTable Contains attributes that relate to PPP connection configuration.
cdtPppPeerIpAddrPoolTable Contains a prioritized list of named pools for each PPP template.
cdtEthernetTemplateTable Contains attributes pertaining to the dynamic interfaces initiated on

ethernet virtual interfaces or automatically created VLANs.

cdtSrvTemplateTable Contains attributes pertaining to a service.

'MIB Constraints

Table 3-16 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-DYNAMIC-TEMPLATE-MIB. Any MIB object not listed in this table is implemented as defined in the MIB.

CISCO-DYNAMIC-TEMPLATE-MIB Constraints

MIB Objects Notes
cdtTemplateTable


• cdtTemplateName.
• cdtTemplateUsageCount
• cdtTemplateStatus
• cdtTemplateStorage
• cdtTemplateType
• cdtTemplateSrc

Read only


Read only.
Read only.
Not implemented.
Not implemented.
Not implemented.

cdtTemplateAssociationTable


• cdtTemplateAssociationName

Read only.
cdtTemplateUsageTable


• cdtTemplateUsageTargetType
• cdtTemplateUsageTargetId

Read only.


Read only.

cdtTemplateTargetTable Not implemented.
cdtTemplateCommonTable Not implemented.
cdtIfTemplateTable Not implemented.
cdtPppTemplateTable Not implemented.
cdtPppPeerIpAddrPoolTable Not implemented.
cdtEthernetTemplateTable Not implemented.
cdtSrvTemplateTable Not implemented.

CISCO-EIGRP-MIB

The CISCO-EIGRP-MIB contains objects to manage Enhanced Interior Gateway Protocol (EIGRP). EIGRP is a Cisco proprietary distance vector routing protocol, based on the Diffusing Update Algorithm (DUAL). DUAL defines the method to identify loop-free paths through a network.

CISCO-EMBEDDED-EVENT-MGR-MIB

The CISCO-EMBEDDED-EVENT-MGR-MIB provides descriptions and stores events generated by the Cisco Embedded Event Manager. The Cisco Embedded Event Manager detects hardware and software faults and other events such as OIR for the system.

CISCO-ENHANCED-IMAGE-MIB

The CISCO-ENHANCED-IMAGE-MIB provides information about events running on the system. The MIB modular operating systems.

CISCO-ENHANCED-MEMPOOL-MIB

The CISCO-ENHANCED-MEMPOOL-MIB contains objects to monitor memory pools on all of the physical entities on a managed system. It represents the different types of memory pools that may be present in a managed device. Memory use information is provided to users at three different intervals of time: 1 minute, 5 minutes, and 10 minutes. Memory pools can be categorized into two groups, predefined pools and dynamic pools. The following pool types are currently predefined:

• 1:Processor memory • 2:I/O memory • 3:PCI memory • 4:Fast memory • 5:Multibus memory • Other memory

Dynamic pools have a pool type value greater than any of the predefined types listed above. Only the processor pool is required to be supported by all devices. Support for other pool types is dependent on the device being managed.

Note The lsmpi_io memory is not modelled. The Cisco ASR1000 RP2 supports 64-bit architecture. Effective from Cisco IOS Release 15.2(4)S onwards, the CISCO-PROCESS-MIB supports 64-bit architecture.

MIB Constraints

The CISCO-ENHANCED-MEMPOOL-MIB is supported only in the Active RP module. Table 3-17 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-ENHANCED-MEMPOOL-MIB.

CISCO-ENHANCED-MEMPOOL-MIB Constraints

MIB Objects Notes
cempMemBufferPoolTable


• cempMemBufferSize
• cempMemBufferMin
• cempMemBufferMax
• cempMemBufferPermanent
• cempMemBufferTransient

Read only.


Read only.
Read only.
Read only.
Read only.

cempMemPoolTable


• cempMemPoolUsedLowWaterMark
• cempMemPoolAllocHit
• cempMemPoolAllocMiss
• cempMemPoolFreeHit
• cempMemPoolFreeMiss
• cempMemPoolHCShared
• cempMemPoolHCUsedLowWaterMark
• cempMemPoolShared
• cempMemPoolSharedOvrflw
• cempMemPoolUsedLowWaterMarkOvrflw

Not Implemented.


Not Implemented.
Not Implemented.
Not Implemented.
Not Implemented.
Not Implemented.
Not Implemented.
Not Implemented.
Not Implemented.

cempMemBufferPoolTable


• cempMemBufferFreeHit
• cempMemBufferFreeMiss

Not Implemented.


Not Implemented.

CISCO-ENTITY-ALARM-MIB

The CISCO-ENTITY-ALARM-MIB enables the Cisco ASR 1000 Series Routers to monitor the alarms generated by system components, such as chassis, slots, modules, power supplies, fans, and ports.

CISCO-ENTITY-ALARM-MIB supports these modules:

• SPA-10X1GE-V2 • SPA-1X10GE-L-V2 • SPA-1XCHSTM1/OC3 • SPA-1XCHOC12/DS0 • SPA-1XOC12-POS • SPA-1XOC3-ATM-V2 • SPA-1XOC48POS/RPR: 1 -port OC48/STM16 POS/RPR SFP Optics SPA • SPA-2X1GE-V2 • SPA-2XCT3/DS0 with T1 channels (Serial interface) • SPA-2XCT3/DS0 without the T1 channels • SPA-2XOC12-POS: 2-port OC12 POS SPA • SPA-2XOC3-POS • SPA-2XOC48POS/RPR • SPA-2XT3/E3 as Serial interface only (not as controller). • SPA-3XOC3-ATM-V2 • SPA-4XOC12-POS: 4-port OC12 POS SPA • SPA-4XOC48POS/RPR • SPA-4XT-Serial • SPA-4XT-Serial as Serial interface only • SPA-5X1GE-V2 • SPA-8X1FE-TX-V2 • SPA-8X1GE-V2 • SPA-8XCHT1/E1 • SPA-8XOC12-POS: 8-port OC12 POS SPA • SPA-8XOC3-POS: 8-port OC3 POS SPA • SPA-DSP • SPA-2X1GE-SYNCE • SPA-1X10GE-WL-V2 • SPA-1CHOC3-CE-ATM • ASR1001-IDC-4XT3 • ASR1001-IDC-2XOC3POS • ASR1001-IDC-HDD • ASR1001-IDC-4XGE • ASR1001-IDC-8XT1E1 • SPA-OC192POS-XFP: 1-port OC192/STM64 POS/RPR XFP Optics SPA • SPA-WMA-K9 : Butler (WebEx) SPA: 1-port WebEx SPA


All the other interface types are not supported for this release. Sensor Alarms are not supported for SPA sensors and transceiver sensors in this release.

For more information on this MIB, refer Appendix A, “CISCO-ENTITY-ALARM-MIB.”

Note The CISCO-ENTITY-ALARM-MIB is supported on the ASR 1001 chassis.

Note Effective from Cisco IOS Release 15.1(3)S, CISCO-ENTITY-ALARM-MIB is supported on SPA-24CHT1-CE-ATM and SPA-2CHT3-CE-ATM.

Note The alarms supported for the POS Ports of the Cisco ASR 1000 Series Routers are also supported for SPA-1X10GE-WL-V2 for the Ethernet WIS port.

Note “Transceiver Missing - Link Down” alarm will be reported with a severity of “CRITICAL” in the CLI output “show facility-alarm status”

Note Effective from Cisco IOS Release 15.3(1)S, CISCO-ENTITY-ALARM-MIB is supported on the Cisco ASR1000: 40G Native Ethernet Line Card and SPA-8XT3/E3.

• SPA-1XOC12-ATM-V2 : 1-port OC12/STM4 ATM Shared Port Adapte

MIB Constraints

Table 3-18 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-ENTITY-ALARM-MIB.

CISCO-ENTITY-ALARM-MIB Constraints

MIB Objects Notes
ceAlarmTable

• ceAlarmFilterProfile
• ceAlarmFilterProfileIndexNext

Not implemented.


Not implemented.

ceAlarmFilterProfileTable Not implemented.
ceAlarmDescrTable


• ceAlarmDescrSeverity

Read only.

The ENTITY-MIB table, entPhysicalTable, identifies the physical system components in the router. The following list describes the table objects that describe the alarms for the CISCO-ENTITY-ALARM-MIB: • Physical entity—The component in the Cisco ASR 1000 Series Routers that generates the alarm. • ceAlarmDescrVendorType—The object specifies an identifier (typically an enterprise-specific OID) that uniquely identifies the vendor type of those physical entities to which this alarm description applies. • Alarm severity—Each alarm type defined by a vendor type and employed by the system is assigned an associated severity: – Critical—Indicates a severe, service-affecting condition has occurred and that immediate corrective action is imperative, regardless of the time of day or day of the week. For example, online insertion and removal or loss of signal failure when a physical port link is down.

Major—Used for hardware or software conditions. Indicates a serious disruption of service or the malfunctioning or failure of important hardware. Requires immediate attention and response of a technician to restore or maintain system stability. The urgency is less than in critical situations because of a lesser effect on service or system performance. – Minor—Used for troubles that do not have a serious effect on service to customers or for alarms in hardware that are not essential to the operation of the system. – Info—Notification about a condition that could lead to an impending problem or notification of an event that improves operation. The syntax values are critical(1), major(2), minor(3), and info(4). • Alarm description text—Specifies a readable message describing the alarm. • Alarm type—Identifies the type of alarm that is generated. An arbitrary integer value (0 through 255) that uniquely identifies an event relative to a physical entity in the Cisco ASR 1000 Series Routers.

Table 3-19 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Router POS ports.

Alarms Supported for Cisco ASR 1000 Series Routers POS Ports

Physical Entity entPhysicalVendorType ceAlarmDescr Severity ceAlarmDescrText
Interface cevPortPOS


cevPortOc3
cevPortOc12
cevPortOc48
cevPortOc192

critical Section Loss of Signal Failure.
critical Section Loss of Frame Failure.
critical Section Out of Frame Alignment.
critical Section J0 mismatch.
critical Section Bit Interleaved Parity.
critical Line Alarm Indication Signal.
critical Line Remote Failure Indication.
critical Line Bit Interleaved Parity.
critical Line Far End Block Errors.
critical Path Alarm Indication Signal.
critical Path Remote Failure Indication.
critical Path Loss of Pointer.
critical Path Bit Interleaved Parity.
critical Path Far End Block Errors.
critical Protection Switch Byte Failure.
critical Path Pointer justifications.
critical Path positive pointer stuff event.
critical Path negative pointer stuff event.
critical Path Payload Label Mismatch.
critical Path payload Unequipped.
critical Count of APS.
critical Receiver Data out of Lock Failure.
critical Signal Failure Alarm.
critical Signal Degrade Alarm.
critical Threshold Cross Alarm - B1.
critical Threshold Cross Alarm - B2.
critical Threshold Cross Alarm - B3.
critical Port Link Down Alarm.
critical Path Trace Identifier Mismatch.
critical Path Trace Identifier Unstable.
minor Signal Failure Alarm/B3 errors.
minor Loss of Multiframe.
critical Loss of Multiframe.
info Port Administrative Down Alarm


Table 3-20 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Router CHOC3-STM1 and CHOC12 ports.

Alarms Supported for Cisco ASR 1000 Series Routers CHOC3-STM1 & CHOC12 Ports

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
Channelized SONET interface cevPortChOc3Stm1/cevPor tChOcX critical Section Loss of Frame Failure.
tChOcX critical Section Out of FrameAlignment.
cevPortChOc3Stm1/cevPortChOcX critical JOMM
cevPortChOc3Stm1/cevPortChOcX critical Section Bit Interleaved Parity.
cevPortChOc3Stm1/cevPortChOcX critical Line Alarm Indication Signal.
cevPortChOc3Stm1/cevPortChOcX critical Line Remote Defect Indication.
cevPortChOc3Stm1/cevPortChOcX critical Line Bit Interleaved Parity.
cevPortChOc3Stm1/cevPortChOcX critical Line Far End Block Errors.
cevPortChOc3Stm1/cevPortChOcX critical Path Alarm Indication Signal.
cevPortChOc3Stm1/cevPortChOcX critical Path Remote Defect Indication.
cevPortChOc3Stm1/cevPortChOcX critical Path Loss of Pointer.
cevPortChOc3Stm1/cevPortChOcX critical Path Bit Interleaved Parity.
cevPortChOc3Stm1/cevPortChOcX critical Path Far End Block Errors.
cevPortChOc3Stm1/cevPortChOcX critical Protection Switch Byte Failure.

cevPortChOc3Stm1/cevPortChOcX

info PNEWPTR
cevPortChOc3Stm1/cevPortChOcX critical Path positive pointer stuffevent.
cevPortChOc3Stm1/cevPortChOcX critical Path negative pointer stuff event.
cevPortChOc3Stm1/cevPortChOcX critical Path Payload Label Mismatch.
cevPortChOc3Stm1/cevPortChOcX critical PUNEQ
cevPortChOc3Stm1/cevPortChOcX critical PTIM
cevPortChOc3Stm1/cevPortChOcX critical PTIU
cevPortChOc3Stm1/cevPortChOcX critical Count of APS.
cevPortChOc3Stm1/cevPortChOcX critical Receiver Data out of LockFailure.
cevPortChOc3Stm1/cevPortChOcX critical Signal Failure Alarm.
cevPortChOc3Stm1/cevPortChOcX critical Signal Degrade Alarm.
cevPortChOc3Stm1/cevPortChOcX critical Signal Failure Alarm – B3.
cevPortChOc3Stm1/cevPortChOcX critical Signal Degrade Alarm – B3.
cevPortChOc3Stm1/cevPortChOcX critical Threshold Cross Alarm - B1.
cevPortChOc3Stm1/cevPortChOcX critical Threshold Cross Alarm - B2.
cevPortChOc3Stm1/cevPortChOcX critical Threshold Cross Alarm - B3.
cevPortChOc3Stm1/cevPortChOcX critical LOM
cevPortChOc3Stm1/cevPortChOcX critical FEPLF
cevPortChOc3Stm1/cevPortChOcX critical MODEMM
cevPortChOc3Stm1/cevPortChOcX critical CHANNELMM


Table 3-21 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers T3/E3 ports. The entries for T3/E3 ports mentioned in this table are always populated for ceAlarmDescrTable and ceAlarmDescrVendorType, irrespective of the presence or absence of the ports.

Alarms Supported for Cisco ASR 1000 Series Routers T3/E3 Ports

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
T3/E3 port cevPortCT3

cevPortT3E3

major Transmitter is sending remote alarm.
major Transmitter is sending AIS.
major Receiver has loss of signal.
major Receiver is receiving AIS.
major Receiver has loss of frame.
major Receiver has remote alarm.
major Receiver has idle signal.
major Other failure.
major DS3 port link down.

info

DS3 port admin down.


Table 3-22 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers T1/E1 ports. The entries for T1/E1 ports mentioned in this table are always populated for ceAlarmDescrTable and ceAlarmDescrVendorType, irrespective of the presence or absence of ports.

Alarms Supported for Cisco ASR 1000 Series Routers T1/E1 Ports

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
T1/E1 port cevPort1E1 minor Transmitter is sending remote alarm.
minor Transmitter is sending AIS.
major Transmitter is sending AIS.
major Receiver is receiving AIS.
minor Transmitter is sending TS16 LOMFAlarm.
minor Receiver has loss of multi-frame in

TS16.

minor Receiver has loss of signal
minor Receiver is getting AIS
minor Receiver has loss of frame
minor Receiver has loss of frame
minor Receiver has loss of frame.
minor Receiver has loss of frame
minor Receiver has remote alarm
minor Receiver is getting AIS in TS16
minor Receiver has remote TS16 LOMF Alarm.
minor Receiver has remote TS16 LOMF Alarm.
minor Other failure
minor Ds1 Physical Port Link Down
info Ds1 Physical Port Administrative

State Down

Table 3-23 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers ATM ports

Alarms Supported for the Cisco ASR 1000 Series Routers GE Ports =

Physical Entity entPhysicalVendorTyp e ceAlarmDescr Severity ceAlarmDescrText
ATM interface cevPortAtm critical Section Loss of Signal Failure
critical Section Loss of Frame Failure
critical Section Out of FrameAlignment
critical Section Bit Interleaved Parity
critical Line Alarm Indication Signal
critical Line Remote Failure Indication
critical Line Bit Interleaved Parity
critical Line Far End Block Errors
critical Path Alarm Indication Signal
critical Path Remote Failure Indication
critical Path Loss of Pointer
critical Path Bit Interleaved Parity
critical Path Far End Block Errors
critical Protection Switch Byte Failure
critical Path Pointer justifications
critical Path positive pointer stuff event
critical Path negative pointer stuffevent
critical Path Payload Label Mismatch
critical Path payload Unequipped
critical Count of APS
critical Receiver Data out of Lock Failure
critical Signal Failure Alarm
critical Signal Degrade Alarm
critical Signal Failure B3 Alarm
critical Signal Degrade B3 Alarm
critical Threshold Cross Alarm - B1
critical Threshold Cross Alarm - B2
critical Threshold Cross Alarm - B3
critical Loss of Multiframe
critical Loss of Cell Delineation
critical Physical Port Link DownAlarm
ATM interface cevPortAtm info Physical Port AdministrativeState Down


Table 3-24 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers over Gigabit Ethernet (GE) ports.

Alarms Supported for the Cisco ASR 1000 Series Routers GE Ports

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
GE port cevPortGE critical Physical port link down.
info Physical Port Administrative

State Down

info Physical port not configured.

Table 3-25 lists the alarm descriptions and severity levels for the WMA Virtual ports in the Cisco ASR 1000 Series Routers.

Alarms Supported for the Cisco ASR 1000 Series Routers WMA Virtual Ports

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
Service Engine interface cevPortSEInternal critical Physical port link down.
info Physical Port Administrative

State Down

Table 3-26 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers SFP Container.

Alarms Supported for the Cisco ASR 1000 Series Routers WMA Virtual Ports

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText Scenario
SFP container cevContainerSFP critical Transceiver missing Physical port link down. When the interface is not using RJ-45 and is in link down state
SFP container cevContainerSFP info Transceiver missing When the interface is configured to use RJ-45 (only applicable to SPA-2X1GE) or is in admin down state.

Table 3-27 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers SPAs.

Alarms Supported for the Cisco ASR 1000 Series Routers SPAs

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
SAP cevSpa10pGeV2 major Unknown state
cevSpa10pGeV2 major Boot state
major Boot state
cevSpa1p10GeXfpV2 major Disabled
cevSpa1pChOc3Stm1 critical Failed
cevSpa1pOc12Pos


cevSpa1pOc192PosRprXfp
cevSpa1pOc48PosSfp
cevSpa2pCT3
cevSpa2pCT3
cevSpa2pGeV2
cevSpa2pGeV2
cevSpa2pOc12Pos
cevSpa2pOc3Atm
cevSpa2pOc3Pos
cevSpa2pOc48PosRprHH
cevSpa2pT3E3Serial
cevSpa24pCt1e1CemAtm
cevSpa2pCt3e3CemAtm
cevSpa4pOc48PosSfp
cevSpa4xoc12Pos
cevSpa4xtSerial
cevSpa5pGeV2
cevSpa5pGeV2
cevSpa8pCT1E1
cevSpa8pCT1E1
cevSpa8pGeV2
cevSpa8pOc12Pos
cevSpa8xfeTxV2
cevSpa8xoc3Pos
cevSpaWmaSw
cevSpa1pOc12Atm
cevSpa1pChoc12Ds0
cevSpaDsp
cevSpa2pGeSynce
cevSpa1x10geWlV2
cevSpa1pChoc3CemAtm

major stopped

Table 3-28 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers sensors.

Alarms Supported for Cisco ASR 1000 Series Routers Sensors

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
Sensor cevSensor critical cevSensor
critical Reading above normal (Shutdown)
critical Reading above normal
major- Reading above normal
minor Reading above normal
critical Readingbelow normal (Shutdown)
critical Reading below normal
major Reading below normal
minor Reading below normal.
Note: These alarms are not supported for SPA and XCVR sensors. You can use

CISCO-ENTITY-SENSOR-MIB to monitor the alarms listed in the Table 3-28.

Table 3-29 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers SPA containers.

Alarms Supported for Cisco ASR 1000 Series Routers SPA Container

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
SPA bay cevContainerSPABay critical Active card removed OIR alarm.
critical Card stopped responding.

Table 3-30 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers USB ports.

Alarms Supported for Cisco ASR 1000 Series Routers USB Ports

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
USB port cevPortUSB critical Active card removed OIR alarm.
critical Card stopped responding.

Table 3-31 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers RP containers.

Alarms Supported for Cisco ASR 1000 Series Routers RP Container

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
RP container cevContainerASR1000RP Slot critical RP removed OIR alarm.
critical RP stopped responding.

Table 3-32 lists the alarm descriptions and severity levels for the Cisco ASR 1001 Series Routers h hard disk containers.

Alarms Supported for the Cisco ASR 1001 Series Router Hard Disk Container

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
hard disk container cevContainerHardDiskSlot major Hard disk missing.

Table 3-33 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers FP containers.

Alarms Supported for Cisco ASR 1000 Series Router FP Container

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
FP container cevContainerASR1000FP Slot critical FP removed OIR alarm
critical FP stopped responding
Note': The Forwarding Processor (FP) does not register to OIR alarm because it is not a FRU entity in the CISCO-ENTITY-ALARM-MIB for ASR1002-F chassis.

Table 3-34 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers SIP containers.

Alarms Supported for Cisco ASR 1000 Series Routers SIP Container

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
SIP container cevContainerASR1000CC

Slot

critical CC removed OIR alarm
critical CC stopped responding.

Table 3-35 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers power supply bay.

Alarms Supported for Cisco ASR 1000 Series Routers Power Supply Bay

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
Power Supply Bay cevContainerASR1000PowerSupplyBay critical Power supply/Fan module missing.

Table 3-36 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers RPs.

Alarms Supported for Cisco ASR 1000 Series Routers RP Module

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
RP Module cevModuleASR1000RP1 major Unknown state.
cevModuleASR1000RP2 major Boot state.
cevModuleASR1002RP1 major Disabled.
critical Incompatible
critical CPLD incompatible
critical Active RP CPLD incompatible
critical Failed.
critical Cutover.
major Secondary failure.
major Secondary removed.
major Secondary not synchronized.
critical No working ESP.
major Harddisk Missing1.
1. Not applicable for cevModuleASR1002RP1.
Note: The Cisco ASR 1002 Router does not have harddisk, so the ‘Harddisk Missing’ alarm is not registered for cevModuleASR1002RP1.

The vendor OID for the RP Module is set to cevModuleASR1000UnknownRP for the following conditions: • The secondary RP is loaded with the valid image and the RP Module is not operational. • The software does not understand the hardware subtype of the secondary RP Module. • The secondary RP is loaded with an invalid image.

Prior to RLS3 release, cevModuleASR1000UnknownRP alarm was registered for all the RP alarms, this behavior is changed from Release 3 and only the Module alarms are registered.

Table 3-37 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers Unknown RP Module.

Alarms Supported for Cisco ASR 1000 Series Routers Unknown RP Modules

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
RP Module cevModuleASR1000Unk

nownRP

major Unknown state.
major Boot state.
major Disabled.
critical Failed.
critical Stopped.

Table 3-38 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers Power Supply Module.

Alarms Supported for Cisco ASR 1000 Series Routers Power Supply Module

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
Power Supply Modules cevPowerSupplyASR100 6AC nownRP critical Power Supply Failure.
critical All Fans Failed.
critical Multiple Fan Failures.
major Fan 0 Failure.
major Fan 1 Failure.
major Fan 2 Failure.
Note: ASR1002 and ASR1002-F have two fans each.

Table 3-39 lists the alarm descriptions and severity levels for the Cisco ASR 1000 Series Routers ESP modules.

Alarms Supported for Cisco ASR 1000 Series Routers ESP/SIP Module

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
ESP Module cevModuleASR1000ESP10 major Unknown state.
cevModuleASR1000SIP10 major Boot State.
cevModuleASR1000ESP5 major Disabled.
cevModuleASR1000ESP20 critical Incompatible
cevModuleASR1002SIP10 critical CPLD incompatible
cevModuleASR1000SIP40 critical Active RP CPLD incompatible
cevModuleASR1000ESP10N critical Failed
major Stopped.

Table 3-40 lists the alarms that the FanTray module of the Cisco ASR 1001 Router support.

Alarms Supported for the Cisco ASR 1001 Series Routers FanTray Module

Physical Entity ceAlarmDescrVendorType ceAlarmDescr Severity ceAlarmDescrText
FanTray

Modules

cevFanASR1001FanTray critical FanTray/Module Failure.
critical All Fans Failed.
critical Multiple Fan Failures.
major Fan 0 failure.
major Fan 1 failure.
major Fan 2 failure.
major Fan 3 failure.
major Fan 4 failure.
major Fan 6 failure.

Note: FanTray is supported on the ASR1001 Router chassis having seven fans and no sensors.


Note: “Transceiver Missing - Link Down” alarm will be reported with a severity of “CRITICAL” in the CLI output “show facility-alarm status”


Note: The ceAlarmHistTable contains alarm data asserted/cleared in the current active RP. It does not retain the alarms asserted/cleared in the previous active RP. The data contained in ceAlarmHistTable is refreshed after a switchover. | |} CISCO-ENTITY-ASSET-MIB | | |The CISCO-ENTITY-ASSET-MIB provides asset tracking information (ceAssetTable) for the physical components in the ENTITY-MIB (RFC 4133) entPhysicalTable. | |The ceAssetTable contains an entry (ceAssetEntry) for each physical component on the router. Each entry provides information about the component. The component information includes:

| |• Orderable part number |• Serial number |• Hardware revision |• Manufacturing assembly number |• Manufacturing revision. |Most physical components are programmed with a standard Cisco-generic ID PROM value that specifies asset information for the component. If possible, the MIB accesses the component’s ID PROM information.

|Note:The ENTITY-MIB (RFC 4133) contains all the objects defined under the CISCO-ENTITY-ASSET-MIB. Thus, you can use the ENTIITY-MIB (RFC 4133) instead of the CISCO-ENTITY-ASSET-MIB

-ENTITY-EXT-MIB

|The CISCO-ENTITY-EXT-MIB contains extensions for the processor modules listed in the ENTITY-MIB entPhysicalTable. A processor module is any physical entity that has a CPU, RAM, and NVRAM, and can load a boot image and save a configuration. The extensions in this MIB provide information such as RAM and NVRAM sizes, configuration register settings, and bootload image name for each processor module. | |Note: Prior to RLS3 release, CPU entity was modeled for CISCO-ENTITY-EXT-MIB. This behavior has now changed and the RP Module entity is modeled for this MIB instead of CPU entity. |Note ASR1000 RP2 supports 64-bit architecture. The ceExtProcessorRam object of CISCO-ENTITY-EXT-MIB supports only 32 bit values. When RP module contains memory more than 4GB, this object returns incorrect value. New objects will be added to provide 64-bit support for this MIB in Release 4. | MIB Constraints

|Only the active RP processor is supported in Cisco ASR 1000 Series Router. The standby RP and SIP processors are not managed in this MIB. | | |Table 3-41 lists the constraints that the router places on the objects in the CISCO-ENTITY-EXT-MIB.

CISCO-ENTITY-EXT-MIB Constraints

MIB Object Notes
ceExtConfigRegNext Read only.
ceExtSysBootImageList Read only.

CISCO-ENTITY-FRU-CONTROL-MIB

The CISCO-ENTITY-FRU-CONTROL-MIB contains objects to configure and monitor the status of the field-replaceable units (FRUs) on the Cisco ASR 1000 Series Routers listed in the ENTITY-MIB entPhysicalTable. A FRU is a hardware component (such as a line card and module, fan, or power supply) that can be replaced on site. This MIB is applicable to Cisco ASR 1000 Series SPA interface processor (SIP) and shared port adapter (SPA) modules for this release.

Note:When RP switchover is caused by the zone failure (when both power supplies in the zone fail) in the active RP. No notification is sent for the modules in the failure zone. The zone failure can be identified by the status of the power supply. P0 and P1 are in one zone, and P2 and P3 are in the other zone.

Note:Effective from Cisco IOS Release 15.1(3)S, CISCO-ENTITY-FRU-CONTROL-MIB is supported on SPA-24CHT1-CE-ATM and SPA-2CHT3-CE-ATM.

Note: Effective from Cisco IOS Release 15.3(1)S, CISCO-ENTITY-FRU-CONTROL-MIB is supported on the Cisco ASR1000: 40G Native Ethernet Line Card and SPA-8XT3/E3. Table 3-41 lists the constraints that the router places on the objects in the CISCO-ENTITY-EXT-MIB.

MIB Constraints

Table 3-42 lists the constraints that the Cisco ASR 1000 Series Router places on the objects in the CISCO-ENTITY-FRU-CONTROL-MIB.

CISCO-ENTITY-FRU-CONTROL-MIB Constraints

MIB Object Notes
• cefcModuleAdminStatus Read only. Always enabled(1) for harddisk and USB.
• cefcModuleOperStatus The following values are supported:

• unknown(1) • ok(2) • boot(5) • failed(7) • dormant(12) • outOfServiceAdmin(13) Always ok(2) for harddisk and USB.

• cefcModuleResetReason Implemented for SPA Modules only.
cefcModuleLastClearConfigTime Not implemented.
• cefcModuleResetReasonDescription Not implemented.
• cefcModuleStateChangeReasonDescr Not implemented.
cefcFRUPowerSupplyGroupTable Not implemented.
cefcFRUPowerSupplyValueTable Not implemented.
cefcFRUPowerStatusTable Not implemented.
cefcFRUPowerAdminStatus

cefcFRUPowerOperStatus

always on(1)

The following values are supported:

• always on(2) • failed(8) • onButFanFail(9)

cefcFanTrayStatusTable

cefFanTrayOperStatus

always up(2)
cefcIntelliModuleTable</B> Not implemented.
cefcPhysicalTable Not implemented.
cefcModuleUpTime Always zero for USB and Harddisk.

| The Cisco ASR 1002 Router behavioral changes for RP, SIP, and SPA 0/0:


• The RP, SIP, and SPA 0/0 are fixed on the Cisco ASR 1002 chassis and CISCO-ENTITY-FRU-CONTROL-MIB does not have entries for these modules. You can use CISCO-ENTITY-ALARM-MIB to monitor these modules. • When the status of these modules is changed, the cefcModuleStatusChange trap is generated with the entity physical status of the module. • When the status of SIP module is changed to down/up, cefcFRURemoved/cefcFRUInserted trap is generated for SPA 0/0 module.

Note:The RP, FP, and SIP can not be removed from the ASR1002-F chassis.

Note:The CISCO-ENTITY-FRU-CONTROL-MIB is supported on the ASR 1001 chassis.

"""CISCO-ENTITY-PERFORMANCE-MIB"""

The CISCO-ENTITY-PERFORMANCE-MIB defines objects to monitor the performance of the Crypto ASIC module of the Extended Service Platform (ESP). Performance monitoring includes utilization of resources and I/O rate for packets and bytes.


MIB Constraints


Table 3-43 lists the constraints that the Cisco ASR 1000 Series Router places on the objects in the CISCO-ENTITY-PERFORMANCE-MIB. These constraints are applicable only for the Crypto ASIC module.

CISCO-ENTITY-PERFORMANCE-MIB Constraints

MIB Object Notes
cepEntityTable Not supported.
cepConfigTable Read only.
• CiscoEntPerfType These MIB object values are supported:

• utilization(1) • packetInputRate(5) – Mapped to Decrypt Packet Rate (DPR.) • packetOutputRate(6) – Mapped to Encrypt Packet Rate (EPR).

cepConfigRisingThreshold Read only.
cepConfigFallingThreshold Read only.
cepConfigThresholdNotifEnabled Read only.
cepEntityIntervalTable Supports performance monitoring every 15 minutes.
cepIntervalStatsTable Supports interval value, fifteenMinutes (3).
cepPerfThreshFallingEvent Not supported.
cepPerfThreshRisingEvent Not supported.
cepThresholdNotifEnabled</> Read only.

Note:The MIB object cepStatsMeasurement is made type Counter64 in order to accommodate maximum values. By definition, Counter 64 does not decrement until it wraps around the maximum value. But, in this case, we have an exception where the cepStatsMeasurement increments or decrements when the value of cepConfigPerfRange is rangePercentage(1).


MCISCO-ENTITY-QFP-MIB

The CISCO-ENTITY-QFP-MIB defines objects to manage Quantum Flow Processors (QFP) listed as entPhysicalClass attribute in the entPhysicalTable of ENTITY-MIB.. The Quantum Flow Processors (QFP) technology control functions such as packet forwarding via fully integrated and programmable networking chipsets. This MIB module contains objects to monitor various QFP statistics such as system state, processor utilization, and memory. The processor utilization statistics comprise these attributes: • Input—Communication channel where packets arrive on the QFP. • Output—Communication channel where packets exit the QFP. • Priority—Indicates that the processing priority for the packet is high. • Non-Priority—Indicates that the processing priority for the packet is low. • Processing Load—Indicates the percentage of time spent forwarding packets.

Note: QFP entities from an inactive or standby FP are not monitored.


Note: For ESP100 or ESP200, the processing load reports the average value for the different CPP subdevs, and for other statistics like pps (packets per second) and bps ( bytes per second), SNMP reports the sum of the individual values for the different CPP subdevs.


MIB Tables

|Table 3-44 lists the tables in CISCO-ENTITY-QFP-MIB.

CISCO-ENTITY-QFP-MIB Tables

MIB Object Description
<b>ceqfpSystemTable Contains the QFP system information for each QFP physical entity.

A separate row is created for each QFP physical entity when a physical entity supporting the QFP system information is detected. If a physical entity supporting the QFP system information is removed, the corresponding row is deleted from the table.

ceqfpUtilizationTable Contains the utilization statistics for each QFP physical entity. A

separate row is created for each QFP physical entity when a physical entity supporting the QFP system information is detected. If a physical entity supporting the QFP system information is removed or the utilization statistics are not received for a specific interval, the corresponding row is deleted from the table. The interval to wait before deleting an entry from this table depends on the supporting device.

<b>ceqfpMemoryResourceTable1 Contains the memory resources statistics for each QFP physical

entity. A separate row is created for each QFP physical entity when a physical entity supporting the QFP system information is detected. If a physical entity supporting the QFP system information is removed or the memory resource statistics are not received for a specific interval, the corresponding row is deleted from the table.

ciscoEntityQfpSystemGroup Contains objects related to QFP system information.
ciscoEntityQfpUtilizationGroup Contains objects related to QFP utilization information.
ciscoEntityQfpMemoryResourceGr oup Contains objects related to QFP memory resource information.
ciscoEntityQfpNotifGroup</> Contains QFP notification such as memory resource crossing threshold.
<b>ciscoEntityQfpMemoryResNotifGro up Contains the QFP memory resource notification control object.
1. The physical DRAM memory resource is logically divided into DRAM and IRAM in the CLI, but the

ceqfpMemoryResourceTable table would show the aggregate of DRAM and IRAM data. The IRAM memory is secondary and is used when DRAM memory is exhausted . The notification is generated whenever the threshold exceeds or subcedes the aggregated value.

MIB Constraints

Table 3-45 lists the constraints that the Cisco ASR 1000 Series Router places on the objects in the CISCO-ENTITY-QFP-MIB.

CISCO-ENTITY-QFP-MIB Constraints

MIB Object Notes
ciscoEntityQfpMemoryResourceGroup

• ceqfpMemoryResRisingThreshold

Read only.
• ceqfpMemoryResFallingThrehold Read only.

CISCO-ENTITY-SENSOR-MIB

The CISCO-ENTITY-SENSOR-MIB contains objects that support the monitoring of sensors. The MIB is applicable to sensors present in various SPA modules and transceiver modules inserted in the SPAs. This MIB allows you to monitor sensor values and thresholds on sensors that are discovered by the ENTITY-MIB.

Note:The CISCO-ENTITY-SENSOR-MIB is supported on the Cisco ASR 1001 chassis.

Note':Effective from Cisco IOS Release 15.1(3)S, the CISCO-ENTITY-SENSOR-MIB is supported on SPA-24CHT1-CE-ATM and SPA-2CHT3-CE-ATM.

Note:Effective from Cisco IOS Release 15.3(1)S, the CISCO-ENTITY-SENSOR-MIB is supported on the Cisco ASR1000: 40G Native Ethernet Line Card and SPA-8XT3/E3.

Note:The CISCO-ENTITY-SENSOR-MIB replaces the CISCO-ENVMON-MIB.

MIB Constraints

Table 3-46 lists the constraints that the Cisco ASR 1000 Series Router places on the CISCO-ENTITY-SENSOR-MIB.

CISCO-ENTITY-SENSOR-MIB Constraints

MIB Object Notes
• entSensorMeasuredEntity Implemented for all sensors except for SPA and transceiver sensors.
•entSensorThresholdRelation


• entSensorThresholdSeverity>
entSensorThresholdValue

Read only.


Read only.
Read only.

Note:The MIB object entSensorThresholdEvaluation for SPA module is not supported, as the SPA sensor monitoring is not supported and the sensor value is updated only on demand. Hence for SPA sensors, you can compare the entSensorValue retrieved from the agent with thresholds to obtain the entSensorThresholdEvaluation.

MIB Usage Values for Cisco Transceivers

The table in this section lists each type of sensor’s value represented in the entSensorValueTable and the entSensorThresholdTable.

Table 3-47 lists CISCO-ENTITY-SENSOR-MIB sensor objects and their usage values for Cisco ASR 1000 Series Routers transceivers in the entSensorValueTable.

== CISCO-ENTITY-SENSOR-MIB Usage Values in the entSensorValueTable for Cisco Transceivers ==

MIB Sensor Object Notes
Module Temperature Sensor


• entSensorType
• entSensorScale</B
• entSensorThresholdSeverity>
• entSensorPrecision
• entSensorStatus
• entSensorValue
• entSensorValueTimeStamp
• entSensorValueUpdateRate

celsius(8)


units(9).
3 ok(1)
Reports most recent measurement seen by the sensor.
Value indicates the age of the value reported by entSensorValue object.
Value indicates the rate that the agent updates
entSensorValue in seconds (for example, 60 seconds).

Tx Supply Voltage Sensor


•entSensorType
• entSensorScale
• entSensorPrecision
• entSensorStatus
•entSensorValue
•ntSensorValueTimeStamp
•entSensorValueUpdateRate

voltsDC(4)


milli(8)
ok(1)
Reports most recent measurement seen by the sensor.
Value indicates the age of the value reported by entSensorValue object.
•Value indicates the rate that the agent updates entSensorValue in seconds (for example, 60 seconds).

Tx Laser Current Sensor


• entSensorType
•entSensorScale
• entSensorPrecision
•entSensorStatus
•entSensorValue
•entSensorValueTimeStamp
• entSensorValueUpdateRate

amperes(5)


milli(8)
0
Reports most recent measurement seen by the sensor.
Value indicates the age of the value reported by entSensorValue object.
Value indicates the rate that the agent updates entSensorValue in seconds (for example, 60 seconds).

Transmit Power Sensor (Optical Tx)Receive Power Sensor (Optical Rx)


• entSensorType
• entSensorScale
• entSensorPrecision
• entSensorStatus
• entSensorValue
• entSensorValueTimeStamp entSensorValue object.

• entSensorValueUpdateRate


Value indicates the age of the value reported by
dBm(14)

units(9)
|0
ok(1)
Reports most recent measurement seen by the sensor.
Value indicates the rate that the agent updates entSensorValue in seconds (for example, 60 seconds). Note:The RPs, FPs, SIPs, and power supplies support various sensors. These sensors are supported in the CISCO-ENTITY-SENSOR-MIB.

Table 3-48 lists the constraint that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-ETHERLIKE-EXT-MIB.

CISCO-ETHERLIKE-EXT-MIB Constraint

MIB Object Notes
<b>ceeDot3PauseExtTable Not supported.

CISCO-EVC-MIB The CISCO-EVC-MIB defines the managed objects and notifications describing Ethernet Virtual Connections (EVCs)..

MIB Constraint

Table 3-49 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-EVC-MIB.

CISCO-EVC-MIB Constraint

MIB Object Notes
cevcEvcUniTable Not supported.
cevcEvcActiveUnis Not supported.
ciscoEvcStatusChangedNotification Not supported.
• cevcEvcOperStatus Returns unknown as value.


CISCO-FLASH-MIB

The CISCO-FLASH-MIB contains objects to manage flash cards and flash-card operations.

MIB Constraint

Table 3-50 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-FLASH-MIB.

CISCO-EVC-MIB Constraint

MIB Object Notes
ciscoFlashDeviceTable


• ciscoFlashDeviceInitTime

Not Implemented.
• ciscoFlashPhyEntIndex Not Implemented.
ciscoFlashPartitionTable


• ciscoFlashPartitionFileCount
• ciscoFlashPartitionChecksumAlgorithm
• ciscoFlashPartitionUpgradeMethod
• ciscoFlashPartitionNeedErasure
• ciscoFlashPartitionFileNameLength

Not Implemented.


Not Implemented.
Not Implemented.
Not Implemented.
Not Implemented.

ciscoFlashFileTable


• ciscoFlashFileChecksum
• ciscoFlashFileType

Not Implemented.


Values not supported:
config(2)
image(3)
crashinfo(5)

Note:The index of files stored in USB changes frequently since the files are mounted and unmounted after regular intervals.

Note:When both primary and secondary RPs are up and running, entities for standby usb flash and Flash disk are not populated for CISCO-FLASH-MIB. Compact Flash is not supported in ASR series Routers. So, it wont be modelled in CISCO-FLASH-MIB. Once the file is copied successfully via tftp, it takes atleast 50 secs to reflect the correct file size in ciscoFlashFileSize object.

Note:The Cisco ASR 1006 Router does not identify the flash device until it is inserted the first time. The MIB object CiscoFlashDevicesSupported shows its value as 1 till the device is inserted or after router reload, and changes to 2 after the device is inserted. After the flash device is removed, the CiscoFlashDevicesSupported value will still hold 2 as this object indicates the number of the Flash Devices 'Supported by the Router' as per the MIB definition.

CISCO-FRAME-RELAY-MIB

The CISCO-FRAME-RELAY-MIB contains Frame Relay information that is specific to Cisco products or that is missing from RFC 1315.

MIB Constraints

Table 3-51 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-FRAME-RELAY-MIB. Objects that are not listed in the table are implemented as defined in the MIB.

Note:Frame Relay Switched Virtual Circuits (SVCs) are not currently supported in Cisco ASR 1000 Series Routers.

CISCO-FRAME-RELAY-MIB Constraints

MIB Object Notes
cfrCircuitTable


• cfrCircuitType

Supported value is pvc(1).
cfrExtCircuitTable


• cfrExtCircuitMinThroughputOut
• cfrExtCircuitMinThroughputIn
• cfrExtCircuitShapeByteLimit
• cfrExtCircuithapeInterval
• cfrExtCircuitShapeByteIncrement
• cfrExtCircuitShapeActive
• cfrExtCircuitShapeAdapting

Supported for QoS. Otherwise value is 0.


Supported for QoS. Otherwise value is 0.
Supported for QoS. Otherwise value is 0.
Supported for QoS. Otherwise value is 0.
Supported for QoS. Otherwise value is 0.
Supported for QoS. Otherwise value is 0.
Supported for QoS. Otherwise value is 0.

cfrMapTable

• cfrMapType

Values are:


• static(1)
• dynamic(2)
Not Implemented.

CISCO-FTP-CLIENT-MIB

The CISCO-FTP-CLIENT-MIB contains objects to invoke File Transfer Protocol (FTP) operations for network management. This MIB has no known constraints and all objects are implemented as defined in the MIB.

CISCO-HSRP-EXT-MIB

The CISCO-HSRP-EXT-MIB provides an extension to the CISCO-HSRP-MIB which defines the Cisco Hot Standby Router Protocol (HSRP), which is defined in RFC 2281. The extensions cover assigning of secondary IP addresses and modifying an HSRP group’s priority.

CISCO-HSRP-MIB

The CISCO-HSRP-MIB contains objects to configure and manage the Cisco Hot Standby Router Protocol (HSRP), which is defined in RFC 2281.

CISCO-IETF-ATM2-PVCTRAP-MIB

The CISCO-IETF-ATM2-PVCTRAP-MIB contains objects that supplement the ATM-MIB. This MIB implements the Virtual Channel Link (VCL) section of the IETF document "draft-ietf-atommib-atm2-11.txt," Section 9 ATM Related Trap Support.

Note:This MIB is currently not supported for broadband configurations.

CISCO-IETF-BFD-MIB

The CISCO-IETF-BFD-MIB contains managed object definitions for the Bidirectional Forwarding Detection (BFD) Protocol. BFD is a protocol that detects faults in the bidirectional path between two forwarding engines, including interfaces, data links, and to the extent possible, the forwarding engines themselves, with potentially very low latency. It operates independently of media, data protocols, and routing protocols.

Note:The CISCO-IETF-BFD-MIB is based on the draft-ietf-bfd-mib-07.txt internet draft. Following is the support information on the Virtual Routing and Forwarding (VRF) context for the MIB:

• The CISCO-IETF-BFD-MIB supports IPv4 and IPv6 in the non-VRF context. • The CISCO-IETF-BFD-MIB supports IPv4 in the VRF context, and does not support IPv6 in theVRF context.

CISCO-IETF-FRR-MIB The CISCO-IETF-FRR-MIB contains managed object definitions for MPLS Fast Reroute (FRR).

CISCO-IETF-ISIS-MIB

The CISCO-IETF-ISIS-MIB introduces network management support for the IS-IS routing protocol through the use of IS-IS MIB table entries, MIB objects, and MIB trap notification objects. A new CLI is added to enable SNMP notifications for the objects. Notifications are provided for errors and other significant event information for the IS-IS network.

CISCO-IETF-NAT-MIB

The CISCO-IETF-NAT-MIB contains objects for Network Address Translation (NAT) operations on the router, as defined in RFC 3022. The MIB inclued objects containing NAT configuration, NAT bindings, and run-time statistics. |The MODULE-IDENTITY for the CISCO-IETF-NAT-MIB is ciscoIetfNatMIB, and its top-level OID is 1.3.6.1.4.1.9.10.77 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscoIetfNatMIB).

CISCO-IETF-PPVPN-MPLS-VPN-MIB

The CISCO-IETF-PPVPN-MPLS-VPN-MIB is an extension of the MPLS-VPN-MIB. It contains a new notification, mplsNumVrfRouteMaxThreshCleared, which was added with MPLS-VPN-MIB-DRAFT-05.


CISCO-IETF-PW-ATM-MIB

The CISCO-IETF-PW-ATM-MIB contains managed object definitions for Pseudo Wire (PW) emulation of ATM over Packet Switched Networks (PSN).

Note:Effective from Cisco IOS Release 15.1(3)S, CISCO-IETF-PW-ATM-MIB is supported on SPA-2CHT3-CE-ATM.

MIB Constraints

Table 3-52 lists the constraints that the Cisco ASR 1000 Series Router places on the objects in the CISCO-IETF-PW-ATM-MIB.

Note:Frame Relay Switched Virtual Circuits (SVCs) are not currently supported in Cisco ASR 1000 Series Routers.

CISCO-IETF-PW-ATM-MIB Constraints

MIB Object Notes
CpwVcAtmPerfEntry


• cpwAtmCellsReceived
• cpwAtmCellsSent
• cpwAtmCellsRejected
• cpwAtmCellsTagged
• cpwAtmHCCellsReceived

• cpwAtmHCCellsRejected
• cpwAtmHCCellsTagged
• cpwAtmAvgCellsPacked

Not supported, returns zero.


Not supported, returns zero.
Not supported, returns zero.
Not supported, returns zero.
Not supported, returns zero.
Not supported, returns zero.
Not supported, returns zero.
Not supported, returns zero.

CISCO-IETF-PW-ENET-MIB

The CISCO-IETF-PW-ENET-MIB contains objects that describe the model for managing Ethernet point-to-point pseudo wire services over a Packet Switched Network (PSN).

MIB Constraints

Table 3-53 lists the constraints that the Cisco ASR 1000 Series Router place on the objects in the CISCO-IETF-PW-ENET-MIB.

CISCO-IETF-PW-ENET-MIB Constraints

MIB Object Notes
cpwVcEnetMplsPriMappingTable


• ciscoFlashDeviceInitTime

Not supported.

CISCO-IETF-PW-FR-MIB

The CISCO-IETF-PW-FR-MIB contains the network management objects defined for FRoPW services over a PSN.

CISCO-IETF-PW-MIB

The CISCO-IETF-PW-MIB contains managed object definitions for PW operation.

Note:Effective from Cisco IOS Release 15.1(3)S, the CISCO-IETF-PW-MIB is supported on the SPA-24CHT1-CE-ATM and SPA-2CHT3-CE-ATM.

""MIB Constraints""

Table 3-54 lists the constraints that the Cisco ASR 1000 Series Router places on the objects in the CISCO-IETF-PW-MIB.

CCISCO-IETF-PW-MIB Constraints

MIB Object Notes
cpwVcTable


• CpwVcEntry
• cpwVcIndex
• cpwVcType
• cpwVcOwner
• cpwVcPsnType
• cpwVcSetUpPriority
• cpwVcHoldingPriority
• cpwVcInboundMode
• cpwVcPeerAddrType
• cpwVcPeerAddr
• cpwVcID
• cpwVcLocalGroupID
• cpwVcControlWord
• cpwVcLocalIfMtu
• cpwVcRemoteControlWord
• cpwVcOutboundVcLabel
• cpwVcInboundVcLabel
• cpwVcName
• cpwVcDescr
• cpwVcAdminStatus
• cpwVcTimeElapsed
• cpwVcRowStatus
cpwVcStorageType

Not-accessible.


Not-accessible.
Read only.
Read only.
Read only.
Not implemented.
Not implemented.
Read only.
Read only.
Read only.
Read only.
Read only.
Read only.
Read only.
Read only.
Read only.
Read only.
Read only.
Read only.
Read only.
Not implemented.
Read only.
Read only.

cpwVcPerfCurrentTable


• cpwVcPerfCurrentEntry
• cpwVcPerfCurrentInHCPackets
• cpwVcPerfCurrentInHCBytes
• cpwVcPerfCurrentOutHCBytes
• cpwVcPerfCurrentOutHCPackets

Not implemented.


Not implemented.
Not implemented.
Not implemented.

cpwVcPerfIntervalTable


cpwVcPerfIntervalEntry
• cpwVcPerfIntervalNumber
• cpwVcPerfIntervalValidData
• cpwVcPerfIntervalInHCPackets
• cpwVcPerfIntervalInHCBytes
• cpwVcPerfIntervalOutHCPackets
• cpwVcPerfIntervalOutHCBytes


Not implemented.


Not implemented.
Not implemented.
Not implemented.
Not implemented.
Not implemented.
Not implemented.
Not implemented.
Not implemented.

cpwVcNotifRate Not implemented.

CISCO-IETF-PW-MPLS-MIB

The CISCO-IETF-PW-MPLS-MIB contains objects that complement the CISCO-IETF-PW-MIB for PW operation over MPLS.

Effective from Cisco IOS Release 15.1(3)S, the CISCO-IETF-PW-MPLS-MIB is supported on the SPA-24CHT1-CE-ATM and SPA-2CHT3-CE-ATM.

MIB Constraints Table 3-55 lists the constraints that the Cisco ASR 1000 Series Router places on the objects in the CISCO-IETF-PW-MPLS-MIB.

CISCO-IETF-PW-MPLS-MIB Constraints

MIB Object Notes
cpwVcMplsOutboundIndexNext Not supported.
cpwVcMplsInboundIndexNext Not supported.

CISCO-IETF-PW-TDM-MIB

The CISCO-IETF-PW-TDM-MIB contains managed object definitions for encapsulating TDM (T1,E1, T3, E3, NxDS0) as pseudo-wires over packet-switching networks (PSN). The SPA-1XOC3-ATM-V2 and SPA-3XOC3-ATM-V2 do not support CEM (Circuit Emulation). Therefore. this MIB is not supported for these hardware.

CISCO-IF-EXTENSION-MIB

The CISCO-IF-EXTENSION-MIB contains objects that provide additional interface-related information that is not available in the IF-MIB (RFC 2863).

Note:Effective from Cisco IOS Release 15.1(3)S, CISCO-IF-EXTENSION-MIB is supported on SPA-24CHT1-CE-ATM and SPA-2CHT3-CE-ATM.

Note:Effective from Cisco IOS Release 15.3(1)S, the CISCO-IF-EXTENSION-MIB is supported on the Cisco ASR1000: 40G Native Ethernet Line Card and SPA-8XT3/E3.


MIB Constraints Table 3-56 lists constraints that the Cisco ASR 1000 Series Router places on the object in CISCO-IF-EXTENSION-MIB

CISCO-IF-EXTENSION-MIB Constraints

MIB Object Notes
cielInterfaceTable


• cieIfDhcpMode
• cieIfMtu
• cieIfContextName
• cieIfKeepAliveEnabled

Not implemented.


Not implemented.
Not implemented.
Not implemented. Not supported for ATM interfaces.

cieSystemMtu Not implemented.
cieIfUtilTable Not supported for SPA GE interfaces.
cieIfDot1dBaseMappingTable Not implemented.
cieIfDot1qCustomEtherTypeTable Not implemented.
cieIfNameMappingTable Not implemented.
Notes Some objects defined in cieIfPacketStatsTable and cieIfInterfaceTable are applicable to physical interfaces

only. As a result, this table may be sparse for non-physical interfaces. ATM interfaces do not support the cieIfKeepAliveEnabled object.

CISCO-IGMP-FILTER-MIB

The CISCO_IGMP-FILTER-MIB provides a mechanism for users to configure the system to intercept Internet Group Management Protocol (IGMP) joins for IP Multicast groups identified in this MIB and only allow certain ports to join certain multicast groups.

CISCO-IMAGE-MIB

The CISCO-IMAGE-MIB contains objects that identify the capabilities and characteristics of the Cisco IOS image.

CISCO-IMAGE-LICENSE-MGMT-MIB

The CISCO-IMAGE-LICENSE-MGMT-MIB contains objects to control the management level of the IOS image on a device. Cisco licensing mechanism provides flexibility to run a device at different image levels. This mechanism is referred to as image-level licensing. Image-level licensing leverages the universal image-based licensing solution. A universal image containing all levels of a software package is loaded on to the device. During startup, the device determines the highest level of license and loads the corresponding software features or subsystems.

CISCO-IP-LOCAL-POOL-MIB

The CISCO-IP-LOCAL-POOL-MIB contains objects that provide a network manager with information related to the local IP address pools. This MIB provides configuration and statistics reflecting the allocation of local IP pools. Each entry provides information about a particular local IP pool, including the number of free and used addresses. The SNMP agent does not have to be configured in any special way for CISCO-IP-LOCAL-POOL-MIB objects to be available to the network management system. You can configure the SNMP agent to send the ciscoIpLocalPoolInUseAddrNoti notification to a particular host using the snmp-server host ip-address community-name iplocalpool command. The ciscoIpLocalPoolInUseAddrNoti notification is enabled:

|• Through SNMP by using the cIpLocalPoolNotificationsEnable object |• Using the snmp-server enable traps ip local pool CLI configuration

CISCO-IPMROUTE-MIB

The CISCO-IPMROUTE-MIB contains objects to manage IP multicast routing on the router.

CISCO-IPSEC-FLOW-MONITOR-MIB

The CISCO-IPSEC-FLOW-MONITOR-MIB allows monitoring of the structures in IPsec-based virtual private networks.

CISCO-IPSEC-MIB

The CISCO-IPSEC-MIB models the Cisco implementation-specific attributes of a Cisco entity that implements IPsec.

CISCO-IPSEC-POLICY-MAP-MIB

The CISCO-IPSEC-POLICY-MAP-MIB contains objects that supplement the proposed IETF standards for IPsec VPNs. In particular, this MIB maps dynamically instantiated IPsec protocol structures (such as tunnels and security associations) to the policy entities that created them (such as policy definitions, crypto maps, and transforms). The MODULE-IDENTITY for the CISCO-IPSEC-POLICY-MAP-MIB is ciscoIpSecPolMapMIB, and its top-level OID is 1.3.6.1.4.1.9.9.172 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoIpSecPolMapMIB).

MIB Constraints This MIB is supported only in Cisco IOS software images that support DES encryption (-k8- or -k9-).

CISCO-IP-TAP-MIB The CISCO-IP-TAP-MIB manages Cisco intercept feature for IP. This MIB is used along with CISCO-TAP2-MIB to intercept IP traffic.

CISCO-IP-URPF-MIB

The CISCO-IP-URPF-MIBcontains objects that allow users to specify a Unicast Reverse Path Forwarding (URPF) drop-rate threshold on interfaces of a managed device, which when exceeded, a SNMP notification is sent. It includes objects specifying global (to a managed device as a whole) and per-interface drop counts and drop rates, and also generates traps based on the drop rate exceeding a configureable per-interface threshold.

MIB Constraints


CISCO-PRODUCTS-MIB

The CISCO-PRODUCTS-MIB lists the object identifiers (OIDs) assigned to the Cisco hardware platforms. CISCO ASR1006, ASR1004, ASR1002, ASR1002-F, ASR1001, and ASR1013 OIDs are supported.

CISCO-QINQ-VLAN-MIB

The CISCO-QINQ-VLAN-MIB describes configuration and monitoring capabilities relating to 802.1QinQ interfaces.

MIB Constraints


Table 3-57 lists the constraints that Cisco ASR 1000 Series Router places on the CISCO-IP-URPF-MIB.

CISCO-IP-URPF-MIB Constraints

MIB Object Notes
cipUrpfIfMonTable Entries in this tables are present when URPF is

enabled on an interface. They are not available when the interface is removed or if RPF is disabled on the interface.

cipUrpfIfConfTable Entries in this tables are present when URPF is

enabled on an interface. They are not available when the interface is removed or if RPF is disabled on the interface.

CISCO-LAG-MIB

The CISCO-LAG-MIB contains objects to manage link aggregation (LAG) on the router, as defined by IEEE Standard 802.3ad. The MIB contains link aggregation information that supplements to IEEE8023-LAG-MIB or is specific to Cisco products.


CISCO-LICENSE-MGMT-MIB

The CISCO-LICENSE-MGMT-MIB contains objects to manage the licenses on a system. The licensing mechanism provides flexibility to enforce licensing for various features in the system. These are the different kinds of licenses:

• NODE LOCKED LICENSE • NON-NODE LOCKED LICENSE • METERED LICENSE • EVALUATION LICENSE • RIGHT TO USE (RTU) LICENSE • EXTENSION LICENSE • GRACE PERIOD LICENSE • COUNTED LICENSE • UNCOUNTED LICENSE • IMAGE LEVEL LICENSING • FEATURE LEVEL LICENSING

CISCO-MVPN-MIB

The CISCO-MVPN-MIB contains managed object definitions for the Cisco implementation of multicast in VPNs defined by the Internet draft, draft-rosen-vpn-mcast-05.txt. The Multicast VPN MIB feature introduces the capability for Simple Network Management Protocol (SNMP) monitoring of a Multicast VPN (MVPN). Using the MVPN MIB, network administrators can access MVRF information from PE routers. This information can be accessed for VPN traffic across multiple CE sites in real time. SNMP operations can be performed to monitor the MVRFs on the PE routers, using the get and set commands. These commands are entered on the Network management system (NMS) workstation for which the SNMP has been implemented. The NMS workstations is also known as the SNMP manager.

Note Currently only IPv4 is supported.

Note For all MIB objects with "read-create" access privileges, currently only "read-only" access is supported. For more information on this MIB, please access the following link:

https://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/mcvpnmib.html3

CISCO-NBAR-PROTOCOL-DISCOVERY-MIB

The CISCO-NBAR-PROTOCOL-DISCOVERY-MIB provides SNMP support for Network-Based Application Recognition (NBAR), including enabling and disabling protocol discovery on a per-interface basis, and configuring the traps that are generated when certain events occur. You can also display the current NBAR configuration and run-time statistics.

Note: The MODULE-IDENTITY for the CISCO-NBAR-PROTOCOL-DISCOVERY-MIB is ciscoNbarProtocolDiscoveryMIB, and its top-level OID is 1.3.6.1.4.1.9.9.244 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoNbarProtocolDiscoveryMIB).

Note: The cnpdTopNConfigTable and cnpdTopNStatsTable tables do not have details for the protocol "unknown".

CISCO-NETFLOW-MIB

The CISCO-NETFLOW-MIB provides a simple and easy method to get NetFlow cache information, the current NetFlow configuration, and statistics.

MIB Constraints'

Table 3-58 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-NETFLOW-MIB.

CISCO-NETFLOW-MIB Constraints

MIB Object Notes
cnfCICacheEnable The following values are not supported:


• destinationOnly(6)
• sourceDestination(7)
• fullFlow(8)
• expBgpPrefix(23)

CISCO-NTP-MIB

The CISCO-NTP-MIB contains objects to monitor a Network Time Protocol (NTP) server. NTP is used to synchronize timekeeping among a set of distributed time servers and clients. Primary time servers, which are synchronized to national time standards, are connected to widely accessible resources such as backbone gateways. These primary servers send timekeeping information to other time servers, and perform clock checking to eliminate timekeeping errors due to equipment or propagation failures.

MIB Constraints

Table 3-59 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-NTP-MIB.

CISCO-NTP-MIB Constraints

MIB Object Notes
cntpSysLeap Read only.
cntpSysStratum Read only.

CISCO-OSPF-MIB

The CISCO-OSPF-MIB contains objects for managing OSPF implementation. Most of the MIB definitions are based on the IETF draft draft-ietf-ospf-mib-update-05.txt and include support for OSPF Sham link. The CISCO-OSPF-MIB is an extension to the OSPF-MIB defined in RFC 1850.

CISCO-OSPF-TRAP-MIB

The CISCO-OSPF-TRAP-MIB contains new and modified notification objects and events, which are defined in the latest version for OSPF-MIB IETF draft draftietf-ospf-mib-update-05.txt in addition to support for OSPF Sham link.

CISCO-PIM-MIB

The CISCO-PIM-MIB defines Cisco-specific objects and variables for managing Protocol Independent Multicast (PIM) on the router. These MIB definitions are an extension of those in RFC 2934, which is the IETF PIM MIB.

CISCO-PING-MIB The CISCO-PING-MIB contains objects to manage ping requests on the router.

CISCO-PPPOE-MIB

The CISCO-PPPOE-MIB contains objects to manage Point-to-Point Protocol over Ethernet (PPPoE) sessions. These objects represent PPPoE sessions at the system and virtual channel (VC) level.

MIB Constraints

Table 3-60 lists the constraints that the Cisco ASR 1000 Series Router places on the objects in the CISCO-PPPOE-MIB.

CISCO-PPPOE-MIB Constraints

MIB Object Notes
cPppoeSystemMaxAllowedSessions Read only.
cPppoeSystemThresholdSessions Read only.
cPppoeVcCfgTable


• cPppoeVcEnable

Read only.
cPppoeVcSessionsTable

• cPppoeVcMaxAllowedSessions • cPppoeVcExceededSessionErrors

Read only


Read only.

CISCO-PROCESS-MIB

The CISCO-PROCESS-MIB displays memory and CPU usage on the router and describes active system processes. CPU utilization presents a status of how busy the system is. The numbers are a ratio of the current idle time over the longest idle time. (This information should be used as an estimate only)

MIB Constraints

Table 3-61 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-PROCESS-MIB.

CISCO-PROCESS-MIB Constraints

MIB Object Notes
cpmProcessTable


• cpmProcExtPriority

Read only.
cpmCPURisingThreshold Not Supported
cpmCPUFallingThreshold Not Supported

NoteThe Cisco ASR1000 RP2 supports 64-bit architecture. Effective from Cisco IOS Release 15.2(4)S onwards, the CISCO-PROCESS-MIB supports 64-bit architecture.

Note The RP2 contains 2 physical CPUs, but the CPUs are not monitored separately. The monitoring the CPU utilization is the aggregate result of both the CPUs. Hence, the cpmCPUTotalTable object contains only one entry for RP CPUs.

Effective from Cisco IOS Release 15.4(2)S, the object cpmCPUTotalIndex does not change with the RP, ESP, or CC reboot, and remains persistent across reloads. CISCO-PROCESS-MIB Usage

The cpmCPUTotal5sec, cpmCPUTotal1min, and cpmCPUTotal5min objects have been deprecated and replaced by cpmCPUTotal5secRev, cpmCPUTotal1minRev, and cpmCPUTotal5minRev, respectively. Note When an object is deprecated, it does not mean that an object instance may not be returned. For these deprecated objects, object instances are returned. However, their returned values must be ignored. The values returned by the new objects must be used.

Note The cpmVirtualProcessTable is not populated on ESP since the IOS daemon is not running on ESP.

Note The CPU utilization objects such as cpmCPUTotal5sec, cpmCPUTotal1min, and cpmCPUTotal5min are calculated for all the processes used by CPU except under idle condition.

Table 3-62 lists the support matrix for the CISCO-PROCESS-MIB cpmCPUTotalTable object.

Support-Matrix for cpmCPUTotalTable

cpmCPUTotalTable Objects RP CPU Stdby RP CPU CC CPU ESP CPU Stdby ESP CPU
cpmCPULoadAvg1min Yes No Yes Yes No
cpmCPULoadAvg5min Yes No Yes Yes No
cpmCPULoadAvg15min Yes No Yes Yes No
cpmCPUMemoryCommitted Yes No Yes Yes No
cpmCPUTotalPhysicalIndex Yes No Yes Yes No
cpmCPUTotal5sec Yes No Yes Yes No
cpmCPUTotal1min Yes No Yes Yes No
cpmCPUTotal5min Yes No Yes Yes No
cpmCPUTotal5secRev Yes No Yes Yes No
cpmCPUTotal1minRev Yes No Yes Yes No
cpmCPUTotal5minRev Yes No Yes Yes No
cpmCPUMonInterval No No No No No
cpmCPUTotalMonIntervalValue No No No No No
cpmCPUInterruptMonIntervalValue No No No No No
cpmCPUMemoryUsed Yes No Yes Yes No
cpmCPUMemoryFree Yes No Yes Yes No
cpmCPUMemoryKernelReserved No No No No No
cpmCPUMemoryLowest Yes No Yes Yes No

Table 3-63 lists the support matrix for cpmProcessTable and cpmProcessExtRevTable for ESP CPU.

Support Matrix for cpmProcessTable and cpmProcessExtRevTable for ESP CPU

cpmProcessTable and cpmProcessExtRevTable Objects Processes[Process Name: cman_fp, fman_fp_image, hman ]
cpmProcessPID Yes
cpmProcessName Yes
cpmProcessuSecs No
cpmProcessTimeCreated Yes
cpmProcessAverageUSecs Yes
cpmProcExtMemAllocatedRev Yes
cpmProcExtMemFreedRev No
cpmProcExtInvokedRev No
cpmProcExtRuntimeRev No
cpmProcExtUtil5SecRev No
cpmProcExtUtil1MinRev No
cpmProcExtUtil5MinRev No
cpmProcExtPriorityRev Yes
cpmProcessType No
cpmProcessRespawn No
cpmProcessRespawnCount No
cpmProcessRespawnAfterLastPatch No
cpmProcessMemoryCore No
cpmProcessLastRestartUser No
cpmProcessTextSegmentSize No
cpmProcessDataSegmentSize No
cpmProcessStackSize No
cpmProcessDynamicMemorySize No

Table 3-64 lists the support matrix for the CISCO-PROCESS-MIB cpmProcessTable and cpmProcessExtRevTable objects for RP CPU.

Support Matrix for the cpmProcessTable and the cpmProcessRevExtTable for RP CPU

cpmProcessTable and cpmProcessRevExtTable Objects IOSD Process [Process Name: ppc_linux_iosd-] Other Process [Process Name: Cmand, hman, imand]
cpmProcessName Yes Yes
cpmProcessuSecs No No
cpmProcessTimeCreated Yes Yes
cpmProcessAverageUSecs Yes Yes
cpmProcExtMemAllocatedRev Yes Yes
cpmProcExtMemFreedRev No No
cpmProcExtInvokedRev No No
cpmProcExtRuntimeRev No No
cpmProcExtUtil5SecRev No No
cpmProcExtUtil1MinRev No No
cpmProcExtUtil5MinRev No No
cpmProcExtPriorityRev Yes Yes
cpmProcessType No No
cpmProcessRespawn No No
cpmProcessRespawnCount No No
cpmProcessRespawnAfterLastPatch No No
cpmProcessMemoryCore No No
cpmProcessLastRestartUser No No
cpmProcessTextSegmentSize No No
cpmProcessDataSegmentSize No No
cpmProcessStackSize No No
cpmProcessDynamicMemorySize No No


Table 3-65 lists the support matrix for the CISCO-PROCESS-MIB cpmProcessTable and cpmProcessExtRevTable objects for CC CPU.


Support Matrix for the cpmProcessTable and the cpmProcessExtRevTable for CC CPU

cpmProcessTable & cpmProcessExtRevTable Objects SPA IOS Process Other Process [Process Name: cmcc, hman, imccd]
cpmProcessName Yes Yes
cpmProcessuSecs No No
cpmProcessTimeCreated Yes Yes
cpmProcessAverageUSecs Yes Yes
cpmProcExtMemAllocatedRev Yes Yes
cpmProcExtMemFreedRev No No
cpmProcExtInvokedRev No No
cpmProcExtRuntimeRev No No
cpmProcExtUtil5SecRev No No
cpmProcExtUtil1MinRev No No
cpmProcExtUtil5MinRev No No
cpmProcExtPriorityRev Yes Yes
cpmProcessType No No
cpmProcessRespawn No No
cpmProcessRespawnCount No No
cpmProcessRespawnAfterLastPatch No No
cpmProcessMemoryCore No No
cpmProcessLastRestartUser No No
cpmProcessTextSegmentSize No No
cpmProcessDataSegmentSize No No
cpmProcessStackSize No No
cpmProcessDynamicMemorySize No No


Table 3-66 lists the support matrix for the CISCO-PROCESS-MIB cpmVirtualProcessTable object.

Support Matrix for the cpmVirtualProcessTable

cpmVirtualProcessTable Objects Process running under Active RP IOSD Process Process running under CC SPA IOS Process
cpmVirtualProcessName Yes Yes
cpmVirtualProcessUtil5Sec Yes Yes
cpmVirtualProcessUtil1Min Yes Yes
cpmVirtualProcessUtil5Min Yes Yes
cpmVirtualProcessMemAllocated Yes Yes
cpmVirtualProcessMemFreed Yes Yes
cpmVirtualProcessInvokeCount Yes Yes
cpmVirtualProcessRuntime Yes Yes

Table 3-67 lists the threshold values for committed memory.

Threshold Values for Committed Memory

Board Type Subtype Total Available Memory Warning Values(%) Critical values(%)
cc 10G 512 95 100
cc 10G 1024 95 100
cc 40G 1024 95 100
fp 5G 1024 90 95
fp 10G 1024 90 95
fp 20G 2048 90 95
fp 20G 4096 90 95
fp 10G 2048 90 95
fp 40G 8192 90 95
fp 40G 16384 90 95
fp 80G 16384 90 95
fp 160G 32768 90 95
rp RP1 2048 90 95
rp RP1 4031 90 95
rp RP1 4096 90 95
rp 1RU 4096 300 310
rp 1RU 8192 300 310
rp 1RU 16384 300 310
rp 2RU 2048 90 95
rp 2RU 4031 90 95
rp 2RU 4096 90 95
rp RP2 8192 90 95
rp RP2 16384 90 95
rp RSP 2048 300 310


Table 3-68 lists the threshold values for average load conditions at 1 minute:

Threshold Values for Average Load Conditions at 1 Minute

Board Type Subtype Total Available Memory Warning Values(%) Critical values(%)
cc 10G 512 5 8
cc 10G 1024 5 8
cc 40G 1024 5 8
fp 5G 1024 5 8
fp 10G 1024 5 8
fp 20G 2048 5 8
fp 20G 4096 5 8
fp 10G 2048 5 8
fp 40G 8192 5 8
fp 40G 16384 5 8
fp 80G 16384 5 8
fp 160G 32768 5 8
rp RP1 2048 5 8
rp RP1 4031 5 8
rp RP1 4096 5 8
rp 1RU 4096 8 12
rp 1RU 8192 8 12
rp 1RU 16384 8 12
rp 2RU 2048 5 8
rp 2RU 4031 5 8
rp 2RU 4096 5 8
rp RP2 8192 5 8
rp RP2 16384 5 8
rp RSP 2048 8 12

Table 3-69 lists the threshold values for average load conditions at 5 minutes:

Threshold Values for Average Load Conditions at 5 Minutes

Board Type Subtype Total Available Memory Warning Values(%) Critical values(%)
cc 10G 512 5 8
cc 10G 1024 5 8
cc 40G 1024 5 8
fp 5G 1024 5 8
fp 10G 1024 5 8
fp 20G 2048 5 8
fp 20G 4096 5 8
fp 10G 2048 5 8
fp 40G 8192 5 8
fp 40G 16384 5 8
fp 80G 16384 5 8
fp 160G 32768 5 8
rp RP1 2048 5 8
rp RP1 4031 5 8
rp RP1 4096 5 8
rp 1RU 4096 8 12
rp 1RU 8192 8 12
rp 1RU 16384 8 12
rp 2RU 2048 5 8
rp 2RU 4031 5 8
rp 2RU 4096 5 8
rp RP2 8192 5 8
rp RP2 16384 5 8
rp RSP 2048 8 12

Table 3-70 lists the threshold values for average load conditions at 15 minutes:

Threshold Values for Average Load Conditions at 15 Minutes

Board Type Subtype Total Available Memory Warning Values(%) Critical values(%)
cc 10G 512 5 8
cc 10G 1024 5 8
cc 40G 1024 5 8
fp 5G 1024 5 8
fp 10G 1024 5 8
fp 20G 2048 5 8
fp 20G 4096 5 8
fp 10G 2048 5 8
fp 40G 8192 5 8
fp 40G 16384 5 8
fp 80G 16384 5 8
fp 160G 32768 5 8
rp RP1 2048 5 8
rp RP1 4031 5 8
rp RP1 4096 5 8
rp 1RU 4096 10 15
rp 1RU 8192 10 15
rp 1RU 16384 10 15
rp 2RU 2048 5 8
rp 2RU 4031 5 8
rp 2RU 4096 5 8
rp RP2 8192 5 8
rp RP2 16384 5 8
rp RSP 2048 10 15

CISCO-PRODUCTS-MIB

The CISCO-PRODUCTS-MIB lists the object identifiers (OIDs) assigned to the Cisco hardware platforms. CISCO ASR1006, ASR1004, ASR1002, ASR1002-F, ASR1001, and ASR1013 OIDs are supported.

CISCO-QINQ-VLAN-MIB

The CISCO-QINQ-VLAN-MIB describes configuration and monitoring capabilities relating to 802.1QinQ interfaces.

MIB Constraints

Table 3-71 lists the constraints that the Cisco ASR 1000 Series Routers places on the objects in the CISCO-QINQ-VLAN-MIB.

CISCO-QINQ-VLAN-MIB Constraints

MIB Objects Notes
cqvTerminationTable

• cqvTerminationPeEncap • cqvTerminationRowStatus

Implemented as Read only.
Implemented as Read only.
cqvTranslationTable Not supported

CISCO-RADIUS-EXT-MIB

The CISCO-RADIUS-EXT-MIB contains MIB objects used for managing the RADIUS authentication and accounting statistics.

CISCO-RF-MIB

The CISCO-RF-MIB provides configuration control and status information for the redundancy framework subsystem. The redundancy framework subsystem provides a mechanism for logical redundancy of the software functionality and is designed to support 1:1 redundancy for the processor cards.

CISCO-RTTMON-IP-EXT-MIB

The CISCO-RTTMON-IP-EXT-MIB provides extensions for the tables in CISCO-RTTMON-MIB to support IP layer extensions, specifically IPv6 addresses and other information related to IPv6 standards.

CISCO-RTTMON-MIB

The CISCO-RTTMON-MIB contains objects to monitor network performance. The MIB provides information about the response times of network resources and applications. Each conceptual round-trip time (RTT) control row in the MIB represents a single probe, which is used to determine an entity’s response time. The probe defines an RTT operation to perform (for example, an FTP or HTTP get request), and the results indicate whether the operation succeeded or failed, and how long it took to complete.

If you plan to schedule an RTT operation, see Table 3-72 for information about rttMonScheduleAdminRttStartTime in the rttMonScheduleAdminTable. Note An rttMonCtrlOperConnectionLostOccurred trap is generated when an RTT connection cannot be established to the destination router because the router responder application is not running. However, the trap is not generated if the physical connection to the router is lost. MIB Constraints

Table 3-72 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-RTTMON-MIB.

CISCO-RTTMON-MIB Constraints

MIB Objects Notes
RttMonProtocol The following values are not supported:

• snaRUEcho • snaLU0EchoAppl.

rttMonApplAuthTable
rttMonCtrlAdminTable

• rttMonCtrlAdminRttType

Supported values are:

• echo(1) • pathEcho(2) • udpEcho(5) • tcpConnect(6) • http(7) • dns(8) • jitter(9) • ftp(12) All other values not supported

rttMonEchoAdminTable

rttMonEchoAdminProtocol

Supported values:

• ipIcmpEcho(2) • ipUdpEchoAppl(3) • ipTcpConn(24) • httpAppl(25) • dnsAppl(26) • jitterAppl(27) • ftpAppl(30) All other values not supported.

rttMonScheduleAdminTable

• rttMonScheduleAdminRttStartTime

Before setting this object to a date/time value,

make sure the ESR clock was set through the CLI clock set command. Otherwise, the scheduled RTT operation does not run.

rttMonHistoryCollectionTable HTTP and Jitter types are not supported.

CISCO-SLB-EXT-MIB

The CISCO-SLB-EXT-MIB contains extensions to the Cisco server load-balancing (SLB) MIB (CISCO-SLB-MIB). Server load balancing enables the router to balance the processing of packets and connections from a number of other devices, such as real servers, firewalls, or caches. An SLB device determines how to handle incoming frames and connections according to the contents of the incoming data and various configuration options.

CISCO-SLB-MIB

The CISCO-SLB-MIB contains objects to manage server load-balancing (SLB) managers, such as those provided by the Cisco IOS SLB product. The MIB includes objects for the manager-side implementation of the Dynamic Feedback Protocol (DFP), which is used to obtain information about servers. CISCO-SESS-BORDER-CTRLR-CALL-STATS-MIB

The CISCO-SESSION-BORDER-CONTROLLER-CALL-STATS-MIB defines the statistics information for Session Border Controller application. The statistic information is of two types: • Call statistics • Media statistics

CISCO-SESS-BORDER-CTRLR-EVENT-MIB

The CISCO-SESS-BORDER-CTRLR-EVENT-MIB defines the SNMP notifications, events, and alarms generated by Session Border Controller application, and sends these notifications to SNMP manager application. The various notification, events, and alarms generated by a SBC application can be:

• Change in the state of a configured SBC service. • Change in the connection state with an adjacency or a radius server or H.248 controller attached to SBC, CPU or memory congestion, due to a large number of ongoing SIP/H.248 calls. • Violation in the call policies configured for the current ongoing SIP/H.248 calls, when SBC application receives media (RTP/RTCP) packets from an unknown IP address or port. CISCO-SESS-BORDER-CTRLR-STATS-MIB The CISCO-SESS-BORDER-CTRLR-STATS-MIB contains objects to manage the statistics information for the Session Border Controller application. The statistics information is categorized into these types: • RADIUS Messages Statistics—Represents the statistics of various RADIUS messages for the RADIUS servers with which the client (SBC) shares a secret. • RF Billing Statistics—Represents the RF billing statistics information, which is used to monitor the messages sent per realm over the IMS Rx interface by the RF billing manager(SBC). • SIP Statistics—Represents the SIP requests and responses on a SIP adjacency for a specific interval.


MIB Tables

Table 3-73 lists the tables in CISCO-SESS-BORDER-CTRLR-STATS-MIB.

CISCO-RTTMON-MIB Constraints

MIB Tables Description
csbRadiusStatsTable Maintains the RADIUS messages for the RADIUS servers.
csbRfBillRealmStatsTable Maintains the RF billing statistics information.
csbSIPMthdCurrentStatsTable Contains the total number of SIP request and responses for each SIP

method on a given adjacency for a specific interval.

csbSIPMthdHistoryStatsTable Contains the historical count of SIP requests and responses for each

SIP method on a SIP adjacency for the different intervals defined by the csbSIPMthdHistoryStatsInterval object.

csbSIPMthdRCCurrentStatsTable Contains the SIP method request and response code statistics

corresponding to the method and response code combination on a given adjacency for a specific interval.

csbSIPMthdRCHistoryStatsTable Contains the historical data for the SIP method request and

response code statistics corresponding to the method and response code on a given adjacency for a specific interval.

CISCO-SIP-UA-MIB

The CISCO-SIP-UA-MIB manages the Session Initiation Protocol (SIP) User Agents (UA). SIP is an application-layer signalling protocol for creating, modifying, and terminating multimedia sessions with one or more participants. A UA is an application that contains both a User Agent Client (UAC) and a User Agent Server (UAS). A UAC is an application that initiates a SIP request. A UAS is an application that contacts the corresponding user when a SIP request is received and returns a response on behalf of the user.

CISCO-SONET-MIB

The CISCO-SONET-MIB contains objects to describe SONET/SDH interfaces on the router. This MIB is an extension to the standard SONET-MIB (RFC 2558). The CISCO-SONET-MIB has objects that provide additional SONET-related information not found in the SONET-MIB. Note CISCO-SONET-MIB supports SONET traps that are seen when the linestatus, sectionstatus, pathstatus changes, and Notifications are enabled.

MIB Constraints

The following CISCO-SONET-MIB tables are not implemented in the Cisco ASR 1000 Series Routers:

• csConfigTable • csVTConfigTable • csAPSConfigTable • cssTraceTable • cspTraceTable • csStatsTable • cspConfigTable

Note Only the section, line, and path totals objects from the ciscoSonetStatsMIBGroup and the complete ciscoSonetEnableGroup must be supported. All network elements containing one or more SONET interfaces must implement this MIB.

CISCO-SUBSCRIBER-SESSION-MIB

The CISCO-SUBSCRIBER-SESSION-MIB contains objects that describe the subscriber sessions terminated by a Remote Access Service (RAS).

MIB Tables

Table 3-74 lists the tables in CISCO-SUBSCRIBER-SESSION-MIB.

CISCO-SUBSCRIBER-SESSION-MIB Tables

MIB Tables Description
csubSessionTable Describes a list of subscriber sessions currently maintained by the

system.

csubSessionByTypeTable Sorts the subscriber sessions first by corresponding subscriber

session type, and then by the ifIndex assigned to the corresponding subscriber session.

csubAggStatsTable Contains sets of aggregated statistics pertaining to subscriber

sessions, where each set has a unique scope of aggregation. csubAggStatsIntTable Contains aggregated subscriber session performance data collected for every 15-minute measurement intervals.

csubJobTable Contains the subscriber session jobs submitted by the element

management system (EMS) and network management system (NMS).

csubJobMatchParamsTable Contains subscriber session job parameters that describe the match

criteria.

csubJobQueryParamsTable Contains subscriber session job parameters that describe the query

parameters.

csubJobQueueTable Lists the subscriber session jobs pending in the subscriber session

job queue.

csubJobReportTable Contains the reports corresponding to subscriber session jobs that

have query as the csubJobType, and finished as the csubJobState.

MIB Constraints

Table 3-75 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the CISCO-SUBSCRIBER-SESSION-MIB. Any MIB object that is not listed in this table is implemented as defined in the MIB.

Table 3-74 lists the tables in CISCO-SUBSCRIBER-SESSION-MIB.

CISCO-SUBSCRIBER-SESSION-MIB Constraints

MIB Objects Notes
csubSessionByTypeTable Not implemented.
csubAggStatsIntTable Not implemented.
csubJobQueueTable Not implemented.
csubSessionTable

• csubSessionType

• csubSessionAuthenticated • csubSessionCreationTime • csubSessionAvailableIdentities

Read only.

The pppSubscriber(3), pppoeSubscriber(4), ipInterfaceSubscriber(7), ipPktSubscriber(8), and ipDhcpv4Subscriber(9) types are supported. Read only. Read only. Read only.

csubSessionSubscriberLabel

• csubSessionMacAddress • csubSessionNativeVrf • csubSessionNativeIpAddrType • csubSessionNativeIpAddr • csubSessionNativeIpMask • csubSessionDomainVrf • csubSessionPbhk • csubSessionRemoteId • csubSessionCircuitId • csubSessionNasPort • csubSessionDomain • csubSessionUsername • csubSessionAcctSessionId • csubSessionProtocol

• csubSessionLocationIdentifier • csubSessionServiceIdentifier • csubSessionLastChanged • csubSessionNativeIpAddrType2 • csubSessionNativeIpAddr2 • csubSessionNativeIpMask2 • csubSessionIpAddrAssignment • csubSessionRedundancyMode • csubSessionDerivedCfg • csubSessionDnis • csubSessionMedia • csubSessionMlpNegotiated • csubSessionServiceName • csubSessionDhcpClass • csubSessionTunnelName

Read only.

Read only. Read only. Read only. Read only. Read only. Read only. Read only. Read only. Read only. Read only. Read only. Read only. Read only. Read only. The IP(3) and PPP(5) values are supported. Read only. Read only. Read only. Read only. Read only. Read only. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented

csubAggStatsTable

• csubAggStatsPendingSessions • csubAggStatsUpSessions • csubAggStatsAuthSessions • csubAggStatsUnAuthSessions

Currently the scope of aggregation is limited to

providing the statistics at the RAS level. Read only. Read only. Read only. Read only.

csubAggStatsLightWeightSessions

• csubAggStatsHighUpSessions • csubAggStatsAvgSessionUptime • csubAggStatsAvgSessionRPM • csubAggStatsAvgSessionRPH • csubAggStatsTotalFailedSessions • csubAggStatsTotalUpSessions . • csubAggStatsTotalLightWeightSessions • csubAggStatsTotalFlowsUp • csubAggStatsCurrFlowsUp • csubAggStatsRedSessions • csubAggStatsThrottleEngagements • csubAggStatsTotalCreatedSessions • csubAggStatsTotalAuthSessions • csubAggStatsTotalDiscSessions • csubAggStatsDayCreatedSessions • csubAggStatsDayFailedSessions • csubAggStatsDayUpSessions • csubAggStatsDayAuthSessions • csubAggStatsDayDiscSessions • csubAggStatsCurrTimeElapsed • csubAggStatsCurrValidIntervals . • csubAggStatsCurrInvalidIntervals • csubAggStatsCurrCreatedSessions • csubAggStatsCurrFailedSessions • csubAggStatsCurrUpSessions • csubAggStatsCurrAuthSessions • csubAggStatsCurrDiscSessions

Read only.

Read only. Read only. Read only. Read only. Read only. Read only Read only. Read only. Read only. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented.

csubJobTable

• csubJobId • csubJobStatus • csubJobStorage • csubJobType • csubJobControl If the job is executing, the abort action is ignored. • csubJobState csubJobStartedTime • csubJobFinishedTime • csubJobFinishedReason

Read only.

The values, Not-In-Service and Not-Ready, are not supported. Read only. Read only. Read only. Read only. Read only. The sysuptime at the time of job start is measured in timeticks. The sysuptime at the time of job start is measured in timeticks. The value insufficientResources is returned if a job query is started without sufficient job match parameters.

csubJobMatchParamsTable

• csubJobMatchParamsEntry • csubJobMatchIdentities • csubJobMatchSubscriberLabel • csubJobMatchMacAddress • csubJobMatchNativeVrf • csubJobMatchNativeIpAddrType • csubJobMatchNativeIpAddr • csubJobMatchPbhk • csubJobMatchOtherParams • csubJobMatchDomainVrf • csubJobMatchRemoteId • csubJobMatchCircuitId • csubJobMatchNasPort • csubJobMatchUsername • csubJobMatchAccountingSid • csubJobMatchDomain • csubJobMatchDnis • csubJobMatchMedia • csubJobMatchMlpNegotiated • csubJobMatchProtocol • csubJobMatchServiceName • csubJobMatchDhcpClass • csubJobMatchTunnelName • csubJobMatchDanglingDuration

Read only.

Read only. Read only. Read only. Read only. The job search based on IPv6 is not supported. Read only. Read only. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented. Not implemented.

csubJobQueryParamsTable

csubJobQueryResultingReportSize

When the EMS or NMS sets the jobcontrol value

to release, the job and the csubJobQueryResultingReportSize object become invalid. • The csubJobQueryParamsTable is created only when the jobfinished value becomes normal.

csubJobReportTable

• csubJobReportId • csubJobReportSession

Read only. Read only.
csubJobFinishedNotifyEnable Read-write.
csubJobIndexedAttributes The supported indexed attributes are:

• Subscriber Label • Mac Address • IP Address (IPv4 only) • Native VRF • Port-bundle Host Key (PBHK)

CISCO-SYSLOG-MIB

The CISCO-SYSLOG-MIB contains all system log messages generated by the Cisco IOS software. The MIB provides a way to access these syslog messages through SNMP. All Cisco IOS syslog messages contain the message name and its severity, message text, the name of the entity generating the message, and an optional time stamp. The MIB also contains a history of syslog messages and counts related to syslog messages.

Note You can configure the Cisco ASR 1000 Series Routers to send syslog messages to a syslog server.

Note The MIB does not keep track of messages generated from debug commands entered through the command-line interface (CLI).

CISCO-UNIFIED-FIREWALL-MIB

The CISCO-UNIFIED-FIREWALL-MIB contains status and performance statistics for Cisco firewall implementation. The ASR 1000 platform only supports the statistics for the zone base firewall.

Note Begining with Cisco IOS Release 3.6, the CISCO-UNIFIED-FIREWALL-MIB is supported on IPv6 networks.

MIB Tables

Table 3-76 lists the tables in CISCO-UNIFIED-FIREWALL-MIB.

CISCO-UNIFIED-FIREWALL-MIB Tables

MIB Tables Description
cufwConnSummaryTable Contains information about the connection activity on the firewall for each

layer3 and layer 4 protocols. Each entry in the table lists the connection summary of a distinct network protocol.

cufwAppConnSummaryTable Contians firewall connections information for Layer 7 protocols.

Each entry in the table lists the connection summary corresponding to a distinct application protocol.

cufwPolicyConnSummaryTable Contains firewall connections information for layer3 and layer 4

protocols for each applied policy. Each entry in the table lists the connection summary of a distinct network protocol, configured on the specified target policy on the firewall.

cufwPolicyAppConnSummaryTable Contains firewall connections information for Layer 7 protocols for

each applied policy. Each entry in the table lists the connection summary of a distinct application protocol, configured on the specified target policy on the firewall.

cufwInspectionTable Contains objects to identify whether or not an application protocol

is configured for inspection. It also contains attributes to identify whether or not the specified protocol is currently being verified.

cufwUrlfServerTable Lists the URL filtering servers configured on the managed devices

and corresponding performance statistics.

MIB Constraints

Table 3-77 lists the constraints that the Cisco ASR 1000 Series Router places on CISCO-UNIFIED-FIREWALL-MIB.

CISCO-UNIFIED-FIREWALL-MIB Constraints

MIB Objects Notes
cufwInspectionTable Not supported.
cufwUrlfServerTable Not supported.
cuFwConnectionGlobalsTable

• cufwConnGlobalNumSetupsAborted • cufwConnGlobalNumPolicyDeclined • cufwConnGlobalNumResDeclined • cufwConnGlobalNumExpired • cufwConnGlobalNumAborted • cufwConnGlobalNumEmbryonic • cufwConnGlobalNumRemoteAccess cufwConnGlobalConnSetupRate1 • cufwConnGlobalConnSetupRate5

Not supported, default value set to zero.

Not supported, default value set to zero. Not supported, default value set to zero. Not supported, default value set to zero. Not supported, default value set to zero. Not supported, default value set to zero. Not supported, default value set to zero. Not supported, default value set to zero. The number of sessions created in the last minute. The number of sessions created in the last five minutes.

cufwConnSummaryTable

• cufwConnNumSetupsAborted • cufwConnNumPolicyDeclined • cufwConnNumResDeclined • cufwConnNumAborted • cufwConnSetupRate1 • cufwConnSetupRate5

Not supported, default value set to zero.

Not supported, default value set to zero. Not supported, default value set to zero. Not supported, default value set to zero. The number of sessions created in the last minute. The number of sessions created in the last five minutes

cufwAppConnSummaryTable

cufwAppConnNumSetupsAborted • cufwAppConnNumPolicyDeclined • cufwAppConnNumPolicyDeclined • cufwAppConnNumAborted • cufwAppConnSetupRate1 • cufwAppConnSetupRate5

Not supported, default value set to zero.

Not supported, default value set to zero. Not supported, default value set to zero. Not supported, default value set to zero. The number of sessions created in the last minute. The number of sessions created in the last five minutes.

ufwPolicyConnSummaryTable

cufwPolConnNumSetupsAborted • cufwPolConnNumPolicyDeclined . • cufwPolConnNumResDeclined • cufwPolConnNumAborted

Not supported, default value set to zero.

Not supported, default value set to zero Not supported, default value set to zero. Not supported, default value set to zero.

cufwPolicyAppConnSummaryTable

cufwPolAppConnNumSetupsAborted • cufwPolAppConnNumPolicyDeclined • cufwPolAppConnNumResDeclined • cufwPolAppConnNumAborted

Not supported, default value set to zero.

Not supported, default value set to zero. Not supported, default value set to zero. Not supported, default value set to zero.

CISCO-TAP2-MIB

The CISCO-TAP2-MIB manages Cisco intercept feature. This MIB replaces CISCO-TAP-MIB. This MIB defines a generic stream table that contains fields common to all intercept types. Specific intercept filters are defined in the following extension MIBs: • CISCO-IP-TAP-MIB for IP intercepts • CISCO-802-TAP-MIB for IEEE 802 intercepts •CISCO-USER-CONNECTION-TAP-MIB for RADIUS-based user connection intercepts.

MIB Constraints

Table 3-78 lists the constraints that the Cisco ASR 1000 Series Router places on CISCO-TAP2-MIB.

CISCO-TAP2-MIB Constraints

MIB Objects Notes
cTap2MediationRtcpPort Not supported.
cTap2MediationRetransmitType Not supported.
cTap2MediationTransport Only udp(1) is supported


CISCO-TAP-MIB

The CISCO-TAP-MIB contains objects to manage Cisco intercept feature. CISCO-UBE-MIB

The CISCO-UBE-MIB contains objects to manage the Cisco Unified Border Element (CUBE), which is a Cisco IOS Session Border Controller (SBC) that interconnects independent voice over IP (VoIP) and video over IP networks for data, voice, and video transport.

CISCO-USER-CONNECTION-TAP-MIB

The CISCO-USER-CONNECTION-TAP-MIB is a filter MIB that provides the functionality to manage the Cisco intercept feature for user connections. This MIB is used along with the CISCO-TAP2-MIB to intercept and filter user traffic. To create a user connection intercept, an entry named cuctTapStreamEntry is created in the CISCO-USER-CONNECTION-TAP-MIB. This entry contains the filtering information.

CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB

The CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB contains VLAN-ID and ifIndex information for each routed virtual LAN (VLAN) interface on the router. A routed VLAN interface is the router interface or subinterface to which you attach the IP address used by the router on the VLAN. The MIB maps each VLAN-ID to an ifIndex, which you can use to access the ipRouteTable to obtain the routing configuration for the routed VLAN interface.

CISCO-VLAN-MEMBERSHIP-MIB

The CISCO-VLAN-MEMBERSHIP-MIB provides management functions for the VLAN membership within the framework of Cisco VLAN Architecture, Version 2.0. The MIB provides information on VLAN Membership Policy Servers used by a device and VLAN membership assignments of non-trunk bridge ports of the device.

CISCO-VPDN-MGMT-MIB

The CISCO-VPDN-MGMT-MIB provides operational information about the Virtual Private Dialup Network (VPDN) feature on the router. You can use the MIB to monitor VPDN tunnel information on the router, but you cannot use the MIB to configure VPDN.

VPDN enables the router to forward Point-to-Point Protocol (PPP) traffic between an Internet service provider (ISP) and a home gateway. The CISCO-VPDN-MGMT-MIB includes several tables that contain VPDN tunneling information:

• cvpdnSystemTable—Provides system-wide VPDN information. • cvpdnTunnelAttrTable—Provides information about each active tunnel. • cvpdnSessionAttrTable—Provides information about each active session within each tunnel. • cvpdnUserToFailHistInfoTable—Provides information about the last failure that occurred for each tunnel user. • cvpdnTemplateTable—Identifies each VPDN template and indicates the number of active sessions associated with the template. See Table 3-79 for information about template name restrictions and and their effect on SNMP.

MIB Constraints

The CISCO-VPDN-MGMT-MIB contains read-only information. In addition, the MIB objects in Table 3-79 have been deprecated. Although currently supported, their use is being phased out and we recommend that you use the replacement object instead.

CISCO-VPDN-MGMT-MIB Constraints

MIB Objects Notes
cvpdnTunnelTotal Replaced by cvpdnSystemTunnelTotal.
cvpdnSessionTotal Replaced by cvpdnSystemSessionTotal.
cvpdnDeniedUsersTotal Replaced by cvpdnSystemDeniedUsersTotal.
cvpdnTunnelTable Replaced by cvpdnTunnelAttrTable.
cvpdnTunnelSessionTable Replaced by cvpdnSessionAttrTable.

cvpdnTemplateTable SNMP limits the size of VPDN template names to 128 characters. If any template name in the cvpdnTemplateTable exceeds this length, you cannot use an SNMP getmany request to retrieve any table entries. Instead, you must use individual getone requests to retrieve each template name (cvpdnTemplateName) that does not exceed 128 characters.

NoteCISCO-VPDN-MGMT-MIB does not support L2TPv3.

CISCO-VOICE-ANALOG-IF-MIB

The CISCO-VOICE-ANALOG-IF-MIB provides the standard configuration, timing parameters, telephony hook, and ring status information on the Cisco Analog Voice interface implementation. This MIB manages the following groups:

• Analog interface general group • E&M (recEive and transMit) interface group • FXO (Foreign Exchange Office) interface group • FXS (Foreign Exchange Station) interface group

Note This MIB is not supported in the ASR 1000 Series Routers.

CISCO-VOICE-COMMON-DIAL-CONTROL-MIB

The CISCO-VOICE-COMMON-DIAL-CONTROL-MIB contains voice-related objects that are common across more than one network encapsulation, such as VoIP, Voice over ATM (VoATM), and Voice over Frame Relay (VoFR).

CISCO-VOICE-DIAL-CONTROL-MIB

The CISCO-VOICE-DIAL-CONTROL-MIB module enhances the IETF Dial Control MIB (RFC2128) by providing the management of voice telephony peers on both a circuit-switched telephony networks and IP data networks.

CISCO-VOICE-IF-MIB

The CISCO-VOICE-IF-MIB manages the common voice-related parameters for both voice analog and Integrated Services Digital Network (ISDN) interfaces.

Note This MIB is not supported in the ASR 1000 Series Routers.

CISCO-VOIP-TAP-MIB

The CISCO-VOIP-TAP-MIB module defines the objects to manage the Intercept feature for Voice over IP (VoIP). This MIB is used along with CISCO-TAP2-MIB to intercept the VoIP control and data traffic.

DIAL-CONTROL-MIB (RFC 2128)

The DIAL-CONTROL-MIB (RFC 2128) contains peer information for demand access.

DS1-MIB (RFC 2495)

The DS1-MIB(RFC-2495) contains a description of the DS1, E1, DS2, and E2 interface objects. Note Effective from Cisco IOS Release 15.1(3)S, DS1-MIB is supported on SPA-24CHT1-CE-ATM. Note DS1-MIB is not supported on SPA-2CHT3-CE-ATM because only the clear channel T3 mode is supported in Cisco IOS Release 15.1(3)S.

MIB Constraints

Table 3-80 describes the constraints that the Cisco ASR 1000 Series Router places on the objects in the DS1-MIB. For detailed definitions of the MIB objects, see the corresponding MIB.

DS1-MIB Constraints

MIB Objects Notes
dsx1ConfigTable

• dsx1LineStatusChangeTrapEnable • dsx1Channelization • dsx1LineLength • dsx1LineType • dsx1LineCoding • dsx1SendCode • dsx1CircuitIdentifier • dsx1LoopbackConfig • dsx1SignalMode • dsx1TransmitClockSource • dsx1Fdl Read only. • dsx1LoopbackStatus

This MIB object cannot be set through

SNMP. The snmp-server enable traps ds1 command can be used to enable status change traps. Read only. Read only. Read only. Read only. Read only. Read only. Read only. Read only. Read only or SPA-8XCHT1/E1 usage is always none(1). Read only. SPA-8XCHT1/E1 usage: Payload loopbacks are not supported (dsx1NearEndPayloadLoopback, dsx1FarEndPayloadLoopback).

dsx1FracTable Not implemented.
dsx1FarEndIntervalTable Not implemented.

DS3-MIB (RFC 2496)

The DS3-MIB(RFC-2496) contains a description of the DS3 and E3 interface objects. Note Effective from Cisco IOS Release 15.1(3)S, DS3-MIB is supported on SPA-2CHT3-CE-ATM. Note Effective from Cisco IOS Release 15.3(1)S, the DS3-MIB is supported on SPA-8XT3/E3.

MIB Constraints

Table 3-81 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the RFC1407-MIB. Objects that are not listed in the table are implemented as defined in the RFC 1407-MIB.

DS3-MIB Constraints

MIB Objects Notes
dsx3ConfigTable

• dsx3LineType • dsx3LineCoding • dsx3SendCode • dsx3TransmitClockSource • dsx3CircuitIdentifier • dsx3LoopbackConfig

Supported values are:

• T3 supports dsx3M23(2) and dsx3CbitParity(4). • E3 supports e3Framed(7) and e3Plcp(8). Read only. Supported values are: • T3 supports dsx3B3ZS(2). • E3 supports e3HDB3(3). Read only. Supports only dsx3SendNoCode Supported values are loopTiming(1) and localTiming(2). Read only. Read only.

dsx3FarEndConfigTable Not implemented.
dsx3FarEndCurrentTable Not implemented.
dsx3FarEndIntervalTable Not implemented.
dsx3FarEndTotalTable Not implemented.
dsx3FracTable Not implemented.
Notes

All T3/ATM line cards only support read-only values on all variables. Currently for the dsx3FracTable to operate, the DS1 layer must be implemented in the ifTable. In this release, this table is shown as not implemented because no rows are instantiated.

ENTITY-MIB (RFC 4133)

The ENTITY-MIB (RFC 4133) allows functional component discovery. It is used to represent physical and logical entities (components) in the router and manages those entities. The current software release supports the RFC 4133 version of this MIB. The following are the conformance groups contained in the ENTITY-MIB: • entityPhysical group—Describes the physical entities managed by a single agent. • entityLogical group—Describes the logical entities managed by a single agent. • entityMapping group—Describes the associations between the physical entities, logical entities, interfaces, and non-interface ports managed by a single agent. • entityGeneral group—Describes general system attributes shared by potentially all types of entities managed by a single agent. • entityNotifications group—Contains status indication notifications. The following groups are added from RFC 4133: • entityPhysical2 group—This group augments the entityPhysical group. • entityLogical2 group—Describes the logical entities managed by a single agent, and replaces entityLogical group.

The MIB table entPhysicalTable identifies the physical entities in the router. The entPhysicalTable contains a single row for the Cisco ASR 1000 Series Router chassis and a row for each entity in the chassis. A physical entity may contain other entities. For example, a SIP10 in slot 6 with one SPA 1XOC12 POS-SPA in subslot 6/0 supports the following entities in this SNMP output for SPAs and SIPs, sensors on the SIP, and SPA ports:

entPhysicalDescr.1040 = 1-port OC12/STM4 POS Shared Port Adapter entPhysicalContainedIn.1040 = 1027 entPhysicalDescr.1066 = subslot 0/0 temperature Sensor 0 entPhysicalContainedIn.1066 = 1040 entPhysicalDescr.1067 = subslot 0/0 temperature Sensor 1 entPhysicalContainedIn.1067 = 1040 entPhysicalDescr.1068 = subslot 0/0 temperature Sensor 2 entPhysicalContainedIn.1068 = 1040 entPhysicalDescr.1078 = subslot 0/0 voltage Sensor 0 entPhysicalContainedIn.1078 = 1040 entPhysicalDescr.1079 = subslot 0/0 voltage Sensor 1 entPhysicalContainedIn.1079 = 1040 entPhysicalDescr.1080 = subslot 0/0 voltage Sensor 2 entPhysicalContainedIn.1080 = 1040 entPhysicalDescr.1081 = subslot 0/0 voltage Sensor 3 entPhysicalContainedIn.1081 = 1040 entPhysicalDescr.1091 = subslot 0/0 transceiver container 0 entPhysicalContainedIn.1091 = 1040 entPhysicalDescr.1092 = OC12 SR-1/STM4 MM entPhysicalContainedIn.1092 = 1091 entPhysicalDescr.1093 = Packet over Sonet entPhysicalContainedIn.1093 = 1092 entPhysicalDescr.1095 = subslot 0/0 transceiver 0 Temperature Sensor entPhysicalContainedIn.1095 = 1092 entPhysicalDescr.1096 = subslot 0/0 transceiver 0 Supply Voltage Sensor entPhysicalContainedIn.1096 = 1092 entPhysicalDescr.1097 = subslot 0/0 transceiver 0 Bias Current Sensor entPhysicalContainedIn.1097 = 1092 entPhysicalDescr.1098 = subslot 0/0 transceiver 0 Tx Power Sensor entPhysicalContainedIn.1098 = 1092 entPhysicalDescr.1099 = subslot 0/0 transceiver 0 Rx Power Sensor entPhysicalContainedIn.1099 = 1092

For more information on this MIB, refer Appendix A, “ENTITY-MIB.”

Note The ENTITY-MIB is also supported on the Cisco ASR 1013 and ASR 1001 chassis.

Note Effective from Cisco IOS Release 15.1(3)S, ENTITY-MIB is supported on SPA-24CHT1-CE-ATM and SPA-2CHT3-CE-ATM.

'Note Effective from Cisco IOS Release 15.3(1)S, the ENTITY-MIB is supported on the Cisco ASR1000: 40G Native Ethernet Line Card and SPA-8XT3/E3.

For the Cisco ASR1000 platform, the entPhysicalParentRelPos are populated with the slot numbers (except for the RP, ESP, and PEM slot numbers) given in the external label. Table 3-82 lists the mapping between external label and entPhysicalParentRelPos.


Table 3-82 Mapping the External Label to the entPhysicalParentRelPos Value

Type External Label Value
SIP Container 0 to 5 0 to 5 match the external label.
RP Container R0 and R1 6 for R0, and 7 for R1.
FP Container F0 and F1 8 for F0 and 9 for F1.
Power Supply Bay 0 and 1 14 for PEM 0, and 15 for PEM 1.
CPU Starts from 0.
QFP Starts from 0.
Crypto ASIC Module of FP Starts from 0.

The Cisco ASR 1001 Router chassis includes inbuilt RP module, SIP module, SPA module 0/0, IDC modue 0/2, FP or ESP Module, and FanTray Module. Table 3-83 lists the values of the affected MIB table objects in the Cisco ASR 1001 Router:

Table 3-83 Affected MIB Objects in a Cisco ASR 1001 Router

Type External Label Value
entPhysicalContainedIn RP Module entPhysicalIndex of Chassis.
ESP Module entPhysicalIndex of Chassis.
SIP Module entPhysicalIndex of Chassis.
SPA Module 0/0 entPhysicalIndex of SIP Module.
IDC Module 0/2 entPhysicalIndex of SIP Module.
FanTray Module entPhysicalIndex of Chassis.
entPhysicalIsFRU RP Module false(2)
ESP Module false(2)
SIP Module false(2)
SPA Module 0/0 false(2)
IDC Module 0/2 false(2)
FanTray Module false(2)
entPhysicalParentRelPos RP Module 6
ESP Module 8
SIP Module 0
SPA Module 0/0 0
IDC Module 0/2 2
FanTray Module 0

Table 3-84 lists the fans supported on a Cisco ASR 1000 series Router.

Table 3-84 Fans Supported on a Cisco ASR 1000 series Router

Modules Number of Fans
ASR1001 PEM 1
ASR1002/ASR1002-F PEM 2
ASR1004/ASR1006/ASR1013 PEM 3
ASR1001 FanTray Module 7

Table 3-85 lists the variations between the entPhysicalTable values for the hard disk in the RP1 and RP2 modules.

Table 3-85 Variations Between the entPhysicalTable Values

MIB Object ASR 1000 RP1 ASR 1000 RP2
entPhysicalContainedIn entPhysicalIndex of RP module. entPhysicalIndex of hard disk container.
entPhysicalIsFRU false(2). true(1).

MIB Constraints

Table 3-86 lists the constraints that the Cisco ASR 1000 Series Routers places on the objects in the ENTITY-MIB.

Table 3-86 ENTITY-MIB Constraints

MIB Object Notes
entPhysicalSoftwareRev Supported for RP and SIP Modules.
entPhysicalAssetAlias Not supported
entPhysicalAssetId Not supported for Transceiver Modules, USB and

Harddisk. Implemented only as read-write for the following entPhysicalClass entities: • Chassis • Powersupply • Module

entPhysicalSerialNum Implemented as Readonly. Not implemented for USB and Harddisk.
entPhysicalModelName Not implemented for USB and Harddisk.
entPhysicalMfgName Not implemented for USB and Harddisk.
entPhysicalUris Not implemented for USB and Harddisk.

Implemented as Read only.

entPhysicalAlias Not supported for transceiver modules, USB and

Harddisk. Implemented only as read-write for the following entPhysicalClass entities: • Chassis • Powersupply

entPhysicalMfgDate Not implemented.


The RP2 module contains Harddisk Container for installing the external Harddisk.

Note The RP2 module contains more sensors than RP1. Hence, the indexing of ENTITY-MIB varies for RP2

Note The RP2 contains 2 physical CPUs, but the CPUs are not monitored separately. The monitoring the CPU utilization is the aggregate result of both the CPUs. Hence, the cpmCPUTotalTable object contains only one entry for RP CPUs.

Note Effective from Cisco IOS Release 15.2(4)S, the entPhysicalIsFRU object for the 6XGE-BUILT-IN SPA in the ASR1002-X chassis is shown as True. This results in the 6XGE-BUILT-IN SPA getting wronglypopulated in the cefcModule table.

For the CISCO ASR 1002 Router, RP Module, SIP Module, and SPA Module 0/0 are built-in to the chassis. Table 3-87 lists the values of the affected MIB Objects. • Module

For the CISCO ASR 1002 Router, RP Module, SIP Module, and SPA Module 0/0 are built-in to the chassis. Table 3-87 lists the values of the affected MIB Objects.

Affected MIB Objects in CISCO ASR 1002 Router

MIB Object Module Value
entPhysicalContainedIn RP Module SIP Module SPA Module 0/0 entPhysicalIndex of chassis. entPhysicalIndex of chassis.

entPhysicalIndex of SIP Module.

entPhysicalIsFRU RP Module SIP Module

SPA Module 0/0

false(2) false(2) false(2)
entPhysicalSerialNum SPA Module 0/0 No Serial Number
entPhysicalParentRelos RP Module ESP Module SIP Module 0 0 0
SIP Module 0

For the CISCO ASR 1002-F Router, RP Module, SIP Module, SPA Module 0/0, and FP or ESP Module are built-in to the chassis. Table 3-88 lists the values of the affected MIB Objects.

Affected MIB Objects in Cisco ASR 1002-F Router

MIB Object Module Value
entPhysicalContainedIn RP Module


ESP Module
SIP Module
SPA Module 0/0

entPhysicalIndex of Chassis.


entPhysicalIndex of Chassis.
entPhysicalIndex of Chassis.
entPhysicalIndex of SIP Module.

entPhysicalIsFRU RP Module


ESP Module
SIP Module
SPA Module 0/0

false(2)


false(2)
false(2)
false(2)

entPhysicalSerialNum SPA Module 0/0 No Serial Number.
entPhysicalParentRelos RP Module


ESP Module
SIP Module

0


0
0

When both primary and secondary RPs are up and running, entities for standby usb flash, Flash disk, and Harddisk are not populated for ENTITY-MIB. Note For cevModuleASR 1000 UnknownRP object, only RP module entry is populated without any child entities for it.

Note On CEoP SPAs, the entPhysicalFirmware object is mapped to the UFE Field-Programmable Device (FPD).

ENTITY-SENSOR-MIB (RFC 3433)

The ENTITY-SENSOR-MIB (RFC 3433) contains objects that manage physical sensors, which are represented in the Entity-MIB with entPhysicalEntry and an entPhysicalClass value of sensor(8). The ENTITY-SENSOR-MIB contains a single table called the entPhySensorTable.

Note In ASR1002-F, the RP, FP, and SIP support various sensors. These sensors are supported on the CISCO-ENTITY-SENSOR-MIB.


Effective from Cisco IOS Release 15.1(3)S, ENTITY-SENSOR-MIB is supported on SPA-24CHT1-CE-ATM and SPA-2CHT3-CE-ATM.

Note Effective from Cisco IOS Release 15.3(1)S, the ENTITY-SENSOR-MIB is supported on the Cisco ASR1000: 40G Native Ethernet Line Card and SPA-8XT3/E3.

Note The ENTITY-SENSOR-MIB replaces the CISCO-ENVMON-MIB.

ENTITY-STATE-MIB

The ENTITY-STATE-MIB defines objects to extend the functionality provided by the ENTITY-MIB. This MIB supports the entities having these entPhysicalClass values:

• chassis • container (Slot container, SPA container, PS bay, and Transceiver Container) • module (RP, FP, CC, SPA, and Transceiver) • powerSupply • fan

Note The ENTITY-STATE-MIB is supported on the Cisco ASR 1001 chassis.

Note Effective from Cisco IOS Release 15.1(3)S, ENTITY-STATE-MIB is supported on SPA-24CHT1-CE-ATM and SPA-2CHT3-CE-ATM.

Note Effective from Cisco IOS Release 15.3(1)S, ENTITY-STATE-MIB is supported on the Cisco ASR1000: 40G Native Ethernet Line Card and SPA-8XT3/E3.

MIB Constraints

Table 3-89 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the ENTITY-STATE-MIB

ENTITY-STATE-MIB Constraints

MIB Object Notes
entStateAlarm Valid values are:

• critical • major • minor • warning These values indicate the

entStateAdmin -


Power supply and fan alarms are generated on either the Power Entry Module or FanTray module. Therefore no alarm is generated on the entStateAlarm associated with either the power supply or the fan. Note For the RP, FP, CC, and SPA modules, the entStateOper attribute is set to D_entStateOper_enabled if the module is up. Else, the entStateOper attribute is set to D_entStateOper_disabled.

ETHER-WIS (RFC 3637)

The ETHER-WIS (RFC 3637) MIB contains objects to manage application details for the Ethernet WAN Interface Sublayer (WIS).

MIB Constraints

Table 3-90 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the ETHER-WIS (RFC 3637) MIB.

ETHER-WIS (RFC 3637) MIB Constraints

MIB Object Notes
etherWisDeviceTable Not supported.
etherWisSectionCurrentTable Not supported.
etherWisFarEndPathCurrentTable Not supported.

ETHERLIKE-MIB (RFC 3635)

The ETHERLIKE-MIB contains objects to manage Ethernet-like interfaces. Cisco IOS Release 12.2(18)SXF and Cisco IOS Release 12.2(33)SRA support the RFC 2665 version of the MIB. Cisco IOS Release 12.2(33)SRB supports the RFC 3635 version of the MIB.

Note Effective from Cisco IOS Release 15.3(1)S, the ETHERLIKE-MIB is supported on the Cisco ASR1000: 40G Native Ethernet Line Card.

ETHERLIKE-MIB Constraints

MIB Object Notes
dot3CollTable Not implemented.
dot3ControlTable Not implemented.
dot3Control Not implemented.
dot3PauseAdminMode Read only.

EVENT-MIB (RFC 2981)

The EVENT-MIB (RFC 2981) contains objects to define event triggers and actions for network management purposes.

EXPRESSION-MIB

The EXPRESSION-MIB (RFC 2982) contains objects to define the expressions of MIB objects for network management purposes.

FRAME-RELAY-DTE-MIB (RFC1315-MIB)

The FRAME-RELAY-DTE-MIB (RFC1315-MIB) contains objects to manage a Frame Relay data terminal equipment (DTE) interface, which consists of a single physical connection to the network with many virtual connections to other destinations and neighbors. The MIB contains the objects used to manage: • The Data Link Connection Management Interface (DLCMI) • Virtual circuits on each Frame Relay interface • Errors detected on Frame Relay interfaces

MIB Constraints

Table 3-92 lists the constraints that the router places on the objects in the RFC1315-MIB.

FRAME-RELAY-DTE-MIB Constraints

MIB Object Notes
frDlcmiTable

• frDlcmiAddress • frDlcmiAddressLen

Always q922November90(3), which indicates a 10-bit DLCI.

Always two-octets(2).

frCircuitTable

• frCircuitCommittedBurst • frCircuitExcessBurst • frCircuitThroughput

Normally, the QoS configuration entered through the

Modular QoS CLI (MQC) syntax does not appear in these frCircuitTable objects. However, when QoS is configured through the MQC and the following conditions are met, these frCircuitTable objects contain the QoS values as they are entered through the MQC: • The default class is configured on the policy-map only. • An output policy is attached to the Frame Relay (FR) Permanent Virtual Circuit (PVC). • The Cisco class-based-QoS (CBQ) enhancement only supports two MQC actions: police cir and shape. • If both police cir and shape actions exist, then the FR traffic-shaping QoS takes precedence before policing.

frCircuitState

• frErrTable

Not supported.


HC-ALARM-MIB

The HC-ALARM-MIB defines Remote Monitoring MIB extensions for High Capacity Alarms.

MIB Tables

Table 3-93 lists the tables in HC-ALARM-MIB.

HC-ALARM-MIBTables

MIB Table Description
hcAlarmTable A list of entries for the configuration of high capacity alarms.

IEEE8023-LAG-MIB

The IEEE 8023-LAG- MIB is the Link Aggregation module for managing IEEE Std 802.3ad.

IF-MIB (RFC 2863)

The IF-MIB (RFC 2863) describes the attributes of physical and logical interfaces (network interface sublayers). The router supports the ifGeneralGroup of MIB objects for all layers (ifIndex, ifDescr, ifType, ifSpeed, ifPhysAddress, ifAdminStatus, ifOperStatus, ifLastChange, ifName, ifLinkUpDownTrapEnable, ifHighSpeed, and ifConnectorPresent). One of the most commonly used identifiers in SNMP-based network management applications is the Interface Index (ifIndex) value. IfIndex is a unique identifying number associated with a physical or logical interface. • The IF-MIB supports the Circuit Emulation (CEM) only on the SPA-1CHOC3-CE-ATM. For each controller, only a single CEM interface is supported bacause it is being used for l1/l2 forwarding. • Multiple sublayers are not supported for the SPA-1CHOC3-CE-ATM from SNMP. Hence, the layers corresponding to digital signal layer 1 (DS1), Synchronous Transport Signal (STS), and Virtual Tributary (VT) are not modeled for the CE interface.

Note Effective from Cisco IOS Release 15.1(3)S, IF-MIB is supported on SPA-24CHT1-CE-ATM and SPA-2CHT3-CE-ATM.

Note The ifInDiscards, ifInErrors, ifInUnknownProtos, ifOutDiscards, and ifOutErrors IF-MIB objects are not supported for Gigabit subinterfaces.

Note Effective from Cisco IOS Release 15.3(1)S, the IF-MIB is supported on the Cisco ASR1000: 40G Native Ethernet Line Card and SPA-8XT3/E3.

Note The Cisco ASR1000: 40G Native Ethernet Line Card 2x10GE + 20x1GE supports a total number of 22 ports. Interface numbering is continuous from 0-19 for GE ports and 20-21 for 10GE ports. You can configure interface GigabitEthernet 0/0/x as well as TenGigabitEthernet 0/0/y at the same time, where x = 0 till 19 and y = 20 and 21)

MIB Constraints

Table 3-94 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the IF-MIB.

IF-MIB Constraints

MIB Objects Notes
ifOutErrors Not supported for ATM subinterfaces.
ifPromiscuousMode Read only.
ifStackStatus Read only.

Note To define a Virtual port of a service engine connecting the RP and SE, set the value of ifType to ethernetCsmacd and ifDescr to Service-Engine. The physical port of the SPA is not controlled by the router, the router controls the virtual port of the SPA. This interface is named using in Service-Engine 1/1/0 command and functions as a Gigabit Ethernet Interface. Since, a sub-interface can not be created on this interface, ifStackTable is not implemented.

Note The valueof ifLastChange is always 0 for VT layer in SPA-1xCHSTM1/OC3.

IGMP-STD-MIB (RFC 2933)

The IGMP-STD-MIB(RFC 2933) manages Internet Group Management Protocol (IGMP).

IP-FORWARD-MIB (RFC 4292)

The IP-FORWARD-MIB (RFC 4292) contains objects to control the display of Classless Interdomain Routing (CIDR) multipath IP Routes.

MIB Constraints

Table 3-95 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the IP-FORWARD-MIB.

IF-MIB Constraints

MIB Objects Notes
inetCidrRouteTable Implemented for IPv6 only.

IP-MIB (RFC 4293)

The IP-MIB (RFC 4293) module contains objects for managing IP and Internet Control Message Protocol (ICMP) implementations, but excluding their management of IP routes.

Note The IP-MIB supports both IPv4 and IPv6 networks.

IPMROUTE-STD-MIB (RFC 2932)

The IPMROUTE-STD-MIB (RFC 2932) contains objects to manage IP multicast routing, but independent of the specific multicast routing protocol in use.

MIB Constraints

Table 3-96 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the IPMROUTE-STD-MIB.

IPMROUTE-STD-MIB Constraints

MIB Objects Notes
ipMRouteScopeNameTable Not implemented.
ipMRouteEnable Read only.
ipMRouteInterfaceTtl Read only.
ipMRouteInterfaceRateLimit Read only.

MPLS-L3VPN-STD-MIB (RFC 4382)

The MPLS-L3VPN-STD-MIB contains managed object definitions for the Layer-3 Multiprotocol Label Switching Virtual Private Networks. This MIB is based on RFC 4382 specification.

MPLS-LDP-GENERIC-STD-MIB (RFC 3815)

The MPLS-LDP-GENERIC-STD-MIB (RFC 3815) contains managed object definitions for configuring and monitoring the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP), utilizing ethernet as the Layer 2 media.

MPLS-LDP-STD-MIB (RFC 3815)

The MPLS-LDP-STD-MIB (RFC 3815) contains managed object definitions for the Multiprotocol Label Switching (MPLS) and Label Distribution Protocol (LDP) document.

MPLS-LSR-STD-MIB (RFC 3813)

The MPLS-LSR-STD-MIB (RFC 3031) contains managed object definitions for the Multiprotocol Label Switching (MPLS) router.

MPLS-TE-MIB

The MPLS-TE-MIB enables the Cisco ASR 1000 Series Routers to perform traffic engineering for MPLS tunnels. The MIB is based on Revision 05 of the IETF MPLS-TE-MIB.

Traffic engineering support for MPLS tunnels requires the following configuration:

• Setting up MPLS tunnels with appropriate configuration parameters. • Configuring tunnel loose and strict source routed hops.

MIB Constraints

Table 3-97 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the MPLS-TE-MIB.

IPMROUTE-STD-MIB Constraints

MIB Objects Notes
mplsTunnelIndexNext Read only. Always 0.
mplsTunnelTable

• mplsTunnelName • mplsTunnelDescr • mplsTunnelIsif • mplsTunnelXCPointer • mplsTunnelSignallingProto • mplsTunnelSetupPrio • mplsTunnelHoldingPrio • mplsTunnelSessionAttributes • mplsTunnelOwner Read only. • mplsTunnelLocalProtectInUse • mplsTunnelResourcePointer • mplsTunnelInstancePriority • mplsTunnelHopTableIndex • mplsTunnelIncludeAnyAffinity • mplsTunnelIncludeAllAffinity • mplsTunnelExcludeAllAffinity • mplsTunnelPathInUse • mplsTunnelRole • mplsTunnelTotalUpTime • mplsTunnelInstanceUpTime • mplsTunnelAdminStatus • mplsTunnelRowStatus • mplsTunnelStorageType

Read only.

Read only. Read only. Read only. Read only. Read only. Always 7. Read only. Always 7. Read only. Read only. Read only. Always false(2). Read only. Read only. Always 0. Read only. Read only. Always 0. Read only. Read only. Read only. Read only. Read only. Read only. Always 0. Read only. Read only. Always readOnly(5). Read only. Volatile(2). Always active.

mplsTunnelHopListIndexNext Read only. Always 0.
mplsTunnelHopTable

• mplsTunnelHopAddrType • mplsTunnelHopIpv4Addr • mplsTunnelHopIpv4PrefixLen • mplsTunnelHopIpv6Addr • mplsTunnelHopIpv6PrefixLen • mplsTunnelHopAsNumber • mplsTunnelHopLspId • mplsTunnelHopType • mplsTunnelHopRowStatus • mplsTunnelHopStorageType

Read only. Always ipv4(1).

Read only. Read only. Always 32. Read only. NULL. Read only. Always 0. Read only. Read only. Read only. Always strict(1). Read only. Always active(1). Read only. Value is readOnly(5).

mplsTunnelResourceIndexNext Read only. Always 0.
mplsTunnelResourceTable

• mplsTunnelResourceMaxRate • mplsTunnelResourceMeanRate • mplsTunnelResourceMaxBurstSize • mplsTunnelResourceRowStatus

Read only.

Read only. Read only. Read only. Always active(1).

mplsTunnelResourceStorageType Read only. Value is readOnly(5).

Notes: The mplsTunnelTable allows new MPLS tunnels to be created between an MPLS LSR and a remote endpoint and existing tunnels to be reconfigured or removed. The Cisco ASR 1000 Series Routers support point-to-point tunnel segments, although multipoint-to-point and point-to-multipoint connections are supported by an LSR acting as a cross-connect. Each MPLS tunnel can have one out-segment originating at an LSR and one in-segment terminating at that LSR. The mplsTunnelTable is enhanced by the mplsTunnelPerfTable that provides several counters to measure the performance of the MPLS tunnels. The mplsTunnelResourceTable indicates the resources required for a tunnel. Multiple tunnels can share the same resources by pointing to the same entry in this table. Tunnels that do not share resources must point to separate entries in this table. The mplsTunnelHopTable indicates strict or loose hops for an MPLS tunnel defined in mplsTunnelTable when you establish the hop using signaling. Multiple tunnels share the same hops by pointing to the same entry in this table. Each row also has a secondary index, mplsTunnelHopIndex, corresponding to the next hop of this tunnel. The scalar mplsTunnelMaxHops indicates the maximum number of hops that you can specify on each tunnel supported by this LSR. The mplsTunnelARHopTable indicates the actual hops crossed by a tunnel as reported by the MPLS signaling protocol after the tunnel is set up. There are three notifications in this MIB. The notifications mplsTunnelUp and mplsTunnelDown indicate that the value of mplsTunnelOperStatus has transitioned to up(1) or down(2). The notification mplsTunnelRerouted is generated when a tunnel is rerouted or re-optimized.

MPLS-VPN-MIB

The MPLS-VPN-MIB: • Describes managed objects for modeling a Multiprotocol Label Switching/Border Gateway Protocol virtual private network • Configures and monitors routes and route targets for each VRF instance on a router • Facilitates provisioning VPN Routing and Forwarding (VRF) instances on MPLS interfaces • Measures the performance of MPLS/BGP VPNs The MIB is based on Revision 05 of the IETF MPLS-VPN-MIB.

MIB Constraints

Table 3-98 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the MPLS-VPN-MIB.

MPLS-VPN-MIB Constraints

MIB Objects Notes
mplsNumVrfSecViolationThreshExceeded Not implemented.
mplsVpnVrfSecTable

• mplsVpnVrfSecIllegalLabelViolations • mplsVpnVrfSecIllegalLabelRcvThresh

Read only. Always 0. Read only. Always 0.
mplsVpnVrfTable

• mplsVpnVrfConfRowStatus • mplsVpnVrfConfStorageType • mplsVpnVrfConfMidRouteThreshold • mplsVpnVrfConfHighRouteThreshold • mplsVpnVrfConfMaxRoutes • mplsVpnVrfConfMaxPossibleRoutes • mplsVpnVrfDescription • mplsVpnInterfaceVpnClassification

Read only.

Read only. Volatile(2). Read only. Read only. Read only. Read only. Always 0. Read only. Read only.

mplsVpnInterfaceConfTable

• mplsVpnInterfaceConfStorageType • mplsVpnInterfaceConfRowStatus Values: active(1), notInService(2). • mplsVpnInterfaceLabelEdgeType

Read only. Volatile(2).

Read only. Read only. providerEdge(1).

mplsVpnVrfRouteTargetTable

• mplsVpnVrfRouteTargetRowStatus

Read only. Values: active(1), notInService(2).
mplsVpnVrfBgpNbrAddrTable

• mplsVpnVrfBgpNbrRowStatus • mplsVpnVrfBgpNbrRole • mplsVpnVrfBgpNbrType • mplsVpnVrfBgpNbrAddr • mplsVpnVrfBgpNbrStorageType

Read only. Values: active(1), notInService(2).

Read only. providerEdge(1). Read only. Read only. Read only. Volatile(2).

mplsVpnVrfRouteTable

• mplsVpnVrfRouteInfo • mplsVpnVrfRouteTarget • mplsVpnVrfRouteTargetDescr • mplsVpnVrfRouteDistinguisher • mplsVpnVrfRouteNextHopAS • mplsVpnVrfRouteRowStatus • mplsVpnVrfRouteStorageType • mplsVpnVrfRouteDestAddrType • mplsVpnVrfRouteMaskAddrType • mplsVpnVrfRouteTos • mplsVpnVrfRouteNextHop • mplsVpnVrfRouteNextHopAddrType • mplsVpnVrfRouteifIndex • mplsVpnVrfRouteType • mplsVpnVrfRouteProto

Read only. Value nullOID.

Read only. Determines the route distinguisher for this target. Description of the route target. Currently this object is not supported in this Cisco IOS release. Therefore, the object is the same as mplsVpnVrfRouteTarget. Read only. Read only. Always 0. Read only. This object normally reads active(1), but may read notInService(2), if a VRF was recently deleted. Read only. Volatile(2). Read only. Read only. Read only. Always 0. Read only. Read only. Read only. Read only. Read only.

mplsVpnVrfBgpNbrPrefixTable Not implemented.

Notes: The mplsVpnVrfConfTable represents all the MPLS/BGP VPNs configured. The NMS configures an entry in this table for each MPLS/BGP VPN configured to run in this MPLS domain. The mplsVPNInterfaceConfTable extends the interface MIB to provide specific MPLS/BGP VPN information on MPLS/BGP VPN-enabled interfaces. The mplsVPNPerfTable enhances the mplsVpnVrfConfTable to provide performance information. The mplsVpnVrfRouteTable and the mplsVpnRouteTargetTable facilitate the configuration and monitoring of routes and route targets, respectively, for each VRF instance.

MSDP-MIB

The MSDP-MIB contains objects to monitor the Multicast Source Discovery Protocol (MSDP). The MIB can be used with SNMPv3 to remotely monitor MSDP speakers. For more information about this MIB, see its feature module description at the following URL: http://www.cisco.com/en/US/docs/ios/12_1t/12_1t5/feature/guide/dt5msdp.html



NAT-MIB

Network address translation (NAT) is a methodology of remapping one IP address space into another by modifying network address information in Internet Protocol (IP) datagram packet headers while they are in transit across a traffic routing device. The NAT-MIB helps in providing these translation details.

MIB Constraints

The below Table lists the constraints for the objects in the NAT-MIB.


Note - Traps are not implemented


NAT-MIB Constraints

MIB Objects Notes
natDefTimeouts Not supported.
natNotifCtrl Not supported.
natInterfaceServiceType Not supported.
natAddrBindCurrentIdleTime Not supported.
natAddrMapTable Not supported.
natAddrBindInTranslates Not supported.
natAddrBindOutTranslates Not supported.
natAddrPortBindTable Not supported.
natSessionTable Not supported.
natProtocolTable Not supported.
natInstanceTable Not supported.
natLimitsTable Not supported.



NHRP-MIB

The Cisco NHRP MIB feature introduces support for the NHRP MIB, which helps to manage and monitor the Next Hop Resolution Protocol (NHRP) through the Simple Network Management Protocol (SNMP). Statistics can be collected and monitored through standards-based SNMP techniques (get operations) to query objects defined in the NHRP MIB. The NHRP MIB is VRF-aware and supports VRF-aware queries. For more information about this MIB, refer: http://www.cisco.com/en/US/docs/ios/sec_secure_connectivity/configuration/guide/sec_dmvpn_nhrp_ mib.html

MIB Constraints

Table 3-99 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the NHRP-MIB.

NHRP-MIB Constraints

MIB Objects Notes
nhrpClientNbmaSubaddr Not implemented.
nhrpClientNhsNbmaSubaddr Not implemented.
nhrpServerNbmaSubaddr Not implemented.
nhrpServerNhcNbmaSubaddr Not implemented.
nhrpCachePreference Not implemented.
nhrpClientDefaultMtu Not implemented.
nhrpCacheNegotiatedMtu Not implemented.
nhrpPurgePrefixLength Not implemented.
nhrpCacheNbmaSubaddr Not supported.
nhrpCacheType

• atmarp(7) N • scsp(8)

Not supported.

Not supported.

NOTIFICATION-LOG-MIB (RFC 3014)

The NOTIFICATION-LOG-MIB contains objects for logging SNMP notifications; that is, traps and informs types of notifications.

OLD-CISCO-CHASSIS-MIB

The OLD-CISCO-CHASSIS-MIB describes chassis objects in a device running an old implementation of the Cisco IOS operating system. The chassis objects are now described in the ENTITY-MIB, and OLD-CISCO-CHASSIS-MIB is not supported for Cisco ASR 1000 Series Routers.

OLD-CISCO-SYS-MIB

The OLD-CISCO-SYS-MIB defines objects to manage the system bootstrap description and the corresponding version identification. Note Currently, only the whyReload object is supported in this MIB.

OSPF-MIB (RFC 1850)

The OSPF-MIB (RFC 1850) contains objects that describe the OSPF Version 2 Protocol. The RFC1253-MIB corresponds to the OSPF-MIB (Open Shortest Path First [OSPF] protocol).

OSPF-TRAP-MIB (RFC 1850)

The OSPF-TRAP-MIB (RFC 1850) contains objects that describe traps for the OSPF Version 2 Protocol.

PIM-MIB (RFC 2934)

The PIM-MIB (RFC 2934) contains objects to configure and manage Protocol Independent Multicast (PIM) on the router. The MIB is extracted from RFC 2934.

MIB Constraints

Table 3-100 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the PIM-MIB.

PIM-MIB Constraints

MIB Objects Notes
pimIpMRouteTable Not implemented.
pimIpMRouteNextHopTable Not implemented.
pimInterfaceTable

• pimInterfaceMode • pimInterfaceHelloInterval • pimInterfaceStatus • pimInterfaceJoinPruneInterval • pimInterfaceCBSRPreference

Read only.

Read only. Read only. Read only. Read only.

pimJoinPruneInterval Read only.
pimCandidateRPTable

• pimCandidateRPAdressd • pimCandidateRPRowStatus

Read only.

Read only.

pimComponentTable

• pimComponentCRPHoldTime • pimComponentStatus

Read only.

Read only.

RFC1213-MIB

The RFC1213-MIB defines the second version of the Management Information Base (MIB-II) for use with network-management protocols in TCP-based internets. This RFC1213-MIB includes the following groups : • system • interfaces • at • ip • icmp • tcp • udp • igmp • transmission • snmp

Note For more information, refer to the latest RFCs specified in the RFC-1213-MIB. RMON-MIB (RFC 1757)

The RMON-MIB (RFC 1757) contains objects to remotely monitor devices in the network.

MIB Constraints

Only alarm and event groups are supported in Cisco ASR 1000 Series Routers. RSVP-MIB

The RSVP-MIB contains objects to manage the Resource Reservation Protocol (RSVP).

MIB Constraints

Table 3-101 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the RSVP-MIB.

RSVP-MIB Constraints

MIB Objects Notes
rsvpIfRefreshBlockadeMultiple

rsvpIfRefreshMultiple

Read only.

Read only.

rsvpIfTTL Read only.
rsvpIfRefreshInterval Read only.
rsvpIfRouteDelay Read only.
rsvpIfUdpRequired Read only.


SNMP-COMMUNITY-MIB (RFC 2576)

The SNMP-COMMUNITY-MIB (RFC 2576) contains objects that help support coexistence among SNMPv1, SNMPv2c, and SNMPv3.

SNMP-FRAMEWORK-MIB (RFC 2571)

The SNMP-FRAMEWORK-MIB (RFC 2571) contains objects that describe the SNMP management architecture. There are no constraints on this MIB.

SNMP-MPD-MIB (RFC 2572)

The SNMP-MPD-MIB (RFC 2572) contains objects for Message Processing and Dispatching (MPD). SNMP-NOTIFICATION-MIB (RFC 2573)

The SNMP-NOTIFICATION-MIB (RFC 2573) contains managed objects for SNMPv3 notifications. The MIB also defines a set of filters that limit the number of notifications generated by a particular entity (snmpNotifyFilterProfileTable and snmpNotifyFilterTable). Objects in the snmpNotifyTable are used to select entities in the SNMP-TARGET-MIB snmpTargetAddrTable and specify the types of SNMP notifications those entities are to receive.

SNMP-PROXY-MIB (RFC 2573)

The SNMP-PROXY-MIB (RFC 2573) contains managed objects to remotely configure the parameters used by an SNMP entity for proxy forwarding operations. The MIB contains a single table, snmpProxyTable, which defines the translations to use to forward messages between management targets.


SNMP-TARGET-MIB (RFC 2573)

The SNMP-TARGET-MIB (RFC 2573) contains objects to remotely configure the parameters used by an entity to generate SNMP notifications. The MIB defines the addresses of entities to send SNMP notifications to, and contains a list of tag values that are used to filter the notifications sent to these entities (see the SNMP-NOTIFICATION-MIB).

SNMP-USM-MIB (RFC 2574)

The SNMP-USM-MIB (RFC 2574) contains objects that describe the SNMP user-based security model. SNMPv2-MIB (RFC 1907)

The SNMPv2-MIB (RFC 1907) contains objects to manage SNMPv2 entities. The SNMPv2-MIB contains the following mandatory object groups:

• SNMP group—Collection of objects providing basic instrumentation and control of an SNMP entity. • System group—Collection of objects common to all managed systems. • snmpSetGroup—Collection of objects that allow several cooperating SNMPv2 entities, all acting in a manager role, to coordinate their use of the SNMPv2 set operation. • snmpBasicNotificationsGroup—The two notifications are coldStart and authenticationFailure, which an SNMPv2 entity is required to implement.


SNMP-VIEW-BASED-ACM-MIB (RFC 2575)

The SNMP-VIEW-BASED-ACM-MIB (RFC 2575) contains objects that describe the view-based access control model for SNMP. Note To access the SNMP-VIEW-BASED-ACM-MIB, you must create an SNMPv3 user with access to a view that includes all of the information from the Internet subtree. For example: Router(config)# snmp-server view abcview internet included Router(config)# snmp-server group abcgroup v3 noauth read abcview write abcview notify abcview Router(config)# snmp-server user abcuser abcgroup v3

SONET-MIB (RFC 2558)

The SONET-MIB (RFC 2558) provides both the configuration and performance monitoring objects for the SONET interfaces.

Note The ASR 1000 Series Routers use GR253 standards for SES calculation for path/line/section. Hence, the SNMP query for sonetSESthresholdSet will return ansi1993(3).

Note The SONET-MIB is not supported on SPA-1X10GE-WL-V2 although the SONET alarms listed in Table 3-20 are supported for the Ethernet WIS Port.

MIB Constraints

Table 3-102 lists the constraints that the Cisco ASR 1000 Series Routers place on the objects in the SONET-MIB.

SONET-MIB Constraints

MIB Objects Notes
sonetPathCurrentTable

• sonetPathCurrentWidth

Read only.
sonetVTCurrentTable Not implemented.
sonetVTIntervalTable Not implemented.
sonetFarEndVTCurrentTable Not implemented.
sonetFarEndVTIntervalTable Not implemented.
SonetMediumTable

• sonetMediumLineCoding • sonetMediumLineType • sonetMediumCircuitIdentifier • sonetMediumLoopbackConfig

Read only.

Read only. Read only. Read only.

sonetSESthresholdSet Read only.

When the SONET path is initialized and no active alarms exist, the value of sonetPathCurrentStatus object is zero.

Note If an alarm is triggered and cleared, the value of sonetPathNoDefect object is one.

TCP-MIB (RFC 4022)

The TCP-MIB (RFC 4022) contains objects to manage the Transmission Control Protocol (TCP) implementations on the router.

TUNNEL-MIB (RFC 4087) The TUNNEL-MIB contains objects to manage IP Tunnels independent of the encapsulation scheme in use.

UDP-MIB (RFC 4113)

The UDP-MIB (RFC4113) contains objects to manage the User Datagram Protocol (UDP) on the router. There are no constraints.

Rating: 0.0/5 (0 votes cast)

Personal tools