Table Of Contents
Release Notes for Cisco ONS 15454
Release 8.0Maintenance and Administration
Mismatch Equipment Attributes Alarm on EIA
ONS 15454 Conducted Emissions Kit
CSCdv10824: Netscape Plugins Directory
SONET and SDH Card Compatibility
CSCds13769: Fujitsu FLM-150 and Nortel OC-3 Express
Active Cross Connect (XC10G/XCVT) or TCC2/TCC2P Card Removal
Resolved Caveats for Release 8.0
Maintenance and Administration
New Features and Functionality
MSPP-on-a-Blade Card (ADM-10G)
New Software Features and Functionality
ML-AINS and other Enhanced State Model (ESM) changes.
Link Aggregation Control Protocol (LACP)
DISA Password Complexity, Max Password Length, Min Password Length.
Mozilla 1.7 Supported on Solaris 9 with Java plug-in 5.0.
Superuser Privileges for Provisioning Users
Configuring Mesh DWDM Networks
Automatic Node Turn-Up (Installation without Cisco MetroPlanner)
Obtaining Optical Networking Information
Where to Find Safety and Warning Information
Cisco Optical Networking Product Documentation CD-ROM
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco ONS 15454
Release 8.0
May, 2008
Note
The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.
Release notes address closed (maintenance) issues, caveats, and new features for the Cisco ONS 15454 SONET multiplexer. For detailed information regarding features, capabilities, hardware, and software introduced with this release, refer to the "Release 8.0" version of the Cisco ONS 15454 DWDM Installation and Operations Guide; and the "Release 8.0" version of the Cisco ONS 15454 Procedure Guide; Cisco ONS 15454 Reference Manual; Cisco ONS 15454 Troubleshooting Guide; and Cisco ONS 15454 SONET TL1 Command Guide. For the most current version of the Release Notes for Cisco ONS 15454 Release 8.0, visit the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/ong/15400/454relnt/index.htm
Cisco also provides Bug Toolkit, a web resource for tracking defects. To access Bug Toolkit, visit the following URL:
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl
Contents
•
•
•
Changes to the Release Notes
This section documents supplemental changes that have been added to the Release Notes for Cisco ONS 15454 Release 8.0 since the production of the Cisco ONS 15454 System Software CD for Release 8.0.
Added additional caveats for the DWDM hardware section. Added the MSPP-on-a-Blade (ADM-10G) feature description.
Added additional hardware caveats.
Corrected information that suggested support for CE-MR-10 and ML-MR-10 cards. These two cards are not supported in Release 8.0.
Added the issue of RTRV-FAC TL1 command showing the payload as FSTE instead of GIGE on the ML1000-2 card in the resolved caveats section.
Changes to Caveats
The following caveats have been added to the release notes:
Caveats
Review the notes listed below before deploying the ONS 15454. Caveats with tracking numbers are known system limitations that are scheduled to be addressed in a subsequent release. Caveats without tracking numbers are provided to point out procedural or situational considerations when deploying the product.
Alarms
CSCsj26750
When the card type in CTC is changed from DS1_14 to DS1_E1_56 with DS1-14 physical card in the slot, the LED in DS1_14 card will show Act (Green) LED, instead of Fail (RED) LED. This issue will be resolved in a future release.
Hardware
CSCsg42366
Traffic outage (120 sec) occurs when field-programmable gate array (FPGA) upgrade is done with manual switch on Y-cable and client port is in out of service.
To prevent traffic outage, follow the procedure for the FPGA upgrade:
1.
–
–
–
–
2.
3.
4.
5.
6.
7.
8.
9.
10.
CSCsi64440
A software upgrade from a release prior to 8.0, to 8.0 causes a multi-second outage on the DS3XM-12 card in slots 1,3,5,12,14,16, when XC or XCVT cross connect cards are installed.
A software upgrade from a release prior to 8.0, to 8.0 causes a complete outage on the DS3XM-12 cards in protect slots 2,4,6,13,15,17, when XC or XCVT cross connect cards are installed.
A soft reset in 8.0 causes multi-second outage on the DS3XM-12 card in the slots 1,3,5,12,14,16 when the active XC or XCVT cross connect cards is in slot 8.
A total outage of the DS3XM-12 card in slots 1,3,5,12,14,16 occurs when the active XC or XCVT cross connect card is in slot 10. A hard reset will clear the problem, but a further soft reset will cause an outage again.
A soft reset in 8.0 causes a multi-second outage on the DS3XM-12 card in protect slots 2,4,6,13,15,17 when the active XC or XCVT cross connect card is in slot 10.
A total outage of the DS3XM-12 card in protect slots 2,4,6,13,15,17 occurs when the active XC or XCVT cross connect card is in slot 8. A hard reset will clear the problem, but a further soft reset will cause an outage again.
There is no workaround when using DS3XM-12 and XC or XCVT cross connect cards. Replacing the XC or XCVT with a XC10G or XC-VXC-10G cross connect cards resolves this problem. This will be fixed in a future release.
CSCuk44284
An optical connector and optical attenuators inserted into the SFP may force the fiber against the shelf door when it is closed. Use the following types of optical connectors and optical attenuators when connecting to the SFP:
•
•
–
–
–
CSCsg35496
When slot 17 is switched in 1:N protection for the first time, slot 16 is switched. This issue was observed in Release 7.04 and occurs only at the first-time switch.
CSCse67377
AIS-L Alarm is not visible against EC1 port, if LOS or LOF is injected onto the port. EC1 port is in service and there is no circuit present. This is a hardware limitation which detects AIS-L received from line side, but it cannot raise AIS-L when it receives LOS or LOF from the line.
Jitter Performance with XC10G
During testing with the XC10G, jitter generation above 0.10 UI p-p related to temperature gradient testing has been observed. This effect is not expected to be seen under standard operating conditions. Changes are being investigated to improve jitter performance in a future release. Tracking numbers related to this issue include CSCdv50357, CSCdv63567, CSCdv68418, CSCdv68441, CSCdv68389, CSCdv59621, and CSCdv73402.
CSCdz49928
When using KLM type fuses with specific types of fuse and alarm panels, the PWR-REDUN alarm may not be displayed once the fuse is blown. A KLM fuse does not have a blown fuse indicator built into it. As a result, the blown fuse detection circuitry on the FAP may continue to provide voltage on its output despite a blown fuse.
CSCsi78715
When loss of signal (LOS) occurs on the client side of MXP-MR-2.5G card, the Y-cable protection switch does not occur and drops the traffic. The MXP-MR-2.5G will not report generic framing procedure (GFP) alarms such as client signal fail (CSF) and in case of fiber channel client, the link recovery counter will not be incremented correctly.
Workaround is to manually switch the traffic away from the client experiencing LOS. This will be fixed in a future release.
CSCsi29405
The 15454-FTA3 Fan Tray Assemblies have an electrical noise problem that might cause communications failures between the fan tray and the controller cards. Eventually this condition causes fan tray alarms, and the controller card resets. Also, the LCD might display meaningless characters and the buttons on the LCD will not function normally. Running the fan tray at high speed decreases the noise and prevents the communication failure and the card reset. The workaround is to remove one of the fans, which will cause the fans to run at full speed. This will be fixed in a future release.
Maintenance and Administration
Caution
Note
Note
CSCsc00811
Deleting a monitor circuit and its parent at the same time might result in a PARTIAL parent circuit. To avoid this, delete the monitor circuit before deleting the parent circuit. This issue will not be resolved
CSCsc36281
The software Activating progress popup window might fail to automatically close during multiple or parallel software activations. If this occurs you must manually close the popup window. The following error message might also be raised and need to be closed:
"EID-3251 Unable to complete requested action. Unable to activate because the working software version is newer than the protect one."
To ensure that all nodes are using the correct software version you should close and restart CTC. This issue will be resolved in a future release.
CSCsh02230
If IOS CLI is used to configure Timezone and DST rule configuration then the output shown in the show running config command and show clock detail differ from what was configured. To avoid this issue it is recommended to use CTC provisioning tab to configure clock related provisioning. This issue will be resolved in a future release.
CSCse04103
Applying the forced switch/manual switch on protect facility when no protection switch in operation, FRCDWKSWBK-NO-TRFSW/MANWKSWBK-NO-TRFSW is not raised for 1+1. There is no workaround for this issue.
CSCse87943
RFI-P is raised on both Working and Protect path in a 1+1 topology on an ONS 15310-MA. This occurs with an ML card with an STS cross connection with another ML card in another chassis and when the POS port on the 15310 MA side is shut down. There is no workaround for this issue.
CSCse38590
In the RPR topology, one station reports a "remote WTR" on a space, even though the neighboring station is not advertising WTR. This issue is observed after many XC pulls/switches, deleting and recreating circuits, and replacing cross connects completely. This issue does not appear to have any real impact to traffic, but can potentially complicate troubleshooting. This problem was seen after multiple XC-pulls, XC-side-switches, circuit-deletions and circuit-creations. The workaround is to configure a forced-switch on both ends of the problem span, and then remove the forced-switch from both ends.
CSCsd44081
A series of crashes and reboots may occur when a policy-map includes approximately 200 class-map entries and policers. This error appears to occur when the card is boots up, the FPGA process is attempting to download the new FPGA, the policy-map has at least 200 class-map entries, and traffic has been punted to the host. These conditions may trigger a provisioning-message timeout on the ML card that can lead to a crash. Since the system boots up in the same state, a continuous series of crashed and reboots may occur. A workaround is to remove the circuits and wait until the node boots up with the latest FPGA image before re-configuring the circuits.
CSCse23518
The RPR SPAN-MISMATCH alarm is not reported correctly in some situations. After creating and deleting an East-to-East RPR circuit through TL-1 x-connects and creating a West-to-West RPR circuit through the TL-1 x-connects script, both within less than on second of the other, the RPR-SPAN-MISMATCH alarm is seen only on one side of the circuit and not on the other side. This problem does not occur when the operations are made manually. This alarm indicates mis-cabling or cross-connects created between two East spans or two West spans. A workaround is to ensure more than one second between the deletion of one circuit and creation of the another.
CSCse75851
Trace backs are seen in "show tech" or "show ons alarm defect" output for ML100T-8 on the ONS 15310-CL after logging in through the CTC by way of the IOS CLI. This issue does not occur when these commands are issued through the console. The work-around is to ignore these trace backs because they do not impact the functioning of the data card.
CSCse90514
The soak timer on POS port reduces which is not an expected behavior after creating a circuit on a POS port that is kept in OOS state. There is no workaround for this issue.
CSCse58432
Upgraded splitter OCHCC has OCHTRAILs shown as OOS[PARTIAL]. When upgrading a splitter-protected OCHCC 7.01 to 8.0, in 8.0 the OCHTRAIL circuits are reported as OOS[PARTIAL]. Indeed the two terminal nodes (Source and Destination) report state as OOS,DSBLD. TL1 and TCC report their states as IS-NR.
CSCsg29444
On rare occasions, the STM64 4-port DWDM card may into continuous resets after a node power down. A hard reset of the card usually brings it up normal.
CSCsd00882
In an IDRI setup, with an exiting SRG Violation between one of the rings and the IDRI hand-off spans, the SRG Violation Warning prints the same span twice. This happens only when the circuit is routed manually on a BLSR-path protection or a path protection DRI/IDRI. The functionality of the Circuit Routing is as expected. The one violation gets printed twice because the DRI span traverses twice.
CSCse96118
RTRV-COND-STS does not display path alarms on BLSR protect path. When BLSR is switched onto protection and the protect paths have conditions on them, the TL1 retrieval command does not show those conditions on protection paths.
CSCse53133
RTRV-COND-STS does not display path alarms on BLSR protect path. When BLSR is switched onto protection and the protect paths have conditions on them, the TL1 retrieval command does not show those conditions on protection paths.
CSCsb88234
When a card is provisioned and a filler card is plugged in, a DBCHG with ENT-EQPT is sent, but when a filler card is plugged in without a prior provision there is no plug-in message. Similarly, there is no message upon removal of the filler card. The workaround for TL1-NONE, is to issue an inventory call and the filler card appears. For CTC, the card is displayed and removed when the card is removed.
CSCsg03334
After ML card reset, system comes up with POS0=PSAS true. When nodes from Release 6.2 are activated with ML V-up enabled and there is a soft reset of the ML cards to clear SW-MISMATCH, the ML cards come up with PSAS on for POS 0. Consequently, the port does not report any alarms (only conditions) for eight hours. The NE Default is off for PSAS, so POS 0 should not have PSAS on. The workaround is to manually reset PSAS flag to FALSE.
CSCsg10963
Connections remain in OOS-AU,FLT after roll is cancelled. This occurs under the following conditions:
1.
2.
3.
4.
UNEQ-P alarms clear and connection states remain OOS-AU,FLT.
CSCsg16500
ROLL-PEND condition is seen for VT circuits on the CTC conditions pane.
1.
2.
3.
4.
The ROLL-PEND condition is now visible on VT circuits in CTC, TL1.
CSCsg32263
When DBCHG messages are turned on by using the ALW-MSG-ALL command, there is no DBCHG message when creating and then deleting a proxy firewall tunnel. This issue will be resolved in a future release.
CSCse22576
CTC BLSR views not updated properly after consecutive ENT-MSSPR commands. After entering 16 consecutive ENT-MSSPR TL1 commands across three nodes, the CTC does not update the NetView > BLSR table. The workaround is to restart the CTC so it shows the screens properly. This issue will be resolved in a future release.
CSCse91968
The AINS-to-IS transition on BLSR 4F Protect not functioning properly. When a BLSR 4fibre ring is used, the AINS-to-IS transition is not correct when protect is active (ring switched). Sometimes the wrong protect is transitioning at the IO. If the TSC is notified incorrectly, it becomes out of sync with the IO, and becomes stuck in AINS, even when the protect switch is released. The PCA is also being incorrectly notified of an AINS-to-IS transition. This issue will be resolved in a future release.
CSCse92248
System does not declare TIM-P or retrieves received J1 Path Trace value on switched BLSR. With BLSR switched onto the protect. With the J1 path trace value changed on one node, the receiving node is not retrieving the new J1 Path Trace value and, therefore, is not raising the TIM-P alarm. This issue will be resolved in a future release. This issue will be resolved in a future release.
CSCsf01901
Standby TSC may continuously reboot and Node may loose visibility when there is a huge number of alarm transitions on the node for more than an hour. The standby TSC should be hard reset and the visibility will be regained. This issue will be resolved in a future release.
CSCsf96856
Database Restore may fail with a large database. When restoring a large database with full-capacity cross connects, alarms, and PM databases, the restoration through CTC may fail with an error. A workaround is to attempt the database operation again and it usually succeeds. This issue will be resolved in a future release.
CSCsg00090
There is no response when command "RTRV-TH-STS1::all:1;" is issued. Expected behavior is a DENY response with the correct error message or COMPLD response with the appropriate threshold values displayed. This issue will be resolved in a future release.
CSCsg16680
RTRV-PM-<mod2_path> does not display any PM counts for ALL aid. The TL1 command is COMPLD, but nothing displays. This issue arises when 2F-BLSR circuits are provisioned with IPPM enabled and B3 errors are injected and where some PM counts are generated. Then, STS12c circuits are created and the command RTRV-PM-STS12c::all:1 is executed. Otherwise, RTRV-PM-ALL works fine, and RTRV-PM-<mod2_path> with individual AID works normally.
CSCsg13597
After pulling line cards out of shelves involved in the DCC between nodes a EOC alarm was raised and did not clear after the cards were re-inserted.
DWDM Cards
CSCsg22669
There is a traffic hit of greater than 50ms but less than 60 ms on MXP-2.5G-10E in Y cable configuration when a fiber cut occurs.
CSCsf04299
When triggering the switch of optimized 1+1 protection and the failure is cleared, the WTR condition is raised, but once the WTR time expires the switch back of protection is not triggered. A workaround is to manually force back the protection.
CSCse97200
On ADM-10G, attempts to pre-provision local and express orderwire circuits on trunk port are not successful. E1/E2 orderwire is not supported.
Hardware
CSCse74522
The LAN front panel LEDs of the standby TCC were switched OFF (i.e. no lights, port disabled). Multishelf MSTP with SSC connected to the Node Controller via Catalyst 3750.
Mismatch Equipment Attributes Alarm on EIA
In Release 6.0 a Mismatch Equipment Attributes (MEA) alarm is raised incorrectly against the B-Side BIC (EIA) on an ONS 15454 node using the 15454-SA-HD (high density) chassis with 1BNCB48, 1BNCB24, or 1SMBB84 EIAs installed. The 1BNCB48, 1BNCB24, and 1SMBB84 EIA panels are compatible with the 15454-SA-HD shelf assembly; however, the software in Release 6.0 fails to recognize their compatibility. The MEA alarm raised as a result of this issue is not service impacting, but does cause a standing alarm.
As a workaround to the standing alarm, you can change the BIC-MEA alarm severity by creating and using a custom alarm profile following the steps that apply for your network in the NTP-A71 Create, Download, and Assign Alarm Severity Profiles procedure of the Manage Alarms chapter in the Cisco ONS 15454 Procedure Guide, Release 6.0. This issue will be resolved in Release 6.1.
CSCeh84908
A CTC client session can disconnect from an ONS node during simultaneous deletion of large numbers of VT level circuits (3000+). Connectivity to the node will recover without any user action. If the condition persists, restart the CTC session to reconnect. This issue is under investigation.
CSCei36415
When retrieving GBIC inventory for the FC_MR-4, nothing is returned for the CLEI code. In a future release, enhanced inventory information will be available for ONS GBICs. This will include the CLEI code.
CSCeh92201
When you create a bidirectional BLSR-path protection IDRI circuit using auto-routing and select the PCA option for secondary spans, the circuit is created over working BLSR spans and does not use PCA spans. To enforce the use of the PCA option, provision the circuit using manual routing. This issue will not be resolved.
CSCee96164
The Wait To Restore (WTR) alarm does not appear to be raised for as long as the WTR timer is set for. The WTR is raised correctly, but the alarm is hidden for the first 12 seconds due to the clear soaking time for a CLDRESTART alarm. You can see this behavior if you set up a 1+1 bidirectional revertive protection group, remove the working card, and then reinsert the card. There are no plans to change this behavior.
CSCee25136
If you create a PM schedule with the Start time for the PM report equal to 00:00 (in TL1, "0-0"), after a few minutes the PM report start time might change to 23:59 (in TL1, "23-59"). This issue will not be resolved.
CSCed23484
A user might remain in the logged-in state after rebooting the PC while logged into a node running CTC. The user login will time out once the "Idle User Timeout" limit is up. Alternatively, you can log in as a superuser and force the user off. This issue will not be resolved.
CSCds88976
When a new circuit is created around a ring (path protection or BLSR), the SD BER or SF BER alarm can be raised depending on the order in which the spans are provisioned. The alarms will eventually clear by themselves. Traffic is not affected. This issue will not be resolved.
CSCdu82934
When you auto-route a VT circuit on an ONS 15454 node, a path is computed based on the availability of STSs on the nodes involved. This selection process, when combined with a lack of VT matrix (or STS-VT connections) on an auto-route selected node, can result in the VT circuit creation failing with the message "unable to create connection object at node." To correct this situation, manually route VT circuits in cases when auto-routing fails. The error message will indicate which node is at issue.
CSCef28522
When you inject errors on a splitter protection card in the node's working port, CVL and ESL are incremented for the working and protect far end ports. This issue will not be resolved.
CSCuk49106
The amplifier gain set point shown by CTC and the actual measured amplifier gain differ. The following steps illustrate this issue.
Step 1
Step 2
The APC procedure does not check consistency between the gain set point and the real gain, but rather only verifies the amplifier total output power. As a workaround, manual setting can be performed to align these values, although the discrepancy does not impact the normal functioning of the amplifier. This issue will not be resolved.
CSCef05162
Clearing the displayed statistics for a port will also clear the displayed history for that port. Clearing the displayed statistics for all ports will also clear the displayed history for all ports. There is no warning message from the TCC2. If History information is to be retained, do not clear displayed statistics for any port without first documenting the displayed history information for the associated port. This issue will not be resolved.
CSCef29516
The ALS pulse recovery minimum value is 60 instead of 100. If this occurs, increase the value to 100. This issue will not be resolved.
CSCeb36749
In a Y-Cable configuration, if you remove the client standby RX fiber; a non-service affecting LOS is raised, as expected. However, if you then remove the trunk active RX fiber; a non-service affecting LOS-P is raised, but the previously non-service affecting LOS on the client port is now escalated to a service affecting alarm, in spite of no traffic having been affected. This issue will not be resolved.
CSCee82052
After setting the node time (either manually or via NTP) you must wait for the endpoint of the interval to be reached before the end time will reflect the recently-set node time. Until this has occurred, the date time stamp for the end of the retrieved interval remains 12/31/69. This issue has been closed and will not be resolved.
CSCdx35561
CTC is unable to communicate with an ONS 15454 that is connected via an Ethernet craft port. CTC does, however, communicate over an SDCC link with an ONS 15454 that is Ethernet connected, yielding a slow connection. This situation occurs when multiple ONS 15454s are on a single Ethernet segment and the nodes have different values for any of the following features:
•
•
•
When any of these features are enabled, the proxy ARP service on the node is also disabled. The ONS 15454 proxy ARP service assumes that all nodes are participating in the service.
This situation can also occur immediately after the aforementioned features are enabled. Other hosts on the Ethernet segment (for example, the subnet router) may retain incorrect ARP settings for the ONS 15454s.
To avoid this issue, all nodes on the same Ethernet segment must have the same values for Enable OSPF on the LAN, Enable Firewall, and Craft Access Only. If any of these values have changed recently, it may be necessary to allow connected hosts (such as the subnet router) to expire their ARP entries.
You can avoid waiting for the ARP entries to expire on their own by removing the SDCC links from the affected ONS 15454 nodes. This will disconnect them for the purposes of the proxy ARP service and the nodes should become directly accessible over the Ethernet. Network settings on the nodes can then be provisioned as desired, after which the SDCC can be restored.
This issue will not be resolved.
CSCdy56693
Microsoft Windows XP uses more memory than previous Microsoft operating systems, and this may result in reduced CTC performance. To avoid reduced performance, you can:
•
•
•
•
•
CSCdy62092
When a node connected via SDCC has no Ethernet LAN connectivity, display of SDCC termination alarms is delayed if the fiber connecting a DCC connected node is removed. This issue cannot be resolved.
CSCdy10030
CVs are not positively adjusted after exiting a UAS state. When a transition has been made from counting UAS, at least 10 seconds of non-SES must be counted to exit UAS. When this event occurs, Telcordia GR-253 specifies that CVs that occurred during this time be counted, but they are not. There are no plans to resolve this issue at this time.
CSCdy11012
When the topology host is connected to multiple OSPF areas, but CTC is launched on a node that is connected to fewer areas, the topology host appears in CTC, and all nodes appear in the network view, but some nodes remain disconnected. This can occur when the CTC host does not have routing information to connect to the disconnected nodes. (This can happen, for example, if automatic host detection was used to connect the CTC workstation to the initial node.)
CTC will be able to contact the topology host to learn about all the nodes in all the OSPF areas, but will be unable to contact any nodes that are not in the OSPF areas used by the launch node. Therefore, some nodes will remain disconnected in the CTC network view.
To work around this issue, if no firewall enabled, then the network configuration of the CTC host can be changed to allow CTC to see all nodes in the network. The launch node must be on its own subnet to prevent network partitioning, and craft access must not be enabled. The CTC host must be provisioned with an address on the same subnet as the initial node (but this address must not conflict with any other node in the network), and with the default gateway of the initial node. CTC will now be able to contact all nodes in the network.
If a firewall is enabled on any node in the network, then CTC will be unable to contact nodes outside of the initial OSPF areas. This issue will not be resolved.
NE Defaults
The following caveats apply for NE defaults when managing older, pre-Release 4.5 nodes.
•
•
•
ONS 15454 Conducted Emissions Kit
If you are deploying the Cisco ONS 15454 within a European Union country that requires compliance with the EN300-386-TC requirements for Conducted Emissions, you must obtain and install the Cisco ONS 15454 Conducted Emissions kit (15454-EMEA-KIT) in order to comply with this standard.
CSCdv10824: Netscape Plugins Directory
If you use CTC, JRE, and the Netscape browser with a Microsoft Windows platform, you must ensure that any new installation of Netscape uses the same Netscape directory as the previous installation did, if such an installation existed. If you install Netscape using a different path for the plugins directory, you will need to reinstall JRE so that it can detect the new directory.
"Are you sure" Prompts
Whenever a proposed change occurs, the "Are you sure" dialog box appears to warn the user that the action can change existing provisioning states or can cause traffic disruptions.
Common Control Cards
CSCdw27380
Performing cross connect card switches repeatedly might cause a signal degrade condition on the lines or paths that can trigger switching on these lines or paths. If you must perform repeated cross connect card switches, lock out the corresponding span (path protection, BLSR, or 1+1) first. This issue will not be resolved.
CSCsj39710
In CTC Card View, Maintenance Pane, the Loopback Type displays as False. The parameter is to be set to True. A workaround is to manually set the parameter to True. This is for the release(s) prior to 8.0.
This is for cards OC-3, OC-12, OC-48, and OC-192. This issue is resolved in this release.
Ethernet Polarity Detection
The TCC2/TCC2P does not support Ethernet polarity detection. The TCC+ and TCCI both support this feature. If your Ethernet connection has the incorrect polarity (this can only occur with cables that have the receive wire pairs flipped), the TCC+/I will work, but the TCC2/TCC2P will not. In this event, a standing condition, "LAN Connection Polarity Reverse Detected" (COND-LAN-POL-REV), will be raised (a notification will appear on the LCD, and there will be an alarm raised). This issue will most likely be seen during an upgrade or initial node deployment. To correct the situation, ensure that your Ethernet cable has the correct mapping of the wire wrap pins. For Ethernet pin mappings, consult the user documentation.
Optical IO Cards
CSCsk03288
The OC48-LR-1550-1 optical card with P/N 87-32-00001 and firmware (bootrom) rev number 76-99-00014-x02a continuously reboots and does not start up during upgrade to a software release 7.20 through 7.23 or 8.0.
Before upgrading to releases 7.20, 7.21, 7.22, 7.23 or 8.0, it is recommended to retrieve the inventory list through CTC or TL1 and check the HW part number field for 87-32-00001 and firmware rev field for 76-99-00014-x02a. If any card matches the HW part number and firmware rev number, replace it with the newer version of the OC48 card such as the OC48AS or MRC card.
This issue will be resolved in Release 8.5.
CSCei26718
On the 15454_MRC-12, when a one way VT/VC circuit on path protection over 1+1 protection is
created, the alarm behavior is not the same as in two way circuit creation. In particular, for the one way circuit creation, UNEQ-V and PLM-V alarms are reported, and the circuit state remains OOS. This issue will not be resolved.
CSCdw66444
When an SDH signal is sent into an ONS 15454 OC-12/STM-4 (IR, 1310 LR and 1550 LR) or an OC-48/STM-16 high-speed (IR and LR) port which has been configured to support SDH, an SD-P (Signal Degrade) alarm will appear as soon as the circuit is created. This alarm will continue to exist until the circuit is deleted.
To avoid this problem, when provisioning an OC-12/STM-4 (IR, 1310 LR and 1550 LR) or an OC-48/STM-16 high-speed (IR and LR) port to support SDH, disable the signal degrade alarm at the path level (SD-P) on the port.
Also, PM data at the path level will not be reliable. You must set associated threshold values to 0 in order to avoid threshold crossing alerts (TCA) on that port. The path threshold values to set to zero are CV-P, ES-P, SES-P, and UAS-P.
These issues are the result of a hardware limitation, and there are no current plans to resolve them.
CSCdw09604
If you are using an XC10G with OC-48, you must use either OC-48AS or OC-48 cards with a revision number higher than 005D.
Electrical IO Cards
CSCsc65320 and CSCin92295
In a DS3-EC1-48 1:N protection group for which a path protection circuit drops onto a 1:N protected card, if you remove the card and then reseat it the switch time might exceed 60 ms. This issue will be resolved in a future release.
CSCei59527
When an XC switch occurs, LOF is driven to the line side. On a DS1-14 this can cause us to see long switch times that are related to hardware issues if the "Treat LOF as a Defect" flag has been set. To avoid this issue, do not set the "Treat LOF as a Defect" flag to true on DS1-14 cards. A future release will remove the "Treat LOF as a Defect" option for this card.
CSCeh43011
An LOS alarm is cleared when switching to protect when the working card is on opposite side of the shelf from the protect card (in portless configuration) in a DS3XM-12 1:N protection group. An electrical port brought into IS state on the portless only card produces an LOS alarm. If you then switch to protect, the alarm appears to clear. To avoid this issue, do not bring electrical ports into IS state on a portless only card. This issue will be resolved in a future release.
CSCdx40300
A transient WKSWPR condition is raised upon deletion of a DS3XM 1:1 protection group. This issue will be resolved in a future release.
CSCec39567
Deleting a DS3I 1:N protection group may leave the protect card LED in a standby state. This can occur in a DS3I 1:N protection group with a LOCKON applied to the working card (ONS 15454 ANSI chassis only). Upon deleting the protection group, the LED on the protect DS3I card and the CTC display are still in the standby state. Soft reset the protect card to update the LED on the card and in CTC. An alternative workaround is to remove the LOCKON before deleting the protection group. This issue will be resolved in a future release.
Data IO Cards
SONET and SDH Card Compatibility
Tables 1, 2, and 3 list the cards that are compatible for the ONS 15454 SONET and ONS 15454 SDH platforms. All other cards are platform specific.
CSCsc11981
Under certain circumstances, E-series cards might learn invalid MAC addresses and temporarily lose well-known/static addresses, possibly resulting in high flood rates. This issue can occur when traffic flows through an E-series card and there are no MAC addresses currently in the MAC table for that E-series card (for instance, after you have cleared the complete MAC table, or when the node is just coming up). The chipset can cause the E-series card to learn invalid addresses in this scenario under high rates of flood traffic (multicast, broadcast, unknown) or PHY interface noise. Side-effects of clearing the MAC table when traffic is flowing can cause the E-series card to lose well-known/static MAC addresses along with dynamically learned MAC addresses. This can cause high flood rates (multicast, broadcast, unknown) possibly reaching the limitation described in the following field notice:
http://www-tac.cisco.com/Support_Library/field_alerts/fn13171.html
This issue can last for a few seconds (typically less). The workaround is to avoid issuing any operation (such as the "Clear all MAC" command) that clears the complete MAC table under heavy traffic loads. To recover from this issue, wait for a few seconds to let the invalid addresses age out, and to allow the software to restore the well-known/static MAC addresses.
CSCdy37198
On Cisco ONS 15454s equipped with XCVT cross-connect cards, neither the E100T-12 nor the E1000-2 cards raise an alarm or condition in CTC when Ethernet traffic is predictably lost due to the following circumstances:
Circuits exist between Ethernet cards (E100T-12 and/or E1000-2) built over Protection Channel Access (PCA) bandwidth on BLSR spans. When BLSR issues a switch, the PCA bandwidth is preempted. Since there is no longer a connection between the ends of the Ethernet circuit, traffic is lost.
Note
This issue will not be resolved.
CSCdr94172
Multicast traffic can cause minimal packet loss on the E1000-2, E100-12, and E100-4 cards. Packet loss due to normal multicast control traffic should be less than 1%. This issue was resolved in Release 2.2.1 for broadcast, and in Release 2.2.2 for OSPF, and some multicast frames. As of Release 3.0.3, the ONS 15454 supports HSRP, CDP, IGMP, PVST, and EIGRP, along with the previously supported broadcast and OSPF.
Note
Note
Note
Multicast MAC addresses used by the control protocols in Table 4 have been added to the static MAC address table to guarantee no loss of unicast traffic during normal usage of these MAC addresses.
E1000-2/E100T
Do not use the repair circuit option with provisioned stitched Ethernet circuits.This issue is under investigation.
Single-card EtherSwitch
Starting with Release 2.2.0, each E100/E1000 card can be configured as a single-card EtherSwitch configuration to allow STS-12c of bandwidth to be dropped at each card. The following scenarios for provisioning are available:
1.
2.
3.
4.
5.
6.
7.
When configuring scenario 3, the STS-6c must be provisioned before either of the STS-3c circuits.
Multicard EtherSwitch
When deleting and recreating Ethernet circuits that have different sizes, you must delete all STS circuits provisioned to the EtherSwitch before you create the new circuit scenario. (See the preceding "Single-card EtherSwitch" section for details on the proper order of circuit creation.) Enable front ports so that the VLANs for the ports are carried by the largest circuit first. A safe approach is to enable the front port before you create any circuits and then retain the front port VLAN assignment afterwards. If you break the rules when creating a circuit, or if you have to delete circuits and recreate them again, delete all circuits and start over with the largest first.
CSCds02031 E1000-2/E100
When you drop two 3c multicard EtherSwitch circuits onto an Ethernet card and delete only the first circuit, you should not provision STS-1 circuits to the card without first deleting the remaining STS-3c circuit. If you attempt to create an STS-1 circuit after deleting the first STS-3c circuit, the STS-1 circuit will not work and no alarms will indicate this condition. Under rare conditions, this could trigger a TCC reset. To avoid a failed STS-1 circuit and other possible problems, delete the second STS-3c prior to creating any STS-1 circuit.
CSCed96068
If an ML-Series card running Software Release 4.6.2 or later is interoperating with an ML-Series card running Software Release 4.6.0 or 4.6.1, then the pos vcat resequence disable command must be added to the configuration of the ML-Series card running R4.6.2 or later. For documentation of this command, consult the Ethernet Card Software Feature and Configuration Guide.
CSCec52443
On an ML-series RPR ring circuit deletion or creation causes an approximately 200 ms traffic loss. To avoid this issue, from the ML-series CLI, perform a "shutdown" on both ends of the circuit prior to circuit changes. This issue will not be resolved.
CSCec52372
You must issue a "shut" command to both ends of a POS circuit before placing the circuit OOS, and issue IS before a "no shut" command. Placing a POS circuit OOS without shutting down can cause long traffic hits. This issue will not be resolved.
CSCec51252
You must issue a "shut" on both ends of affected POS circuits before performing a maintenance action on those circuits. If a POS circuit is restored without first issuing the shut commands, one end of the circuits could come up before the other. During that time, traffic is lost because the other end is not up yet. This issue will not be resolved.
CSCea46580
SPR input counters do not increment on a BVI with an SPR interface. This issue will not be resolved.
CSCea35971
A monitor command may disappear from the configuration after a TCC reboots. To avoid this issue, use the exec command, "terminal monitor," instead (a minor drawback is that this command applies to all VTYs), or, alternatively, reapply the monitor command after connection is lost. This is as designed.
CSCdz49700
The ML-series cards always forward Dynamic Trunking Protocol (DTP) packets between connected devices. If DTP is enabled on connected devices (which might be the default), DTP might negotiate parameters, such as ISL, that are not supported by the ML-series cards. All packets on a link negotiated to use ISL are always counted as multicast packets by the ML-series card, and STP and CDP packets are bridged between connected devices using ISL without being processed. To avoid this issue, disable DTP and ISL on connected devices. This functionality is as designed.
CSCdz68649
Under certain conditions, the flow-control status may indicate that flow control is functioning, when it is not. Flow-control on the ML-series cards only functions when a port-level policer is configured. A port-level policer is a policer on the default and only class of an input policy-map. Flow-control also only functions to limit the source rate to the configured policer discard rate, it does not prevent packet discards due to output queue congestion.
Therefore, if a port-level policer is not configured, or if output queue congestion is occurring, policing does not function. However, it might still mistakenly display as enabled under these conditions. To avoid this issue, configure a port-level policer and prevent output queue congestion. This issue will not be resolved.
CSCdz69700
Issuing a shutdown/no shutdown command sequence on an ML1000 port clears the counters. This is a normal part of the startup process and there are no plans to change this functionality.
CSCin29274
When configuring the same static route over two or more interfaces, use the following command:
ip route a-prefix a-networkmask a.b.c.d
Where a.b.c.d is the address of the outgoing gateway, or, similarly, use the command:
ip route vrf vrf-name
Do not try to configure this type of static route using only the interface instead of the address of the outgoing gateway. This issue will not be resolved.
CSCin32057
If no BGP session comes up when VRF is configured and all interfaces have VRF enabled ensure that at least one IP interface (without VRF) is configured and add an IP loopback interface on each node. This issue will not be resolved.
CSCdy47284
ML-100 FastEthernet MTU is not enforced. However, frames larger than 9050 bytes may be discarded and cause Rx and Tx errors. This issue will not be resolved.
CSCdz74432
Issuing a "clear IP route *" command can result in high CPU utilization, causing other processes to be delayed in their execution. To avoid this issue do not clear a large number of route table entries at once, or, if you must use the "clear IP route *" command, do not install more than 5000 EIGRP network routes.
DWDM Cards
CSCsd92505
Traffic hits of 100 ms to 300 ms might occur during an OPT-PRE or OPT-BST card software reset or firmware upgrade. This occurs only with cards displaying the vendor ID 1025 in the CTC node level inventory tab when the following conditions are present for the affected card.
•
–
•
–
This issue is resolved in Release 7.0.1 and all subsequent releases except for Release 7.2.
CSCei19148
When a port is placed in-service while the conditions necessary to squelch the port are present, as in when the trunk port on a DWDM card is OOS,DSBLD and a client port is placed in-service, the client will momentarily enable, emitting light, before squelching due to the trunk OOS,DSBLD condition. The pulse is approximately 500 ms. This issue will not be resolved.
CSCei87554
When using a 1GE payload over the TXP_MR_2.5G the IfInErrors counter does not report oversized, undersized, or CRC errored frames, but rather, reports frame coding only. This issue will not be resolved.
CSCsb47323
For MXP_MR_10DME-C and MXP_MR_10DME-L cards, an unexpected RFI condition might be raised along with an OTUk-BDI. When there is an LOS downstream, the node receives OTUk-BDI. Because of the placement of dual OTN and SONET wrappers, it can also receive an RFI. This issue will not be resolved.
CSCsb79548
A long traffic hit can occur when an active TCC2/TCC2P resets while an MXP_MR_10DME-C or MXP_MR_10DME-L card is rebooting.
This issue can be reproduced as follows:
Step 1
Step 2
Step 3
Step 4
OTUk/ODUk-SD, FEC Uncorrected word alarms are raised on the trunk port. Traffic goes down and does not recover until the MXP_MR_10DME card is able to come up. It is not known when or if this issue will be resolved.
CSCsb94736
After a fault condition (trunk LOS or Y-cable switch) an MXP_MR_10DME card might fail to detect the login message and traffic might not start for some minutes (after multiple login trials). This can occur in an N-F configuration with MDS switch and MXP_MR_10DME distance extension on, where test equipment traffic is set to 2G Fibre channel (FC) full bandwidth occupancy and started. Stop traffic or keep bandwidth occupancy below 80% during the login phase to work around this issue. This issue will not be resolved.
CSCsb95918
All GFP related alarms are raised with their active severities on the standby card after a Y-Cable protection switch. When a DWDM card (with GFP support) in a Y-Cable protection group becomes standby as a result of a Y-Cable protection switch, the GFP alarms raised when the card was active retain their severities instead of assuming standby severities. The alarms can be seen in the alarm pane if not suppressed, or in the condition pane if suppressed. This issue will be resolved in a future release.
CSCsc36494
Manual Y cable switches with squelching turned off can cause a Fibre channel link with brocade switches to go down.
This issue can be reproduced as follows:
Step 1
Step 2
Step 3
Step 4
After a few switchovers, the FC link will go down. SIGLOSS and GFP-CSF alarms are seen on the CTC.
Cisco recommends you provision squelching to be on when interworking with brocade switches. If for some reason, squelching must be off with brocade switches, Cisco recommends you use a FORCE command to perform Y cable switches. It is not known when or if this issue will be resolved.
CSCsc60472
CTC is not able to discover a TL1 OCHCC circuit provisioned over an ITU-T line card (ITU-T OC48/STM16 and ITU-T OC192/STM64). This issue can occur when, using the TL1 client interface, you create the OCHNC layer that will be used by the OCHCC circuit, then create the OCHCC connections that involve the ITU-T line cards. The result is an OCHNC and two OCHCC partial circuits, instead of an OCHNC and a single OCHCC complete circuit. This issue will not be resolved.
CSCsc14290
LOW communication between two nodes equipped with TXP-MR-10E and AIC-I cards does not work with TXP-MR-10E cards in line termination mode, G.709 enabled, GCC present on the trunk port, and LOW circuits created between the transponders and AIC-I; Cisco recommends that you use EOW instead. This issue will be resolved in a future release.
CSCeh94567
Setting a Terminal loopback on an MXP-2.5G-10G trunk port causes OTUK alarms.
This can occur under the following conditions.
1.
2.
3.
4.
This terminal loopback causes OTUK-LOF and OTUK-IA alarms to be reported on both MXP-2.5G-10G trunk ports. This issue will not be resolved.
CSCef15415
RMON TCAs are not raised on the TXPP_MR_2.5G client port after a hardware reset. To see this issue, provision two nodes with TXPP_MR_2.5G (TXP-1 and TXP-2) as follows.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
After the card reboots, only DWDM-A and DWDM-B (trunk) port RMON TCAs are raised in the CTC History pane. RMON TCAs for port 1 (client) are not raised. This issue will not be resolved.
CSCef15452
RMON TCAs are not raised when the RMON history is cleared on TXPP_MR_2.5G card. To see this issue, provision two nodes with TXPP_MR_2.5G (TXP-1 and TXP-2) as follows.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
RMON TCAs are not raised for any port. This issue will not be resolved.
CSCuk48503
Under very specific conditions the MXPD fails the Telcordia GR-253/G.825 Jitter generation mask test on the 10G transmit trunk port. The 2.5 G transmit client jitter generation remains within mask and does not exhibit this issue.
This only occurs when, in SONET mode, with no FEC, no G,709, and client interfaces looped back, with non-synchronous clocking, and performing the following steps.
Step 1
Step 2
The jitter testbox TX clock recovers from RX with an additional 5 ppm offset added. This issue will not be resolved.
CSCef50726
Receive client fiber removal can cause a switch from the protect to the active in a TXPP_MR_2.5G. To see this issue, perform the following steps.
Step 1
Step 2
<
Guest
