|
|
Table Of Contents
Release Notes for Cisco 10000 Series Manager Release 1.0
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco 10000 Series Manager Release 1.0
Contents
This document is divided into the following sections:
•
Caveats
•
•
Introduction
Cisco 10000 Series Manager uses the Cisco Element Management Framework (Cisco EMF), which provides simplified element management of day-to-day tasks, including Fault, Configuration, Accounting, Performance, and Security (FCAPS) management. The Cisco 10000 Series Manager application provides easy navigation to the FCAPS functionality, offering concentrated management for each main element at multiple object levels.
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 10000 Series Manager only with Cisco 10000 Series routers using Cisco IOS Releases 12.0(24)S1 for leased line or 12.2(20030205:091427) for broadband. Other IOS versions may be used; however, some functionality may not be compatible with other IOS software.
Cisco 10000 Series Manager servers and clients operate with the following software:
•
•
Note
License Requirements
The EM uses Cisco EMF, which requires a license key to operate.
Note
Hardware Supported
Cisco 10000 Series Manager supports the following Cisco routers and modules:
•
•
The following table includes each module supported by Cisco 10000 Series Manager. For descriptions of each router and module, refer to the Cisco 10000 Series Manager User Guide.
Table 1 Modules Supported
Installation Notes
The Cisco 10000 Series Manager Installation Guide provides information to install, configure, and uninstall the Cisco 10000 Series Manager product. For any specific installation issues in this software release, see the "Caveats" section of this document.
Caveats
The following caveats exist in Cisco 10000 Series Manager Release 1.0. Generally, caveats include unexpected behaviors or defects in the software release. This document addresses a subset of 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).
•
Symptom: The values within the Power Supply tab on the Chassis Status dialog are not populating even when there is a power supply on the device.
Conditions: Deploy and commission a 10KM router that contains a power supply module. Launch the Chassis Status dialog against the chassis that has been deployed. Select the Power Supply tab. None of the values in this tab are populated, although the Power supply module is present.
Workaround: No workaround is currently available
•
Symptom: The values within the Fan tab on the Chassis Status dialog are not populating even when there is a fan present on the device.
Conditions: Deploy and commission a 10KM router that contains a fan. Launch the Chassis Status dialog against the chassis that has been deployed. Select the Fan tab. None of the values in this tab are populated, although the fan is present.
Workaround: No workaround is currently available
•
Symptom: Backup/restore: chassis stuck in discovery
Conditions: Cisco EMF backup and restore may show devices in a normal state after restoring, when they did not start in the normal state before backup. 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 to move the chassis from the discovery state into a normal state.
•
Symptom: Failure to map alarm to object for module commissioning
Conditions: The object name for some chassis commission alarms may not be mapped in the event browser.
Workaround: Close the Event Browser and relaunch the application.
•
Symptom: Manual Deployment of a chassis using Quickstart wizard does not check for the correctness of IOS CLI username/password/exec password that are provided to the wizard.
Conditions: Use Quickstart Wizard to manual deploy a chassis. Specify an incorrect combination of username/password/exec password. Complete all other steps to finish deployment. No error message given regarding the incorrect username/password/exec password, when an error message might be expected.
Workaround: Confirm that the IOS username/password/exec password are correct using the IOS password dialog and change accordingly.
•
Symptom: Syslog (Error Log) incorrect field/attribute label
Conditions: In Syslog (Error Log) dialog, there is a field labeled Min. Syslog Severity. The value that is displayed in the field does not match the label. The value, from the MIB, is Max Syslog Severity.
Workaround: No workaround is currently available
•
Symptom: Chassis Configuration dialog for 10k polls RHINO MIB
Conditions: In the Chassis Configuration dialog, on the Configuration tab, the "Action", "Clock" and "Power Supply" panels are greyed out for the 10008 device.
Workaround: No workaround is currently available
•
Symptom: The CPU attributes on the Module Performance dialog do not update correctly when changing from one module to another.
Conditions: Open the Module Performance dialog against a module that has a CPU. The attributes CPU busy, 1min, and 5min are populated correctly. If you then change to another module within the dialog that does not have a CPU, and therefore the attributes are not supported, the values for these attributes still show the previous version. Additionally, the button to start perf logging is enabled for modules that do not have a CPU.
Workaround: Refreshing the dialog will update the values displayed.
•
Symptom: Chassis details attributes show blank for entity chassis
Conditions: In the Chassis Inventory dialog, General tab, the following Chassis Details attributes are not displayed on a 10005 device: Number of Slots, Environmental Monitor Type, and Backplane Type.
Workaround: No workaround is currently available
•
Symptom: Unable to change the IOS Enable Password via the EMS.
Conditions: The IOS Enable password can be created via the EMS with a space in it. If this is done, you will no longer be able to set the password via the EMS.
Workaround: Don't create the password with a space in it. Or if unable to set via the EMS - telnet to the device and set via IOS CLI.
•
Symptom: Windows do not return errors when unreachable
Conditions: The values of all status windows do not return an error when the chassis is unreachable; they are just blank.
Workaround: No workaround is currently available
•
Symptom: Cisco EMF Action Report after a CPU/PRE switchover does not provide information
Conditions: The Cisco EMF Action Report is incomplete and doesn't provide information of the action invoked (Force- failover).
Workaround: No workaround is currently available
•
Symptom: Auto-sync running configuration unable to update on Redundancy dialog
Conditions: The "auto-sync running config" attribute field is not updated after a change at the command line interface (CLI) level.
Workaround: No workaround is currently available
•
Symptom: Mismatched chassis is discovered
Conditions: If you deploy a 10008 router with the IP address of a 10005, the chassis moves into the mismatch state. However, it then discovers all the modules and moves into normal state before moving back into mismatch.
Workaround: No workaround is currently available
•
Symptom: Certain ATM Status fields should not be grayed out
Conditions: The "Number of VPCs", "Admin Address", and "ATM Address Type" fields are grayed out on the ATM Status dialog. These fields are supported and should not be grayed out.
Workaround: No workaround is currently available
•
Symptom: Deploying a chassis with an incorrect template and commissioning of 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 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: Action Reports are not displayed using the Quick Start deployment method
Conditions: When using the quick start method of deployment, an Action Report showing whether or not the deployment is successful is not displayed.
Workaround: No workaround is currently available
•
Symptom: Action Report incorrectly states success
Conditions: After selecting to commission a previously commissioned chassis, the system incorrectly displays an Action Report stating that the commissioning was successful. The process should have failed as the chassis was already commissioned.
Workaround: No workaround is currently available
•
Symptom: When the system is under a high amount of stress, the Chassis configuration dialog may fail to open.
Conditions: 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: 10K network outage does not meet PRD requirements
Conditions: 10K PRD and Test Plan requires that the recovery of network outage occur in 10 minutes, but it actually took around 12 minutes or more.
Workaround: No workaround is currently available
•
Symptom: Attempting to delete a module when it is in a state that prevents it from being deleted gives a non-descriptive error message.
Conditions: When attempting to delete a module when it is in one of the following states; discoverylostcomms, perfPolling, Normal, Mismatch, the following error is given. ---- Deletion Failed. Deployment/Deletion failed: No reason was given. ---- This does not indicate the deletion failed because it is in a state that does not allow deletion and should be in the decommissioned state.
Workaround: To delete the module, first decommission using the Module Configuration dialog.
•
Symptom: When decommissioning a module, the action report states that the module fails to decommission, although the module moves into the decommissioned state.
Conditions: Open the Module Configuration dialog and select a module that is in the normal state. Press the Decommission button. The module moves into the decommissioned state, as can be seen in the map viewer, but the action report fails to appear. After 5 minutes the action report appears and states that the decommission was unsuccessful.
Workaround: Ignore the Action report and check the status of the module using the map viewer and module configuration dialogs.
•
Symptom: Removing a module from a chassis that is decommissioned causes the module to change to Mismatched.
Conditions: Physically removing a module from a decommissioned device causes the module to go into mismatch. When the module is reinserted into the device it goes into normal state.
Workaround: Decommission the re-inserted module using the Module Configuration dialog.
•
Symptom: Some fields in the Module Status dialog contain chassis values and not from the module.
Conditions: The following fields in the Module Status dialog show values that are the same as those in Chassis Fault Management dialog: Up Time, Last Authentication Failure Address, Last Restart Reason, and Cisco Contact Details. The 'Free Memory' field is not in Chassis Fault Management dialog, but the value displayed is also for the chassis not for the module.
Workaround: No workaround is currently available
•
Symptom: Preprovisioned module stays in mismatched state after replacing with the correct module.
Conditions: Deploy and commission a 10K chassis with 2 empty slots. Preprovision both of the slots to contain 2 different modules. Insert the wrong module into one of the slots. The module will correctly go to mismatched. When the module is then removed the module stays in mismatched instead of returning to preprovisioned.
Workaround: Decommission and recommission the module to return it to the preprovisioned state.
•
Symptom: Unable to save on the POS Configuration dialog, without entering a threshold for every alarm type.
Conditions: On the POS configuration dialog, opened against a chassis with a POS module, deselect one of the "Alarm Reporting and Threshold" buttons and clear the associated field. The save fails.
Workaround: Enter a threshold for every alarm type, regardless of whether the button is selected.
•
Symptom: Unsupported attributes on ATM Profile dialog should be grayed out.
Conditions: Currently, attributes not supported by the EM are activated on the ATM Profile dialog. Unsupported fields should be grayed out to lessen confusion for the user.
Workaround: No workaround is currently available
•
Symptom: Syslog Messages dialog: Min Syslog Severity should be Max Syslog
Conditions: On the Syslog Message dialog in the SysLog Message Details section, the Min. SysLog Severity label should read Max. SysLog Severity.
Workaround: No workaround is currently available
•
Symptom: Link up/down traps appear in event browser when the traps have been disabled in the Generic Interface Configuration dialog.
Conditions: Set the Link Up/Down Trap status to disable using the Generic Interface Configuration dialog. Shutdown the interface on device using "shutdown" command on the device. The following Link down trap appears on the Event Browser: Interface: POS7/0/0 Down, Operational status: down, Administrative Status: up, Reason: down A link up is also displayed when performing a "no shutdown" command on the device.
Workaround: Log in to IOS on the device and disable the Link up/Link down traps using the IOS commands.
•
Symptom: After PRE switchover, the auto-sync window is active for LL IOS
Conditions: After a CPU switchover, the Auto-Sync Option window becomes active even though is not supported for the lease line IOS. However, once the standby PRE becomes Normal, the options are grayed out as expected.
Workaround: No workaround is currently available
•
Symptom: User must refresh the Redundancy dialog after an action
Conditions: The user must click on the refresh icon to see updated information and reactivate the Redundancy dialog after an action is invoked. The dialog should refresh automatically after an action.
Workaround: No workaround is currently available
•
Symptom: Unsupported attributes in the ATM Interface Configuration Profile dialog are not greyed out.
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: The traffic light icon is not disabled on the DS3/E3 Interface dialog under some circumstances.
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 lights icon under the above circumstances.
•
Symptom: Ethernet Interface dialog - invalid loopback options for PRE
Conditions: In the Ethernet Interface Configuration dialog, select a fast ethernet interface of PRE; the loopback options Internal/External are not valid for this type of interface. Gray out invalid options on PRE ethernet interface objects.
Workaround: No workaround is currently available
•
Symptom: Commissioning is allowed on chassis in sync or normal state
Conditions: In the Chassis Configuration dialog, you are currently allowed to commission a chassis that is in the normal or sync state. When a chassis is in normal/sync state, no commission action should be performed.
Workaround: No workaround is currently available
•
Symptom: Cannot commission multi-selected modules
Conditions: From the Module Configuration dialog, multi-select modules and click on decommission. Verify all the selected modules go to decommissioned state. Multi-select the same modules that are in decommissioned state and click on commission. None of the modules move to discovery state, they all remain decommissioned.
Workaround: No workaround is currently available
•
Symptom: Wrong action report on Management Information dialog
Conditions: Used auto-discovery to deploy a chassis and commission it without editing the default SNMP community strings, which are 'public' for both RO and RW. In Management Information dialog, changed some field values, e.g. System Name, and got an error. Checked the SNMP community string values on the device. The SNMP RW community string value in the action report is wrong.
Workaround: No workaround is currently available
•
Symptom: Redundancy dialog broken on 12.0(24.4)S1
Conditions: The output of "show redundancy" has changed. Therefore, the perl scripts that populate the dialog must change to pull out the appropriate information.
Workaround: No workaround is currently available
•
Symptom: Issues on power supply
Conditions: Power Supply is discovered in the current build and it showed up in all module-related dialogs or interface dialogs that contain a module list. In the Module Performance dialog, performance polling can be started/stopped on a power supply object. In the Chassis Fault Management dialog, the power supply tab is available, but in the 10k functional spec it is supposed to be grayed out.
Workaround: No workaround is currently available
•
Symptom: Redundancy Dialog: Sync Configuration on Failover field is useless
Conditions: In the Redundancy dialog, the 'Synchronize Configuration on Failover' field has two options - yes or no. No matter what value is set, the running configuration will always be synchronized between the primary and secondary PRE. From a device, when running the forced failover, running configuration will always be synchronized. There is no option to choose whether to synchronize configuration or not.
Workaround: No workaround is currently available
•
Symptom: Redundancy dialog: auto-sync options become active for the LL IOS
Conditions: The auto-sync options become available for the LL IOS and for RPR-Plus Mode. After after setting the redundancy mode to RPR-Plus and forcing a pre-switchover, the auto-sync options became permanently active. LL IOS does not support auto-sync options.
Workaround: No workaround is currently available
•
Symptom: % returned in an information message from IOS
Conditions: This refers to the Auto-Configuration and Address Registration parameters in the ATM Configuration dialog. It happens when you try to enable/disable these fields. Per the IOS guideline, '%' should be there only if it is an error.
Workaround: No workaround is currently available
•
Symptom: Unable to toggle the redundancy mode from Redundancy dialog
Conditions: After changing the redundancy mode, the user can't switch back to the original mode due to the grayed out "Change Mode" button. For the LL IOS, the user should be able to set the redundancy mode for either SSO or RPRplus.
Workaround: No workaround is currently available
•
Symptom: DS3/E3 Configuration dialog should provide set functionality
Conditions: In DS3/E3 Configuration dialog, there is no way to set any attribute.
Workaround: No workaround is currently available
•
Symptom: Attributes should be enabled DS3/E3 in Generic Interface Configuration dialog
Conditions: In the Generic Interface Configuration dialog, the left panel shows E3 interfaces/controllers. However, all of the attributes in the right panel, with the exception of the Alias attribute, are disabled. The applicable attributes should be enabled.
Workaround: Telnet to the router and login to an enable shell. Configure the terminal by entering
conf tat the command prompt. Enterinterface Serial <Slot/Subslot/Port>at the prompt, then enterdescription ?. Up to an 80 character description of the interface is displayed.•
Symptom: There are no values in the Bandwidth Utilization fields in the Generic Interface Performance dialog
Conditions: In the Generic Interface Performance dialog, Transmitted Bandwidth Utilization and Received Bandwidth Utilization fields don't have any information displayed. For interfaces that have traffic load, the dialog should display the actual percentage information on bandwidth utilization.
Workaround: No workaround is currently available
•
Symptom: One attribute value out of legal MIB value range for DSX Line Status attribute
Conditions: In the MIB file "RFC1407-MIB.mib", for dsx3LineStatus attribute, its legal range is 1-1023. However, the MIB browser shows many values for DS3/E3 controller/interfaces as 4094.
Workaround: No workaround is currently available
•
Symptom: ATM CM Upload Mgmt -> Upload Button should be disabled
Conditions: Currently, on the ATM CM -> Upload Management window, the Alarm Sync button is selectable for the 10000 series of devices. COM should disable this button based on the data found in the syncFramework directory, or even better, disable the menu item altogether so the user can't even get to that dialog if it isn't supported for that chassis type.
Workaround: No workaround is currently available
•
Symptom: In the ATM Interface Configuration Profile dialog, when there are multiple profiles, some attributes fail to save for the second profile in the list.
Conditions: Launch the ATM Interface Configuration Profile dialog and create at least two profiles. Set a value for the "UNI Signalling Version" and the Save icon lights up. Continue entering data for the following fields: Maximum VPCs, Maximum VCCs, Transmit Queue Limit, Number of VCs per VP, Clock Source, Auto-Configuration, Configuration and Address Resolution. Save the profile. Select the second profile, and enter the values specified above. The save button does not light up until the "Transmit Queue Limit" value is entered. Save the profile. If the dialog is closed and reopened and the second profile is selected, only the Transmit Queue Limit, Number of VCs per VP and Clock Source are set. All of the other values are blank.
Workaround: No workaround is currently available
•
Symptom: Interaction with IOS will fail when the prompts for User Name and Password are changed on the device.
Conditions: If the device has the prompts changed from the default "username" and "password" then CEMF will be unable to interact with the device to perform configuration changes and to get IOS values.
Workaround: Change the Username and Password prompts to "username" and "password".
•
Symptom: COM 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. This occurs on chassis where there is more than one of the following alarms raised: Sys Log alarms and Authentication failure alarms. These alarms are not lost as all alarms of this type are automatically cleared when a new alarm of the same type comes in.
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.
•
Symptom: Should not be able to access performance polling data from all modules
Conditions: The Module Performance window is accessible from any module even though performance data is only provided for certain module types (e.g., PRE). Data is not displayed in the fields on the Module Performance window when the performance polling feature is not supported for the selected module.
Workaround: Avoid launching or viewing the Module Performance window from modules for which the performance polling feature is not supported.
Related Documentation
While you can access all related documentation on the Cisco website, URLs which are available at the time of publication are noted in the following lists.
The following Cisco EMF documentation is available for reference:
•
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
In addition to this guide, the following Cisco 10000 Series Manager documentation is available for reference:
•
•
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 12:41:40 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
