|
|
6Retrieving Subscriber or Provisioning Data by Using an External Interface
7Using Southbound Application Program Interfaces in CCDM
8Setting Parameters in .INI Files
9Using and Customizing Troubleshooting Tips
10Viewing Real-Time Modem Status Reports
13Sample Code for Northbound and Southbound APIs
Cisco Cable Diagnostic Manager Release 1.0 (CCDM 1.0) is a web-based, network management application that is designed for the customer service representative (CSR) at a multiple system operator (MSO). An MSO provides a variety of cable services such as TV, data or voice telephony. The CSR uses CCDM to support the MSO's customers who have cable modems for high-speed data, or telephony. With CCDM, the CSR can provide first-line troubleshooting and support to a customer who is experiencing problems with a cable modem.
CCDM 1.0 runs on PCs, Linux workstations, and Solaris workstations. It provides the following functionality:
To simplify integration, guidelines and samples are provided for the script and HTTP options.
This section describes the system requirements for the following platforms:
You can install CCDM on a server that is running the Linux OS.
You can install CCDM on a server that is running the Solaris OS.
You can install CCDM on a server that is running the Windows OS.
After CCDM is installed on a server, you can access and use CCDM from a client computer with a web browser.
The routers must have the following attributes set to interact with CCDM.
 |
Note CCDM retrieves the Cisco IOS release number, router name, and router type by using SNMP. |
The following procedures describe how to install Cisco Cable Diagnostic Manager on each supported platform.
Step 2 Insert the CCDM CD-ROM into the CD-ROM drive.
Step 3 To mount the CD, enter:
Step 4 To change to the CCDM Linux directory, enter:
Step 5 To start the installation program, enter:
The CCDM server is now running.
Step 6 To start CCDM by typing a command, enter:
To launch CCDM by using a browser:
Open a browser and enter the URL for your CCDM server:
http://CCDM server IP address:8090/CCDMHomePage.html
Step 7 In the Log In window (see Figure 1), enter your username and password.
Step 8 (Optional) To stop CCDM, enter:
cd /opt/CSCOccdm/bin
./stop_app
To exit CCDM by using a browser:
From the Exiting CCDM Menu, choose Log Out.
Step 2 Insert the CCDM CD-ROM into the CD-ROM drive.
Step 3 To change to the CCDM Solaris directory and install CCDM, enter:
The CCDM server is now running.
Step 4 To start CCDM by typing a command, enter:
To launch CCDM by using a browser:
Open a browser and enter the URL for your CCDM server:
http://CCDM server IP address:8090/CCDMHomePage.html
Step 5 In the Log In window (see Figure 1), enter your username and password.
Step 6 (Optional) To stop CCDM, enter:
cd /opt/CSCOccdm/bin
./stop_app
To exit CCDM by using a browser:
From the Exiting CCDM Menu, choose Log Out.
Step 2 From Windows Explorer, double-click SETUP in CDROM_DRIVE\WIN\DISK1.
Step 3 Select the default answers to the installation questions.
The CCDM server is now running.
Step 4 To start CCDM by using Windows menus, choose:
Start > Programs > CCDM > Start CCDM
To launch CCDM by using a browser, open a browser and enter:
http://CCDM server IP address:8090/
Step 5 In the Log In window (see Figure 1), enter your username and password.
Step 6 (Optional) To stop CCDM, choose:
Start > Programs > CCDM > Stop CCDM
To exit CCDM by using a browser:
From the Exiting CCDM Menu, choose Log Out.
After you start CCDM, you see the CCDM task menu. A version of the menu that lists all the available tasks is shown in Figure 2:
The tasks in the menu are divided into the following groups:
The next sections describe the tasks within each group.
This section contains the following task:
This section contains the following tasks:
This section contains the following tasks:
This section contains the following tasks:
The number of tasks you see in the CCDM menu varies according to the type of user you are. There are three user types in CCDM, each with access to different tasks:
The menu for the CSR-T2 user is shown in Figure 3.
The menu for the CSR-T1 user is shown in Figure 4.
Figure 5 illustrates a high-level workflow of tasks that each type of user, the administrator and the CSR, performs in CCDM.
The first four tasks shown in Figure 5 are ones that only an administrator can perform.
The remainder of this guide explains these tasks in greater detail.
The last task shown in Figure 5 is one that a customer service representative performs.
In addition to the above tasks, the second-tier customer service representative can troubleshoot the modem by performing the following diagnostic tests:
This section describes the following important setup tasks that only a CCDM administrator can perform:
For security reasons, we recommend that you change the default password for the administrator.
To change the administrator password:
http://yourmachine:8090/CCDMHomePage.html
|
Note In the URL, yourmachine is the server on which you installed CCDM. |
The Login dialog box appears. See Figure 1.
Step 2 Log in as admin with the default password changeme.
Step 3 To change the password, from the Configuring CCDM menu choose Manage Users.
You can add users in CCDM by using either of the following methods:
For each user, the ASCII text file must contain the following three fields: User Name, Password, and User Type. Each field must be separated with a comma. A sample file is in the following locations:
The following example shows one user's data in this format.
|
Note For a complete description of each field in the ASCII file, see the online help for Import a List of Users. |
Step 2 To import a list of users, from the Running Utilities menu, choose Import a List of Users and specify the ASCII file that contains a list of users. (See Figure 6.)
or
To add a user manually, from the Configuring CCDM menu, choose Manage Users. (See Figure 7.)
You can add router information in CCDM by using either of the following methods:
If you choose to import an ASCII file, for each CMTS the file must contain information or a placeholder for the 13 fields described below.
A sample file is in the following locations:
The following example shows the data for a CMTS in this format:
|
Note For a complete description of each field in the ASCII file, see the online help for Import a List of CMTSs. |
To add the Cisco uBR7100, Cisco uBR7200, and Cisco uBR10000 series routers in CCDM:
Step 2 To import a list of routers, from the Running Utilities menu, choose Import a List of CMTSs and specify the ASCII file that contains a list of managed CMTSs. (See Figure 8.)
or
To add a router manually, from the Configuring CCDM menu, choose Manage CMTSs.
To successfully manage routers, make sure that you enable SNMP on these routers.
 |
Tip Verify that access lists, if configured in the router, allow for SNMP read access from your workstation. |
To add subscriber information in CCDM, you import an ASCII text file that contains the subscriber information.
For each subscriber, the ASCII text file can contain 12 fields. Each field, including blank ones, must be separated with | (the pipe symbol). The following fields are typical, although only the first one is required:
A sample file is in the following locations:
The following example shows the data for a subscriber in this format:
|
Note For a complete description of each field in the ASCII file, see the online help for Import Subscriber Data. |
To add subscriber information to CCDM:
Step 2 From the Running Utilities menu, choose Import Subscriber Data and specify the ASCII file that contains subscriber data. (See Figure 9.)
CCDM supports two types of interfaces:
This section describes using northbound interfaces in CCDM.
With CCDM you can set up an external interface to retrieve subscriber or provisioning data.
You can use the following methods to set up an external interface:
|
Note If you set an external interface for provisioning information and CCDM does not find provisioning data there, CCDM reverts to the local database. This fallback behavior does not apply to subscriber information. |
Figure 10 shows the dialog box where you specify the method. The remainder of this section describes how to set up an external interface with each method.
You can implement an external data retrieval application via a scripting language. To see a sample script that you can modify according to your needs, see "Northbound Shell Script for Retrieving Subscriber or Provisioning Information".
|
Note You can also implement an external data retrieval application in programming languages such as PL/SQL, C/C++, and Java, as long as it is embedded in a shell script. |
The script must support the ability to search for a cable modem's MAC address by entering the customer's phone number, IP address, or fiber node. The input parameters for the script are:
For example, the following script invokes a search for the modem's MAC address by using the phone number 408-123-4567:
The next script invokes a search for the modem's MAC address by using the fiber node SanJose_1:
The last script invokes a search for the modem's MAC address by using the IP address 172.2.3.1:
|
Note A MAC address query by phone number or fiber node invokes the subscriber information script. A MAC address query by IP address invokes the provisioning information script. |
The output of the script must be in the following format:
OUT_DATA=MAC followed by one or more MAC addresses (non-dotted format) separated by ^
The following examples show the output for one and two MAC addresses:
If you use a script to query subscriber information, it needs to support the ability to search for subscriber data, such as name and account number, by entering the MAC address of the subscriber's cable modem. The input parameters for the script are:
script-name GET_SUBSCRIBER MAC non-dotted-modem-mac-address
For example, the following script invokes a search for subscriber data by using the MAC address 001c.ab23.45fe in a non-dotted format:
The output of the script must be in the following format:
OUT_DATA=SUBSCRIBER^Account Number=value^Name=value^Address=value^Phone=value^Class of Service=value^Fiber Node=FIBER_^misc1=value1^misc2=value2
The following example shows the output for a subscriber's data, which includes two user-defined fields after Fiber Node:
|
Note In the Real-Time Modem Status Report, CCDM displays subscriber information in the order in which the fields are returned from the script. |
If you use a script to query provisioning information, it needs to support the ability to search for provisioning data, such as CMTS and cable modem IP addresses, by entering one MAC address of a cable modem or multiple MAC addresses of multiple cable modems. The input parameters for the scripts are:
For example, the following script invokes a search for provisioning data by using the MAC address 001c.ab23.45fe:
The output of the script must be in the following format:
OUT_DATA=PROVISION^cmts-ip-address^cm-ip-address^
The following example shows the output for provisioning data:
OUT_DATA=PROVISION^127.23.45.1^127.23.127.5^
The next script example invokes a search for provisioning data by using multiple MAC addresses, 001c.ab23.45fe and 001c.ab23.45ff:
The output of the script must be in the following format:
OUT_DATA=PROVISION^mac1=cmts-ip-address,cm-ip-address^mac2=cmts-ip-address,cm-ip-address^
The following example shows the output for provisioning data:
OUT_DATA=PROVISION^001cab2345fe=127.23.45.1,127.23.127.5^001cab2345ff=127.23.45.1,127.23.127.5^^
If an error occurs within the script or the embedded application called by the script, the script should return the output in the following format:
The following example shows output for an error:
OUT_DATA=ERROR^Unable to query the subscriber database.^
In the graphical user interface (GUI), CCDM displays the error message to the user in a message box.
To retrieve subscriber or provisioning information by using a script:
Step 2 From the Configuring CCDM menu, choose Set External Interfaces to specify one or both of the following:
See "Directions for Troubleshooting the Script".
You can implement an external data retrieval application via an application running on an HTTP server. CCDM sends the request to the HTTP server via the POST method. To see a sample application file that you can modify according to your needs, see "Northbound Java Code for Retrieving Subscriber or Provisioning Information".
The application running on an HTTP server must support the ability to search for a cable modem's MAC address by entering the customer's phone number, IP address, or fiber node. CCDM sends the following parameters to the appropriate server:
For example, the following parameters search for the modem's MAC address by using the phone number 408-123-4567:
The response from the server must be in the following format:
OUT_DATA=MAC followed by one or more MAC addresses separated by ^
The following examples show the output for one and two MAC addresses:
OUT_DATA=MAC^001c64ff23ef^013e45ed1245^
|
Note When the SEARCH_TYPE is PHONE, the subscriber information URL is used. When the SEARCH_TYPE is IP, the provisioning information URL is used. |
If you use an application running on an HTTP server to query subscriber information, it needs to support the ability to search for subscriber data, such as name and account number, by entering the MAC address of the subscriber's cable modem. CCDM sends the following parameters to the server:
For example, the following parameters search for subscriber data by using the MAC address 001cab2345fe:
The response from the server must be in the following format:
OUT_DATA=SUBSCRIBER^Account Number=value^Name=value^Address=value^Phone=value^Class of Service=value^Fiber Node=FIBER_^misc1=value1^misc2=value2
The following example shows the output for a subscriber's data, which includes two user-defined fields after Fiber Node:
OUT_DATA=SUBSCRIBER^Account Number=123456^Name=Doe_John^Address=123 Tasman, San Jose, CA 93443^Phone=4081234567^Class of Service=N/A^FiberNode=FIBER_1^Customer Since=1999^Account Status=Paid
|
Note In the Real-Time Modem Status Report, CCDM displays subscriber information in the order in which the fields are returned from the script. |
If you use an application running on an HTTP server to query provisioning information, it needs to support the ability to search for provisioning data, such as CMTS and cable modem IP addresses, by entering the MAC address of the cable modem or multiple MAC addresses of multiple cable modems.
To search for provisioning data by entering a single MAC address, CCDM sends the following parameters to the server:
For example, the following parameters search for provisioning data by using the MAC address 001cab2345fe:
The response from the server must be in the following format:
OUT_DATA=PROVISION^cmts-ip-address^cm-ip-address^
The following example shows the output for provisioning data:
OUT_DATA=PROVISION^127.23.45.1^127.23.127.5^
To search for provisioning data by entering multiple MAC addresses, CCDM sends the following parameters to the server:
For example, the following parameters search for provisioning data by using the MAC addresses 001cab2345fe and 0001abcdefff:
The response from the server must be in the following format:
OUT_DATA=PROVISION^mac1=cmts-ip-address,cm-ip-address^mac2=cmts-ip-address,cm-ip-address^
The following example shows the output for provisioning data:
OUT_DATA=PROVISION^001cab2345fe=127.23.45.1,127.23.127.5^0001abcdefff=127.23.45.1,127.23.127.5^
If an error occurs within the application running on an HTTP server, the script should return the output in the following format:
The following example shows output for an error:
OUT_DATA=ERROR^Unable to query the subscriber database.^
In the GUI, CCDM displays the error message to the user in a message box.
To retrieve subscriber or provisioning information with an application on an HTTP server:
Step 2 From the Configuring CCDM menu, choose Set External Interfaces to specify one or both of the following:
See "Directions for Troubleshooting the Sample HTTP Application".
You can use Lightweight Directory Access Protocol (LDAP) to retrieve external subscriber or provisioning information. LDAP is a nonproprietary, standards-based protocol. If you use the LDAP method, see your LDAP server administrator to obtain the information about the LDAP server that CCDM requires.
To retrieve external subscriber or provisioning information by using LDAP:
Step 2 Depending on the type of information you want to retrieve, do one or both of the following:
Step 3 To fill in the LDAP Access Parameters dialog box, see your LDAP server administrator to obtain the required information and refer to the online help for directions on how to fill in each of the LDAP fields that CCDM requires.
You can retrieve provisioning information only by using BPR, which stands for Cisco Broadband Provisioning Registrar. BPR automates provisioning and configuration tasks. CCDM supports BPR 2.0. For product information on BPR, refer to:
http://www.cisco.com/en/US/products/sw/netmgtsw/ps529/index.html
To retrieve provisioning information by using BPR:
Step 2 In the Provisioning Information section, click BPR. Follow the online help for directions on how to fill in each of the following BPR fields that CCDM requires:
You can retrieve provisioning information only by using CNR, which stands for Cisco Network Registrar. CNR is an application that provides scalable Domain Name System (DNS), Trivial File Transfer Protocol (TFTP), and Dynamic Host Configuration Protocol (DHCP) services.
For product information on CNR, refer to:
http://www.cisco.com/en/US/products/sw/netmgtsw/ps1982/index.html
If you use CNR, the following caveats apply to the setup:
To retrieve provisioning information by using CNR:
Step 2 In the Provisioning Information section, click CNR. Follow the online help for directions on how to fill in each of the following CNR fields that CCDM requires:
CCDM can retrieve subscriber data from its own local Sybase database after the data has been added in CCDM. After installation, Local Database is the default method for retrieving subscriber data.
To retrieve subscriber information from the local database:
Step 2 From the Configuring CCDM menu, choose Set External Interfaces.
Step 3 In the Subscriber Information section, click Local Database.
Step 4 (Optional) To update or replace the existing subscriber information, click Import Subscriber to open the Import Subscriber Data dialog box, as shown in Figure 11. In it, follow the online help for directions on how to import a subscriber.
CCDM can retrieve provisioning data from its own local Sybase database after the data has been added to it. After installation, Local Database is the default method for retrieving provisioning data. To store provisioning information in its local database, CCDM polls CMTSs using SNMP. CCDM provides two ways to do this:
|
Tip If you are using CCDM on the Windows OS, Cisco recommends that you use the CCDM GUI method. |
When you install CCDM, the default method for retrieving provisioning information is the local database. Because the Poller is part of the process for this method, it is on by default after installation. The default schedule for the Poller is to run at or about midnight and to repeat every 24 hours. You can change these settings according to your own needs.
To query CMTSs using the Poller, you specify two parameters:
The syntax to start the Poller on Linux or Solaris is:
The following example shows a polling session that starts 8 hours after you schedule it and repeats every 24 hours:
The following example shows how to stop the Java poller application on Linux or Solaris:
|
Note There is no impact to CCDM if you turn the Poller off. |
At each polling interval, the poller accesses the CCDM routers list file and performs SNMP queries to each CMTS using its SNMP read-only community string. The CCDM routers list file is in the following location:
/opt/CSCOccdm/jakarta-tomcat-4.0.3/webapps/ROOT/WEB-INF/classes/config/myrouters
In addition to the on-demand polling that you schedule, CCDM submits a polling request when it detects that a change has been made to the list of routers that CCDM manages. For example, CCDM submits a polling request when it detects that a new chassis has been added to a router.
|
Note The more frequent the polling interval, the more SNMP traffic that is generated to the CMTSs. This means that CPU utilization on the CMTS increases when polling is in progress. The impact on the CCDM server side is minimal. |
To retrieve provisioning information from the local database:
Step 2 From the Configuring CCDM menu, choose Set External Interfaces.
Step 3 In the Provisioning Information section, click Local Database.
To schedule when and how often the Poller populates the local database with provisioning information that it gathers from CMTSs, you can use the GUI or type a command.
To use the GUI, from the Configuring CCDM menu, choose Schedule CMTS Polling. The Schedule CMTS Polling dialog box appears, as shown in Figure 12. In it, follow the online help for directions on how to schedule the Poller.
To use a command, type the following command and specify the parameters in hours, as explained in the previous section:
CCDM supports two types of interfaces:
Northbound interfaces are discussed in "Retrieving Subscriber or Provisioning Data by Using an External Interface".
CCDM supports three southbound application program interfaces (APIs):
The following parameters are common to these APIs:
CCDM retrieves the values for these parameters from the Manage CMTSs dialog box.
To retrieve the maximum number of CPE devices that can be attached to a cable modem, use the API GetCMMaxCpeNumber. The input parameters, separated by a space, for this API are:
script-name GET_CM_MAX_CPE CMTS-IP UserName Password ReadOnlyCommunityString non-dotted-modem-mac-address
For example, the following API queries the maximum number of CPE devices that can be attached to the modem with the MAC address 000164ffc3c7 on CMTS 145.2.3.4:
The output of the script must be in the following format:
The following example shows the output for the maximum number of CPE devices for this modem:
To retrieve the current number of CPE devices that are be attached to a cable modem, use the API GetCMCurrCpeNumber. The input parameters, separated by a space, for this API are:
script-name GET_CURR_CPE_NUM CMTS-IP UserName Password ReadOnlyCommunityString on-dotted-modem-mac-address
For example, the following API queries the current number of CPE devices that are be attached to the modem with the MAC address 000164ffc3c7 on CMTS 145.2.3.4:
The output of the script must be in the following format:
OUT_DATA=CURR_CPE_NUM^integer^
The following example shows the output for the current number of CPE devices attached to this modem:
To get the state of modems on a fiber node, use the API GetFiberNodeTestResult. This API provides the following data for each upstream on each cable modem termination system:
The input parameters, separated by a space, are:
ScriptName GET_FIBER_NODE_TEST_RESULT CMTS-IP UserName Password ReadOnly-CommunityString non-dotted-modem-mac-address nodeName
For example, the following API queries the fiber node assigned to the MAC address 000164ffc3c7:
The output format of the script must be in the following format:
OUT_DATA=FIBER_NODE_TEST^^NUM_OF_ROWS^FiberNodeName^CMTS_IP^US_DESCRIPTOR^TOTAL_MODEM^ONLINE%^OFFLINE%^
The following example shows the output for the current number of each upstream on each cable modem termination system in the fiber node:
OUT_DATA=FIBER_NODE_TEST^^1^FiberNode_SanJose^172.22.85.7^Cable3/0-upstream5^
1^1(100%)^0(0%)^^
If an error occurs within the script, the script should return the output in the following format:
The following example shows output for an error:
OUT_DATA=ERROR^Unable to login device 172.3.4.5^
In the GUI, CCDM displays the error message to the user in a message box.
This section describes the parameters you set in two .INI files in CCDM:
This section describes parameters that you configure in the CONFIGS.INI file, which is located in the following platform-dependent directories:
One way to specify a cable modem in CCDM is to search on a subscriber's phone number. You can configure the phoneLength parameter in the CONFIGS.INI file. This parameter determines the number of integers for the phone number format in CCDM. The default setting is 10, as shown below:
You can increase this setting to handle international phone numbers.
|
Note You can also configure the phone number format in the CCDM GUI. From the Configuring CCDM menu, choose Set System Options. |
When CCDM displays detailed information on a cable modem, color-coding indicates the modem's status:
The following parameters set the thresholds that determine the boundaries for color-coding and must be configured in the CONFIGS.INI file:
upstreamXmitPowerFloor—This parameter determines the minimum upstream transmit power for a cable modem to show a functioning status. This measurement is expressed in decibels millivolt (dBmV). The default setting is 34, as shown below:
upstreamXmitPowerCeiling—This parameter determines the maximum upstream transmit power for a cable modem to show a functioning status. This measurement is expressed in decibels millivolt (dBmV). The default setting is 52, as shown below:
downstreamSnrFloor—This parameter determines the minimum signal-to-noise (SNR) for a cable modem to show a functioning status. SNR is a measure of transmission quality, which is expressed by the ratio of good data (signal) to bad data (noise) that is heard on a line. This ratio is measured in decibels (dB). A higher ratio indicates a better transmission quality. For example, 30 dB is better than 24 dB. The default setting is 30, as shown below:
downstreamReceivePowerFloor—This parameter determines the minimum downstream receive power for a cable modem to show a functioning status. This measurement is expressed in decibels millivolt (dBmV). The default setting is 15, as shown below:
downstreamReceivePowerFloor=15
downstreamReceivePowerCeiling—This parameter determines the maximum downstream receive power for a cable modem to show a functioning status. This measurement is expressed in decibels millivolt (dBmV). The default setting is 5, as shown below:
downstreamReceivePowerCeiling=5
The following parameters are for using a southbound interface:
SouthBoundExtIntf—This parameter specifies the script location of the southbound external interface that CCDM uses to access cable modem termination systems that are not from Cisco to gather information from the device by using a non-standard (i.e. non-DOCSIS SNMP) method. For more information, see "Southbound Script for Accessing CMTSs Not from Cisco".
SouthBoundExtIntfTimeout—This parameter determines when CCDM will time out when executing SouthBoundExtIntf. This measurement is expressed in milliseconds. The default setting is 5000, as shown below:
The following parameters are used when you test a modem's state:
ModemStateMaxLife—This parameter specifies the maximum length of time that CCDM keeps the modem state test, once the ModemStateMaxHash (see below) has reached its limit. This measurement is expressed in hours. The default setting is 4, which is also the minimum allowed value, as shown below:
ModemStateMaxHash—This parameter specifies the maximum number of modem state test entries CCDM keeps before purging old tests that have passed the length of time set in ModemStateMaxLife (see above). The default setting is 2000, which is also the minimum allowed value, as shown below:
The administrator specifies external interface parameters to tell CCDM where to access subscriber and provisioning information. Most of these parameters are in the Set External Interfaces dialog box. However, you must configure the following external interface parameters in the CONFIGS.INI file.
SubscriberExtIntfTimeout—This parameter determines the maximum wait time before CCDM times out during a query for subscriber information. This measurement is expressed in milliseconds (msecs). The default setting is 5000, which is equal to 5 seconds, as shown below:
ProvisionExtIntfTimeout—This parameter determines the maximum wait time before CCDM times out during a query for provisioning information. This measurement is expressed in milliseconds (msecs). The default setting is 5000, which is equal to 5 seconds, as shown below:
When it starts, the Poller accesses the POLLER.INI file, which is in the following location:
|
Note For a detailed description of the Poller, see "About the Poller". |
The poller accesses POLLER.INI to gather the following configurable parameters:
maximumThread—This parameter determines the maximum number of different execution threads that can run simultaneously in the Poller. The valid range is 1 to 50. The default setting is 20, as shown below:
maximumDBConnection—This parameter determines the maximum number of CCDM Sybase database connections the Poller uses to perform the polling operation. The valid range is 1 to 7. The default setting is 7, as shown below:
SnmpTimeout—This parameter determines the number of seconds before the attempt to create the SNMP connection will reach a timeout or fail. The valid range is 1 to 3. The default setting is 2, as shown below:
SnmpRetry—This parameter determines the number of times you want to try to create the SNMP connection. The valid range is 1 to 5. The default setting is 3, as shown below:
Debug—This parameter determines if debug messages are sent to the log file, which is in the following location:
Valid values are true and false. The default setting is false, as shown below:
maximumAge—This parameter tells the poller which outdated records to purge, based on the number of polling intervals that have occurred during which those records have not been updated. This measurement is expressed in polling intervals. A valid range is 1 to 7. The default setting is 2, as shown below:
PollerServerPort—This parameter sets the HTTP server port number where Poll Manager listens to polling requests. The default setting is 8040:
|
Note If a parameter in POLLER.INI is set out of the valid range, CCDM resets the parameter to its default value. |
CCDM provides troubleshooting tips to help you diagnose and solve cable modem failure scenarios. These troubleshooting tips are for common cable modem failure scenarios. You can customize troubleshooting tips by adding causes and tips for other failure scenarios.
CCDM provides troubleshooting tips to help you diagnose and solve the following common cable modem failure scenarios:
If a cable modem is not online, you see troubleshooting tips in two places:
Table 1 shows the troubleshooting tips for the TFTP server problem.
Table 1 Troubleshooting Tips for TFTP Server Problem
The TROUBLESHOOT_TIPS.INI file allows you to add troubleshooting tips for other cable modem failure scenarios. The blank TROUBLESHOOT_TIPS.INI file is shown below:
The file contains a line of causes and tips for each cable modem failure scenario.
When you add a failure scenario and customize the causes and tips in the TROUBLESHOOT_TIPS.INI file, the following format restrictions apply:
|
Note One cause or one solution can have multiple parts, as shown in the first row of Table 1. In the first row, the cause has three conditions and the solution has three steps, but CCDM still considers it one cause and one solution. |
To modify the TROUBLESHOOT_TIPS.INI file:
Step 2 Add a line for SCENARIO_CAUSES=, where SCENARIO represents the name of the failure scenario you are adding.
Step 3 For the cable modem failure scenario that you are adding, type the information for its causes according to one of the following formats:
^Cause 1a,Cause 1b,Cause 1c^—Use this format when a cause has more than one condition. (See Row 1 of Table 2)
^Cause 2^—Use this format when a cause has only one condition. (See Row 2 of Table 2)
Step 4 Add a line for SCENARIO_TIPS=, where SCENARIO represents the name of the failure scenario you are adding.
Step 5 For the cable modem failure scenario that you are customizing, type the information for its respective tips according to one of the following formats:
^Tip 1a,Tip 1b,Tip 1c^—Use this format when a tip has more than one step. (See Row 1 of Table 2)
^Tip 2^—Use this format when a tip has only one step. (See Row 2 of Table 2
Step 6 After you have made all of your modifications, save the TROUBLESHOOT_TIPS.INI file.
Step 7 Restart the CCDM server for the new settings to take effect.
Table 2 Format of Troubleshooting Tips in CCDM GUI
| Potential Causes | Solution |
|---|---|
The following example shows the format for a new cable modem failure scenario in the TROUBLESHOOT_TIPS.INI file.
NEW_SCENARIO_CAUSES=^1a) Add cause text.,1b) Add cause text.,1c) Add cause text.^^2) Add cause text.^
NEW_SCENARIO_CAUSES=^1a) 1. Add tip text.,1b) 2. Add tip text.,1c) 3. Add tip text.^^2) Add tip text.^
After CCDM is configured according to your needs and the subscriber and provisioning data is accessible, you can review a modem's status. This information is in the Real-Time Modem Status Report, as shown in Figure 13.
CCDM provides two ways to get a cable modem status report:
To get a report using the external script, you specify five parameters:
Separate each input parameter with a space. The format for this script is:
/opt/CSCOccdm/bin/getStatusReport REPORT_TYPE USER_NAME USER_PASSWORD MODEM_MAC DESTINATION
For example, the following script retrieves a Cable Modem Real-Time Status Report for the cable modem with the MAC address 001cab2345fe:
The output of the report is in Extensible Markup Language (XML) format. For details on and a sample of the format, see "Northbound XML Schema and Sample Files".
To view a status report for a cable modem by using the GUI:
Step 2 In the Specify a Cable Modem to Query dialog box, shown in Figure 14, follow the online help for directions on how to fill in each field so that you can query a cable modem for its status.
This section provides directions to troubleshoot error messages for the following CCDM components:
You can use the Poller, a separate Java application, to store provisioning information in CCDM's local Sybase database. This database poller queries the CMTSs by using SNMP. If the Debug parameter in POLLER.INI is set to true, the Poller sends information to the Poller.log file in the following location:
|
Note See "Parameters in the POLLER.INI File" for an explanation of each parameter in POLLER.INI. |
The following output from Poller.log indicates that no router was found:
No router was found in the routers list file because of one of the following conditions:
To add routers in CCDM, see "Adding Router Information".
The following output from Poller.log indicates that the login to the database failed:
The database login failure occurs because the database ran out of connections. That is, it tried to use more connections than it can support.
If the database ran out of connections, restart CCDM to clear all existing database connections and start the database.
|
Note For directions on restarting CCDM, see "Installing and Starting CCDM". |
The following output from Poller.log indicates that an SNMP timeout has occurred:
The SNMP timeout occurs when the network connection to the router, or the router itself, is so busy that it cannot satisfy the request within the specified time.
If the SNMP timeout occurs too frequently, change the settings in the POLLER.INI file:
Step 2 Increase one or both of the following settings:
Step 3 To activate the new settings, restart the CCDM server.
|
Tip Check for incorrect SNMP community strings because an invalid community string for read/write will also result in an SNMP timeout. |
Step 2 Insert the Cisco Cable Diagnostic Manager CD-ROM into the CD-ROM drive.
Step 3 To mount the CD, enter:
Step 4 To change to the CCDM Linux directory, enter:
Step 5 To uninstall CCDM, enter:
Step 2 Insert the Cisco Cable Diagnostic Manager CD-ROM into the CD-ROM drive.
Step 3 To change to the CCDM Solaris directory and uninstall CCDM, enter:
cd /cdrom/cdrom0/solaris
./uninstall
To uninstall CCDM by using the CCDM CD-ROM:
Step 2 From Windows Explorer, double-click SETUP in CDROM_DRIVE\WIN\DISK1.
Step 3 To uninstall CCDM, click Remove.
To uninstall CCDM by using Windows menus:
Step 2 Select Cisco Cable Diagnostic Manager.
Step 3 Click Remove.
This section contains the README files for the following northbound and southbound application program interfaces:
The sections that describe scripts and code provide the following information:
The XML section provides the XML schema and a sample file.
You can use a sample script written for various databases to retrieve subscriber or provisioning information from an external source. These scripts, that you can modify according to your needs, are in the README file in the following locations:
This section provides a printed copy of that README file, formatted for this user guide.
This file describes how to use scripts written against a Sybase database. The sybase directory contains sample scripts that you can modify to meet your needs. These scripts demonstrate how to:
After trying the sample scripts, you can tailor them for your database or any other external data source.
The following list describes the purpose of each script or file:
1. Modify insert_cmts.sql to insert a list of CMTSs and cable modems into the database.
2. Execute insert_cmts from the command line:
./insert_cmts
3. Modify subscriberinfo.txt to import subscriber information into CCDM. For field descriptions, refer to online help for the Import Subscriber Data dialog box.
4. Start CCDM. Log in as an Admin user.
5. Click Import Subscriber Data, enter the Subscriber Data File Location, and click Start.
6. Click Set External Interfaces.
7. Under Subscriber Information, select the Script radio button and enter the location of the get_subscriber filename (for example, /my_dir/get_subscriber) in the Script Location text box.
8. Under Provisioning Information, select the Script radio button and enter the location and the get_provision filename (for example, /my_dir/get_provision) in the Script Location text box.
./get_provision GET_PROVISION MAC 000216d5a0cf
OUT_DATA=PROVISION^172.22.85.10^172.22.127.26^
./get_provision GET_PROVISION MAC_LIST 000216d5a0cf^000164ffeb95
OUT_DATA=PROVISION^000216d5a0cf=172.22.85.10,172.22.127.26^000216d5eb95=172.22.85.10,172.22.127.26
./get_provision GET_MAC IP 172.22.127.26
./get_subscriber GET_SUBSCRIBER MAC 000216d5a0cf
OUT_DATA=SUBSCRIBER^AccId=ID000006^Name=Name000006^Phone=6172300006^Address=175 West Tasman^ClassOfService=Policy000006^FiberNode=User A000006^
./get_subscriber GET_MAC PHONE 5106663152
OUT_DATA=MAC^000164ffeb95^000164ffc3c7^
./get_subscriber GET_ADDRESS MAC 000164ffc3c7^000164ffeb95^
OUT_DATA=ADDRESS^000164ffc3c7=170 West Tasman Drive,95134^000164ffeb95=170 West Tasman Drive,95134^
echo OUT_DATA=PROVISION^^172.22.85.10^^172.22.127.26^^
The following sample code is extracted from get_subscriber script:
"GET_MAC") function=${argv[$i]};;
#retrieving MAC based on Customer phone number
if [ "$function" = "GET_MAC" ] ; then
str="SELECT MACAddress FROM SUBSCRIBERINFO where CusPhone='$in_param';";
echo $str >> "$tmpDir/script.$filenameExt"
str="OUTPUT TO $tmpDir/test.$filenameExt FORMAT ASCII;"
echo $str >> "$tmpDir/script.$filenameExt"
tmpi=\Qdbisqlc -q -c $dbAccess read $tmpDir/script.$filenameExt\Q
rm $tmpDir/script.$filenameExt
MAC=\Q$commLib/cat $tmpDir/test.$filenameExt | $commLib/sed s/\'//g\Q
echo $MAC > $tmpDir/test.$filenameExt
MAC=\Q$commLib/cat $tmpDir/test.$filenameExt | $commLib/sed 's/ /^/g'\Q
if [ $tmp = "OUT_DATA=MAC^^" ] ; then
echo "OUT_DATA=ERROR^No data found for $in_param^";
You can use an application that is running on an HTTP server to retrieve subscriber or provisioning information from an external source.
A sample application that you can modify according to your needs is in the README file in the following locations:
This section provides a printed copy of that README file, formatted for this user guide.
This file describes how to use Data Manager, a sample HTTP application. The http directory contains this sample application that you can modify to meet your needs. Data Manager demonstrates how to:
This section lists the modules and files used in Data Manager, the sample HTTP application. For a description, refer to a specific module or file. To modify Data Manager to suit your needs, refer to the next section, "Modifiable Components in the Data Manager Application."
If create_tbls.sql is changed, the code for these functions must be changed accordingly.
If the provisioning and subscriber data tables reside in the same database, these two files must have identical information. In Data Manager, the provisioning and subscriber data is in two separate databases.
For both files, the following settings must be changed accordingly:
For more information, contact your local DBA.
start_dm—Starts the Data Manager HTTP application.
The current variable settings in start_dm are:
(Send debug messages to a log file.)
(Change to the port of your choice.)
logDir= /opt/CSCOccdm/jakarta-tomcat-4.0.3/logs
(Specify the location where the log file should be created and changes should be written.)
stop_dm—Stops the Data Manager HTTP application.
The following variable settings are in stop_dm:
(IP address where the HTTP application is running.)
(Port in which the HTTP application is running. This should be the same port specified in the start_dm script.)
For these three scripts (Makefile, start_dm, and stop_dm), the following properties need to be updated according to the system environment:
For more information, check with your DBA.
1. Build class files and copy files to destination.
a. Start CCDM. Log in as an Admin user.
b. Click Set External Interfaces.
c. Under Subscriber Information, select the HTTP radio button and enter the URL for the application in the URL Location text box:
http:// your_machine_name:port_num/DataManager
5. Under Provision Information, select the HTTP radio button and enter the URL for the application in the URL Location text box:
http:// your_machine_name:port_num/DataManager
Make sure there is connectivity between the machine and the Oracle database. A quick way to test this is to invoke Oracle's sqlplus application. For example, assume that the following settings are in Db-Vital.properties:
If there is no response or an error occurs, check the tnsnames.ora setting with your local DBA.
Make sure that JAVA_HOME in the Makefile points to the correct JAVA compiler.
The sample HTTP application was written to use the Oracle OCI protocol for communicating with the database. Oracle OCI requires machine-dependent libraries, so make sure that the path to the libraries is set correctly in Makefile.
This error occurs when port_num is changed in start_dm and stop_dm. To correct it, restart the program /opt/CSCOccdm/bin/start_dm
It is possible that some of the Oracle environment did not get set up correctly. To check this, review oracle.csh, update it as required, and source it. Then, run start_dm again.
1. Setup Http Connection to receive request from CCDM (HttpManager.java)
HttpRequest = new HttpRequest()
2. Fetch message's header (HttpRequest.java):
StringBuffer sb = new StringBuffer();
InputStream is = sock.getInputStream();
DataInputStream fromBrowser = new DataInputStream(is);
sb.append(msg + nl); // put back the '\n\r' for newline
3. Fetch message's body (HttpRequest.java):
DataInputStream fromBrowser = sock.getInputStream();
StringBuffer sb = new StringBuffer();
// return int range 0-255, -1: end of stream
// however, char is 16 bits for unicode 2 bytes
// now use 2 bytes to hold just one byte data.
4. Parse message (HttpObj.java):
//parse and save message into Hashtable
String req_command = decodeString(command);
//System.out.println ("req_command=" + req_command);
// Parse the data from the servlet
StringTokenizer rdata = new StringTokenizer(req_command, "&");
//System.out.println ("data=" + data + ", rdata=" + rdata);
while (rdata.hasMoreTokens()) {
String cmd = rdata.nextToken();
String key = cmd.substring(0, index);
String val = cmd.substring(index+1);
5. Process message (HttpManager.java & DataManager.java):
//if POST message then process the message:
if (req.getReqType().equals ("POST")) {
status = dm_.processCommand(req);
//examine the request type and process the message accordingly:
Hashtable hParams = req.getParams();
String task = (String)hParams.get("REQUEST");
if (task.equals(GET_PROV_INFO)) {
String sType = (String)hParams.get("SEARCH_TYPE");
String sTmp = (String)hParams.get("IN_PARAM");
String sMac = sTmp.toLowerCase();
Logger.debug("In Mac is " + sMac);
sStr = DbQuery.getProvInfo(sMac);
Logger.debug("Prov Info is " + sStr);
// retrieve information from the database (DbQuery.java):
public static String getProvInfo(String Mac) {
long start = (new java.util.Date()).getTime();
start = (new java.util.Date()).getTime();
stmt = vital_db_conn.createStatement();
query = "select subscriberid, ipaddress,giaddr from device where deviceid = '" + Mac + "'";
ResultSet rs = stmt.executeQuery(query);
subscriberId = rs.getString(1);
long end = (new java.util.Date()).getTime();
Logger.debug("total msec to execute getProvInfo: " + (end - start));
return ("OUT_DATA=ERROR^" + Mac + " does not exist in the Provisioning Database.^");
String sStr = "OUT_DATA=PROVISION^" + cmtsIp + "^" + modemIp + "^";
String sError = "OUT_DATA=ERROR^" + se.getMessage() + "^";
6. Build a Post Http Response to return data to CCDM (HttpResponse.java):
Logger.error("DataManager.HttpResponse:sendHeader: error: " + e);
e.printStackTrace(DataManager.getLogPW());
StringBuffer sb = new StringBuffer();
sb.append ("HTTP/1.0 200 OK" + nl);
sb.append ("Content-type: text/html" + nl);
byte[] b = (sb.toString()).getBytes();
Logger.error ("DataManager.HttpResponse:sendHeader: error write: " + e);
e.printStackTrace(DataManager.getLogPW());
7. Send result data off to CCDM
CCDM is a diagnostic tool that is deployed in an environment where a trouble-ticket system exists. Therefore, it is helpful to transfer the diagnostic information collected by CCDM to a trouble-ticket system. This functionality is provided by using XML to encode the diagnostic information.
When you view a Real-Time Status Report for a cable modem, you can view a detailed version of the report. From the detailed version, you can click Save Report. CCDM saves the report in XML format.
The XML schema file in this section defines the content used in the real-time status report:
<?xml version="1.0" encoding="UTF-8"?>
<input type="macAddress">00:02:16:d5:a4:27</input>
<fqdn>Horsham_ubr_1.cisco.com</fqdn>
<ipaddress>10.87.117.2</ipaddress>
<macaddress>00:02:16:d5:a4:27</macaddress>
<ipaddress>10.1.4.27</ipaddress>
<test name="cmts-snmp-connectivity" status="successful">
<status-text>test completed successfully</status-text>
<start-time>09/04/02 12:00:36 EDT</start-time>
<finish-time>09/04/02 12:00:39 EDT</finish-time>
<name>DownStreamChannel</name>
<value>Cable3/0downstream</value>
<value>Cable3/0upstream1</value>
<name>Upstream Receive Power</name>
<name>Modem Status (DOCSIS)</name>
<name>Maximum Number of Connected CPE's</name>
<name>Current Number of Connected CPE's</name>
<name>Maximum Downstream</name>
<value>192.168.2.118, 192.168.2.119</value>
The sample XML file in this section shows a real-time status report that conforms to the schema in the previous section:
<?xml version="1.0" encoding="UTF-8" ?>
<ipaddress>172.22.85.7</ipaddress>
<input type="MAC">000164ffeb95</input>
<macaddress>000164ffeb95</macaddress>
- <test name="neighborhood-lookup" status="successful">
<status-text>test completed successfully</status-text>
<start-time>Jan 15, 2003 12:14 PM America/Los_Angeles</start-time>
<end-time>Jan 15, 2003 12:14 PM America/Los_Angeles</end-time>
<name>Cable3/0-upstream5 total modems count(percentage)</name>
<name>Cable3/0-upstream5 online modems count(percentage)</name>
<name>Cable3/0-upstream5 offline modems count(percentage)</name>
<name>Cable3/0-upstream5 online count(percentage)</name>
<name>Cable3/0-downstream total modems count(percentage)</name>
<name>Cable3/0-downstream online modems count(percentage)</name>
<name>Cable3/0-downstream offline modems count(percentage)</name>
<name>Cable3/0-downstream online count(percentage)</name>
<name>Fiber Node total modems count(percentage)</name>
<name>Fiber Node online modems count(percentage)</name>
<name>Fiber Node offline modems count(percentage)</name>
<name>Fiber Node online count(percentage)</name>
- <test name="cmts-info" status="successful">
<status-text>test completed successfully</status-text>
<start-time>Jan 15, 2003 12:14 PM America/Los_Angeles</start-time>
<end-time>Jan 15, 2003 12:14 PM America/Los_Angeles</end-time>
- <test name="cmts-icmp-ping" status="successful">
<status-text>test completed successfully</status-text>
<start-time>Jan 15, 2003 12:14 PM America/Los_Angeles</start-time>
<end-time>Jan 15, 2003 12:14 PM America/Los_Angeles</end-time>
- <test name="cmts-snmp-connectivity" status="successful">
<status-text>test completed successfully</status-text>
<start-time>Jan 15, 2003 12:14 PM America/Los_Angeles</start-time>
<end-time>Jan 15, 2003 12:14 PM America/Los_Angeles</end-time>
<name>Downstream Channel</name>
<value>Cable3/0-downstream</value>
<value>Cable3/0-upstream5</value>
<name>Upstream Receive Power</name>
<name>Maximum Number Of Connected CPEs</name>
<name>Current Number of Connected CPEs</name>
<name>Guaranteed Upstream</name>
<name>Maximum Downstream</name>
- <test name="cm-icmp-ping" status="successful.">
<status-text>test completed successfully</status-text>
<start-time>Jan 15, 2003 12:14 PM America/Los_Angeles</start-time>
<end-time>Jan 15, 2003 12:14 PM America/Los_Angeles</end-time>
- <test name="cm-snmp-connectivity" status="successful">
<status-text>test completed successfully</status-text>
<start-time>Jan 15, 2003 12:14 PM America/Los_Angeles</start-time>
<end-time>Jan 15, 2003 12:14 PM America/Los_Angeles</end-time>
<value>Cisco Internetwork Operating System Software IOS (tm) 925 Software (UBR925-K8SV4Y5-M), Version 12.2(2)XA, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) TAC:Home:SW:IOS:Specials for info Copyright (c) 1986-2001 by cisco Systems, Inc. Compiled Wed 27-Jun-01</value>
<value>16 days 1 hours</value>
<name>Downstream Channel Power</name>
<threshold-floor>-15</threshold-floor>
<threshold-ceiling>5</threshold-ceiling>
<name>Upstream Transmit Power</name>
<threshold-floor>34</threshold-floor>
<threshold-ceiling>52</threshold-ceiling>
<name>Downstream Signal to Noise Ratio</name>
- <test name="subscriber-db" status="successful">
<status-text>test completed successfully</status-text>
<start-time>Jan 15, 2003 12:14 PM America/Los_Angeles</start-time>
<end-time>Jan 15, 2003 12:14 PM America/Los_Angeles</end-time>
<value>Multi-user Test</value>
You can use a script to access CMTSs that are not from Cisco and gather network information that is needed by CCDM.
A sample script that you can modify according to your needs is in the README file in the following locations:
This section provides a printed copy of that README file, formatted for this user guide.
This file describes how to use a script to interface with CCDM to access CMTSs that are not from Cisco. The script gathers network information from those devices that is needed by CCDM. The sample directory contains a sample script and code that you can modify to meet your needs. The script and code demonstrate how to:
The following requirements apply to the southbound script for accessing CMTSs that are not from Cisco:
The following list describes the purpose of each script or file:
1. Install Java 2 Platform, Standard Edition (J2SE) v1.3.1. See Sample Script/Code Requirements section on URL location to download, http://java.sun.com/j2se/1.3/download.html.
2. Copy samples/SBExtIntfSample/* to a new subdirectory SBExtIntfSample.
Example: /usr/test/SBExtIntfSample
Throughout these directions, /usr/test/SBExtIntfSample will be used as the root directory that holds the sample script and code.
3. Change directory to the newly created sample directory.
Example: cd /usr/test/SBExtIntfSample
4. Modify script-root-dir and j2se-installed-dir in Makefile and SampleScript.sh to reflect the:
5. Modify SampleCode.java to include the necessary logic to query the CMTS that is not from Cisco, based on the request passed in from CCDM. For the south-bound interface APIs that need to be supported, see "Using Southbound Application Program Interfaces in CCDM".
7. Modify SouthBoundExtIntf in CONFIGS.INI to point to the Sample script:
Example: SouthBoundExtIntf=/usr/test/SBExtIntfSample/SampleScript.sh
These sections explain how to obtain documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at this URL:
http://www.cisco.com/public/countries_languages.shtml
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.
You can order Cisco documentation in these ways:
http://www.cisco.com/cgi-bin/order/order_root.pl
http://www.cisco.com/go/subscription
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online 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 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 with these tasks:
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
You can use the Cisco TAC Web Site 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 this URL:
All customers, partners, and resellers who have a valid Cisco service 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 this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. 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 automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this 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). When you call the center, please have available your service agreement number and your product serial number.
Posted: Sat Apr 12 03:34:27 PDT 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
