The 5.0.20 software release supports the existing Cisco MGX 8220, and is recommended for mixed networks with MGX 8220 series switches and BPX 8600 series switches. Software Release 5.0.20 is based on 5.0.19.
Clarifications
None.
Special Installation/Upgrade Requirements
General
Please consult your Support Representative before performing any software upgrade.
Firmware Version Interoperability Requirements
The MGX 8220 ASC 5.0.20 bundle consists of the following firmware images:
Board Type
F/W Ver
F/W Image
Boot Version
Boot Image
ASC
5.0.20
asc_5.0.20.fw
ASC_BT_1.0.03
asc_ASC_BT_1.0.03.fw
AUSM8
5.0.18
ausm_8t1e1_5.0.18.fw
AU8_BT_1.0.02
ausm_8t1e1_AU8_BT_1.0.02.fw
FRSM8
5.0.18
frsm_8t1e1_5.0.18.fw
FR8_BT_1.0.02
frsm_8t1e1_FR8_BT_1.0.02.fw
FRSM HS1
5.0.17
frsm_hs1_5.0.17.fw
HS1_BT_1.0.02
frsm_hs1_HS1_BT_1.0.02.fw
IMATM8
5.0.17
imatm_5.0.17.fw
IMA_BT_1.0.02
imatm_IMA_BT_1.0.02.fw
CESM8
5.0.17
cesm_8t1e1_5.0.17.fw
CE8_BT_1.0.02
cesm_8t1e1_CE8_BT_1.0.02.fw
FRSM HS2
5.0.16
frsm_vhs_5.0.16.fw
VHS_BT_1.0.01
frsm_vhs_VHS_BT_1.0.01.fw
AUSM4
4.0.24
ausm_4.0.24.fw
BT_4.0.00
ausm_BT_4.0.00.fw
CESM4
4.0.20
cesm_4.0.20.fw
BT_4.0.01
cesm_BT_4.0.01.fw
FRSM4
4.0.26
frsm_4.0.26.fw
BT_4.0.00
frsm_BT_4.0.00.fw
Firmware Images' File Sizes
Board Type
F/W Image
Size (bytes)
Boot Image
Size (bytes)
ASC
asc_5.0.20.fw
1846548
asc_ASC_BT_1.0.03.fw
495176
AUSM8
ausm_8t1e1_5.0.18.fw
1126936
ausm_8t1e1_AU8_BT_1.0.02.fw
377836
FRSM8
frsm_8t1e1_5.0.18.fw
775716
frsm_8t1e1_FR8_BT_1.0.02.fw
297988
FRSM HS1
frsm_hs1_5.0.17.fw
694964
frsm_hs1_HS1_BT_1.0.02.fw
293052
IMATM8
imatm_5.0.17.fw
1117108
imatm_IMA_BT_1.0.02.fw
405800
CESM8
cesm_8t1e1_5.0.17.fw
651376
cesm_8t1e1_CE8_BT_1.0.02.fw
264592
FRSM HS2
frsm_vhs_5.0.16.fw
892084
frsm_vhs_VHS_BT_1.0.01.fw
467332
AUSM4
ausm_4.0.24.fw
755452
ausm_BT_4.0.00.fw
265288
CESM4
cesm_4.0.20.fw
625640
cesm_BT_4.0.01.fw
267212
FRSM4
frsm_4.0.26.fw
780060
frsm_BT_4.0.00.fw
264404
Shelf Controller Firmware Requirements
Version 5.0.20 requires one or two (for redundant operation) ASCs or ASC2s. If two Shelf Controllers are in place, they must both be at Version 5.0.20 (The active shelf controller will overwrite the firmware on the standby controller).
Both ASC and ASC2 Controller models should use ASC_BT_1.0.03 as their backup boot for proper operation.
Upgrade Considerations
Upgrades are only supported from Version 4.x. Shelves running 2.x and 3.x releases should be first upgraded to 4.x before upgrading to 5.x.
Smooth upgrade of AUSM-8P cards from releases 4.x to 5.0.1x is not supported. This was a design decision based on the fact that Forum compliant IMA and release 4.x (proprietary) IMA protocols have certain configuration parameters that do not have counterparts in the other protocol.
However, there is a minimal level of help for upgrade. The configuration and the connection database does not need to be re-initialized after an upgrade. Once the AUSM-8P firmware is upgraded and the AUSM-8P card is reset, the following will be true:
All of the IMA groups will still be present. Some configuration parameters in the IMA groups will be set to Forum-compliant default values. The administrator is advised to do a dspimagrp on each group and, if necessary, modify the parameters like Minimumnumber of links.
All of the connections that were present will be intact.
Please note that co-existing of release 4.x and release 5.0.1x AUSM-8P cards on the same shelf is not supported. This means that all AUSM-8P cards on a given shelf need to be upgraded at the same time.
For manual upgrades using the revup command from the CLI prompt, it should be taken care that the revision name is not longer than 20 characters otherwise it will fail to rename the file.
Additional Commands/Features
None.
Additional Deliverables
There are no additional deliverables required for Release 5.0.20.
Features Not Supported
Removed the RAS diagnostics support from ASC. (CSCdz14047)
The SELFTEST feature is available on all the 4 Port cards.
The SELFTEST feature is removed from following cards:
1. Modules running versions 2.X or 3.X are not supported as of Release 5.0.1x.
2. AUSM8 Proprietary IMA is no longer supported as of Release 5.0.1x. IMA ports must be converted to ATM Forum-compliant IMA.
Notes & Cautions
1. CESM-8T1 supports two kinds of models:
Model A: Supports Basic, SF and ESF connections on a structured port and basic connection on an unstructured port.
Model B: Supports Basic, SF, SF-MF, ESF and ESF-MF on a structured port and basic connection on an unstructured port.
2. How to distinguish Model B card from Model A card?
Use dspcd command, "Fab number" field contains the necessary information for Model B card.
3. Procedure for graceful replacement of Model B card with Model A card:
Step 1 Change all SF-MF connections on the line to SF connections using xcnfchan command.
Step 2 Change all ESF-MF connections on the line to ESF connections using xcnfchan command.
Step 3 Replace Model B card with Model A card.
4. Effect of ungraceful replacement of Model B card with Model A card:
Model A card does not support SF-MF and ESF-MF types of connections. All SF-MF and ESF-MF connections will automatically be changed to SF and ESF connections respectively. Though it does it automatically, it's "NOT advisable" to do so.
5. Procedure for replacing Model A card with Model B card:
Step 1 Replace Model A card with Model B card.
Step 2 On Model B card, if you want to change SF / ESF connections to SF-MF / ESF-MF connections on a particular line, use xcnfchan command.
Such change will take effect for all the other channels on that particular line, so that there's no conflict of CAS type of different connections on same line.
Note When CESM-8T1 Model B card is reset, when the card is in "BOOT" state, dspcds shows the card
type as "?". This is a cosmetic problem as the card comes up fine and when it does, the display is
correct.
6. ASC's with flash disk have a high probability of disk failure if a write to the disk is interrupted. Writes can be interrupted while resetting the card, removing the card and for other reasons. Therefore, it is absolutely necessary that the disk should be queisced or downed before doing any operation that could interrupt a disk write. The 5.0.1x ASC firmware does an automatic queisce or downdisk for most of the cases in which a write to the disk can be interrupted. There are some scenarios where the downdisk has to be manually executed and there are some cases where it is not possible to do downdisk.
The following table lists the various possible scenarios when a disk write can be interrupted.
Scenarios
Downdisk Operation
Comment
Power Outage
Cannot be done
Flash disk is exposed to corruption if a write was being done at the time of power outage.
Manual Power Shutdown
Manual
Flash disk can be protected by doing a downdisk from CLI on Active and Standby ASC before power shutdown. Use option 1 in downdisk CLI.
ASC Removal
Manual
Flash disk can be protected by performing a downdisk on the ASC to be pulled out.
Watchdog timer reset
Cannot be done
Flash disk is exposed to corruption if a write was being done at the time of ASC reset.
ASC reset from CLI resetcd
Automatic
The firmware automatically shuts the disk before resetting the ASC.
Shelf reset from CLI resetsys
Automatic
The firmware automatically shuts the disk on both Active and Standby before resetsys.
clrallcnf CLI
Automatic
The firmware automatically shuts the disk on both Active and Standby after clearing the configuration and before resetting.
Shelf reset by task failure
Automatic
The firmware automatically shuts the disk before resetting the ASC.
ASC reset due to GRAM exception
Automatic
The firmware automatically shuts the disk before resetting the ASC.
ASC reset due to SAR exception
Automatic
The firmware automatically shuts the disk before resetting the ASC.
ASC reset because unknown reason
Cannot be done
The flash disk is exposed to corruption if a write was being done at the time of ASC reset.
For information on downdisk CLI to perform manual queisce of the hard disk refer to the section on Additional Commands/Features.
Note These procedures when applied to all types of hard disks in the ASC increases their reliability and
hence it is highly recommended to follow these procedures for all the hard disks.
7. ASC/B cards with Calluna Hard disk are exposed to failures due to EMI when all of the following conditions are present:
Slot 5 is not empty
The service module in slot 5 does not have a backcard and
SRM-3T3 is employed to provide bulk mode distribution
The workaround for this problem is:
not to have a service module in slot 5 or
to use backcards for all the service modules on the shelf
This is problem is more frequent if the service module used in slot 5 is CESM8. The problem is also seen with FRSM4 in slot 5 but the frequency is considerably less. This problem is present in all previous AXIS firmware releases.
Limitations
The tstcon command cannot be used between IGX/BPX/MGX. This is because whenever a tstcon is used the SWSW tells the remote end to be in remote loopback. In this scenario SWSW in BPX cannot directly communicate to any service card in AXIS hence the loopback command is not sent to FRSM. Because of this limitation the tstcon payload will be processed as a normal data payload and hence will not loopback.
The cell bus fixes and enhancements have not been done for ASC, AUSM-4T1E1 and FRSM-4T1E1, these cards are still exposed the problem of cards going to Reserved/Empty/ Failed state when doing either clrallcnf or resetsys or resetcd. The card has to be reset to recover from this limitation.
The output of `dsplmistats' will not show the correct BPX status if a physical loopback is put on BNM. The BPX status is displayed as OK, which is not correct.
IMATM-8T1E1 does not work with UXM release abd and below.
Overloading the BNM interface with traffic causes the AUSM cards to fail.
Known Anomalies
Bug ID
Description
CSCdv78134
Add line with ln loop on FRSM-HS1 should not be allowed
CSCdy80418
cell loss and PDU error if SCR policing and CLP tagging changed from default
CSCdz27904
CBR rate higher than needed
CSCin55369
dspport throws Address load exception on configuring port bert
CSCec35635
addlnloop command fails on FRSM-HS1/B card
Additional Documentation
For FRSM-HS1 with V.35 backcard the maximum line rate depends on the number of lines and is as follows:
Number of Lines Enabled
Maximum Line Rate supported on each line
1
8 Mbps
2
8 Mbps (16 / 2)
3
5.3 Mbps (16 / 3)
4
4 Mbps (16 / 4)
Compatibility Notes
1. Release 5.0.20 requires CWM 9.2.03 or later.
2. Release 5.0.20 is compatible with SWSW 8.4, 9.1, 9.2, and 9.3. The Release 9.2 is still preferred, since rigorous compatibility testing was performed on this version.
3. DS3 BNM default parameters are as follows:
STI (No UNI or NNI)
LineNum:
1
LineType:
dsx3CbitParity
LineCoding:
dsx3B3ZS
LineLength:
LessThan225ft
LineOOFCriteria:
3 out of 8
LineAIScBitsCheck:
Check C-bits
LineLoopbackCommand:
NoLoop
LineRcvFEACValidation:
4 out of 5 FEAC codes
4. OC-3 BNM default parameters are as follows:
UNI
sonetLineType:
sonetSts3c
sonetLineLoopback:
NoLoop
sonetHCSmasking:
Enabled
sonetPayloadScramble:
Enabled
sonetFrameScramble:
Enabled
sonetMediumType:
sonet
sonetMediumLineCoding:
Other
sonetMediumLineType:
ShortSingleMode
sonetMediumCircuitIdentifier:
BNM-155 Trunk
Note Modules running versions 2.X or 3.X are not supported as of Release 5.x.
Bugs fixed in Release 5.0.20
Bug ID
Card
Description
CSCdv60960
ASC
dspalm returns error message Invalid Entry multiple times
CSCdz14047
ASC
Enabling RAS features make standby ASC unavailable
CSCec01504
ASC
SNMP does not reply. Incorrect isIPBroadcastAddress check and mistaken source
CSCdx08196
ASC
Connection modification fails with Mib ID error
CSCea60308
ASC
LMI status shows incorrect status of loop
CSCdz03658
ASC
Need to remove runslftstno from CLI
CSCea54190
AUSM-8T1E1
dspcd shows ATM PORT ALARM but dspport shows clear on AUSM
CSCea46955
FRSM-8T1E1
incorrect messages in the log when added link to the ima grp
CSCdz13650
BNM-155
Need to Initialize ITE SRAM in BNM for VPI 0 to 2
CSCdx84257
CESM-8T1E1
Remote Loops causing CRC errors on the CESM Unstructured Circuits
CSCea40731
CESM-8T1E1
CESMT1/E1 is not passing traffic after changing channel signaling
CSCdy83478
FRSM-4T1E1
Inconsistent help string for % util param
CSCea45904
FRSM-4T1E1
LOS or LOF Alarms was reported after FRSM-4T1 softswitch.
CSCdx23010
FRSM-8T1E1
Db corruption port missing on FRSM
CSCdz65198
FRSM-8T1E1
FRSM card sends Abit=0 alarm to CPE under unknown conditions
CSCeb19808
FRSM-8T1E1
ASC resets when too many messages come in
CSCec11476
FRSM-8T1E1
FRF.5 NIW Compliance wrt FR-SSCS DLCI value of 1022
CSCdw65416
FRSM-HS1
RDI from ATM network by SIW con is not mapped into a-bit on Frame Relay side
CSCdz03901
FRSM-HS1
FRSM-HS1&HS1/B reset if clrsarcnt is entered without parm
CSCdx52017
FRSM-VHS
dspalms incorrectly displays option X21 instead of x21
CSCeb55973
FRSM-VHS
FRSM-HS2 resets when mid-segment of connection is downed
CSCdx04691
ULIB
In the Statistic files, No. of Object has a negative value in it
CSCdw71288
FRSM-HS1
DLCI value change (Switch CLI) goes through but does not reflect the change
Bugs fixed in Release 5.0.19
Bug ID
Card
Description
CSCdv42148
ASC
ident command gives an error message on standby ASCs
CSCds29819
ASC
downdisk on active ASC2(BNM-T3) causes login failure & communication down
CSCdv34666
ASC
runslftstno 5,8 failed on ASC
CSCdv78354
ASC
Major alarm on standby ASC after switchcc
CSCdv34647
ASC
cnfslftst result cant be confirmed with dspslftsttbl
CSCdv42448
ASC
Redundancy table not restored during config restore.
CSCdt59397
ASC
Hardcoded snmp RO community.
CSCdw64075
ASC
SNMP req timing out to AUSM (provisioning XPVC/PVC from CWM)
CSCdw66368
ASC
ASC resets when there are too many log messages.
CSCdw31174
AUSM-4T1E1
Wrong Egress Service Rate value is returned via a Snmp GET
CSCdt80684
AUSM-8T1E1
AUSM Card reboots when doing dspports while in Mismatch state
CSCdw34118
AUSM-8T1E1
Dsploads in AUSMT1 does not display properly
CSCdv82044
AUSM-8T1E1
Wrong Egress Service Rate value is returned via a Snmp GET
CSCdw16662
AUSM-8T1E1
runslftstno 6 on standby card returns incorrect error message
CSCdw46529
AUSM-8T1E1
Port ILMI failure on card after deleting port
CSCdx03437
AUSM-8T1E1
Need support of ausmChanEgrSrvRate in TFTP upload of all AUSM cards
CSCdw39361
AUSM-8T1E1
Softswitch on axis causes remote abit failure on channels on far end
CSCdw53021
AUSM-8T1E1
Sequence Number of Cell become unsequenced suddenly
CSCdy18941
AUSM-8T1E1
Egress OAM cells on AUSM get delayed in case of max traffic on ima link
CSCdx10034
CESM-8T1E1
CESM-8t1e1 may fail when the axis shelf is power cycled
CSCdv83988
CESM-8T1E1
Log is getting error message Invalid msgType from ACRED 4
CSCdx09631
CESM-8T1E1
MIB for Back cards will not get updated for CESM-8t1e1
CSCdx36528
CESM-8T1E1
Incase of some of the line alarm (RcvAIS) etc., the port still remains active
CSCdx02796
CESM-8T1E1
Chan E1 CESM Dax conn, logs bit err on Bert when new cons added on line
CSCdv86967
CESM-8T1E1
CESM-8T1 cell lost for 24*64 kbps,CAS enable and partial full of 25 bytes
CSCdv34684
FRSM-4T1E1
cnfslftst can not use on standby FRSM-4T1
CSCdw50493
FRSM-8T1E1
ChanNumNextAvailable: wrong display on dspchans, dspcons
CSCdw52919
FRSM-8T1E1
runslftstno6/8 blanks out LED in FRSM-8t1e1 in PXM1-based MGX/axis
CSCdw38770
FRSM-8T1E1
RDI from ATM network by SIW con is not mapped into a-bit on Frame Relay
CSCdw94301
FRSM-8T1E1
MIB for Backcards will not get updated
CSCdx44060
FRSM-8T1E1
Line code Violation Errs incrementing constantly on FRSM lines
CSCdw51623
FRSM-8T1E1
FRSM shows chanNextAvail as 1015 after reset
CSCin05984
FRSM-8T1E1
xcnfchan on FRSM said string too long and reject the command
CSCdy29403
FRSM-VHS
No of objects to be changed to 1015 for channel stats on FRSM-HS2
CSCdv89610
FRSM-HS1
No alarm indication if cons in config are failed to be added after reset
CSCdv81905
FRSM-HS1
FRSM-HS1 card CLI display locks up
CSCdv05925
FRSM-HS1
Misleading log message when back card is missing
CSCdv81784
FRSM-HS1
Duplicate DLCIs in PRI file causes card reset repeatedly
CSCdx08431
ULIB
To prevent memory overwrite when all stats on FRSM is enabled
CSCin08967
BNM-155
clralm on sonet has problems
CSCdv61382
IMATM-8T1E1
Ima Fe Unavailable Seconds increment but no outage recognized.
Bugs fixed in Release 5.0.18
Bug ID
Description
CSCdw63646
An error can occur with management protocol processing. Please use the following URL for further information:
Problem of Alarm status of AXIS connected between BNM-155 and BXM-155
CSCdp07434
FRSM-HS1
Axis: Buffer overflow problem causes one way traffic
CSCdp87022
ASC
FallBack Switchcc does not switch back even if SRM port is in Alarm
CSCds32840
AUSM-8T1E1
Override CAC parameter cannot be enabled/disabled
CSCds34620
CESM-8T1E1
CESM ports are not seen in connection manager intermittent
CSCds36158
FRSM-8T1E1
frsm-8 lines go into alarm if runslftstno 7 is used under bulk distribution
CSCds45380
FRSM-8T1E1
Statistics collection on FRSM card showing disabled
CSCds54986
ASC
Unable to addred for all slots FRSM-8T1 by Invalid card type
CSCds71491
ASC
Incorrect backcard corrupted redundancy table
CSCdt30617
AUSM-8T1E1
dspcon command will show connection that does not exist
CSCdt40285
FRSM-8T1E1
Override CAC parameter cannot be enabled/disabled
CSCdt43435
AUSM-8T1E1
Secondary card doesn't take over in 1:N redundancy when Primary is pulled out
CSCdt48354
SRM-T1E1
SRM-3T3 inserted message logged when reset ASC(SRM-4T1E1).
CSCdt65537
AUSM-8T1E1
AUSM Card goes into Alarm after Deleting IMA groups
CSCdt70815
ASC
clralm accepts e3 option for ds3 lines and vice versa
CSCdt74630
CESM-8T1E1
Log is getting error messages 14 cmm 8171 Invalid Value: Invalid msg Type
CSCdt82296
ASC
Standby ASC stuck in Updating, Active Low on Buffers
CSCdt86483
AUSM-8T1E1
A typo in cnfimatst command.
CSCdt91224
ASC
dspalm -sonet shows extra lines
CSCdt94979
BNM-155
Line Statistical Alarm on BNM-155 can not be cleared in clralmcnt.
CSCdt97429
AUSM-4T1E1
Log is getting error messages 14 cmm 8171 Invalid Value: Invalid msg Type
CSCdt97435
CESM-4T1E1
Log is getting error messages 14 cmm 8171 Invalid Value: Invalid msg Type
CSCdt97740
ASC
dspln accepts extra parameters
CSCdu01707
ASC
CESM channel reports erroneous alarm on channel 272
CSCdu12985
AUSM-8T1E1
AUSM-8T1/E1 cards stuck in CardInit state during boot up
CSCdu31876
SRM-T1E1
Local Loopback didn't work on bert test with E configured clear
CSCdu40630
ASC
Modify on Clock Source in Physical Line Config(dsx3) on SRM3T3 gives error
CSCdu43559
AUSM-8T1E1
Ausm card is detecting shelf alarm and sending AIS cells to the port side.
CSCdu66788
ASC
Trap 50064: coreCardSwitchInProgress received w/ invalid varbind
CSCdu76885
FRSM-8T1E1
Missing portM32EgressQueueThresh support for Frsm-8t1e1
CSCdu76896
FRSM-4T1E1
Missing portM32EgressQueueThresh support for Frsm-4t1e1
CSCdu79152
FRSM-8T1E1
need AUSM-8T1E1 Style DS1 counters in FRSM-8T1E1
CSCdu82780
ASC
Trap 50065: coreCardSwitchBlocked received with different varbind.
CSCdu87342
CESM-8T1E1
Secondary card doesn't take over in 1:N redundancy when Primary is pulled out
CSCdu88880
CESM-8T1E1
Violation of R2.3.1.1 in CES-IS 2.0
CSCdv05921
FRSM-VHS
Misleading log message when back card is missing
CSCdv20088
CESM-8T1E1
display of dspcd should distinguish between modelA and modelB cards
CSCdv21357
FRSM-8T1E1
Alarms cleared after resetting card on FRSM-8E1[B
CSCdv37135
ASC
Putting a temporary change on ASC side to support CESM-8T1/B card
CSCdv53446
CESM-8T1E1
Swapping CESM/B and CESM/A card caused connection type mismatch.
CSCdv53811
CESM-8T1E1
UNABLE TO SNMPSET cesmChanConditionedSigCode TO A VALUE OTHER THAN 0
CSCdv54970
AUSM-8T1E1
Support stats collection for chan egress counters and some other counters
CSCdv57752
CESM-8T1E1
On configuring Bulk mode for CESM/B, dellink does not work properly
Hardware and Firmware Compatibility
The following table provides the compatibility matrix for the hardware revision with the firmware and boot code versions given in the matrix on Page 2.
Hardware Type
Hardware Revision
Image Type
ASC
AH, AJ, AK, AL, AM, AN, AP, AR
ASC
ASC/B
AN
ASC
ASC2
BA, BB, BC, BD, BE, BF
ASC
ASC2F
BA, BB, BC, BD, BE, BF
ASC
BNM-T3
AJ, BA, BB, BC, BD
ASC
BNM-T3/B
BE, BF
ASC
BNM-E3
AA, AB, AC
ASC
BNM-E3/B
AD, AE
ASC
BNM-155
AA, AB, AC, AD, AE, AF, AH
ASC
SRM-T1E1
AB, AC, BA, BB, BC
ASC
SRM-T1E1/B
BD
ASC
SRM-3T3
SRM-3T3/B
BA, BB, BC, BD, BE, BF
ASC
FRSM-4T1E1
AJ, BK, BL, BM, BN, BP, BQ, CA, CB, CC, CE
FRSM
FRSM-8T1E1
AA, AB, AC
FRSM-8T1E1
FRSM-HS1
AA, AB, AC, AD, AE, AH, AJ
FRSM-HS1
FRSM-HS1/B
AA
FRSM-HS1
FRSM-HS2
800-02909-03 A0
800-02909-04 A0
FRSM-HS2
CESM-4T1E1
AA, BA, BB, BC
CESM
AUSM-4T1E1
AA, AB, AC, BA, BB, BC, BD
AUSM
AUSM-8T1E1
AA, AB, AC, AD, AE, AF
AUSM-8T1E1
AUSM-8T1E1/B
AA
AUSM-8T1E1
IMATM-8T1E1
AA, AB, AC, AD, AE, AF, AG
IMATM8
IMATM-8T1E1/B
AA, AB, AC, AD, AE, AF
IMATM8
CESM-8T1E1
AA, AB, AC
CESM-8T1E1
Obtaining Documentation
The following sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following URL:
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:
Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems Attn: Document Resource Connection 170 West Tasman Drive San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to
Streamline business processes and improve productivity
Resolve technical issues with online support
Download and test software packages
Order Cisco learning materials and merchandise
Register for online skill assessment, training, and certification programs
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; 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 will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
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). In addition, please have available your service agreement number and your product serial number.
