Release Notes for Cisco ONS 15310-MA Release 7.0.7

OL-15522-01June 27, 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 15310-MA. For detailed information regarding features, capabilities, hardware, and software introduced with this release, refer to Release 7.0 of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide, Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, Cisco ONS SONET TL1 Command Guide, and the Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide. For the most current version of the Release Notes for Cisco ONS 15310-MA Release 7.0.7, visit the following URL:

Contents

Changes to the Release Notes

This section documents supplemental changes that have been added to the Release Notes for Cisco ONS 15310-MA Release 7.0.7 since the production of the Cisco ONS 15310-MA System Software CD for Release 7.0.7.

No changes have been added to the release notes for Release 7.0.7.

Caveats

Review the notes listed below before deploying the ONS 15310-MA. 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.

Maintenance and Administration

Caution VxWorks is intended for qualified Cisco personnel only. Customer use of VxWorks is not recommended, nor is it supported by Cisco's Technical Assistance Center. Inappropriate use of VxWorks commands can have a negative and service affecting impact on your network. Please consult the troubleshooting guide for your release and platform for appropriate troubleshooting procedures. To exit without logging in, enter a Control-D (hold down the Control and D keys at the same time) at the Username prompt. To exit after logging in, type "logout" at the VxWorks shell prompt.

CSCsc56694

IPPM enabled by CTC for an OCn trunk card is disabled automatically after two hours. This issue will be resolved in Release 8.0.

Alarms

CSCse85355

The NE should report alarms or conditions on ingress port not on any internal ports. Alarm detected at the internal ports (TERM) side will be ingress map to the MON side. So the NE raises the STS-MON/VT-MON and STS-TERM/VT-TERM alarms or conditions on the STS-MON/VT-MON ports, irrespective of the actual detection port (MON or TERM). If the user wants the customized severity to be reflected for a specifc STS/VT alarms, the alarm profile entities of both STS-MON and STS-TERM, if available, should be changed to the same severity.

CSCsd52665

The NE should report alarms or conditions on ingress port not on any internal ports. Alarm detected at the internal ports (TERM) side will be ingress map to the MON side. So the NE raises the STS-MON/VT-MON and STS-TERM/VT-TERM alarms or conditions on the STS-MON/VT-MON ports, irrespective of the actual detection port (MON or TERM). If the user wants the customized severity to be reflected for a specifc STS/VT alarms, the alarm profile entities of both STS-MON and STS-TERM, if available, should be changed to the same severity.

CSCsd56328

The NE should report alarms or conditions on ingress port not on any internal ports. Alarm detected at the internal ports (TERM) side will be ingress map to the MON side. So the NE raises the STS-MON/VT-MON and STS-TERM/VT-TERM alarms or conditions on the STS-MON/VT-MON ports, irrespective of the actual detection port (MON or TERM). If the user wants the customized severity to be reflected for a specifc STS/VT alarms, the alarm profile entities of both STS-MON and STS-TERM, if available, should be changed to the same severity.

Electrical IO Card

CSCsh17691

The 3-DS3 / 84 DS1 pack does not output any DS3 rate signal, i.e. no pulses, while in the IS or IS, AINS states if a crossconnection to the port is not in effect. The pack should put out a DS3 AIS signal when not crossconnected, regardless of its state. This appears when the crossconnection to the port is not present. No workaround available. This issue will be resolved in Release 8.01.

Common Control Cards

CSCsc52028

The CTX 2500 card does not accept more than 52 ENE sessions. Figuring 16 ENE sessions per GNE session, the expected ENE logins for 7 GNE sessions is 112, whereas the CTX 2500 accepts only 52. This issue will be resolved in Release 8.0.

Alarms

CSCse85355

After setting the alarm profile to report UNEQ-V as CR, the alarm still reports as the default, MJ, in some instances. To see this, on a single ONS 15310-MA create a path protection VT circuit using a single source with a primary and secondary destination to create the path selector. Inject UNEQ-V into the protect path (for example, CTX2). This declares a minor UNEQ-V. Now inject UNEQ-V into the working path (for example, CTX1). A major UNEQ-V will be declared, rather than the CR that the alarm profile is set to. If the UNEQ-V is injected into the working path first, then into the protect path, a CR UNEQ-V will be declared and is correct. The workaround is to apply profiles for UNEQ-V monitor and UNEQ-V term that both have the same severity desired. This issue will be resolved in a future release.

CSCsh20447

When you have two open slots and if you enable Alarms on open slots and do a retrive all alarms from TL1 Session you can see only one alarm even though you have two open slots. In 7.04 load, in CTC Provisioning->defaults->node->general->RaiseAlarmOnOpenSlot set this flag to true. Open a TL1 session; give RETR-COND-ALL: C. This issue is expected to be fixed in a future release.

CSCsh22922

Create a path protection between 310ma and 454 nodes have a loopback for OC3 card in 454. Create a vt circuit from 310ma to OC3 in 454. Connect test set to ds1 and pump traffic on ds1 port. From the CTC do edit circuit option, in switch column give a Manual to Protection switch. MAN-REQ alarm rises with severity as MN/NA. Change the severity of this alarm from CTC and give APPLY. Do a SYNC option from CTC. Even though you changed the severity of the Alarm that wont reflects in Conditions Pane. If you do a switch from Manual to working this works fine. This issue will be resolved in Release 8.0.

CSCsh20419

When you have two OPEN SLOTS in 15310MA and if you enable alarms on Open slots you will see only one alarm getting raised in Condition Pane of CTC. In 7.04 load, in CTC Provisioning->defaults->node->general->RaiseAlarmOnOpenSlot, set this flag to true. Do retrive in Conditions Pane. Only one alarm is raised, even though you have 2 open slots. This issue is expected to be fixed in a future release.

TL1

Note To be compatible with TL1 and DNS, all nodes must have valid names. Node names should contain alphanumeric characters or hyphens, but no special characters or spaces.

CSCsc51017

When multiple TL1 GNE and ENE sessions are created on a 30+ node network, some of the TL1 sessions might continue to be displayed in the user login pane under the network view, even when the sessions have been closed. If this occurs, restart CTC. This issue will be resolved in a future release.

CSCsh24550

Issuing the RTRV-NE-IPMAP command with ALL aid from TL1 to a 15310MA node retrieves the IP of 454 on the other side of DCC more than once. Command that creates the problem: RTRV-NE-IPMAP:: ALL: A; This issue will be resolved in Release 8.0.

CSCsh21744

The performance Monitoring registers for the counts SASCPP, UASCPP, SESCPP, ESCP, and CVCPP are not initialized to zero. May lead to a Threshold Crossing Alert. 1. DS1-28-DS3-EC1-3 and DS1-84-DS3-EC1-3 cards on 15310MA. 2. The DS3 ports configured with C-BIT frame format. 3. Command which will create the problem INIT-REG-T3: T3-1-1:1:: CVCPP; or SASCPP or SESCP or UASCP or ESCP.

Workaround: All the registers can be cleared at one go through the CTC or by the following TL1 command. INIT-REG-T3: T3-1-1:1: all. This issue is expected to be resolved in 8.01 release.

Resolved Caveats for Release 7.0.x

This section documents caveats resolved in Release 7.0.x.

Maintenance and Administration

CSCsl04416

When a node is upgraded from 4.14 release to 7.05 release, the Back Plane (BP) LAN connection goes to down state. If slot 7 has the active TCC on the 4.14 release and we try to activate to 7.05 release, there is a high probability that the BP LAN stays in down state.

The workaround is to make TCC in slot 11 active, before the activation to 7.05 release.

The problem is solved by protecting the critical area of the LAN port during the activation process. This issue is resolved in release 7.0.7.

Note If the upgrade from release 4.14 to 7.05 causes the Back Plane LAN to go down, the only way to bring it back up is to:1. Reset the active TCC2. Issue the vxWork command to re-enable the BP LAN

CSCsg17018

The Inhibit FE loopback parameter for the mentioned cards should be set to true. (The check box should be checked.) Before you test this, a) Please delete the database. (FlmDeleteDb) b) And reboot the node. (Reboot)

You can check the parameter as mentioned below.

•Card View

•Maintenance Pane

•Loopback Pane

•Port pane on the card for which this is supported. (Mentioned in the bracket)

For 7.04 310MA

•DS1_28_DS3_EC1_3_LINE_CARD (DS3 Port)

•DS1_84_DS3_EC1_3_LINE_CARD (DS3 Port)

15454

•DS3XM_LINE_CARD (DS3)

•DS3XM12_LINE_CARD (DS3)

•DS3I_LINE_CARD (DS3I)

•DS3E_LINE_CARD (DS3)

•DS3_EC1_48_LINE_CARD (DS3 & EC1 Port)

DS1_E1_56_LINE_CARD (You can see these values on loopback pane itself)

CSCsi04127

When you upgrade nodes from R6.22 to R7.0.4, BITS-1 IN, BITS-2 IN, BITS-1 OUT, and BITS-2 OUT go into In-Service (IS), although the R6.2.2 line-timed nodes have all the BITS facilities set to Out-of-service (OOS), before the upgrade. This issue is resolved in Release 7.05 and 7.23.

CSCsi46648

The port labeling on the 15310 DS1 circuit is inconsistent with the DS1 labeling on the 15454 DS1 circuit.

In case of DS1 circutis created using DS1_84_DS3_EC1_3_LINE_CARD and DS1_28_DS3_EC1_3_LINE_CARD in 15310 MA the DS1 port information is displayed differently in the circuit table.

Workaround: The DS1 port information can be derived using the port and vt information displayed.

pDS1(1-28)/S1/V1-1 => port 1 (1-1 is the first port in the 1-28 range)

Common Control Cards

CSCsi97098

Standby TCC resets after connecting to the database through FTP. Standby TCC resets and somtimes a DBOSYNC alarm is raised for 30 seconds after it comes up.

This condition happens when the FTP connection between the active and standby TCC faces an interruption and the standby TCC decides to reset itself.

This issue is resolved by allowing the standby TCC to reinitialize its FTP connection to the active TCC before rebooting. This issue is resolved in release 7.0.7.

Alarms

CSCsi23824

The Signal Fail-Path (SF-P) and Signal Degrade-Path (SD) alarms are not reported on the following cards.

•OC192XFP: 15454-10G-RX, 15454E-10G-RX, 15454-10G-S1, 15454E-10G-I1

•MRC-12: 15454-MRC-I-12, 15454E-MRC-I-12

•MRC25G-12: 15454E-MRC-2.5G12

•MRC25G-4: 15454-MRC-2.5G4

•ADM-10G: 15454-ADM-10G

•RAN-SVC - 15454-RAN-SVC, 15454E-RAN-SVC

In case Path Protection circuits are created on the affected cards, these circuits may not switch if the SF-P and SD-P conditions exist on the path.

This isuue is resolved in release 7.0.7.

Electrical IO Cards

CSCsd59042

When upgrading the software from Release 6.x.x to Release 7.x.x, the DS3 and EC1-12 cards fail to load if the node name begins with the letters FL. Changing the node name resolves this issue.

TL1

CSCsg22884

This bug is about retrieval of Far end Performance Monitoring values through TL1 on the 15310MA on the cards DS1-28-DS3-EC1-3 and DS1-84-DS3-EC1-84. Now these are retrievable through TL1.

Path Protection

CSCsh77496

If path protection/SNCP circuits are created while path defects are present on path protection/SNCP trunks, then sometimes path protection/SNCP circuits may not switch and traffic outage is observed

Workaround: Avoid creating path protection circuits while faults are present on either of thepath protection trunks ports. This issue is resolved in 6.03, 7.05 and 7.2.3

Electrical IO Cards

CSCsg23089

SF LED is ON even when all the DS3 or DS1 ports are in IS_AINS state. Expected behavior is, SF LED should be on only in IS state and if any of IS port has any alarms on it. In all other states it should be OFF. It is made consistent with expected behavior.

CSCsi56959

DS3 unidirectional traffic goes down when reverting from 8.x, 7.05 or higher versions.

The issue can be reproduced as follows :

Step 1 A unidirectional STS circuit is connected between any two DS3 port in 15310MA with WBE cards running 7.04 version.

Step 2 The traffic is up.

Step 3 An upgrade is made to 7.05 or 8.x versions and then downgraded to 7.04 version.

Workaround 1:

•Once the downgrade to 7.04 is done, hard reset the WBE card in 310MA that has the source port of the unidirectional circuit. This brings back the traffic.

Workaround 2:

1. Delete unidirectional circuit after the downgrade is done.

2. Create and delete a bidirectional circuit on the same source and destination, once.

3. Create the unidirectional circuit on the same port.

This brings back the traffic.

Note This issue is valid only if we see the signal coming out of the destination port of the unidirectional circuit having DS3-AIS. For any other DS3 failures, this issue may not be the valid root cause.

New Features and Functionality

The following feature has been added to the ONS 15310-MA for Release 7.0.2.

Daylight Savings Time Support

With Release 7.0.2 CTC and TL1 display daylight savings time (DST) in keeping with the new DST rules applicable from 2007 forward. As described in the change in energy policy for the United States of America (USA), the DST start date will be the 2nd Sunday of March and the DST end date will be 1st Sunday of November.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

Subscribe to the What's New in Cisco Product Documentationas a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.