Table Of Contents
4.0 Software Release Notes for the Cisco SES PNNI Controller
Contents
About Release 4
SES PNNI and SVC Controller
Feature Overview
New and Changed Information for Release 4
Closed User Groups
Preferred Routes for PNNI Multipeer Group Networks
Point-to-Multipoint SVC/SPVC Support
IGX as an AAL5 Feeder
Detailed Feature Information
System Requirements
Hardware Compatibility Matrix
Software Compatibility
Compatible Releases
Additional Deliverables
SPVC Connection Statistics
Upgrade Notes and Cautions
Upgrading the SES Node
Upgrading to a New Software Release
Special Installation and Upgrade Requirements
Upgrading from SES Release 1.1.75 or Release 3.0.20 to Release 4
Upgrading the Backup Boot Image
Upgrading the Backup Boot on Non-Redundant Systems
Upgrading the Cisco SES PNNI Runtime Image
Upgrading the Runtime Image on Redundant Systems
Upgrading the Runtime Image on Non-Redundant Systems
Upgrade Path
Cisco SES PNNI Controller Bring Up Procedure
Limitations and Restrictions
General Limitations and Restrictions
Recommendations
Caveats
Open Anomalies in Release 4.0.00
BXM Firmware MFX Release Notes
About the Firmware MFX
Front Cards
Front Card for APS Compatibility
BackCards
New Features supported in BXM Firmware MFX
New Features supported in BXM Firmware MFW
New Features supported in BXM Firmware MFV:
New Features supported in BXM Firmware MFU
New Features supported in BXM Firmware MFT
New Features supported in BXM Firmware MFR
New Features supported in BXM Firmware MFP
New Features supported in BXM Firmware MFN
New Features supported in BXM Firmware MFM
New Features supported in BXM Firmware MFK
New Features supported in BXM Firmware MFJ
New Features supported in BXM Firmware MFH
New Features supported in BXM Firmware MFF
New Features supported in BXM Firmware MFE
New Features supported in BXM Firmware MFD
New Features supported in BXM Firmware MFC
New Features supported in BXM Firmware MFB
New Features supported in BXM Firmware MFA
New Features supported in BXM Firmware MEC
New Features supported in BXM Firmware MEB
New Features supported in BXM Firmware MEA
New Features supported in BXM Firmware MDA
Special Installation/Upgrade Requirements
APS Issues
Channel Stats Issues
Features Obsoleted
Notes, Cautions & Clarifications
Known Anomalies
Bugs Fixed in MFX
Bugs Fixed in MFW
Logic to calculate actual cell transmission rate in a BXM card is as follows (CSCdm94372):
Firmware Filenames and Sizes
Related Documentation
Cisco WAN Manager Release 12
SES PNNI Release 4
Cisco WAN Switching Software Release 9.4
Conventions
Obtaining Documentation
Cisco.com
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Cisco TAC Website
Cisco TAC Escalation Center
Obtaining Additional Publications and Information
4.0 Software Release Notes for the Cisco SES PNNI Controller
Contents
This document contains the following sections:
About Release 4
These release notes describe the system requirements, new and changed procedures, upgrade procedures, and limitations that apply to Release 4 of the Service Expansion Shelf (SES) controller. These notes also contain Cisco support information. Software Release 4 supports the following Cisco WAN switching products: Cisco BPX 8600 series with SES controller.
SES PNNI and SVC Controller
Release 4 of the SES controller is compatible with the Cisco BPX 8600 series software Release 9.4.00. The SES controller is connected to the Cisco BPX 8600 series switch via a BXM-155 (or T3/E3) port configured as a trunk. Redundant SES systems contain two controller cards which offer APS protection on the ports connecting to the BPX.
Feature Overview
The SES controller is a Virtual Switch Interface (VSI) controller which provides a Cisco BPX 8600 series wide-area switch the capability to create switched virtual circuits (SVCs) and soft permanent virtual circuits (SPVCs) using the User-to-Network Interface (UNI) and Private Network-to-Network Interface (PNNI) protocols. One SES controller is required for each Cisco BPX 8600 series node that will be originating, transporting, or terminating SVC/SPVC connections. The SES controller is offered in redundant or non-redundant configurations.
New and Changed Information for Release 4
This section describes new and changed features in Release 4 of the SES controller.
Closed User Groups
The Closed User Groups (CUG) supplementary service enables network users to form groups, to and from which access is restricted. A network user may be associated with one CUG, multiple CUGs, or no CUG. Members of a specific CUG can communicate typically among themselves, but in general not with network users outside of the CUG. Specific network users can have additional restrictions preventing them from originating calls to, or receiving calls from, network users of the same CUG (Outgoing Calls Blocked or Incoming Calls Blocked). In addition, a network user can be further restricted in originating calls to, or receiving calls from, network users outside of any CUG membership defined for the network user (Outgoing Access or Incoming Access.).
•
The feature is based on the ITU-T Q.2955.1 recommendation.
•This feature is aligned with the 4.0 release. All the features supported by the previously deployed releases for the MGX 8850/8830/8950, and SES will be supported and seamless upgrade capabilities will be provided.
Preferred Routes for PNNI Multipeer Group Networks
Preferred routing of connections provides the network operator a means of bypassing the PNNI route selection, and configuring a specific path through the network which a connection will follow. Preferred routes can be configured as either Preferred or Directed routes. A Preferred route is one which will follow the configured path if available, but will revert to a PNNI-selected route if the preferred route is not available. A Directed route is one which will follow only the configured path; if the configured path is not available, the connection will remain unrouted.
Preferred routes can be specified for SPVCs from source switch to the destination switch end-to-end using CLI or SNMP. The end-to-end preferred route for connections can span across multiple peer groups. The implementation is based on PNNI 1.1 specification.
Point-to-Multipoint SVC/SPVC Support
The SVC/SPVC point-to-multipoint (P2MP) feature offers the ability for one root SVC/SPVC connection to establish a simple tree topology to one or more leaf connections. The data traffic is uni-directional from root multicast to all leaves, i.e., what is sent from the root data channel is received by all leaves. From the root, leaves can be added to the connection using SETUP/ADD_PARTY signaling messages. Point-to-multipoint is a mandatory feature described in UNI 3.0, UNI3.1 and UNI4.0 specs. The implementation is compliant with in Q2971.
IGX as an AAL5 Feeder
This feature adds the ability to the IGX to act as an AAL5 feeder to the PXM45-based Cisco MGX 8850, the PXM1E-based Cisco MGX 8850 and Cisco MGX 8830, or the BPX+SES. In prior releases, the IGX could only be a feeder to the BPX (or another IGX). The two nodes communicate by using Annex G LMI over a proprietary Auto Route Networking Channel.
This new IGX AAL5 feeder support is added by encapsulating the LMI messages in ATM AAL5 cells on the UXM feeder trunk connected to an AXSM, AXSM-E, PXM1E, or BXM card.
Detailed Feature Information
As networks grow in size, PNNI becomes a critical element in the ability to scale a network. PNNI provides a standard, interoperable, and scalable method to grow PVC (SPVC) networks to large sizes. In addition, applications such as voice, video, and LAN require WAN switches to provide dynamic connection capabilities in the form of SVCs. The SES controller provides the Cisco BPX 8600 series switch with a centralized controller for establishing SPVCs and SVCs in both the Cisco BPX 8600 series networks and in mixed vendor environments.
The Cisco BPX 8600 series switch in combination with the SES controller (Release 4) supports the following features:
•SPVC and SVC real time statistics with MIB support
•SNTP
•Priority routing of connections
•Standards based path and connection trace facilities
•Single-ended and double-ended SPVC and SPVP configuration
•ATM UNI 3.0/3.1, 4.0 (CBR, VBR, UBR)
•PNNI Single Peer Group and Multiple Peer Group (MPG)
•AINI
•60,000 LCN on BXM-E
•Point-to-Point SVCs, SPVCs, and SPVPs
•IISP with PNNI Inter-networking
•E.164 and AESA/NSAP (DCC, ICD, E.164) addressing
•Address filtering (source and destination)
•ILMI 4.0
•SPVC and SPVP endpoint provisioning (including ABR)
•OC-3/STM-1, T3/E3 interfaces
•OC-12/STM-4 interfaces
•Intelligent CAC
•Call Processor Redundancy (calls stable across switchover)
•APS on controller uplinks to the Cisco BPX 8600
•Connection and Path Trace facilities
•Integrated management via CWM and SNMP MIBs
•100, 000 connections (SVC+SVP+SPVC+SPVP) per node. 100,000 connection for DACS only, or routed SPVC only, or mixed.
•200,000 max endpoints per node (if all 100,000 connections are DACS)
•99 UNI/PNNI SVC ports per node
•100 calls per second
•Dynamic partitioning and soft partitioning
•SPVC support on feeder trunks
•Dedicated Q-bin for control signaling
•SPVC Connection Statistics
•Graceful upgrades to Release 4.0 are fully supported from Release 3.0.20 and Release 1.1.75. If you are running a release prior to 1.1.75, use the appropriate upgrade paths as follows:
–If you are running release 1.0.15, upgrade to Release 3.0.20 or Release 1.1.75 before you upgrade to Release 4.0.
–If you are running release 1.0.14 or lower, upgrade to Release 1.0.15. Once Release 1.0.15 is up on your switch, upgrade to Release 1.1.75 or Release 3.0.20, and then upgrade to Release 4.0.
System Requirements
This section describes the hardware supported in this release and the software compatibility requirements.
Hardware Compatibility Matrix
Table 1 and Table 2 list the hardware supported in Release 4, and show which back cards are compatible with each front card.
Table 1 OC3 Hardware Compatibility
OC3 Combinations (Shipping/Customer Configurations)
|
No.
|
Description
|
Front Card (PXM)
|
PXM UI Back Card
|
PXM Uplink Back Card
|
1
|
MMF OC3
|
SES-PXM-CNTL-4-155
(with 4-port OC3)
P/N 800-06454-01 or later
|
PXM-UIA
Rev. A0 or later
|
MMF-4-155
Rev. A0 or later
|
2
|
SMF-OC3, Intermediate Range
|
SES-PXM-CNTL-4-155
(with 4-port OC3)
P/N 800-06454-01 or later
|
PXM-UIA
Rev. A0 or later
|
SMFIR-4-155
Rev. A0 or later
SMFIR-4-155/B
Rev. A0 or later
|
Table 2 T3/E3 Hardware Compatibility
T3/E3 Combinations (Shipping/Customer Configurations)
|
No.
|
Description
|
Front Card (PXM)
|
PXM UI Back Card
|
PXM Uplink Back Card
|
1
|
T3
|
SES-PXM-CNTL-2T3E3
(with 2-port T3E3)
P/N 800-06699-01
|
PXM-UIA
Rev. A0 or later
|
BNC-2T3
Rev. A0 or later
|
2
|
E3
|
SES-PXM-CNTL-2T3E3
(with 2-port T3E3)
P/N 800-06699-01
|
PXM-UIA
Rev. A0 or later
|
BNC-2E3
Rev. A0 or later
|
Table 3 lists the MGX hardware which is compatible with Release 4 of the SES controller.
Table 3 MGX Hardware Compatibility
Feeder
|
MGX 8850 R1
|
MGX 8220
|
Release
|
1.2.20
|
5.0.19
|
HW Cards
|
PXM-1
PXM1-2T3E3
PXM1-4OC3
PXM1-OC12
MGX-SRM-3T3/C
MGX-SRM-3T3/B
AX-CESM-8E1
AX-CESM-8T1
AX-CESM-8T1/B
MGX-AUSMB-8E1
MGX-AUSMB-8T1
MGX-CESM-T3
MGX-CESM-E3
MGX-FRSM-8E1
MGX-FRSM-8T1
MGX-FRSM-HS2
MGX-FRSM-HS2/B
MGX-FRSM-2CT3
MGX-FRSM-2T3
MGX-FRSM-2E3
MGX-FRSM-HS1/B
MGX-VISM-8T1
MGX-VISM-8E1
MGX-VISM-PR-8T1E1
MGX-RPM-128M/B
MGX-RPM-PR
|
MGX-FRSM-4T1/4E1/4T1-C/4E1-C
MGX-SRM-T1E1
MGX-SRM-3T3/C
MGX-SRM-3T3/B
AX-CESM-4T1/4E1
AX-CESM-8T1/8E1
MGX-AUSM-4T1/4E1
MGX-FRSM-8T1/8E1
MGX-AUSM-8T1/8E1
MGX-AUSMB-8T1/8E1
MGX-AUSMB-8T1/8E1
MGX-FRSM-HS1
MGX-FRSM-HS1/B
MGX-FRSM-HS2
IMATM-T3T1/E3E1
IMATMB-T1/E1
|
Software Compatibility
Table 4 lists the software that is compatible for use in a switch running Release 4 software.
Table 4 Software Compatibility Matrix
Board Pair
|
SES Controller Release
|
Latest Boot Code Version
|
Minimum
Boot Code
Version
|
BXM Firmware
|
SWSW
|
CWM
|
PXM1
|
1.0.10
|
pxm1_001.000.001.000_bt.fw
|
1.0.01
|
MFH
|
9.3.10
|
10.3
|
PXM1
|
1.0.11
|
pxm1_001.000.011.001_bt.fw
|
1.0.11
|
MFJ
|
9.3.10
|
10.4
|
PXM1
|
1.0.12
|
pxm1_001.000.011.001_bt.fw
|
1.0.11
|
MFL
|
9.3.11
|
10.4
|
PXM1
|
1.0.13
|
pxm1_001.000.013.000_bt.fw
|
1.0.13
|
MFM
|
9.3
|
10.4
|
PXM1
|
1.0.14
|
pxm1_001.000.013.000_bt.fw
|
1.0.13
|
MFN
|
9.3.11
9.3.24
|
10.4
|
PXM1
|
1.0.15
|
pxm1_001.000.013.000_bt.fw
|
1.0.13
|
MFN
|
9.3.11
9.3.24
|
10.4
|
PXM1
|
1.1.60
|
pxm1_001.001.060.102_bt.fw
|
1.1.60
|
MFN
|
9.3.30
|
10.5
|
PXM1
|
1.1.70
|
pxm1_001.001.070.201_bt.fw
|
1.1.60
|
MFR
|
9.3.35
|
10.5.10
|
PXM1
|
1.1.75
|
pxm1_001.001.075.101_bt.fw
|
1.1.60
|
MFU
|
9.3.36
|
10.5.10
Patch 1
|
PXM1
|
3.0
|
pxm1_003.000.000.000_bt.fw
|
1.1.75
|
MFV
|
9.3.40
|
11.0
|
PXM1
|
3.0.10
|
pxm1_003.000.010.001_bt.fw
|
3.0.00
|
MFW
|
9.3.42
|
11.0.10
|
PXM1
|
3.0.20
|
pxm1_003.000.010.002_bt.fw
|
3.0.00
|
MFW
|
9.3.45
|
11.0.10
Patch 1
|
PXM1
|
4.0.00
|
pxm1_004.000.000.201_bt.fw
|
4.0.00
|
MFW
|
9.3.47
|
12.0.00
|
Compatible Releases
Release 4 of the SES controller is certified with the following releases:
•Graceful upgrades to Release 4.0 are fully supported from Release 3.0.20 and Release 1.1.75. If you are running a release prior to 1.1.75, use the appropriate upgrade paths as follows:
–If you are running release 1.0.15, upgrade to Release 3.0.20 or Release 1.1.75 before you upgrade to Release 4.0.
–If you are running release 1.0.14 or lower, upgrade to Release 1.0.15. Once Release 1.0.15 is up on your switch, upgrade to Release 1.1.75 or Release 3.0.20, and then upgrade to Release 4.0.
•BPX SWSW Version 9.4.00 (see Software Compatibility Notes Matrix, first and second bullets)
•BXM firmware version MFX (see Software Compatibility Notes Matrix, first and second bullets)
•CiscoView Version 5.4.1
•Cisco WAN Manager (CWM) Release 12.0
•BCC-3-64
•BPX-BCC-4V or BPX-BCC-4V/B
•MGX 8850 Release 1, Release 1.2.20
•MGX 8220 Release 5.0.19
•SNMP MIB for Release 4.0 is bpxsesrel4000mib.tar
For further information on the BXM card, refer to the 9.4.00 Version Release Notes Cisco WAN Switching Software.
Additional Deliverables
The SES controller MIB is being provided with the delivery of Release 4.0 of the SES controller software on CCO. The MIB is in standard ASN.1 format, and is included in the same directory where the SES controller software is located within CCO. The SNMP SES controller MIB file can be compiled with most standards-based MIB compilers.
Refer to the Cisco SES PNNI Controller Software Configuration Guide, Release 3, Appendix D, "SNMP Management Information Base," for a description of the MIBs supported by the SES controller.
SPVC Connection Statistics
SPVC connection statistics display the statistics generated for the originator node. In MPG nodes, the SPVC connection statistics display the statistics for the border nodes, as well. The SPVC connection statistics show the number of SPVC connections that are successfully routed, the number of connections that failed, and the number of crank backs initiated and received.
Upgrade Notes and Cautions
To upgrade to the latest releases, please follow the following upgrade sequence to upgrade different software components in your network:
1. First, upgrade CWM.
2. Second, upgrade the BXM firmware.
3. Third, upgrade the BPX/IGX software.
4. Lastly, upgrade the SES software.
Upgrading the SES Node
Use the following procedure to upgrade an SES node:
Step 1 At the BPX node, upgrade the BXM firmware to MFX. For detailed information on BXM firmware upgrades, refer to the 9.4.00 Version Release Notes Cisco WAN Switching Software.
Step 2 At the BPX node, upgrade the BCC switch software to Release 9.4.00. For detailed information on BCC switch software upgrades, refer to the 9.4.00 Version Release Notes Cisco WAN Switching Software.
Step 3 Upgrade the SES controller to Release 4. The current boot image is pxm1_004.000.000.201_bt.fw. The current runtime software is pxm1_004.000.000.201_ses.fw.
The latest upgrade procedures are included in the sections that follow.
Step 4 If applicable, upgrade other feeders in your network to a newer release.
Upgrading to a New Software Release
This section contains installation and upgrade instructions. For complete details, refer to the Cisco SES PNNI Controller Software Configuration Guide, Release 3.0, part number 78-14258-01.
Graceful upgrades to Release 4.0 are fully supported from Release 3.0.20 and Release 1.1.75. If you are running a release prior to 1.1.75, use the appropriate upgrade paths as follows:
•If you are running release 1.0.15, upgrade to Release 3.0.20 or Release 1.1.75 before you upgrade to Release 4.0.
•If you are running release 1.0.14 or lower, upgrade to Release 1.0.15. Once Release 1.0.15 is up on your switch, upgrade to Release 1.1.75 or Release 3.0.20, and then upgrade to Release 4.0.
When upgrading your node, upgrade the software in the following order:
1. PXM boot software
2. PXM runtime software
The following sections describe how to upgrade the PXM cards.
Special Installation and Upgrade Requirements
This section covers the procedures for upgrading the backup boot and runtime images for the following hardware:
•Redundant controller card
•Single controller card (the PXM)
Upgrading from SES Release 1.1.75 or Release 3.0.20 to Release 4
The procedures for upgrading the boot and runtime software are in the sections that follow.
Graceful upgrades to Release 4.0 are fully supported from Release 3.0.20 and Release 1.1.75. If you are running a release prior to 1.1.75, use the appropriate upgrade paths as follows:
•If you are running release 1.0.15, upgrade to Release 3.0.20 or Release 1.1.75 before you upgrade to Release 4.0.
•If you are running release 1.0.14 or lower, upgrade to Release 1.0.15. Once Release 1.0.15 is up on your switch, upgrade to Release 1.1.75 or Release 3.0.20, and then upgrade to Release 4.0.
Upgrading the Backup Boot Image
This section provides instructions for upgrading the backup boot images from Release 1.1.75 or 3.0.20 to Release 4. The boot upgrade can be graceful or non-graceful, depending on the type of card to be upgraded and the configuration of the node.
Upgrading the Backup Boot on Redundant Systems
Note Use the following procedure to upgrade the boot on both the active and the redundant controller cards. When performing upgrades on redundant cards, run this procedure on the standby card and not on the active card. This keeps the node in service during the upgrades. Before you upgrade the boot image, FTP the new backup boot firmware, pxm1_004.000.000.201_bt.fw, to the disk (should be the same as the PXM FW procedure.)
To upgrade the boot image on the active controller cards on redundant systems, follow these steps:
Step 1 Transfer the backup boot image to the card disk, as follows:
a. At the SES CLI, enter the dspipif command on the active controller card to find the node's IP address. The field internet address for lnPci 0 interface is the node IP address.
b. From the workstation containing the PXM backup boot image, enter ftp <Node IP address>.
c. Enter the username cisco.
d. Enter your password.
Note The default password is 1ciscoinc. If you have changed the default password to a new password, use your new password.
e. Enter the cd C:/FW command to get to the switch directory.
f. Enter the bin command (for a binary transfer).
g. Enter the put <PXM backup boot image name> command to transfer the backup boot and runtime files from the server to the switch directory C:/FW. See the following example:
put pxm1_004.000.040.200_bt.fw
Replace <PXM backup boot image name> with the boot image name. For Release 4 of the SES, the boot image name is pxm1_004.000.000.201_bt.fw.
h. Enter the bye command to end your session.
Step 2 At the SES controller CLI, enter the dspcds command to determine the standby card slot number.
Step 3 To verify that the boot IP for both the active and standby card is unique, enter the bootchange command.
Step 4 Press Enter until you see inet on ethernet (e). This is the boot IP address for the active PXM.
To change the boot IP address to make it unique, type a new address at the inet on ethernet (e) prompt.
Note Changing the boot IP address on the active PXM also changes it on the standby PXM.
Step 5 Enter the cc <slot number> command to change to the standby card.
Replace <slot number> with the slot number of the card you want to work on.
Step 6 Type sh to go to the shellConn.
Step 7 Enter the sysBackupBoot command.
Step 8 Press Return after you see the disk sync message to get back to active PXM.
Step 9 Exit or open a new telnet window. Telnet into the standby IP host inet address from Step 3.
Note An alternate way to get to the standby card is via the console port on the standby.
Step 10 Perform the following tasks to reset the card:
a. Verify that the card is at the pxm1bkup> prompt. If it is not, enter the sysBackupBoot shellConn command on the standby card.
b. Enter the sysPxmRemove command as shown in the following example.
After you enter the sysBackupBoot command, it takes about one minute for the active PXM to reset the card. If the active PXM resets the standby PXM, wait until it comes to the standby state (approximately four or five minutes), then telnet into the standby and repeat Step 5 and Step 6. After the sysPxmRemove command is entered, the active PXM can not reset the standby.
Step 11 Enter the cd "C:/FW" command from pxm1bkup> prompt to get the FW directory.
Step 12 Enter the ls command to verify that the boot firmware file is there.
Step 13 Enter the sysFlashBootBurn <"boot firmware file name"> command to burn the image on the disk:
pxm1bkup>sysFlashBootBurn "pxm1_004.000.000.201_bt.fw"
The system will ask if you want to proceed. Enter Y for Yes.
Step 14 When the pxm1bkup> prompt returns, enter the reboot command.
Flash Download completed...
Step 15 Log in to the active PXM.
a. Enter the dspcds command to ensure the standby is in standby state.
b. Enter the dspcd <standby slot #> command to verify the firmware was loaded successfully.
Step 16 Load the backup boot onto the active PXM.
a. Enter the switchcc command to change cards.
b. Log in to the SES controller.
c. Perform Step 5 to Step 13 on the new standby PXM.
Upgrading the Backup Boot on Non-Redundant Systems
The upgrade of the boot on a non-redundant controller card is non-graceful. This means the traffic gets disrupted on the card during this operation. The upgrade can only take place when the card is in the BOOT stage. Because there is only one controller card, there will be a node outage as well.
For non-redundant systems, use the following procedures to upgrade the backup boot.
Step 1 Transfer the backup boot image to the card disk using FTP as follows:
a. At the SES CLI, enter the dspipif command at the active controller card to find the Node's IP address. The field internet address for lnPci 0 interface is the node IP address.
b. From the workstation containing the PXM backup boot image, enter ftp <Node IP address>.
c. Enter the username cisco.
d. Enter your password.
Note The default password is 1ciscoinc. If you have changed the default password to a new password, use your new password.
e. Enter the cd C:/FW command to get to the switch directory.
f. Enter the bin command (for a binary transfer).
g. Enter the put <PXM backup boot image name> command to transfer the backup boot and runtime files from the server to the switch directory C:/FW. See the following example:
Replace <PXM backup boot image name> with the boot image name. For Release 4.0 of the SES, the boot image name is 4.0.
h. Enter the bye command to end your session.
Step 2 Log in to the SES.
Step 3 At the shell, enter the sysBackupBoot command to put the controller card into the PXM backup prompt stage.
The PXM card resets.
Step 4 Log in to the PXM.
Step 5 Enter the cd "C:/FW" command at the pxm1bkup> prompt to get the FW directory.
Step 6 Enter the ls command to verify the boot firmware file is there.
Step 7 Enter the sysFlashBootBurn <"boot firmware file name"> command to burn the image on the disk.
pxm1bkup>sysFlashBootBurn "pxm1_004.000.000.201_bt.fw"
The system will ask if you want to proceed. Enter Y for Yes.
Step 8 At the pxm1bkup> prompt, enter the reboot command.
The node resets.
Step 9 Log in to the node.
Step 10 Log in to active PXM.
Step 11 Enter the dspcd <active card> command to determine if the upgrade was successful.
Upgrading the Cisco SES PNNI Runtime Image
This section provides instructions for upgrading the runtime images from Releases 1.1.75 or 3.0.20 to Release 4.
The upgrade of the runtime image on the redundant controller card is graceful. This means the traffic will not be disrupted. The new runtime image for Release 4 is pxm1_004.000.000.201_bt.fw.
Upgrading the Runtime Image on Redundant Systems
Follow these steps to upgrade the runtime image on redundant systems:
Step 1 Use FTP to transfer the runtime image to the card disk.
a. At the SES CLI, enter the dspipif command at the active controller card to find the node's IP address. The field internet address for lnPci 0 interface is the node IP address.
b. From the workstation containing the PXM backup boot image, enter ftp <Node IP address>.
c. Enter the username cisco.
d. Enter your password.
Note The default password is 1ciscoinc. If you have changed the default password to a new password, use your new password.
e. Enter the cd C:/FW command to get to the switch directory.
f. Enter the bin command (for a binary transfer).
g. Enter the put <runtime image name> command to transfer the runtime files from the server to the switch directory C:/FW. See the following example:
put pxm1_004.000.000.201_bt.fw
h. Enter the bye command to end your session.
Step 2 Enter the dspcds command to determine the standby slot.
Step 3 Enter the loadrev <standby slot> <image version> command to load the new version of runtime image on the controller card.
ses1.1.PXM.a>loadrev 2 4.0(0.200)
The standby card resets and comes up in the new revision.
Step 4 When the standby card is in the STANDBY state, enter the runrev <standby slot> <image version> command to run the new version of runtime image on the controller card.
ses1.1.PXM.a>runrev 2 4.0(0.200)
The active card resets and the standby card takes over as active. Both cards are running the new revision.
Step 5 When the standby card is in STANDBY again, enter the abortrev <standby slot> <image version> command to abort this upgrade if needed, as in the following example:
ses1.1.PXM.a>abortrev 1 4.0(0.200)
Step 6 Enter the commitrev <standby slot> <image version> command to commit the new version of the runtime image of the controller card, as in the following example:
ses1.1.PXM.a>commitrev 2 4.0(0.200)
Step 7 Enter the dspcd command to verify a successful upgrade.
Upgrading the Runtime Image on Non-Redundant Systems
The upgrade of the runtime image on the a non-redundant controller card is non-graceful. That means the traffic is disrupted on the card during this operation.
For non-redundant systems, follow these steps.
Step 1 Use FTP to transfer the runtime image to the card disk.
a. At the SES CLI, enter the dspipif command at the active controller card to find the node's IP address. The field internet address for lnPci 0 interface is the node IP address.
b. From the workstation containing the PXM backup boot image, enter ftp <Node IP address>.
c. Enter the username cisco.
d. Enter your password.
Note The default password is 1ciscoinc. If you have changed the default password to a new password, use your new password.
e. Enter the cd C:/FW command to get to the switch directory.
f. Enter the bin command (for a binary transfer).
g. Enter the put <runtime image name> command to transfer the runtime files from the server to the switch directory C:/FW. See the following example:
put pxm1_004.000.000.201_bt.fw
h. Enter the bye command to end your session.
Step 2 Set the new version of the runtime image on the controller card as in the following procedure:
a. Enter the loadrev <slot> <image version> command as in the following example:
ses1.1.PXM.a>loadrev 1 4.0(0.200)
Note No cards will reset.
b. Reply Y (yes) to the proceed question.
c. Enter the dspcd command in the following example:
The secondary revision on the PXM is set to new image version.
Step 3 Enter the runrev <slot> <image version> command to run the new version of runtime image on the controller card.
ses1.1.PXM.a>runrev 1 4.0(0.200)
The card will reset and run the new revision when it returns.
Step 4 Enter the dspcd command to verify a successful upgrade.
Step 5 At this point, you can still abort this upgrade if needed. To abort the upgrade, enter the abortrev command.
ses1.1.PXM.a> abortrev 1 4.0(0.200)
Step 6 Enter the commitrev <slot> <image version> command to commit the new version of the runtime image of the controller card.
ses1.1.PXM.a> commitrev <slot> <image version>
ses1.1.PXM.a> commitrev 1 4.0(0.200)
Step 7 Enter the dspcd command to verify that the runtime image is correct on the card.
Upgrade Path
Graceful upgrades to Release 4.0 are fully supported from Release 3.0.20 and Release 1.1.75. If you are running a release prior to 1.1.75, use the appropriate upgrade paths as follows:
•If you are running release 1.0.15, upgrade to Release 3.0.20 or Release 1.1.75 before you upgrade to Release 4.0.
•If you are running release 1.0.14 or lower, upgrade to Release 1.0.15. Once Release 1.0.15 is up on your switch, upgrade to Release 1.1.75 or Release 3.0.20, and then upgrade to Release 4.0.
Cisco SES PNNI Controller Bring Up Procedure
For detailed procedure changes, refer to the Cisco SES PNNI Controller Software Configuration Guide at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/bpx8600/pnni_ses/rel30/scg/index.htm
Limitations and Restrictions
The following sections describe issues in this release:
•General Limitations and Restrictions
•Recommendations
General Limitations and Restrictions
The following list describes limitations and restrictions that apply to this release:
•If a Closed User Group (CUG) membership configuration is modified in any manner, the CUG interlock code information maintained by the SVC connections which have already been routed is not altered. The CUG feature is not supported on nodes which are configured with right-justified E.164 addresses using cnfe164justify. This feature allows a maximum of 10 CUGs per AESA address at a UNI interface. It allows CUG membership to be provisioned at a maximum of 50 AESA addresses per node. When configuring CUGs on a node up to 500 different 20-byte AESA administrative addresses can be specified (50 addresses with 10 CUGs each) in the leading portion of the CUG interlock codes within the node.
•The192 signaling feature has been tested on PXM45B and PXM45C on MGX8850 and MGX8950 platform only. SES only supports 100.
•Preferred route configured with higher node ID cannot be blocked. Please see CSCdz41145, CSCdz49001. QoS precedence over Preferred Route does not apply to MPG network (CSCdz40310)
•Delpref when Preferred Route in use is allowed in SES 4.0 and not allowed in SES 3.0)
•When upgrading to SES 4.0, Preferred Route feature configured in SES 3.0 release will need to be re-provisioned in SES 4.0.
•When an IGX is added as a feeder to a SES/BPX or MGX node, it will have a default node number, this node number may not be unique within the network. If it is not unique then it needs to be modified to a unique node number by issuing cli command rnmnd <x> where x should be unique with respect to all other auto-route nodes. To find the other node numbers, use cli command dspnds +n". Failing to do so, CWM Databroker may have incorrectly formed hybrid connection database, the CWMGUI may show the connection as incomplete.
•IGX cannot function as both feeder and switch at the same time.
•A graceful upgrade can only be completed from the SES controller software Releases 1.1.75 or 3.0.20.
•If you are running release 1.0.15, upgrade to Release 3.0.20 or Release 1.1.75 before you upgrade to Release 4.0.
•If you are running release 1.0.14 or lower, upgrade to Release 1.0.15. Once Release 1.0.15 is up on your switch, upgrade to Release 11.75 or Release 3.0.20, and then upgrade to Release 4.0.
•The number of connections is always less then the max con value used in the addpart command. This is due to the fact that each card needs 1 LCN for control VC. If your network is a PNNI network, there is another VC for RCC. Therefore, if the max con value is set to 9000 connections, only 8999 or 8998 connections can be added.
•The dspcons command does not support ranges for VPI/VCI. If you enter dspcons -vpi 2, all SPVCs with a VPI less than and equal to 2 are displayed; not just the SPVCs with a VPI equal to 2.
•The Route Optimization algorithm is node-by-node and is based on connection mastership. It is not distributed across the node. For example, if Node A is connected to Node C via Node B, Node A only knows about the connections from A to B, and not about the connections from B to C. This limitation does not allow Node A to use route optimization for connections from B to C.
•There is no check for preventing multiple masters of SPVC connections from pointing to the same slave. When provisioning a second connection to a slave VPI/VCI that is already used, there will be no CLI warning that the connection has failed.
•In a large network, it can take up to 30 seconds (or more) to accept new calls after a switchover. This is because PNNI relearns the topology on a switchover. For existing connections, the control plane and the data plane are not affected on a switchover.
•Node names are not required for each node. A node name can be entered and distributed, but there is no check for node name uniqueness within the network. Multiple nodes with the same name do not cause inconsistencies in PNNI routing.
•BXM interface (OC and T3) traffic policing only works if the cell rate is higher than 50 cells per second.
•When the master endpoint is deleted on a DACS SPVC connection, the slave endpoint is also deleted.
•Release 3.0.20 and above of the SES Controller allows 100 K connections. Since CWM can not support a large number of connections, the number of persistent SPVC connections is limited to 100 K. Also, when using inband management, only 50 K connections are supported.
•The following limitation is in the BXM firmware release MFL and all the releases that follow: due to limited memory space on the BXM card and increased code size, channel statistics level 0 is no longer supported on BXM cards (BXM-155-4, BXM-155-8, BXM-622, BXM-622-2, BXM-T3-8, BXM-T3-12, BXM-E3-8, BXM-E3-12 models). When the BXM card firmware is upgraded to MFL or any post MFL release, regardless how many connections are provisioned, channel statistics level 0 is no longer supported. If a BXM card has channel statistics level 0 turned on, use one of the following upgrade paths to upgrade BXM firmware to MFL or any post MFL release:
–Change the BXM card to run channel statistics level 1. Statistics level 1 supports a maximum of
16 K connections on a card. If a card has more than 16 K connections configured, some connections must be relocated to other BXM interfaces to reduce the total number of connections to be less than 16 K. Reset the card after changing to statistics level 1.
–Replace the BXM card with a BXM-E card. The BXM-E card can continue running statistics level 0. Statistics level 0 can support a maximum of 32 K connections on a card.
Recommendations
The following recommendations apply to Release 4 of the SES controller:
•SPVC connections are provisioned according to a double-ended provisioning model, similar to the way connections are provisioned using AR. This provisioning model enables more robust management (including fault conditions) of both connection endpoints, as opposed to a model which only provisions the master endpoint.
In order to establish a double-ended DACS or a double-ended routed SPVC, provision the slave endpoint before provisioning the master endpoint. The traffic parameters and QoS parameters on both the master and slave endpoints must match in order to establish an SPVC. To establish a single-ended SPVC connection, you only need to provision the master endpoint.
•For each SPVC addition, deletion, or modification, the SES controller generates a trap to CWM. This trap enables CWM to sync up its connection management database with the BPX SES node in real time. The trap information exchange between CWM and SES is handled by an inter-system communication protocol. The trap-handling rate is much slower than the script driven SPVC setup or delete rate. When you use a script to do burst SPVC addition or deletion, the trap queue may overflow and cause trap loss due to limited trap queue size. If burst SPVC add and delete size is more than 1 K connections, Cisco recommends that you pace your setup and delete rate to be 1 connection per second to avoid trap loss.
•The minSvccVci value for the partition is defaulted to 35. VCI 33 and 34 are marked for future control plane use.
•In the case of obtaining optimized routes while performing PNNI on demand route lookup, Cisco recommends that you change the routing policy to the best fit option
Caveats
This section provides information on the open anomalies in Release 4.
Open Anomalies in Release 4.0.00
Table 5 describes the known anomalies in Release 4 of the SES controller. A more in depth discussion of each bug is available in the release note enclosure in Bug Navigator.
Table 5 Open Anomalies for Release 4.0.00
Bug ID
|
Description
|
CSCdw53912
|
Headline
CIT30:uplink shows down after load new image, but call can go through.
Symptom
The uplink was down after loaded the new image, but calls could still go through.
Conditions
The nodes were running an older Release 3 image, everything worked fine. clrallcnf was done on SES nodes, and loaded newer image which was a patch image built on top of a stable label. After SES came up, dsplmilink showed no information about the uplink, dspnode on BPX showed the SES was UNREACHABLE. But the ports on SES were all up (dsppnports). Added lnloop on some port on BPX, SES was updated. But the change of the name of SES, BPX was not updated. Calls could go through these nodes. After deleting the controller and shelf configuration on BPX and added it back, the problem was gone. Did the same scenario on several nodes, the problem was noticed on some of the nodes.
Workaround
None.
|
CSCdw76129
|
Headline
addcon is allowed to add slave with slavepersfalg 1.
Symptom
The command addcon is allowed with slavepersflag 1 while adding the slave end point.
Conditions
Always.
Workaround
None.
Additional Information
Does not effect the connections.
|
CSCea02774
|
Headline
UPGRD:lmiRootTask complains time spec is out of range.
Symptom
SES's error log shows lmiRootTask complained time spec is out of range.
Conditions
Changed clock on BPX.
Workaround
None.
|
CSCea13938
|
Headline
REG4: Incoming CUG call is not correctly checked at destination CUG.
Symptom
Incoming CUG call is not checked properly.
Conditions
Incoming CUG call has OA requested.
Destination CUG has IA allowed.
Workaround
None.
|
CSCea41723
|
Headline
Add ICR range check to SES CLI interface (cnfcon and addcon).
Symptom
On an SES controller ABR connection ICR may be greater than PCR or less than MCR when VSVD (internal and/or external) is on.
Conditions
Modify or add a connection with ICR less than MCR or greater than PCR and VSVD on.
Workaround
Do not add or modify an ABR connection to have MCR to be greater than the ICR or the PCR to be less than the ICR if VSVD is on.
Further
The SES CLI should enforce the requirement that MCR <= ICR <= PCR when VSVD is enabled.
|
CSCea42668
|
Headline
CIT40:while port dn-in-prog, admin state change up to dn after switch.
Symptom
After switchover, the Admin_st of pnport change from up to down at newly active PXM.
Conditions
1. configure nni port down and up, the port should be "down in progress" and "up". 2. issue switchover. 3. the Admin_st of pnport change from up to down at newly active PXM.
Workaround
None.
|
CSCea74459
|
Headline
Invalid entries in atm_connection for SES endpoints.
Symptom
CWM does not show newly added connections on SES after upgrade.
Conditions
After upgrading new version, the newly added connection's transaction id correctly on ram, but not on disk (transaction id is zero). After resetsys, the newly added transaction id will become zero. CWM database table (atm_connection) has invalid entries for SES endpoints.
Workaround
None.
|
CSCea78204
|
Headline
CIT40: SES node stays in mem and leg congestion.
Symptom
After stop script of down/up all pnports at node, observe the orion node stays in both mem and leg congestion.
Conditions
In test network, there are 92k SPVC connections in SES node. using call loading from adtech to pump P2P and P2MP SVC call. Execute script of down/up all pnports, and after stop the script then observe both mem and leg congestion flag set to on at SES.
Workaround
Execute resetcd or resetsys.
|
BXM Firmware MFX Release Notes
The sections that follow provide information about the BXM MFX firmware.
About the Firmware MFX
BXM Firmware version M.F.X. supports all the existing interfaces and models of BXM hardware. The following table describes the hardware revisions supported for BXM firmware version M.F.X.
Front Cards
Table 6 describes the different types of BXM front cards.
Table 6 BXM card cards
Model Num
|
Description
|
FW model
|
HW Rev
|
FW Rev
|
BXM-155-4
|
4 port OC3 Line Module (Front Card)
|
F
|
B
|
MFX
|
BXM-155-8
|
8 port OC3 Line Module (Front Card)
|
F
|
B
|
MFX
|
BXM-622
|
1 port OC12 Line Module (Front Card)
|
F
|
D
|
MFX
|
BXM-622-2
|
2 port OC12 Line Module (Front Card)
|
F
|
D
|
MFX
|
BXM-T3-8
|
8 port T3 Line Module (Front Card)
|
F
|
B
|
MFX
|
BXM-T3-12
|
12 port T3 Line Module (Front Card)
|
F
|
B
|
MFX
|
BXM-E3-8
|
8 port E3 Line Module (Front Card)
|
F
|
B
|
MFX
|
BXM-E3-12
|
12 port E3 Line Module (Front Card)
|
F
|
B
|
MFX
|
BXM-155-8DX
|
8 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-155-8D
|
8 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-155-4DX
|
4 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-155-4D
|
4 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-622-2DX
|
2 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-622-2D
|
2 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-622-DX
|
1 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-T3-12EX
|
12 port T3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-T3-12E
|
12 port T3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-T3-8E
|
8 port T3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-E3-12EX
|
12 port E3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-E3-12E
|
12 port E3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-E3-8E
|
8 port E3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
Front Card for APS Compatibility
Table 7 describes the different types of BXM front cards that are compatible with APS.
Table 7 BXM Front Cards with APS Compatibility
Model Num
|
Description
|
FW model
|
HW Rev
|
FW Rev
|
BXM-155-4
|
4 port OC3 Line Module (Front Card)
|
F
|
C
|
MFX
|
BXM-155-8
|
8 port OC3 Line Module (Front Card)
|
F
|
C
|
MFX
|
BXM-622
|
1 port OC12 Line Module (Front Card)
|
F
|
E
|
MFX
|
BXM-622-2
|
2 port OC12 Line Module (Front Card)
|
F
|
E
|
MFX
|
BXM-155-8DX
|
8 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-155-8D
|
8 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-155-4DX
|
4 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-155-4D
|
4 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-622-2DX
|
2 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-622-2D
|
2 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BXM-622-DX
|
1 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFX
|
BackCards
Table 8 describes the different types of BXM back cards.
Table 8 BXM Back Cards
Model Num
|
Description
|
HW Rev
|
FW Rev
|
MMF-155-4
|
4 port multi-mode fiber back card
|
A
|
—
|
MMF-155-8
|
8 port multi-mode fiber back card
|
A
|
—
|
SMF-155-4
|
4 port single-mode fiber intermediate-reach back card
|
A
|
—
|
SMF-155-8
|
8 port single-mode fiber intermediate-reach back card
|
A
|
—
|
SMFMR-155-4
|
4 port single-mode fiber long-reach back card
|
A
|
—
|
SMFMR-155-8
|
4 port single-mode fiber long-reach back card
|
A
|
—
|
SMF-622
|
1 port intermediate-reach OC12 back card
|
A
|
—
|
SMF-622-2
|
2 port intermediate-reach OC12 back card
|
A
|
—
|
SMFMR-622
|
1 port long-reach OC12 back card
|
A
|
—
|
SMFMR-622-2
|
2 port long-reach OC12 back card
|
A
|
—
|
XLR-622
|
1 port extra long-reach OC12 back card
|
A
|
—
|
XLR-622-2
|
2 port extra long-reach OC12 back card
|
A
|
—
|
BPX-T3/E3-12
|
12 port T3/E3 back card
|
A
|
—
|
BPX-T3/E3-8
|
8 port T3/E3 back card
|
A
|
—
|
RDNT-LR-622-2
|
2 port long-reach OC12 redundant back card
|
A
|
—
|
RDNT-SM-622-2
|
2 port intermediate reach OC12 redundant back cards
|
A
|
—
|
RDNT-SM-622
|
1 port intermediate reach OC12 redundant back cards
|
A
|
—
|
RDNT-LR-155-8
|
8 port long-reach OC3 redundant back cards
|
A
|
—
|
RDNT-SM-155-4
|
4 port intermediate-reach OC3 redundant back cards
|
A
|
—
|
RDNT-SM-155-8
|
8 port intermediate-reach OC3 redundant back cards
|
A
|
—
|
New Features supported in BXM Firmware MFX
•VSI bandwidth overbooking - CSCdy72578
•ECAC support added on BXM for VSI connections - CSCdw83279
New Features supported in BXM Firmware MFW
Bug fix only.
New Features supported in BXM Firmware MFV:
VC Merge support added.
New Features supported in BXM Firmware MFU
•Virtual Trunk Oversubscription
•VC Shaping
New Features supported in BXM Firmware MFT
Bug fix only.
Note MFT includes a fix for the bug CSCdw54957.
New Features supported in BXM Firmware MFR
Bug fix only.
New Features supported in BXM Firmware MFP
Configurable number of ILMI traps
New Features supported in BXM Firmware MFN
•F4-F5 Mapping on ports and F4 AIS detection on Virtual Trunks
•Support for E2E tstpingoam
•Support for O.151 OAM standard
New Features supported in BXM Firmware MFM
Bug fix only.
New Features supported in BXM Firmware MFK
LCN CAC with policing parameters set by PNNI controller. (Look at "Notes Cautions & Clarifications" for warnings).
New Features supported in BXM Firmware MFJ
Bug fix only.
New Features supported in BXM Firmware MFH
•Dynamic partitioning feature is supported on BXM card by default. Remote Shell Feature through the BCC CLI provides a mechanism to turn off this feature.
•SPVC feeder support.
New Features supported in BXM Firmware MFF
Use of separate qbin to guarantee bandwidth resources for the control channels of VSI controllers.
New Features supported in BXM Firmware MFE
Support for APS 1:1 added for VSI
Note MFE is a bug fix release only.
New Features supported in BXM Firmware MFD
MFD is a bug fix release only.
New Features supported in BXM Firmware MFC
1. Support for SES (PNNI controller).
2. BootCore enhancement to support multi-vendor flash-SIMMs.
3. 1 msec granularity for tstdelay measurement.
New Features supported in BXM Firmware MFB
• Multiple VSI (2.2) partition feature. Three partitions are supported.
•Hitless Connection Density Upgrade for BXM.
•SCR and PCR policing at less than 50 CPS for T3/E3 BXMs.
•Control Traffic Shaping.
New Features supported in BXM Firmware MFA
Multiple VSI (2.2) partition feature (two partitions).
Note This is the first release in MF branch of firmware.
New Features supported in BXM Firmware MEC
There are no new features in release MEC.
New Features supported in BXM Firmware MEB
There are no new features in release MEC.
New Features supported in BXM Firmware MEA
•VSI version 2.2 (single partition).
•ITUT Annex B and configurable Signal Degrade (SD) and Signal Failure (SF) thresholds for SONET Linear APS on BXM-OC3 and BXM-OC12 (1+1, 2 card, 1:1).
The current default thresholds are as follows:
BIP count
|
Condition
|
10^-4
|
SF detected
|
10^-5
|
SD detected & SF clear
|
10^-6
|
SD clear & SF clear
|
New Features supported in BXM Firmware MDA
•Support for Virtual Trunking
•Support for BXM Multi-Level Channel Statistics
•SONET Linear APS on BXM-OC3 and BXM-OC12 (1+1, 2 card, 1:1)
•Support for card based LMI and ILMI
•Upgrade from VSI 1.1 to VSI 2.2 is supported in this release. See the upgrade section on next page
Special Installation/Upgrade Requirements
APS Issues
If APS feeder trunks are configured on an MGX 8850 (PXM1), but the BPX node you are configuring does not support APS, use the following procedure to upgrade the BXM to MFX from release MEK and lower.
Step 1 Change the MGX8850 (PXM1) feeder to use APS1+1 unidirectional, and disable K1K2 processing. You may need to delete APS and then add it again.
Step 2 On the BPX, temporarily configure unidirectional mode.
Step 3 At the MGX8850 (PXM1), enter the dspapsln command to verify that both lines are OK.
Step 4 If both lines are OK, delete the APS line on the BPX.
Step 5 Upgrade the BXM cards as if they are using Y-cable redundancy.
Step 6 After both BXM cards are upgraded to the MFX firmware, add APS back onto the BPX.
Step 7 Reconfigure both MGX8850 (PXM1) and BPX to use the appropriate APS configurations.
To upgrade a BXM card pair in Y-red configuration, complete the following steps:
Step 1 Upgrade the standby card with the MFA or above firmware version. Wait for all of the configuration to be downloaded into the card.
Step 2 Do a switchyred to switch to the card with firmware MFA or above version.
Step 3 Burn the other card with the desired version MFA or above firmware. Follow the standard firmware upgrade procedure for downloading and burning the firmware into the cards.
Step 4 If BCC SWSW version is 9.1.18 and dspnovram shows 0 or 4 for Number of Channel Stats, go directly to MFC or above versions from MCC.
For APS (1+1) MEx or MFA image versions are not to be treated as compatible with MFx (minus MFA) image versions. During an upgrade procedure from MEx or MFA image to MFx (minus MFA) image, both cards must be upgraded to the MFx (minus MFA) image with minimal interval between them.
The incompatibility is due to APS intercard messages from one end not being recognized by the other end. See bug CSCdu67053 for the symptoms caused by this incompatibility.
Note Intra-MFx (minus MFA) and intra-MEx upgrades are compatible.
Channel Stats Issues
Use one of the following upgrade procedures if you are upgrading firmware on OC3, 1 port OC12 BXM cards on which the stats level is greater than 1.
Use the following procedures to upgrade from firmware revision MEA or higher.
Step 1 Upgraded the switch software to Release 9.2.30 or higher.
Step 2 Upgrade the BXM firmware to MFX.
Use the following procedures to upgrade from any firmware revision lower than MEA.
Note The following procedure will avoid card mismatch.
Step 1 Upgrade the firmware to MEC.
Step 2 Upgrade the switch software to Release 9.2.30 or higher.
Step 3 Upgrade the BXM firmware to MFX.
Ensure that there are no interruptions while the firmware is being upgraded. If the BXM resets in the middle of an upgrade, that card will be stuck in the core or failed state, and the dspcds command will report the card as FAILED. This state can be recovered by re-burning the firmware into the card.
Note A blinking yellow LED on the front of the BXM means that the card is stuck in the core state. A solid red LED on the front of the BXM means that the card is stuck in the failed state.
Features Obsoleted
The following features are obsolete in the MFX firmware:
•VSI 1.0 is obsoleted by VSI 2.2 in the MDA release onwards.
•From versions MFJ to MFN channel statistics level 0 is no longer supported for BXM-155-4, BXM-155-8, BXM-622, BXM-622-2, BXM-T3-8, BXM-T3-12, BXM-E3-8, BXM-E3-12 models. MFN onwards conditional support for stats level 0 is revoked. Please see the Notes, Cautions & Clarifications section point 13 for more details.
•In all other models channel statistics level 0 is supported by all firmware versions i.e. (BXM-155-8DX, BXM-155-8D, BXM-155-4DX, BXM-155-4D, BXM-622-2DX, BXM-622-2D, BXM-622-DX, BXM-T3-12EX, BXM-T3-12E, BXM-T3-8E, BXM-E3-12EX, BXM-E3-12E, BXM-E3-8E)
Notes, Cautions & Clarifications
•BXM Model F firmware is intended for use with release 9.3 or later switch software. Do not use BXM Model F firmware to upgrade BXMs while you are upgrading the switch software from release 9.2 to 9.3. BXM Model F firmware has not been tested for compatibility with release 8.4, 8.5, and 9.1 switch software. It is compatible with IOS version 12.05t2 or greater for MPLS.
•BXM firmware MFX and later can be used for release 9.4.00 switch software.
•MFE is a not on CCO, as it an SES specific release.
•Protection Switching based on BER on BXM may not comply to standards. The GR-253 & ITU-T G.783 requires that switching be completed within 60 msec from the time the error starts. BXM is unable to detect BER threshold crossing until the next poll, which occurs every 250 msec. Thus, switching time may be up to 250 msec under certain circumstances.
•In APS 1+1 default configuration, both backcard LEDs show green when primary card is active and selection is from PROT line. When primary card is active and it is selecting from PROT, PROT backcard should be green, since it is carrying traffic. WORK backcard should also be green since that is the physical path for the primary (and active) card to pass traffic. So backcard LED green means the backcard is directly or indirectly carrying traffic and pulling the backcard will cause traffic disruption. (CSCdm53430)
•In APS 1+1 default configuration, when a manual W->P is on and the switchyred command is issued, a manual W->P event is logged. By default, when the switchyred command is entered, the new active card comes up in the "clear" state. But in this case since there is a manual W->P on, the APS line switches to PROT and the switching is logged. (CSCdm53404)
•In APS 1+1 default configuration if the selected line is PROT and last user request is clear and a switchyred is issued, line switches to WORK. If the last user request is "clear", full automatic APS switching is in effect with the working line being active by default. When there is no last user switch request to switch to any particular line, the working line will become active. (CSCdm53420)
•When APS Annex B is added to local end which has the Secondary card active, the APS trunk goes into Comm Failure for few seconds and then clears. If Secondary card is active, then do a switchyred to make Primary card active and then add APS Annex B. (CSCdm46359).
•MFK and above versions support LCN CAC for class of services. Controller will reserve some LCNs for control VC as default. These reserved LCN can not be used by any class of service any more in MFX. If all the LCNs for the partition has been used in a version earlier than MFK, after MFX is updated in the switch, some connections may not be added because they try to use LCNs reserved for control VC which is not allowed. You need to configure more LCNs for the partition to make sure there is enough LCNs for all the connections.
•The OC-3 MultiMode Fiber backcards do not support Y-cable redundancy.
• APS 1:1 is not supported for VSI in versions before MFE. (Bug CSCdp42996) APS 1:1 should not be configured on ports intended to be used by PNNI or MPLS, as after switchover traffic flow is stalled on the protection line for releases before MFE. However in MFE and above, this problem is fixed.
• Total BW allocated to all VSI partitions on a BXM should not be more than an OC12 rate (i.e., 1412832 cells/s). The current BCC switch software allows you to configure more than an OC12 rate, in which case all the PNNI connection commit requests would be NACKed by BXM
• In firmware versions prior to MFF signalling bandwidth for SES controller was not guaranteed. In MFF and above the signalling Qbin feature has been added (with Sw/Sw 9.3.10 and above and SES image 1.0.10 and above) to guarantee signalling bandwidth.
• Stats level 0 for legacy BXM cards was obsoleted in Model F releases until MFN. But in version MFP and above conditional support Stats Level 0 for legacy cards is revoked. The condition is that stats level 0 is not supported if there is any VSI configuration on the card. If a card was configured with Stats Level 0 with VSI enabled in a previous release of firmware (model C or E), upon upgrading to MFP or above revisions, mismatch will occur on legacy cards. Customers will have to reconfigure their card to Stats Level 1 or above before upgrading, otherwise VSI operation will be impacted. However the BXME (enhanced cards) support all stats levels unconditionally with all valid configurations, models and releases.
•Excessive BIP-8 error rates (10-3) which escalate into unavailable seconds (UAS) are now reported to Switch Software as red alarms. This feature is not configurable, and may cause failed connections and rerouted trunks in configurations where APS is not enabled, alternate trunk routes do not exist or on UNI ports. This feature is not active when APS is configured and enabled.
Known Anomalies
Table 9 lists the known anomalies in the BXM firmware.
Table 9 Known Anomalies in the BXM firmware
Bug ID
|
Description
|
Apply to SES
|
CSCdx52484
|
Symptom:
CBR traffic got dropped on ENNI link on BPX side where there is congestion.
Conditions:
resetcd of BXM can solve the problem.
Workaround:
Unknown.
|
No
|
CSCdx79141
|
Symptom:
Channel allocation inconsistency between BPX and SES.
Conditions:
Have only 1 part. first (Max. lcn > Min.),add conns. > min. Add more parts such that sum(Min.s)>Max(max.).
Workaround:
None.
|
Yes
|
Bugs Fixed in MFX
Table 10 lists the bugs that were fixed in the MFX firmware.
Table 10 Bugs Fixed in MFX Firmware
Bug ID
|
Description
|
CSCdw76023
|
Symptom:
For APS 1:1 intracard configuration, dspapsln command keeps showing false and misleading alarm APS missing card.
Conditions:
APS 1:1 intracard setup using R (redundant) designated backcard.
Workaround:
Do not use an R -designated backcard when configuring APS 1:1 intracard setup.
Use just the normal backcard. It is just a false alarm. All APS functionality should still be working correctly.
|
CSCdw95063
|
Symptom:
dspapsln doesn't show card missing on standby even though the standby card has been removed. dspapsln shows OK even though standby BXM card is removed to cause a switchover to the newly active card.
Conditions:
Remove the active BXM to cause the switchover to the newly active card in an APS 1+1 configuration setup.
Workaround:
Insert back the standby BXM card.
|
CSCdx28781
|
Symptom:
When bit errors happen on a line, all the connections provisioned on the line fail.
Conditions:
MFM onwards (There is a code change went into firmware image MFM, which puts the line into Path AIS as long as UAS-P condition persists. This change is good for trunks as alternate routes could be chosen. But on lines, especially when they are error prone, there is no choice but to keep using the line, application might slow down (but at least connection does not get failed).
Workaround:
Use images before MFM or replace the buggy physical cable.
|
CSCdx40378
|
Symptom:
When sending F5 OAM end to end flows through a DACS SPVC, only the egress counters of dspconstats increment. This true for F5 end to end AIS, or F5 end to end loopback.
Conditions:
This affects OAM cell counting on all SPVC connections. It will occur with firmware MFW or lower revision.
Workaround:
None.
|
CSCdx50089
|
Symptom:
ILMI did not update its neighbor's IP address and IfName to be "N/A", when its physical link on which it was running went down. dspnebdisc would show the previous neighbor's IP address and IfName in this situation.
Conditions:
The physical link on which ILMI was running went down.
Workaround:
Reset the card will clear the old information.
|
CSCdx72292
|
Symptom:
Commit connection request is failed due to NAK from BXM, while still a lot of available bandwidth at partition level.
Conditions:
1. Single/Multiple partitions on a interface enabled.
2. The bandwidth common pool of this interface is zero.
3. At least in one partition, sum of (cos_min_bw) > part_min_bw, due to the round up when applying the policy parameters -minbw to get cos_min_bw.
Workaround:
When configuring the multiple partitions, gives at least 20 cells in common pool. The work around for CSCdv03058 applies to this problem.
See CSCdv03058 for detail workaround explanation.
|
CSCdy16927
|
Symptom:
BXM LMI clears Abit alarms on SPVC feeder after switchcc or switchyred.
Conditions:
SPVC feeder1 === BPX1/SES1=== BPX2/SES2 === SPVC feeder **
1. The connection segment in the BPX/SES network is down.
2. The corresponding segment in the SPVC feeder is in Abit alarm
3. After a switchcc or a BXM switchyred on BPX1, the BXM LMI session at "**" tells SPVC feeder1 to clear the Abit alarm on the segment corresponding to the downed VSI connection in the BPX/SES network.
Workaround:
None.
|
CSCdy57435
|
Symptom:
Fatal PRFD Pending error has been seen at BXM card. (SIMBA errors excess its threshold).
Conditions:
Most likely, it happens during FW/SW upgrade.
Workaround:
None.
|
CSCdy75277
|
Symptom:
A pnport stuck is in down state after being added and configured
Conditions:
Add and configure pnport on a freshly added trunk/port. Delete all the configuration and down all interfaces, then newly add and configure the pnport from scratch.
Workaround:
Unknown
|
CSCdy80205
|
Symptom:
When physical interface in alarm (LOS), dsppnport shows the "operstatus" as up in SES.
Conditions:
When SES is running 3.0(10.0) or later, even if the physical interface is in alarm (LOS), if ILMI is enabled, with out configuring signalling type (NNI or UNI) in SES, the "operstatus" of interface is shown as UP.
With BXM Image MFW or prior.
Workaround:
Configure signalling type in SES.
|
CSCdy89521
|
Symptom:
The AAL5 Feeder attached to the BPX routing hub becomes unreachable after a delshelf command was issued on the BPX, even though there are no existing connections on either the feeder or the BPX.
Conditions:
BXM runs the LMI protocol.
Workaround:
None.
|
CSCdz49797
|
Symptom:
Doing a switchyred on BXM causes AXSM connection to go into Abit/AIS alarm.
Conditions:
A switchyred on BXM card running XPVC in a mixed MGX8220 BPX MGX1 MGX45 network can go into alarm, and then the alarm will not clear. Typically a transition outside of the PNNI network (a switchyred on the BPX in this case) can cause the ingress port to generate an AIS alarm, which it sends into the PNNI network and is received by CPE at the other end. Because the AIS is incorrect, there's never any indication to the ingress port that it should clear the alarm.
Workaround:
Executing dncon/upcon on the AXSM end which is generating switch side Tx AIS (if that is the master connection) If the problem is on the slave end need to delete and re-add the connection.
|
CSCin33357
|
Symptom:
After burning the MFW image, the BXM enhanced card went to resetting.
Conditions:
BXME card with stats lvl 0 and VSI connections.
Workaround:
Do not use stats lvl 0 for BXME card.
|
CSCdz60041
|
Symptom:
BPX may not be able to recover clock from the line with PLCP framing configuration.
Conditions:
BPX may experience clock recovery issues when recovering clock from the line connected to other vendor equipment.
Workaround:
None.
|
Bugs Fixed in MFW
Table 11 lists the bugs that were fixed in the MFW firmware.
Table 11 Bugs Fixed in MFW Firmware
Bug ID
|
Description
|
CSCdw80712
|
Symptom:
1:1 APS allows manual/forced switchapsln P->WLine.
Conditions:
1. 1:1 APS with Bi-Dir configured; remote is AXSM/B.
2. Manual switchaps W->PLine from AXSM/B.
3. Forced switchaps P->WLine from BXM.
Workaround:
None.
|
CSCdx45385
|
Symptom:
BXM did not update SES with the latest available cos level LCN when there is cnfrsrc LCN resources (LCN) change on this partition (part_min_lcn, part_max_lcn).
Conditions:
1. A PNNI partition has been configured with some connections up. dsppnportrsrc reports the correct available lcn for each cos level.
2. Do cnfrsrc on this partition, to change the min_lcn and max_lcn at partition level. The available lcn at cos level in SES dose not get updated.
Workaround:
Add a con or down a con to trigger the update.
|
CSCdx55794
|
Symptom:
BXM incorrectly sends back LMI version 4 to IGX AAL5 feeder, while it does not support LMI version 4.
Conditions:
1. IGX AAL5 feeder is added to a BXM feeder trunk in the BPX.
2. IGX feeder LMI is running LMI version 4, and talk to BXM LMI.
Workaround:
None
|
CSCdx56537
|
Symptom:
Setting cnftrkparm 9 2500/15000 causes trunk failure.
Conditions:
BXM running MFU firmware. Found in Lab environment but likely to also be found in a Live network if these trunkparm values are used and the trunk passes over another medium such as a TDAX or SDH backbone.
Workaround:
Set cnftrkparm 9 2500/10000 which is the default for STM1. Don't use the values 2500/15000 for cnftrkparm 9. Tests have yet to show if this would effect other values but default settings have been confirmed problem free.
|
CSCdx59080
|
Symptom:
Customer is performing tests of MFU firmware prior to deployment in live network and has found that when a BXM trunk is configured for loop clock yes at both ends it remains in a looped back state when the BXM is reset by command resetcd ? h.
Conditions:
BXME trunk needs to be configured for loop clock yes and the BXM card be reset. Tests showed that causing a LOS or resetting the card again would not recover the trunk.
Workaround:
Issue cnftrk and change none of the parameters by stepping through them.
|
CSCdy01870
|
Symptom:
SIMBA reset card errors logged due to PRFD Pending Errors
Conditions:
BXM image MEE and SWSW image 9.3.00
Workaround:
None
|
CSCdy01951
|
Symptom:
Unnecessary alarms are triggered when BXM sends slot errors to SWSW.
Conditions:
The FW adds all slot errors before sending them to BCC. There are situations when the number of traffic related slot errors will trigger unnecessary alarms on SWSW. These alarms will be suppressed.
Workaround:
None
|
CSCdy05515
|
Symptom:
Current BXM firmware only support a few stats counters. In order to enhance customer operation and maintenance capability, a few new stats counters have been added. The detail description about the new created stats and associated CLI cmd and MIB can be found in the latest VSI document. Please also refer to DDTS case CSCdy05597 (SES and MIBs).
Conditions:
All previous FW don't support the new connection stats.
Workaround:
N/A
|
CSCdy13987
|
Symptom:
Newly added routed SPVC carries counter values of previously deleted SPVC.
Conditions:
Delete routed SPVC. Then re-add the SPVC with same VPI/VCI values.
Workaround:
Problem is fixed in MFW (MF20).
|
Logic to calculate actual cell transmission rate in a BXM card is as follows (CSCdm94372):
if (configured cell rate == full line cell rate) then
transmitted cell rate = full line cell rate
else
transmitted cell rate = from equation below or from table 1
Example 1 Calculation of Actual Cell Transmission Rate in a BXM Card
If a trunk is configured at 100,000 CPS, the actual transmitted cell rate is then 98,013 CPS any traffic sent over 98,013 CPS would be discarded.
Therefore, only rates in the table or computed from the equation should be used.
Otherwise cell loss may be experienced.
Table 12 lists the BXM card's cell transmission rates.
Table 12 BXM Transmitted Cell Rate
1464865
|
56552
|
28832
|
19348
|
14559
|
11670
|
9738
|
8355
|
733860
|
54458
|
28278
|
19097
|
14416
|
11579
|
9674
|
8308
|
489558
|
52513
|
27744
|
18852
|
14277
|
11488
|
9611
|
8261
|
367288
|
50703
|
27231
|
18614
|
14139
|
11399
|
9549
|
8215
|
293888
|
49013
|
26736
|
18381
|
14005
|
11311
|
9487
|
8169
|
244938
|
47432
|
26258
|
18154
|
13872
|
11225
|
9426
|
8124
|
209966
|
45950
|
25798
|
17933
|
13743
|
11140
|
9366
|
8079
|
183733
|
44558
|
25353
|
17717
|
13616
|
11056
|
9307
|
8035
|
163327
|
43247
|
24923
|
17506
|
13491
|
10974
|
9248
|
7992
|
147001
|
42012
|
24508
|
17300
|
13368
|
10892
|
9190
|
7948
|
133642
|
40845
|
24106
|
17099
|
13248
|
10812
|
9133
|
7906
|
122509
|
39741
|
23717
|
16902
|
13129
|
10733
|
9077
|
7863
|
113088
|
38695
|
23341
|
16710
|
13013
|
10656
|
9021
|
7822
|
105012
|
37703
|
22976
|
16522
|
12899
|
10579
|
8966
|
7780
|
98013
|
36761
|
22623
|
16339
|
12787
|
10503
|
8912
|
7739
|
91889
|
35864
|
22280
|
16159
|
12677
|
10429
|
8858
|
7699
|
86485
|
35010
|
21947
|
15983
|
12568
|
10355
|
8805
|
7659
|
81681
|
34196
|
21625
|
15812
|
12462
|
10283
|
8753
|
7619
|
77383
|
33419
|
21311
|
15643
|
12357
|
10212
|
8701
|
7580
|
73515
|
32676
|
21007
|
15479
|
12254
|
10141
|
8650
|
7541
|
70014
|
31966
|
20711
|
15318
|
12153
|
10072
|
8599
|
7502
|
66833
|
31286
|
20423
|
15160
|
12053
|
10003
|
8549
|
7464
|
63927
|
30634
|
20143
|
15005
|
11955
|
9936
|
8500
|
7427
|
61264
|
30009
|
19871
|
14853
|
11859
|
9869
|
8451
|
7389
|
58814
|
29409
|
19606
|
14705
|
11764
|
9803
|
8403
|
7352
|
Firmware Filenames and Sizes
BXMMFX.000
|
65536
|
BXMMFX.001
|
65536
|
BXMMFX.002
|
65536
|
BXMMFX.003
|
65536
|
BXMMFX.004
|
65536
|
BXMMFX.005
|
65536
|
BXMMFX.006
|
65536
|
BXMMFX.007
|
65536
|
BXMMFX.008
|
65536
|
BXMMFX.009
|
65536
|
BXMMFX.010
|
65536
|
BXMMFX.011
|
65536
|
BXMMFX.012
|
65536
|
BXMMFX.013
|
65536
|
BXMMFX.014
|
65536
|
BXMMFX.015
|
65536
|
BXMMFX.016
|
65536
|
BXMMFX.017
|
65536
|
BXMMFX.018
|
65536
|
BXMMFX.019
|
65536
|
BXMMFX.020
|
65536
|
BXMMFX.021
|
65536
|
BXMMFX.022
|
65536
|
BXMMFX.023
|
65536
|
BXMMFX.024
|
65536
|
BXMMFX.025
|
48064
|
BXMMFX.026
|
14
|
BXMMFX.027
|
2
|
BXMMFX.IMG
|
784
|
BXMMFX.img
|
784
|
Related Documentation
This "Related Documentation" section describes the technical manuals and release notes listed in the "Guide to Cisco Multiservice Switch Documentation." That guide, part DOC-7815358=, shipped with your product.
The following Cisco publications contain information related to the operation of this product and associated equipment in a Cisco WAN switching network.
Note Starting in April 2003, the documents listed in the "Related Documentation" section will be available online only.
There are several ways you can find these documents online:
•In your browser's URL field, enter www.cisco.com. In the top right search field, enter the document part number (for example, OL-3837-01) and click on GO.
•For all documents, in your browser's URL field, enter http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm. Look for the switch name, then release number (for example, MGX 8850 (PXM1E), then Release 4).
Cisco WAN Manager Release 12
Table 13 lists the product documentation for the Cisco WAN Manager (CWM) network management system for Release 12.
Table 13 Cisco WAN Manager Release 12 Documentation
Title
|
Description
|
Cisco WAN Manager Installation Guide for Solaris 8, Release 12
OL-3837-01
|
Provides procedures for installing Release 12 of the CWM network management system and Release 5.4 of CiscoView on a Solaris 8 platform.
|
Cisco WAN Manager User's Guide, Release 12
OL-3838-01
|
Describes how to use the CWM Release 12 software, which consists of user applications and tools for network management, connection management, network configuration, statistics collection, and security management.
|
Cisco WAN Manager SNMP Service Agent Guide, Release 12
OL-3840-01
|
Provides information about the CWM Simple Network Management Protocol Service Agent, an optional adjunct to CWM that is used for managing Cisco WAN switches using SNMP.
|
Cisco WAN Manager Database Interface Guide, Release 12
OL-3839-01
|
Provides information about accessing the CWM Informix OnLine database that is used to store information about the network elements.
|
SES PNNI Release 4
Table 14 lists the product he product documentation for the understanding, the installation, and the operation of the Service Expansion Shelf (SES) Private Network-to-Network Interface (PNNI) Controller.
Table 14 SES PNNI Controller Release 4 Documentation
Title
|
Description
|
Cisco SES PNNI Controller Software Configuration Guide, Release 3*
DOC-7814258=
|
Describes how to configure, operate, and maintain the SES PNNI Controller.
|
Cisco SES PNNI Controller Command Reference, Release 3*
DOC-7814260=
|
Provides a description of the commands used to configure and operate the SES PNNI Controller.
|
PNNI Network Planning Guide for MGX and SES Products
OL-3847-01
|
Provides guidelines for planning a PNNI network that uses Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), Cisco MGX 8950, and Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 series switch requires an SES for PNNI route processing.
|
* This book was last updated for Release 3.
|
Cisco WAN Switching Software Release 9.4
Table 15 lists the product documentation for the installation and operation of the Cisco WAN Switching Software Release 9.4.
Table 15 Cisco WAN Switching Release 9.4 Documentation
Title
|
Description
|
9.4.00 Version Software Release Notes Cisco WAN Switching System Software
OL-3189-01
|
Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
|
Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30
DOC-7812907=
|
Provides a general description and technical details of the Cisco BPX broadband switch.
|
Cisco WAN Switching Command Reference, Release 9.3.30
DOC-7812906=
|
Provides detailed information on the general command line interface commands.
|
Cisco IGX 8400 Series Installation Guide
OL-1165-05
|
Provides hardware installation and basic configuration information for Cisco IGX 8400 Series switches that are running Switch Software Release 9.3.30 or later.
|
Cisco IGX 8400 Series Provisioning Guide
OL-1166-03
|
Provides information for configuration and provisioning of selected services for the Cisco IGX 8400 Series switches that are running Switch Software Release 9.3.30 or later.
|
Cisco IGX 8400 Series Regulatory Compliance and Safety Information
DOC-7813227=
|
Provides regulatory compliance, product warnings, and safety recommendations for the Cisco IGX 8400 Series switch.
|
Conventions
This publication uses the following conventions.
Command descriptions use these conventions:
•Commands and keywords are in boldface.
•Arguments for which you supply values are in italics.
•Required command arguments are inside angle brackets (< >).
•Optional command arguments are in square brackets ([ ]).
•Alternative keywords are separated by vertical bars ( | ).
Examples use these conventions:
•Terminal sessions and information the system displays are in screen font.
•Information you enter is in boldface screen font.
•Nonprinting characters, such as passwords, are in angle brackets (< >).
•Default responses to system prompts are in square brackets ([ ]).
Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.
Caution Means
reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.
Tips Means the following information will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver.
Warning This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, you must be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. (To see translated versions of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied the product.)
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:
http://www.cisco.com
International Cisco websites 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 regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.
Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html
All users can order monthly or quarterly subscriptions through the online Subscription Store:
http://www.cisco.com/go/subscription
Ordering Documentation
Note Starting in April 2003, the documents listed in the "Related Documentation" section will be available online only.
There are several ways you can find these documents online:
•In your browser's URL field, enter www.cisco.com. In the top right search field, enter the document part number (for example, OL-3837-01) and click on GO.
•For all documents, in your browser's URL field, enter http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm. Look for the switch name, then release number (for example, MGX 8850 (PXM1E), then Release 4).
You can find instructions for ordering other Cisco documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:
http://www.cisco.com/en/US/partner/ordering/index.shtml
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
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 comments by using the response card (if present) 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-9883
We 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:
•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
To obtain customized information and service, you can self-register on Cisco.com at this URL:
http://tools.cisco.com/RPF/register/register.do
Technical Assistance Center
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: the Cisco TAC website and the Cisco TAC Escalation Center. The type 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:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration. There is little or no impact to your business operations.
•Priority level 3 (P3)—Operational performance of the network is impaired, but most business operations remain functional. You and Cisco are willing to commit resources during normal business hours to restore service to satisfactory levels.
•Priority level 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively impacted by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
•Priority level 1 (P1)—An existing network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Cisco TAC Website
The Cisco TAC website provides online documents and tools to help troubleshoot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:
http://www.cisco.com/tac
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/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation 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 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.
•The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:
http://www.ciscopress.com
•Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:
http://www.cisco.com/go/packet
•iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:
http://www.cisco.com/go/iqmagazine
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0304R
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
