Cisco Systems 78-16845-01 appendix Alarm Processing Basics

Page 62

Appendix J Troubleshooting

J.10.5 Configuration Center, Chassis View, Diagnostics Center, and Statistics Report Problems

J.10.5.5 Configuration Center, Chassis View, Diagnostics Center, or Statistics Report Alarm Issues

This section includes the following information:

•J.10.5.5.1 Alarm Processing Basics, page J-62

•J.10.5.5.2 XML Schema for Alarm Rules, page J-63

•J.10.5.5.3 Alarm Severity and Object Severity, page J-65

•J.10.5.5.4 Severity Shown on Tree View Does Not Match Severity Shown on Platform, page J-66

•J.10.5.5.5 Alarm List Shows Alarm that Does Not Exist on Platform, page J-67

•J.10.5.5.6 Transient Event Has Disappeared Unexpectedly, page J-68

•J.10.5.5.7 Port in Tree View Displays Aggregate Alarm; However, No Children Exist Under Port, page J-68

J.10.5.5.1 Alarm Processing Basics

Alarm processing is done within the NMServer processes. The following are some vital points with regard to alarm processing:

•Alarm rules are defined in an XML file (/opt/svplus/xml/ruledata.xml). For details on XML schema alarm rules, see Figure J-2.

•GUI clients register for alarms by providing the parent FDN.

•GUI clients pull initial alarms from NMServer. After initial pull of alarms, all alarms are pushed to registered clients by NMServer when alarms occur.

•Object severity for any and all network elements is determined by the XML alarm rule.

•Administrative states of network element states are not displayed in the alarm list, only alarm states.

•Alarm List displays mostly active alarms, however some events are also displayed. For details on events versus alarms, see J.10.5.5.2 XML Schema for Alarm Rules, page J-63.

•Some alarms result in the network element having a different alarm severity then the actual alarm. For details on object severity versus alarm severity, see J.10.5.5.3 Alarm Severity and Object Severity, page J-65.

Alarms for various network elements are stored in memory cache in the NMServer Object Tree. GUI clients register for alarms from NMServer by providing the FDN of the network element for which they would like alarms. All alarms for network elements under the FDN registered will be sent if the parent FDN is registered. GUI clients may also update alarms, for example by flagging an alarm as acknowledged or manually clearing an alarm. These updates are done through the Alarm Repository component of NMServer. Figure J-2illustrates the client/server architecture for alarm components in NMServer.

Cisco Transport Manager Release 6.0 User Guide

 

J-62

78-16845-01

 

 

 

Page 61 Page 63
Image 62
Page 61 Page 63
Contents Troubleshooting Server Problems Conditions that Affect CTM Server PerformanceCTM Server Does Not Respond Cannot Connect to the CTM Server NE Connection State Is Listed as Unavailable Trap Port Is Unavailable Launching Tables Results in Database ErrorsSnmp Traps Are Not Forwarded from NEs Problems with ONS 15530 and ONS 15540 Configuration Performance Monitoring Data Is Not DisplayedONS 15501, ONS 15540, or ONS 15530 Is Not Reachable CTC-Based NE Is Not DiscoveredCTC-Based NE Is Not Reachable NE Model Type Appears as Unknown Circuits Are Not DisplayedCircuit State for Monitor Circuits Reads Duplicate ID Getinfo.sh Script Fails Memory Backup, Memory Restore, or Software Download FailsCannot Copy CTC Binary to the CTM Server Using the get nestate Command Database Is Not AvailableCannot Log In as Provisioner or Operator Database Timeout OccursAre the CTM Client and the CTM Server Connected? Cannot Authenticate User Message Appears Model Index Is UnknownAdded a New Software Version to the Wrong NE Cannot Delete an NECTC Fails to Start Cannot Schedule Jobs Cannot Delete a SubnetworkCannot Move an NE Between Subnetworks NE Displays Incorrect Configuration Management Data Bandwidth-Intensive Operations Are BlockedCannot Customize the Network Map How Do I Collect Thread Dumps? SnmptrapClick OK How Do I Replace the Alarm Interface Panel? Client Debug MessagesCTM GateWay/TL1 Problems Cisco CRS-1 and Catalyst 6509 Problems Cat6509 enable# set snmp trap enable all CTM Does Not Receive Traps from the CatalystCTM Does Not Receive syslog Events from the Catalyst SyslogCTM Does Not Collect Historical PM Data for the CRS-1 Memory Backup or Restore Fails for the CRS-1 Click NE Service How Do I Configure SSH on the CRS-1? Cannot Delete an Out-of-Service NE from CTMHow Do I Configure Telnet on the CRS-1? How Do I View the Snmp Configuration on the Catalyst 6509? How Do I Load a Software Image on the Catalyst 6509?Output is similar to the following example Reporting XR 12000 Issues CTM Cannot Discover an XR 12000 Node4 XR 12000 Alarm and Event Reporting Issues 5 XR 12000 PM Collection Issues6 XR 12000 BGP and CDP Neighbor Discovery Issues 7 XR 12000 NE Explorer Applications Are DisabledNo Nodes Are Discovered Discovery Issues at StartupDiscovery Mechanism Output of the switch CLI, selnd, and dbnds Node Name Is Incorrect in the DatabaseNode Alarm Is Shown Incorrectly in the Database Node IP Is Incorrect in the DatabaseReachable Node Is Shown as Unreachable CTM State Is IncorrectDiscovery Issues at Runtime Collect the output of the switch CLI, selnd, and dbnds Equipment Management Problems Node Mode Remains Ls -ltr *.9 SMCARD01SRM.CF Node Resync Mode Is SMCARD01RPM.CFEMCSnmpFunccProcFuncGenNodeBulkFile1 entering Appendix J Troubleshooting Equipment Management Problems Appendix J Troubleshooting Equipment Management Problems Appendix J Troubleshooting Equipment Management Problems Database Table Population Through Traps and Snmp Upload Appendix J Troubleshooting Equipment Management Problems Appendix J Troubleshooting Equipment Management Problems You should see something like the following Figure J-1shows the end-to-end architecture Figure J-1 CTM End-to-End Architecture Basic Issues Topology Discovery Issues Appendix J Troubleshooting CTM CLI Network Element Discovery Issues All the Cards Under a Node Are MissingCisco Transport Manager Release 6.0 User Guide 78-16845-01 Appendix J Troubleshooting Alarm Processing Basics XML Schema for Alarm Rules Figure J-2 Client/Server Architecture for Alarm ComponentsFigure J-3 Correlated Alarm Rule Diagram Alarm Severity and Object Severity Figure J-5 Transient Alarm Rule DiagramCisco Transport Manager Release 6.0 User Guide 78-16845-01 Alarm List Shows Alarm that Does Not Exist on Platform Transient Event Has Disappeared Unexpectedly Chassis View Problems Chassis View BasicsLines Not Displayed in the Chassis View Card Not Displayed in the Chassis ViewRPM Card Status Not Updated Ethernet Status Not Updated on PXM CardsHIST, CBRX, and Cbtx Status Not Updated in MGX Nodes 10.6.4 DCA/DCB Status Not Displayed on PXM CardsLines Not Selectable Configuration Center ManagementConfiguration Center Framework Wrong Tooltip Is DisplayedCannot Launch the Configuration Center Choose Tools Configuration Center from any applicationAppendix J Troubleshooting Configuration Center Management Element Management-Drag and Drop Within Configuration Center Element Tab-Internal Frame Does Not LaunchCross Application-Configuration Center as Drag Source Appendix J Troubleshooting Configuration Center Management Configuration Center-Element Management XML Parsing ErrorSnmp No Data Error Details, Create, Delete, and Refresh Buttons Are Not EnabledSnmp Timeout Error Snmp Set ErrorObject Not Found In Tree View Error Element Data Inconsistent with Switch Config Server Reports Error Messages Connection Management ProblemsConfiguration Center GUI-Framework Issues Appendix J Troubleshooting Connection Management Problems Appendix J Troubleshooting Connection Management Problems Cross Application-Connection List as Drag Source Configuration Center GUI-CM Server-Reported Errors Configuration Centers Connection Tab Does Not RespondDATABASEERRORDatabase error %s Appendix J Troubleshooting Connection Management Problems Cmsvr Errors Cannot Create One-Segment Hybrid Unsupported Service Type-General node-slot-port-version Cmsvr-Connection Diagnostic Issues TestConn or TestDelay Failed with Switch ErrorConnection Up/Down/Reroute Failed Connection Trace FailuresCmgrd High-Level Connection Management Subsystem Architecture Figure J-6 Connection Management SubsystemCmgrd-Sdbroker Errors Related key index entries cmgrd, sdbroker, vpi/vci Appendix J Troubleshooting Connection Management Problems Cmgrd Errors 100101 102 Cmgrd-Switch Errors 103104 105 106 Diagnostics Center Problems 107Diagnostics Center Framework 108Cannot Launch Diagnostics Center 109110 111 Diagnostics Center Does Not Respond GUI Is Grayed OutDrop Target Displays Incorrect Object or Object Data Diagnostics Center Server-Specific Issues 112113 XML Parser ErrorSnmpcommtimeout Error While Polling MIB Objects Polling of Real-Time Counters Fails Node Sync-Up Status Are Not Shown in the Diagnostics CenterNode Resync Fails 114115 Some Real-Time Counters Are Not ShownUnable to Start, Stop, or Modify Bert Operations 116 Cannot Perform Connection DiagnosticsUnable to Start/Stop IMA Link Test Patterns Miscellaneous Issues or Problems in Diagnostics Center Performance Management Collection and Parsing ProblemsPM Collection Issues Pmcollector-Generic Troubleshooting118 PM Collection Fails for the Node-Log File Shows Snmp failed 119PM Collection Fails for the Node-Log File Shows Ftp failed 120StatsParser-Generic Troubleshooting Statistics Report ProblemsPM Parsing Issues 121You Collected Data but You See No Data Available You See FDNs for Other Entities when You Generate a ReportStatistics Report You Generated a Report but Do Not See Data for a Long TimeRtmProxy Service Agent ProblemsUtilization Report Value Is Greater than 100% 123124 Registration with RtmProxy FailedNot Receiving Any Traps Nodal Community Strings Do Not Work Audit Trail Logging Mechanism ProblemsManager Gets Deregistered 125Audit Trail Log File Naming Convention Miscellaneous ProblemsAuditLogger.conf Usage 12610.13.1 NTS Nodes Stay in Mode 1 After ColdStartConfig Change or Provisioning Activity Not Reflected on CTM 127How To Interpret NTS Log 128129 Connection Inconsistency Between the Switch and GUIData Inconsistency Each output line is similar to this 130Process ID of the sdbroker will be returned 131132 Inconsistent Connection StatusInconsistent Connection Secondary Status Incomplete Connections 133CTM FTP Daemon Generic TroubleshootingFTP Username and Password FTP Daemon Overview135 Cwmftpd-File Not Available On SwitchFTP Sessions in Switch 136 10.13.3.7 421 Session Limit Reached10.13.3.8 499 Session Limit Reached General Log Information Failed to Acquire a Session with a SwitchFailed to Acquire Session After All Retries 137138
Related manuals
Manual 68 pages 52.71 Kb
Top Page Image Contents