|
|
Table Of Contents
Release Notes for Cisco Broadband Troubleshooter Release 3.3
New and Changed Information in CBT 3.3
Downloading and Upgrading CBT 3.3
Requirements for Installing DST Operating System Patches
Using Subscriber Traffic Management with CBT 3.3
Disabling or Enabling Password Text Display
Enabling Instantaneous CPU Assessment for Spectrum Polling
Sorting Support in the Trace Window
Mapping Hostnames from Applet to Servlet
Configuring Administrative Parameters for Spectrum Analysis
Using Auto-Select in the Trace Window
Troubleshooting Tips for CBT 3.3
Troubleshooting Continuous Sweep Spectrum Operation in CBT 3.3
Changing Server Ports in XML Script
Saving System Message Logs for Troubleshooting
Verifying Installation Status on the CBT 3.3 Server
Release Notes for Cisco Broadband Troubleshooter Release 3.3
Cisco Broadband Troubleshooter Release 3.3
OL-14014-01
June 28, 2007Multiple Service Operators (MSOs) and Cable companies provide a variety of services such as TV, video on demand, data, and voice telephony to subscribers. Network Administrators and radio frequency (RF) technicians need specialized tools to monitor and resolve RF problems in the cable plant.
Cisco Broadband Troubleshooter 3.3 (CBT 3.3) is a simple, easy-to-use tool designed to recognize and resolve such issues with efficiency and accuracy.
This document describes the new features and configurations introduced in CBT release 3.3, with resolved caveats and additional references.
Contents
This document describes CBT enhancements and feature sets for multiple versions of CBT in the following sections:
•
New and Changed Information in CBT 3.3
•
New and Changed Information in CBT 3.3
Cisco Broadband Troubleshooter Release 3.3 introduces significant enhancements, while sustaining several additional features introduced in prior versions (CBT 3.2 and CBT 3.1).
•
New Features in CBT 3.3
Cisco Broadband Troubleshooter Release 3.3 introduces the following categories of enhancements and features:
•
•
•
•
•
CBT 3.3 Download File Sizes
Table 1 summarizes approximate download file sizes for CBT 3.3.
Table 1 CBT 3.3 File Sizes
Solaris
CBT33-Solaris.tar.gz
209 MB
Linux
CBT33-Linux.tar.gz
268 MB
Windows
CBT33-Win.exe
155 MB
1 Approximate compressed download file size.
Administrative and Security Enhancements
•
•
•
•
•
•
•
•
•
Cisco CMTS Support and Licensing Enhancements
•
•
•
Enhanced Hardware Server and Client Support
Windows Systems
Windows systems supported include Windows 2000, Windows XP, and Windows XP Workstation with Linux Enterprise Edition.
UNIX Server Systems with Solaris
The following environment supports 10 Cisco CMTS headend systems:
•
•
•
•
•
The following environment supports 50 or 100 Cisco CMTS headend systems:
•
•
•
•
•
The following environment supports 500 Cisco CMTS headend systems:
•
•
•
•
•
UNIX Server Systems with Linux
The following environment supports 10, 50, or 100 Cisco CMTS headend systems:
•
•
•
•
PC Server Systems for Windows
The following environment supports 10, 50, or 100 Cisco CMTS headend systems:
•
•
•
•
UNIX Client Machine with Solaris
The following client system supports CBT 3.3 on Solaris:
•
•
•
UNIX Client Machine with Linux
The following client system supports CBT 3.3 with Linux:
•
•
•
PC Client Machine with Windows
The following client system supports CBT 3.3 with Windows:
•
•
•
Enhanced Support for Operating Systems and Web Server Applications
CBT 3.3 offers enhanced support for the following operating systems and web server software environments:
•
•
•
•
•
•
DST Patch for Operating Systems
CBT 3.3 introduces the operating system patch associated with recent Daylight Savings Time (DST) requirements.
Java Runtime Environment in CBT 3.3
CBT 3.2 supported the Java Runtime Environment (JRE) through JRE version 1.4.1. CBT 3.3 comes with Java J2SE Runtime Environment 5.0 embedded in it.
We recommend upgrading to JRE 5.0 on the client side to benefit from the latest enhancements, caveat resolutions, and security features, specifically for the Solaris platform.
Linux Operating System
CBT 3.3 introduces support for Red Hat Enterprise Linux products and the Red Hat Desktop operating system. We recommend upgrading from prior Linux versions, such as Linux Red Hat 7, 8, and 9, as these prior versions have reached the end of their support lifetimes.
Solaris Operating System
CBT 3.3 introduces support for the Solaris operating system through Solaris 10. CBT 3.2 supported Solaris through Solaris 8. We recommend upgrading to Solaris 10 for use with CBT 3.3 to gain support for high-performance server machines that require Solaris 10, and related CBT 3.3 enhancements.
Tomcat Application Server
CBT 3.3 introduces upgraded support for the Tomcat Application Server. With the prior CBT 3.2 version, support was limited to jakarta-tomcat-4.1. CBT 3.3 extends support to include apache-tomcat-5.5.15. The latest Tomcat version introduces scalability and reliability enhancements supported in CBT 3.3, performance optimizations, and reduced garbage collection.
CBT 3.3 implements the latest Tomcat application upgrade, and it is not necessary to download this application server separate from an upgrade to CBT 3.3.
Windows Operating System
CBT 3.3 supports the latest Windows operating systems from Microsoft, such as Windows 2000 or Windows XP. No additional Windows upgrades are required for CBT 3.3.
SNMP MIBs
CBT 3.3 introduces support for additional Management Information Bases (MIBs) and related network management enhancements.
•
–
–
–
•
•
•
•
•
•
In CBT 3.2, the STM feature obtained Enforce Rules and Get All Violators with the following obsolete MIB objects:
–
–
These obsolete MIB objects are not used by CBT 3.3, in which STM tools are compatible with the latest MIB changes supported in Cisco IOS, through release 12.3(21)BC.
Refer to the following document on Cisco.com for detailed information about MIBs support in relation to CBT 3.3:
•
Trace Window Enhancements
•
•
•
Refer to the Cisco Broadband Troubleshooter Release 3.3 User Guide for additional information about using the Trace Window.
Troubleshooting Enhancements
The Flap List Analyzer management functions are enhanced to support detection of flap lists that may comprise hundreds of cable modems. In cases in which the number of cable modems exceeds 2,000, CBT 3.3 prompts you of the quantity of cable modems, and provides you with the option to either continue or cancel the Flap List Analyzer functions. CBT 3.3 shows the number of cable modems within the Flap List Analyzer.
Resolved Caveats for CBT 3.3
Table 2 describes CBT 3.3 enhancements that resolve prior caveats in earlier CBT releases.
Table 2 Resolved Caveats in CBT 3.3
CSCsb95957
CBT 3.3 updates the MIBs by which the Subscriber Traffic Manager feature obtains Enforce Rules and Violator Status. CBT 3.3 replaces the obsolete MIB object supporting Subscriber Traffic Management (STM) with the latest objects in the related MIB. This enhancement is supported for the Cisco IOS STM feature after Cisco IOS Release 12.3(9a)BC.
Refer to the following section or document on Cisco.com for detailed information about MIBs support in relation to CBT 3.3:
•
CSCsc09577
CBT 3.3 introduces and supports a mechanism by which scheduled polling events do not consume CPU processing, as was the case in prior CBT releases. The prior issue related to the SpecDataMaxCPU parameter being exceeded.
The SpecDataMaxCPU parameter now represents a gateway check that stops new CBT requests from being created if the CPU utilization exceeds a certain threshold.
CSCsc09669
CBT 3.3 introduces a new mechanism by which network administrators may control Spectrogram settings, such as upper and lower frequencies, polling intervals, and step size. These functions are supported in Trace Window Spectrogram displays. Prior releases of CBT did not support these Spectrogram administrative controls and configuration parameters.
Refer to the "Configuring Administrative Parameters for Spectrum Analysis" section for additional information.
CSCsc13740
CBT 3.3 introduces support for checking CPU utilization, and supports the associated SNMP MIBs that enable this function in the Trace Window. Refer to the following section or document on Cisco.com for related information:
•
CSCsc13923
CBT 3.3 retains the security of hidden passwords, even when the Password field is highlighted.
CSCsc29221
CBT 3.3 correctly reports the specific CBT release that must be installed when valid licensing error messages are displayed.
CSCsc29256
CBT 3.3 enables you to remove a scheduled polling event that is running, without having to stop it first. CBT 3.3 removes the associated row in the ccsSpectrumRequestTable display, even when the polling event is not stopped prior to its removal.
CSCsc29262
CBT 3.3 resolves occurrences, in prior CBT releases, of a counter locking problem in the Trace Window display, in circumstances in which CBT was closed without first stopping or closing the Trace Window.
CSCsc74283
CBT 3.3 resolves occurrences, in prior CBT releases, in which the ccsSNRRequestEntry MIB object was not cleared properly, when the CBT server was shut down.
CSCsd47616
CBT 3.3 introduces support for checking cable interface line card CPU utilization, and the associated SNMP MIBs that enable this function in the Trace Window. Refer to the following section or document on Cisco.com for related information:
•
CSCse00909
CBT 3.3 supports the latest Cisco uBR10-MC5X20S/U/H broadband processing engines (BPEs).
CSCse38589
CBT 3.3 resolves occurrences, in prior CBT releases, in which the graphical user interface (GUI) would become inaccessible when stopping the application. This prior issue arose when the poller was run for a few hours, and related to Tomcat processes and Telnet session timeouts.
CSCsf96230
CBT 3.3 disables the auto-select behavior for entries in the Trace Window, and CBT 3.3 introduces the ability to sort and reverse-sort all fields of the Trace Window Criteria dialog box. Refer to the Cisco Broadband Troubleshooter Release 3.3 User Guide for additional information.
CSCsg32141
CBT 3.3 introduces support for CMTS hostnames to include dotted notation. Refer to the "Administrative and Security Enhancements" section for additional information.
CSCsg39114
The GS Analyzer tool of CBT 3.3 adds more efficiency to the maintenance and processing of information in relation to the cdxIfCmtsCmStatusLastResetTime MIB object. Prior to CBT 3.3, related limitations had a negative impact on Flap List troubleshooting on Cisco CMTS headends supporting 7,200 more cable modems.
CSCsg46989
CBT 3.3 introduces a standard feature by which Cisco CMTS headend systems are listed first by name, then by IP address. Prior CBT versions did not support CMTS hostnames. Refer to the "Administrative and Security Enhancements" section for additional information.
CSCsg74720
CBT 3.3 introduces enhanced Flap List Analyzer functions that provide warnings about large numbers of cable modems on a given Cisco CMTS. Refer to the "Troubleshooting Enhancements" section for additional information.
Upgrading to CBT 3.3
This section describes installation, upgrade, and patch installation procedures for CBT 3.3. This section contains the following procedures:
•
•
Downloading and Upgrading CBT 3.3
Use the following steps to download and to install CBT 3.3 on a system with the Linux, Solaris, or Windows operating systems.
Using TCP Ports for CBT 3.3 Upgrade and Operation
Note
We recommend ports other than 8005, 8080, 9080, 9443, or 9082.
The following are the default ports used by CBT 3.3:
•
•
•
•
•
•
CBT 3.3 uses the following port ranges for spectrum operations. Spectrum events such as Trace Window, Spectrogram, CNR Trending, and the Generic Query use a specified range of port numbers for operation.
•
•
•
•
CBT 3.3 Download and Upgrade
Step 1
•
http://www.cisco.com/cgi-bin/tablebuild.pl/cbt
•
–
–
–
–
Step 2
•
a.
b.
c.
•
a.
b.
c.
Step 3
•
•
•
–
–
Step 4
•
•
•
–
–
Note
Step 5
•
•
www.cisco.com/go/license/public
Note
Demonstration copies are available either via the Internet, or as an ordered accessory for a universal broadband router product. The copies supplied with a universal broadband router product include a demo license certificate with a PAK key. The copy available from the Internet uses a registration page where the PAK key is emailed to you.
Step 6
•
1.
2.
3.
•
1.
2.
3.
•
1.
2.
3.
Note
Requirements for Installing DST Operating System Patches
CBT 3.3 requires that the latest operating system patches be installed for all platforms supported by CBT 3.3. Refer to the "Enhanced Support for Operating Systems and Web Server Applications" section for additional information about supported platforms.
JRE OS-Level Requirements
CBT 3.3 supports the latest Java Runtime Environment (JRE 5.0) platform. However, the network administrator must ensure that all OS-level patches are installed to avoid system problems with CBT 3.3. This section describes patch requirements according to platform.
•
–
•
–
–
•
–
Australia—#102178: Daylight Saving Time (DST) Changes for Australia (2006)
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102178-1United States (2007) and additional countries http://sunsolve.sun.com/search/document.do?assetkey=1-26-102178-1
Using CBT 3.3
CBT 3.3 introduces the following new procedures and enhanced configurations supported in release 3.3. These procedures are not supported in releases prior to CBT 3.3. Refer also to the "Related Documentation" section for further CBT 3.3 documentation and configuration information.
General Procedures for CBT 3.3
•
•
CPU Procedures for CBT 3.3
•
Trace Window Procedures for CBT 3.3
•
•
•
•
Using SNMP MIBs in CBT 3.3
Cisco Broadband Troubleshooter (CBT) 3.3 uses the following SNMP MIBs in the Cisco IOS 12.3 BC Software Release train. Refer also to the "Resolved Caveats for CBT 3.3" section.
•
•
•
•
•
•
•
•
–
–
–
–
•
•
•
–
–
–
–
–
–
When extracting the downloaded CBT 3.3 file, these MIBs are placed by default in the following path:
<CBT Install Directory>/httpServer/webapps/ROOT/WEB-INF/mibs
Note
Generally, all read and create objects in the ccsSpectrumRequestTable and ccsSNRRequestTable can be set with spectrum management tools in CBT 3.3. These objects require a WRITE community string:
•
–
–
–
–
–
–
–
•
–
–
–
For additional MIBs information for the Cisco CMTS, refer to the following resources on Cisco.com:
•
•
http://www.cisco.com/pcgi-bin/Support/Mibbrowser/unity.pl
Using Subscriber Traffic Management with CBT 3.3
To use the Subscriber Traffic Management (STM) feature of CBT 3.3, the cable qos enforce-rule command on the Cisco CMTS must be used with a QoS profile that is not created by the cable modem. Any in-use QoS profile, such as one created by a cable modem, can be turned into a management profile.
Note
To create a management profile, follow these steps:
Disabling or Enabling Password Text Display
CBT 3.3 enables you to display password text, or to disable password text display according to your needs. By default, this parameter is set to YES. If you set the corresponding parameter to NO, CBT does not display password text when the Password field is displayed.
Perform the following steps to disable or to enable password text display for one or more user names.
Step 1
•
•
Step 2
•
Step 3
Step 4
Enabling Instantaneous CPU Assessment for Spectrum Polling
CBT 3.3 enables the option of preventing excessive CPU consumption in circumstances in which the Trace Window, Spectrogram functions, or Scheduled Polling features might otherwise exceed CPU bandwidth.
CBT has provisions to instantaneously check the CPU utilization and prevents the spectrum operation if the CPU utilization exceeds the CPU thresholds (value of SpecDataMaxCPU parameter).
Perform these steps to enable or disable CPU assessment in the Trace Window Criteria dialog box, the Spectrogram Criteria dialog box, or the Spectrum Data Clients dialog box before launching the spectrum event.
DETAILED STEPS
Step 1
Step 2
•
•
•
Step 3
Figure 1
Check CPU Util Dialog Box
Step 4
This setting means that the CPU utilization is checked and compared with the SpecDataMaxCPU parameter. Upon positive results, the spectrum operation gets started. The spectrum data is collected continuously with the specified poll interval.
One sweep corresponds to a single polling of spectrum data. After 10 such polling events, CBT again checks the CPU Utilization and compares it with the SpecDataMaxCPU parameter. If the results are positive, the spectrum operation continues; otherwise, the continuous query is stopped. If the number of sweeps is 1, then the CPU utilization is checked before every polling of spectrum data.
Step 5
Viewing Trace Windows
Some browsers give the user the ability to stop pop-up windows from being launched by the browser. CBT 3.3 normally launches a new window to display the trace and spectrum data charts. If the data chart window does not appear and the browser is configured to stop pop-up windows from launching, you can configure CBT 3.3 to display data charts within the browser window.
To configure CBT 3.3 to display data charts within the browser window, perform the following steps:
Step 1
Step 2
Sorting Support in the Trace Window
CBT 3.3 introduces sorting support for the List fields in the following windows or dialog boxes:
•
•
•
•
•
To change the order of sorting, perform the following steps:
Step 1
•
•
•
•
•
Step 2
Mapping Hostnames from Applet to Servlet
CBT 3.3 introduces support for hostname-based communications between applet and servlet on the network, in addition to sustaining IP-based communications, as with the prior CBT 3.2.
In CBT 3.2 all the communication between the applet and the servlet was based only on the IP address of the server. Every request and response between the applet and servlet had the IP address in the URL. CBT 3.3 removes this limitation, to support both hostnames and IP addresses.
This mapping configuration procedure changes the UseHostName parameter of the GUNSLINGER.INI file. By default, this value is NO in CBT 3.3. Changing this value to YES enables hostname-based communication between applet and servlet, and removes IP addresses from corresponding displays and processing.
Some Web proxy functions only allow hostname-based IP communication, and otherwise drop communications with IP addresses in the URL. This feature is helpful in such cases.
Prerequisites
This procedure requires that applet and servlet hostnames be established and otherwise functional on the network prior to mapping hostnames in CBT 3.3. Both the client and server should be able to resolve the hostname of the CBT server machine.
Perform these steps to map hostnames from applet to servlet.
Step 1
•
•
Step 2
•
•
Step 3
Step 4
Configuring Administrative Parameters for Spectrum Analysis
CBT releases prior to CBT 3.3 support options for spectrum operation parameters, and CBT 3.3 continues support for these parameters. CBT 3.3 introduces support for administrators to configure upper and lower limits for multiple fields in the Spectrum Operations windows. CBT 3.3 introduces additional configurable parameters in the SPECTRUM.INI file.
Perform the following steps to define administrative upper and lower limits in Spectrum Operations windows:
Step 1
•
•
Step 2
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
You can configure the upper and lower limit for the start, stop frequency, poll interval, step size and data points. While entering such data spectrum parameters, CBT 3.3 sustains native-level validation, and additionally, CBT 3.3 validates entries with respect to the newly configured limits in the SPECTRUM.INI file. The following list describes various fields and supported ranges for validation in a Spectrum Event:
•
•
•
–
–
Validation is performed on Center Frequency and Frequency Span in the following way:
–
–
–
As a result, these values should be in the range 5 to 65. In this way, both the fields are validated.
•
–
–
•
•
•
•
•
•
•
–
•
•
Note
Step 3
CBT 3.3 also supports additional checking with respect to the administratively configured values in the SPECTRUM.INI file. When changing this file, all the field values should also be in the range specified, and saved to the SPECTRUM.INI file for non-default configurations.
Note
Using Auto-Select in the Trace Window
CBT 3.3 does not select any given field in the Trace Window by default. To retrieve and display information for any given field in the Trace Window display, select the desired field.
Troubleshooting Tips for CBT 3.3
This section contains the following procedures for verifying and troubleshooting CBT 3.3:
•
•
•
•
•
Troubleshooting Continuous Sweep Spectrum Operation in CBT 3.3
A non-standard behavior has been observed in which the Continuous Sweep Spectrum Operation of CBT 3.3 fails, even in circumstances in which the Single Sweep Spectrum Operation remains functioning. One example would be the proper Trace Window single sweep operation, but with failed continuous wweep behavior in the Trace Window.
CBT 3.3 requires that the following processes and tasks be used for Continuous Sweep Spectrum Operation.
Step 1
•
•
•
•
•
•
Refer also to the "Using TCP Ports for CBT 3.3 Upgrade and Operation" section.
Step 2
•
•
•
•
Changing Server Ports in XML Script
Cisco IOS Release 12.3(9a)BC changes the Tomcat server port in server XML script. The script is set to port 8105. This prevents possible port conflict when multiple Tomcat Web servers are running on the same workstation.
If required, perform the following steps to change the Tomcat server port in XML script to port 8105 and check for additional port conflicts:
Step 1
/opt/CSCOcbt/httpServer/conf
Step 2
•
•
•
•
Saving System Message Logs for Troubleshooting
When troubleshooting CBT 3.3, we recommend that message logs be saved and filtered in the following ways:
Step 1
This is a fixed-size log file that continuously removes the oldest entry as it is updated. This log file is not viewable using an editor (such as vi).
Step 2
Step 3
For Solaris and Linux, the log file is located at /opt/CSCOcbt/httpServer/logs/catalina.out. This file is viewable with viewing utilities such as vi, Cat, Tail, or others.
Note
Verifying Installation Status on the CBT 3.3 Server
The status of the installed CBT 3.3 server can be verified with the following steps.
Step 1
•
•
Step 2
•
ps -ef|grep dberoot 26449 1 0 Aug 18 ? 0:24 dbeng8 -x tcpip{ServerPort=2640} -q -ud -s local0 -m -c 16M -n cbtdbengine /opt•
Step 3
•
ps -ef|grep javaroot 26478 1 0 Aug 18 ? 0:39 /opt/CSCOcbt/jre/bin/java -DCBTpoller -cp /opt/CSCOcbt/httpServer/webapps/ROOT/root 26489 1 0 Aug 18 ? 148:55 /opt/CSCOcbt/jre/bin/java -Djava.endorsed.dirs=/var/CSCOcbt/httpServer/common/e
Note
•
Verifying the CBT 3.3 License
Perform the following steps to verify the CBT 3.3 installation license:
For Solaris and Linux, perform these steps:
1.
/opt/CSCOcbt/httpServer/webapps/ROOT/WEB-INF/classes/lic/License
2.
3.
/opt/CSCOcbt/httpServer/logs/ for error messages
For Windows, perform these steps:
1.
INSTALLATION_DIR\httpServer\webapps\ROOT\WEB-INF\classes\lic\License
2.
3.
Related Documentation
The following sections provide references related to CBT 3.3.
Related Documents
CBT 3.3
•
http://www.cisco.com/en/US/products/sw/netmgtsw/ps530/products_user_guide_list.html
•
Cisco IOS Release Notes for Cisco Universal Broadband Routers
•
http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/prod_release_note09186a0080326360.html
•
http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/prod_release_note09186a00803265f8.html
•
http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/prod_release_note09186a0080771b95.html
Standards
MIBs
Technical Assistance
This document is to be used in conjunction with the documents listed in the Related Documentation section.
Copyright © 2007 Cisco Systems, Inc. All rights reserved.
Posted: Tue Jul 31 18:23:32 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
