|
|
Cisco documentation and additional literature are available in a CD-ROM package. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
The 4.1.12 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 4.1.12 is based on 4.1.11 and contains bug fixes.
None.
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 Firmware Images' table.
The MGX 8220,AXIS 4.1.12 bundle consists of the following firmware images:
| Board Type | F/W Ver | F/W Image | Boot Version | Boot Image |
ASC | 4.1.11 | asc_4.1.11.fw | ASC_BT_1.0.03 | asc_ASC_BT_1.0.03.fw |
AUSM8 | 4.0.25 | ausm_8t1e1_4.0.25.fw | AU8_BT_1.0.02 | ausm_8t1e1_AU8_BT_1.0.02.fw |
FRSM8 | 4.0.25 | frsm_8t1e1_4.0.25.fw | FR8_BT_1.0.02 | frsm_8t1e1_FR8_BT_1.0.02.fw |
FRSM HS1 | 4.0.21 | frsm_hs1_4.0.21.fw | HS1_BT_1.0.02 | frsm_hs1_HS1_BT_1.0.02.fw |
AUSM4 | 4.0.22 | ausm_4.0.22.fw | BT_4.0.00 | ausm_BT_4.0.00.fw |
CESM4 | 4.0.18 | cesm_4.0.18.fw | BT_4.0.01 | cesm_BT_4.0.01.fw |
FRSM4 | 4.0.24 | frsm_4.0.24.fw | BT_4.0.00 | frsm_BT_4.0.00.fw |
IMATM | 4.0.23 | imatm_4.0.23.fw | IMA_BT_1.0.02 | imatm_IMA_BT_1.0.02.fw |
CESM8 | 4.1.10 | cesm_8t1e1_4.1.10.fw | CE8_BT_1.0.02 | cesm_8t1e1_CE8_BT_1.0.02.fw |
 |
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 MGX8220. |
s
| Board Type | F/W Image | Size (bytes) | Boot Image | Size (bytes) |
|---|---|---|---|---|
ASC | asc_4.1.11.fw | 1764620 | asc_ASC_BT_1.0.03.fw | 495176 |
AUSM8 | ausm_8t1e1_4.0.25.fw | 1020868 | ausm_8t1e1_AU8_BT_1.0.02.fw | 377836 |
FRSM8 | frsm_8t1e1_4.0.25.fw | 731444 | frsm_8t1e1_FR8_BT_1.0.02.fw | 297988 |
FRSM HS1 | frsm_hs1_4.0.21.fw | 686008 | frsm_hs1_HS1_BT_1.0.02.fw | 293052 |
IMATM8 | imatm_4.0.23.fw | 1009544 | imatm_IMA_BT_1.0.02.fw_ | 405800 |
CESM8 | cesm_8t1e1_4.1.10.fw | 637632 | cesm_8t1e1_CE8_BT_1.0.02.fw | 264592 |
AUSM4 | ausm_4.0.22.fw | 758068 | ausm_BT_4.0.00.fw | 265288 |
CESM4 | cesm_4.0.18.fw | 625676 | cesm_BT_4.0.01.fw | 267212 |
FRSM4 | frsm_4.0.24.fw | 778556 | frsm_BT_4.0.00.fw | 264404 |
Version 4.1.12 requires one or two (for redundant operation) ASCs or ASC2s. If two Shelf Controllers are in place, they must both be at Version 4.1.12 (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 image for proper operation.
Upgrades are supported from Version 2.X, Version 3.X, Version 4.0.x and Version 4.1.x. For upgrade procedures, reference the Version 4.1.X upgrade procedures document.
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. This issue is encountered only with the dated revision names, and not necessarily with the standard ones.
There are no additional deliverables required for Release 4.1.12.
There are known issues with AUSM ILMI, in version 4.x. For ILMI support it is advised to upgrade the firmware to 5.0.16 and later versions.
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.
Use dspcd command, "Fab number" field contains the necessary information for Model B 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.
The 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.
Step 2 Now on Model B card, if you want to change SF / ESF connections to SF-MF / ESF-MF connections on a particular line, use the 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. |
 |
Caution ASC service modules 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 quiesced or downed before doing any operation that could interrupt a disk write. The 4.1.05 ASC and subsequent firmwares do an automatic quiesce 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. Verify disk health after occurrence. |
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. Verify disk health after occurrence. |
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. Verify disk health after occurrence. |
For information on downdisk CLI to perform manual quiescence 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. |
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:
1. not to have a service module in slot 5 or
2. 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.
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 the 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.
AUSM ILMI should not be turned on in version 4.x. There are known issues in this version.
clralm -sonet will not clear 15min alarms on the ASC.
| BugId | Description |
|---|---|
CSCdv81784 | Duplicate DLCIs in PRI file causes card reset repeatedly Symptom: SM Card in reset loop Conditions: Previously saved PRI File downloaded to the switch. Connections provisioned after this. Workaround: Reset the card after the PRI file download. |
CSCdv34701 | Executing the runslftstno 8 command on a standby FRSM-4T1 can cause card reset Symptom: Executing a runslftstno 8 command causes reset on standby FRSM-4T1. Conditions: runslftstno 8 executed on standby FRSM-4T1. Workaround: None. |
CSCdv81905 | FRSM-HS1 card CLI display locks up Symptom: Display commands like dspchan etc. locks up. Conditions: If there is a task suspended in the card. The "i" command will show all the tasks and the state. Workaround: Executing the resetcd command is the cleanest way of clearing up this failure. |
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) |
| Bug ID | Description |
|---|---|
CSCdw63646 | An error can occur with management protocol processing. Please use the following URL for further information: http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903 |
| BugId | Service Module | Description |
|---|---|---|
CSCds54986 | ASC | Unable addred for all slots FRSM-8T1 by Invalid card type Symptom: Unable addred for all slots FRSM-8T1 by Invalid card type Conditions: Reset the primary card when the standby is still in Update in Progress. Before that do delete/addition of a few 1:N redundancies. Workaround: resetcd for primary slot |
CSCdt97740 | ASC | dspln accepts extra parameters Symptom: The dspln command accepts extra parameters Condition: Always Workaround: None. Fixed in 4.1.11 |
CSCdu01707 | ASC | CESM channel reports erroneous alarm on channel 272 Symptom: dspchancnt shows the channel to be in alarm on a CESM but there is no hindrance to passing traffic. This occurs after a failure of a T1 connected to the CESM. Workaround: Please call TAC and reference CSCdm89320 and TAC will be able to clear the alarm |
CSCdt70815 | ASC | The clralm command accepts E3 options for DS3 lines and vice versa Symptom: The clralm command accepts E3 options for DS3 lines (and vice versa) Conditions: BNM-T3, or BNM-E3 Workaround: Don't set the non-applicable options |
CSCdt91224 | ASC | The dspalm -sonet command shows extra lines Symptom: The dspalm -sonet command shows extra lines Condition: Execution of dspalm with only -sonet option. workaround: Execute 'dspalm -sonet 1' |
CSCdu40630 | ASC | Modify on Clock Source in Physical Line Config(dsx3) on SRM3T3 gives error Symptom: Modify on Clock Source in Physical Line Config(dsx3) on SRM3T3 gives error Conditions: Open the Physical Line Config(dsx3) dialog from one of the SRM3T3 lines which is enabled. Try modifying Clock Source to "local Clk" and press Apply button.cvweb returns "NoSuchInstance".But the community string associated with SRM is AXIS_SRM_ACTIVE, using this the error table return no entry.Whereas if you use AXIS_ASC_ACTIVE the error table has the correct entry. Workaround: No workaround. Fixed in 4.1.11 |
CSCds71491 | ASC | Incorrect backcard corrupted redundancy table Symptom: An incorrect backcard was inserted into the ASC slot. As a result the redundancy table got corrupted. Conditions: It happened only once. Workaround: None. Fixed in 4.1.11 |
CSCdp87022 | ASC | FallBack Switchcc does not switch back even if SRM port is in Alarm Symptom: The Y-cable was not plugged into Standby SRM for an enabled T3 line and FallBack Switchcc was issued on Active ASC. The newly Active ASC should have switched back automatically because of this but it never did so. Conditions: The T3 line on the Active alarm should not be in Alarm and after the FallBack switchcc it should go into alarm on the newly Active SRM. Workaround: None. Fixed in 4.1.11 |
CSCdt97429 | AUSM-4T1E1 | Log is getting error messages 14 cmm 8171 Invalid Value : Invalid msg Type Symptom: When the SM is in standby mode, it logs messages "Invalid message received from ACRED 3" in the log file. Conditions: Occurs when the SM is in standby mode. Workaround: None. Fixed in 4.1.11 |
CSCdt95939 | AUSM-8T1E1 | cnfimagrp syntax description error Symptom: xcnfimagrp syntax description error Condition: Always Workaround: None. Fixed in 4.1.11 |
CSCds59856 | AUSM-8T1E1 | AUSM card get stuck in Failed state after clrsmcnf (frequency intermittent) Symptom: AUSM card get stuck in failed state. Conditions: After executing the CLI clrsmcnf on the card. This occurs intermittently. Workaround: Reset the card. |
CSCdu64998 | AUSM-8T1E1 | The dspchan display on AUSM VP has -214565300 in VCI field, normally zero. Symptom: When issuing dspchan on AUSM running 4.0.22, 4.0.23 or 4.0.24 and you configure a connection as a Virtual path the display now shows an "S" in the VP line or text and in the VCI field instead of a ZERO there is now displayed an negative value -2145654300. Conditions: Run any of the above firmware and build a Virtual Path with any numerical value will produce display with same S and negative outputs. Workaround: None. Fixed in 4.1.11 |
CSCdt95075 | AUSM-8T1E1 | AUSM ABRFST PVCs not rating back to MCR on BXM in congestion Symptom: ABRFST PVC's on AUSM not rating down to MCR when run over congested BXM Conditions: Lab environment. Manufactured congestion. Workaround: Configure IBS = 0. |
CSCdt94979 | BNM-155 | Line Statistical Alarm on BNM-155 can not be cleared in clralmcnt. Symptom: Line Statistical Alarm which occurs on BNM-155 tried clralmcnt but can not clear alarm. Conditions: Line Statistical Alarm recorded on BNM Workaround: Go to shellConn. Issue IntegrateCardAlarm(0,2097,12) Execute the switchcc command
Further Problem Description: Line statistical alarm was not getting cleared because the 15min stats alarms remained. Clearing 15min alarms is a design change and would require a PER for the change to come to effect. CSCdu05641 carries the justification for the same. A SONET equipment provides performance monitoring registers for the current 15-minute and one-day periods. Once a time period lapses, register counts are stored and a new register starts for the next time period. For historical purposes, the current 15-minute and day registers, as well as the last 32 15-minute registers and the last day register, are stored. Each SONET network element provides a sliding window of performance history for each of its facilities. For long-term data storage and historical trend analysis, performance monitoring information can be reported to an operations support (OS) system or network manager. That's why the Current15min alarms are not cleared. If clralm is issued 15 minutes after the line goes in statistical alarm, i.e. after the Current15min alarms have spilled over 15min bucket into the 24hr one, the alarms will be cleared and card will behave as expected. Fix Description: Since 15min alarms could not be cleared a patch is put in place which would clear the alarm state of the BNM-155 card. Nevertheless, because the 15min alarms are on, dspalm output would show them. Also, the MINOR LED on the card will glow as the aumUpdateAsmAlarms function will update the LED's. The fix is available in the 5.0.17 version as part of 5.0.17 bundle of images. |
CSCdj68472 | BNM-155 | Problem of Alarm status of AXIS connected between BNM-155 and BXM-155 Symptom: Difference of Alarm status between LED and CLI. Conditions: When Tx cable on BNM-155 is pulled out, the card LED shows Major alarm but dspcds/dsplog show Minor Alarm. Workaround: None. Fixed in 4.1.11 |
CSCdt97435 | CESM-4T1E1 | Log is getting error messages 14 cmm 8171 Invalid Value : Invalid msg Type Symptom: When the SM is in standby mode, it logs messages "Invalid message received from ACRED 3" in the log file. Conditions: Occurs when the SM is in standby mode. Workaround: None. Fixed in 4.1.11 |
CSCdt74630 | CESM-8T1E1 | Log is getting error messages 14 cmm 8171 Invalid Value : Invalid msg Type Symptom: When the SM is in standby mode, it logs messages "Invalid message received from ACRED 3" in the log file. Conditions: Occurs when the SM is in standby mode. Workaround: None. Fixed in 4.1.11 |
CSCds34620 | CESM-8T1E1 | CESM ports are not seen in connection manager intermittently Symptom: Sometimes, while adding a new connection, ports are not showing up in the selection window properly in spite of their being present in the database. For example if the database has 4 ports for a card and shelf, it shows up only two of them or it does not show any. Conditions: It is intermittent and highly random. Workaround: Hit Cancel button so that the new connection window disappears. And restart the configure new connection window from connection manager GUI. Further Problem Description: On the MGX side the problem is not seen if a physical (metallic) loopback is added instead of the soft loopback (through addlnloop). |
CSCdu87342 | CESM-8T1E1 | Secondary card doesn't take over in 1:N redundancy when Primary is pulled out Symptom: The secondary card in 1:N redundancy doesn't cover the primary card if the primary card is physically removed. Conditions: Occurs when removing the primary card slowly Workaround: Use the softswitch command. |
CSCdu88880 | CESM-8T1E1 | Violation of R2.3.1.1 in CES-IS 2.0 Symptom: Analog modem calls which are transported over the Structured T1 CAS CESM connections may experience more bit corruptions than on a normal TDM link. This may even exceed the tolerable Signal to Noise Ratio(SNR) for some modems and might result in modem calls getting dropped. Conditions: The problem could be observed on Structured T1 CAS connections. Workaround: Use unstructured CESM connections if analog modems drop calls due to excessive bit corruption. |
CSCdv20088 | CESM-8T1E1 | display of dspcd should distinguish between model A and model B cards Symptom: The display generated by running the dspcd command does not distinguish between model A and model B cards Condition: Always Workaround: None. Fixed in 4.1.11 |
CSCdv53811 | CESM-8T1E1 | Unable to snmpset cesmChanConditionedSigCode to a value other than 0 Symptom: Using SNMP to set the "Conditional Signalling" field to any value other than 0 reports a SNMP general failure on a CESM PVC. Also trying to use xcnfchan command fails to modify condsig value on an MGX8220 yet it works OK on an MGX 8250. Conditions: A CE-CE PVC is built using CWM. As CWM does not have a field to enter a Conditional Signalling value it gets set to 0. Trying to use SNMP to set this to say 5 reports a general error: aptcwm01% snmpset -c AXIS_SM_5 axis4-lan
stratacom.110.5.3.2.1.1.1.26.32
INTEGER 5
snmpset: Agent reported an error.
snmpset: SNMP: A general failure occured on the agent.
aptcwm01% snmpset -c AXIS_SM_5 axis4-lan stratacom.110.5.3.2.1.1.1.2.32
INTEGER
3 stratacom.110.5.3.2.1.1.1.26.32 INTEGER 5
snmpset: Agent reported an error.
snmpset: SNMP: A general failure occured on the agent.
aptcwm01%
Workaround: Delete and rebuild PVC via CLI and enter value manually. Further Problem Description: When using CAS signalling on a E1 line and you have a PVC added via CWM the Conditional Signalling code gets set to 0 automatically. This means that if there is an underrun the channel will send 0000 which causes the CPE equipment to drop the whole 2Meg line as it gets confused thinking there is a 2Meg line failure when it sees all zero's. This problem of trying to use SNMPSET is only a problem on MGX8220 shelves. IT DOES NOT EXIST ON MGX8250 SHELVES. MGX8250 Allows SNMPSET successfully. |
CSCdv53446 | CESM-8T1E1 | Swapping CESM/B and CESM/A card caused connection type mismatch. Symptom: Swapping CESM/B and CESM/A card caused connection type mismatch. Condition: With MF and none-MF connection on the same card, replace Model B card with Model A card, add some new connections, then change Model B card back. Workaround: None. Fixed in 4.1.11 |
CSCdv57752 | CESM-8T1E1 | On configuring Bulk mode for CESM/B, dellink does not work properly Symptom: On configuring Bulk mode for CESM/B, dellink does not work properly Condition: node: 172.29.15.215 slot: 7 Workaround: None. Fixed in 4.1.11 |
CSCdu76896 | FRSM-4T1E1 | Missing portM32EgressQueueThresh support for Frsm-4t1e1 Symptom: The portM32EgressQueThresh is not preset in the .CF file. This impacts CWM. Conditions: TFTP of .CF file. Workaround: None. Fixed in 4.1.11 |
CSCdu76885 | FRSM-8T1E1 | Missing portM32EgressQueueThresh support for Frsm-8t1e1 Symptom: The portM32EgressQueThresh is not preset in the .CF file. This impacts CWM. Conditions: TFTP of .CF file. Workaround: None. Fixed in 4.1.11 |
CSCds36158 | FRSM-8T1E1 | FRSM-8 lines go into alarm if runslftstno 7 is used under bulk distribution Symptom: FRSM-8 card, running 5.0.12: Under Bulk distribution. When the "runslftstno 7" command is run, all lines go into alarm. Conditions: FRSM-8 card, running 5.0.12: Under Bulk distribution. Workaround: Check to see if card is under bulk distribution: Use the command "dspslotlink <slot>" on the active ASC. If under BULK distribution, then DO NOT use the "runslftstno 7" command on the FRSM-8 card. If the problem has already occurred, a softswitch to the redundant FRSM-8 card resolves the problem. |
CSCdt40285 | FRSM-8T1E1 | Override CAC parameter cannot be enabled/disabled Symptom: Cannot modify the CAC override enable/disable using CM GUI. It's always disabled. Condition: Occurs on AUSM-8T1E1 5.0.12 firmware Workaround: Use snmpsets to enable/disable the CAC override. |
CSCdu79152 | FRSM-8T1E1 | Need AUSM-8T1E1 style DS1 counters in FRSM-8T1E1 Symptom: T1 alarm counters are missing. Conditions: FRSM-8T1E1 Workaround: None |
CSCdv21357 | FRSM-8T1E1 | Alarms cleared after resetting card on FRSM-8E1with 2 lines connected back-to-back Symptom: Line alarms clear after a card reset if lines are connected back to back on the same card. Conditions: Only when 2 lines on the same card are connected back to back. Workaround: Up the other side of the lines (and delete it). |
CSCds45380 | FRSM-8T1E1 | Statistics collection on FRSM card showing disabled Symptoms: Enabling statistics collection on FRSM connections fails if 6 different connection stats are already enabled. Conditions: Statistics Collection Flag is disabled if there are more than 6 parameters for which Statistics are being collected despite the fact that it is specifically being enabled through the enable file from CWM. This has been seen on MGX 8220s running 5.0.12, 5.0.10, 4.x.x software. Workaround: The workaround is to reset the FRSM card which then allows as many different types of connection statistics to be enabled as required. |
CSCdp07434 | FRSM-HS1 | Axis: Buffer overflow problem causes one way traffic Symptoms: Egress Buffer overflow on the card causes one way traffic. Traffic from network to CPE does not go through. Conditions: HS1 FRSM 4.0.16 Workaround: resetcd |
CSCdt48354 | SRM-T1E1 | SRM-3T3 inserted message logged when reset ASC (SRM-4T1E1). Symptom: ASC, BNM and SRM-T1E1 is configured the redundancy structure. Then, if the ASC is reset (switchcc/clrallcnf), SRM-3T3 is logged on "dsplog". Conditions: Resetting one of the core cards so that the line module inserted message is logged. Workaround: None. |
CSCdu31876 | SRM-T1E1 | Local Loopback didn't work on BERT test with E1 line configured as clear Symptom: While running a BERT test with a local loopback on a E1 line configured as Clear, the BERT test came back and gave some bits error count. Conditions: Workaround: The workaround for this problem is to use a physical loopback plug and configure the BERT test as no local loopback. The test pattern will be sent out to the line and the pattern will come back as you have the loopback plug on. All test should pass with this test setup. |
The following table provides the list of Hardware revisions with which the Firmware and Bootcode in MGX 8220 Release 4.1.11 are compatible.
| 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 |
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 |
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your chassis.
|
Note If you purchased your product from a reseller, you can access Cisco Connection On-line (CCO) as a guest. CCO is Cisco Systems' primary, real-time support channel. Your reseller offers programs that include direct access to CCO's services. |
For service and support for a product purchased directly from Cisco, use CCO.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
|
Note If you are a network administrator and need personal technical assistance with a Cisco
product that is under warranty or covered by a maintenance contract, contact Cisco's
Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To
obtain general information about Cisco Systems, Cisco products, or upgrades, contact
800 553-6387, 408 526-7208, or cs-rep@cisco.com. |
Posted: Fri Mar 1 16:32:54 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.