cc/td/doc/product/cable/cbl_mgt
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Release Notes for Cisco Cable Manager Release 2.2

Contents

Introduction

Installation and Uninstallation Related Changes

CCM 1.0 to CCM 2.2

Upgrading CCM 2.0 to CCM 2.2

Upgrading CCM 2.1 to CCM 2.2

Ignoring EM Upgrade Errors

About Configuration Management

Loading the Expect and TCL utilities if you don't find them installed on your system

About Renaming Objects from Map Viewer

About Bundled Software

Installing Netscape Navigator

About Starting Cisco Broadband Troubleshooter 2.0 from CCM 2.2

Registering CBT 2.0 with CCM 2.2

Unregistering CBT 2.0

About Starting CiscoView Web 5.2 from CCM 2.2

Registering CVW 5.2 with CCM 2.2

Unregistering CVW 5.2 with CCM 2.2

About General Polling Behavior

Rehoming Cable Modems

Discovering Cards After a Card Is Inserted or Removed

About Performance Management Data Modeling

Assessing Your Information Needs

Resizing Your Database

About Performance Reports

Dynamically Starting Polling for Newly Added Cable Modems

Caveats

CEMF Caveats

Installation Caveats

Deployment Caveats

Workaround

Workaround

Performance Management [Polling and Reports] Caveats

Fault Management Caveats

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Release Notes for Cisco Cable Manager Release 2.2

Note Cisco Cable Manager Release 2.2 requires Cisco Element Management Framework (CEMF) 3.1 patch 5 and patch 5.2. The CEMF 3.1 patches are available at /auto/emsbu/CEMF/3.1/patches/CEMF3.1_Patchnn.
For more information, go to http://www.cisco.com/warp/public/707/cisco-malformed-snmp-msgs-non-ios-pub.shtml.

Contents

• Introduction

• Installation and Uninstallation Related Changes

• About Configuration Management

• About Renaming Objects from Map Viewer

• About Bundled Software

• About Starting Cisco Broadband Troubleshooter 2.0 from CCM 2.2

• About Starting CiscoView Web 5.2 from CCM 2.2

• About General Polling Behavior

• About Performance Management Data Modeling

• About Performance Reports

• Caveats

• CEMF Caveats

• Installation Caveats

• Deployment Caveats

• Performance Management [Polling and Reports] Caveats

• Fault Management Caveats

• Obtaining Documentation

• Obtaining Technical Assistance

Introduction

These release notes describe important information and caveats for the Cisco Cable Manager Release 2.2. Information in this document supplements information in the Cisco Cable Manager Users' Guide Release 2.0.

•Regular user groups have been added.

Cisco Cable Manager can deploy the uBR 10012 chassis with single or dual performance routing engines (PRE1).

The following informational items will be added to the Cisco Cable Manager Users' Guide with the next release of the document.

Installation and Uninstallation Related Changes

Note The master installation and uninstallation scripts have been renamed install_CCM and uninstall_CCM respectively.

The installation and uninstallation procedures remain the same.

To install CCM as root, enter:

Step 1 cd dir where CCM package was extracted.

Step 2 ./install_CCM

To uninstall CCM, enter:

Step 1 cd dir where CCM package was extracted.

Step 2 ./uninstall_CCM

Note When installing CCM, you must configure the raw partition in order to utilize the hard-disk capacity effectively with a large-scale deployment.

CCM 1.0 to CCM 2.2

Note Remove CCM 1.0, including the database, before installing CCM 2.2.

To uninstall CCM 1.0, run the uninstall script. Enter:

Step 1 cd dir where CCM package was extracted.

Step 2 Enter ./uninstall_CCM 1.0

To install CEMF 3.1, run the install script. As root, enter:

Step 1 cd dir where CEMF 3.1 was extracted

Step 2 Enter ./cemfinstall

Step 3 Follow the script procedure.

To install CEMF 3.1 patch 5 and patch 5.2, run the install script. As root, enter:

Step 1 cd dir where each CEMF 3.1 patch was extracted.

Step 2 Enter ./cemfinstall

Step 3 Follow the script procedure.

To install CCM 2.2, run the install script:

Step 1 cd dir where CCM package was extracted.

Step 2 Enter ./install_CCM

Upgrading CCM 2.0 to CCM 2.2

Note Do not use the archived performance polling data from CCM2.0 to regenerate the Cable Modem Usage Report in CCM2.2 since the related polling group internal data representation has been changed to improve the Usage Report performance.

The install_CCM script has been modified, so that if CCM 2.0 is already installed on this host, an Element Manager (EM) upgrade is performed automatically. The current database created with CCM 2.0 is read by CCM 2.2, and CCM 2.2-specific attributes are added, so that the database can be used by CCM 2.2.

Caution Do NOT use the CEMF restore procedure to restore the CCM 2.0 database while CCM 2.2 is installed.

Task 1: (Optional) Manually backing up the CCM 2.0 database before installing CCM 2.2.

If there is any possibility that you may want to uninstall CCM 2.2 and re-install CCM 2.0 in its place, you must manually backup the CCM 2.0 database before installing CCM 2.2.

Task 2: Installing CEMF 3.1 patch 5 and patch 5.2.

Run the install script. As root, enter:

Step 1 cd dir where CEMF 3.1 patches were extracted

Step 2 Enter ./cemfinstall

Step 3 Follow the script procedure.

Task 3: Deleting the current database - uninstall CCM 2.0 and install CCM 2.2.

Run the uninstall script. Enter:

Step 1 cd dir where CCM package was extracted.

Step 2 Enter ./uninstall_CCM

To install CCM 2.2, run the install script. Enter:

Step 1 cd dir where CCM package was extracted.

Step 2 Enter ./install_CCM

Task 4: Reusing the current database - install CCM 2.2:

To install CCM 2.2, run the install script

Step 1 cd dir where CCM package was extracted.

Step 2 Enter ./install_CCM

Upgrading CCM 2.1 to CCM 2.2

The install_CCM script has been modified, so that if CCM 2.1 is already installed on this host, an Element Manager (EM) upgrade is performed automatically. The current database created with CCM 2.1 is read by CCM 2.2, and CCM 2.2-specific attributes are added, so that the database can be used by CCM 2.2.

Caution Do NOT use the CEMF restore procedure to restore the CCM 2.1 database while CCM 2.2 is installed.

Task 1: (Optional) Manually backing up the CCM 2.1 database before installing CCM 2.2.

If there is any possibility that you may want to uninstall CCM 2.2 and re-install CCM 2.1 in its place, you must manually backup the CCM 2.1 database before installing CCM 2.2.

Task 2: Installing CEMF 3.1 patch 5 and patch 5.2.

Run the install script. As root, enter:

Step 1 cd dir where CEMF 3.1 patches were extracted

Step 2 Enter ./cemfinstall

Step 3 Follow the script procedure.

Task 3: Deleting the current database - uninstall CCM 2.1 and install CCM 2.2.

Run the uninstall script. Enter:

Step 1 cd dir where CCM package was extracted.

Step 2 Enter ./uninstall_CCM

To install CCM 2.2, run the install script. Enter:

Step 1 cd dir where CCM package was extracted.

Step 2 Enter ./install_CCM

Task 4: Reusing the current database - install CCM 2.2:

To install CCM 2.2, run the install script.

Step 1 cd dir where CCM package was extracted.

Step 2 Enter ./install_CCM

Note See also DDTS CSCdx03905, CCM upgrade should save and restore user config files, in the Installation Caveats section.

Answering EM Upgrade Questions

During the upgrade, to reuse the CCM 2.0 database, enter y to the following questions:

The package cblMgrm is already installed on the system. Do you wish to upgrade this package? [y][y.n,?]

Enter y.

Are you sure you wish to upgrade the package cblMgrm? [y][y.n,?]

Enter y.

Are you sure you wish to install the package cblMgrm? [y][y.n,?]

Enter y.

Ignoring EM Upgrade Errors

Two error messages appear as a result of the EM upgrade. These do not affect the CCM 2.2 installation. Ignore them. Sample messages are:

objectspec - Running "/opt/cemf/config/selfManagement/actions/p.objectspec" ObjectFileParser: create/delete failure. Object Name = 'ldapConfigObj' (Path error) ERROR: Action returned an error.

viewspec - Running "/opt/cemf/config/selfManagement/actions/p.viewspec" ObjectFileParser: create/delete failure. ERROR: Action returned an error.

About Configuration Management

The device configuration and diagnostic requests will not function if you don't have the Expect and TCL utilities installed on your system. A cblCtrl core dump appears if these utilities are missing.

Check the ccm2.2.tar.Z file for the following Expect/TCL libraries:

expect.5.31.5_PkgOnSolaris2.6.tar.Z
tcl.8.3.0_PkgOnSolaris2.6.tar.Z

Loading the Expect and TCL utilities if you don't find them installed on your system

To load the Expect package, enter the following commands:

Step 1 uncompress -d expect.5.31.5_PkgOnSolaris2.6.tar.Z

Step 2 tar -xvf expect.5.31.5_PkgOnSolaris2.6.tar

Step 3 pkgadd -d directory directory containing the Expect program

To load the TCL package, enter the following commands:

Step 1 uncompress -d tcl.8.3.0_PkgOnSolaris2.6.tar.Z

Step 2 tar -xvf tcl.8.3.0_PkgOnSolaris2.6.tar

Step 3 pkgadd -d directory directory containing the TCL program

About Renaming Objects from Map Viewer

Caution Do not rename any objects in Map Viewer; do not use the menu option View Manipulation > Rename Objects.

CEMF provides the menu option View Manipulation > Rename Objects to rename objects (icons) shown in the Map Viewer. Some internal caches in CCM are based on the ObjectName, such as the cable modem MAC Address, the group name under each cell-name, or an unprovisioned object in the Tree View (Map Viewer). Renaming an object in Map Viewer can corrupt these caches and cause Cable Manager not to function properly

About Bundled Software

The following information describes software that is bundled with Cisco Cable Manager 2.2.

Netscape Navigator Bundled as Browser

Netscape Navigator is bundled with Cable Manager as of the 2.2 release. The Cisco Cable Manager (CCM) installation procedure will automatically install the browser, which starts CiscoView Web and Cisco Broadband Troubleshooter 2.0 if those packages have been purchased separately and if they have been registered with CCM (see Registering CBT 2.0 with CCM 2.2 and Registering CVW 5.2 with CCM 2.2). The browser will be installed automatically on both the CCM server and client machines.

Note The CCM uninstallation script will remove the browser from both the server and client machines automatically.

Installing Netscape Navigator

When installing Netscape Navigator, you are asked the following questions.

Note Make sure you choose the default answer for both the questions; DO NOT change the directory name for the installation.

Query 1

-------

Please specify the directory path under which the software will be installed. The default directory is auto-generated directory name, but you may install anywhere you wish (if you have permission to do so).

Location for Navigator software [auto-generated directory name]:

Query 2

-------

Existing 'auto-generated directory name' directory found.

The existing contents may be modified or replaced if you install in this directory. If you choose not to install in 'auto-generated directory name', you will be prompted for a different directory.

Do you wish to install in 'auto-generated directory name'? (y/n)[y]

CiscoView Classic

CiscoView Classic is bundled with CCM 2.2 and has been updated to include support for the Cisco uBR925, the uBR10012, the CVA122E, and the uBR7100 series.

Cisco Cable Troubleshooter 1.3

Cisco Cable Troubleshooter 1.3 is bundled with CCM 2.2 and has been updated to include support for the uBR7100 series and the uBR10012.

About Starting Cisco Broadband Troubleshooter 2.0 from CCM 2.2

A new set of scripts, install_cbt and uninstall_cbt, are bundled with Cisco Cable Manager (CCM) 2.2. Run these scripts manually. The scripts are not run automatically by the CCM master installation/uninstallation scripts.

Note These scripts DO NOT install or uninstall CBT 2.0. The scripts register already installed information with CCM 2.2

Registering CBT 2.0 with CCM 2.2

The install_cbt script registers the CBT server name and port number with CCM 2.2. After running install_cbt, only CBT 2.0 starts when you start it from the CCM menus.

To register CBT 2.0 with CCM 2.2 as root, enter:

Step 1 cd dir where CCM package was extracted.

Step 2 Enter ./install_cbt

You must register CBT 2.0 on the CCM server as well as on the client machine. Install_cbt automatically detects a CBT 2.0 installation on the CCM server machine.

Unregistering CBT 2.0

The uninstall_cbt script removes the CBT server and port number entries. After running uninstall_cbt, only CCT starts from the CCM menus.

Note You must purchase CBT 2.0 separately. You can install CBT 2.0 on the same machine as the CEMF/CCM server machine or any other machine that is accessible by the CCM server or client machine. The machine with the CBT 2.0 installation must have IP and SNMP connectivity to the managed devices.

About Starting CiscoView Web 5.2 from CCM 2.2

Note CCM 2.2 only supports CiscoView Web Release 5.2 (CVW 5.2).

Install_ciscoview_web and uninstall_ciscoview_web are bundled with CCM 2.2. Run these scripts manually.

Note These scripts DO NOT install or uninstall CVW 5.2. They register already installed information with CCM 2.2

Registering CVW 5.2 with CCM 2.2

The install_ciscoview_web script registers the CiscoView Web (CVW 5.2) server name and port number with CCM 2.2.

When registering CVW 5.2 with CCM 2.2, the JAVA plug-in and the identity database needed for starting CVW 5.2 are installed automatically. These components are needed to start CVW 5.2. [To start CiscoView 5.3 or other releases, different sets of components may be needed. It is up to the user to install them.]

After running install_ciscoview_web, you can only start CiscoView Web from the CCM menus.

To register CiscoView Web with CCM 2.2 as root, enter:

Step 1 cd dir where CCM package was extracted.

Step 2 ./install_ciscoview_web

Note You must register CVW on the CCM server as well as on the client machine.

Unregistering CVW 5.2 with CCM 2.2

The uninstall_ciscoview_web script removes the JAVA plug-in and the identity database and the CVW 5.2 server and port number entries. After running uninstall_ciscoview_web, only CiscoView Classic (CVC) starts from the CCM menus.

Note You must purchase CVW 5.2 separately. You can install CVW 5.2 on the same machine as the CEMF/CCM server machine or any other machine that is accessible by the CCM server or client machine. The machine with the CVW 5.2 installation must have IP and SNMP connectivity to the managed devices.

Sequence of Registering CVW and CBT 2.0

If CiscoView Web is registered with CCM AFTER CBT 2.0 is registered, close any browser window opened for CBT 2.0 before starting CVW from the CCM menu.

About General Polling Behavior

The uBR object "ENTITY-MIB.entLastChangeTime" is polled every 15 minutes (default) to detect any changes (such as OIR). If a change is detected, rediscovery is initiated. Polling of ENTITY-MIB.entLastChangeTime is spread across a 15-minute interval to evenly distribute the load on the system. The spread poll interval depends on the number of uBRs to be polled and the poll interval. The spread poll interval is impacted when uBRs are added (deployed) or removed (deleted). All subsequent polls occur at 15-minute intervals.

Example:

Scenario 1: poll interval = 15 minutes number of UBRs successfully deployed = 3 spread poll interval = 5 minutes ( poll interval / number of UBRs ) Assuming deployment started around 10:00am.

first poll cycle: ubr-1 is polled at 10:05 am ubr-2 is polled at 10:10 am ubr-3 is polled at 10:15 am

subsequent poll cycles: ubr-1 is polled at 10:20 am ubr-2 is polled at 10:25 am ubr-3 is polled at 10:30 am

Scenario 2: If a uBR is added (deployed) or removed (deleted), the process of calculating the spread poll interval is repeated.

Assume 2 additional uBRs are deployed at 10:30 am. Poll interval = 15 minutes number of uBRs successfully deployed = 5 spread poll interval = 3 minutes (poll interval / number of UBRs)

next poll cycle: ubr-1 is polled at 10:33 am ubr-2 is polled at 10:36 am ubr-3 is polled at 10:39 am ubr-4 is polled at 10:42 am ubr-5 is polled at 10:45 am

subsequent poll cycles: ubr-1 is polled at 10:48 am ubr-2 is polled at 10:51 am ubr-3 is polled at 10:54 am ubr-4 is polled at 10:57 am ubr-5 is polled at 11:00 am

CABLE MODEM PERIODIC DISCOVERY Cable modem periodic rediscovery is initiated every 24 hours (default). The 24 hour interval starts from the time the uBR was first polled. ubr-1 CM rediscovery will start at 10:05am + 24 hrs ubr-2 CM rediscovery will start at 10:10am + 24 hrs ubr-3 CM rediscovery will start at 10:15am + 24 hrs ubr-4 CM rediscovery will start at 10:42am + 24 hrs ubr-5 CM rediscovery will start at 10:45am + 24 hrs

Rehoming Cable Modems

The secondary uBR IP address is not required to perform the rehoming/reparenting operation.

Note Rehoming (redundancy) is not supported on the same uBR. You cannot rehome or reparent a cable modem from one card to another card within the same chassis.

Discovering Cards After a Card Is Inserted or Removed

Cisco Cable Manager 2.2 can detect if a card has been inserted or removed (OIR) from a uBR chassis in the following ways:

•Polling the uBR Chassis for the attribute <entLastChangeTime> every 15 minutes

•Decommissioning/commissioning the uBR:

Step 1 In the uBR Commission/Decomission template, click Decommission.
This moves the uBR state from Idle to Decommission

Step 2 Insert a card into or remove a card from the selected uBR chassis.

Step 3 In the uBR Commission/Decomission template, click Commission.

Note The Tree View shows the following states: Card Removed is reported as a "minor" alarm; Card Inserted is reported as a "normal" alarm.

Deleting Cable Modems

An out-of-service cable modem (a cable modem which is no longer registered on any uBR) is not automatically deleted from the Map Viewer. You must manually delete all cable modems that are no longer registered with any uBR.

About Performance Management Data Modeling

This section serves as a comprehensive guide for the you to model your performance data in your local network environment, creating a customized polling setup and database configuration.

Note Read this entire section before improving performance by modeling your data.

Note The following information about database modeling is only for raw data. By default, CCM polling does not use summary rules. If you implement summary rules, the summarized data size needs to be considered. No performance management application currently requires summarized data.

Cisco Cable Manager performance management includes performance polling and performance reporting tools.

Polling Groups

UBR polling groups contains uBR, downstream, upstream, RF card, Mac layer, and some cable modem information. These MIB objects are stored on the Cable Modem Termination System (CMTS) and can be polled from the CMTS directly.

Some cable modem information is stored in the cable modem, requiring the direct polling of cable modems.

Note If cable modem polling groups are turned on for a large number of cable modems, the database size can grow rapidly.

ObjectStore Database

CEMF uses ObjectStore, an Object-Oriented database.

The polling data is stored in attributeHistoryServer.db and attributeHistoryCollector.db.

For detailed information about performance polling and performance report tools or CEMF, see the Cisco Cable Manager Users' Guide Release 2.0, the Release Notes for Cisco Cable Manager Release 2.1, and the Cisco Element Management Framework Release 3.1 User Guide.

Database Purging

Database purging is scheduled daily for midnight. You can set the maxValueCount in the attributeHistoryServer.ini file to determine purging frequency. When `maxValueCount' values are known for a sample, the oldest values will be deleted first.

For example, if the default polling rate is 15 minutes, and the maxValueCount is set to 1000, polling table data will be purged after approximately 10 days. Each day, 96 samples are generated, which total 960 samples for 10 days.

If you set the default polling rate to 30 minutes and set the maxValueCount to 1000, the polling table will be purged after approximately 20 days.

Note Purging a database takes a long time if the database is very large. This problem is resolved in CEMF 3.2.

AttributeHistoryServer

AttributeHistoryServer is the process in CEMF that collects and manages polling data. This server purges polling data periodically according to the purging rules set in /opt/cemf/config/init/attrubiteHistoryServer.ini.

Minimizing Performance Degradation

While a database is being purged, applications running in CCM may experience some performance degradation. To minimize the performance impact:

Step 1 Set maxPurgeChunk = 1 in /opt/cemf/config/init/attributeHistoryServer.ini.

Step 2 To stop the historyAttributeServer process, enter

/opt/cemf/bin/sysmgrClient -k attributeHistoryServer

Step 3 To start the historyAttributeServer process, enter

/opt/cemf/bin/sysmgrClient -l attributeHistoryServer

Assessing Your Information Needs

Your hard-disk capacity affects performance, which is dependent on how many days of polling data you need to retain (data storage requirements) and how frequently you purge the polling data (purging frequency). To manage performance effectively, you need to determine how often you need what performance reports, which also determines your data storage requirements and the purging frequency. After you determine these requirements, you can effectively resize your database.

Data Storage Requirements

Determine how many days of data you need to maintain. This number affects the purging frequency and your minimum hard-disk capacity requirement.

Remodel the database size based on the new polling parameters and database configuration.

Performance Management Requirements

Use Tables 1, 2 and 3 to assess which reports you want to generate and the schedule for generating those reports. Turn off unnecessary polling groups and reduce the performance polling rate.

Polling Group and Performance Report Mapping

Table1 shows performance polling tables related to each performance report.

Table 1 Polling Group and Report Mapping

Performance Report
Polling Group

USSignalQualityReport

cblUbrGroup.CblUsSigTbl

USUtilizationReport

cblUbrGroup.cblUSTbl

DSUtilizationReport

cblUbrGroup.CblDSTbl

MacThroughputReport

cblUbrGroup.CblRFCardIfTbl
cblUbrGroup.cblUSTbl

MacStatisticsReport

cblUbrGroup.CblRFCardDiagTbl

PAPortThroughputReport

cblUbrGroup.CblPAPortTbl

CMUsageReport

cblUbrGroup.CblCMSIDTbl
cblUbrGroup.cblCMStatusTbl

CMQualityReport

cblCM

CMCpeReport

cblubrGroup.CblCmCpeTbl

To run a specific set of performance reports, you can turn on polling for certain polling groups and set polling intervals. Cisco recommends that you remodel the performance data sizing after making configuration changes. Also consider the hard-disk capacity and the database purging rates.

Polling Matrix

Table 2 shows the MIB objects or polling attributes included in each polling group. Polling is enabled for the polling group as a whole. Individual polling attributes cannot be enabled or disabled.

Note The cblCM and cblCMEther polling tables are polled from cable modems directly.

Table 2 Polling Matrix

Polling Table
Polling Attributes

cblUbrGroup.cblUBRTbl

OLD-CISCO-CPU-MIB.avgBusy5
CISCO-MEMORY-POOL-MIB.ciscoMemoryPoolUsed
CISCO-MEMORY-POOL-MIB.ciscoMemoryPoolFree

cblUbrGroup.CblDSTbl

IF-MIB.ifSpeed
IF-MIB.ifOutOctets
IF-MIB.ifOutUcastPkts
IF-MIB.ifOutDiscards
IF-MIB.ifOutErrors
IF-MIB.ifOutMulticastPkts
IF-MIB.ifOutBroadcastPkts
DOCS-IF-MIB.docsIfDownChannelPower

cblUbrGroup.cblUSTbl

IF-MIB.ifSpeed
IF-MIB.ifInOctets
IF-MIB.ifInUcastPkts
IF-MIB.ifInDiscards
IF-MIB.ifInErrors
IF-MIB.ifInUnknownProtos
IF-MIB.ifInMulticastPkts
IF-MIB.ifInBroadcastPkts
CISCO-DOCS-EXT-MIB.cdxQosCtrlUpAdmissionRejects
CISCO-DOCS-EXT-MIB.cdxQosCtrlUpReservedBW

cblUbrGroup.CblUsSigTbl

DOCS-IF-MIB.docsIfSigQUnerroreds
DOCS-IF-MIB.docsIfSigQCorrecteds
DOCS-IF-MIB.docsIfSigQUncorrectables
DOCS-IF-MIB.docsIfSigQSignalNoise

cblUbrGroup.CblRFCardIfTbl

IF-MIB.ifInOctets
IF-MIB.ifInUcastPkts
IF-MIB.ifInNUcastPkts
IF-MIB.ifInDiscards
IF-MIB.ifInErrors
IF-MIB.ifInUnknownProtos
IF-MIB.ifOutOctets
IF-MIB.ifOutUcastPkts
IF-MIB.ifOutNUcastPkts
IF-MIB.ifOutDiscards
IF-MIB.ifOutErrors

cblUbrGroup.CblRFCardDiagTbl

DOCS-IF-MIB.docsIfCmtsStatusInvalidRangeReqs
DOCS-IF-MIB.docsIfCmtsStatusRangingAborteds
DOCS-IF-MIB.docsIfCmtsStatusInvalidRegReqs
DOCS-IF-MIB.docsIfCmtsStatusFailedRegReqs
DOCS-IF-MIB.docsIfCmtsStatusInvalidDataReqs
DOCS-IF-MIB.docsIfCmtsStatusT5Timeouts

cblUbrGroup.CblPAPortTbl

IF-MIB.ifSpeed
IF-MIB.ifInOctets
IF-MIB.ifInUcastPkts
IF-MIB.ifInNUcastPkts
IF-MIB.ifInDiscards
IF-MIB.ifInErrors
IF-MIB.ifInUnknownProtos
IF-MIB.ifOutOctets
IF-MIB.ifOutUcastPkts
IF-MIB.ifOutNUcastPkts
IF-MIB.ifOutDiscards
IF-MIB.ifOutErrors

cblUbrGroup.cblPALocTbl

OLD-CISCO-INTERFACES-MIB.locIfInputQueueDrops
OLD-CISCO-INTERFACES-MIB.locIfOutputQueueDrops
OLD-CISCO-INTERFACES-MIB.locIfInRunts
OLD-CISCO-INTERFACES-MIB.locIfInGiants
OLD-CISCO-INTERFACES-MIB.locIfInFrame
OLD-CISCO-INTERFACES-MIB.locIfInOverrun
OLD-CISCO-INTERFACES-MIB.locIfInIgnored
OLD-CISCO-INTERFACES-MIB.locIfInAbort
OLD-CISCO-INTERFACES-MIB.locIfResets
OLD-CISCO-INTERFACES-MIB.locIfCollisions

cblUbrGroup.CblCMSIDTbl

DOCS-IF-MIB.docsIfCmtsServiceInOctets
DOCS-IF-MIB.docsIfCmtsServiceInPackets
CISCO-DOCS-EXT-MIB.cdxIfCmtsServiceOutOctets
CISCO-DOCS-EXT-MIB.cdxIfCmtsServiceOutPackets

cblubrGroup.CblCmCpeTbl

SNMP:CISCO-DOCS-EXT-MIB.cdxCmCpeMacAddress
SNMP:CISCO-DOCS-EXT-MIB.cdxCmCpeIpAddress

cblUbrGroup.cblCMStatusTbl

DOCS-IF-MIB.docsIfCmtsCmStatusIpAddress
DOCS-IF-MIB.docsIfCmtsCmStatusMacAddress
DOCS-IF-MIB.docsIfCmtsCmStatusRxPower
CISCO-DOCS-EXT-MIB.cdxIfCmtsCmStatusPercentOnline
CISCO-DOCS-EXT-MIB.cdxIfCmtsCmStatusAvgOnlineTime
CISCO-DOCS-EXT-MIB.cdxIfCmtsCmStatusAvgOfflineTime

cblCM

DOCS-IF-MIB.docsIfDownChannelPower
DOCS-IF-MIB.docsIfCmStatusTxPower
DOCS-IF-MIB.docsIfSigQSignalNoise
DOCS-IF-MIB.docsIfSigQMicroreflections

cblCMEther

IF-MIB.ifType
IF-MIB.ifInOctets
IF-MIB.ifOutOctets

Polling Data Characteristics

Table 3 lists the characteristics for polling data that is generated at each polling interval for each object type.

Table 3 Polling Data Characteristics

Object
Polling Group and Table
Polling Data
Default Polling Rate (in minutes)

uBR

cblUbrGroup.cblUBRTbl

3 integer

Not polled

Down Stream

cblUbrGroup.CblDSTbl

8 integer

15

Up Stream

cblUbrGroup.cblUSTbl
cblUbrGroup.CblUsSigTbl

10 integer
4 integer

15
30

RF Card

cblUbrGroup.CblRFCardIfTbl
cblUbrGroup.CblRFCardDiagTbl

11 integer
6 integer

15
30

PA Port

cblUbrGroup.CblPAPortTbl
cblUbrGroup.cblPALocTbl

12 integer
10 integer

15
Not polled

Cable Modem

cblUbrGroup.CblCMSIDTbl
cblubrGroup.CblCmCpeTbl
cblUbrGroup.cblCMStatusTbl
cblCM
cblCMEther

4 integer
3 integer
14 integer
4 integer
3 integer

Not polled
Not polled
30
30
Not polled

Resizing Your Database

You can use the following formula to estimate database size:

db size per obj = (no of attrs per obj) * (bytes required if value changes | bytes required if value does not change) * ( no. of values collected over time interval) * (4/3 = overhead of using ObjectStore collection)

According to the CEMF 3.1 documentation on Performance Data Storage, each attribute data sample of integer type (AttrInt32Value) has a size of 24 bytes (including a pointer to value, timestamp, and a status flag). If a value does not change, only 4 bytes are required to store the timestamp. However, because it is impossible to predict how frequently the value changes, it is reasonable to assume that each sample value changes over time to get an estimate for the worst case scenario.

Daily Polling Data Example

To calculate 24 hours of polling data for a cable network of 14 uBR7223 devices and 12000 cable modems, based on the default polling interval, do the following:

per UBR: not polled by default per DS: 8 * 24 * 96 *4/3 = 24576 B per US: 10 * 24 * 96 * 4/3 + 4 * 24 * 48 * 4/3= 36864 B per RFCard: 11 * 24 * 96 * 4/3 + 6 *24 * 48 * 4/3= 43008 B per PA Port: 12 *24*96*4/3 = 36864 B per CM: 14 * 24 * 48 *4/3 + 4*24*48*4/3 = 27648 B

Each uBR7223 has 2 radio frequency (RF) cards and one port adapter (PA) port; each RF card has one downstream and six upstream channels.

total DB size = 14 *2*1*24576 B + 14*2*6*36864 B + 14*2*43008 B + 14*1*36864 B + 12000*27648B = 340377600B =340 MB

The raw daily polling data size for all default polling groups, using default polling rate, is about 340 MB.

Maximum Database Size Example

In another example, assume all polling groups are turned on and the maxValueCount is set to 1000 in the attributeHistoryServer.ini file. Assume that, after some days of polling, all attributes of all objects have more than 1000 samples and are purged. Therefore there are a maximum of 1000 samples each. Calculate the data size per object as follows:

UBR: 3 * 24 * 1000 *4/3 = 96 kb DS: 8 * 24 * 1000 *4/3 = 256 kb US: 14 * 24 * 1000 * 4/3 = 448 kb RFCard: 17 * 24 * 1000 * 4/3 = 544 kb PA Port:22*24*1000*4/3 = 704 kb CM: 27 * 24 * 1000 *4/3 = 864 kb

For 14 uBRs and 12000 cable modems with all polling groups (including cable modem polling) turned on after an extended period, each polling attribute should have 1000 samples as set by the maxValueCount in the attributeHistoryServer.ini file. The estimation of the attributeHistoryServer.db size is:

ubr data size = <number of UBR> * 96KB + <number of DS> * 256KB + <number of US> * 448KB + <number of RFCard> * 544KB + <number of PA port> * 704KB

with the default

cm data size = 12000 * 864kb = 10368 mb = 10GB

Based on this example and assuming that the hard-disk 10GB, the hard-disk will be full before purging begins. Therefore, you must adjust the maxValueCount to a smaller value so that purging takes place frequently. If you intend to keep a large number of samples per polling attribute, increase the hard-disk capacity.

Because there are multiple variables in database modeling, when one or two of the variables change, follow the steps described in the "Resizing Your Database" section, readjust the other variables if necessary, and recompute the database sizing.

About Performance Reports

The Cable Modem (CM) Usage and Customer Premise Equipment (CPE) reports - in addition to other reports - have been redesigned to improve response time.

The CPE Type column in the CM CPE report has been eliminated because the CPE Type is set to a constant value on the agent.

Spikes in Performance Reports Attribute Value

If you see a spike in a performance chart or an unusually large delta value in a tabular report, the uBR or cable modem has probably been rebooted. This is not an error.

In performance reports, when a delta value is calculated for Counter32-type polling of raw data, it takes counter-rollover into consideration. The delta value is adjusted by adding the Counter32 maximum value of 4294967295L. If the counter value decreased between two consecutive intervals due to counter-resets triggered by the uBR or to cable modem reboots, the performance report treats the event as a counter-rollover case.

Save Or Load Function for All Performance Reports

The save or load function can now accept user-specified directories. However, the user-specified directory must have a subdirectory structure that consistent with the structure in the default directory to ensure that all reports are categorized by report type. You must also set the directory permissions correctly and ensure that the files in each directory are of the proper report type.

The directory structure for performance reports is default dir or user specified dir/PerformanceReportLog/report type specific dir

The specific report type directory name can be one of the following:

• USSignalQualityReport

• USUtilizationReport

• DSUtilizationReport

• MacThroughputReport

• MacStatisticsReport

• PAPortThroughputReport

• CMUsageReport

• CMQualityReport

• CMCpeReport

Note You can only specify the top level directory.

Dynamically Starting Polling for Newly Added Cable Modems

The performance polling controller periodically checks for new cable modems (default time interval is 3600 seconds). If any new cable modems are discovered for a uBR in "AllCMsPerfPolling" state, polling is enabled automatically within 3600 seconds after the cable modems are added to the Physical Tree view.

To disable the feature or to reconfigure the discovery interval, restart the performance polling controller:

Step 1 As root, enter:

cd $CEMF_ROOT/bin

cemf shell

./sysmgrClient -k perfPollCtrl

Step 2 Modify two variables in the config file $CEMF_ROOT/config/perfPollCtrl/perfPollCtrlUserData.ini under the CmPollingChecking section:

periodicCheckingEnable = 1; 0 for disable, 1 for enable

periodicCheckingInterval = 3600; unit is seconds

Step 3 Save the changes.

Step 4 Enter:

./sysmgrClient -x perfPollCtrl

Step 5 To check whether a uBR is in "AllCMsPerfPolling" state, choose:

Site object > Performance Polling > Start/Stop uBR/CM Polling

The Start/Stop UBR/CM Polling dialog box appears. The current state in the Cable Modem Polling frame indicates whether all cable modems under selected uBRs are in a polling state.

Note To set the state variable, click the Start (or Stop) Polling All CMs button in the Start/Stop UBR/CM Polling dialog box.

Caveats

This section describes known Cisco Cable Manager Release 2.0 and Release 2.2 software caveats and their related behaviors.

CEMF Caveats

DDTS: CSCdx07323
Limitation: CCM Cannot Handle a Flood of Traps

Symptom

When CCM receives a flood of traps (approximately 4-8 traps per second), it only processes the traps and all other functionality is blocked.

Problem Description

When there is a continuos flooding of traps, especially from cable modems changing online or offline status, CCM will not be able to create a new cable modem, update the status index of existing modems, or update the index of upstream or downstream ports on uBRs. This could result in incorrect data in the Performance Reports. Continuos flooding of traps could also affect other CCM functions such discovery, polling and threshold.

Workaround

To disable traps being forwarded to CCM from the uBR generating the traps:

Step 1 Telnet to the router generating the flood of traps.

Step 2 Enter enable to turn on privileged commands.

Step 3 Enter configure t to configure from the terminal.

Step 4 Enter no snmp-server host <ipaddress> <read community string>, replacing <ipaddress> with the ipaddress of the machine on which CCM is currently running and <read community string> with the read community string of the uBR.

DDTS: CSCdw91164
Large Number of Cable Modems On/Off trap at a time, could fail the CM Creation

Symptom

A large number of cable modems sending online or offline traps could cause a cable modem creation to fail.

Problem Description

Generating a large number of cable modem online or offline traps overloads the ubrController and the SNMP Stack. This could cause a cable modem creation to fail. This problem is related to an Agent DDTS CSCdw66359 (Flood of Traps being sent for Offline/flapping modems).

Workaround

Don't generate a flood of traps. Attach only a few (5 - 6) upstream modems at any given time. The uBR should be in IDLE state, and the cell-name (unprovisioned) and group-name should already be created. Or run the following CLI command: clear cable modem <mac-Address> reset for few modems at a time and make sure the uBR is in IDLE state. SNMP Community string are set for cable modems in CCM.

DDTS: CSCdw78340
Failed to Create Modem on Trap, if No Cell or Cell-Group Present Under Upstream

Symptom

If there is no Cell or Cell_Group under an Upstream, a new cable modem will not be created on TRAP.

Problem Description

Cable modem creation on trap fails if its respective Cell and Group objects are not present in the Map Viewer. This feature is not supported by CCM 2.2 or any prior release.

Workaround

None.

Installation Caveats

DDTS: ATLuk21287
CCM 2.2 May Not Install Properly

Symptom

While installing CEMF 3.1 patch 5 and patch 5.2, if you don't select the default Network Interface option, the Object Store database is not initialized correctly and CCM 2.2 may not be properly installed.

Problem Description

UNIX machines with multiple networks interface cards.

Workaround

Choose the default option "Network Interface" while installing CEMF.
See the following example to install the CEMF 3.1 package:

CEMF Manager Installation This machine is configured with multiple network interfaces.
Please choose the number that corresponds to the interface
you wish to use. Or hit return to enter the name by hand. 1 cta-8.cisco.com/141.22.77.21
2 cta-8a.cisco.com/1.8.6.22
3 cta-8b.cisco.com/10.2.2.11 Please choose a number (default: Other) [?,??,q]: <press RETURN KEY> Please enter the hostname of the server for this CEMF Manager system.
Hostname? [cta-8] [?] <press RETURN KEY> The hostname specified was "cta-8".
Is this correct? [y] [y,n,?] < press Y > CEMF Manager Installation Server Hostname : cta-8
Server IP Address : 141.22.77.21 Is this setup correct? [y] [y,n,?] <press Y >

DDTS: CSCdt51258
CEMF May Not Start Correctly

Symptom

CEMF may not start correctly after a UNIX machine is rebooted.

Problem Description

If you store the transact.log file in the /tmp directory while installing CEMF 3.1, the file can be lost. There is no guarantee that any files will still be in the /tmp directory after a system reboot.

Also, editing the AutoDiscoveryConfig.spec file may introduce some non-printable characters. If this configuration file is not parsed correctly by the discovery module, Cisco Cable Manager processes are not initialized properly.

Workaround

Note When you install CEMF 3.1, do NOT select /tmp for storing the database transaction log file transact.log.

Store the transact.log file on a separate disk partition with a reasonable amount of disk space (recommended: 9 GB) because this file is large with a large-scale uBR/cable modem deployment.

Tips Edit the AutoDiscoveryConfig.spec file carefully to avoid introducing any non-printable characters.

DDTS: CSCdu44445
CEMF Client Bug

Symptom

An application started from the launch3rdPartyApp service does not launch.

Problem Description

If you use a different installation path for the client than the one used for the server, the third-party application will not start on that client.

Workaround

Install third-party applications in the same location on both clients and servers.

DDTS: CSCdx03905
CCM Upgrade Should Save and Restore User Config Files

Symptom

CCM upgrade does not save user config files and restore them back after the upgrade is complete.

Problem Description

When CCM is being upgraded, save and restore the following files:

•RfCardCMOfflineThreshold.txt

•RfCardErrorDiscardRateThreshold.txt

•RfCardUtilizationThreshold.txt

•UpStreamCMOfflineThreshold.txt

•userTags.txt

•vendorTags.txt

Workaround

If you have modified any of the following files, you must save the modified files, upgrade the files, then copy the saved files back to $AV_ROOT/config/cblCtrl before using CCM.

• RfCardCMOfflineThreshold.txt

• RfCardErrorDiscardRateThreshold.txt

• RfCardUtilizationThreshold.txt

• UpStreamCMOfflineThreshold.txt

• userTags.txt

• vendorTags.txt

Note You may have to stop and start CEMF after restoring the saved files.

Deployment Caveats

DDTS: CSCdt95650
DDTS: CSCdu01000
DDTS: CSCdu02253
Cable Modem Grouping

Symptom

Group names are not in order. Extra group names are generated.

Problem Description

A group is supposed to have 100 cable modems before another group is created during the discovery process. There are instances when additional empty groups are created, or multiple groups are created, each containing less than 100 cable modems. Alternatively, some groups contain more than 100 cable modems, which could affect performance reporting.

Also, group names are not created in numerical sequence.

Workaround

No workaround.

DDTS: CSCdv23986
Cable Modem Discovery Status not Refreshed in the Manual Discovery Dialog Box

Symptom

The discovery status of the cable modem is not always updated in the Manual Discovery dialog box.

Problem Description

The current discovery state value for a uBR object is not always shown correctly in the Manual Discovery and Commission/Decommission dialog boxes. This is due to a refresh problem.

Workaround

To verify the status of the uBR, click refresh in the Manual Discovery and Commission/Decommission dialog boxes.

DDTS: CSCdw75413
Discovery/Polling Status Is Mixed Up

Symptom

Discovery or Polling State may appear in the wrong window.

Problem Description

This problem is seen when an attribute on an Element Manager dialog box exists in multiple dialog boxes. All dialog boxes displays the attribute that needs to be updated.

Workaround

Close and reopen the window; the correct state appears.

DDTS: CSCdw92201
uBR 10012: No entAliasMappingEntry for PRE-1

Symptom

The Fast Ethernet Interface on the Performance Routing Engine (PRE or PRE-1) will not appear in CCM2.2 Map Viewer GUI if the PRE or PRE-1 is moved from the primary to a secondary slot.

Problem Description

When the Performance Routing Engine (PRE or PRE-1) is moved from the primary to a secondary slot onthe uBR100012 chassis, the Fast Ethernet Interface will not appear under the secondary Performance Routing Engine in Map Viewer.

Workaround

No workaround.

Performance Management [Polling and Reports] Caveats

DDTS: CSCdt57598
Cable Modem Polling Affects Polling Cycle Intervals

Symptom

Cable modem polling interval skewed with every cable modem polling start.

Problem Description

After starting cable modem polling on one or more uBRs, subsequently starting cable modem polling on any other uBR causes an adjustment in the poll sample time for the uBRs that had polling turned on initially. This is a result of the design of the poller: the poller spreads the load of polling over time to ensure that CPU usage is at a constant low level. When new objects are added to the object list maintained by the poller, it redistributes all the objects that need polling over the polling interval. This is a transient issue in that it only occurs when polling configuration parameters are changed. The poller will then return to a steady state and the times between subsequent cable modem polls will again become constant.

Workaround

None.

DDTS: CSCdt44418
Cable Modem Polling Takes Too Long

Symptom

Cable modem polling takes too long to start for large-scale deployments.

Problem Description

The latency between the time that cable modem polling is started on a large number of modems and the first polled sample is received can be quite large, up to 2 times the configured polling interval. After the initial latency, the poller reaches a steady state and the polling interval is fairly constant between subsequent polls.

Workaround

None

DDTS: CSCds46075
DDTS: CSCds91305
Polling Takes Place even after uBR Is Decommissioned

Symptom

Polling takes place and alarms are received, even after a uBR is decommissioned.

Problem Description

Polling takes place and alarms relating to that uBR are received, even after the uBR has been decommissioned (from the user's perspective). Theoretically, polling should end if a uBR is decommissioned and should start if the uBR is recommissioned.

Workaround

None.

DDTS: CSCdw89817
Polling Offline Modems Could Severely Impact CCM System Performance

Symptom

There is a Snmp stack busy message in the asnycSnmpDataRepository.log file, and a Snmp timeout message in the perfPollCtrl.log file.

Problem Description

Modems that are currently offline are being polled, which causes SNMP timeouts. Depending on the number of SNMP retries associated with the number of offline modems and on network conditions that affect response time, the snmp stack busy condition can generate a missed poll for reachable devices.

Workaround

You can turn off cable modem polling on any uBR with a large number of offline modems. You can resume polling on that uBR after the majority of modems are online again.

DDTS: CSCdw83052
Polling Anomaly on uBR After Card Swap

Symptom

After a card swap, the two original radio frequency (RF) card objects remain in the object tree while two new RF card objects are added.

Problem Description

Instead of removing the old card object and its children when you swap out an RF card, the entPhysicalIndex of the old card object is set to -1 to preserve all historical data, such as performance polling data and event/alarms.

Choose Tools > Open Object Configuration and select ENTITY-MIB.entity PhysicalcblRFCard for Object Type. The EntityPhysicalIndex is set to -1 for the old card. All the new data collected will be stored against the new card object and its children. Based on this information, you know which card is actually in the slot. You can also monitor the Event log in the Event Browser to catch the OIR occurrence.

Poller Behavior

When the OIR occurs, the poller continues to poll the uBR. It is the new card and all its children (related attributes) that are being polled. However, this polling data is not stored unless a workaround is applied. For the old card, the macLayer is not polled but a missed poll message is recorded for all attributes associated with the children of the old card.

Impact on Performance Reports

For the old card, you can run performance reports without any workaround; all polling data before the OIR is reported. You must apply the workaround as soon as possible after the card swap to avoid data loss for the new object.

Impact on CEMF Performance Manager

For the old card, all polling data associated with it and its children appear as `missed poll' or simply no polling data recorded for macLayer after OIR. After applying the workaround, polling data for the new card object and its children appear.

Workaround

Stop and start polling to force the object group to update after an OIR or other configuration change, such as inserting a new card.

DDTS: CSCdw49383
DS Util field > 100% for MAC Throughput Report

Symptom

The column labeled Downstream Util in the MAC Throughput Report should be a percentage, but the values displayed are sometimes greater than 100%.

Problem Description

The reason downstream utilization is above 100% is that the current algorithm deriving macLayer ifSpeed does not take the downstream ifSpeed into consideration. This algorithm needs to be enhanced to use maximum downstream ifSpeed for outUtilization, and use maximum upstream ifSpeed for inUtilization.

Workaround

None.

Fault Management Caveats

DDTS: CSCdx07354
Limitation: Default Threshold Regime Frequency Cannot Sustain Poll

Symptom

Limitation: Default Threshold Regime Frequency Cannot Sustain Poll.

Problem Description

While creating a threshold regime, the default frequency is 5 minutes. This default is supplied by the CEMF Threshold Manager. This value will overload the SNMP stack, causing lots of failures if a large number of objects are selected.

Workaround

Change the frequency value to 30 minutes while creating the threshold.

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

•http://www.cisco.com

•http://www-china.cisco.com

•http://www-europe.cisco.com

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships 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 as an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

•Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

•P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

•P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows:

•P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

•P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.

This document is to be used in conjunction with the Cisco Cable Manager Users' Guide publication.

CCIP, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Fast Step, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.

All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0201R)


Copyright © 2002, Cisco Systems, Inc.
All rights reserved.

hometocprevnextglossaryfeedbacksearchhelp

Posted: Thu May 27 06:57:06 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.