Cisco Systems 78-16845-01 appendix Using the get nestate Command, Database Is Not Available

Page 11

Appendix J Troubleshooting

J.2.20 Using the get nestate Command

J.2.20 Using the get nestate Command

The get nestate command-line interface (CLI) command available in the ctm utility in the EMS server bin directory returns the provisioned operational state (NE_Info_Table: NEState) and the read-only modifiers to the operational state (NE_Info_Table: NEDiscoveryState). The get nestate command returns the following possible values:

Preprovisioned

In Service

Out of Service

Under Maintenance

In Service–Initializing

In Service–Sync Configuration

In addition, the show nelist command lists all of the NEs with the following information:

NE database ID

NE IP address

Model type

SID

Network partition ID

Operational state

J.3 Client Connectivity Problems

The CTM client might not be able to connect to the CTM server for various reasons. Complete the following procedures in the order listed until the problem is resolved.

J.3.1 Database Is Not Available

If the CTM client cannot connect to the CTM server, verify that the database is available.

Step 1 Log into the CTM server as the Oracle user.

Step 2 Enter the following command to connect to the database: sqlplus ctmanager/ctm123!

Step 3 If the error message “maximum processes exceeded” is received, the maximum number of database connections has been reached. Close several clients or ask the database administrator to increase the maximum number of processes for the database.

Cisco Transport Manager Release 6.0 User Guide

 

78-16845-01

J-11

 

Image 11
Contents Troubleshooting Conditions that Affect CTM Server Performance Server ProblemsCTM 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 Performance Monitoring Data Is Not Displayed Problems with ONS 15530 and ONS 15540 ConfigurationONS 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 Database Is Not Available Using the get nestate CommandCannot Log In as Provisioner or Operator Database Timeout OccursAre the CTM Client and the CTM Server Connected? Model Index Is Unknown Cannot Authenticate User Message AppearsAdded 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 Bandwidth-Intensive Operations Are Blocked NE Displays Incorrect Configuration Management DataCannot Customize the Network Map Snmptrap How Do I Collect Thread Dumps?Click OK Client Debug Messages How Do I Replace the Alarm Interface Panel?CTM GateWay/TL1 Problems Cisco CRS-1 and Catalyst 6509 Problems CTM Does Not Receive Traps from the Catalyst Cat6509 enable# set snmp trap enable allSyslog CTM Does Not Receive syslog Events from the CatalystCTM 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 Load a Software Image on the Catalyst 6509? How Do I View the Snmp Configuration on the Catalyst 6509?Output is similar to the following example CTM Cannot Discover an XR 12000 Node Reporting XR 12000 Issues5 XR 12000 PM Collection Issues 4 XR 12000 Alarm and Event Reporting Issues7 XR 12000 NE Explorer Applications Are Disabled 6 XR 12000 BGP and CDP Neighbor Discovery IssuesNo Nodes Are Discovered Discovery Issues at StartupDiscovery Mechanism Node Name Is Incorrect in the Database Output of the switch CLI, selnd, and dbndsNode IP Is Incorrect in the Database Node Alarm Is Shown Incorrectly in the DatabaseCTM State Is Incorrect Reachable Node Is Shown as UnreachableDiscovery Issues at Runtime Collect the output of the switch CLI, selnd, and dbnds Equipment Management Problems Node Mode Remains Ls -ltr *.9 SMCARD01SRM.CF SMCARD01RPM.CF Node Resync Mode IsEMCSnmpFunccProcFuncGenNodeBulkFile1 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 All the Cards Under a Node Are Missing Network Element Discovery IssuesCisco Transport Manager Release 6.0 User Guide 78-16845-01 Appendix J Troubleshooting Alarm Processing Basics Figure J-2 Client/Server Architecture for Alarm Components XML Schema for Alarm RulesFigure J-3 Correlated Alarm Rule Diagram Figure J-5 Transient Alarm Rule Diagram Alarm Severity and Object SeverityCisco 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 Basics Chassis View ProblemsCard Not Displayed in the Chassis View Lines Not Displayed in the Chassis View10.6.4 DCA/DCB Status Not Displayed on PXM Cards Ethernet Status Not Updated on PXM CardsHIST, CBRX, and Cbtx Status Not Updated in MGX Nodes RPM Card Status Not UpdatedWrong Tooltip Is Displayed Configuration Center ManagementConfiguration Center Framework Lines Not SelectableChoose Tools Configuration Center from any application Cannot Launch the Configuration CenterAppendix J Troubleshooting Configuration Center Management Element Tab-Internal Frame Does Not Launch Element Management-Drag and Drop Within Configuration CenterCross Application-Configuration Center as Drag Source Appendix J Troubleshooting Configuration Center Management XML Parsing Error Configuration Center-Element ManagementDetails, Create, Delete, and Refresh Buttons Are Not Enabled Snmp No Data ErrorSnmp Set Error Snmp Timeout 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 Centers Connection Tab Does Not Respond Configuration Center GUI-CM Server-Reported ErrorsDATABASEERRORDatabase error %s Appendix J Troubleshooting Connection Management Problems Cmsvr Errors Cannot Create One-Segment Hybrid Unsupported Service Type-General node-slot-port-version TestConn or TestDelay Failed with Switch Error Cmsvr-Connection Diagnostic IssuesConnection Trace Failures Connection Up/Down/Reroute FailedCmgrd Figure J-6 Connection Management Subsystem High-Level Connection Management Subsystem ArchitectureCmgrd-Sdbroker Errors Related key index entries cmgrd, sdbroker, vpi/vci Appendix J Troubleshooting Connection Management Problems 100 Cmgrd Errors101 102 103 Cmgrd-Switch Errors104 105 106 107 Diagnostics Center Problems108 Diagnostics Center Framework109 Cannot Launch Diagnostics Center110 111 Diagnostics Center Does Not Respond GUI Is Grayed OutDrop Target Displays Incorrect Object or Object Data 112 Diagnostics Center Server-Specific Issues113 XML Parser ErrorSnmpcommtimeout Error While Polling MIB Objects 114 Node Sync-Up Status Are Not Shown in the Diagnostics CenterNode Resync Fails Polling of Real-Time Counters Fails115 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 Pmcollector-Generic Troubleshooting Performance Management Collection and Parsing ProblemsPM Collection Issues Miscellaneous Issues or Problems in Diagnostics Center118 119 PM Collection Fails for the Node-Log File Shows Snmp failed120 PM Collection Fails for the Node-Log File Shows Ftp failed121 Statistics Report ProblemsPM Parsing Issues StatsParser-Generic TroubleshootingYou Generated a Report but Do Not See Data for a Long Time You See FDNs for Other Entities when You Generate a ReportStatistics Report You Collected Data but You See No Data Available123 Service Agent ProblemsUtilization Report Value Is Greater than 100% RtmProxy124 Registration with RtmProxy FailedNot Receiving Any Traps 125 Audit Trail Logging Mechanism ProblemsManager Gets Deregistered Nodal Community Strings Do Not Work126 Miscellaneous ProblemsAuditLogger.conf Usage Audit Trail Log File Naming Convention127 Nodes Stay in Mode 1 After ColdStartConfig Change or Provisioning Activity Not Reflected on CTM 10.13.1 NTS128 How To Interpret NTS Log129 Connection Inconsistency Between the Switch and GUIData Inconsistency 130 Each output line is similar to this131 Process ID of the sdbroker will be returned132 Inconsistent Connection StatusInconsistent Connection Secondary Status 133 Incomplete ConnectionsFTP Daemon Overview Generic TroubleshootingFTP Username and Password CTM FTP Daemon135 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 137 Failed to Acquire a Session with a SwitchFailed to Acquire Session After All Retries General Log Information138
Related manuals
Manual 68 pages 52.71 Kb