|
|
The 5.0.17 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.17 is based on 5.0.16.
Please consult your Support Representative before performing any software upgrade.
The boot codes for CESM-8T1 and FRSM-HS1 cards need to be upgraded to their respective 1.0.02 versions. Refer to the Firmware Images' table.
The MGX 8220 ASC 5.0.17 bundle consists of the following firmware images:
 |
Note Starting from this release, the FRSM-HS1 Boot Image has the following change in nomenclature: Version: FH1_BT has been changed to HS1_BT. Consequently, the boot image will be called frsm_hs1_HS1_BT_1.0.02.fw. This boot firmware works for all HS1 card models on MGX 8220. |
Version 5.0.17 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.17 (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.
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:
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.
There are no additional deliverables required for Release 5.0.17.
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.
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 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 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.
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:
The workaround for this problem is:
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.
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.
Once the ASC-RAS cycle starts, it can't be stopped in middle. So even if `delrasdsk' is issued while the RAS diagnostic cycle is in progress, the RAS status will become disabled but the current cycle will proceed to completion.
While the RAS cycle is in Progress on a shelf with two ASCs and `delrasdsk' is issued on Active ASC, the Active ASC will immediately show the RAS Status as `Disabled' whereas the Standby ASC will reflect the change only when it is through with its RAS specific testing.
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.
clralm -sonet will not clear 15min alarms on the ASC.
For FRSM-HS1 with V.35 backcard the maximum line rate depends on the number of lines and is as follows:
1. Release 5.0.17 requires CWM 9.2.03 or later.
2. Release 5.0.17 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:
|
|
||||||||||||||||||
4. OC-3 BNM default parameters are as follows:
|
|
||||||||||||||||||||
|
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.
The following sections explain how to obtain documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following URL:
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
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.
Cisco documentation is available in the following ways:
http://www.cisco.com/cgi-bin/order/order_root.pl
http://www.cisco.com/go/subscription
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
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 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
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:
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
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:
http://www.cisco.com/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:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
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:
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). In addition, please have available your service agreement number and your product serial number.
Posted: Mon Feb 9 18:08:59 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.