Release Notes for Cisco ONS 15310-MA Release 7.2.2
Available Languages
Table Of Contents
Release Notes for Cisco ONS 15310-MA
Release 7.22Changes to New Features and Functionality
Maintenance and Administration
CSCse85355 CSCsd52665 CSCsd56328
Resolved Caveats for Release 7.2.x
Maintenance and Administration
New Features and Functionality
IP Addressing with Secure Mode Enabled
Network Circuit Automatic Routing Overridable NE Default
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco ONS 15310-MA
Release 7.22
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.
August 2007
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, and the Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, and Release 7.2 of the Cisco ONS SONET TL1 Command Guide. For the most current version of the Release Notes for Cisco ONS 15310-MA Release 7.22, visit the following URL:
http://www.cisco.com/en/US/products/hw/optical/ps2001/prod_release_notes_list.html
Cisco also provides Bug Toolkit, a web resource for tracking defects. To access Bug Toolkit, visit the following URL:
http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs
Contents
Resolved Caveats for Release 7.2.x
New Features and Functionality
Obtaining Documentation and Submitting a Service Request
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.2 since the production of the Cisco ONS 15310-MA System Software CD for Release 7.22.The following changes have been added to the release notes for Release 7.2.2.
Changes to New Features and Functionality
The following new feature's summary has been revised to better explain secure mode locking behavior:
IP Addressing with Secure Mode Enabled
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
CSCse36337
When a Server Trail is created on a 1+1 Protection Group, the Node's database gets deleted, and the Node goes for continuous reboot. No workaround available. This issue will be resolved in Release 7.22, 8.0.
CSCse89357
CTC Network view shows up without any Nodes. The initialization of the network view sometimes would get interrupted with exceptions. Workaround is to relaunch CTC. This issue will be resolved in a future release.
CSCse96077
On an IO port with this issue false TCAs that indicate line or traffic problems are raised every 15 min after the 15 min pm report. There are no alarms with the associated ports. Traffic is not affected. In Release 7.2, during a very short period when the defect is present (less than 1 sec), false TCAs might be raised. This can be reproduced by either removing or then reinserting the card, or by a small burst of defects.
The cards affected are:
•
•
There are two workarounds:
•
•
This issue will be resolved in a future release.
CSCsh37934
Unable to create 1+1 Optimized APS (also called J-APS) on a line timed port. Can do so using TL1 . This issue will be reoslved in a future release.
CSCsh37934
Unable to create 1+1 Optimized APS (also called J-APS) on a line timed port using CTC. Use TL1 to create the 1+1 Optimized APS. This will be resolved in a future release
CSCsd84638
Sometimes IP connectivity to an ONS 15310-MA is lost and pinging the node fails. Also, as a result, CTC fails to come up. This can occur if both the Ethernet port on the CTXMA card and the Ethernet port on the backplane are accidentally connected to the same network, resulting in loops in the switching network. In normal operation the backport should be used to connect to the network and the frontport should only be used for onsite maintenance. If this issue occurs detach the Ethernet cables from both the frontport and the backport and connect via the backport (or frontport) only, rather than via both at the same time. This issue will not be resolved.
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
CSCsh48090
When there is a mismatch in the Trace Identifier String configured and what is received, TIM-S is raised as expected on 310MA WBE-84 card. Now if we pull the cable , Loss Of Signal (LOS) alarm is raised, however TIM-S is not suppressed. LOS alarm should supress TIM-S as LOS alarm has higher priority. This will be resolved in a future release.
CSCsh48107
After an upgrade from 7.0 to 7.22 in a Revertive Protection Group set up with two connected nodes and with circuits between them, when issued protection switch from working to protect and back, WKSWPR alarm was not raised. This issue will be resolved in a future release.
CSCse85355 CSCsd52665 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.
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 not be resolved.
CSCsb62127
A DCC Link discovered by CTC, can show incorrect bandwidth. When a DCC tunnel is created using two different OC cards, like OC12 and OC48 at its ends, CTC Network view shows incorrect bandwidth. Such a provisioning is a provisioning mistake. No workaround available. This issue will be resolved in a future release.
Electrical IO Cards
CSCsh20228
1-Day TCA is not generated for DS1-84. Provision TOD 23:59:59 from TL1 with DST as 0. We have DS3 line errors (LOS). After date is changed after one second of time change, the 1-Day bucket must be restarted. The TCAs must be generated for 1-Day, which is not happening. This issue will be fixed in a future release.
Alarms
CSCsh37976
APSCM(Protection Switching Channel Match Failure) is NOT raised for 1+1 Optimized Protection. The configuration is as below
•
•
•
•
•
•
This issue is expected to be resolved in a future release.
TL1
Note
Resolved Caveats for Release 7.2.x
The following items are resolved in Release 7.2.x
Maintenance and Administration
CSCsg52340
Automatic Routing of circuits using CTC 7.2 or higher, on nodes older than 7.2 is not possible. A new NE Default introduced in 7.2, causes this problem. Workaround is to toggle the CIRCUITS_AUTO_ROUTE_DEFAULT_OVERRIDABLE NE Default. This issue is resolved in Release 7.22, 8.0.
CSCse92125
Attempt to log-in using CTC. CTC login fails. Workaround is to ensure that the PC is not running a Turkish locale. This issue is fixed in Release 8.0.
CSCse99104
CTC can incur either repeated failures when you attempt to log in to an NE, and/or a very long time to discover all ENEs behind a GNE (could be over 30 minutes on a medium sized network). This issue affects all ONS 15xxx releases from R4.1 to 7.2. This condition is more likely to happen on Windows XP after an upgrade to Service Pack 2, and when the network is made of a medium to large number of GNEs/ENEs with SOCKS enabled. This condition can also happen in the case of networks with poor connectivity between CTC and the GNEs.
The solution involves an enhancement to the SOCKS discovery protocol by introducing the concept of designated SOCKS servers. A designated SOCKS server is a NE that runs SOCKS, is LAN connected and has been explicitly marked as a potential SOCKS server by the user. CTC allows the user to enter an unlimited number of designated SOCKS servers. When designated SOCKS servers are defined, the automatic SOCKS server discovery protocol is disabled, resulting in substantial performance improvement during CTC login and ENE discovery.
CSCse53017
Circuit creation when attempted on ML cards between a 7.2 NE and an older NE, the wizard would die. The source should be on 7.2 NE and destination on the older NE. Workaround is to interchange the source and destination. This issue is resolved in Release 7.22, 8.0.
CSCse53017
Circuit creation when attempted on ML cards between a 7.2 NE and an older NE, the wizard would die. The source should be on 7.2 NE and destination on the older NE. Workaround is to interchange the source and destination. This issue is resolved in Release 7.22, 8.0.
Common Control Cards
CSCse01108
When the NE time is changed from CTC (or TL1), the pm bins of the interfaces (OCn/Ds1 on ctx-cl and OCn on 310-MA), which are on the active tcc, does n't get marked as partial. No workaround available. This issue is resolved in Release 7.22 and 8.0.
CSCse98996
The issue can be reproduced as follow:
Step 1
with Node Time Zone
Step 2
Step 3
Step 4
Step 5
Electrical Cards
CSCsg23128
All DS3 Ports Automatically Transition to IS State After Card Upgrade. Have a WBE28 card in one of the IO slots (1/2/5/6) of 310MA. Provision admin state of DS3 ports to IS-AINS. Upgrade this card to WBE84 using change card option of CTC window. We see MEA alarm raised. At this time, when we plug-out WBE28 and plug-in WBE84 card, we see WBE84 card comes up and all DS3 ports transition from IS-AINS to IS autonomously. After this, the user can't set the admin state of these ports to IS-AINS as these ports autonomously transition from AINS to IS within few seconds after provisioning. No workaround available. This issue is resolved in Releases 7.22, 7.04 and 8.0.
Alarms
CSCse98987
AIS-P and RFI-P are seen on the same STS if the path terminating equipment is a DS3 card. This happens when you configure a bi-directional circuit using a DS3 card as the path terminating equipment. Inject AIS-P into the circuit. AIS-P and RFI-P are seen on the same STS. This is fixed in 7.22
CSCsh24561
When you change the alarm profile of BITS:SSM-STU from default value which is NA/NSA to CR/MN. The alarm severity changes to CR. BITS-SSM-STU reports a critical alarm eventhough it si NSA. Single node provisioned in external timing mode with BITS 1 as the primary reference. Connect a testset to BITS-In 1 and feed a DS1 signal with SSM-STU as the Dsn loopcode. BITS reports SSM-STU traceable and the node synchronizes to STU with default NA/NSA severity. Now From the CTC change the alarm profile such that BITS:SSM-STU is set to CR/MN. The alarm severity changes to CR. BITS-SSM-STU reports a critical alarm. This issue will be fixed in Release 8.01.
CSCsf09471
SFP's with a serial number starting with ECL cause the 15310-MA to raise an MEA alarm when using R7.0 or R7.2 sw. This has been seen on Release 7.0 and 7.2. Workaround is to use SFP's with SN#'s that do not start with ECL or upgrade to 7.2.2.
TL1
CSCsg22884
When the RTRV-T1::<aid>:<ctag>:1::<montype>,,fend; command is issued on a T1 facility on 15310MA DS1-28/84-DS3-EC1-3, the Far End performance monitoring counts are not available on DS1-28/84-DS3-EC1-3 cards through TL1 . However the far end performance monitoring counts can be viewed on the CTC. This issue is fixed in 7.04 and 7.22 and 8.0.
New Features and Functionality
This section highlights new features and functionality for Release 7.2. For complete documentation of each of the features of the ONS 15310-MA, consult the user documentation.
New Software Features
The following sections describe new software features for Release 7.2.
IP Addressing with Secure Mode Enabled
This section addresses Release 7.2 secure mode. It also describes how this mode's locked or unlocked options operate in various scenarios with R7.2, or R7.2 in combination with R7.0.
Secure Mode
In Release 7.2, you can separate LAN interface access from backplane Ethernet port access by use of the secure mode. Additionally, you can lock this mode so that a node's configuration cannot be altered.
The CTX2500 card defaults to nonsecure, unlocked mode. (Your network's defaults may differ; refer to the NE Defaults documentation to confirm them.) In nonsecure mode, the LAN and backplane Ethernet ports share a single MAC address and IP address. The CTX2500 card allows you to place a node in secure mode to prevent a LAN port user from accessing the network through the backplane port. Secure mode can also be locked, which prevents the mode from being altered.
Dual IP Addresses
Changing an ONS 15310-MA node from nonsecure mode to secure mode allows you to provision two Ethernet addresses for the node and causes the active CTX2500 to assign the ports different MAC addresses. In secure mode, one IP address is provisioned for the ONS 15310-MA backplane Ethernet port and the other is provisioned for the CTX2500 LAN port. Both addresses reside on different subnets and packets are not exchanged between these two ports. The dual addresses provide an additional layer of separation between the LAN access port and the ONS 15310-MA network. If secure mode is enabled, the IP addresses provisioned for both ports must follow general IP addressing guidelines and must reside on different subnets from each other and the default router IP address.
In secure mode, the LAN port IP address becomes a private address while the backplane port connects the node to an Operations Support System (OSS) through a central office or private enterprise network. A superuser can configure the node to hide or reveal the backplane's Ethernet IP address in CTC, the routing table, or autonomous message reports.
Secure Mode Locking
A superuser can convert a secure node from unlocked to locked mode. Doing so permanently changes the chassis hardware. The procedure for placing a node in secure mode or secure locked mode is similar to the process for an ONS 15454 node. Refer to the "Manage the Node" chapter in the Cisco ONS 15454 Procedure Guide for instructions.
When a node is secure and locked, its configuration, Ethernet port status, its secure mode, and the locked status cannot be changed by any network user— including a superuser. To have a secure node's lock removed, contact Cisco Technical Support to arrange a Return Material Authorization (RMA) for the chassis and the CTX2500 card(s). Refer to the Obtaining Technical Assistance section of the Cisco ONS 15310- CL and ONS 15310-MA Procedure Guide as needed.
When a node is secure and locked, its configuration, Ethernet port status, its secure mode, and the locked status cannot be changed by any network user— including a superuser. To have a secure node's lock removed, contact Cisco Technical Support to arrange a Return Material Authorization (RMA) for the chassis and the CTX2500 card(s). Refer to the Obtaining Technical Assistance section of the Cisco ONS 15310- CL and ONS 15310-MA Procedure Guide as needed.
Note
Mixed Release Shelf Scenarios
When an active CTX2500 card is converted to locked mode, the standby CTX2500 card and chassis are also changed. The components retain their locked status even if separated.
Caution
Note
Note
Following are some example scenarios using locked or unlocked Release 7.2 and Release 7.0 components:
•
•
•
•
•
Node Role Flexibility
In nonsecure mode, a node can be a GNE or ENE. Placing the node into secure mode automatically turns on SOCKS proxy and defaults the node to GNE status. However, the node can be changed back to an ENE. In nonsecure mode, an ENE's SOCKS proxy can be disabled—effectively isolating the node beyond the LAN firewall—but it cannot be disabled in secure mode.To change a node's GNE or ENE status and disable the SOCKS proxy, refer to the "Turn Up a Node" chapter in the Cisco ONS 15310-CL and ONS 15310-MA Procedure Guide.
Note
Network Circuit Automatic Routing Overridable NE Default
The Network Circuit Automatic Routing Overridable NE default makes it possible to set by default whether or not a user creating circuits can change (override) the automatic circuit routing setting (also provisionable as a default).
The new NE default supporting this feature is:
CTC.circuits.RouteAutomaticallyDefaultOverridable
This default works in combination with the existing circuit routing default:
CTC.circuits.RouteAutomatically
The overridable option enables network administrators to manage how circuits are created on a network-wide basis. For example, if the Automatic Circuit Routing default is set to FALSE (the check box is unchecked by default), then setting the Network Circuit Automatic Routing Overridable default to FALSE ensures that manual circuit routing is enforced for all users creating circuits (the default is not overridable by the user). When the Network Circuit Automatic Routing Overridable default is set to TRUE (the factory configured setting) users can click in the Automatic Routing check box to change the automatic routing setting if they wish.
When the Route Automatically check box is not selectable during circuit creation, the following automatic routing sub-options will also be unavailable:
•
•
Like the Automatic Circuit Routing default, the Network Circuit Automatic Routing Overridable default applies to all nodes in the network. The Route Automatically check box is either overridable or not depending on how the default is set for the node you are logged into through CTC. To ensure correct behavior after setting the default, propagate the chosen default setting to all nodes through which users might log into the network to perform provisioning. For more information on NE defaults and their provisioning consult the user documentation.
Related Documentation
Release-Specific Documents
•
•
•
•
•
•
Platform-Specific Documents
•
Provides installation, turn up, test, and maintenance procedures•
Provides technical reference information for cards, nodes, and networks•
Provides a list of SONET alarms and troubleshooting procedures, general troubleshooting information, transient conditions, and error messages•
Provides a comprehensive list of TL1 commands•
Provides general information, procedures, and errors for TL1•
Provides software feature and operation information for Ethernet cardsObtaining 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:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as 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.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
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.
© 2007 Cisco Systems, Inc. All rights reserved.
FeedbackLet Us Help
- Open a Support Case
- (Requires a Cisco Service Contract)