cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/camp_3x/cmgr_3_0
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for Campus Manager 3.0.1 Voice Update on Solaris

Release Notes for Campus Manager 3.0.1 Voice Update on Solaris

These release notes are for use with the Solaris version of the Campus Manager 3.0.1 Voice Update for the CiscoWorks2000 family of products.

These release notes provide:

Documentation Roadmap

Use these publications to learn how to install and use Campus Manager 3.0.1:

Refer to these publications to learn how to install and use Cisco CallManager 3.0:

Additional Information Online

Use these online sources for more information about Campus Manager 3.0.1:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/sup_dev/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/

Overview of the Voice Update

Caution The Voice Update overwrites certain Campus Manager 3.0 packages, so rollback to Campus Manager 3.0 requires that you uninstall and reinstall Campus Manager 3.0 and restore your database.

The Campus Manager Voice Update is a collection of updated packages for voice feature support. Install the Voice Update if you plan to:

The Voice Update also contains:

The Voice Update contains only the updated packages, not a complete Campus Manager image. Therefore, Campus Manager 3.0 is required for the Voice Update. In addition, you must install the CD One Voice Update or a version of CD One more recent than the 2nd Edition, if one becomes available. To download the CD One Voice Update, refer to the following URL:

http://www.cisco.com/kobayashi/sw-center/netmgmt/cw2000/cw2000server.html

Note   To discover Cisco CallManagers, you must install the Cisco CallManager 3.0(2b) software release.

Installing the Voice Update

This section contains the following information:

Note   You must install the CD One Voice Update or a version of CD One more recent than the 2nd Edition, if one becomes available. Refer to Release Notes for the CD One 2nd Edition 1.1.1 Voice Update on Solaris for more information.

Only the installation paths in Table 1 are supported.


Table 1: Overview of Voice Update Installation Paths
If you want to... Then you must...

Install the Voice Update on Campus Manager 3.0.

    1. Back up the database.

    2. Install the CD One Voice Update or a more recent version of CD One, if one becomes available.

    3. Install the Campus Manager Voice Update from CD-ROM or CCO.

Reinstall the Voice Update on a system that already has the Voice Update installed.

    1. Reinstall the Voice Update from CD-ROM or CCO.

Reinstall Campus Manager 3.0 plus the Voice Update on a system that already has the Voice Update installed.

    1. Run the allowrollback script.

    2. Reinstall Campus Manager 3.0.

    3. Reinstall the Campus Manager Voice Update from CD-ROM or CCO.

Note   You must reinstall the Voice Updates to be in a supported configuration.

Uninstall both Campus Manager 3.0 and the Voice Update

    1. Back up the database.

    2. Uninstall Campus Manager 3.0 and the Voice Update.

Remove the Campus Manager Voice Update and return to Campus Manager 3.0.

    1. Back up the database.

    2. Uninstall Campus Manager 3.0 (also uninstalls the Voice Update and the database).

    3. Reinstall Campus Manager 3.0.

    4. Restore data from the backup previous to Voice Update installation.

Installing the Voice Update from CCO

Note   You must install the CD One Voice Update or a version of CD One more recent than the 2nd Edition, if one becomes available. Refer to Release Notes for the CD One 2nd Edition 1.1.1 Voice Update on Solaris for more information.

The Voice Update and a readme file explaining the installation procedure are available from CCO at the following URL:

http://www.cisco.com/kobayashi/sw-center/netmgmt/cw2000/cm.html

Installing the Voice Update from the CD-ROM

Note   You must install the CD One Voice Update or a version of CD One more recent than the 2nd Edition, if one becomes available. Refer to Release Notes for the CD One 2nd Edition 1.1.1 Voice Update on Solaris for more information.
Step 1   Back up the database.

Caution The Voice Update overwrites certain Campus Manager 3.0 packages, so rollback to Campus Manager 3.0 requires that you uninstall and reinstall Campus Manager 3.0, and you will need this backup.

Step 2   Install the CD One Voice Update or a version of CD One more recent than the 2nd Edition if one becomes available. Refer to the Release Notes for the CD One 2nd Edition 1.1.1 Voice Update on Solaris for more information.

Step 3   As root, mount the Campus Manager Voice Update CD-ROM, using either of the following methods:

For more information on mounting and unmounting the CD-ROM, refer to Installing and Setting Up Campus Manager on Solaris.

Step 4   Run the installation program.

For a local installation, enter:

# cd /cdrom/cdrom0
# ./setup.sh

For a remote installation, enter:

# cd remotedir
# ./setup.sh

where remotedir is the remote location where the CD-ROM is mounted.

Step 5   To verify the installation, select CiscoWorks2000 Server>About CiscoWorks2000>Applications and Versions. The Campus Manager Version 3.0 row should show the current installation date and one installed patch.

Reinstalling Campus Manager 3.0 and the Voice Update

The Voice Update overwrites certain Campus Manager 3.0 packages, so uninstalling the Voice Update removes both the Voice Update and Campus Manager 3.0, as well as the database. The allowrollback script allows you to reinstall Campus Manager 3.0 plus the Voice Update without needing to uninstall.

Caution You must reinstall the Voice Update after running this script to return your system to a supported configuration.

If you want to remove the Voice Update, refer to the "Uninstalling Campus Manager 3.0 and the Voice Update" section.

To reinstall Campus Manager 3.0.1:

Step 1   Run the allowrollback script for Campus Manager:

Caution Do not run the allowrollback script for the CD One Voice Update until you run the script for products that depend on it; verification is not automatically performed.

# cd path/patch

# ./allowrollback.sh cm

where path is the path in which you installed Campus Manager (the default is /opt/CSCOpx).

Step 2   Reinstall Campus Manager 3.0, to restore files that were overwritten by the Voice Update. Refer to Installing and Setting Up Campus Manager on Solaris for more information.

Step 3   Delete the temporary file cw2k.install:

# rm /TEMP/cw2k.install

where TEMP is the setting of your TEMP environment variable.

Step 4   Reinstall the Voice Update according to the instructions in the "Installing the Voice Update from the CD-ROM" section.

Step 5   To verify the installation, select CiscoWorks2000 Server>About CiscoWorks2000>Applications and Versions. The Campus Manager Version 3.0 row should show the current installation date and one installed patch.

Uninstalling Campus Manager 3.0 and the Voice Update

The Voice Update overwrites certain Campus Manager 3.0 packages, so rollback to Campus Manager 3.0 requires that you uninstall and reinstall Campus Manager 3.0 and restore data from the backup previous to Voice Update installation.

Caution Uninstalling Campus Manager deletes the database. Make sure to back up your database before uninstalling.

If you want to reinstall both Campus Manager 3.0 and the Voice Update, refer to the "Reinstalling Campus Manager 3.0 and the Voice Update" section.

Step 1   Back up the database.

Step 2   Uninstall both Campus Manager 3.0 and the Voice Update. Refer to Installing and Setting Up Campus Manager 3.0 on Solaris.

Step 3   Reinstall Campus Manager 3.0. Refer to Installing and Setting Up Campus Manager 3.0 on Solaris.

Step 4   Restore the database from your previous backup. Refer to the ANI Server Admin online help for more information.

Caution Restoring the database from a backup permanently replaces your database with the backed up version. Also, as a part of restoring the database, CiscoWorks2000 is shut down and restarted. Make sure you are not running any critical tasks. Otherwise, you might lose data.

Addendum to Installing and Setting Up Campus Manager on Solaris

To update Installing and Setting Up Campus Manager on Solaris, add Step 7 to the "Setting Up Path Analysis" section of Chapter 3, "Setting Up Campus Manager":

Step 7: Install Cisco CallManager with Call Detail Record (CDR) logging enabled, or Voice over IP (VoIP) traces will fail.

Addendum to Using Campus Manager

Using Campus Manager has been updated to include information about the Voice over IP support provided by Campus Manager.

For the latest version of Using Campus Manager, do one of the following:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/camp_3x/cmgr_3_0/index.htm

The following chapters have been changed:

Chapter 5--Managing Physical and Logical Network Services Using Topology Services

The following sections are new or changed:

Using Network Topology Windows

The second and third sub-bullets under the bullet, "Network Views--Displays the following" have been replaced with the following:

Using Topology Services

The following task has been added to Table 2-3, Topology Services Tasks:
Task Purpose Action

Launch Cisco CallManager from the Layer 2 view.

You can launch Cisco CallManager for any discovered Cisco CallManager server.

Right-click on a Cisco CallManager icon in a network view and select Cisco CallManager from the pop-up menu. Or right-click on a Cisco CallManager entry in the summary view and select Cisco CallManager from the pop-up menu.

Refer to the Cisco CallManager documentation or online help for detailed information.

Cisco CallManager (New)

Cisco CallManager is an application that provides signaling and call-control services to Cisco integrated multimedia and third-party applications. The ANI Server discovers Cisco CallManager servers, and Topology Services displays them in the map views, for example, the Layer 2 view. You can start Cisco CallManager for a particular Cisco CallManager server from Topology Services.

Chapter 6--Locating Users in the Network with User Tracking

The following sections have been changed:

User Tracking Tasks

The following tasks have been added to Table 3-2, User Tracking Tasks:

Task Purpose Action

Discover IP phones in your network.

To query all IP phones registered with discovered Cisco CallManager servers. (Cisco CallManager servers are discovered by ANI.)

Select Action > Discover IP Phones.

Display IP phones in your network.

To display IP phones in your network.

Select Query > Show IP Phones.

User Tracking Concepts

The paragraph in this section has been replaced with the following:

User Tracking uses the user and host acquisition service module in the Asynchronous Network Interface (ANI) Server to discover end-user nodes. IP phones are discovered by querying the Cisco CallManager servers. Cisco CallManager servers are discovered the same way as other devices, such as switches and routers, are using ANI. See ANI online help for more information about ANI and user and host acquisition. ANI uses the device discovery service module to obtain IP phone information. Refer to the Getting Started with the CiscoWorks2000 Server guide for a detailed description of these service modules.

Chapter 7--Tracking Packet Flow Using Path Analysis

The following sections are new or changed:

Starting and Navigating in Path Analysis

Figure 4-1 has been replaced with the following:


Path Analysis Tasks

The following tasks have been added to Table 4-2, Path Analysis Tasks:

Item Description Usage Notes

Perform a VoIP trace on a completed call.

Trace the paths that VoIP traffic for a completed call follows on your data network.

A completed call is a call that was answered and completed without error; therefore, a CDR exists for the call.

First you retrieve the CDRs that contain the data relevant to the call you are interested in, and then perform the trace based on the telephone numbers in the CDR.

    1. Select Voice Trace.

    2. Click Find Call....

    3. Select (or clear) the Match Calling Number check box to enable (or disable) filtering on the calling telephone number.

    4. If the Match Calling Number check box is selected, enter the source telephone number in the Match Calling Number field.

    5. Select (or clear) the Match Called Number check box to enable (or disable) filtering on the called telephone number.

    6. If the Match Called Number check box is selected, enter the destination telephone number in the Match Called Number field.

    7. Select (or clear) the Match Time Call Placed check box to enable (or disable) filtering on the time the call was placed.

    8. If the Match Time Call Placed check box is selected, enter the time the call was placed.

    9. Click Get Records.

    10. Select the desired CDR.

    11. Click Start Trace.

Item Description Usage Notes

Perform traces:

  • To or from a gateway to Cisco CallManager server.

  • To or from an IP telephone to a Cisco CallManager.

  • To or from two end points for a call in progress.

  • To or from two end points for a potential call.

Trace the signaling path from a gateway or IP telephone to Cisco CallManager if you are experiencing latency, dropped packets, jitter, or missing dial tone with IP phone functionality.

Trace a call in progress or a potential call to determine the most likely path using IP addresses rather than telephone numbers as the source and destination.

    1. Obtain IP addresses in User Tracking for the voice-enabled devices and gateways in your network, including IP phones and Cisco CallManagers.

    2. In the Path Analysis main window, select Data Trace.

    3. Enter the IP address for the gateway or IP phone in the From field.

    4. Enter the IP address for the Cisco CallManager in the To field.

    5. Click Start Trace.

Path Analysis Requirements

The following paragraph has been added to the end of this section:

For Voice over IP (VoIP) tracing, CDR logging must be enabled on all Cisco CallManager servers.

Valid VoIP Trace End Points (New)

You can trace the flow of packets for three types of VoIP telephone calls on your data network, and the type of end points you specify depends on the type of call you are interested in:

Type of Call

Description

Trace Methods

 Completed call


 Telephone call that has occurred and been completed. Call Detail Records (CDRs) exist only for completed calls.


 Trace as voice data, using the telephone number of the called (destination end point) telephone.


 Call in progress


 Telephone call that has begun, but has not yet concluded.


  • Obtain IP addresses in User Tracking for the voice-enabled devices and gateways in your network.
    

  • Trace the packets as standard data (select Data Trace), using end point IP addresses.
    

  • Do not use telephone numbers. (No CDRs exist for a call in progress.)
    



 Potential call


 Telephone call that has not occurred, but might occur in the future.


  • Obtain IP addresses in User Tracking for the voice-enabled devices and gateways in your network.
    

  • Trace the packets as standard data (select Data Trace), using end point IP addresses.
    

  • Do not use telephone numbers. (No CDRs exist for a call in progress.)

Call Detail Records and VoIP Tracing (New)

Call Detail Records (CDRs) exist only for completed calls (calls that have occurred and have been successfully completed). CDRs contain the called and calling telephone numbers, which are required to perform a voice trace.

To find the required CDRs, you can filter your search criteria by any combination on the following three filters available in the Voice Trace Query window:

If your search query proves too broad to produce the desired results, you can narrow your search by providing a Calling Number value. When you enable Calling Number Filtering, you include among your CDR search criteria the source end point to which the call was directed.

Call Detail Record (CDR) results appear in the large white space within the Voice Trace Query window. This area contains a collapsible tree display of CDRs received from the server.

You can expand a CDR to display additional information about the segment, such as the date and time of the call, the IP address of the VoIP device, the port, and the cause of termination. Information in the tree view allows you to confirm you have found the correct CDR before you start to trace the path between the end points.

Appendix A--Troubleshooting Campus Manager

The following sections contain new information:

Topology Services--Frequently Asked Questions

The following new frequently asked questions have been added to this section:

Which view shows the Cisco CallManager servers in my network? (New)

Topology Services displays the Cisco CallManager servers discovered by the ANI Server in the Layer 2 view and all other applicable views. For example, if the Cisco CallManager server is connected to a device that belongs to a particular VTP domain, the Cisco CallManager server is displayed in that VTP domain view.

Why does a Windows NT server appear as a Cisco CallManager Server? (New)

If a Windows NT server is used as a seed device for ANI Server discovery, it will appear in Topology Services as a Cisco CallManager (CCM) server. Because a CCM server is installed on Windows NT, Topology Services discovers both of these device types as one device.

Note   It is not recommended to use an end-station as a seed device. Refer to the ANI Online Help for information about choosing a seed device.

User Tracking--Frequently Asked Questions

The following new frequently asked question has been added to this section:

Why doesn't the IP phone display act like the User Tracking table? (New)

The IP phone display is a dialog box that displays noninteractive information. The menu functionality of the User Tracking display table does not apply to dialog boxes. For example:

User Tracking regenerates IP phone entries after a major acquisition or whenever you select Action > Discover IP Phones.

Select Query > Show IP Phones to view the latest information.

Path Analysis--Frequently Asked Questions

The following new frequently asked questions have been added to this section:

Do I need to configure anything in order for voice traces to function? (New)

Yes, you need to:

    1. Enable Call Detail Records (CDRs) on Cisco CallManager (CCM).

    2. Enable SNMP on CCM.

    3. Provide community strings for all CCM devices to the ANI Server.

    4. Provide IP addresses for discovery of CCM devices.

Am I required to use the Voice tab for voice traces? (New)

In nearly all cases, you must select the Voice Trace radio button in the Path Analysis main window to trace completed calls. However, there are two exceptions.

Do not select the Voice Trace radio button if you are looking at the signaling path by either:

In these two cases, select the Data Trace radio button instead.

Should I use parentheses or hyphens when specifying a telephone number for voice tracing? (New)

Any parentheses, hyphens, spaces, or other non-numeric characters that you enter when specifying a telephone number for voice tracing are automatically deleted from your query.

Should I specify a calling number for voice tracing? (New)

The Calling Number value might not provide valid Call Detail Record (CDR) matches to your query, so in most cases you should not specify a calling number.

However, if you do not specify a calling number, and if your query results in too many CDRs found, then you can narrow your search criteria by specifying a calling number.

Should I specify the called number for voice tracing? (New)

Yes, it is the best to specify the called number.

Should I specify the time and time range for voice tracing? (New)

Yes. It is best to specify the start time and time range for voice tracing.

What is the best time range to specify for voice tracing? (New)

In many cases, a 15-minute range before and after the specified time is sufficient to locate a call without exceeding the limit of 100 Call Detail Records (CDRs).

If your query matches more than 100 CDRs, no records are shown. Instead, an error message appears.

If you specify a time range that is too brief, the search might not find your desired CDR.

How do I trace calls over a Public Switch Telephone Network (PSTN)? (New)

IP phone calls routed over a Public Switch Telephone Network (PSTN) follow a uniform path:

Calls following this path produce one Call Detail Record (CDR) for the first leg of the call and another CDR for the final leg of the call. Each CDR contains a start and end point for its leg of the call. No CDR exists for the PSTN path.

When you search for this kind of call, both CDRs should appear in the Voice Trace Query Results window. You must then select each CDR independently to perform a trace on that leg of the call.

You cannot perform a voice trace on the PSTN leg of the call.

Can I perform a trace on busy or unanswered calls? (New)

Yes, however you must perform a data trace using the IP addresses of the IP telephones. You cannot perform a voice trace using the calling and called numbers because busy or unanswered calls do not generate CDR records, which reference the calling and called numbers.

Path Analysis--Troubleshooting Suggestions

The following information has been added to table A-5:

Symptom Probable Cause Possible Solution
Voice Traces

No records found in query.

Records might not be found because:

  • The Cisco CallManager (CCM) server might not have been discovered.

  • The search criteria are too narrow.

  • Call Detail Record (CDR) logging is disabled on the CCM server, or on one or more CCMs in a cluster.

    1. Select Topology Services > Layer 2 View and check whether the CCM server was discovered. The CCM server icon should be green.

    2. Enter a less restrictive time range, exclude the Calling Number value, and/or enter a less specific called number.

    3. Enable CDR logging on CCM.

Too many matches found.

The search criteria are too broad.

Enter a more restrictive time range and/or a more specific calling/called number.

Call Detail Record (CDR) query takes too long.

CDR query might take too long because:

  • Your search criteria are too broad. In organizations with high call volume, a longer time range (outside the 15-minute recommended range) might be too broad, causing the CCM server to have to search through too many records.

  • Path Analysis cannot access the CCM server.

    1. Narrow your search criteria by reducing the time range or providing a calling number.

    2. Make sure that all CCM servers that have been discovered in Topology Services are running and accessible.

Notes and Known Problems

Known problems are unexpected behaviors or defects in the Campus Manager 3.0.1 Voice Update software.

You can search for known problems on the Cisco bug tracking system tool, called Bug Navigator II. To access Bug Navigator II, do one of the following:

This section contains notes and caveats for Campus Manager 3.0.1 Voice Update, as follows:

General Notes and Known Problems

Note   Note the following:


Table 2: General Known Problems
Bug_ID Summary Explanation

None

The User Tracking online help includes descriptions of fields that do not exist in the Voice Update.

The User Tracking online help includes descriptions of the UserName and E911Locations columns, but they do not exist in the Campus Manager Voice Update.

None

CAM certificate expired.

Sometimes, when you are asked to install CAM, the dialog box indicates that the certificate has expired. Answer yes to indicate that you would like to continue anyway.

CSCdm83204

Applets do not work when accessed using localhost.

Campus Manager applets do not work when accessed using localhost. All three applets launch but system stops responding.

To work around problem, access server locally, with full DNS name or IP address.

Note   The DNS name must be the first entry in /etc/hosts.

CSCdr98840

Telnet not working with Windows 95/98 client.

Telnet cannot be invoked from Topology Services or Path Analysis menus on Windows 95 or Windows 98 clients.

To work around, launch CiscoView for the device and click the Telnet button in CiscoView.

Topology Known Problems


Table 3: Topology Known Problems
Bug ID Summary Explanation

CSCdp66221

Link to fast hubs is in alarm state (red).

The links to a fast hub device are displayed in red.

CSCdr37775

Topology Services displays more Cisco CallManagers than are in the ANI database.

If a Windows NT server has CDP running but not Cisco CallManager SNMP, Topology Services still displays it as a Cisco CallManager.

User Tracking Known Problems


Table 4: User Tracking Known Problems
Bug ID Summary Explanation

None

An IP phone entry of a Cisco CallManager or host in the main User Tracking table may show the MAC address but not the IP address.

The MAC and IP address of a Cisco CallManager or host in main User Tracking table is acquired from discovered switches and routers. If the appropriate router was not discovered to resolve MAC to IP, User Tracking will not be able to show IP address.

Note   IP addresses of IP phones shown in the phone table are acquired from Cisco CallManager and not the router.

CSCdp99565

User Tracking: PortName field is wrong for Catalyst 1900 and 2800 devices.

User Tracking might show incorrect PortName for stations that are connected to Catalyst 1900 and 2800 devices.

CSCdr53022

Cisco CallManager host does not show up in the main User Tracking table.

When a Cisco CallManager (or host or IP phone) is connected to a hub where there is a CDP device such as a switch or router connecting to the hub, User Tracking will not be able to discover that Cisco CallManager (or host or IP phone).

CSCdr55949

User Tracking IP phone table does not show all the Cisco CallManager supported phones.

User Tracking phone table does not show SoftPhone Entries.

The SNMP agent in Cisco Call Manager does not report any SoftPhone entries, such as H.323; therefore, User Tracking will not be able to discover these SoftPhones.

CSCdr55953

SNMP requires CCM service restarted for phone addition/deletion.

After you add or remove an extension from a phone, you must restart the Cisco CallManager service for SNMP agent to report the new information so User Tracking can discover the changes.

CSCdr79231

Unable to query large number of entries in User Tracking with Windows 98 and Internet Explorer 5.01

User Tracking in Campus Manager 3.0 and 3.0.1 cannot show more than 1,000 host entries on Internet Explorer on a Windows 98 client.

To work around, use Netscape Navigator on a Windows 98 client.

CSCdr85384

Phone entries shown in UT differ from entries in Cisco CallManager database.

The User Tracking phone entries for each Cisco CallManager acquired via SNMP may be different from the entries in Cisco CallManager.

The Cisco CallManager database displays a historical record of all phones ever registered to the Cisco CallManager. However, the SNMP agent only retains a record of phone registrations since the agent was started.

CSCdr87027

SNMP agent does not report consistent phone entries among Cisco CallManagers in a cluster.

User Tracking displays a different phone list for each Cisco CallManager in a cluster, based on the SNMP registration list per Cisco CallManager.

The Cisco CallManager databases in a cluster are synchronized, but each SNMP agent in a Cisco CallManager cluster maintains its own registration list.

Path Analysis Known Problems


Table 5: Path Analysis Known Problems
Bug ID Summary Explanation

CSCdr31392

Path Analysis voice trace shows fewer properties than data trace.

Voice trace might display less data than a data trace because algorithm used ensures all voice traces are not data.

CSCdr49831

Selecting CDR records in Voice Trace window might not work.

Sometimes, selecting CDR records in the Voice Trace window does not work. Java Console displays NullPointerException. Path traces are unaffected.

To work around, select the records again.

CSCdr85174

Need more details when clusterinfo.asp not accessible.

When Path Analysis queries for CDRs, a warning box displays for each Cisco CallManager (or other PC running SNMP and CDR). If multiple errors are displayed at the same time, the program might stop responding.

To work around:

    1. Determine if each Cisco CallManager is properly configured by entering the following URL in your web browser:

http://CCM address/ccn/clusterinfo.asp
where CCM address is the address of your Cisco CallManager. The response should contain a unique node identifier and an IP address.

    2. To exclude improperly configured Cisco CallManagers from discovery, use the Do not discover devices in these ranges option in the Configure Discovery Settings window.

Obtaining Documentation

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or 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. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.

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

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Note   If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.

Cisco Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online 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.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, 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 CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO in the following ways:

You can e-mail questions about using CCO to cco-team@cisco.com.

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.

To contact by e-mail, use one of the following:

Language

E-mail Address

 English


 tac@cisco.com


 Hanzi (Chinese)


 chinese-tac@cisco.com


 Kanji (Japanese)


 japan-tac@cisco.com


 Hangul (Korean)


 korea-tac@cisco.com


 Spanish


 tac@cisco.com


 Thai


 thai-tac@cisco.com

In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

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, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

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

We appreciate and value your comments.

Access Registrar, AccessPath, Any to Any, Are You Ready, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, IQ Breakthrough, IQ Expertise, IQ FastTrack, IQ Readiness Scorecard, The IQ Logo, Kernel Proxy, MGX, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, CollisionFree, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document 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. (0005R)


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Aug 10 10:55:38 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.