Table Of Contents
Release Notes for Cisco 12000/10720 v3.1.2
Router Manager
Contents
Introduction
Cisco 12000/10720 Router Manager Features
New Features in Cisco 12000/10720 v3.1.2 Router Manager
System Requirements
Software Compatibility
Determining the Software Version
Version Supported
GRP and Router Processors
Line Cards Supported by Cisco 12000 Series Router Manager
ATM Line Cards Supported by Cisco 12000 Series Router Manager
ATM Line Cards Not Yet Supported by Cisco 12000 Series Router Manager
POS Line Cards Supported by Cisco 12000 Series Router Manager
POS Line Cards Not Yet Supported by Cisco 12000 Series Router Manager
Ethernet Line Cards Supported by Cisco 12000 Series Router Manager
DS-3 Line Cards Supported by Cisco 12000 Series Router Manager
E3 Line Cards Supported by Cisco 12000 Series Router Manager
SRP Line Cards Supported by Cisco 12000 Series Router Manager
SRP Line Cards Not Supported by Cisco 12000 Series Router Manager
Channelized Line Cards Supported by Cisco 12000 Series Router Manager
Channelized Line Cards Not Supported by Cisco 12000 Series Router Manager
Line Cards Supported by Cisco 10720 Routers
SRP Line Cards Supported by Cisco 10720 Routers
Ethernet Line Cards Supported by Cisco 10720 Routers
Manually Deploying Supporting Modules
Cisco 12000/10720 Router Manager Alarms
Threshold Alarms
Known Limitations in this Release
Caveats
Cisco EMF Issues
Cisco 12000/10720 Router Manager Issues
Routing Issues
MPLS/VRF Issues
IOS Issues
Documentation Updates
Setting Up a Cisco 12000/10720 Router Manager and C-NOTE Co-resident Installation to Receive SNMP Traps
Backing Up a C-NOTE/Element Manager Co-resident Installation
Device in RME Not Responding
Configuring a PVC Under a Sub-interface
Updates to the Cisco EMF 12000/10720 Router Manager User Guide
Chapter 3
Chapter 4
Reload
Chapter 5
Reload
Chapter 12
Chapter 14
Chapter 14
Chapter 14
Chapter 18
Related Documentation
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Cisco TAC Web Site
Cisco TAC Escalation Center
Release Notes for Cisco 12000/10720 v3.1.2
Router Manager
Contents
This document contains the following information:
•
Introduction
•Cisco 12000/10720 Router Manager Features
•New Features in Cisco 12000/10720 v3.1.2 Router Manager
•System Requirements
•Software Compatibility
•GRP and Router Processors
•Line Cards Supported by Cisco 12000 Series Router Manager
•Cisco 12000/10720 Router Manager Alarms
•Known Limitations in this Release
•Caveats
•Documentation Updates
•Related Documentation
•Obtaining Documentation
•Obtaining Technical Assistance
Introduction
Cisco 12000/10720 Router Manager is an Element Manager (EMS) that works in conjunction with the Cisco Element Management Framework (Cisco EMF) to enable service providers to plan, provision, configure, and monitor network services on Cisco 12000/10720 Routers. Cisco 12000/10720 Router Manager is designed to meet the operator business requirements for the control and operation of the Cisco 12000/10720 Routers. Cisco 12000/10720 Router Manager eases and accelerates device deployment and enables efficient operation of Cisco 12000/10720 Router network environments; for example, by supporting MPLS troubleshooting for efficient maintenance of Cisco 12000 and 10720 Router based services.
Cisco 12000/10720 Router Manager Features
Cisco 12000/10720 Router Manager features include the following:
•Maps for Chassis representation of Cisco 12000/10720 Router objects
•Cisco 12000/10720 Router Manager windows and wizards—Eliminate the need for operators to have detailed Cisco IOS software and SNMP-based knowledge for individual interface or system parameter commands
•Cisco 12000/10720 Router Manager deployment—eases deployment of large networks by enabling template-based element configuration, operations, administration, and maintenance
–Pre-deployment of chassis, GRP and line cards
–AutoDiscovery—Automatically discovers existing Cisco 12000/10720 Routers
•Comprehensive fault management system—for chassis, line cards and interfaces
•Configuration Backup/Restore using RME—Uses Resource Manager Essentials to back up and save the running configuration of a device and its modules so that if a hardware failure occurs, you can restore configuration
•Configuration Editor—Uploads and saves the running configuration on a device after editing
•Configuration operations—Performs in bulk to numerous Cisco 12000/10720 Routers
•Cisco 12000/10720 Router Manager Management—Fault, Configuration, Accounting and Performance (FCAP) Element Management of Cisco 12000 series Routers using Cisco EMF windows
•Interface profiles—Enables you to apply the same parameters to a large number of objects at one time
•Layer 3 QoS support—Includes Committed Access Rate (CAR), Weighted Random Early Detection (WRED), WRED ToFab and Modified Deficit Round Robin (MDRR)
•Line cards and interfaces— Supports various line cards and interfaces, such as packet-over-SONET (POS), Asynchronous Transfer Mode (ATM), Digital Signal 3 (DS3), Dynamic Packet Transport (DPT), Spatial Reuse Protocol (SRP) and Gigabit and Fast Ethernet
•Cisco IOS releases—Easily downloads new software releases from Cisco 12000/10720 Router Manager onto devices using RME
•ATM Connections Management—Uploads existing PVCs and associated QoS profiles from any device into the Cisco 12000/10720 Router Manager and also manual deployment and management of PVCs and SVCs
•Subchassis discovery—Determines the physical chassis contents, such as line cards and interfaces
•Rediscover Line Cards after online insertion or removal (OIR)
•BGP and OSPF Protocols Management— Configuration and Fault Management for BGP and OSPF routing protocols and uploading BGP Address Family configurations
•Route Processor Redundancy (GRP and PRP) support for chassis management
•Complete support for IP Routing, TCP and UDP Status Management
•MPLS Management—Fault Management and Performance Management for MPLS Interfaces and Sub-Interfaces, Fault Management for LDP Entities and MPLS Tunnels, Configuring MPLS and VRF Traps
•VRF Management—Configuration of VRFs in the EM. Creation of VRFs in the device through EM and Association of VRFs to Interfaces. Fault Management for VRFs
•VLAN Management—Configuration and performance monitoring of the VLAN sub-interfaces
•VLAN Synchronization—Uploads the existing VLAN information from the network into Cisco 12000/10720 Router Manager
•Reload menu option—Reboot any selected 12000 Router Chassis and 12000 Router Modules
Cisco 12000/10720 Router Manager delivers these management functions within Cisco EMF. Cisco EMF provides consistency across a common user interface, operational event management, auto map building, and common data management for various Cisco element managers. Cisco EMF also provides a robust foundation and toolkit for building scalable CORBA-based provisioning integration modules for customer-specific Operational Support System (OSS) environments.
Cisco 12000/10720 Router Manager and Cisco EMF are part of the Cisco Service Management (CSM) suite, a strategic component of Cisco's products and solutions for New World Operations.
Note Cisco 12000/10720 Router Manager can co-reside with Cisco 7000 Series Manager v2.0, Cisco Access Router Manager v1.1, Cisco Catalyst Switch Manager v3.0 and Cisco Universal Gateway Manager v2.1. A programme of inter-operability testing continues and customers should contact Cisco to determine if they can load Cisco 12000/10720 Router Manager with another EM on the same Cisco EMF system.
Note Not all the dialogs (GUIs) provided by the Cisco 12000/10720 Router Manager are in sync with the device when launched. The details of the dialogs that are in sync and of those that are not are provided is available in the Appendix B of the Cisco 12000/10720 v3.1.1 Router Manager User Guide.
New Features in Cisco 12000/10720 v3.1.2 Router Manager
Release 3.1.2 of Cisco 12000/10720 Router Manager adds the following functionality to release 3.1.1:
•Support for Frost Card Management:
–Channelized OC3/STM1->DS1/E1, 2 ports Intermediate Reach (2CHOC3/STM1-IR-SC)
Note Other channelized line cards are not supported.
•Service Menu option to reboot any selected 12000 Router Chassis and 12000 Router Modules
System Requirements
The details for the system requirements are available in the "Before You Start Your Installation" chapter of Cisco 12000/10720 v3.1.1 Router Manager Installation and Configuration Guide.
Software Compatibility
This software release has been tested on release 2.6/2.8 of the Solaris operating environment, for Sun SPARC workstations, and for Year 2000 Compliance.
Table 1 details software compatibility for Cisco 12000/10720 v3.1.2 Router Manager.
Table 1 Software Compatibility for Cisco 12000/10720 v3.1.2 Router Manager
Compatibility
|
•Cisco EMF 3.2, CEMF_3.2_PATCH_7
•Supports Cisco 12000 series Routers with Cisco IOS releases: 12.0(19)S, 12.0(19)ST1, 12.0(21)S1, 12.0(21)ST1, 12.0(22)S, 12.0(23)S, 12.0(24)S, S 12.0(24)S1, 12.0(24)S2, 12.0(24.4)S, 12.0(25)S, 12.0(25.3), 12.(0)23S3 and 12.(0)24S3.
•Supports Cisco 10720 Router with Cisco IOS releases: 12.0(21)SP1, 12.0(22.4)S, 12.0(23)S and 12.0(24)S
•Cisco 12000/10720 Manager runs on Sun® hardware running Solaris operating environment 2.6/2.8
|
Chassis Support
|
•Cisco 12416, Cisco 12410, Cisco 12406, Cisco 12404, Cisco 12016, Cisco 12012, Cisco 12008 and YB 10720
|
Line Card Support
|
•See Line Cards Supported by Cisco 12000 Series Router Manager. Also refer to the "Manually Deploying Line Cards" section in the Cisco 12000/10720 Router Manager User Guide for the list of linecards supported in Release 3.1.2.
|
Determining the Software Version
To determine installed Cisco EMF packages, and version numbers, use the Cisco EMF command:
<CEMF_ROOT>/bin/cemf install -show
Note <CEMF_ROOT> is the convention adopted in Cisco EMF documentation to indicate the installation directory for Cisco EMF and the Cisco 12000/10720 Router Manager software. This default location is /opt/cemf.
Version Supported
For this Cisco 12000/10720 v3.1.2 Router Manager release, the following components must be installed:
•Cisco EMF v3.2 Service Pack 7
•CiscoWorks Common Services 2.2 and Resource Manager Essentials 3.5
GRP and Router Processors
Table 2 GRP and Router Processors
Product Part Number
|
Cisco 12000/10720 Router Manager Menu Option
|
Card Description
|
GRP-B
|
RP>GRP
|
Route Processor, 128MB and 20MB Flash, ECC support
|
GRP-B/R
|
RP>GRP
|
12000 Router Route Processor, Redundant Option
|
PRP-1
|
RP>NGRP
|
Cisco 12000 Series Performance Route Processor
|
PRP-1/R
|
RP>NGRP
|
Redundant PRP-1 chassis upgrade option, factory only
|
Line Cards Supported by Cisco 12000 Series Router Manager
ATM Line Cards Supported by Cisco 12000 Series Router Manager
Table 3 ATM Line Cards Supported by Cisco 12000 Series Router Manager
Card Type
|
Product Part Number
|
Cisco 12000/10720 Router Manager Menu Option
|
Card Description
|
atm-qoc3-sm
|
4OC3/ATM-SM-SC
|
ATM>OC-3 4>SM
|
4 Port OC3 ATM Single Mode (SM) Line Card
|
atm-qoc3-mm
|
4OC3/ATM-MM-SC
|
ATM>OC-3 4>MM
|
4 Port OC3 ATM Multi Mode (MM) Line Card
|
gsr-en-8oc3
|
8OC03/ATM/TS-MM-B (8xOC3c/STM1c ATM/TS)
8OC03/ATM/TS-IR-B (8xOC3c/STM1c ATM/TS)
|
ATM>OC-3-8>SM
|
GSR enhanced 8 port OC3c/STM-1 ATM Line Card
|
sr-atm-en-8oc3-mm
|
|
ATM>OC-3-8>MM
|
GSR enhanced 8 port OC3c/STM-1 Multimode ATM Line Card
|
atm-oc12-sm
|
LC-1OC12/ATM-SM
|
ATM>OC-12 1>SM
|
Single Port OC-12 Single Mode (SM) Line Card
|
atm-oc12-mm
|
LC-1OC12/ATM-MM
|
ATM>OC-12 1>MM
|
Single Port OC-12 Multi Mode (MM) Line Card
|
gsr-qoc12-sm
|
4OC12/ATM-IR-SC
|
ATM>OC-12 4> SM
|
4 port OC12 ATM Single Mode (SM) Line Card
|
gsr-qoc12-mm
|
4OC12/ATM-MM-SC
|
ATM>OC-12 4>MM
|
4 port OC12 ATM Multi Mode (MM) Line Card
|
gsr-e48-atm-4oc12-mm-sr-sc
|
4OC12X/ATM-MM-SC (4xOC12c/STM4c ATM/IP)
|
cannot be manually deployed
|
GSR Edge Engine 48, ATM, 4 port OC12/STM4Multi Mode Short Reach Line Card
|
gsr-e48-atm-4oc12-sm-ir-sc
|
4OC12X/ATM-IR-SC (4xOC12c/STM4c ATM/IP)
|
cannot be manually deployed
|
GSR Edge Engine 48, ATM, 4 ports OC12/STM4 Single Mode Intermediate Reach Line Card
|
ATM Line Cards Not Yet Supported by Cisco 12000 Series Router Manager
•4OC3/ATM-IR-SC
POS Line Cards Supported by Cisco 12000 Series Router Manager
Table 4 POS Line Cards Supported by Cisco 12000 Series Router Manager
POS Card Type
|
Product Code Name
|
Cisco 12000/10720 Router Manager Menu Option
|
Card Description
|
pos-qoc3-sm
|
LC-4OC3/POS-SM
|
POS>OC-3 4>E4 SM
|
4 Port Packet Over SONET OC-3c/SM Single Mode Line Card
|
pos-qoc3-sm-l
|
|
POS>OC-3 4>E4 SM-LR
|
4 Port Packet Over SONET OC-3c/STM-1 Single Mode Long Reach Line Card
|
pos-qoc3-mm
|
LC-4OC3/POS-MM
|
POS>OC-3 4>E4 MM
|
4 Port Packet Over SONET OC-3c/MM Multi Mode Line Card
|
gsr-e48-pos-4oc3-mm-sr-mtrj
|
4OC3X/POS-MM-MJ-B
|
POS>OC-3 4>E4+ MM-SR
|
4 Port POS OC 48 Multi Mode Short Reach Line Card
|
gsr-e48-pos-4oc3-sm-lr-lc
|
4OC3/POS-LR-LC-B
|
POS>OC-3 4>E4+ SM-LR
|
4 Port POS OC 48 Single Mode long Reach Line Card
|
gsr-e48-pos-4oc3-sm-lr-lc
|
4OC3/POS-LR-SC
|
POS>OC-3 4>E4+ SM-LR
|
4 Port POS OC 48 Single Mode long Reach Line Card
|
gsr-e48-pos-4oc3-sm-ir-lc
|
4OC3X/POS-IR-LC-B
|
POS>OC-3 4>E4+ >SM-IR
|
4 Port POS OC 48 Single Mode Intermediate Reach Line Card
|
pos-8oc3-mm
|
8OC3/POS-MM
|
POS>OC-3 8 Port>E4 MM
|
8 Port OC3 Multimode POS
|
pos-8oc3-ir
|
8OC3/POS-SM
|
POS>OC-3 8 Port>E4 SM
|
8 Port OC3 SM Intermediate Reach POS
|
pos-8oc3-lr
|
|
POS>OC-3 8 Port>E4 SM-LR
|
8 port OC3 SM Long Reach POS
|
gsr-e48-pos-8oc3-mm-sr-mtrj
|
8OC3X/POS-MM-MJ-B=
|
POS>OC-3 8 Port>E4+ MM-SR
|
8 Port POS OC 3 multi MOde Short Reach Line Card
|
gsr-e48-pos-8oc3-sm-ir-lc
|
8OC3X/POS-IR-LC-B=
|
POS>OC-3 8 Port>E4+ SM-IR
|
8 Port POS OC 3 Single Mode Intermediate Reach Line Card
|
pos-oc12-sm
|
LC-1OC12-POS-SM
|
POS>OC-12 1 Port>SM
|
1 Port Packet Over SONET OC-12 Single Mode (SM) Line Card
|
pos-oc12-mm
|
LC-1OC12-POS-MM
|
POS>OC-12 1 Port>MM
|
1 Port Packet Over SONET OC-12 Multi Mode (MM) Line Card
|
pos-qoc12-sm-lr
|
|
POS>OC-12 4 Port>SM
|
4 Port (Quad) OC-12 POS Card, Single Mode, Long Reach
|
pos-qoc12-mm-sr
|
4OC12X/POS-M-SC-B
|
POS>OC-12 4 Port>MM
|
4 port (Quad) OC-12 POS Card, Single Mode, Short Reach
|
pos-en-qoc12-sr
|
|
POS>Enhanced OC-12 4 Port>MM
|
Enhanced 4 Port OC-12 Short Reach Line Card
|
pos-en-qoc12-ir
|
4OC12/POS-IR-SC-B
|
cannot be manually deployed
|
Enhanced 4 port OC-12 Intermediate Reach Line Card
|
pos-oc48-sm-lr-fc
|
|
POS>OC-48>LR-FC
|
1 Port Packet Over Sonet OC-48, Single Mode, Long Reach, FC Connector Card
|
pos-oc48-sm-lr-sc
|
OC48E/POS-LR-SC-B
|
POS>OC-48>LR-SC
|
1 Port Packet Over Sonet OC-48, Single Mode, Long Reach, SC Connector Card
|
pos-oc48-sm-sr-fc
|
|
POS>OC-48>SR-FC
|
1 Port Packet Over SONET OC-48c/STM-16 Single Mode Short Reach with FC Connector
|
pos-oc48-sm-sr-sc
|
OC-48E/POS-SR-SC-B
|
POS>OC-48>SR-SC
|
1 Port Packet Over Sonet OC-48, Single Mode, Short Reach, SC Connector Card
|
pos-en-oc48-lr-fc
|
|
POS>Enhanced OC-48>LR-FC
|
Enhanced OC-48 Long Reach FC Connector Line Card
|
pos-en-oc48-lr-sc
|
OC48X/POS-LR-SC
|
POS>Enhanced OC-48>LR-SC
|
Enhanced OC-48 Long Reach SC Connector Line Card
|
pos-en-oc48-sr-fc
|
|
POS>Enhanced OC-48>SR-FC
|
Enhanced OC-48 Short Reach FC Connector Line Card
|
pos-en-oc48-sr-sc
|
OC-48E/POS-SR-SC-B
|
POS>Enhanced OC-48>SR-SC
|
Enhanced OC-48 Short Reach SC Connector Line Card
|
pos-en-qoc48-sm-sr-sc
|
|
POS>Enhanced OC-48 4>E4 SR-SC
|
4 Port (Quad) Enhanced OC-48 Short Reach SC Connector Line Card
|
pos-en-qoc48-sm-sr-fc
|
|
POS>Enhanced OC-48 4>E4 SR-FC
|
4 Port (Quad) Enhanced OC-48 Short Reach FC Connector Line Card
|
pos-en-qoc48-sm-lr-sc
|
|
POS>Enhanced OC-48 4>E4 LR-SC
|
4 Port (Quad) Enhanced OC-48 Long Reach SC Connector Line Card
|
pos-en-qoc48-sm-lr-fc
|
|
POS>Enhanced OC-48 4>E4 LR-FC
|
4 Port (Quad) Enhanced OC-48 Long Reach FC Connector Line Card
|
gsr-e-qoc48-sm-sr-sc
|
4OC-48E/POS-SR-SC
|
POS>Enhanced OC-48 4>E4+ SR-SC
|
4 Port Enhanced OC 48 Short Reach SC Connector Line Card
|
gsr-e-qoc48-sm-sr-fc
|
|
POS>Enhanced OC-48 4>E4+ SR-FC
|
4 Port Enhanced OC 48 Short Reach FC Connector Line Card
|
gsr-e-qoc48-sm-lr-sc
|
4OC-48E/POS-LR-SC
|
POS>Enhanced OC-48 4>E4+ LR-SC
|
4 Port Enhanced OC 48 Long Reach SC Connector Line Card
|
gsr-e-qoc48-sm-lr-fc
|
|
POS>Enhanced OC-48 4>E4+ LR-FC
|
4 Port Enhanced OC 48 Long Reach FC Connector Line Card
|
pos-oc192-sm-sr-sc
|
OC192/POS-SR-SC
|
POS>OC-192 1>E4 SR-SC
|
OC-192 Short Reach SC Connector Line Card
|
pos-oc192-sm-sr-fc
|
OC192/POS-SR-FC
|
POS>OC-192 1>E4 SR-FC
|
OC-192 Short Reach FC Connector Line Card
|
pos-oc192-sm-ir-sc
|
OC192/POS-IR-SC
|
POS>OC-192 1>E4 IR-SC
|
OC-192 Intermediate Reach SC Connector Line Card
|
pos-oc192-sm-ir-fc
|
OC192/POS-IR-SC
|
POS>OC-192 1>E4 IR-FC
|
OC-192 Intermediate Reach FC Connector Line Card
|
pos-en-oc192-sm-vsr
|
OC192/POS-VSR
|
POS>OC-192 1>E4 VSR
|
Enhanced OC-192 Very Short Reach Line Card
|
gsr-e-oc192-sm-sr2-sc
|
OC192/POS-SR2-SC
|
POS>OC-192 1>E4 SR2-SC
|
GSR Edge 1 Port OC 192 Short Reach 2 SC Connector Line Card
|
gsr-e-oc192-sm-sr2-fc
|
OC192/POS-SR2-FC
|
POS>OC-192 1>E4 SR2-FC
|
GSR Edge 1 Port OC 192 Short Reach 2 FC Connector Line Card
|
pos-en-oc192-sm-sr2-sc
|
|
POS>OC-192 1>E4+ SR2-SC
|
Enhanced 1 Port OC 192 Short Reach 2 SC Connector Line Card
|
pos-en-oc192-sm-sr2-fc
|
|
POS>OC-192 1>E4+ SR2-FC
|
Enhanced 1 Port OC 192 Short Reach 2 FC Connector Line Card
|
gsr-e-oc192-sm-sr-sc
|
OC192E/POS-SR-SC
|
POS>OC-192 1>E4+ SR-SC
|
1 Port OC 192 Short Reach SC Connector Line Card
|
gsr-e-oc192-sm-sr-fc
|
OC192E/POS-SR-FC
|
POS>OC-192 1>E4+ SR-FC
|
1 Port OC 192 Short Reach FC Connector Line Card
|
gsr-e-oc192-sm-ir-sc
|
OC192E/POS-IR-SC
|
POS>OC-192 1>E4+ IR-SC
|
1 Port OC 192 Intermediate Reach SC Connector Line Card
|
gsr-e-oc192-sm-ir-fc
|
OC192E/POS-IR-FC
|
POS>OC-192 1>E4+ IR-FC
|
1 Port OC 192 Intermediate Reach FC Connector Line Card
|
gsr-e-oc192-vsr
|
OC192E/POS-VSR
|
POS>OC-192 1>E4+ VSR-SC
|
Enhanced OC-192 Very Short Reach SC Connector Line Card
|
pos-16oc3-lr
|
|
POS>OC-3 16>E4 LR
|
16 Port OC3 SM long Reach POS
|
pos-16oc3-ir
|
16OC3/POS-SM
|
POS>OC-3 16>E4 SM
|
16 Port OC3 SM Intermediate Reach POS
|
pos-16oc3-mm
|
16OC3/POS-MM
|
POS>OC-3 16>E4 MM
|
16 Port OC3 Multi Mode POS
|
gsr-e48-pos-16oc3-mm-sr-mtrj
|
16OC3X/POS-M-MJ-B=
|
POS> OC-3 16>E4+ MM-SR
|
16 Port OC3 Multi Mode Short Reach POS
|
gsr-e48-pos-16oc3-sm-ir-lc
|
16OC3X/POS-I-LC-B
|
POS>ISE>OC-3 16>IR
|
16 Port OC3 SM Intermediate Reach POS
|
gsr-e48-pos-qoc12-sm-ir-sc
|
4OC12X/POS-I-SC-B
|
POS>ISE>OC-12 4>IR
|
4 Port OC12 SM Intermediate Reach POS
|
gsr-e48-pos-oc48-sm-ir-lc
|
OC48X/POS-LR-SC
|
POS>ISE>OC-48 1> IR
|
1 Port OC48 Intermediate Reach POS
|
gsr-e48-pos-oc48-sm-sr
|
OC48X/POS-SR-SC
|
POS>ISE>OC-48 1> SR
|
1 Port OC48 Short Reach POS
|
gsr-e48-pos-oc48-sm-lr
|
OC48X/POS-LR-SC
|
POS>ISE>OC-48 1> LR
|
1 Port OC48 Long Reach POS
|
POS Line Cards Not Yet Supported by Cisco 12000 Series Router Manager
•OC192E/POS-LR-SC
Ethernet Line Cards Supported by Cisco 12000 Series Router Manager
Table 5 Ethernet Line Cards Supported by Cisco 12000 Series Router Manager
Card Type
|
Product Code Name
|
Cisco 12000/10720 Router Manager Menu Option
|
Card Description
|
gsr-1ge
|
GE-GBIC-SC-B
|
Ethernet>Giga>1 Port
|
1 Port Gigabit Ethernet Line Card
|
gsr-3ge
|
3GE-GBIC-SC
|
Ethernet>Giga>3 Port
|
3 Port Gigabit Ethernet Line Card (trident)
|
gsr-4ge
|
4GE-SFP-LC
|
Ethernet>Giga>4 Port
|
4 Port Gigabit Ethernet Line Card (Tetra)
|
gsr-10pge
|
10x1GE-SFP-LC-B
|
Ethernet>Giga>10 Port
|
10 port Gigabit Ethernet Line Card
|
gsr-8fe-tx
|
8FE-TX-RJ45
8FE-TX-RJ45-B
|
Ethernet>Fast>8 Port>Copper
|
8 port Fast Ethernet card with Copper Interface
|
gsr-8fe-fx
|
8FE-FX-SC
8FE-FX-SC-B
|
Ethernet>Fast>8 Port>Fiber
|
8 port Fast Ethernet card with Fiber Interface
|
gsr-1p10ge
|
1x10GE-LR-SC
1x10GE-ER-SC
|
Ethernet>10Giga>1 Port
|
1 Port 10Giga Ethernet Line Card
|
gsr-pa-1ge
|
EPA-GE/FE-BBRD
|
Ethernet>Modular>Gigabit/ FastEthernet Card
|
1 Port Modular Gigabit Fast Ethernet Line Card
|
gsr-pa-3ge
|
EPA-GE/FE-BBRD
EPA-3GE-SX/LH-LC
|
Ethernet>Modular>Port Adaptor>3 Port Gigabit
|
3 Port Modular Port Adaptor Gigabit Line Card
|
gsr-pa-24fe
|
|
Ethernet>Modular>Port Adaptor>24 Port FastEthernet
|
24 Port Modular Port Adaptor Fast Ethernet Line Card
|
DS-3 Line Cards Supported by Cisco 12000 Series Router Manager
Table 6 DS-3 Line Cards Supported by Cisco 12000 Series Router Manager
Card Type
|
Product Code Name
|
Cisco 12000/10720 Router Manager Menu Option
|
Card Description
|
copper-6ds3
|
6CT3-SMB=
6DS3-SMB-B
|
DS3>6 Port
|
6 Port Copper DS3 Interface Line Card
|
copper-12ds3
|
12DS3-SMB=
12DS3-SMB-B
|
DS3>12 Port
|
12 Port Copper DS3 Interface Line Card
|
E3 Line Cards Supported by Cisco 12000 Series Router Manager
Table 7 E3 Line Cards Supported by Cisco 12000 Series Router Manager
Card Type
|
Product Code Name
|
Cisco 12000/10720 Router Manager Menu Option
|
Card Description
|
copper-6e3
|
6E3-SMB
6E3-SMB=
|
E3>6 Port
|
6 Port E3 Interface Line Card
|
copper-12e3
|
12E3-SMB
12E3-SMB=
|
E3>12 Port
|
12 Port E3 Interface Line Card
|
SRP Line Cards Supported by Cisco 12000 Series Router Manager
Table 8 SRP Line Cards Supported by Cisco 12000 Series Router Manager
Card Type
|
Product Code Name
|
Cisco 12000/10720 Router Manager Menu Option
|
Card Description
|
srp-oc12-sm-ir
|
OC12/SRP-IR-SC-B(=)
|
cannot be manually deployed
|
1 Port OC-12 Single Mode SRP Intermediate Reach Line Card
|
srp-oc12-mm
|
OC12/SRP-MM-SC-B(=)
|
cannot be manually deployed
|
1 Port OC-12 Multi Mode SRP Line Card
|
srp-oc48-sm-sr
|
OC-48/SRP-SR-SC-B
|
cannot be manually deployed
|
1 Port OC-48 SRP Single Mode Short Reach Line Card
|
srp-oc48-sm-lr
|
OC-48/SRP-LR-SC-B
|
cannot be manually deployed
|
1 Port OC-48 SRP Single Mode Long Reach Line Card
|
ssrp-e48-2oc12-sm-ir
|
OC12/SRP-IR-SC-B
|
cannot be manually deployed
|
2 Port OC 12 Single Mode Intermediate Reach Line Card
|
ssrp-e48-2oc12-sm-xr
|
OC12/SRP-XR-SC
|
cannot be manually deployed
|
2 Port OC 12 Single Mode Line Card
|
ssrp-oc192-sm-lr
|
|
cannot be manually deployed
|
GSR 1 port SONET based SRP OC-192c/STM-64
|
ssrp-oc192-sm-ir
|
OC192/SRP-IR-SC
|
cannot be manually deployed
|
OC 192 Single Mode Intermediate Reach Line Card
|
ssrp-oc192-sm-sr
|
OC192/SRP-SR-SC
|
cannot be manually deployed
|
OC 192 Single Mode Short Reach Line Card
|
ssrp-oc192-sm-vsr
|
OC192/SRP-VSR
|
cannot be manually deployed
|
OC 192 Single Mode Very Short Reach Line Card
|
gsr-dtp-dense48
|
|
cannot be manually deployed
|
A dual mode card. It can function as a 4xOC48 or 2xSRP48
|
SRP Line Cards Not Supported by Cisco 12000 Series Router Manager
•4OC48/SRP-SFP
•4OC12X/SRP-IR-LC
•4OC12X/SRP-XR-LC
Channelized Line Cards Supported by Cisco 12000 Series Router Manager
Table 9 Channelised Line Cards
Product Code
|
Product Code Name
|
Engine
|
Cisco 12000/10720 Router Manager Menu Option
|
Card Description
|
2CHOC3/STM1-IR-SC
|
OC3/STM1->DS1/E1
|
0
|
cannot be manually deployed
|
Channelized OC3/STM1 -> DS1/E1, 2 ports Intermediate Reach
|
Channelized Line Cards Not Supported by Cisco 12000 Series Router Manager
•CHOC48/DS3-SR-SC
•CHOC12/DS1-IR-SC
•CHOC12/STS3-IR-SC
•LC-OC12-DS3
•4CHOC12/DS3-I-SCB
•6CT3-SMB
•xDS3-SMB-B
•xE3-SMB
Line Cards Supported by Cisco 10720 Routers
SRP Line Cards Supported by Cisco 10720 Routers
Table 10 SRP Line Cards Supported by Cisco 10720 Routers
Card Type
|
Product Code Number
|
Cisco 12000/10720 Router Manager Menu Option
|
Card Description
|
srp-oc48-sr
|
10720-SR-LC
|
cannot be manually deployed
|
1 port OC-48c SRP SM short reach uplink card
|
srp-oc48-ir
|
10720-IR-LC
|
cannot be manually deployed
|
1 port OC-48c SRP SM intermediate reach uplink card
|
ul-srp48-lr1
|
10720-LR1-LC
|
cannot be manually deployed
|
1 port OC-48c SRP SM long (40km) reach uplink card
|
ul-srp48-lr2
|
10720-LR2-LC
|
cannot be manually deployed
|
1 port OC-48c SRP SM long (80km) reach uplink card
|
ul-pos-srp48-sm-sr
|
10720-SR-LC-POS
|
POS>SR
|
c10720 OC-48c POS/SRP SM short reach uplink card
|
ul-pos-srp48-sm-ir
|
10720-IR-LC-POS
|
POS>IR
|
c10720 OC-48c POS/SRP SM intermediate reach uplink card
|
ul-pos-srp48-sm-lr1
|
10720-LR1-LC-POS
|
POS>LR1
|
c10720 OC-48c POS/SRP SM Long Reach (40Km) uplink card
|
ul-pos-srp48-sm-lr2
|
10720-LR2-LC-POS
|
POS>LR2
|
c10720 OC-48c POS/SRP SM Long Reach (80Km) uplink card
|
Ethernet Line Cards Supported by Cisco 10720 Routers
Table 11 Ethernet Line Cards Supported by Cisco 10720 Routers
Card Type
|
Product Code Number
|
Cisco 12000/10720 Router Manager Menu Option
|
Card Description
|
acc-24fe-tx
|
10720-FE-TX
|
Fast>24 Port
|
24 port fast Ethernet TX access card
|
acc-24fe-fx-mm
|
10720-FE-FX-MM
|
Fast>24 Port
|
24 port fast Ethernet FX MM (2km) access card
|
acc-24fe-fx-sm
|
10720-FE-FX-SM
|
Fast>24 Port
|
24 port fast Ethernet FX SM (15km) access card
|
Manually Deploying Supporting Modules
Table 12 Cisco 12000/10720 Router Manager Supported CSC and SFC Line Cards
Card
|
Card Type
|
Product Number
|
Card Description
|
CSC
|
CSC0
|
|
OC48 Clock Scheduler Card
|
| |
CSC4
|
GSR04-FABRIC=
|
OC48 ClockScheduler Card
|
| |
CSC8
|
GSR8-CSC/ALRM
|
OC48 Clock Scheduler Card
|
| |
CSC16
|
GSR16/80-CSC=
|
OC48 Clock Scheduler Card for 12016 chassis
|
| |
CSC16XOC192
|
GSR16/320-CSC=
GSR16-ALRM=
Can not be manually deployed
|
OC192 Clock Scheduler Card for 12416 chassis
|
| |
CSC10XOC192
|
GSR10-CSC=
|
OC192 Clock Scheduler Card for 12410 chassis
|
| |
CSC6XOC192
|
GSR6-CSC=
Can not be manually deployed
|
OC192 Clock Scheduler Card for 12406 chassis
|
| |
CSCSFC64
|
|
Combined CSC-SFC card for 12404 chassis
|
SFC
|
SFC0
|
|
OC48 Switch Fabric Card
|
| |
SFC8
|
GSR8-SFC=
|
OC48 Switch Fabric Card
|
| |
SFC16
|
GSR16/80-SFC=
|
OC48 Switch Fabric Card for 12016 chassis
|
| |
SFC16XOC192
|
GSR16/320-SFC=
Can not be manually deployed
|
OC192 Switch Fabric Card for 12416 chassis
|
| |
SFC10XOC192
|
GSR10-SFC=
|
OC192 Switch Fabric Card for 12410 chassis
|
| |
SFC6XOC192
|
GSR6-SFC=
Can not be manually deployed
|
OC192 Switch Fabric Card for 12406 chassis
|
Cisco 12000/10720 Router Manager Alarms
This section details information about the alarms that can be raised in the Cisco 12000/10720 Router Manager, as follows:
•Alarms Generated by Traps
•Alarms Generated by State Behaviour
•CNS Alarms
•RME Alarms
•MPLS Alarms
•Traps supported by the Cisco 12000/10720 Router Manager
Table 0-13 Alarms Generated by Traps
MIB/Trap
|
Trap Varbind Value
|
Maps to Alarm Class
|
Alarm Description
|
Maps to Alarm Severity
|
Raised on Object
|
Clear Correlation Rules
|
BGP4-MIB/BgpEstablished
|
bgpPeerState 1 = idle
bgpPeerState 2 = connect
bgpPeerState 3 = active
bgpPeerState 4 = opensent
bgpPeerState 5 = openconfirm
bgpPeerState 6 = established
bgpPeerLastError = OctetString value
|
ciscoBgpEstablishedAlarm
|
BGP Connection Established with Peer <peer-IP-Address>, Connection is in <peer-state> State
|
Normal
|
Chassis
|
BgpBackwardTransition
|
BGP4-MIB/BgpBackwardTransition
|
bgpPeerState 1 = idle
bgpPeerState 2 = connect
bgpPeerState 3 = active
bgpPeerState 4 = opensent
bgpPeerState 5 = openconfirm
bgpPeerState 6 = established bgpPeerLastError = OctetString value
|
ciscoBgpBackwardTransitionAlarm
|
BGP Connection Broken with Peer <peer-IP-Address>, Connection is in <peer-state> State
|
Major
|
Chassis
|
BgpBackwardTransition
|
CISCO-CONFIG-MAN-MIB/CiscoConfigManEventNotification
|
ccmHistoryEventCommandSource = {1,2} {commandLine,snmp}
ccmHistoryEventConfigSource = {1..7}
ccmHistoryEventConfigDestination = {1..7}
1 = erase
2 = commandSource
3 = running
4 = startup
5 = local
6 = networkTftp
7 = networkRcp
|
ciscoConfigManEventAlarm
|
Config Change, Command Source:<ccmHistoryEventCommandSource >, Config Source:<ccmHistoryEventConfigSource>, Config Destination: <ccmHistoryEventConfigDestination>
|
Info
|
Chassis
|
CiscoConfigManEvent Notification
|
CISCO-ENVMON-MIB/CiscoEnvMonVoltage Notification
|
ciscoEnvMonVoltageStatusDescr = OctetString
ciscoEnvMonVoltageStatusValue = Integer in mV
ciscoEnvMonVoltageState = integer {1..5}
1 = normal
|
CiscoChassisVoltageNormalEnvmonAlarm
|
<ciscoEnvMonVoltageStatusDescr>,<ciscoEnvMonVoltageState>,<ciscoEnvMonVoltageStatusValue> mV
|
Normal
|
Chassis
|
Clears Alarms of Class:
CiscoChassisVoltage WarningEnvmonAlarm
CiscoChassisVoltage CriticalEnvmonAlarm
CiscoChassisVoltage ShutdownEnvmonAlarm
CiscoChassisVoltage NotPresentEnvmonAlarm
|
| |
2 = warning
|
ciscoChassisVoltageWarningEnvmonAlarm
|
<ciscoEnvMonVoltageStatusDescr>,<ciscoEnvMonVoltageState>,<ciscoEnvMonVoltageStatusValue> mV
|
Warning
|
Chassis
|
All except Normal
|
| |
3 = critical
|
ciscoChassisVoltageCriticalEnvmonAlarm
|
<ciscoEnvMonVoltageStatusDescr>,<ciscoEnvMonVoltageState>,<ciscoEnvMonVoltageStatusValue> mV
|
Critical
|
Chassis
|
All except Normal
|
| |
4 = shutdown
|
ciscoChassisVoltageShutdownEnvmonAlarm
|
<ciscoEnvMonVoltageStatusDescr>,<ciscoEnvMonVoltageState>,<ciscoEnvMonVoltageStatusValue> mV
|
Critical
|
Chassis
|
All except Normal
|
| |
5 = notPresent
|
ciscoChassisVoltageNotPresentEnvmonAlarm
|
<ciscoEnvMonVoltageStatusDescr>,<ciscoEnvMonVoltageState>,<ciscoEnvMonVoltageStatusValue> mV
|
Info
|
Chassis
|
All except Normal
|
CISCO-ENVMON-MIB/CiscoEnvMonTemperatureNotification
|
ciscoEnvMonTemperatureStatusDescr = OctetString
ciscoEnvMonTemperatureState = Integer in mV
ciscoEnvMonTemperatureStatusValue = Integer {1..5}
1 = normal
|
CiscoChassisTempOKEnvmonAlarm
|
<ciscoEnvMonTemperatureStatusDescr>,<ciscoEnvMonTemperatureState>,<ciscoEnvMonTemperatureStatusValue> Celsius
|
Normal
|
Chassis
|
Clears Alarms of Class:
CiscoChassisTemp WarningEnvmonAlarm
CiscoChassisTemp CriticalEnvmonAlarm
CiscoChassisTemp ShutdownEnvmonAlarm
CiscoChassisTemp NotPresentEnvmonAlarm
|
| |
2 = warning
|
CiscoChassisTempWarningEnvmonAlarm
|
<ciscoEnvMonTemperatureStatusDescr>,<ciscoEnvMonTemperatureState>,<ciscoEnvMonTemperatureStatusValue> Celsius
|
Warning
|
Chassis
|
All except Normal
|
| |
3 = critical
|
CiscoChassisTempCriticalEnvmonAlarm
|
<ciscoEnvMonTemperatureStatusDescr>,<ciscoEnvMonTemperatureState>,<ciscoEnvMonTemperatureStatusValue> Celsius
|
Critical
|
Chassis
|
All except Normal
|
| |
4 = shutdown
|
CiscoChassisTempShutdownEnvmonAlarm
|
<ciscoEnvMonTemperatureStatusDescr>,<ciscoEnvMonTemperatureState>,<ciscoEnvMonTemperatureStatusValue> Celsius
|
Critical
|
Chassis
|
All except Normal
|
| |
5 = notPresent
|
ciscoChassisTemperatureNotPresentEnvmonAlarm
|
<ciscoEnvMonTemperatureStatusDescr>,<ciscoEnvMonTemperatureState>,<ciscoEnvMonTemperatureStatusValue> Celsius
|
Info
|
Chassis
|
All except Normal
|
CISCO-ENVMON-MIB/CiscoEnvMonFan Notification
|
ciscoEnvMonFanStatusDescr = OctetString
ciscoEnvMonFanStatusValue = Integer {1..5}
1 = normal
|
CiscoChassisFanNormalEnvmonAlarm
|
<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>
|
Normal
|
Chassis
|
Clears Alarms of Class:
CiscoChassisFan WarningEnvmonAlarm
CiscoChassisFanCriticalEnvmonAlarm
CiscoChassisFan ShutdownEnvmonAlarm
CiscoChassisFan NotPresentEnvmonAlarm
|
| |
2 = warning
|
CiscoChassisFanWarningEnvmonAlarm
|
<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>
|
Warning
|
Chassis
|
All except Normal
|
| |
3 = critical
|
CiscoChassisFanCriticalEnvmonAlarm
|
<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>
|
Critical
|
Chassis
|
All except Normal
|
| |
4 = shutdown
|
CiscoChassisFanShutdownEnvmonAlarm
|
<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>
|
Critical
|
Chassis
|
All except Normal
|
| |
5 = notPresent
|
CiscoChassisFanNotPresentEnvmonAlarm
|
<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>
|
Info
|
Chassis
|
All except Normal
|
CISCO-ENVMON-MIB/CiscoEnvMonRedundantSupplyNotification
|
ciscoEnvMonRedundatSupplyStatusDescr = OctetString
ciscoEnvMonRedundatSupplyStatusValue = Integer {1..5}
1 = normal
|
CiscoChassisPowerSupplyRedundantSupplyOKEnvMonAlarm
|
<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>
|
Normal
|
Chassis
|
Clears Alarms of Class:
CiscoChassisPower SupplyRedundant SupplyWarningEnvMonAlarm
CiscoChassisPower SupplyRedundant SupplyCriticalEnvMon Alarm
CiscoChassisPower SupplyRedundant SupplyShutdownEnv MonAlarm
CiscoChassisPower SupplyRedundant SupplyNotPresentEnv MonAlarm
|
| |
2 = warning
|
CiscoChassisPowerSupplyRedundantSupplyWarningEnvMonAlarm
|
<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>
|
Warning
|
Chassis
|
All except Normal
|
| |
3 = critical
|
CiscoChassisPowerSupplyRedundantSupplyCriticalEnvMonAlarm
|
<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>
|
Critical
|
Chassis
|
All except Normal
|
| |
4 = shutdown
|
CiscoChassisPowerSupplyRedundantSupplyCriticalEnvMonAlarm
|
<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>
|
Critical
|
Chassis
|
All except Normal
|
| |
5 = notPresent
|
CiscoChassisPowerSupplyRedundantSupplyNotPresentEnvMonAlarm
|
<ciscoEnvMonFanStatusDescr>,<ciscoEnvMonFanState>
|
Info
|
Chassis
|
All except Normal
|
CISCO-SYSLOG-MIB/ClogMessageGenerated
|
clogHistMsgText = OctetString
clogHistFacility = OctetString
clogHistMsgName =OctetString
clogHistTimestamp = TimeTicks
clogHistSeverity = integer {1-8}
1 = SeverityEmergency
|
CiscoSyslogSeverityEmergency
|
Asserted [<clogHistMsgText>] by facility [<clogHistFacility>], Message name [<clogHistMsgName>]
|
Critical
|
Chassis
|
|
| |
2 = SeverityAlert
|
CiscoSyslogSeverityAlert
|
Asserted [<clogHistMsgText>] by facility [<clogHistFacility>], Message name [<clogHistMsgName>]
|
Critical
|
Chassis
|
|
| |
3 = SeverityCritical
|
CiscoSyslogSeverityCritical
|
Asserted [<clogHistMsgText>] by facility [<clogHistFacility>], Message name [<clogHistMsgName>]
|
Critical
|
Chassis
|
|
| |
4 =SeverityError
|
CiscoSyslogSeverityError
|
Asserted [<clogHistMsgText>] by facility [<clogHistFacility>], Message name [<clogHistMsgName>]
|
Major
|
Chassis
|
|
| |
5 = SeverityWarning
|
CiscoSyslogSeverityWarning
|
Asserted [<clogHistMsgText>] by facility [<clogHistFacility>], Message name [<clogHistMsgName>]
|
Minor
|
Chassis
|
|
| |
6 = SeverityNotice
|
CiscoSyslogSeverityNotice
|
Asserted [<clogHistMsgText>] by facility [<clogHistFacility>], Message name [<clogHistMsgName>]
|
Minor
|
Chassis
|
|
| |
7 = SeverityInfo
|
CiscoSyslogSeverityInfo
|
Asserted [<clogHistMsgText>] by facility [<clogHistFacility>], Message name [<clogHistMsgName>]
|
Info
|
Chassis
|
|
| |
8 = SeverityDebug
|
CiscoSyslogSeverityDebug
|
Asserted [<clogHistMsgText>] by facility [<clogHistFacility>], Message name [<clogHistMsgName>]
|
Info
|
Chassis
|
|
IF-MIB/LinkDown
|
<ifIndex> = Integer {1..x} = unique interface number
|
LinkDown
|
Interface:<ifName> Down,Operational Status: Down, Administrative Status:
<ifAdminStatus>, Reason: <locIfReason>
|
Major
|
Interface
(Chassis if that Interface object is not available in the EM Database)
|
LinkDown
|
IF-MIB/LinkUp
|
<ifIndex> = Integer {1..x} = unique interface number
|
LinkUp
|
Interface:<ifName> Up,Operational Status: Up
|
Normal
|
Interface
(Chassis if that Interface object is not available in the EM Database)
|
Clears Alarms of Class:
LinkDown
|
SNMPv2-MIB/ColdStart
|
sysUpTime=TimeTicks,whyReload=reload
|
CiscoColdStartAlarm
|
Cold Start: Agent reinitializing; configuration may have changed.
|
Major
|
Chassis
|
CiscoColdStartAlarm
|
SNMPv2-MIB/WarmStart
|
sysUpTime=TimeTicks
|
CiscoWarmStartAlarm
|
Warm Start: Agent reinitializing; configuration is unaltered.
|
Major
|
Chassis
|
CiscoWarmStartAlarm
|
SNMPv2-MIB/Authentication Failure
|
sysUpTime=TimeTicks,authAddr=IPAddress
|
CiscoAuthenticationFailureAlarm
|
ìAuthentication Failureî
|
Major
|
Chassis
|
CiscoAuthenticationFailureAlarm
|
Table 0-14 Alarms Generated by State Behaviour
When Raised
|
Alarm Description
|
Alarm Class
|
Alarm Severity
|
Object Raised On
|
Clear Correlation Rules
|
Raised when Chassis moves into Normal State
|
Chassis Operational Status is Up
|
CiscoChassisNormalAlarm
|
Normal
|
Chassis
|
Clears Alarms of Class:
CiscoChassisDiscoveryLost CommsAlarm
CiscoChassisCommissioning Alarm
CiscoChassisPerformance LoggingOnAlarm
CiscoChassisMismatchedAlarm
ciscoChassisNormalAlarm
|
Raised when Chassis moves into Lost Comms State
|
Connection to device Lost
|
CiscoChassisLostCommsAlarm
|
Major
|
Chassis
|
Clears Alarms of Class:
CiscoChassisLostCommsAlarm
|
Raised when Chassis moves into Discovery Lost Comms State
|
Connection to device lost during Discovery
|
CiscoChassisDiscoveryLostCommsAlarm
|
Major
|
Chassis
|
Clears Alarms of Class:
CiscoChassisDiscoveryAlarm
CiscoChassisDiscoveryLostCommsAlarm
|
Raised when Sub Chassis Discovery fails
|
Chassis commissioning failed
|
CiscoChassisCommissionFailAlarm
|
Critical
|
Chassis
|
Clears Alarms of Class:
CiscoChassisCommissionFail Alarm
ciscoChassisCommissionFail Alarm
|
Raised when Sub Chassis Commissioning is successful
|
Chassis commissioning successful
|
CiscoChassisCommissionOKAlarm
|
Normal
|
Chassis
|
Clears Alarms of Class:
CiscoChassisCommissionFailAlarm
CiscoChassisCommissionOKAlarm
|
Raised when a change is detected in a Chassis being managed via the OLD-CISCO-CHASSIS MIB
|
Chassis Configuration has changed
|
CiscoChassisChangeHeartbeatFailOldChassisAlarm
|
Info
|
Chassis
|
Clears Alarms of Class:
CiscoChassisChangeHeartbeatFailOldChassisAlarm
|
Currently NOT Raised
|
Chassis is Decommissioned
|
CiscoChassisDecommissionedAlarm
|
|
Chassis
|
|
Currently NOT Raised
|
Chassis is Discovering
|
CiscoChassisDiscoveryAlarm
|
|
Chassis
|
|
Raised when a Module Mismatch has occurred
|
Deployed Chassis does not match actual device
|
CiscoChassisMismatchedAlarm
|
Critical
|
Chassis
|
Another Chassis Mismatch alarm
|
Currently NOT Raised
|
Chassis is logging Performance Data
|
CiscoChassisPerformanceLoggingOnAlarm
|
|
Chassis
|
|
Currently NOT Raised
|
Software Download to Chassis in progress
|
CiscoChassisDownloadAlarm
|
|
Chassis
|
|
Currently NOT Raised
|
Chassis is Resetting
|
CiscoChassisResetAlarm
|
|
Chassis
|
Clears Alarms of Class:
CiscoChassisDownloadAlarmciscoChassisResetAlarm
|
Currently NOT Raised
|
Chassis Change Heartbeat OK Alarm
|
CiscoChassisChangeHeartbeatFailOldChassisAlarm
|
|
Chassis
|
|
Raised when Module moves into Errored State
|
Module Operational Status is Down
|
CiscoModuleHeartbeatPollingFailAlarm
|
Major
|
Module
|
Clears Alarms of Class:
ciscoModuleLostCommsAlarm
CiscoModuleDiscoveryLostCommsAlarm
|
Raised when Module moves into Normal State
|
Module Operational Status is Up
|
CiscoModuleHeartbeatPollingOKAlarm
|
Normal
|
Module
|
Clears Alarms of Class:
CiscoModuleHeartbeatPollingFailAlarmciscoModuleLostCommsAlarm
CciscoModuleDiscoveryLost CommsAlarm
CiscoModuleLostCommsNoPollAlarm
CiscoModuleCommissioningAlarm
CiscoModulePerformanceLoggingOnAlarm
CiscoModuleMismatchedAlarm
CiscoModuleInvalidAlarm
CiscoModulePreprovisionedAlarm
CiscoModuleHeartbeatPollingOKAlarm
|
Raised when Module moves into Mismatched State
|
Deployed module does not match actual module.
|
CiscoModuleMismatchedAlarm
|
Major
|
Module
|
Clears Alarms of Class:
CiscoModuleMismatchedAlarm
|
Raised when Module moves into Lost Comms State
|
Connection to device lost
|
CiscoModuleLostCommsAlarm
|
Major
|
Module
|
Clears Alarms of Class:
CiscoModuleDiscoveryLostCommsAlarm
ciscoModuleHeartbeatPolling FailAlarm
|
Raised when Module moves into Discovery Lost Comms State
|
Connection to device lost during Discovery
|
CiscoModuleDiscoveryLostCommsAlarm
|
Major
|
Module
|
Clears Alarms of Class:
CiscoModuleDiscoveryAlarm
CiscoModuleLostCommsAlarm
CiscoModuleHeartbeatPollingFailAlarm
|
Currently NOT Raised
|
Serial number of module on device has changed
|
CiscoModuleSerialNumberChangeAlarm
|
|
Module
|
Clears Alarms of Class:
CiscoModuleSerialNumberChangeAlarm
|
Currently NOT Raised
|
Module is resetting
|
CiscoModuleResetAlarm
|
|
Module
|
Clears Alarms of Class:
CiscoModuleDownloadAlarm
|
Currently NOT Raised
|
Module is Decommissioned
|
CiscoModuleDecommissionedAlarm
|
|
Module
|
|
Currently NOT Raised
|
Module is Discovering
|
CiscoModuleDiscoveryAlarm
|
|
Module
|
|
Currently NOT Raised
|
Module is logging Performance Data
|
CiscoModulePerformanceLoggingOnAlarm
|
|
Module
|
|
Currently NOT Raised
|
Connection to device lost :Module Heartbeat Polling is Off
|
CiscoModuleLostCommsNoPollAlarm
|
|
Module
|
|
Currently NOT Raised
|
Module is Invalid
|
CiscoModuleInvalidAlarm
|
|
Module
|
|
Currently NOT Raised
|
Module is Preprovisioned
|
CiscoModulePreprovisionedAlarm
|
|
Module
|
|
Currently NOT Raised
|
Software Download to Module in progress
|
CiscoModuleDownloadAlarm
|
|
Module
|
|
Raised Only when the Interface moves to Normal from Errored State
|
Interface:<ifName> Up,Operational Status: Up
|
CiscoInterfaceNormalAlarm
|
Normal
|
Interface
|
Clears Alarms of Class:
CiscoInterfaceErroredAlarm
CiscoInterfaceLostCommsAlarm
CiscoInterfaceDiscoveryLostCommsAlarm
CiscoInterfaceCommissioningAlarm
LinkDown
|
Raised when Interface moves into Errored State
|
Interface:<ifName> Down,Operational Status: Down, Administrative Status: <ifAdminStatus>, Reason: <locIfReason>
|
CiscoInterfaceErroredAlarm
|
Major
|
Interface
|
Clears Alarms of Class:
CiscoInterfaceLostCommsAlarm
CiscoInterfaceDiscoveryLostCommsAlarm
CiscoInterfaceCommissioningAlarm
LinkDown
|
Currently NOT Raised
|
Interface is Decommissioned
|
CiscoInterfaceDecommissionedAlarm
|
|
Interface
|
|
Currently NOT Raised
|
Interface is Discovering
|
CiscoInterfaceDiscoveryAlarm
|
|
Interface
|
|
Currently NOT Raised
|
Interface is logging Performance Data
|
CiscoInterfacePerformanceLoggingOnAlarm
|
|
Interface
|
|
Currently NOT Raised
|
Deployed interface does not match actual
|
CiscoInterfaceMismatchedAlarm
|
|
Interface
|
|
Currently NOT Raised
|
Interface is Invalid
|
CiscoInterfaceInvalidAlarm
|
|
Interface
|
|
Currently NOT Raised
|
Interface is Preprovisioned
|
CiscoInterfacePreprovisionedAlarm
|
|
Interface
|
|
Currently NOT Raised
|
Software Download to Interface is in progress
|
CiscoInterfaceDownloadAlarm
|
|
Interface
|
|
Currently NOT Raised
|
Interface is Resetting
|
CiscoInterfaceResetAlarm
|
|
Interface
|
|
Table 0-15 CNS Alarms
MIB/Trap
|
Trap Varbind Value
|
Maps to Alarm Class
|
Alarm Message
|
Maps to Severity/Raised on Object
|
Clear CorrelationRules
|
n/a
|
-
|
cceServerAlarm
|
C-CFG Server : device failed to respond to ICMP ping, may be offline or unreachable
|
Major/cceServer
|
cceServerClear
|
n/a
|
-
|
cceServerClear
|
C-CFG Server : network connectivity to device has been restored
|
Normal/cceServer
|
-
|
Table 0-16 RME Alarms
MIB/Trap
|
Trap Varbind Value
|
Maps to Alarm Class
|
Alarm Message
|
Maps to Severity/Raised on Object
|
Clear Correlation Rules
|
n/a
|
RMEmodule.opString
|
startOperationAlarm
|
<RMEmodule.opString> started
|
Info/RMEServer
|
|
n/a
|
RMEmodule.opString
|
completeOperationAlarm
|
<RMEmodule.opString> completed
|
Normal/RMEServer
|
startOperationAlarm
|
n/a
|
-
|
lossOfCommAlarm
|
Loss of communication with RME Server
|
Major/RMEServer
|
|
n/a
|
-
|
regainCommAlarm
|
Regain communication with RME Server
|
Normal/
RMEServer
|
lossComAlarm
|
n/a
|
RMEmodule.opString,
RMEmodule.ipAddressString,
RMEmodule.alarmText
|
operationOnDeviceFailureAlarm
|
<RMEmodule.opString> failed for <RMEmodule.ipAddressString>: <RMEmodule.alarmText>
|
Major/RMEServer
|
|
n/a
|
RMEmodule.opString
RMEmodule.ipAddressString
|
operationOnDeviceSuccAlarm
|
<RMEmodule.opString> succeeded for <RMEmodule.ipAddressString>
|
Normal/RMEServer
|
operationOnDeviceFailureAlarm
|
n/a
|
RMEmodule.opString,
RMEmodule.alarmText
|
operationFailureAlarm
|
<RMEmodule.opString> failed: <RMEmodule.alarmText>
|
Major/RMEServer
|
|
n/a
|
RMEmodule.alarmText
|
ipAddressChangedAlarm
|
Ip Address <RMEmodule.alarmText>
|
Normal/RMEServer
|
ipAddressChangedAlarm
|
Threshold Alarms
Threshold alarms are user defined, when the user defines the alarm in the Notification in the Cisco EMF Event Manager.
Table 0-17 MPLS Alarms
MIB/Trap
|
Trap Varbind Value
|
Maps to Alarm Class
|
Alarm Message
|
Maps to Severity/Raised on Object
|
Clear Correlation Rules (clears)
|
MPLS-LDP-MIB/mplsLdpSessionUp
|
mplsLdpEntityLdpId = 6 octet
mplsLdpEntityIndex = Unsigned 32
mplsLdpPeerLdpId= 6 octet
mplsLdpSesState = Integer[1..5]
5 = Up
|
ciscomplsLdpSessionUpAlarm
|
LDP Session Up between < MPLS-LDP-MIB.mplsLdpEntityLdpId> number: <a
larmDirectory:MPLS-LDP-MIB.mplsLdpEntityIndex> and Peer <MPLS-LDP-MIB.mplsLdpPeerLdpId>
|
Normal/ Chassis
|
ciscomplsLdpSessionDownAlarm
|
MPLS-LDP-MIB/mplsLdpSessionDown
|
mplsLdpEntityLdpId = 6 octet
mplsLdpEntityIndex = Unsigned 32
mplsLdpPeerLdpId= 6 octet
mplsLdpSesState = Integer[1..5]
1..4 = Down
|
ciscomplsLdpSessionDownAlarm
|
LDP Session Down between <MPLS-LDP-MIB.mplsLdpEntityLdpId> number:
<MPLS-LDP-MIB.mplsLdpEntityIndex> and Peer <MPLS-LDP-MIB.mplsLdpPeerLdpId>
|
Major/ Chassis
|
ciscoMPLSLdpSessionDown alarm
|
MPLS-LDP-MIB/mplsLdpPVLMismatch
|
{mplsLdpEntityLdpId = 6 octet
mplsLdpEntityIndex = Unsigned 32
mplsLdpEntityPVL = Integer32[0..255]}
{mplsLdpEntityLdpId = current
mplsLdpEntityIndex = Unsigned 32
mplsLdpPeerPVL= Integer32[0..255]}
|
ciscomplsLdpPVLMismatchAlarm
|
LDP Entity <MPLS-LDP-MIB.mplsLdpEntityLdpId> number: <alarmDirector
y:MPLS-LDP-MIB.mplsLdpEntityIndex> with Path-Vector-Limit <MPLS-LDP-MIB.mplsLdpEntityPVL> does not match Peer <[ConvertOctT
oIpDecimal] MPLS-LDP-MIB.mplsLdpPeerLdpId> Path-Vector-Limit of <MPLS-LDP-MIB.mplsLdpPeerPVL>
|
Warning/ Chassis
|
ciscomplsLdpPVLMismatchAlarm
|
MPLS-LDP-MIB/mplsLdpInitSesThresholdExceeded
|
mplsLdpEntityLdpId = 6 Octet
mplsLdpEntityIndex = Unsigned32
mplsLdpEntityInitSesThreshold = Integer32
|
ciscomplsLdpSesThreshExceededAlarm
|
For LDP Entity <MPLS-LDP-MIB.mplsLdpEntityLdpId> number: <MPLS-LDP-MIB.mplsLdpEntityIndex> number of Session Initialization messages exceeded the threshold of <MPLS-LDP-MIB.mp
lsLdpEntityInitSesThreshold> messages.
|
Warning/
Chassis
|
ciscomplsLdpSesThreshExceededAlarm
|
MPLS-TE-MIB/mplsTunnelUp
|
mplsTunnelIndex = Integer32[1..65535]
mplsTunnelInstance,= Unsigned32[0..65535]
mplsTunnelIngressLSRId = 4 octet mplsTunnelEgressLSRId,= 4 octet
mplsTunnelAdminStatus = Integer[1..3]
1=up
mplsTunnelOperStatus = Integer[1..7]
1=up
|
ciscomplsTunnelUpAlarm
|
Tunnel <MPLS-TE-MIB.mplsTunnelIndex> instance: <MPLS-TE-MIB.mplsTunnelInstan
ce> UP. Admin Status: <MPLS-TE-MIB.mplsTunnelAdminStatus>, Operational status: <MPLS-TE-MIB.mplsTunnelOper
Status>, Ingress LSR Id: <[ConvertIntToIP] MPLS-TE-MIB.mplsTunnelIngressLSRId>, Egress LSR: <[ConvertIntToIP] alarmDirector
y:MPLS-TE-MIB.mplsTunnelEgressLSRId>.
|
Major/ Chassis
|
ciscomplsTunnelDownAlarm
|
MPLS-TE-MIB/mplsTunnelDown
|
mplsTunnelIndex = Integer32[1..65535]
mplsTunnelInstance,= Unsigned32[0..65535]
mplsTunnelIngressLSRId = 4 octet mplsTunnelEgressLSRId,= 4 octet
mplsTunnelAdminStatus = Integer[1..3]
2=Down
mplsTunnelOperStatus = Integer[1..7]
2=Down
|
ciscomplsTunnelDownAlarm
|
Tunnel <MPLS-TE-MIB.mplsTunnelIndex> instance: <MPLS-TE-MIB.mplsTunnelInstan
ce> Down. Admin Status: <MPLS-TE-MIB.mplsTunnelAdminStatus>, Operational status: <MPLS-TE-MIB.mplsTunnelOper
Status>, Ingress LSR Id: <[ConvertIntToIP] MPLS-TE-MIB.mplsTunnelIngressLSRId>, Egress LSR: <[ConvertIntToIP] alarmDirector
y:MPLS-TE-MIB.mplsTunnelEgressLSRId>.
|
Major/ Chassis
|
ciscomplsTunnelDownAlarm
|
MPLS-TE-MIB/mplsTunnelRerouted
|
mplsTunnelIndex = Integer32[1..65535]
mplsTunnelInstance,= Unsigned32[0..65535]
mplsTunnelIngressLSRId = 4 octet mplsTunnelEgressLSRId,= 4 octet
mplsTunnelAdminStatus = Integer[1..3]
1=Up
mplsTunnelOperStatus = Integer[1..7]
1=Up
|
ciscomplsTunnelReroutedAlarm
|
Tunnel <MPLS-TE-MIB.mplsTunnelIndex> instance: <MPLS-TE-MIB.mplsTunnelInstan
ce> Rerouted. Admin Status: <MPLS-TE-MIB.mplsTunnelAdminStatus>, Operational status: <MPLS-TE-MIB.mplsTunnel
OperStatus>, Ingress LSR Id: <[ConvertIntToIP] MPLS-TE-MIB.mplsTunnelIngressLSRId>, Egress LSR: <[ConvertIntToIP] alarmDire
ctory:MPLS-TE-MIB.mplsTunnelEgressLSRId>.
|
Minor/ Chassis
|
ciscomplsTunnelReroutedAlarm
|
MPLS-VPN-MIB/mplsNumVrfRouteMidThreshExceeded
|
mplsVpnVrfName = OctetString mplsVpnVrfPerfCurrNumRoutes = Unsigned 32
|
ciscomplsNumVrfRouteMidThreshExceededAlarm
|
For VRF: <MPLS-VPN-MIB.mplsVpnVrfName> the current number of routes <MPLS-VP
N-MIB.mplsVpnVrfPerfCurrNumRoutes> exceed the Mid-Threshold value
|
Warning/ Chassis
|
ciscomplsNumVrfRouteMidThreshExceededAlarm
and
ciscomplsNumVrfRouteMaxThreshExceededAlarm
|
MPLS-VPN-MIB/mplsNumVrfRouteMaxThreshExceeded
|
mplsVpnVrfName = OctetString mplsVpnVrfPerfCurrNumRoutes = Unsigned 32
|
ciscomplsNumVrfRouteMaxThreshExceededAlarm
|
For VRF: <MPLS-VPN-MIB.mplsVpnVrfName> the current number of routes <MPLS-VP
N-MIB.mplsVpnVrfPerfCurrNumRoutes> exceed the Max-Threshold value
|
Warning/ Chassis
|
ciscomplsNumVrfRouteMaxThreshExceededAlarm
and
ciscomplsNumVrfRouteMidThreshExceededAlarm
|
MPLS-VPN-MIB/mplsNumVrfSecIllegalLabelThreshExceeded
|
mplsVpnVrfName = OctetString mplsVpnVrfSecIllegalLabelViolations = Counter32
|
ciscomplsNumVrfSecIllegalLabelThreshExceededAlarm
|
Number of illegally received labels <MPLS-VPN-MIB.mplsVpnVrfSecIllegalLabelViolations> exce
ed the thresh value for VRF: <MPLS-VPN-MIB.mplsVpnVrfName>
|
Warning/ Chassis
|
ciscomplsNumVrfSecIllegalLabelThreshExceeded
|
MPLS-VPN-MIB/mplsVrfIfUp
|
mplsVpnInterfaceConfIndex = Integer32 (1..2147483647)
mplsVpnVrfName = OctetString
ifOperStatus = 1(up)
|
ciscomplsVrfIfUpAlarm
|
Interface: <MPLS-VPN-MIB.mplsVpnInterfaceConfIndex> associated with VRF: <MP
LS-VPN-MIB.mplsVpnVrfName> is up
|
Normal/ Chassis
|
|
MPLS-VPN-MIB/mplsVrfIfDown
|
mplsVpnInterfaceConfIndex = Integer32 (1..2147483647)
mplsVpnVrfName = OctetString
ifOperStatus = 2(down)
|
ciscomplsVrfIfDownAlarm
|
Interface: <MPLS-VPN-MIB.mplsVpnInterfaceConfIndex> associated with VRF: <MP
LS-VPN-MIB.mplsVpnVrfName> is down"
|
Major/ Chassis
|
mplsVrfIfDown
|
Table 0-18 Traps supported by the Cisco 12000/10720 Router Manager
MIB/Trap
|
Trap Varbind Value
|
Alarm Description
|
Maps to Alarm Severity
|
Raised on Object
|
Clears
|
IF-MIB/RPR Switchover
|
sysUpTime=TimeTicks,whyReload=RPR Switchover
|
RPR Cold Start: Agent reinitializing;configuration may have changed
|
Major
|
Chassis
|
RPR Switchover
|
IF-MIB/RPR+ Switchover
|
sysUpTime=TimeTicks,whyReload=RPR-Plus switchover
|
RPR+ Cold Start: Agent reinitializing; configuration may have changed
|
Major
|
Chassis
|
RPR+ Switchover
|
CISCO-RF-MIB/Redundancy Framework (RF) Progression
|
cRFStatusUnitId=Integer,cRFStatusUnitState=Integer,
cRFStatusPeerUnitId=Integer,cRFStatusPeerUnitState=Integer
|
RF Notification: RF state has changed. Active Unit: <slot-no> State: <RF-state>. Peer Unit: <slot-no> State: <RF-state>
|
Major
|
Chassis
|
Redundancy Framework (RF) Progression
|
CISCO-FLASH-MIB/FlashDeviceChange
|
ciscoFlashDeviceIndex=Integer
|
A Flash Device has been inserted or removed from the chassis
|
Info
|
Chassis
|
FlashDeviceChange
|
RSVP-MIB/Flow Lost
|
rsvpFlowIndex=OctetString, ifIndex=Integer
|
Flow Lost for <rsvp-FlowIndex> from Link <interface index>
|
Info
|
Interface
|
|
RSVP-MIB/Flow Created
|
rsvpFlowIndex=OctetString,ifIndex=Integer
|
A New Flow has been generated for <rsvp-FlowIndex> from Link <interfaceIndex>
|
Normal
|
Interface
|
Flow Lost
|
CISCO-IETF-ATM2-PVCTRAP-MIB/PVC Failed
|
ifIndex=Integer,atmIntfPvcFailures=Integer,
atmIntfCurrentlyFailingPVcls=Integer
|
Total <no_of_failed_PVCs> PVCs are not up on ATM Interface <interfaceIndex>
|
Info
|
Interface
|
PVC Failed
|
DS1-MIB/DS1 Alarm
|
dsx1LineStatusLastChange=TimeStamp
dsx1LineStatus=Bit mapped Integer
1 dsx1NoAlarm No alarm present
2 dsx1RcvFarEndLOF Far end LOF/Yellow alarm
4 dsx1XmtFarEndLOF Near end sending LOF indication
8 dsx1RcvAIS Far end sending AIS
16 dsx1XmtAIS Near end sending AIS
32 dsx1LossOfFrame Near end LOF/Red alarm
64 dsx1LossOfSignal Near end loss of signal
128 dsx1LoopbackState Near end is looped
256 dsx1T16AIS E1 TS16 AIS
512 dsx1RcvFarEndLOMF Far end sending TS16 LOMF
1024 dsx1XmtFarEndLOMF Near end sending TS16 LOMF
2048 dsx1RcvTestCode Near end detects a test code
4096 dsx1OtherFailure Other failure
8192 dsx1UnavailSigState Near end in unavailable signal state
16384 dsx1NetEquipOOS Carrier equipment out of service
32768 dsx1RcvPayloadAIS DS2 payload AIS
65536 dsx1Ds2PerfThreshold DS2 performance threshold exceeded
|
DS1 line status change detected on <ifDescr>.Alarms: <Alarm Details>
|
Info
|
Chassis
|
Note: No clear correlation supported at present.
|
DS3-MIB/DS3 Alarm
|
dsx3LineStatusLastChange=TimeStamp
dsx3LineStatus=Bit mapped Integer
1 dsx3NoAlarm No alarm present
2 dsx3RcvRAIFailure Receiving Yellow/Remote alarm indication.
4 dsx3XmitRAIAlarm Transmitting Yellow/Remote alarm indication
8 dsx3RcvAIS Receiving AIS failure state
16 dsx3XmitAIS Transmitting AIS
32 dsx3LOF Receiving LOF failure state
64 dsx3LOS Receiving LOS failure state
128 dsx3LoopbackState Looping the received signal
256 dsx3RcvTestCode Receiving a test pattern
512 dsx3OtherFailure Other failure
1024 dsx3UnavailSigState Near end in unavailable signal state
2048 dsx3NetEquipOOS Carrier equipment out of service
|
DS3 line status change detected on <ifDescr>.Alarms: <Alarm Details>
|
Info
|
Chassis
|
Note: No clear correlation supported at present.
|
CISCO-SRP-MIB/srpTrapRingWrapped
|
<ifIndex> = Integer
srpIpsState = Integer
srpMACIpsAutoDetectMode = <SignalFail> < SignalDegrade> < WaitToRestore> srpMACIpsRemoteMode = <SignalFail> < SignalDegrade> < WaitToRestore>
srpMACIpsRemoteType = Integer
1 = shortPath
2 = longPath
srpMACIpsActiveMode = <SignalFail> < SignalDegrade> < WaitToRestore>
srpMACIpsWrapCounter = Counter32 srpMACIpsLastWrapTimeStamp =
Time Stamp
srpMACIpsLastUnWrapTimeStamp = Time Stamp
|
SRP Ring Wrapped
|
Major
|
SRP Side Interface
|
srpTrapRingWrapped
|
CISCO-SRP-MIB/srpTrapRingRestored
|
<ifIndex> = Integer
srpIpsState = Integer
srpMACIpsAutoDetectMode = <SignalFail> < SignalDegrade> < WaitToRestore> srpMACIpsRemoteMode = <SignalFail> < SignalDegrade> < WaitToRestore>
srpMACIpsRemoteType = Integer
1 = shortPath
2 = longPath
srpMACIpsActiveMode = <SignalFail> < SignalDegrade> < WaitToRestore>
srpMACIpsWrapCounter = Counter32 srpMACIpsLastWrapTimeStamp =
Time Stamp
srpMACIpsLastUnWrapTimeStamp = Time Stamp
|
SRP Ring Restored
|
Normal
|
SRP Side Interface
|
srpTrapRingWrapped
srpTrapRingRestored
|
Known Limitations in this Release
The following Cisco 12000 series Router module is not supported in this release:
•Channelized line cards
Note The Frost line card is supported.
Caveats
This section describes known issues with the features provided by Cisco 12000/10720 v3.1.2 Router Manager:
•Cisco EMF Issues
•Cisco 12000/10720 Router Manager Issues
•Routing Issues
•MPLS/VRF Issues
•IOS Issues
Cisco EMF Issues
•CSCin36736
Problem: In MPLS Tunnel Information dialog, IpV6 Address attribute is not displayed properly in Head Tunnel Hops Tab and LSP Hops Tab.
Workaround: None
Cisco 12000/10720 Router Manager Issues
•CSCea52670
Problem: In OAM Ping Tab for ATM VCL Configuration dialog the error message is not proper if the ping operation fails, when selected card is in the Admin Down state.
Workaround: None
•CSCin38332
Problem: The field "Redundancy Mode" present in both RPR Config and RPR Status dialogs shows truncated information for some temporary states of RP. The temporary states are "RPR Plus (standby)" and "RPR Plus (standby initalization)". This problem occurs just after a switchover.
Workaround: None
•CSCin38351
Problem: In OAM Ping Tab for ATM VCL Configuration Dialog, default values should be displayed for Repeat Count, Timeout In Second and Loopback Type, when a new PVC is selected in OAM Ping Tab.
Workaround: None
Routing Issues
•CSCea33825
Problem: In the BGP Configuration window, the attributes in the BGP Information frame of the BGP-Details tab, are populated with values even if BGP is not configured for that chassis. Similarly, in the OSPF Status dialog, General Group / Interface tab populates when no OSPF is configured on the device.
Workaround: None
•CSCin39598
Problem: On removing the Address-Family from the EM using Configure Address Family dialog the selected chassis disappears from the chassis selector list and the dialog is greyed out.
Workaround: Close the Configure Address Family dialog and reopen it for any other selected address family from the AF-General tab in BGP Address Family Configuration dialog.
•CSCin41998
Problem: On removal of an address family through the EM the running-config is not copied to the startup-config sometimes.
Workaround: On removal of an address family through the EM the write mem operation should be performed explicitly by launching the Chassis Configuration dialog and selecting the writeMem action button present in the Device Management tab.
•CSCin52334
Problem: If the ISIS Redistribute Protocol is configured for Ipv4 Unicast AF without Tag, the BGP AF-Configuration and AF Status dialog's AF-Redistribute Tab displays incorrect values against AS/Tag field for ISIS Redistribute Protocol.
Workaround: Configure Redistribute ISIS Protocol with Tag id followed by the Routing Level.
MPLS/VRF Issues
•CSCec13751
Problem: Can not upload LSP tunnel information in the Tunnel Information Dialog when router is configured with 500 or 1000 tunnels.
Workaround: None through the EMS GUI. User needs to telnet into the router and run the appropiate CLI command that will display the LSP tunnels.
•CSCin37046
Problem: Special Characters are not allowed for naming the VRF objects during deployment.
Workaround: Use strings with alphabets and numbers to deploy vrf objects.
•CSCin36791
Problem: In the MPLS Traps Configuration Dialog, Auto Refresh behavior is not proper when the authentication information is changed to an incorrect value for the selected chassis in the chassis list and when the value is changed back to the previous value.
Workaround: Manually refreshing the MPLS Trap Configuration dialog will populate values correctly.
•CSCin38505
Problem: Auto Refresh does not happen for the VRF Object Status dialog for the first time as well as when the VRF is removed from the device using CLI. Sometimes, auto refresh may fail for the Interface VRF Status dialog.
Workaround: All values will be populated correctly after manually refreshing the dialogs.
•CSCin38656
Problem: For any configuration changes on a VRF in the device, the dialog does not refresh even after reselecting the same VRF or moving from one VRF to another in the list. Also refreshing the dialog causes the first VRF to be selected always instead of refreshing and highlighting the already selected VRF.
Workaround: Manually refresh the VRF Status dialog and then select the required VRF Object from the VRF list.
•CSCin46635
Problem: Performance data is not collected for interface MPLS layer attributes when the performance polling is enabled globally or against the indvidual interface objects.
Workaround: Launch either the MPLS Interface Status or MPLS Interface Performance dialogs against the respective interface objects and select the interfaces from the interface object selector list, then enable performance polling on the interface objects.If the performance polling is enabled already , then need to stop and start the performance polling on the interface objects to enable the Router Manager to collect the MPLS performance attributes for the interface objects.
IOS Issues
•CSCin35210
Problem: The mplsVrfIfUp and mplsVrfIfDown traps should be supported at the interface level.
Workaround: Currently these traps are raised as alarms against the chassis and can be viewed by launching Event Browser against the chassis.
•CSCin37225
Problem: After inserting a new linecard against a managed chassis, running IOS 12.0(24)S or 12.0(25)S, the Cisco 12000/10720 Router Manager discovers only the module object for the inserted linecard. The interfaces are not discovered, as the IF Table is not updated properly.
Workaround: Recommission the module after the linecard is moved to the IOS RUN state in the device. All the interface objects have been deployed and commissioned successfully.
•CSCin49840
Problem: The Link Down alarm for the Frost card's controller is not sent by the device running IOS Version "12.(0)23S3" when the "shutdown" command is issued.
Workaround: None.
Documentation Updates
This section of the Release Notes includes the following updates to the Cisco EMF documentation set:
•Setting Up a Cisco 12000/10720 Router Manager and C-NOTE Co-resident Installation to Receive SNMP Traps
•Backing Up a C-NOTE/Element Manager Co-resident Installation
•Device in RME Not Responding
•Configuring a PVC Under a Sub-interface
•Updates to the Cisco EMF 12000/10720 Router Manager User Guide
Setting Up a Cisco 12000/10720 Router Manager and C-NOTE Co-resident Installation to Receive SNMP Traps
Both Cisco 12000/10720 Router Manager and C-NOTE receive SNMP traps. Since the applications are co-resident on the same hardware platform they cannot both listen to the default port of 162.
You must configure the installation as follows:
•Cisco 12000/10720 Router Manager listens to the default port 162
•Configure C-NOTE to listen to a non-default port (which is 6162 in our example). In addition C-NOTE listens to a virtual address, as follows:
# enable traps to be sent to C12k-M
snmp-server host 172.18.137.35 version 2c texan
# enable traps to be sent to C-Note
snmp-server host 172.18.137.90 texan udp-port 6162
As you can see from this example, more than one trap destination must be configured, with the user being able to specify the IP address, and community string.
Backing Up a C-NOTE/Element Manager Co-resident Installation
The EMS can be installed on the same server as CNS Notification Engine (C-NOTE), this is a co-resident installation. You can use the backup procedure to backup the C-NOTE files.
To have the CNS files backed up as part of a backup, you should append the full file paths to the <CEMF_ROOT>/data/filesToBackup file. The files are listed at http://www.cisco.com/en/US/products/sw/netmgtsw/ps156/products_installation_and_configuration_guide_chapter09186a00801781f7.html#12745.
Note These are base lists. Any other files customized by the user will also need to be included.
In addition to the files listed, you should also back up the following file:
•/opt/ssng/log/nodeinfo.dat—Include this file in the <CEMF_ROOT>/data/filesToBackup file.
Note C-NOTE should not be running on the standby server when the cemf restore takes place. C-NOTE must be started after the cemf restore completes.
Device in RME Not Responding
When a device is added to RME it may go into the Not Responding State. This occurs if the processor RAM of the device in question is equal to or greater than 2GB.
The tables named MEMORY_POOL, FLASH_PARTITION and CISCO_ENTITY_EXT defined in RME have some of the columns defined as integer data type. When a device has a very high value for these fields, insertion into the RME database fails and the device does not go into a managed state.
If you encounter this problem, please contact TAC.
Configuring a PVC Under a Sub-interface
If a PVC is configured under a sub-interface and uploaded to the EMS, and the user then changes the sub-interface number of the PVC through the CLI, the EMS does not update the sub-interface number.
Updates to the Cisco EMF 12000/10720 Router Manager User Guide
Chapter 3
A new table is added to Chapter 3:
Table 19 DS1/E1 cards supported by Cisco 12000 series internet routers
Card Type
|
Cisco 12000/10720 Router Manager Menu Option
|
Card Description
|
gsr-2oc3-chds1
|
Cannot be deployed manually
|
2 Ports OC3 Channelized to DS1/E1
|
Chapter 4
In Chapter 4, the following information is added to Table 4-1:
Table 20 Launching the Chassis Management Windows
Cisco 12000/10720 Router Manager Window/Task
|
Objects (that can be selected) to Open the Window
|
Menu Options to Select to Open Window
|
| |
Site
|
Chassis
12000 Series
|
Chassis
10720
|
Module
|
Interface
|
|
Reload
|
No
|
Yes
|
No
|
No
|
No
|
Technology Specific Tools>Reload
|
Reload
The login password to the Cisco 12000 Series Router must be set on the Cisco 12000/10720 Router Manager to allow you to reload a selected 12000 Router Chassis.
Note This feature is not available for the Cisco 10720 Routers.
The Reboot service allows you to reload any selected 12000 Router chassis.
Launching the Reload Status Window
To view the Reload Status window, proceed as follows:
Step 1 Right click on the chassis object and choose Router > Technology Specific Tools > Reload. See Table 4-1 for information on which objects allow you to launch the Reload status window. A confirmation window is shown asking the user to Continue further with reload? Click Yes to reload the chassis.
Step 2 The Reload Status window is displayed.
Figure 1 Reload Status Window
Chapter 5
In Chapter 5, the following information is added to Table 5-2:
Table 0-21 Launching the Module Management Windows
Cisco 12000/10720 Router Manager Window/Task
|
Objects (that can be selected) to Open the Window
|
Menu Options to Select to Open Window
|
| |
Site
|
Chassis
12000 Series
|
Chassis
10720
|
Module
|
Interface
|
|
Reload
|
No
|
No
|
No
|
Yes
|
No
|
Technology Specific Tools > Reload
|
Reload
The login password to the Cisco 12000 Series Router must be set on the Cisco 12000/10720 Router Manager to allow you to reload a selected Cisco 12000 Router's Module.
Note This feature is not available for the Cisco 10720 Routers.
The reload service allows you to reload any selected Cisco 12000 Router's Module.
Launching the Reload Status Window
To view the Reload Status window, proceed as follows:
Step 1 Right click on the module object and choose Module > Technology Specific Tools > Reload. See Table 5-2 for information on which objects allow you to launch the Reload status window. A confirmation window is shown asking the user to Continue further with reload? Click Yes to reload the chassis.
Step 2 The Reload Status window is displayed.
Figure 2 Reload Status Window
Chapter 12
Figure 12-12 is updated as follows:
Figure 3 Deployment Wizard—Templates
Figure 12-14 is updated as follows:
Figure 4 Deployment Wizard—Object Parameters
Chapter 14
In Chapter 14, the following details are added to the Config Tab—Detailed Description section:
Config
VRF Name—Name of the VRF to be associated with the OSPF Process
Chapter 14
In Chapter 14, an additional step is added to the Adding an OSPF Process procedure. The procedure is now as follows:
Step 1 Open the OSPF configuration window. See "Viewing the OSPF Configuration Window" for further details.
Step 2 Enter an OSPF process id in the Process ID textbox.
Step 3 Enter the VRF name (optional) to be associated with the OSPF process ID.
Step 4 Click on the Add OSPF Process button. An action report appears.
Chapter 14
Figure 4-31 is updated as follows:
Figure 5 OSPF Configuration Window
Chapter 18
The following details are added to Table 18-2:
Monitored Attributes for a GRP Module
Trap
|
Alarm Description
|
Severity
|
Clears
|
DS1 line status
|
DS1 line status change detected on <ifDescr>. Alarms <Details of the alarms raised>
|
Informational
|
No ClearCorelation supported
|
DS3 line status
|
DS3 line status change detected on <ifDescr>. Alarms <Details of the alarms raised>
|
Informational
|
No ClearCorelation supported
|
Related Documentation
The documentation supporting this release is:
•Cisco 12000/10720 v3.1.2 Router Manager Quick Start Guide (78-15959-01)
•Cisco 12000/10720 v3.1.1 Router Manager User Guide (OL-4455-01)
•Cisco 12000/10720 v3.1.1 Router Manager Installation and Configuration Guide (OL-4454-01)
•Cisco Element Management Framework User Guide Release 3.2 Service Pack 7 (OL-4506-01)
Obtaining Documentation
The following sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following URL:
http://www.cisco.com
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
http://www.cisco.com/go/subscription
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to,
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL: http://www.cisco.com
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
http://www.cisco.com/tac
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2003, Cisco Systems, Inc. All rights reserved.
