Table Of Contents
3.0.10 Software Release Notes for the Cisco SES PNNI Controller
Contents
About Release 3.0.10
SES PNNI and SVC Controller
Feature Overview
Detailed Feature Information
System Requirements
Hardware Compatibility Matrix
Software Compatibility
Compatible Releases
Additional Deliverables
New and Changed Information for Release 3.0.10
SNTP
Priority Routing of Connections
Preferred Routing of Connections
Per Connection Based Utilization of SPVCs
Standards Based Path and Connection Trace
Single-ended SPVC/SPVP Configuration
100K Connections
SPVC and SVC real time statistics with MIB support
Upgrading the SES Node
Upgrading to a New Software Release
Special Installation and Upgrade Requirements
Upgrading from SES Release 1.0.14, 1.1.75, or 3.0 to Release 3.0.10
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 This Release
Problems Fixed in Release 3.0.10
Open Anomalies in Release 3.0
Open Anomalies in Release 1.1.75
Problems Fixed in Release 1.1.75
Problems Fixed in Release 1.1.70
Anomalies Status Changes for Release 1.1.70
Fixed Anomalies for Release 1.1.60
Related Documentation
Cisco WAN Manager Release 11
Service Expansion Shelf PNNI Controller Release 3
Cisco WAN Switching Software Release 9.3.40
Conventions
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Cisco TAC Web Site
Cisco TAC Escalation Center
3.0.10 Software Release Notes for the Cisco SES PNNI Controller
Contents
This document contains the following sections:
About Release 3.0.10
These release notes describe the system requirements, new and changed procedures, upgrade procedures, and limitations that apply to Release 3.0.10 of the Service Expansion Shelf (SES) controller. These notes also contain Cisco support information. The 3.0.10 software release supports the Cisco WAN switching products: Cisco BPX 8600 series with SES controller.
SES PNNI and SVC Controller
Release 3.0.10 of the SES controller is compatible with the Cisco BPX 8600 series software Release 9.3.30 and with the later 9.3 Releases. 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.
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 3.0.10) supports the following features:
•
SPVC and SVC real time statistics with MIB support
•SNTP
•Priority routing of connections
•Preferred routing of connections
•Standards based path and connection trace facilities
•Single-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 K LCN
•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 K connections (SVC+SVP+SPVC+SPVP) per node
•100 K max endpoints per node (if all 50 K 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
•Graceful upgrade on the SES controller from Release 1.0.14, Release l.1.75, and Release 3.0 to Release 3.0.10.
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 3.0.10, 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 3.0.10 of the SES controller.
Table 3 MGX Hardware Compatibility
Feeder
|
MGX 8850 R1
|
MGX 8220
|
Release
|
1.1.34
|
5.0.16
|
HW Cards
|
PXM-1
PXM1-2T3E3
PXM1-4OC3
PXM1-OC12
SRM-3T3
CESM-8E1
CESM-8T1
AUSMB-8E1
AUSMB-8T1
CESM-T3
CESM-E3
FRSM-8E1
FRSM-8T1
FRSM-HS2
FRSM-2CT3
FRSM-2T3
FRSM-2E3
FRSM-HS1/B
VISM-8T1
VISM-8E1
RPM
RPM-PR
|
FRSM-4T1/4E1/4T1-C/4E1-C
SRM-T1E1
SRM-3T3
CESM-4T1/4E1
CESM-8T1/8E1
AUSM-4T1/4E1
FRSM-8T1/8E1
AUSM-8T1/8E1
AUSMB-8T1/8E1
AUSMB-8T1/8E1
FRSM-HS1
FRSM-HS1/B
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 3.0.10 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
|
MFR
|
9.3.36
|
10.5.10
Patch 1
|
PXM1
|
3.0
|
pxm1_003.000.000.000_bt.fw
|
1.1.75
|
MFR
|
9.3.36
|
10.5.10
Patch 1
|
PXM1
|
3.0.10
|
pxm1_003.000.010.001_bt.fw
|
3.0.00
|
MFR
|
9.3.36
|
11.0.10
|
Compatible Releases
Release 3.0.10 of the SES controller is certified with the following releases:
•Graceful upgrade to Release 3.0.10 from Releases 1.0.14, 1.1.75, and 3.0.
•BPX SWSW Version 9.3.30 or later (see Software Compatibility Notes Matrix, first and second bullets)
•BXM firmware version MFR or later (see Software Compatibility Notes Matrix, first and second bullets)
•CiscoView Version 5.0
•Cisco WAN Manager (CWM) Release 11.0.10
•BCC-3-64
•BPX-BCC-4V or BPX-BCC-4V/B
•MGX 8850 Release 1, Release 1.2.11
•MGX 8220 Release 5.0.18
•SNMP MIB for Release 3.0.10 is sesmibs3010.tar
For further information on the BXM card, refer to the 9.3 Version Release Notes Cisco WAN Switching Software.
Additional Deliverables
The SES controller MIB is being provided with the delivery of Release 3.0.10 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.
New and Changed Information for Release 3.0.10
This section describes new and changed features in Release 3.0.10 of the SES controller.
SNTP
The SNTP feature enables BPX SES nodes with Time of Day (TOD) synchronization. This features allows BPX SES nodes to act as time of day (TOD) servers for the network. Accurate time of day service synchronized to Universal Time Coordinated (UTC). Through SNTP, the BPX SES node can synchronize to any SNTP/NTP time server. This provides accurate time for statistics and alarms generated on the switch and enables accurate synchronization of such events between switches. In a network of BPX SES and MGX switches, the TOD must be set on the BPX in order to be distributed consistently throughout the network.
Priority Routing of Connections
Use the priority routing feature to specify priority of connections, so that high priority connections will be established before low priority connections. During failures, high priority connections are released before low priority connections. High priority connections are rerouted and reestablished before low priority connections.
Preferred Routing of Connections
You can use the preferred routing feature to configure a connection's specific path through the network. Through this feature, a network operator bypasses automatic PNNI route selection. Connections are configured as either preferred routes or directed routes.
•A preferred route follows the configured path if it is available. If the preferred route is not available, the connection reverts to a PNNI-selected route.
•A directed route follows only the configured path. If the configured path is not available, the connection remains un-routed.
In this first implementation of Preferred routes, a set of preferred routes is configured and assigned reference numbers called "route sets." As connections are configured, they can be assigned to a particular route set. Each route set contains one preferred or directed route.
Preferred routes can be specified only across a single PNNI peer group. Preferred routes are interoperable with any standard PNNI implementation. You can control the selection of routes based on criteria other than those allowed in the route selection algorithms offered by PNNI.
Per Connection Based Utilization of SPVCs
The percentage utilization factor for SPVCs improves your control of network utilization for multiple tiers of service on networks supporting various trunk capacities. The percentage utilization factor is used for Connection Admission Control (CAC) for the connection. The actual bandwidth used for CAC is based on the following factors:
•PCR/SCR configured for the connection
•percentage utilization factor configured for the connection
•percent utilization configured for interfaces in the selected path
This feature enables service providers to provide differentiated overbooking on a per connection basis, rather than only on the uniform basis allowed by interface overbooking.
Standards Based Path and Connection Trace
You can determine the path taken by a connection through the path and connection trace feature. The path trace feature collects information about the path of new connections in the process of being established. The connection trace feature is collects information on existing connections that have already been established. The path and connection trace feature conforms to the ATM Forum standard PNNI Addendum for Path and Connection Trace, Version 1.0 af-cs-0141.000. Path and connection trace is a standards based feature that enables SES interoperability with other vendor equipment.
Single-ended SPVC/SPVP Configuration
You can configure both the endpoints of the SPVCs at the master end of the connection. In previous releases, you could only configure double-ended SPVCs, which meant you had to configure both the master and slave ends of a connection. In Release 3.0.10, the slave end of the connection is activated when the connection is established by the master end. This feature enables improved interoperability with other vendor equipment and management stations.
100K Connections
Release 3.0.10 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.
SPVC and SVC real time statistics with MIB support
In addition to existing SPVC and SVC real time stats CLI dspconstats, the new dspchancnt command displays more per SPVC and SVC real time stats counters. The dspconstats command is a Release 3.0.10 feature, and is described in these release notes.
Table 5 describes the new counters dsplayed by the dspchancnt command contains the following:
Table 5 New dspchancnt Command Counters
Ingress
|
Egress
|
IngRcvCLP0
|
EgrRcvCLP0
|
IngRcvCLP1
|
EgrRcvCLP1
|
IngXmtCLP0
|
EgrXmtCLP0
|
IngXmtCLP1
|
EgrXmtCLP1
|
IngCLP0CoSDiscard
|
EgrCLP0CoSDiscard
|
IngCLP1CoSDiscard
|
EgrCLP1CoSDiscard
|
IngCLP0UpcDiscard
|
—
|
IngCLP1UpcDiscard
|
—
|
Note The dspchancnt CLI is supported only on the BXM-E card. It is not supported on the legacy BXM card.
Note Both legacy BXM and BXM-E cards will continue supporting dspconstats CLI.
The CISCO-WAN-ATM-CONN-STAT-MIB file supports user access of real-time stats counters through the dspconstats and dspchancnt commands.
To display connection statistics for a port, enter the dspcconstats command as shown in the following
example:
SES-2.1.PXM.a > dspconstats <portid> <vpi> [<vci>]
Table 6 describes the dspconstats command parameters.
Table 6 dspconstats Command Parameters
Parameter
|
Description
|
portid
|
Portid interface number in the form of [shelf.]slot[:subslot].port[:subport].
|
vpi
|
Minimum VPI value for the connection.
0-4095
|
vci
|
Minimum VCI value for the connection. The default value for virtual path connections is 0.
Range: 0-65535.
|
Note You can use the dspconstats command to display connection statistics on legacy BXM or BXM-E cards, as well as PXM1 cards.
In the following example, the user displays the connection statistics for the Port ID 5.2, with a VPI and VCI of 100.
SES-2.1.PXM.a > dspconstats 5.2 100 100
PortId: 0.5:0.2:0 Vpi: 100 Vci: 100
Cells sent total remote ingress: 14506650
Cells discarded (CLP0) remote ingress:317357
Cells discarded (CLP1) remote ingress:372593
Cells discarded total remote ingress :689950
Cells sent total remote egress: 3739091
Cells discarded (CLP0) remote egress: 0
Cells discarded (CLP1) remote egress: 0
Cells discarded total remote egress : 0
PortId: 0.9:0.2:0 Vpi: 100 Vci: 100
Cells sent total local ingress: 4101541
Cells discarded (CLP0) local ingress: 0
Cells discarded (CLP1) local ingress: 0
Cells discarded total local ingress : 0
Cells sent total local egress: 4062654
Cells discarded (CLP0) local egress: 0
Cells discarded (CLP1) local egress: 0
Cells discarded total local egress : 0
To display statistical counters for a connection (channel), enter the dspchancnt command as shown in the following example:
SES-2.1.PXM.a > dspchancnt <portid> <vpi> [<vci>]
Table 7 describes the dspchancnt command parameters.
Table 7 dspconstats Command Parameters
Parameter
|
Description
|
portid
|
Portid Interface number, in the form of [shelf.]slot[:subslot].port[:subport].
|
vpi
|
Minimum VPI value for the connection.
0-4095
|
vci
|
Minimum VCI value for the connection. The default value for virtual path connections is 0.
Range: 0-65535.
|
Note The dspchancnt command can be used to display connections only on a BXM-E card.
In the following example, the user displays channel counters on a BXM-E for the port ID 5.2, with a VCI and VPI of 100.
SES-2.1.PXM.a > dspchancnt 5.2 100 100
PortId: 0.5:0.2:0 Vpi: 100 Vci: 100
CLP0 cells received: 4820845 1242205
CLP1 cells received: 9641690 2484414
CLP0 cells transmit: 0 1242205
CLP1 cells transmit: 0 2484414
CLP0 cells COS discard: 0 0
CLP1 cells COS discard: 0 0
CLP0 cells UPC discard: 306811 0
CLP1 cells UPC discard: 351496 0
Upgrading the SES Node
Use the following procedure to upgrade an SES node:
Step 1 At the BPX node, upgrade the BXM firmware to MFR. For detailed information on BXM firmware upgrades, refer to the 9.3 Version Release Notes Cisco WAN Switching Software.
Step 2 At the BPX node, upgrade the BCC switch software to Release 9.3.35. For detailed information on BCC switch software upgrades, refer to the 9.3 Version Release Notes Cisco WAN Switching Software.
Step 3 Upgrade the SES controller to Release 3.0.10. The current boot image is pxm1_003.000.010.001_bt.fw. The current runtime software is pxm1_001.001.000.000_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.
Note You can gracefully upgrade the SES controller software from Releases 1.0.14, 1.1.75, or 3.0 to Release 3.0.10.
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.0.14, 1.1.75, or 3.0 to Release 3.0.10
The procedures for upgrading the boot and runtime software are in the sections that follow.
Note You can only upgrade to Release 3.0.10 from Release 1.0.14, 1.1.75, or 3.0. If you are running a release other than 1.0.14 that is prior to 1.1.75 (such as 1.1.70, or 1.0.16), you must upgrade to1.1.75 before you download the 3.0.10 boot and runtime images. For information on upgrading to Release 1.1.75, refer to the 1.1.75 Version Software Release Notes Cisco SES Controller Software.
Upgrading the Backup Boot Image
This section provides instructions for upgrading the backup boot images from Release 1.0.14, 1.1.75, or 3.0 to Release 3.0.10. 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_003.000.010.001_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 Your password is supplied with the image.
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_003.000.010.001_bt.fw
Replace <PXM backup boot image name> with the boot image name. For Release 3.0.10 of the SES, the boot image name is pxm1_003.000.010.001_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:
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 "3.0"
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, follow these steps 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 Your password is supplied with the image.
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 3.0 of the SES, the boot image name is 3.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"3.0"
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.0.14, 1.1.75, and 3.0 to Release 3.0.10.
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 3.0.10 is pxm1_003.000.010.001_ses.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 Your password is supplied with the image.
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_003.000.010.001_ses.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 3.0(10.0)
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 3.0(10.0)
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 3.0(10.0)
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 3.0(10.0)
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 Your password is supplied with the image.
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_001.001.075.101_ses.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 3.0(10.0)
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 3.0(10.0)
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 3.0(10.0)
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 3.0(10.0)
Step 7 Enter the dspcd command to verify that the runtime image is correct on the card.
Upgrade Path
Release 3.0.10 supports upgrades from Releases 1.0.14, 1.1.75, and 3.0.If you are running a release other than 1.0.14 that is prior to 1.1.75 (such as 1.1.70, or 1.0.16), you must upgrade to Release 1.1.75 before you upgrade to Release 3.0.
For information on upgrading to Release 1.0.75, refer to the 1.0.75 Version Software Release Notes Cisco SES Controller Software.
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/rel11/sescnf/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:
•A graceful upgrade can only be completed from the SES controller software Releases 1.0.14, 1.1.75, or 3.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 DAX SPVC connection, the slave endpoint is also deleted.
•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.
•Upgrade the BXM card to the 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 3.0.10 of the SES controller:
•SPVC connections are provisioned according to a two-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 DAX 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 3.0.10.
Open Anomalies in This Release
The following table describes known anomalies in this SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure in Bug Navigator.
Table 8 Open Anomalies for Release 3.0.10
Bug ID
|
Description
|
S1 BUGS
|
|
CSCdx60401
|
Symptom:
Node continuously resets.
Conditions:
Node is receiving hello packets at line rate on a PNNI link.
Workaround:
None.
|
CSCdy75595
|
Symptom:
Connections fail on a SES controller.
Conditions:
None.
Workaround:
Under investigation.
|
S2 BUGS
|
|
CSCdw03688
|
Symptom:
Software error on handler when executing the runrev command while upgrading.
Condition:
48k DAX SPVCs and 11k routed SPVCs on the SES-BPX node.
Workaround:
None.
|
CSCdx35791
|
Symptom:
PXM45 fails to come up. If it were a standby PXM45, the dspcds on the active PXM45 indicates that the standby PXM45 slot is empty. Output from the debug console shows junk characters.
Condition:
When the PXM45's console port is connected through a terminal server with echo mode turned on, junk characters come in into the console port of the PXM45. When this card is reset, the runtime image stops its initialization when it received these junk characters on the console port.
Workaround:
1. Configure the terminal server to disable the echo mode.
2. Alternatively, pull out the console port cable and reset the card.
|
CSCdy36366
|
Symptom:
MPG SPVC cost should include cost of traversing via peer groups.
Condition:
Only includes cost of higher level Hlinks, and source PG cost. Since the via peer group costs are not included, it's possible that we might not take a more optimized route during route optimization.
Workaround:
None.
|
CSCdy51972
|
Symptom:
False channel alarms got stuck after switchyred on BXME.
Conditions:
FW upgrade of BXME cards to MFP caused a line alarm. The customer tried a switchcc on the SES controller to clear the line alarm. This caused false channel alarms. The customer then tried a switchyred to clear the false channel alarms faster. This made the false channel alarms stay. The customer had to reset the FRSM cards to clear the alarms.
Workaround:
Reset the FRSM cards on the MGX(8220) or don't switchyred on the BXME while there are false channel alarms. The false channel alarms would clear in about 30 min.
|
CSCdy59180
|
Symptom:
Once it was observed that 4 SPVC failed to route. This failure was due to slave state of the connections were in the wrong state.
Conditions:
When large number (250k) of SPVC rerouted.
Workaround:
None.
|
CSCdy70426
|
Symptom:
1. The bypasses are not ordered by AvCR. This means that bypasses with smaller bandwidth can be advertised ahead of ones with more bw. However, in most cases, the bypasses are advertised as full-meshed instead of spanning tree, so that the ordering of bypasses wouldn't matter, since all the bypasses are advertised. 2. The routing cost is not calculated correctly for via peer groups that are configured as complex nodes. This could affect finding an optimized route in MPG network.
Condition:
The complex node that is turned on a node with a lot of bypasses.
Workaround:
None.
|
CSCdy72593
|
Symptom:
Conditions:
Workaround:
|
CSCdy77568
|
Symptom:
Changing peer group, internal data base, ancestor flag bit is not being cleared.
Condition:
Changing peer group, internal data base, ancestor flag bit is not being cleared.
Workaround:
Unknown.
|
S3 BUGS
|
|
CSCdw51798
|
Symptom:
S-PVC Calling/Called PartySoft PVCC IE is not be corrected encoded.
Conditions:
PNNI conformance test failed under section R3.1.1.4/R3.1.1.5. The following test verifies the initiating PVPC/PVCC establishment procedure as outlined in AF-CS-0127.000 Section 9.2.1 and PICS conformance as described in ATM Forum AF-CS-0127.000 PNNI SPVC Addendum Version 1.0, July, 1999 and ATM Forum AF-CS-012@7.000PNNI SPVC Addendum Version 1.0, July, 1999.
Workaround:
None.
|
CSCdw57706
|
Symptom:
The VCI values are given with a value of "0" for the Calling and Called Party Soft PVPC or PVCC Information Element. The requirement states this octet - VCI is only present in case of a soft PVCC.
Conditions:
Called/Calling Soft PVPC or PVCC Information Element as described in Section 6.4.6.1 and Section 6.4.6.2 of AF-CS-0127.000.
Workaround:
None.
|
CSCdw64939
|
Symptom:
BPX-SES is responding with an incorrect Cause 43d rather than 100d when a SETUP message is received with an "access information element" with invalid content. Per Non conformance to Q2931 para. 5.6.8.2
Conditions:
None.
Workaround:
None.
|
CSCdw74433
|
Symptom:
PNNI conformance test failed in Q2931 para 5.6.8.2, When a SETUP message is received with invalid length in a non-mandatory IE, The BPX/SES is not taking action on the call.
Conditions:
Running a test suite.
Workaround:
None.
|
CSCdx34833
|
Symptom:
Popup message seen on the cli display.
Conditions:
While the shelf was idle and no cli command where being executed.
Workaround:
None.
|
CSCdx76273
|
Symptom:
The cnfqosdefault command is unusable and does not provide what the ATM Forum specifications intended. The cnfqosdefault should be port-specific and NOT node-wide.
Conditions:
None.
Workaround:
None.
|
CSCdy42620
|
Symptom:
Danglers remain after using the CLI command delcons. This is the caveat with these commands. While provisioning connections in bulk (copycons/delcons), if the PNNI layer get busy due to re-route/de-route activity, then it will reject the deletion.
Conditions:
The command delcons was developed for Dev-test usage only. This command is not recommended to be used on a production node due to resource problems generated by the flood of traps on each con deletion.
Workaround:
Use the delcon command for each individual PVC until a better method is developed see PXM release notes for description of cli commands delcon and delcons usage.
|
Problems Fixed in Release 3.0.10
The following table describes previous anomalies that are fixed in Release 3.0.10 of the SES controller software delivery.
Table 9 Problems Fixed in Release 3.0.10
Bug ID
|
Description
|
S1 BUGS
|
|
CSCdx57063
|
Symptom:
Observed resource (e.g. lcn, vpi/vci) leak on NNI trunks.
Conditions:
Enter resetcd on service modules (where SPVC are terminated) and then deroute connections by using one of the following methods:
1. Reset via/remote node
2. Bring down NNI trunks
3. rrtcon/dncon
Workaround:
switchcc controller card
|
CSCdx69070
|
Symptom:
Several possible symptoms including:
•Inability or sporadic ability, to connect via telnet
•"gray-out" of the node on the CWM topology map
•No output from or receipt of an error message from dsplog command or file system listing command 'ls' or other commands.
•Standby PXM45 or AXSM service modules remain in the Boot and/or Init state, or alternate between the two after a reload.
•Inconsistent connection alarms on slave and master. (one side reporting alarm, the suspect side not)
Condition:
System memory and/or file handle allocation may get into a marginal or maxed out state due to an ungraceful exit from the dsplog command multiple times. This includes exiting the display of the command with any method other than using the Q option to quit, or going to the end of the output. (Contact Cisco TAC to verify condition)
Workaround:
On redundant systems with healthy standby PXM45 present, enter the switchcc command. On non-redundant systems, reset the single PXM45.
|
CSCdy07989
|
Symptom:
1. Both active and standby PXM1E combo cards are stuck in init state indefinitely.
2. Traffic flow is interrupted 100% and does not resume.
3. LAN IP cannot be pinged at all.
4. IPC buffer congestion is observed due to pnCcb & other PNNI tasks holding on to buffers causing buffer allocation failures.
Conditions:
switchcc from active to standby card.
Workaround:
Unknown.
|
CSCdy12829
|
Symptom:
Connection end-points lost after power cycle node with approximately 27k connections and 2k pts.
Conditions:
Power cycle node with approximately 27k conns and 2k pts.
Workaround:
Unknown.
|
CSCdy18142
|
Symptom:
Call fails to route in MPG environment with reason as unallocated or unassigned number.
Condition:
The addresses in the lower level node are not advertised to higher levels on having a Multi peer group network.
Workaround:
None
|
CSCdy26902
|
Symptom:
pnCcb and pnSscop tasks are using a lot of memory and CPU usage for a long time.
Conditions:
Power cycle the node.
Workaround:
Unknown.
|
S2 BUGS
|
|
CSCdx44559
|
Symptom:
A phantom level 0 node may appear in a Multiple Peer Group (MPG) It can be seen in the output of the command dsppnni-node-list as shown here:
node # node id node name level
------- --------------------------------------------------
---------- -------
2 0:6:00.000c020000000100106d3839.35302d376200.00 > 0 <==
Conditions:
PNNI hierarchical network running multiple peer groups (MPG).
Workaround:
None.
|
CSCdx49157
|
Symptom:
Cannot change PCR of SSCOP back to the default value.
Conditions:
After modifying it from the default value of 30800 to the lower value of 4000, and then attempting to modify it back to the default value.
Workaround:
None.
|
CSCdx50255
|
Symptom:
Nodal State PTSE was updated in less then 10 seconds.
Conditions:
After upping and downing a inside trunk with bnPathHoldDown and PTSE holddown set to 10 seconds.
Workaround:
None
|
CSCdx55169
|
Symptom:
Invalid PTSE flooded causes Cat8510 neighbor links to go into the "exchanging" state.
Condition:
Invalid PTSE flooded to Cat8510. Invalid PTSE values seen in dsppnni-ptse.
Workaround:
Functionality can be restored by downing and re-enabling the PNNI in the SES controller (cnfpnni 1 -enable false/true)
|
CSCdx76697
|
Symptom:
The master end of a PNNI connection will show ok while the slave end of the connection will show failed.
Conditions:
The connection will report mismatch state.
Workaround:
Unknown.
|
CSCdy00116
|
Symptom:
Clock source disappeared on executing dnport/upport command.
Conditions:
When one of the clock sources was in LOA.
Workaround:
1. Do not do a dnport /upport on a clock port while the clock sources are being qualified.
2. Else reconfigure the clock source.
|
CSCdy11595
|
Symptom:
dspchancnt/dspconstats locked snmpget on stats counters failed
Conditions:
Simultaneously execute snmpget scripts and CLI (dspchancnt) scripts to collect real time stats on some connections.
Workaround:
Unknown
|
CSCdy17082
|
Symptom:
PNccb task is using a lot of CPU time.
Conditions:
This happens in some cases when all BSE fail and normal statEnq starts with multiple NNI ports having 60 K connections on controller switchover.
Workaround:
None.
|
CSCdy26150
|
Symptom:
svc-rcc does not come up.
Conditions:
After a switchcc is done on the PGL node.
Workaround:
None.
|
CSCdw61915
|
Symptom:
Event logged specified incorrect time data by LMI. Date is being set by BPX on SES feeder.
Conditions:
A new field was added to time structure. This field is not initialized by LMI and can take various values. Under certain conditions, this value is in error and causes the event to be logged.
Workaround:
None.
|
CSCdx78946
|
Symptoms:
MGX 8230/ SES dspsigstats shows "Connect Ack" Messages on AINI SES 1.1.75.103
Conditions:
The configuration is: - 2 SES connected via an AINI. - One SPVC configured with Master endpoint on one SES and Slave endpoint on the other. The problem is that according to ATM Signalling standards the "CONNECT ACK" message only exists in UNI Signalling. It does not exist in AINI. AINI implementation generates a CONNECT ACK message and as a result does not conform with the ATM Forum specification af-cs-0125.000.
Workaround:
Unknown.
|
Open Anomalies in Release 3.0
The following table describes known anomalies in Release 3.0 of the SES controller software. A more in depth discussion of each bug is available in the release note enclosure in Bug Navigator.
Table 10 Open Anomalies for Release 3.0
Bug ID
|
Description
|
S2 BUGS
|
|
CSCdx60401
|
Symptom:
Node continuously resets.
Conditions:
Hello packet flooding at line rate.
Workaround:
Unknown
|
CSCdw03688
|
Symptom:
Software error on handler when executing runrev while upgrading.
Conditions:
48k DAX SPVCs and 11k routed SPVCs on the SES-BPX node.
Workaround:
None.
|
CSCdx35791
|
Symptom:
PXM45 fails to come up. If it were a standby PXM, the dspcds on the active PXM indicates that the Standby PXM slot is empty. Output from the debug console shows junk characters.
Conditions:
When the PXM45's console port is connected through a terminal server with echo mode turned on, junk characters come into the console port of the PXM45. When this card is reset, the runtime image stops its initialization when it received these junk characters on the console port.
Workaround:
1. Configure the terminal server to disable the echo mode.
2. Alternatively, pull out the console port cable and reset the card.
|
CSCdw51798
|
Symptom:
S-PVC Calling/Called PVCC IE is not be corrected encoded.
Conditions:
PNNI conformance test failed under section R3.1.1.4/R3.1.1.5 The following test verifies the initiating PVPC/PVCC establishment procedure as outlined in AF-CS-0127.000 Section 9.2.1 and PICS conformance as described in ATM Forum AF-CS-0127.000 PNNI SPVC Addendum Version 1.0, July, 1999 and ATM Forum AF-CS-012@7.000PNNI SPVC Addendum Version 1.0, July, 1999.
Workaround:
None.
|
CSCdw57706
|
Symptom:
The VCI values are given with a value of "0" for the Calling and Called Party Soft PVPC or PVCC Information Element. The requirement states that this octet - VCI is only present in case of a soft PVCC.
Conditions:
Called/Calling Soft PVPC or PVCC Information Element as described in Section 6.4.6.1 and Section 6.4.6.2 of AF-CS-0127.000.
Workaround:
None.
|
CSCdw64939
|
Symptom:
BPX-SES is responding with an incorrect Cause 43d rather than 100d when a SETUP message is received with an "access information element" with invalid content. Per Non conformance to Q2931 para. 5.6.8.2.
Conditions:
None.
Workaround:
None.
|
CSCdw74433
|
Symptom:
PNNI conformance test failed in Q2931 para 5.6.8.2, When a SETUP message is received with invalid length in a non-mandatory IE, The BPX/SES is not taking action on the call.
Conditions:
Running a test suite.
Workaround:
None.
|
CSCdx32349
|
Symptom:
SES did not add SPVC endpoint.
Conditions:
None.
Workaround:
None.
|
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:
None.
Workaround:
None.
|
CSCdx40400
|
Symptom:
When the tstdelay command is entered on an SPVC on the SES, the "Cells sent total local egress" counter increments, which suggests that a tstdelay (which measures delay inside the network) results in cells being sent over a UNI, outside of the network (that would be wrong). However, using an HP BSTS to monitor traffic on the other side of the interface, it is clear that no cells are sent. So the counter increment is bogus.
Conditions:
None.
Workaround:
None.
|
CSCdx45385
|
Symptom:
On the SES, the dsppnportrsrc command is used to check the available VSI resources on a port. Testing shows that dsppnportrsrc keeps aligned with the exact state of VSI resources when an SPVC endpoint is added to the port. However, the dsppnportrsrc display is not updated following a change of the VSI resources done using the cnfrsrc <slot.port> command on a BPX. This is especially troublesome when a port runs out of LCNs. The dsppnportrsrc command display shows "# Avl Tx Chans:" = 0. After going on the BPX and increasing the size of the VSI partition, the dsppnportrsrc command display still shows the number of available LCN as being 0, so the SES will reject any provisioning attempt on that port, even though there truly are resources available to accept the SPVC endpoint.
Conditions:
Following are screenshots of an example triggering of the problem:
On the BPX, on a BXM-T3-12 card, up a single port. The card must have only port (to facilitate VSI management). The bug also happens with more than one port.
Configure the port as follows:
Up the port.
Enable a VSI partition on the port, with overlapping VPI range, half the BW and min VSI LCN = 0, Max VSI LCN = 1. cnfvssiif <slot.port> 2 cnfrsrc.
On the SES, do a dsppnportrsrc and check the number of available LCNs as seen by the SES (the UNI Signalling Channel is disabled, "cnfpnportsig 3.1 - univer none."
On the BPX, increase the number of Max VSI LCNs from 1 to 5.
On the SES, dsppnportrsrc still shows 1. This never gets updated it seems
Provision an SPVC endpoint against that port. That gets dsppnportrsrc to be updated to the correct value (4).
Provision 4 additional SPVC endpoints against that port. This exhausts the VSI LCNs on the port and gets dsppnportrsrc to show "0."
On the BPX, via cnfrsrc, increase the Max VSI LCN for the port from 5 to 10.
Check dsppnportrsrc on the SES. It still shows 0 available LCNs for nrtvbr.
As a result the SES rejects a provisioning attempt for nrtvbr SPVC endpoint on that port.
On the BPX, increase Max VSI LCN for that port from 10 to 15.
On the SES dsppnportrsrc is still not accurate and still maintains a discrepancy between nrtvbr and other ATM Service Categories.
Workaround:
None.
|
CSCdx76273
|
Symptom:
The cnfqosdefault command is unusable and does not provide what the ATM Forum specifications intended. The cnfqosdefaut command should be port-specific and NOT node-wide.
Conditions:
SES is running 1.1.75.103.
Workaround:
None.
|
Open Anomalies in Release 1.1.75
The following table describes the open anomalies in the 1.1.75 SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure of the problem record in Bug Navigator.
Table 11 Open Anomalies for Release 1.1.75
Bug ID
|
Description
|
S2 BUGS
|
|
CSCdt12655
|
Symptom:
Too many stat collection FTP errors.
Conditions:
Unknown.
Workaround:
None.
|
CSCdw03688
|
Symptom:
Software error on handler when executing runrev while upgrading.
Conditions:
None
Workaround:
None.
|
S3 BUGS
|
|
CSCds74052
|
Symptom:
Given a redundant SES node, pull out the trunk back-card from the active PXM's slot. This causes the active PXM to reboot and the standby PXM to take over as the active front-card. The previously-active PXM card should come up as the standby card but instead, it keeps rebooting.
Conditions:
Not known as yet. It is suspected that some task is trying to access the NOVRAM on the (absent) trunk back-card.
Workaround:
None. The only thing to do is not to pull out the trunk back-card while the front-card is either in the active or standby role.
|
CSCdv22425
|
Symptom:
Standby card goes into rolling boot.
Conditions:
Enter the resetcd command to reset the standby card.
Workaround:
None.
|
CSCdw15621
|
Symptom:
Cannot enable diagnostics on SES PNNI.
Conditions:
Enter the cnfdiag command to enable diagnostics (online/offline).
Workaround:
None.
|
CSCdw57706
|
Symptom:
The VCI values are given with a value of "0" for the Calling and Called Party Soft PVPC or PVCC Information Element. The requirement states (This octet - VCI is only present in case of a soft PVCC.
Conditions:
Called/Calling Soft PVPC or PVCC Information Element as described in Section 6.4.6.1 and Section 6.4.6.2 of AF-CS-0127.000
Workaround:
None.
|
CSCdw64939
|
Symptom:
BPX-SES is responding with an incorrect Cause 43d rather than 100d when a SETUP message is received with an "access information element" with invalid content. Per Non conformance to Q2931 para. 5.6.8.2
Conditions:
None.
Workaround:
None.
|
Problems Fixed in Release 1.1.75
The following table describes the anomalies fixed in the 1.1.75 SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure of the problem record in Bug Navigator.
Table 12 Anomalies Fixed in Release 1.1.75
Bug ID
|
Description
|
S1 BUGS
|
|
CSCdv59710
|
Symptom:
PNNI link corrupted after upgrade from 1.0.15 to 1.1(60.101). PNNI link in attempt state. PNNI VC entry is corrupted.
Condition:
SES upgrade from 1.0.15 to 1.1(60.101).
Workaround:
None. Fixed in 1.1.75.
|
CSCdw34252
|
Symptom:
SES doesn't support MBS less than 9.
Workaround:
None.
|
CSCdw56907
|
Symptom:
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
|
S2 BUGS
|
|
CSCdv63740
|
Symptom:
After changing SES node name to small one, conn shows part of old name.
Condition:
Occurs whenever user assigns a shorter node name to an SES node with a long node name.
Workaround:
None. Fixed in 1.1.75.
|
CSCdv74376
|
Symptom:
a-bit alarms not cleared after a a switch y-red. Few AXIS connections are in a-bit alarms.
Condition:
Occurs whenever user executes a switch y-red on BXM while connections are in a-bit alarms.
Workaround:
Execute switch y-red again.
OR
Execute dncon and upcon on connections that have a-bit alarms (this is service affecting).
|
CSCdv79733
|
Symptom:
DEV: ADDR-5-ADDR_ERROR in dsperrs after reroutes
$$prefcs
|
CSCdv83155
|
Symptom:
CLI: compilation error due to basic CLI prototype definition
$$prefcs
|
CSCdw08130
|
Symptom:
REG21:add/cnfcon is allowed on slave side for SES. dspcon shows frame discard enable on slave side, which has to be on SES.
Conditions:
cnfcon/addcon with frame discard enable on SES, which is the slave side.
Workaround:
None.
|
CSCdw10812
|
Symptom:
Few SPVC are in temporary failure.
$$prefcs
|
CSCdw36332
|
Symptom:
Statistics for connections can't be cleared / reset.
The statistics collection can not be cleared for the connection level statistics and all the counters remain the same after CLI command is executed to clear the statistics.
Conditions:
The statistics collected for a connection cannot be cleared by executing CLI command.
Workaround:
Not known yet other than reset etc.
|
CSCdw44217
|
Symptom:
CBR.1 S-PVC is allows only through-put 50pcs.
The CBR.1 S-PVC with PCR = 1000 cps only allowed traffic through-put at a rate of 50 cps.
Condition:
1. Initiate a CBR.1 S-PVC and verify that the UPC functions as specified by the traffic contract.
–PCR = 1000 cps
–CDVt = 150 us
–CDV = 10000 us
–CTD = 150 ms
2. Generate user traffic at a rate of 500 cps.
Workaround:
Reset interface cards (BXM) then the traffic can run at rate of 500 cps.
|
CSCdw43522
|
Symptom:
pnCcb suspended by switchcc on the new active card.
Standby card undergoes system reload on switchcc.
Conditions:
If node atm prefix is added as an address on a port and the node is a PGL node which has an SVCC based RCC to PEER MPG LGN.
Workaround:
Adding of node prefix as an address on ports is not supported and this address should be deleted. The higher level PNNI node may also be configured with a different ATM address that does not fall under this prefix. This is a configuration problem and will not happen in properly configured nodes.
|
CSCdw46658
|
Symptom:
Counting of control connections on NNI interfaces.
Control connections are not counted at the originating node. This can lead to mismatch in number of connections at two ends of trunk.
Conditions:
Control connections are not counted at the originating node.
Workaround:
None.
|
CSCdw47729
|
Symptom:
Size mismatch when FTPing statistics files from SES node.
CWM cannot get SES SPVC stats.
Conditions:
Due to new changes in CWM, the FTP client in CWM tries to match the size of the file downloaded with the size given via an ftp lib command. This fails and the CWM rejects the downloaded file.
Workaround:
None.
|
CSCdw62579
|
Symptom:.
Should be able to do snmp get for CBR CDVT,show should on cli as well
snmp get for CBR CDVT returns wrong value
Condition:
Can't do snmp get for CBR CDVT value
Workaround:
No work around for snmp get and set (equivalent of cli cnfcon). cdvt can still be set as part of snmp get request (equivalent of cli addcon).
|
CSCdw74115
|
Symptom:
IPCONN: changes to handle low network memory problems.
Workstation or network management system cannot reach node via TCP/IP. Ping, telnet, etc. no longer work.
Condition:
IP Connectivity cache and IP routing in an inconsistent state. IP route exists for atm interface (routeShow) but corresponding interface cache entry does not exist (dspipifcache).
Workaround:
IP route must be manually deleted using routeDelete command.
|
S3 BUGS
|
|
CSCdw15621
|
Symptom:
REG21:Cannot enable off/online diag on SES
Cannot enable diagnostics on SES PNNI.
Conditions:
Enabling diagnostics (online/offline) using cnfdiag.
Workaround:
None.
|
CSCdw25965
|
Symptom:
REG21:cnfcon -frame option does not work on SES.
dsppncon shows frame discard to be disabled.
Conditions:
Use cnfcon to enable frame discard.
Workaround:
Add connection using the -frame option.
|
CSCdw44760
|
Symptom:
Can not telnet to the standby controller during backup boot upgrade.
Conditions:
Workaround:
None.
|
CSCdv38486
|
Symptom:
REG21:No/Incorrect error displayed when level 105 is assigned.
No/Incorrect error displayed when level changed to 105.
Conditions:
Change the level to 105.
Workaround:
None.
|
CSCdv69644
|
Symptom:
Environmental Device Traps must be self contained: PER 3917.
The information in Environmental device traps are not sufficient to figure out for which device it is applicable
Conditions:
When any Environmental Device traps are sent
Workaround:
Look at the cwTrapIndex value and perform SNMP Walk on entPhysicalTable with the INDEX value obtained from cwTrapIndex varbind.
|
Problems Fixed in Release 1.1.70
The following table describes anomalies fixed in the 1.1.70 SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure of the problem record in Bug Navigator.
Table 13 Anomalies Fixed in Release 1.1.70
Bug ID
|
Description
|
S1 BUGS
|
|
CSCdv48381
|
Bulk set on proxy slave not functioning.
|
CSCdv54458
|
Upgrade from 1.0 to 1.1.60 does not work due to SHM_REP_RAM_NODE_DB change.
|
CSCdv57330
|
Connection addition fails (disk update failing).
|
CSCdv59710
|
PNNI link corrupted after upgrade from 1.0.15 to 1.1(60.101).
|
CSCdv84753
|
Call stuck in setup state.
|
S2 BUGS
|
|
CSCdt08059
|
DLS—Telnet daemon allows access without authentication.
|
CSCdt78006
|
DLS—switchcc resulted in temporary connection mismatch on 2 nodes.
|
CSCdu22913
|
Pulling out feeder trunk led to pnredman reset stdby (window timeout).
|
CSCdu24540
|
1.0.13verify:dbsvr failed to upgrade after stdby pxm1 reset.
|
CSCdv49665
|
JAN: AIS sent down to VSIS, but not to LSM in slot1 only.
|
CSCdv58746
|
60302 not send out when conn created failed, chanID reused in new con.
|
CSCdv63740
|
After changing SES node name to small one, conn shows part of old name.
|
CSCdv67375
|
SLT: PXM got rst in SES shelf and IPC buffer leaks after configuration.
|
CSCdv79733
|
DEV: ADDR-5-ADDR_ERROR in dsperrs after reroutes.
|
CSCdv81833
|
Port stuck in down in progress.
|
CSCdw07942
|
REG21:cnfcon -frame option does not work on SES shelf.
|
CSCdw09142
|
addshelf command not working in the SES image.
|
CSCdw10812
|
Few SPVCs are in temporary failure.
|
CSCdw17431
|
REG21: standby PXM1 failed after clrallcnf/restoreallcnf in SES PNNI.
|
S3 BUGS
|
|
CSCdv12060
|
BPX report wrong intf physical ID, dsppnport not work, pnccb runaway.
|
CSCdv27904
|
Duplicate error message in spvc2cli_errcd.
|
CSCdv37284
|
Evt.Log: <ccc session> continuous error message.
|
CSCdv46656
|
MGX/BPX: Incompatible info_length interpretation in sys_cap IG.
|
Anomalies Status Changes for Release 1.1.70
The following table describes anomalies set to a state other than resolved in this SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure of the problem record in the Bug Navigator.
Table 14 Anomalies Status Changes for Release 1.1.70
Bug ID
|
Description
|
S2 BUGS
|
|
CSCdu19130
|
1.0.13Verify:node crashes after abortrev on other node in network; duplicated.
|
Fixed Anomalies for Release 1.1.60
The following table describes fixed anomalies in the Release 1.1.60 SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure of the problem record in the Bug Navigator.
Table 15 Fixed Anomalies for Release 1.1.60
Bug ID
|
Description
|
S2 BUGS
|
|
CSCdt08059
|
Symptoms:
The telnet daemon allowed user access into the switch without authentication.
Conditions:
While in boot mode, you can telnet to the node. Access via telnet during boot mode is not restricted.
Workaround:
None.
|
CSCdt12655
|
Symptoms:
Too many stat collection FTP errors.
Conditions:
Unknown.
Workaround:
None.
|
CSCdu19130
|
Symptoms:
After entering the abortrev command on one node in the network, the other node with 50 K routed connections crashed. It did not respond to certain CLI commands, such as dsppnports and dspcons.
Conditions:
There are 50 K routed connections between node pswpop7/pswbpx2 and orses18/svcbpx23 via node pswpop6/pswbpx6. I entered the loadrev and runrev commands to upgrade the orses18 node from 1.0 to 1.1. Everything was fine after upgrade. I then entered the abortrev command to bring the orses18 node back to the 1.0 image. After entering the abortrev command on the pswpop7 node, it suddenly crashed; many tasks were deleted. The pswpop7 node did not respond to some CLI commands, such as dsppnports, dspcons, and dspconinfo. However, the dspdate, dsplogs, and dsperrs commands worked fine.
Workaround:
None.
|
CSCdu22913
|
Symptoms:
The SSI_SRAM_WIN_TIMEOUT Redman Error caused the standby PXM reset.
Condition:
There were about 50 k routed SPVC connections between two Orion/BPX nodes. One Orion node had redundant PXM cards. I pulled out the Y-cable on the feeder trunk. The RedmanError SSI_SRAM_WIN_TIMEOUT caused the standby PXM to reset.
Workaround:
Unknown.
|
CSCdu24540
|
Symptoms:
After running the script to dncon/upcon on an SES node, the dbsvr command failed to upgrade after the standby PXM reset.
Conditions:
There were about 50 K routed SPVC connections between node orses18/svcbpx23 and node pswpop7/pswbpx2. I ran script to dncon/ upcon on orses18, at the same time reset standby PXM1 on orses18. dbsvr failed to upgrade.
Workaround:
Unknown.
|
CSCdt78006
|
Symptoms:
Connections went into mismatch after replacing the PXMs in a node and entering the switchcc command.
Conditions:
A customer was going through an exercise of replacing PXMs on their nodes. On two nodes, the standby PXM was replaced, and the switchcc command was entered to make the new PXM the active one. Connections went into mismatch state for a short while, and then cleared. We were not able to get into the node to collect information while this condition existed.
Workaround:
Unknown.
|
S3 BUGS
|
|
CSCds74052
|
Symptoms:
I pulled out the trunk back-card from the active PXM's slot on a redundant SES node. This caused the active PXM to reboot and the standby PXM to take over as the active front-card. The previously-active PXM card should have come up as the standby card, but it kept rebooting.
Conditions:
Unknown. It is suspected that some task is trying to access the NOVRAM on the (absent) trunk back-card.
Workaround:
None. Do not pull the trunk back-card out while the front-card is in the active or standby role.
|
Related Documentation
The following Cisco publications contain additional information related to the operation of this product and associated equipment in a Cisco WAN switching network.
Cisco WAN Manager Release 11
The product documentation for the Cisco WAN Manager (CWM) network management system for Release 11 is listed in Table 16.
Table 16 Cisco WAN Manager Release 11 Documentation
Title
|
Description
|
Cisco WAN Manager Installation Guide for Solaris 7, Release 11
DOC-7813567=
|
Provides procedures for installing Release 11 of the CWM network management system and Release 5.4 of CiscoView.
|
Cisco WAN Manager User's Guide, Release 11
DOC-78-13568=
|
Describes how to use the CWM Release 11 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, Release 11
DOC-7813569=
|
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 11
DOC-7813542=
|
Provides information about accessing the CWM Informix OnLine database that is used to store information about the network elements.
|
Service Expansion Shelf PNNI Controller Release 3
The product documentation for the installation and operation of the Service Expansion Shelf (SES) PNNI Controller is listed in Table 17.
Table 17 SES PNNI Controller Release 3 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.
|
Cisco MGX and SES PNNI Network Planning Guide for MGX Release 3 and SES Release 3
DOC-7814261=
|
Provides guidelines for planning a PNNI network that uses the MGX 8850 and the MGX 8950 switches and the BPX 8600 switches. When connected to a PNNI network, each BPX 8600 series switch requires a SES for PNNI route processing.
|
Cisco WAN Switching Software Release 9.3.40
The product documentation for the installation and operation of the Cisco WAN Switching Software Release 9.3.40 is listed in Table 18.
Table 18 Cisco WAN Switching Software Release 9.3.40 Documentation
Title
|
Description
|
Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30
DOC-7812907=
|
Provides a general description and technical details of the 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-01 (online only)
|
Provides hardware installation and basic configuration information for IGX 8400 Series switches that are running Switch Software Release 9.3.30 or earlier.
|
Cisco IGX 8400 Series Provisioning Guide
OL-1166-01 (online only)
|
Provides information for configuration and provisioning of selected services for the IGX 8400 Series switches that are running Switch Software Release 9.3.40 or earlier.
|
Cisco IGX 8400 Series Regulatory Compliance and Safety Information
DOC-7813227=
|
Provides regulatory compliance, product warnings, and safety recommendations for the IGX 8400 Series switch.
|
9.3.40 Version Software Release Notes for Cisco WAN Switching System Software
78-13538-01
|
Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
|
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 or variables 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 ([ ]).
Notes use the following conventions and symbols
Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual.
Obtaining Documentation
These sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com
Translated documentation is available at 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 is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
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/cgi-bin/order/order_root.pl
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
http://www.cisco.com/go/subscription
•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. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you 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
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
http://www.cisco.com
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to 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 Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the Related Documentation section.
CCIP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, 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, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, 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. (0208R)
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
Feedback
