|
|
Troubleshooting Cisco Cable Manager
To verify Cisco Cable Manager Release 2.0 (CCM) server performance and reliability, use the following troubleshooting procedures described in this chapter:
You can back up and restore databases by using the Cisco EMF script located under <CEMF_INSTALL_DIR>/bin.
Step 2 Change to the directory <CEMF_INSTALL_DIR>/bin and enter: ./cemf shell.
A shell window with all the necessary Cisco EMF paths appears.
Step 3 Enter:
This command backs up the databases in <CEMF_INSTALL_DIR>/db and locates them in <CEMF_INSTALL_DIR>/backup/ with a note on the date when it was backed up.
Step 4 To restore a database, enter:
Enter the date in the form of <mm-dd-yyyy> and -d <db1 [db2 ...]> to represent the databases that need to be restored.
Cisco EMF records important run-time information in log files located under the <CEMF_INSTALL_DIR>/logs. These log files are ASCII files that contain all CCM application specific log messages.
By default, DEBUG entries are not included in these log files. To see log messages of DEBUG severity (this includes all other severities), edit the loggercommon.include file located in the <CEMF_INSTALL_DIR>/config/init directory.
 |
Tip By default the loggingLevelMask is set to 10. Change this setting to 15 to log all DEBUG level messages. See "Logging Messages Related to the PerfDR Accesses" section for an example of log levels. |
 |
Note Changing the level to 15 affects how quickly the log files are archived as .old files. Also, changes that you make to the loggercommon.include file do not take effect until you restart the controller process, for example, cblCtrl. Stop the Cisco EMF system and restart it for the changes to take effect. |
Whenever one of the three controller log files (ubrController.log, perfPollCtrl.log, or cblCtrl.log) reaches its maximum size as specified in the control file, it is archived to a .old file and a new log file is created.
Numerous other log files, which are stored in the <CEMF_INSTALL_DIR>/logs directory, are available for troubleshooting.
Occasionally, run the script listCores provided in <CEMF_INSTALL_DIR>/bin (typically /opt/cemf/bin). This report describes any core files affected by malfunctioning processes.
When you see affected core files, report them to Cisco Customer support.
To control the size of the cblCtrl.log file:
Step 2 Add an entry in the logger section of cblCtrl.ini for the size of the log file specified in KBytes.
Step 3 Stop and re-start Cisco EMF.
|
Note You can use this same procedure for the ubrController.log and perfPollCtrl.log files. |
See the following example of a section of the cblCtrl.ini for the logger section to specify a 5 MB cblCtrl.log file:
For quick fault isolation, CCM provides IP and MAC layer ping connectivity tests between the Cisco uBR7200 series universal broadband routers and individual cable modems. You can test connectivity for a single modem or multiple modems.
|
Note You must enter the telnet access information for the related Cisco uBR7200 series universal broadband routers in the uBR Access Parameter dialog box for the Ping feature to be available. |
See the "Applying uBR Access Parameter Configuration Settings" section.
You can use the Find ITCM/CM feature to locate or ping a particular cable modem by specifying any of the following items:
Step 2 From the right-click menu, select Diagnostics > Find Modem.
The Find Modem dialog box appears.
Step 3 Click the FindITCM/CM tab. Enter data into the appropriate fields and click Find.
The containment path of the cable modems appears in the Action Report dialog box.
Step 2 From the right-click menu, select Diagnostics > Find Modem.
The Find Modem dialog box appears.
Step 3 Click the PingITCM/CM tab. Click IPPing or MAC Ping.
The ping results appear in the Action Report dialog box.
You can use the Ping ITCM/CM feature to test the MAC layer and network layer connectivity of selected uBR and cable modems.
Step 2 From the right-click menu, select Diagnostics > Ping Modem.
The Ping Modem dialog box appears.
Step 3 Select the cable modems from the CM List window.
Step 4 Enter data into the appropriate fields and click IPPing or MAC Ping.
The ping results appear in the Action Report dialog box.
The logs used for Performance Reports are maintained in the /tmp/pert.log file. These logs are useful for viewing a history of the performance report runs and for viewing error messages generated by the reporting application.
To successfully generate performance reports:
¯ All the CORBA related processes that are started through "CEMF Start," including:
|
Tip You can verify CORBA related processes started by cemf start by viewing the output of the cemf query command. |
The Performance Reporting application uses the same mechanism as a regular Cisco EMF client to determine the Cisco EMF server/CORBA gateway host information. When Cisco EMF is installed, the gateway host information is based on information stored in the file:
/var/adm/Atlantech/system/info
To change the default port number used by the http server, make changes to the value of the property HTTP_PORT as follows:
./jre118/bin/jre -DHTTP_PORT=9010 -classpath .:./jre118/lib/rt.jar:./httpserver.jar Invoker
Step 2 On every client side installation, in the file:
<CEMF_INSTALL_DIR>/pert/PerformanceReport, replace 9010 with the appropriate port number in the following line:
./jre122/bin/java -DCGW_USERNAME=admin -DCGW_PASSWORD=admin -DHTTP_PORT=9010 -DDEBUG=0 -classpath [fill this in] PerformanceReport $*
In the client side installation file, <CEMF_INSTALL_DIR>/pert/PerformanceReport, replace -DDEBUG=0 with -DDEBUG=1 in the following line:
./jre122/bin/java -DCGW_USERNAME=admin
-DCGW_PASSWORD=admin -DHTTP_PORT=9010 -DDEBUG=0
-classpath [...] PerformanceReport $*
The default Cisco EMF username and password combination used for the CORBA gateway accesses that are used for generating Performance Reports is the default Cisco EMF administrator user and password combination:
To change the defaults, enter the following change for every client side installation in the file:
<CEMF_INSTALL_DIR>/pert/PerformanceReport
Change the values for the properties CGW_USERNAME and CGW_PASSWORD to the appropriate values in the following line:
./jre122/bin/java -DCGW_USERNAME=admin -DCGW_PASSWORD=admin -DHTTP_PORT=9010 -DDEBUG=0 -classpath [...] PerformanceReport $*
Performance Reports use a component of Cisco EMF called "perfDR" to gather performance data stored in the internal database.
By default the loggingLevelMask is set to 10. Change this setting to 15 to log all DEBUG level messages:
<CEMF_INSTALL_DIR>/config/init/loggercommon.include, loggingLevelMask = 15
<CEMF_INSTALL_DIR>/config/init/perfRepository.ini, loggingLevelMask = 15
The perfDR related messages are logged in the file:
<CEMF_INSTALL_DIR>/logs/perfRepository.log
|
Note The perfRepository process must be restarted for this change to take effect. |
You can view a history of the inventory report runs and generated error messages using the inventory log files. You can access and maintain the Inventory Report logs by using the Cisco EMF start menu:
To successfully generate inventory reports, ensure that the following processes are running on the Cisco EMF server machine:
|
Tip You can verify the CORBA related processes that are started through Cisco EMF by using the output of the cemf query command. |
The Inventory Reporting application uses the same mechanism as a regular Cisco EMF client to determine the Cisco EMF server/CORBA gateway host information. This information is based on the information stored in: /var/adm/Atlantech/system/info when you install Cisco EMF.
To change the default port number used by the http server, make changes to the value of the property HTTP_PORT as follows:
./jre118/bin/jre -DHTTP_PORT=9010 -classpath .:./jre118/lib/rt.jar:./httpserver.jar Invoker
Step 2 On every client side installation, in the <CEMF_INSTALL_DIR>/cirt/InventoryReport file, replace 9010 with the appropriate port number in the following line:
./jre122/bin/java -DCGW_USERNAME=admin -DCGW_PASSWORD=admin -DHTTP_PORT=9010 -DDEBUG=0 -classpath .:./argent.jar:./gui.jar:./cemcnr.jar:./ldap.jar:./providerutil.jar:./jndi.jar:./corbaInf.jar:./atl.jar InventoryReport $*
|
Note Repeat step 2 to make the same changes to <CEMF_INSTALL_DIR>/cirt/UbrInvReport |
In the client side installation file, <CEMF_INSTALL_DIR>/cirt/InventoryReport, replace -DDEBUG=0 with -DDEBUG=1 in the following line:
./jre122/bin/java -DCGW_USERNAME=admin
-DCGW_PASSWORD=admin -DHTTP_PORT=9010 -DDEBUG=0
-classpath [...] InventoryReport $*
|
Note Apply the same changes to <CEMF_INSTALL_DIR>/cirt/UbrInvReport |
The default Cisco EMF username and password combination used for the CORBA gateway accesses that are used for generating Inventory Reports is the default Cisco EMF administrator user and password combination:
To change the defaults, enter the following change for every client side installation in the file:
<CEMF_INSTALL_DIR>/cirt/InventoryReport
Change the values for the properties CGW_USERNAME and CGW_PASSWORD to the appropriate values in the following line:
./jre122/bin/java -DCGW_USERNAME=<admin> -DCGW_PASSWORD=<admin> -DHTTP_PORT=9010 -DDEBUG=0 -classpath .:./argent.jar:./gui.jar:./cemcnr.jar:./ldap.jar:./providerutil.jar:./jndi.jar:./corbaInf.jar:./atl.jar InventoryReport $*
|
Note Apply the same changes to <CEMF_INSTALL_DIR>/cirt/UbrInvReport |
You must configure and save the LDAP access information by using the Cisco EMF LDAP configuration dialog box before generating any Cable Modem Inventory Reports. If LDAP is not configured or accessible, the reporting application cannot determine the categories of the various cable modems.
See Configuring LDAP.
If you add a route to change an online_ip_unreachable cable manager to online, you must manually clear the alarm.
Posted: Tue Feb 25 05:21:35 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.