|
|
Table Of Contents
Release Notes for Cisco Access Router Manager
Release 1.1Coresident Element Managers Supported
Cisco Access Router Manager Documentation
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco Access Router Manager
Release 1.1
Contents
This document is divided into the following sections:
•
Caveats
•
•
Introduction
The Cisco Access Router Manager is an element management system (EMS) for the Cisco access routers. The Cisco Access Router Manager routers are a multifunctional platform that combines dial access, routing and LAN-to-LAN services, and multiservice integration of voice, video and data in the same device.
System Requirements
The EM can be deployed in a number of different configurations, from a single hardware system to a multisite distributed management system.
The EM has precise memory requirements, supports specific hardware components, and requires certain Cisco EMF versions. Refer to the following sections for details regarding these system requirements.
All Cisco EMF-based solutions run on Sun Solaris/SPARC hardware running the Solaris operating environment, release 8.
Server Requirements
The recommended minimum hardware requirements for servers are:
•
–
–
–
–
•
–
–
–
–
•
–
–
–
–
If a number of graphically intensive applications are run on a workstation, it is helpful to use a 24-bit Sun color card. A typical manager installation requires 500 MB of free disk space in a file system. An appropriate amount of free disk space for database files is also required.
Client Requirements
The recommended minimum hardware requirements for clients are Sun Microsystems ™ SunBlade 100, Ultra 10 or similar with the following:
•
•
•
If a number of graphically intensive applications are run on a workstation, it is helpful to use a 24-bit Sun color card. A typical manager installation requires 500 MB of free disk space in a file system.
Software Requirements
Use Cisco Access Router Manager only with the supported routers using Cisco IOS Releases 12.1(17), 12.2(13)T3, and 12.2(15)T. Other IOS versions may be used; however, some Cisco Access Router Manager functionality may not be compatible with other IOS software.
Cisco Access Router Manager requires the following software:
•
•
•
Additionally, Cisco EMF 3.2 Service Pack 4, Patch 6.2 is required in support of Cisco Access Router Manager co-residency with Cisco 7000 Series Manager and Cisco 12000/10720 Manager:
Note
http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/products_installation_and_configuration_guide_book09186a00800ffd0d.html.License Requirements
The EM uses Cisco EMF, which requires a license key to operate.
Note
http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/products_user_guide_book09186a00800ffd02.html.Hardware Supported
Cisco Access Router Manager supports the following modular access routers:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The following table includes each module supported by Cisco Access Router Manager. For descriptions of each router and module, refer to the Cisco Access Router Manager User Guide.
Table 1 Modules Supported
Coresident Element Managers Supported
Multiple EMs can be installed onto a single EMS server, thereby allowing multi-device and multi-vendor management on a single system. The following packages are compatible with the Cisco Access Router Manager to create a coresident network management system:
•
•
•
For additional information on installing and using these EMs, refer to the applicable release notes, installation guides, and user guides.
Installation Notes
The Cisco Access Router Manager Installation Guide provides information to install, configure, and uninstall Cisco Access Router Manager. For any specific installation issues in this software release, see the "Caveats" section.
Caveats
Resolved Caveats
The following limitations which existed in the Cisco Access Router Manager, Release 1.0 have been resolved in Release 1.1.
Open Caveats
The following caveats exist in Cisco Access Router Manager. Generally, caveats include unexpected behaviors or defects in the software release. This document addresses caveats which directly impact user functionality and indicates alternative approaches (workarounds) where available. A complete listing of caveats is available in the Cisco bug tracking tool ( http://www.cisco.com/support/bugtools).
Open Caveats in Release 1.0
This section describes known limitations that exist in the Cisco Access Router Manager, Release 1.0.
•
Symptom: The object name for some chassis commissioning alarms may not be mapped in the Event Browser application.
Conditions: This will occur in extremely rare circumstances.
Workaround: Close the Event Browser application and re-launch it.
•
Symptom: Cisco EMF backup and restore may show devices in a normal state when they are not
Conditions: If a Cisco EMF backup is taken when a device is in a non-normal state, upon restore it will show Normal or be stuck in a discovery state when in actually it is currently un-managed.
Workaround: Decommission and recommission the chassis.
•
Symptom: Grey out Performance Log button for modules with no CPU
Conditions: Currently, the Start button for performance polling is enabled for all modules, including modules with no CPU and Power Supplies. Only modules with a CPU should have this button enabled.
Workaround: No workaround is currently available
•
Symptom: When enable secret is being used by a device, changing the exec password in the EM has no affect on the device. The passwords in the EM will then not match the ones on the device and the EM will not be able to manage the device.
Conditions: The problem occurs when the user configures the router to use enable secret within IOS, setting the password to match in the EM. When the user tries to change the passwords through the EM the problem occurs.
Workaround: In the Management Information window, set the value of "Exec Password" and "Confirm Exec Password" to the enable secret password configured on the device and click the "Save Locally" button. This will allow the device to be managed. However, the secret password itself cannot be configured on the device through the EM.
To update the enable password on the device, set the enable secret passwords on the device using IOS and follow the workaround detailed above to change the passwords in the EM.
•
Symptom: Deploying a chassis with an incorrect template and then commissioning the chassis sometimes succeeds
Conditions: If the user attempts to deploy a chassis of one type with the template for another, the deployment will succeed (e.g., deploying a Cisco 3660 chassis using the Cisco 2650 template). When the chassis is commissioned, the commission will succeed, but some of the modules may be deployed in the wrong slots.
Workaround: Ensure that the type of the chassis you deploy matches the template that is being used in the Deployment Wizard.
•
Symptom: Cisco Access Router Manager may be installed without required Cisco EMF patches
Conditions: The Cisco Access Router Manager may be installed despite the absence of the required Cisco EMF patches. Neither warnings nor errors display.
Workaround: Ensure that all required Cisco EMF patches are installed on the system before installing the EM.
•
Symptom: Return of objects to the normal state after lostcomms is delayed
Conditions: When objects are in the lostcomms state, it may take more than ten minutes for those objects to return to the normal state after communications to those objects is reinstated.
Workaround: No workaround is currently available
•
Symptom: Module removal/insertion traps not mapped
Conditions: Map Viewer discards traps sent from the 3662 when removing and inserting modules. Rather than mapping this trap, it is ignored. The system waits for a polling period to pass to notice something has changed, then raises a much more generic alarm. When inserting the card back into the slot, another trap is sent which is also ignored. The system waits for the next polling period and raises a Module Commissioning Successful and Module Operational Status is Up alarms. If a user chooses to enable traps in the IOS dialogs, then EM should map the traps received and display them as they come in.
Workaround: No workaround is currently available
•
Symptom: Incorrect message regarding the number of objects missing from the Map Viewer application
Conditions: Following the first attempt to delete an object from a decommissioned chassis, the Map Viewer application displays a message in the status bar indicating the number of objects missing from the map. When subsequent deletions occur, the status message indicates the number of objects missing but provides a misleading number. The number of objects increases by the total of objects deleted rather than the number of objects deleted by the most current action.
Workaround: Refer to the chassis map to determine the correct number of missing objects.
Open Caveats in Release 1.1
This section describes known limitations that exist in the Cisco Access Router Manager, Release 1.1.
•
Symptom: Only 10 SPVcs are deployed at a time
Conditions: When attempting to deploy greater than 10 SPVCs on a chassis, only 10 are deployed.
Workaround:Deploy a maximum of 10 SPVCs in a single deployment.
•
Symptom: Loopback cannot be set to internal/external
Conditions: Attempts to set the loopback state of an ethernet interface to 'external' or 'internal' in the 'Configuration' page/tab of 'Ethernet Interface Configuration' dialog fail.
Workaround: Use CLI to configure the loopback state as follows:
Router(config-if)#loopback ?driver Loopback at the transceiver levelmac Loopback at the MAC controller level•
Symptom: Deployment and commissioning of chassis with wrong sysoid & class is allowed
Conditions: If the user attempts to deploy a chassis of one type with the template for another, the deployment will succeed. e.g. deploying a 12008 chassis using the template for the 12016. When the chassis is commissioned, the commission will succeed, but some of the modules may be deployed in the wrong slots.
Workaround: Ensure that the type of the chassis to deploy matches the template that is being used to deploy the chassis.
•
Symptom: ATM sync not allowed for multi-chassis when some non-managed
Conditions: Upload action fails if one or more chassis among the selected group of chassis are in Unmanaged State.
Workaround: Choose the chassis that is in Managed State for Connection Upload.
•
Symptom: Chassis configuration dialog fails to come up during soak.
Conditions: When the system is under a high amount of stress, the Chassis configuration dialog may fail to open. This problem occurs when the system is under extreme load, such as a full network outage. Even under severe stress conditions the occurrence of this issue is rare.
Workaround: Wait until the system is under less load before opening these dialogs.
•
Symptom: QoS Profile losing applying can not be removed
Conditions: QoS Profile which is uploaded from the device can not be deleted from CEMF. The Action-Report shows Failure because the QoS Profile is still being applied to some connection.
Workaround: No workaround is currently available
•
Symptom: Upload Status shows wrong infor when doing uploading
Conditions: When a user carries out an ATM Connection Upload manually (forced), the Upload Status panel shows the result. This result does not show the correct Values for Actual Connections, Connection Under Same Port and Unmanaged Interface(s).
Workaround: Telnet to the device through "Initiate Telnet Service" from the "Technology Specific Tools" menu. Issue command "show atm vc" from Exec Mode. User has to count the Actual Connections, Connection Under Same Port, and Unmanaged Interface(s) manually.
•
Symptom: QoS Profile uploading fails when index is the same
Conditions: ATM Connection upload does not upload certain QoS profiles and connections associated with those profiles.
Workaround: In Element Manager, decommission and delete all the associated connections for the profile under consideration. Delete the QoS profile and the associated connections. Now on upload, modified QoS profile and related connections will be successfully uploaded from the device to the Element Manager.
•
Symptom: ATM Connection Management- Can save different configuration to a connection (normal state)
Conditions: VPI/VCI values can be modified for a normal-state connection-object by carrying out a copy/paste operation on the page-configuration functions.
Workaround: No workaround is currently available
•
Symptom: ATM Connection Management: Can modify VPI/VCI of connection in normal state
Symptom: Modifying the VPI and VCI parameters of normal PVC/SPVC connections succeeds. However the correct behaviour is that it should not be possible to modify such values for PVC/SPVC connections when they are in the normal state. If a user multi-selects a number of PVCs/SPVCs while one or more of these connections is in the decommissioned state, then it is possible to amend the VPI and/or VCI parameters of those PVCs/SPVCs that are in the normal state. Once these parameters are changed then the user cannot disconnect these connections.
Workaround: The normal PVC/SPVC connections with the changed VPI and VCI parameters can be removed using the following steps.
–
–
•
Symptom: Cannot save POS Configuration dialog
Conditions: Unable to save on the POS Configuration dialog without entering a threshold for every alarm type.
Workaround: Enter a threshold for every alarm type, regardless of whether the button is selected.
•
Symptom: Disable the unsupported attributes in ATM Interface Configuration Profile
Conditions: The attributes that are disabled in the ATM Interface Configuration dialog are unsupported. When the Profile dialog is opened, the attributes that are disabled in the Configuration dialog are not greyed out in the profile dialog, appearing to be supported. Values can be entered for the unsupported attributes.
Workaround: Only fill in the supported attributes for the ATM Interface Configuration Profile.
•
Symptom: DS3/E3 Interface Status: disable traffic lights
Conditions: On the DS3/E3 Interface dialog, the traffic light icon is not disabled when there is no interface selected on the dialog and when the chassis is in decommissioned or lostcomms.
Workaround: Ignore the value indicated by the traffic light icon under the above circumstances.
•
Symptom: Can not apply CAR Policy with MAC type access list
Conditions: Applying CAR Policy having MAC type access list to an ATM interface fails.
Workaround: CAR Policy can be configured in the device using IOS CLI through "Initiate Telnet Service" from the "Technology Specific Tools" menu. An example configuration of CAR policy with MAC type access-list is as follows.
ems7507a#config tems7505a(config)#access-list 701 permit 0000.0000.0001ems7505a(config)#int atm2/1/0ems7505a(config-if)#rate-limit input access-group 701 8000 8000 8000 conform-action continue exceed-action continue•
Symptom: CAR Policy Apply: Average Transmission Rate not saved on device
Conditions: In the CAR Policy Apply dialog, the value of Average Transmission Rate is not getting saved on the device.
Workaround: No workaround is currently available
•
Symptom: Default QoS profile data not showing in QoS Management dialog
Conditions: Default QoS profile values are not displayed in QoS Profile Management dialog. When a VCL is deployed using the default QoS profile, it is deployed successfully. However, when viewing this newly created VCL using the QoS Profile Management dialog it would appear that all values are blank. The default values for the VCL are not displayed, although they have been correctly set in the device.
Workaround: User needs to telnet to the device and look up the values manually via CLI.
•
Symptom: Wrong error message after applying CAR on controllers
Conditions: For devices, while applying a CAR Policy to a E1/T1/E3/T3 port, the error message generated is misleading. This error message is misleading because it implies that CAR Policy is supported on these ports. Since the CAR Policy is not supported on these ports in devices, the correct behaviour would be some error message stating that CAR is not supported.
Workaround: No workaround is currently available
•
Symptom: Current CAR policy is not updated in CAR Policy Status dialog
Conditions: The "Current CAR Policy" box in the CAR Policy Status Dialog is not getting updated, even if the dynamic updates are enabled.
Workaround: Close the currently open CAR Policy Status dialog. Open a new CAR Policy Status dialog and the updates will be correctly displayed.
•
Symptom: VCL Configuration dialog Layer 3 Configuration tab not working
Conditions: Under the Layer-3 configuration tab of the VCL Configuration Dialog, if the first action a user takes is to set a value for the Encapsulation parameter then it is not then possible to set a value for AAL5Encapsulation. However, if AAL5Encapsulation is set first then it is possible to set a value for Encapsulation.
Workaround: Set AAL5Encapsulation parameter first before the Encapsulation parameter.
•
Symptom: No error message in SVC Configuration dialog when decommissioning SVC
Conditions: Under certain circumstances when saving NSAP address and Sub Interface numbers using the SVC Configuration dialog, the values are not saved nor is there an appropriate error message to the user.
Workaround: The Sub Interface Number field should not be left blank. If no value is to be applied then the field should be left at its default value of "Not-applicable".
•
Symptom: Environmental alarms with a state of 6 (notFunctioning) are not mapped within Cisco EMF.
Conditions: Deploy and commission a chassis, then send a ciscoEnvMonVoltageNotification with EnvMonVoltageState = 6 (notFunctioning). An alarm is not created in Cisco EMF as expected. This applies to voltage, temperature, fan, and power supply alarms. All other alarms are created as expected.
Workaround: No workaround is currently available
•
Symptom: Chassis type is always no label
Conditions: The "Type" attribute in the General Tab of the Chassis Inventory window is always "no label". This occurs even when the MIB has a valid value.
vWorkaround: No workaround is currently available
•
Symptom: Remove all unsupported attributes from Performance Manager
Conditions: Some attributes in ATM Interface Performance dialog may not be populated.
Workaround: No workaround is currently available
•
Symptom: No label for module type even when there is a value
Conditions: The type field is "No Label" for some modules in the Module Inventory window. This occurs even when the MIB has a value. If the MIB has a value, it should be mapped to a value.
Workaround: No workaround is currently available
•
Symptom: No generic performance data for the NM-1CE1U E1 interface
Conditions: Every field in the Generic Interface Performance dialog for NM-1CE1U module is blank.
Workaround: No workaround is currently available
•
Symptom: High capacity performance attributes are no-value or 0-value
Conditions: The HC performance attributes are not populated (for the 3700 series chassis) or populated as 0 (for the 2621XM chassis). The corresponding values are listed as N/A in the MIB.
Workaround: No workaround is currently available
•
Symptom: Paste Configuration always fails in Syslog Messages dialog
Conditions: When you paste a configuration on the Syslog Messages table, an error is reported even though everything pastes correctly. This error should not be reported.
Workaround: No workaround is currently available
•
Symptom: Module not discovered after CEMF restore
Conditions: Take a backup of the dataload in CEMF (i.e. using 'cemf backup' command), Stop CEMF, insert a module in one of the chassis of dataload, start CEMF, do a dataload restore(i.e. using 'cemf restore' command). The module that was inserted into the chassis is not discovered.
Workaround: No workaround is currently available
•
Symptom: Lostcomms device keeps serial interface in performance logging after upgrade
Conditions: While a chassis was in the performance logging state, the chassis was take down to lostcomms. Then the upgrade procedure was performed. After the upgrade, the chassis was still in lostcomms, but the serial interface went back into perf logging state. The chassis was still unreachable. After bringing the chassis back up, everything went into perf logging state. Bringing it down again put the serial interface in lostcomms state only for a moment; it then went back into perf logging state, while the rest of the chassis remained in lostcomms.
Workaround: No workaround is currently available
•
Symptom: NM-4T1-IMA ATM interface goes into error state after upgrade
Conditions: Before the upgrade procedure was performed, an NM-4T1-IMA card (4 ATM ports) was installed on each chassis. Some devices were in the lostcomms state, some in perf logging, and some in the normal state. After the upgrade, the first ATM interface on the module (ATM 3-0) for each chassis went into the errored state, while the remaining three interfaces went into their expected states (perf logging, lostcomms, or normal.)
Workaround: Decommission and recommission the devices.
•
Symptom: Chassis inventory dialog has missing fields
Conditions: On the General tab, the "Type" field is "no label" when there is a proper value in the MIB. Also, when the chassis is unreachable, the fields on the General tab say "Error." However, when the SNMP community strings are not the default of public/private, the fields are blank. In both cases, the chassis is in the lostcomms state. The dialog should be consistent in both these instances.
Workaround: No workaround is currently available
•
Symptom: Problems with Generic Interface Configuration dialog
Conditions: The Alias attribute is not displayed for T1 after saving the configuration. Also, "Testing" is not a valid option for "Admin Status".
Workaround: No workaround is currently available
•
Symptom: Command and Syslog dialog behave inconsistently.
Conditions: When a router is not reachable (i.e. primary interface is shut down), the Command Log and SysLog dialogs show "ERROR" in the Event History Details area. However, when the SNMP community strings are incorrect, these fields are just blank.
Workaround: No workaround is currently available
•
Symptom: Ethernet Interface Performance collision stats frame has no values.
Conditions: The collision Statistics frame of the Ethernet Performance dialog has no values in it. This table should be grayed out if not supported.
Workaround: No workaround is currently available
•
Symptom: Voice Group creation errors not presented in action report
Conditions: Action report does not provide the command-line failure information when a voice group creation fails.
Workaround: No workaround is currently available
•
Symptom: 12k coresident install changes help for other EMs
Conditions: When more than one Element Manager is installed on a CEMF system, invoking help for a dialog brings up to the help page that was installed by the last installed Element Manager.
Workaround: No workaround is currently available
•
Symptom: IP Multicast Fast Switching can be set and get in IP configuration
Conditions: For a device, the value of IP Multicast Fast Switching field in the IP Configuration dialog is not being retrieved correctly from the device.
Workaround: No workaround is currently available
•
Symptom: objectTypeFaileParser Fails
Conditions: CEMF fails to start after the uninstallation of the EM or after resetting the database when multiple EMs are installed.
Workaround: After installing the EMs, ensure that ENTITY-MIB provided is available in the <CEMFROOT>/config/mib directory.
•
Symptom: No action report for commission failure when quick start is used
Conditions: Failure of chassis commissioning due to wrong SNMP community strings is not reported through error message to the user.
Workaround: No workaround is currently available
•
Symptom: Power Supply in decommissioned state while chassis in normal status
Conditions: Power supply is in decommissioned state while the chassis is in normal state.
Workaround: Commission the power supply manually.
•
Symptom: Channelized T3 interface stuck on discovery state
Conditions: When a device having Channelized T3 Port Adapter is commissioned, the interfaces under the port adapter are getting stuck in discovery state. Please note that management of channelised interfaces is not supported.
Workaround: No workaround is currently available
•
Symptom: 26-36 EM should provide NEI related EM-specific files
Conditions: NEI is an event-forwarding tool in CEMF that supports Fault Entity Type information. It should provide four classes of information: NE, Chassis, FRU, and Ports.
Workaround: No workaround is currently available
•
Symptom: Upgrade script is too limited in scope for future patch releases
Conditions: The upgrade script scans the system and lets the user know what is needed for the upgrade. It states patch 6 is needed. It should be clear that this is a minimum requirement and later patches are acceptable. The script then gives a list of installation procedures to choose from and recommends option six for single EM systems. When choosing option 6 for automated install, the script asks for the location of patch 6. This should be left open to the user. It should not specify patch 6, but just ask for a patch location. It should also allow the user to select more than one patch to install as part of the upgrade. Currenly, the user is only given an option to install one patch.
Workaround: No workaround is currently available
•
Symptom: Module Inventory Type field not populated
Conditions: The "Type" field on the Module Inventory dialog says "No Label" for some of the modules. The dialog needs to properly pull this value from the mib.
Workaround: No workaround is currently available
•
Symptom: Issues with OIR alarms when module is in performance polling
Conditions: Module major outstanding alarms are not getting cleared when module object is in performance polling state.
Workaround: 1. Stop and start the performance polling on the module to clear the outstanding alarm. 2. Manually clear the outstanding major alarm.
•
Symptom: Issue when module going to discoverylostcomms state
Conditions: When a module goes to discoverylostcomms state for a Chassis which is already commissioned, no alarms are generated. When a module goes to discoverylostcomms state during the process of commissioning of a Chassis, a major alarm with description "Deployed module does not match actual module" is raised against the module.
Workaround: No workaround is currently available
•
Symptom: Clear corelation is not working for link up/down alarms
Conditions: Interface level link down alarms are not cleared when the device does not define the CEMF server as a trap server. If an interface is brought down, the trap server is removed, and then the interface comes back up, no event is received to clear the event. The polling in CEMF detects that the interface is up but the event is not cleared.
Workaround: Clear the alarms manually.
•
Symptom: Save icon on ATM Interface Configuration Profile dialog not active
Conditions: In the ATM Interface Configuration Profile dialog, when there are multiple profiles, some attributes fail to save for the second profile in the list.
Workaround: No workaround is currently available
•
Symptom: NSAP should not be there for SVC with CEMF endpoint deploy template
Conditions: The deployment template for SVC with CEMF endpoint used for SVC Deployment asks for the NSAP Address field to be filled in by the user. The NSAP address can be calculated automatically from the Destination Port but CEMF does not automatically do this.
Workaround: No workaround is currently available
•
Symptom: EMS appears to lose alarms
Conditions: For certain alarm types, the event browser opened against a chassis only shows the most current alarm raised in the working event view. This gives the impression that only one alarm has been raised of a given type, when there have been many alarms raised of that type on the chassis.
Workaround: The alarms can be viewed by using the history function of the Event Browser to view all of the alarms raised on the chassis.
Related Documentation
The following Cisco EMF and Cisco Access Router Manager documentation is available as additional resource materials.
Cisco EMF Documentation
The following documents are available for the Cisco EMF:
•
Cisco Element Manager November 2002 Upgrade•
Version 3.2 Service Pack 4 (Cisco Element Manager November 2002 Upgrade)•
(Cisco Element Manager November 2002 Upgrade)•
Cisco Element Manager November 2002 Upgradehttp://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/prod_release_note09186a0080128a9c.html
Cisco Access Router Manager Documentation
In addition to these release notes, the following documents are available for the Cisco Access Router Manager, Release 1.1:
•
•
Obtaining Documentation
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco web sites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have 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.
Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:
http://www.cisco.com/go/subscription
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top 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: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
To obtain customized information and service, you can self-register on Cisco.com at this URL:
Technical Assistance Center
The Cisco 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 website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•
•
•
•
Cisco TAC Website
You can use the Cisco TAC website 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 website, 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 website. Some services on the Cisco TAC website require 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://tools.cisco.com/RPF/register/register.do
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
http://www.cisco.com/en/US/support/index.html
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.
Cisco TAC Escalation Center
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.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•
•
http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html
•
http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html
•
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Posted: Wed Dec 8 13:39:03 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
