|
|
November 22, 2000
These release notes describe the Cisco 6700 series embedded software release version 1.3(4).
 |
Note This version of the software is designed to work on the Cisco 6732 series Multiservice Access Platform and the Cisco 6705 Integrated Access Device. Cisco recommends that all network elements be upgraded to the same software version. |
Release notes are updated as needed to describe new features, memory requirements, hardware support, software platform deferrals, and related documents.
For a list of the software caveats that apply to embedded software release version 1.3(4), refer to the "Resolved Caveats" section and the "Open Caveats" section.
 |
Caution Previous documentation listed the upgrade steps in an incorrect sequence. The incorrect sequence causes a Main Common Control (MCC) module bootup failure. Please use "About Upgrading the Software Image on the Cisco 6732" section and "About Upgrading the Software Image on the Cisco 6705" section to upgrade your system software. |
These release notes describe the following topics:
Software Version 1.3(4) supports the Cisco 6732 series Multiservice Access Platform and the Cisco 6705 Integrated Access Device.
The following table lists Cisco 6700 series service modules (SM) and line interface modules (LIM) supported by embedded software release version 1.3(4):
| Module Name | Supported Platforms | Ordering Number |
|---|---|---|
BPS-AC | Cisco 6705 | 6705-PWR-AC= |
MCC-INT | Cisco 6705 | 6705-SM-MCCINT= |
BPS-HP | Cisco 6732 | 6732-PWR-HP= |
MCC-STR3 | Cisco 6732 | 6732-SM-MCC3= |
MCC-STR4 | Cisco 6732 | 6732-SM-MCC4= |
MTAC-TEI | Cisco 6732 | 6700-SM-MTAC-TEI= |
AMM | Cisco 6732 | 6700-SM-AMM= |
BRG | Cisco 6705 and Cisco 6732 | 6700-SM-BRG= |
RUVG/8 | Cisco 6705 and Cisco 6732 | 6700-LIM-RUVG-8= |
FXS/16 | Cisco 6705 and Cisco 6732 | 6700-LIM-FXS-16= |
DSX1/8 | Cisco 6705 and Cisco 6732 | 6700-LIM-DS1= |
T1-2-V35 | Cisco 6705 and Cisco 6732 | 6700-LIM-T1-2-V35= |
DSX3/CHNL | Cisco 6705 and Cisco 6732 | 6700-LIM-DS3-C= |
STSX1/CHNL | Cisco 6705 and Cisco 6732 | 6700-LIM-STS-1= |
OC3c-UNI | Cisco 6705 and Cisco 6732 | 6700-LIM-OC3-UNI |
RPOTS/16 | Cisco 6705 and Cisco 6732 | 6700-LIM-RPOTS-16= |
MSDSL-2W | Cisco 6705 and Cisco 6732 | 6700-LIM-MSDSL-2W= |
ISDN-BRI/8 | Cisco 6705 and Cisco 6732 | 6700-LIM-BRI-8= |
The Cisco 6700 series Embedded Software Version 1.3(4) must be used in conjunction with Element Management System (EMS) Software Version 1.3 or later.
To determine the version of software currently running on the Cisco 6700 series device, you must connect the chassis to a workstation with EMS installed. For more information about installing EMS, refer to the "EMS Installation" section of the Cisco 6700 Series Element Management System User Guide.
Step 2 In the EMS root view, double click the node icon representing the Cisco 6705 or Cisco 6732 chassis.
Step 3 In node view, double click the nameplate button (located near the top of the window). The Network Element (NE) provision window appears.
Step 4 The software release is listed in the NE Loaded Software Version field.
|
Caution When you are upgrading your MCC module always back up your database first. |
The EMS database backup utility allows you to back up the existing configuration of a node to a TFTP server. After the database has been backed up, you can restore the node configuration, if needed.
Before beginning the database backup, complete the following tasks:
To back up the system database, perform the following steps starting in node view:
Step 2 Select the Database Backup tab from the NE provision window.
Step 3 Complete the following fields to begin the database backup procedure:
Step 4 Click Apply to save the backup configuration.
Step 5 Click Backup to begin the database backup.
|
Caution Cisco recommends that you perform a local software upgrade with a local EMS workstation directly connected to the Cisco 6732 MCC that you are upgrading. |
Please use this updated procedure to upgrade the software image on the Cisco 6732.
Before beginning the embedded software upgrade, complete the following tasks:
|
Caution When upgrading multiple nodes in a network, always start from the far end of the network, one node at a time. In a typical network, a number of remote nodes (subscriber nodes) are connected to a central office terminal (COT) node. If the upgrade of the COT is mishandled, management or communication control or both of the entire network may be lost. An upgrade should be attempted at a single remote node located at the networks edge. If the upgrade tests fail on the edge nodes, do not attempt to upgrade the COT node. |
Step 2 To start the NE Provision window, double-click the node nameplate.
Step 3 To see the switch over window, click Common Control Card Switch Over in the function bar.
EMS identifies the active MCC in the Active MCC field.
|
Note The MCC module that is not active is called the standby MCC. For example, if MCC-A is active, then MCC-B is the standby MCC. |
Step 4 To return to node view, click Exit.
Step 2 Set the Admin Status field to OutOfService.
Step 3 To place the MCC module out of service, click Apply.
Step 4 To return to node view, click Exit.
Step 2 To view the Software Upgrade window, click Software Upgrade in the function bar.
Step 3 In the Software Image Host IP Address field, enter the IP address of the TFTP server.
Step 4 In the Software Image File Name field, enter SwLoad.iad.
Step 5 In the Upgrade Software to Main Common Control Card field, select the standby MCC module.
|
Note Upgrade the MCC that is not shown in the Active Main Control Card field. For example, if EMS shows that the active MCC is A, you must select B for the upgrade field. |
Step 6 To confirm the host IP address and path to the image filename, click Apply.
Step 7 To download the embedded software image into the Flash memory of the standby MCC module, click Upgrade.
EMS displays a progress bar.
When the upgrade finishes, the message "Please reboot the node for the new software to take affect" appears.
|
Caution If EMS is unable to complete the embedded software upgrade, an error message appears at the bottom of the NE provision window and in the Problem List of the MCC module. In this case, do not reset the MCC module; restart the embedded software upgrade process. |
Step 8 To return to node view, click the Dismiss button in the software upgrade message prompt and then
click Exit.
Step 2 Right-click the node being upgraded, and select Node Critical Commands from the popup menu.
Step 3 Enter the Node Critical Command password.
Step 4 To open the line card reset window, click MCC Reset in the function bar.
Step 5 In the MCC Reset field, select the standby MCC (A or B).
Step 6 To reset the selected MCC, click Reset.
Step 7 The confirmation message "Are you sure?" appears. Click Yes. The MCC begins a reset and initialization procedure.
|
Note Allow 45 to 60 seconds for the MCC to complete the reset procedure. |
Step 8 To return to net view, click Exit.
Step 2 To view the Software Upgrade window, click Software Upgrade in the function bar.
Step 3 In the Software Image Host IP Address field, enter the IP address of the TFTP server.
Step 4 In the Software Image File Name field, enter SwLoad.iad.
Step 5 In the Upgrade Software to Main Common Control Card field, select the Active MCC card.
Step 6 To confirm the host IP address and path to the image filename, click Apply.
Step 7 To download the embedded software image into the Flash memory of the active MCC module, click Upgrade.
EMS displays a progress bar.
When the upgrade finishes, the message "Please reboot the node for the new software to take affect" appears.
|
Caution If EMS is unable to complete the embedded software upgrade, an error message appears at the bottom of the NE provision window and in the Problem List of the MCC module. In this case, do not reset the MCC module; restart the embedded software upgrade process. |
Step 8 To return to node view, click the Dismiss button in the software upgrade message prompt and then
click Exit.
Step 2 Double-click the standby MCC module. The Plugin Card Provision window appears.
Step 3 Set the Admin Status field to InService.
Step 4 To place the module in service, click Apply.
Step 5 To return to node view, click Exit.
Step 2 Click Common Control Card Switch Over in the function bar.
Step 3 To switch control from the active MCC to the standby MCC, click Switch.
Step 4 To return to node view, click Exit.
|
Note The roles of standby and active MCC have now been switched. If you want the original active MCC to be the active MCC again, you must perform another switchover. Wait for approximately 60 seconds for the database to transfer before performing another switch over. |
|
Caution The following procedure reboots the line interface modules (LIMs) and temporarily takes them out of service. Any traffic that is carried on these modules is dropped. Exercise proper planning and system coordination to eliminate or reduce the potential for interrupted subscriber service. |
Step 2 Right-click the node being upgraded, and select Node Critical Commands from the popup menu.
Step 3 Enter the Node Critical Commands password.
Step 4 To open the Line Card Reset window, click Line Card Reset in the function bar.
Step 5 Set the Reset field to All.
Step 6 To reset all line cards, click Apply.
Step 7 To return to EMS Net View, click Exit.
|
Note Allow 60 to 90 seconds for the MCC modules and LIMs to complete the reset procedure. |
|
Caution Cisco recommends that you perform a local software upgrade with a local EMS workstation directly connected to the Cisco 6705 chassis. |
Please use this updated procedure to upgrade the software image on the Cisco 6732.
Before beginning the embedded software upgrade, complete the following tasks:
|
Caution When upgrading multiple nodes in a network, always start from the far end of the network, one node at a time. In a typical network, a number of remote nodes (subscriber nodes) are connected to a central office terminal (COT) node. If the upgrade of the COT is mishandled, management or communication control or both of the entire network may be lost. An upgrade should be attempted at a single remote node located at the networks edge. If the upgrade tests fail on the edge nodes, do not attempt to upgrade the COT node |
Perform the following steps to upgrade or install the embedded software:
Step 2 From node view, double-click the node nameplate to start the NE provisioning window.
Step 3 Select Software Upgrade from the function bar to view the software upgrade window.
Step 4 In the Software Image Host IP Address field, enter the IP address of the TFTP server.
Step 5 In the Software Image File Name field, enter SwLoad.iad.
Step 6 Set the Upgrade Software to Main Common Control Card field to A; the Cisco 6705 has only one MCC-INT module, identified as A.
Step 7 To confirm the host IP address and path to the image filename, click Apply.
Step 8 To download the embedded software image into the Flash memory of the MCC-INT module,
click Upgrade.
EMS displays a progress bar.
When the upgrade finishes, the message "Please reboot the node for the new software to take affect" appears.
|
Caution If EMS is unable to complete the embedded software upgrade, an error message appears in the EMS NE provisioning window. In this case, do not reset the MCC-INT module; restart the embedded software upgrade process. |
Step 9 To return to Node View, click the Dismiss button in the software upgrade message prompt and then
click Exit.
|
Caution The following procedure reboots the LIMs and temporarily takes them out of service. Any traffic that is carried on these modules is dropped. Exercise proper planning and system coordination to eliminate or reduce the potential for interrupted subscriber service. |
The MCC-INT module must be reset before the new embedded software becomes active. Use one of the following procedures to reset the MCC-INT module:
or
Step 2 Enter the password, then select the MCC Reset tab.
Step 3 Choose Reset. The confirmation message "Resetting MCC can be service affecting. Do you really want to reset the card?" appears. Click Yes.
Step 4 Click Exit.
|
Note Allow 60 to 90 seconds for the MCC-INT and the other LIMs to complete the reset procedure. |
EMS uses password files to control access to security-sensitive operations such as resetting the MCC, erasing the system database, and shutting down the alarm server. If you attempt to start a password-protected application without the password file in place, EMS responds with the error message "Password file does not exist."
Contact your network administrator to obtain the password files and corresponding passwords for EMS.
|
Note Start the network configuration server before starting EMS Net View. Refer to the Cisco 6700 Series Element Management System User Guide for more information. |
From your workstation's desktop view, double-click the Cisco 6700 Netconfig Server icon to start the alarm server. The hourglass (system busy) cursor appears briefly, indicating that the network configuration server has started. The network configuration server application does not appear in the Windows task bar or system tray when it is started.
In the event of loss of communications with a Cisco 6705 node, use the following procedure to enable the Ethernet port on the Cisco 6705 MCC-INT module.
Step 2 Start EMS Net View on the workstation and log in.
Step 3 Identify the node icon of the Cisco 6705 that will be recovered.
Step 4 Physically unseat the MCC-INT in the Cisco 6705 chassis by lifting the removal lever and gently pulling the module away from the backplane.
Step 5 Reseat the MCC-INT by gently sliding the module into the chassis and pressing down on the lever. The MCC-INT begins an initialization sequence.
Step 6 While the MCC-INT is initializing, double-click the Cisco 6705 icon in EMS Net View. The Cisco 6705 Node View appears when the MCC-INT has finished its initialization procedure.
Step 7 In the Cisco 6705 Node View, double-click on the MCC Ethernet port.
|
Note You must place the Ethernet management port in service no later than 30 seconds after the MCC-INT finishes its initialization procedure. |
Step 8 Set the AdminStatus of the Ethernet management port to inService.
Now you can use the Ethernet management port on the Cisco 6705 MCC-INT module to establish communications. Refer to the Cisco 6700 Series Element Management System User Guide for provisioning procedures.
The Class 5 switch GR-303 interface serves as the master controller of the Cisco 6732 GR-303 database. The Cisco 6732 database can lose synchronization with the Class 5 switch if this procedure is not followed.
To delete call reference values (CRV) between the Cisco 6732 and a Class 5 switch:
Step 2 Delete the CRVs from the Cisco 6732 using EMS.
Each CRV provisioned on an ISDN-BRI/8 module occupies three DS0 channels (one DS0 each for the B1, B2, and D channels) over the transport between the Cisco 6732 and the remote node.
When provisioning CRVs for ISDN, make sure that the interface group uses enough transport lines to accommodate three DS0s for each CRV.
For example, a DS1 transport between a Cisco 6705 remote node and a Cisco 6732 local node can carry up to 8 ISDN lines (24 divided by 3) over an FDL INDL. A DS1 transport using a DS0 INDL can carry up to 7 ISDN lines, because one DS0 is used as the INDL (leaving 23 available DS0s).
When deleting an ISDN CRV, you must delete the CRV from the switch before deleting it in EMS. Monitor the facility service state through EMS to ensure that the CRV has been deleted from the switch side. A transition from in service to out of service indicates that the switch has deleted the CRV from its database. After confirming its deletion from the switch side, delete the CRV in EMS.
Under heavy traffic conditions, when deleting an ISDN CRV from the Class 5 switch and the Cisco 6732, the switch may not delete the quarter DS0 carrying the D channel from the Cisco 6732 database. This issue depends on the switch scheduler for deleting CRVs; excessive traffic can delay or prohibit the removal of the quarter DS0.
When viewing the expanded line view of a cross-connected GR-303 facility, the channel with a quarter DS0 appears with a small black hashmark next to the channel. In this case, use EMS to delete the quarter DS0. Refer to "About Deleting a Quarter DS0 Cross Connect"and "About Deleting a Quarter DS0".
Step 2 Select the line that is provisioned with the cross connect. EMS displays the internal cross-connects.
Step 3 Look for a channel with a small black hashmark to the right. This channel carries the quarter DS0. In Figure 1, channel 3 of an STS1 transport carries a quarter DS0.
Step 4 Right-click the quarter DS0 channel and select Display Quarter DS0. EMS starts the cross-connect display.
Step 5 Double-click a cross-connect line to start the cross-connect provisioning window.
Step 6 Click Delete.
Step 7 EMS displays a warning, recommending that this operation be performed from the switch.
Click Yes to proceed.
If EMS is unable to delete the cross-connect, an error message will appear.
Step 8 After deleting the cross-connect, you must close and restart the cross-connect display to reflect the changes made.
Step 2 Select the appropriate QDS0 from the pull-down menu.
Step 3 Click Delete.
Step 4 A warning appears recommending that this operation be performed from the switch. Click Yes to proceed.
|
Note EMS displays an error message if you attempt to delete a cross-connected QDS0. You must delete the cross-connect before deleting the QS0. |
The cross-connect box is refreshed with the current QDS0 status when the you exit from the QDS0 provisioning screen. For instance, if all QDS0s on a DS0 have been deleted, a black hashmark no longer appears on the DS0.
The install script creates two scripts—ems.csh and ems.ksh—in the EMS installation directory. If you are upgrading or reinstalling EMS on the workstation, the script files, network configuration, and alarm information is retained from the previous installation.
EMS can be installed in any directory in which the you have write privileges (root directory). The EMS distribution package for UNIX (ems_unix) contains three files:
To install EMS:
# cp * <user directory>
# cd <user directory>
Step 2 Enter the following command to the install script:
# chmod +x emsinstall
Step 3 Start the install script:
# ./emsinstall
EMS Unix Installation
---------------------
Step 4 Press Return and select the default file name and location, ./ems.tar.
Enter tar file name [./ems.tar]:
Setting up installation...done.
Step 5 Enter a fully qualified path name for the EMS Installation directory. If the B10EMS_HOME environment variable has already been set from a previous installation, the script permits the user to use that value.
Where would you like to install the EMS?
Enter fully qualified path name: /export/home0/ems
Creating /export/home0/ems...done.
Extracting EMS files...
...
Placing EMS files in /export/home0/ems...done.
Step 6 Enter y to install the network configuration server, or enter n to skip installation.
Will this installation use the network configuration server (y/n)? [n]: y
Generating script files with environment variables...done.
Files /export/home0/ems/ems.csh
and /export/home0/ems/ems.ksh
have been created. Set the value of B10EMS_SERVER and
c6700NET_SERVER if necessary in the appropriate file and source it before running the EMS.
Hit Enter to complete the installation...
Completing installation...
EMS installation is complete. The EMS includes the 'nmtrapd' program which requires root permissions. Please get root permissions and type >> ./emsinstall root << to install it.
Step 7 If you do not want to install the alarm server, skip to Step 11.
To install the alarm server, obtain the root password for your workstation, then perform the following steps:
Step 8 Set the user to root:
# su
Step 9 Enter the following command and start the emsinstall script with root privileges:
# ./emsinstall root
The install script prompts for the fully qualified path name of the EMS installation directory unless it is already defined in the environment.
Step 10 Exit from the root login:
# exit
Step 11 You must configure the IP addresses of the alarm server and network configuration server. Use vi or another text editor to set the B10EMS_SERVER (alarm server) and C6700NET_SERVER (network configuration server) variables. Contact your network administrator for the correct IP addresses.
The following example shows how to use Vi to edit the ems.csh file.
# vi ems.csh
"ems.csh" 12 lines, 406 characters
setenv B10EMS_HOME /export/home0/ems
setenv B10EMS_SERVER
setenv C6700NET_SERVER
setenv TCL_LIBRARY $B10EMS_HOME/lib/tcl
setenv TK_LIBRARY $B10EMS_HOME/lib/tk
setenv TNM_LIBRARY $B10EMS_HOME/lib/tnm
setenv TNM_NMTRAPD $B10EMS_HOME/bin/nmtrapd
if (\Qsetenv | grep LD_LIBRARY_PATH\Q != "") then setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:${B10EMS_HOME}/lib
else setenv LD_LIBRARY_PATH ${B10EMS_HOME}/lib
endif
Step 12 After editing the ems.csh or ems.ksh file, you must update the environment.
For C-Shell, start source ems.csh. Alternatively, you can append the ems.csh file to the ~/.cshrc file, log out, and log in.
For Korn Shell, start ems.ksh. Alternatively, you can append the ems.ksh file to the ~/.profile file, log out, and log in.
The following example shows how to update the environment using ems.csh.
# source ems.csh
# env
...
B10EMS_HOME=/export/home0/ems
B10EMS_SERVER=171.68.205.106
C6700NET_SERVER=171.68.205.106
TCL_LIBRARY=/export/home0/ems/lib/tcl
TK_LIBRARY=/export/home0/ems/lib/tk
TNM_LIBRARY=/export/home0/ems/lib/tnm
TNM_NMTRAPD=/export/home0/ems/bin/nmtrapd
LD_LIBRARY_PATH=/export/home0/ems/lib
# exit
Step 13 To enable the node critical commands and alarm server passwords, copy the following password files from the EMS CD to the ems/data/netconfig directory:
The Element Management System (EMS) can be started by using C-Shell or Korn Shell.
Step 2 Use these scripts to start the alarm server, network configuration server, and EMS Net View:
|
Note The display environment must be set when the alarm server is running, or the environment variable must point to some other display that is up. If this is not done, logging out of EMS closes the display environment and shuts down the alarm server. |
|
Note The alarm server uses ports 162 and 2321 as trap daemons. Make sure that these ports are not in use when starting the alarm server. |
These programs are in the EMS installation directory/bin directory, and they can be started from any directory included in the path.
Step 2 Log out, and log back in.
or
Step 2 Log out, and log back in.
All Cisco 6700 series line interface modules are synchronized to Greenwich Mean Time (GMT), rather than the "Time of Day" setting on the EMS workstation. One-day performance monitoring (PM) tests use GMT, not the EMS time of day, to determine the start and end times of the 24-hour monitoring window.
The following new hardware features are supported by the Cisco 6700 series for software release version 1.3(2) and later.
The Cisco 6732 now supports the main control card with stratum 4 clock (MCC-STR4). The MCC-STR4 provides a less expensive timing solution for use with interfaces slower than OC-3.
The OC3c-UNI line interface module offers point-to-point ATM UNI connections over a bidirectional optical interface at the SONET OC-3 rate (155.52 Mbps).
The RPOTS/16 line interface module offers 16 POTS ports. Use of this card requires a ring generator—either a bank ring generator (BRG) service module or an external ringer.
The MSDSL-2W card provides four independent CAP MSDSL two-wire interfaces, capable of carrying payload rates of 144 kbps to 2320 kbps. This module can be used to provide a single pair T1 or fractional T1 transport between Cisco 6732 nodes, or between a Cisco 6732 node and a Telmax CPE device.
The ISDN-BRI/8 line interface module offers eight ports supporting standard basic rate interface (BRI) with 4:1 D channel mapping. The ISDN-BRI/8 module has been certified to interoperate with Nortel and Lucent Class 5 switches over a GR-303 interface.
The metallic test access card-test equipment interface (MTAC-TEI) provides both craft access and third party test box access to the test bus in the Cisco 6732 chassis. The MTAC-TEI is used in conjunction with the Harris 107A/F remote test unit.
The Cisco 6732 now offers one-to-one protection (redundancy) of broadband line interface modules (DSX3/CHNL and STSX1/CHNL) located in slots 17-20.
The Cisco 6732 can now accommodate DSX3/CHNL and STSX1/CHNL line interface modules located in slots 21-32. Up to 10 DS1s are available to broadband line interface modules located in slots 21-32.
The MCC-INT service module on the Cisco 6705 supports up to 3 megabits of user bandwidth over the Ethernet port. Implementation is RFC 1483 (PPP over ATM) standard compliant.
A Cisco 6705 chassis with a disabled Ethernet port can be accessed locally in case of internode data link failure. See the "Ethernet Management Port Shutdown on the Cisco 6705" section for a detailed recovery procedure.
The following new software features are supported by the Cisco 6700 series for software release version 1.3(2).
The EMS client/server based network configuration server allows EMS users to remotely access Cisco 6700 series network configuration data located on the server computer. Any configuration change made by an authorized EMS user also propagates to other concurrent EMS users.
The Cisco 6700 series Element Management System (EMS) now offers three functional levels of user security and privileges.
Dynamic bandwidth allocation (DBA) allows ATM data to pass over idle DS0 voice channels on T1-2-V35 and MSDSL-2W line interface modules. When the voice channel becomes active, the DS0 is reallocated for voice traffic without affecting ATM data traffic.
The Cisco 6700 series supports 100 FDL-INDLs and 16 DS0-based INDLs between nodes.
Some resolved caveats in Cisco 6700 series Embedded Software Release Version 1.3(4) require a newer version of the MCC used in the Cisco 6732 chassis and Cisco 6705 chassis. For identification purposes the new MCCs have the following CLEI codes.
MCC STR3: SBCTFHXEAA, 274659 (part number 800-05990=)
MCC STR4: SBCTFJXEAA, 274742 (part number 800-05992=)
MCC INT: SBCTHLWEAA, 274663 (part number (800-05998=)
|
Caution If you are replacing the MCC's in your Cisco 6732 you must replace both MCCs. The MCCs must have the same CLIE code. |
| Bug ID | CSCdr01352 |
| Description | While booting, the MCC resets several times. FPGA init failures suspect. |
| Symptom | During an MCC reset, the MCC might restart the initialization sequence while loading the embedded software. |
| Workaround | If this occurs, do not manually reset the MCC. The MCC finishes initializing without requiring a manual reset. |
| Bug ID | CSCdr09280 |
| Description | Deletion of VCI causes VPI delete |
| Symptom | With a provisioned VP/VC cross-connect on the Cisco 6732, deleting all VCs on the VP disables the VP, even though EMS continues to report the VP as provisioned. |
| Workaround | When deleting the last VC in a VP, delete the VP as well. |
| Bug ID | CSCds22536 |
| Description | GR303: MCC switchover causes protected STSX1 switch, dropped call |
| Symptom | The major problem and possibly the complete problem is that when the protecting card is active in a STSX1 or DSX3 protection group, a standby MCC that initializes to full standby does not know protection is on the protecting card. Subsequent MCC switchover causes loss of pattern sync, and therefor the talk path in either one or both directions. |
| Solution | Software upgrade. |
| Bug ID | CSCds68433 |
| Description | 64clr isdn does not work via STS in slot 19 to switch |
| Symptom | Problem: 64k clear channel ISDN does not work via STS1 in slot 19 to switch. Workaround: If the B channel is setup manually as clear channel, the test can pass. |
| Resolution | Upgrading the STSX1 card's FPGA to 7.1.5 |
| Bug ID | CSCdp85674 |
| Description | Delete PPP link and FDL link fails |
| Symptom | An FDL internode data link (INDL) is set up between a Cisco 6732 and Cisco 6705. An AAL5 link is set up on the same line of the same card. If you delete the AAL5 link, EMS still displays the FDL INDL, but the INDL is not operational. No communication between the Cisco 6732 and Cisco 6705 exists. |
| Workaround | Connect a local EMS workstation directly to the Cisco 6705, delete the FDL link, and create a new FDL INDL. After provisioning the Cisco 6705, connect a local EMS workstation to the Cisco 6732 and repeat this procedure. |
| Bug ID | CSCdp85678 |
| Description | Deleting VP/VC over FDL causes count mismatch and no response |
| Symptom | Condition: An FDL internode data link (INDL) is created between a Cisco 6732 MSDSL-2W module and a Cisco 6705 MSDSL-2W module. A VP/VC pair is created on the Cisco 6705 MSDSL-2W module over the FDL INDL. Problem: If you delete the VP/VC pair, EMS might respond with the error message "Failed to delete VP/VC object: NoSuchName." The VC will be deleted, but the VP will not be deleted. The configured VP and VC counts in the ATM interface provisioning window may not match the display in the Create or Modify and Delete VP/VC Assignments window. Further attempts to delete the VP prompt the EMS error message "No Response." |
| Workaround | Connect a local EMS workstation directly to the Cisco 6705 and delete the VP. |
| Bug ID | CSCdr02668 |
| Description | AAL5:PPP link goes down and doesn't recover from excess traffic |
| Symptom | Condition: In a configuration with two Cisco 6705 nodes connected through a Cisco 6732 node, excessive traffic over the Ethernet port can cause an AAL5 link between the Cisco 6705 nodes to lose communication. |
| Workaround | Delete the AAL5 link on both Cisco 6705 nodes; then reprovision the AAL5 link. |
| Bug ID | CSCdr09363 |
| Description | DS0s distributed across two OC3c cards gives continuous BIT errors |
| Symptom | Condition: A full cross-connected DS1 that has its DS0s distributed across two or more OC3c-UNI modules might experience bit errors. |
| Workaround | Do not partition a full DS1 across multiple OC3c-UNI modules. |
| Bug ID | CSCds53532 |
| Description | OC3 hsa max vp xconn loses around 250 xconns |
| Symptom | Conditions: The user has configured up to 2044 ATM cross-connections in the 6732 via ATM Provisioning and ATM Cross Connects in EMS. Symptom: ATM traffic cannot pass through the system on the last 249 cross-connections entered. |
| Workaround | There is no workaround. The user is limited to 1796 ATM cross connections. |
| Bug ID | CSCds64505 |
| Description | Timing loss after STSX1 protection switch towards switch |
| Symptom | Conditions: STSX1-based GR-303 Interface Group (IG) is utilized between a head node Cisco 6732 and a Local Digital Switch (LDS). All 28 DS1 member IDs are defined (i.e. provisioned). Two STSX1 Line Cards (LCs) are utilized to create a protection group for the GR-303 link. The LCs of this protection group are installed in slot 17 (protected role) and slot 18 (protecting role) of the Cisco 6732 chassis. The protected STSX1 LC is initially active. The Cisco 6732 is configured to receive its timing reference from the LDS via the active (protected) STSX1 LC. An STSX1 LC protection switch is initiated by any of the following means: - The protecting STSX1 LC is set to the active state via Element Management System (EMS). As a result, the protected LC goes into the standby state. - The active (protected) STSX1 LC is removed from the Cisco 6732 chassis. As a result, the protecting LC switches from the standby state to the active state. - The cable to the active (protected) LC is unplugged at the LC's connector. As a result, the protecting LC switches from the standby state tot he active state. In each of these cases, the Cisco 6732 does not enable the timing reference receiver on the protecting STSX1 LC. Symptoms: The Cisco 6732 is not timed to the LDS. This condition persists as long as the protecting STSX1 LC remains in the active state. |
| Workaround | Restore protected STSX1 LC to the active state and do not use STSX1 LC in a protection group configuration for GR-303 IGs between the Cisco 6732 and an LDS. LDS timing synchronization is restored as soon as the protected STSX1 LC is returned to the active state. |
| Bug ID | CSCds64536 |
| Description | EOC TMC goes down after protection switch on STSX1 |
| Symptom | Conditions: STSX1-based GR-303 Interface Group (IG) is utilized between a head node Cisco 6732 and a Local Digital Switch (LDS). All 28 DS1 member IDs are defined (i.e. provisioned). Two STSX1 Line Cards (LCs) are utilized to create a protection group for the GR-303 link. The LCs of this protection group are installed in slot 17 (protected role) and slot 18 (protecting role) of the Cisco 6732 chassis. The protected STSX1 LC is initially active. The IG comes up and call processing functions normally. An STSX1 LC protection switch is initiated by either of the following: - The protecting STSX1 LC is set to the active state via Element Management System (EMS). As a result, the protected LC goes into the standby state. - The active (protected) STSX1 LC is removed from the Cisco 6732 chassis. As a result, the protecting LC switches from the standby state to the active state. - The cable to the active (protected) LC is unplugged at the LC's connector. As a result, the protecting LC switches from the standby state tot he active state. In each of these cases, call processing is impaired as long as the protecting STSX1 LC is in the active state. Symptoms: The Embedded Operations Channel (EOC) and Timeslot Management Channel (TMC) GR-303 IG data links go down. Cannot get dial-tone in response to off-hook signalling. Cannot establish new calls. |
| Workaround | Restore protected STSX1 LC to the active state and do not use STSX1 LC in a protection group configuration for GR-303 IGs between the Cisco 6732 and an LDS. |
| Bug ID | CSCds65827 |
| Description | INDL over OC3c does not work until MCC resets both ends |
| Symptom | Conditions: OC3-UNI Line Card (LC) installed in a High Speed ATM (HSA) slot (slot 18) of a head node and remote node Cisco 6732 chassis. DS0 Inter-Node Data Link (INDL) created between head node and remote node over the OC3 transport. This INDL problem did not occur when the OC3-UNI LCs were installed in non-HSA slots of the head node and remote node chassis. Symptoms: INDL does not come up initially. |
| Workaround | On the head node Cisco 6732 system, perform a control switch-over by rebooting the active Main Control Card (MCC) |
| Bug ID | CSCds65831 |
| Description | ISDN phone problem over OC3 indl (remote CRVs)-layer 2 establishment |
| Symptom | Conditions: Provisioning ISDN remote Call Reference Values (CRVs) via Inter-Node Data Link (INDL) over an OC3 transport to the remote node. Two different Interface Groups (IGs) were involved: one IG via STSX1 Line Card (LC) installed in a High Speed ATM (HSA) slot and one IG via a DSX1 pair. Using other remote notes with INDLs over different transports (i.e. DSX1, DSX3-CH, MSDSL, T1-UNV2) works fine. Problem seems to be limited to remote nodes with OC3 transports. Symptoms: After a 5-minute period, the lines were automatically placed In-Service (IS) by the Local Digital Switch (LDS). However, did not get dial-tone when phones connected to these lines went off-hook. Phone message display indicates Layer 2 not established. |
| Workaround | None |
| Bug ID | CSCds67131 |
| Description | can not access remote node when INDL flooded with 100% ATM traffic |
| Symptom | Cannot access the remote node from EMS or ping it when INDL is flooded with 100% native ATM traffic. |
| Workaround | Reduce the ATM traffic to available bandwidth. |
| Bug ID | CSCds69623 |
| Description | High & Wet Mntnce-dsbl status on analog phones |
| Symptom | Conditions: Not specific to any Inter-Node Data Link (INDL) or Call Reference Value (CRV) location. Happens with local and remote Loop Start (LS) CRVs. Condition was not experienced with Ground Start (GS) CRVs. Symptoms: Analog LS CRVs sometimes go "High and Wet" at the Local Digital Switch (LDS) when they are assigned to a GR-303 Interface Group (IG). |
| Workaround | Affected CRVs are successfully put In-Service (IS) from the LDS. |
The following sections describe the documentation available for the Cisco 6700 series access devices. The most up-to-date documentation can be found on the web via Cisco Connection Online (CCO) and on the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the hard-copy documents were printed. These release notes should be used in conjunction with the documents listed in Table 2.
The documents listed in Table 2 are available for the Cisco 6700 series access devices. These documents are also available online at Cisco Connection Online (CCO) and on the Documentation CD-ROM.
To access Cisco 6700 series documentation on CCO, follow this path:
Service and Support: Technical Documents: Documentation Home Page: Integrated Access Products: Cisco 6700 Series
To access Cisco 6700 series documentation on the Documentation CD-ROM, follow this path:
DSL Products: Cisco 6700 Series
| Document Title | Part Number | Chapter Topics |
|---|---|---|
Cisco 6732 Full Access Device | 78-10098-02 | Product Overview |
Cisco 6705 Integrated Access Device Hardware Installation Guide | 78-10079-02 | Product Overview |
Cisco 6700 Series Element Management System User Guide for Software Version 1.4
| 78-11372-01 | Overview |
For service and support for a product purchased directly from Cisco, use CCO.
If you have a CCO login account, you can access the following URL, which contains links and tips on configuring your Cisco products:
http://www.cisco.com/kobayashi/serv_tips.shtml
This URL is subject to change without notice. If it changes, point your Web browser to CCO and click on this path: Products & Technologies: Products: Technical Tips.
The following sections are provided from the Technical Tips page:
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language
| E-mail Address
|
|---|---|
| |
| |
| |
| |
| |
| |
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
Posted: Mon Nov 27 09:47:04 PST 2000
Copyright 1989-2000©Cisco Systems Inc.