Release Notes for Cisco ONS 15454 Release 4.6
Available Languages
Table Of Contents
Release Notes for Cisco ONS 15454
Release 4.6DDTS # CSCdy48478 Fan Tray Assembly Fan Fail Lamp Test Failure
SONET and SDH Card Compatibility
Active Cross Connect (XC/XC10G/XCVT) or TCC2 Card Removal
DDTS # CSCeb26662 and CSCea88023
DDTS # CSCds02031 E1000-2/E100
Maintenance and Administration
ONS 15454 Conducted Emissions Kit
DDTS # CSCdv10824: Netscape Plugins Directory
DDTS # CSCds13769: Fujitsu FLM-150 and Nortel OC-3 Express
DDTS # CSCec75064 and CSCec75019
Active Cross Connect (XC/XC10G/XCVT) or TCC2 Card Removal
Resolved Software Caveats for Release 4.6
Maintenance and Administration
DDTS # CSCeb24331 and CSCeb40119
New Features and Functionality
10-Gbps Multirate Transponder Card
New Software Features and Functionality
DWDM and TDM Hybrid Node Support
FC_MR-4 Fiber Channel Card Support
New Default Superuser Password
DCC Capacity, Management, and Tunneling
Go-and-Return Path Protection Routing
Configurable Superuser Clear PM
K2 Bits Alarm Notification on 1+1 APS
Alarming on Duplicate Node IDs
Rear Panel Ethernet Connection Detach Alarm
Port Status via Front Panel LCD
DS3i-N-12 Card Support for SONET Platforms
Obtaining Technical Assistance
Contacting TAC by Using the Cisco TAC Website
Release Notes for Cisco ONS 15454
Release 4.6
August, 2007
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 4.6" version of the Cisco ONS 15454 Procedure Guide; Cisco ONS 15454 Reference Manual; Cisco ONS 15454 Troubleshooting Guide; and Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide. For the most current version of the Release Notes for Cisco ONS 15454 Release 4.6, 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/cgi-bin/Support/Bugtool/launch_bugtool.pl
Contents
Resolved Software Caveats for Release 4.6
New Features and Functionality
Obtaining Technical Assistance
Changes to the Release Notes
This section documents supplemental changes that have been added to the Release Notes for Cisco ONS 15454 Release 4.6 since the production of the Cisco ONS 15454 System Software CD for Release 4.6.
The following changes have been added to the release notes for Release 4.6.
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 DDTS tracking numbers are known system limitations that are scheduled to be addressed in a subsequent release. Caveats without DDTS tracking numbers are provided to point out procedural or situational considerations when deploying the product.
Hardware
DDTS # CSCec73848
When you modify VOA attenuation calibration, an optical power transient can occur. This issue will be resolved in a future release.
DDTS # CSCdy48478 Fan Tray Assembly Fan Fail Lamp Test Failure
A user-initiated lamp test does not illuminate the fan fail LED on the fan tray assembly for the ONS 15454 or the ONS 15454 SDH. The lamp test successfully lights the LEDs for major, minor, and critical alarms on the fan tray, and for all cards in the chassis, but does not light the fan fail LED. An actual fan failure, however, will light the fan fail LED.
DDTS # CSCdw57215
In a configuration with OC-48 Any Slot cards and an STS-24c circuit, provisioned between G1000-4 cards with traffic going over the OC-48 span, extracting the G1000-4 card at one end of the STS-24c circuit before deleting the circuit will result in a traffic hit on all existing SONET circuits defined over that same span. This only occurs when the STS-24c is provisioned on timeslot 25.
In the Cisco ONS 15454 Procedure Guide, Release 4.1.x, refer to the "NTP-77 Delete Circuits" procedure to delete the 24c circuit before removing the card. Once you have deleted the circuit, refer to the "DLP-191 Delete a Card from CTC" task (also in the procedure guide) to delete the G1000-4 card. This issue will be resolved in Release 5.0.
Upgrades
DDTS # CSCec82344
CTC SendPDIP alerts might be raised on upgrades if any of the nodes in your network have the flag for SendPDIP set to "false" in their associated NE Defaults. This is because the upgraded node will have the value set to "true," which is the default setting. You do not need to clear these alerts. They will clear when the upgrade is finished.
Line Cards
Note
DDTS # CSCed36598
When DHCP forwarding is turned on, and the forwarding to address is set to a cellbus address instead of a DHCP server address, you can lose connection to your nodes. Always set the forwarding address to a DHCP server. This issue will be resolved in a future release.
DDTS # CSCed24599
While the DS3E protect card is active, invoking the auto frame format provisioning feature (AUTL) for a port might result in a misprovisioned frame format on that port (as compared to the actual frame format received on the DS3 receive line). If you must provision the frame format for a port while the protect card is active, provision it explicitly (manually select UNFRAMED, M13 or CBIT) instead of using the AUTL feature to ensure appropriate frame format provisioning on that port. This issue will be resolved in a future release.
DDTS # CSCec09783
Rarely, loss of traffic on an EC1 card can occur if you pull the card and quickly reinsert it. To avoid this issue, wait 5 seconds before reinstalling the card. This issue will be resolved in a future hardware release.
DDTS # CSCec57665
When changing the tunnel type from IP Tunnel to a traditional SDCC tunnel, the rollback does not restore the original tunnel. If this occurs, manually recreate the tunnel. This issue will be resolved in Release 5.0.
DDTS # CSCed01244
With a 1+1 protection group configured on an OC3-8 card, an APSCM alarm might be raised unexpectedly. Any switch on the protection group will clear the alarm. This issue will be resolved in a future release.
DDTS # CSCec79028
UNEQ-P & LOP-P CR alarms might be reported momentarily when PCA traffic is preempted while applying a force switch ring or manual switch ring. The issue is more common when there are PCA circuits on multiple node OC-192 rings. This issue will be resolved in Release 5.0.
DDTS # 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.
DDTS # 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 build 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.
Ethernet Polarity Detection
The TCC2 does not support polarity detection & correction on the LAN Ethernet port. This is a change from prior common control cards, such as the TCC+. If your LAN Ethernet connection has the wrong polarity (due to incorrect wiring on the backplane wire-wrap pins), the connection will work when using a TCC+, but not with a TCC2. To avoid possible problems, ensure that your Ethernet cable has the correct mapping of the backplane wire-wrap pins. For Ethernet pin mappings, consult the "DLP-A 21 Install LAN Wires on the Backplane" procedure in the user documentation.
If you are using a TCC+, the Release 4.0 or 4.1.x software will report the polarity issue (previous releases do not), by raising the standing condition: LAN Connection Polarity Reverse Detected (COND-LAN-POL-REV). Also, notification will appear on the fan tray LCD, which will display "BP LAN POL. NEG." The issue will typically be reported during the software upgrade process, but can also be raised during a new installation when using TCC+ and Release 4.0 or 4.1.x.
If this is a new installation with a TCC2 and you have the Ethernet polarity reversed, the TCC2 will not communicate over the LAN Ethernet interface (no polarity correction will occur), and no condition will be reported, nor will the fan tray LCD indicate an issue.
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.
DDTS # 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.
DDTS # 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.
DDTS # 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.
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. DDTS numbers related to this issue include CSCdv50357, CSCdv63567, CSCdv68418, CSCdv68441, CSCdv68389, CSCdv59621, and CSCdv73402.
Active Cross Connect (XC/XC10G/XCVT) or TCC2 Card Removal
You must perform a lockout in BLSR, path protection, and 1+1 before physically removing an active cross connect (XC/XC10G/XCVT) or TCC2 card. The following rules apply.
Active cross connect (XC/XC10G/XCVT) cards should not generally be physically removed. If the active cross connect or TCC2 card must be removed, you can first perform an XC/XCVT/XC10G side switch or TCC2 reset and then remove the card once it is in standby, or you can perform a lockout on all circuits that originate from the node whose active cross connect or active TCC2 will be removed (performing a lockout on all spans will also accomplish the same goal). No lockout is necessary for switches initiated through CTC or through TL1.
DDTS # CSCdv62565, CSCdv62573
In a 1:N protection group, traffic loss could occur if a DS-N card is preprovisioned and then added to the group while another working card in the group is removed from its slot. To avoid this, before adding slots to a protection group ensure that:
•
•
This issue will be resolved in Release 6.0.
DWDM Cards
DDTS # CSCec51270
Far end traffic does not switch in line termination mode with .G709 off. This can occur with non-revertive Y-cable, and DCC enabled, under certain specific conditions. To avoid this issue, turn on .G709 when in line mode. This issue will be resolved in a future release.
DDTS # CSCec40684
After a database restore TXPP trunk ports might report SF, resulting in a traffic outage. The SF occurs when you restore the database and then put the port OOS for DWDM cards; then the operating mode in the database is different from the current operating mode. To avoid this issue, either put the DWDM port OOS before restore the database, or, after restoring the database, reset the DWDM cards. This issue will be resolved in Release 5.0.
DDTS # CSCed05006
In the Defaults pane, when you change the default ALS mode for the TXP/TXPP_2.5G_10G cards to "Manual Restart for Test," CTC issues an error message. The mode can be successfully changed but you must click Reset to proceed with further changes to defaults. Changes to other defaults on that pane may have to be reapplied. To prevent the error, change the default pulse width at the same time as changing the default ALS mode to "Manual Restart for Test." The default pulse width must be in the appropriate range for this mode (80-100). This issue will be resolved in a future release.
DDTS # CSCec78443
You cannot provision an end-to-end circuit through a TXP regen group (a pair of transponders connected back to back via the client interface that provide for regeneration for DWDM) with G.709 on, and in line termination on the TXP cards, which are feeding traffic to the regen group. To avoid this issue turn G709 off for all TXPs. This issue will be resolved in Release 5.0.
DDTS # CSCeb25490
Occasionally the system displays a LO-TXPOWER alarm when SMT4 and STM1 SFP is installed at the client port of a TXP or TXPP card. The LO-TXPOWER alarm is displayed when the alarm threshold is set to the default value in the TX POWER LOW field of the Optical Threshold in the CTC provisioning window. To work around this issue, lower the alarm threshold value (TX POWER LOW (dBm)) of Optical Threshold in the CTC provisioning window. Refer to Table XX for threshold values. This issue will be resolved in Release 5.0.
Table 4 contains the High and Low Alarm Thresholds of Tx-power and Rx-power of SFPs in TXP and TXPP cards. The values of these thresholds are read from the EEPROM inside the SFPs. This table can be used as a reference in PM alarm provisioning and Threshold Alarm verification.
Table 4 Alarm Thresholds
10-1421-02
OC48-SR
2.0
-14.6
0
-21.0
10-1422-01
OC48-IR
4.0
-9.6
3.0
-23.2
10-1829-01
OC12-IR
-6.9
-13.1
-6.0
-31.0
10-1828-01
OC3-IR
-6.9
-13.9
-6.0
-31.0
10-1832-01
2FC/2GB-LX
0.9
-13.2
1.0
-24.0
10-1590-01
2FC
1.0
-14.6
N/A2
N/A
10-1750-01
ESCON
N/A
N/A
N/A
N/A
1 The power unit for TxHi/TxLow/RxHi/RxLow used is dBm.
2 N/A means Not Available. The vendor did not provide the information in this field.
DDTS # CSCuk42668
TXP-MR-2.5G F1-UDC may not be passed through in a line-terminated configuration with OTN off. This can occur with clean, OC-3/STM-1, line-terminated traffic, with OTN disabled, when you create a D1-D3 tunnel, a D4-D12 tunnel, and an F1-UDC from client to client. This issue will not be resolved.
DDTS # CSCuk42752
If you go to the Overhead Circuits Tab in network view and select any User Data, F1 or User Data D4-D12 circuit type, no nXP cards are available for selection in the Endpoints. However, user Data type circuits can still be made end-to-end (where "end-to-end" refers to external cards, such as AIC to AIC) if the nXP cards are put in Transparent mode. This issue will not be resolved.
DDTS # CSCeb49422
With TXPP cards, a traffic loss up to six seconds can occur during a DWDM protection switch. This behavior may be exhibited during protection switches by certain third-party fiber channel switches due to loss of buffer credits resulting in a reconvergence of the fiber channel link. This issue will not be resolved.
DDTS # CSCeb53044
The 2G Fiber Channel (FC) payload data type in the TXP_MR_2.5G and TXPP_MR_2.5G cards does not support any 8B/10B Payload PM monitoring. This is as designed.
DDTS # CSCea78210
The TXP_MR_2.5G and TXPP_MR_2.5G cards do not support TX Optical power performance monitoring on the trunk port. This is as designed.
DDTS # CSCeb32065
Once engaged, ALR will not restart on the trunk lines of a TXP or TXPP card. This occurs whenever ALR engages on the trunk lines of a TXP or TXPP card and the recover pulse width is provisioned to less than 40 seconds. This is a function of the trunk laser turn-on time, and the limiting recovery pulse width will vary by card. To avoid this issue, provision the pulse width to 40 seconds or more.
DDTS # CSCeb26662 and CSCea88023
With TXP-MR-2.5G cards, when the current 1 day Optics PM rolls over, the information is inaccurate for "avgs." This issue will not be resolved.
DDTS # CSCuk42588
With ALS mode configured as "Auto Restart" or "Manual Restart," it is possible the ALS Pulse Duration Recovery time can be set to values out of ITU-T recommendation G.664. You can use values out of the range defined in ITU-T recommendation G.664 only in order to interoperate with equipment that lasers cannot turn on or off within the required pulse time. To stay within the specification, you can set this value to 2 seconds and up to 2.25 seconds.
DDTS # CSCea81219
On the TXPP, the default value for Tx Power High for TCAs & Alarms is too high for the trunk ports. Since Tx Power TCA and Alarm are not supported for trunk ports, this caveat is for informational purposes only.
DDTS # CSCeb27187
During a Y-Cable protection switch, the client interface sends 200,000 to 300,000 8B/10B errors towards the attached Catalyst 3550 switch. The switch reacts to this large amount of 8B/10B errors by reinitializing the interface and spanning tree. The end result is that a protection switch can lead to a 30-45 second traffic hit if the switch is running spanning tree (default mode). This is expected behavior.
DDTS # CSCea87290
In a Y-Cable protection group, if GCCs are defined on both cards, both cards' active LEDs will be green.
DDTS # CSCeb12609
For the TXPP, attenuating Port 2 Rx signal, SD, and SF alarms are not declared before LOC is raised. This is due to the intrinsic design of the optical interface, which allows required BER performances with dispersion and OSNR penalties.
This can occur when Port 2 is in back to back or has low dispersions and high OSNR.
DDTS # CSCea68773
The ACTV/STBY LED shows AMBER when a 2.5G transponder is first connected. The DWDM cards introduced a new design: When all the ports are OOS on a card, the card is considered to be in standby mode.
E Series and G Series Cards
DDTS # CSCdy37198
On Cisco ONS 15454s equipped with XC or 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 be resolved in a future release.
DDTS # 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 following control protocols 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.
DDTS # CSCds02031 E1000-2/E100
Whenever 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. To avoid a failed STS-1 circuit, delete the second STS-3c prior to creating any STS-1 circuit.
ML Series Cards
DDTS # 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.
DDTS # 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.
DDTS # 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 be resolved in a future release.
DDTS # CSCed06286
If you create several bridgegroups before provisioning POS circuits, POS stays in the BLK state. If this issue occurs, perform a shut/no shut on POS interface that is stuck in the BLK state. This issue will be resolved in a future release.
DDTS # CSCea46580
SPR input counters do not increment on a BVI with an SPR interface. This issue will not be resolved.
DDTS # 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.
DDTS # 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.
DDTS # 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.
DDTS # 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.
DDTS # CSCea26847
An unexpected card reload can occur when a card is configured to route IP-Multicast traffic and subsequently sends IP-Multicast frames larger than 1649 bytes. To prevent this, avoid routing IP-Multicast frames larger than 1649 bytes. This issue is under investigation.
DDTS # 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 in Release 4.0. This issue will be resolved in a future release.
DDTS # 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.
DDTS # CSCdy47284
ML-100 FastEthernet MTU is not enforced. However, frames larger than 9050 bytes may be discarded and cause Rx and Tx errors.
DDTS # 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.
Maintenance and Administration
Caution
Note
Note
DDTS # CSCed58066
If a workstation running CTC has multiple NIC cards installed, and the primary NIC card is not used to connect to the node, and the node is unable to send IP packets to the IP address of the primary NIC card, or if the workstation running CTC is separated from the node by a router that performs NAT translation of the CTC workstation IP address, CTC repeatedly disconnects and reconnects (every two minutes). In either of these cases, CTC registers for alarms and provisioning updates using the IP address of the primary NIC, which the node cannot contact. When the node attempts to contact CTC, the connection fails. This causes the node to remove CTC from its list of registered clients. When CTC subsequently polls the node, CTC determines that it is not registered. CTC resets itself to ensure that it has current alarms and provisioning from the node, causing the disconnect and reconnect.
To avoid this issue, enable the proxy server on all LAN connected nodes with the Proxy-only configuration. This issue is resolved in Release 4.6.1.
DDTS # CSCed60557
Connecting two nodes with the same IP address to the same LAN will result in a broadcast storm. If this occurs, disconnect one of the nodes with the duplicate IP address. This issue is resolved in Release 4.6.1.
DDTS # CSCed07126
If you provision a non-existent static route to a node's subnet and then delete it, the node will lose connectivity. If this occurs, remove and replace the Ethernet cable. This issue will be resolved in Release 5.0.
DDTS # CSCec17281
When the "Status" field for a circuit in the circuit table shows "INCOMPLETE," this can be interpreted as an alarm or traffic-affecting condition on the circuit. On path protection and BLSR circuits, a circuit is shown as INCOMPLETE if either the working or protect path is missing a network span or connection, even if traffic is flowing without error on the other, redundant path. This can lead to confusion, since the meaning of "INCOMPLETE" is not well-defined. You can see this if you, for example, introduce LOS on a span in a BLSR network such that traffic is switched to another path around the ring. Ignore the INCOMPLETE circuit status in such cases and instead look for any alarms in the network. The circuit Status will be defined more clearly in Release 5.0.
DDTS # 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.
DDTS # CSCec61769
The time zone shows the incorrect zone when changed via TL1. This issue will correct itself once a TCC2 reset occurs. This issue will be resolved in an future release.
DDTS # CSCec67324
The Generation II SSM value is not sent out correctly when changed from Gen 1 to Gen 2. Perform a TCC2 switch to correct this issue. This issue will be resolved in a future release.
DDTS # CSCec29230
The NE PWR-B alarm is not reported in CTC after an upgrade to Release 3.4.2. You can view the alarm through TL1. This issue will be resolved in a future release.
DDTS # CSCea78364
Simultaneous failure of working and protect cards in 1:N protection groups may not be alarmed as service affecting. This can occur when the working card of the protection group has been removed from the chassis, and the protect card of the protection group is subsequently issued a Manual Reset. Since the working and protect facilities are impaired, the Improper removal alarm should clear and be reissued as a Critical and service affecting condition. This issue will be resolved in Release 6.0.
DDTS # CSCea81001
When a fault condition exists against a circuit or port that is in the OOS-MT or OOS-AINS state (or when you are using the "Suppress Alarms" check box on the CTC Alarm Behavior pane), the alarm condition is not assigned a reference number. If you were to place the circuit or port in service at this time, in the absence of the reference number, the CTC alarm pane would display the condition with a time stamp indicating an alleged, but incorrect, time that the autonomous notification was issued. Clicking the CTC alarm "Synchronize" button at this stage will correct the alarm time stamp. There is no way to remedy the lack of reference number. This issue will be resolved in Release 6.0.
DDTS # 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.
DDTS # CSCdy57891
An LOP-P alarm can be inadvertently cleared by an LOS that is raised and cleared. On OC48AS, OC192, and OC12-4 cards, when an LOP condition and an LOS condition are both present on the input, an LOS will be raised as per Telcordia GR 253 alarm hierarchy. However, upon clearing the LOS with the LOP still present, the LOP alarm, which should then be raised, is not. An AIS-P condition will be visible. This issue will be resolved in Release 6.0.
DDTS # 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:
•
•
•
•
•
DDTS # CSCdy61275
Far end path FC-P is not counted on EC1 or OC3 cards. When a path defect is transmitted to the far end, it reports RDI-P. However, the condition is not examined and reported as a PM count. This issue will be resolved in a Release 6.0.
DDTS # 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. This issue will not be resolved.
DDTS # CSCdy55556
In a 1:N protection group, where a protect card is protecting a failed card and another working card, which is missing, has a lockon condition, upon removing the lockon condition from the missing working card, the protect card may switch from the card it had been protecting to carry the traffic of the missing working card that just had the lockon removed. To avoid this issue, replace the failed working card before removing the lockon. This issue will be resolved in Release 6.0.
DDTS # 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.
NE Defaults
The following caveats apply for NE defaults.
•
•
•
DDTS # 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.
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.
DDTS # 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.
DDTS # 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.
"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.
Alarms
DDTS # CSCed37519
In Releases 4.1.x all alarms and conditions for G1K-4 are reported under Equipment Type = G1000. The equipment type should be G1K-4. This issue will be resolved in a future release.
DDTS # CSCuk47488
A soft reset of the active TCC2 causes a TCC2 switch. In rare cases, subsequently, all BTC based cards XC. This issue will be resolved in a future release.
SNMP
DDTS # CSCeb34423
All 8B10B TCA events show a negative value for the Current Value field. When 8B10B errors cross their threshold, a TCA event is raised. Included in the TCA event is the current value. If either the current value or the threshold exceeds a 32 bit number in a given period (15 MIN or 1 DAY), it will be shown as a negative value. This issue will be resolved in a future release.
DDTS # CSCed05502
SNMP Traps are generated for TCA when the OC3-4 port state is OOS-AINS/MT (whereas TL1 TCAs are inhibited). This issue will be resolved in a future release.
DDTS # CSCed05742
Issuing an SNMP get on UASL does not result in the same output as for TL1 and HTTP when you query a node with PM data for UASL. This issue will be resolved in a future release.
Interoperability
DDTS # CSCds13769: Fujitsu FLM-150 and Nortel OC-3 Express
You cannot provision the FLM-150 and OC-3 Express in 1+1 revertive switching mode. The problem occurs when the ONS 15454 issues a user request in revertive mode to the protect channel. When the user request is cleared, the ONS 15454 issues a No Request. However, the FLM-150 and OC-3 Express issues a Do Not Revert, which causes traffic to remain on the protection channel. Based on GR-253, section 5.3.5.5, the FLM-150 and the OC-3 Express should respond with a No Request.
BLSR Functionality
DDTS # CSCec77697
With a four-fiber non-revertive BLSR in WTR, a soft reset locks the active XC10G on an adjacent NE, causing traffic loss. To avoid this, issue a lockout on the BLSR prior to the soft reset. This issue will be resolved in a future release.
DDTS # CSCec75064 and CSCec75019
On a four-fiber BLSR after a BLSR switch and soft reset of the XC10G, LOP-P and/or UNEQ-P alarms might become stuck. If this occurs, lock out the span card that report the alarm and soft reboot it. This issue will be resolved in a future release.
DDTS # CSCed10127
Extra traffic is not restored when an SF-R occurs on the same span where a lockout of protect is applied at the opposite node, and where the extra traffic is sourced, destined, or travels through the node with the SF-R. to work around this, issue a lockout of protect on the same side and at the same node where the SF-R occurs. Extra traffic should then be restored. This issue will be resolved in Release 5.0.
DDTS # CSCeb09217
Circuit states are not updated after a span update. If you update a four node OC-12 two-fiber BLSR to a four node OC-192 two-fiber BLSR, the previous PCA circuits should be shown as two-fiber BLSR protected, but they are shown as "UNKNOWN" protected. If you relaunch CTC this situation is corrected. This issue will be resolved in Release 5.0.
DDTS # CSCea59342
DS3 PCA traffic may take up to 20 seconds to recover after a BLSR switch is cleared. This can occur with DS3 PCA traffic on two-Fiber or four-Fiber BLSR configuration with XCVT cards in the same nodes as the DS3 cards. This issue will be resolved in a future release.
DDTS # CSCea81000
In a two-fiber or four-fiber BLSR, MS-RFI is not reported for an LOS or LOF with a ring lockout in place on a different span. This issue will be resolved in Release 6.0.
DDTS # CSCdy45902
Traffic that should be dropped remains unaffected when a BLSR Protection Channel Access (PCA) VT tunnel is placed OOS. You must place all circuits in the tunnel OOS before the traffic will be dropped. This issue will be resolved in Release 6.0.
DDTS # CSCdw58950
You must lock out protection BLSR, 1+1, and path protection traffic to avoid long, or double traffic hits before removing an active XC, XCVT, or XC10G card. You should also make the active cross connect card standby before removing it.
DDTS # CSCdv70175
When configuring a node with one 4 Fiber BLSR and one 2 Fiber BLSR, or with two 2 fiber BLSRs, an issue exists related to the version of XC deployed. Revision 004H and earlier revisions of the XC do not support these configurations. All later revisions of the XC and all versions of the XCVT and XC10G cross connects support all permutations of two BLSRs per node.
DDTS # CSCdv53427
In a two ring, two fiber BLSR configuration (or a two ring BLSR configuration with one two fiber and one four fiber ring) it is possible to provision a circuit that begins on one ring, crosses to a second ring, and returns to the original ring. Such a circuit can have protection vulnerabilities if one of the common nodes is isolated, or if a ring is segmented in such a way that two non-contiguous segments of the circuit on the same ring are each broken.
DDTS # CSCct03919
VT1.5 and VC3/VC12 squelching is not supported in BLSR/MSSPR.
Database Restore on a BLSR
When restoring the database on a BLSR, follow these steps:
Step 1
Step 2
Step 3
Path Protection Functionality
DDTS # CSCeb37707
With a VT path protection circuit, if you inject signals with a thru-mode test set into one path of the circuit in a particular order, you may not see the appropriate alarms. This can occur when you first inject LOP-P, then clear, then inject LOP-V. This issue will be resolved in Release 6.0.
DDTS # CSCdv42151
When a path protection circuit is created end-to-end, CTC might not create the cross-connection on all the nodes along the path at the same time. This might cause an SD-P condition along the path. When the circuit is fully provisioned on all nodes, the SD-P will clear automatically. Other conditions that can be expected while the circuit is being created are LOP-P and UNEQ-P. To reduce the risk of unexpected transient conditions, circuits should be created in the OOS_AINS state.
Active Cross Connect (XC/XC10G/XCVT) or TCC2 Card Removal
As in BLSR and 1+1, you must perform a lockout on path protection before removing an active cross connect or TCC2 card. The following rules apply to path protection.
Active cross connect (XC/XC10G/XCVT) cards should not generally be physically removed. If the active cross connect or TCC2 card must be removed, you can first perform an XC/XCVT/XC10G side switch or TCC2 reset and then remove the card once it is in standby, or you can perform a lockout on all circuits that originate from the node whose active cross connect or active TCC2 will be removed (performing a lockout on all spans will also accomplish the same goal). No lockout is necessary for switches initiated through CTC or through TL1.
Performance Monitoring
DDTS # CSCeb85353
Bulk PM does not show 8b10b PM statistics for the TXPP_MR_2.5G card when Payload Type is set to "1G Ethernet." To see these statistics, go to the CTC card view > Performance > Payload PM tabs. This issue will be resolved in Release 5.0.
DDTS # CSCeb41916
If you create a 1+1 protection group, create a circuit on the working line, and then try to retrieve the path PMs on the protect side using TL1, the request is denied. To work around this issue, use CTC to retrieve the Path PMs on the protect line. This issue will be resolved in Release 5.0.
TL1
Note
DDTS # CSCsh41324
When running release 4.1.4, if a circuit is created within CTC and if that circuit is retrieved via TL1, all looks as expected. However, after the software is upgraded to release 6 and latter, the circuit retrive does not show the same value as was before. For example FAC-4-1 changes to FAC-4-0. Workaround is to delete and recreate the circuit within CTC.
DDTS # CSCed18776
Issuing rtrv-pm-stsn and/or rtrv-th-stsn does not return the Pointer Justification (PJ) counts or thresholds respectively. This issue will be resolved in a future release.
DDTS # CSCed08144
Rarely, TL1 autonomous messages might not be displayed in a session after several days of PM-related provisioning changes. This issue will be resolved in a future release.
DDTS # CSCeb33033
An exception is raised when retrieving PM stats via TL1 for the protect card of a 1:1 protection group when the working card is active. To avoid this issue, retrieve stats from the working card instead of the protect card. This issue will be resolved in a future release.
DDTS # CSCdz26071
The TL1 COPY-RFILE command, used for SW download, database backup, and database restore, currently does not allow a user-selected port parameter to make connections to the host. The command expects the default parameter of Port 21 and will only allow that number. This issue will be resolved in Release 5.0
DDTS # CSCdu53509
When a TL1 session to a remote node (ENE) is established via a gateway node (GNE) and you have changed the node name of the ENE via either TL1, CTC or SNMP, then you must wait for about 30 seconds to issue a TL1 command via the GNE. This delay is to permit the updates to propagate to all nodes in the network. During this transition, neither the old node name nor the new node name can be used in the TL1 session to access the ENE. This 30 second window may be reduced in Release 6.0.
Resolved Software Caveats for Release 4.6
The following items are resolved in Release 4.6
ML Series Cards
DDTS # CSCin35960
POS ingress classification based on IP precedence does not match the packets when inbound policy map classifying based on IP precedence is applied to the POS interface, which is configured for HDLC or PPP encapsulation. To avoid this issue, use LEX encapsulation (default) or, at the Ethernet ingress point, mark the COS based on an IP precedence classification, then classify based on the COS during POS ingress. This issue is resolved in Release 4.6.
DDTS # CSCea20962
No warning is displayed when applying OOS to ML drop ports on the circuit provisioning window. This issue is resolved in Release 4.6.
DDTS # CSCea11742
When a circuit between two ML POS ports is provisioned OOS, one of the ports might erroneously report TPTFAIL. This issue exists for both ML100T-12 and ML1000-2 cards. If this occurs, open a console window to each ML card and configure the POS port to shutdown. This issue is resolved in Release 4.6.
DDTS # CSCdy31775
Packets discarded due to output queue congestion are not included in any discard count. This occurs under either of the following conditions:
•
•
This issue is resolved in Release 4.6.
DDTS # CSCeb24757
Disconnecting a transmit fiber on an ML1000 port causes only the neighboring port to take the link down. Ideally, both ports should identify that the link went down so upper layer protocols can reroute the traffic to a different port. To work around this situation, issue "shutdown" and "no shutdown" to the port that has the disconnected or faulty transmit fiber. This issue is resolved in Release 4.6.
DDTS # CSCeb56287
When an ML-series circuit's state is provisioned from In-Service (IS) to Out-of-Service (OOS), and then back to IS, data traffic does not recover. To avoid this issue, prior to changing the state from IS, set the POS port to shut down on the CLI. After the state is changed back to IS from OOS, set the POS port to "no shutdown." This issue is resolved in Release 4.6.
DWDM Cards
DDTS # CSCeb49210
A soft reset of the working or protect 2.5g multirate card in a Y-cable protection group clears an existing "Lockout of protection" request. It is not known when or if this issue will be resolved. This issue is resolved in Release 4.6.
DDTS # CSCeb39991
SCHED-PMREPT-CLNT does not generate the automatic report for TXPP cards. If you schedule PM reports on a Client or Trunk port of a TXPP, REPT^PM^EVT is never generated. However, the RTRV-PMSCHED-ALL count shows that the count is decreasing. This issue is resolved in Release 4.6.
DDTS # CSCeb49144
The Lamp Test feature does not display all the LED colors available on the 2.5G Transponder. This issue is resolved in Release 4.6.
DDTS # CSCeb37346
Near end and far end PMs might increment simultaneously on TXPP-2.5G cards. This can occur when two nodes have TXPP-2.5G cards and two nodes have STM16 cards in a four node network, where both TXPP-2.5G cards have STM16 SFPs on them, and are in MS (Line Termination) mode. By default, the TXPP-2.5G cards are in Splitter protection: the first DWDM port is working and the second is protect. If you remove the receive fiber of the first DWDM port on one TXPP-2.5G card, both near and far end counts begin to increment. The far end counts should not increment in this case. This issue is seen only when the Txpd cards have G709 and FEC on. If the cards have G709 and FEC off, only the near end counts will increment, as expected. This issue is resolved in Release 4.6.
G Series Cards
DDTS # CSCec03291
A G1-K traffic loss can occur on a software upgrade from Release 4.0, 4.1, or 4.5 to a later software release in an ONS 15454 node with XC or XCVT cards installed. This issue does not occur if the equipment has XC10G cards installed. This issue is resolved in Release 4.6 and maintenance Release 4.1.3
DDTS # CSCec05896
When a G-series card is used in transponder mode the severity of reported alarms is incorrect in some cases. When using transponder mode on G-series cards, if alarm severity is an issue, use the alarm profile editor to set the severity to the desired values. This issue is resolved in Release 4.6 and maintenance Release 4.1.3.
DDTS # CSCeb80771
An Ethernet traffic hit of 500-600 ms may occur when upgrading to Release 4.1 from a prior release. This can occur if active traffic is running on a G1000-4, G1K-4 or G1000-2 card when upgrading the node to Release 4.1. The hit will occur only the first time that you upgrade to Release 4.1. On subsequent downgrades followed by upgrades there will be no traffic hit and the upgrade will be errorless. There is no workaround; however the issue will not occur when upgrading from Release 4.1 to a later release. This issue is resolved in Releases 4.1.3 and 4.6.
Line Cards
DDTS # CSCeb45064
Terminal loopback on DS3XM-6 card may not work properly. AIS-P may be transmitted towards the system (away from the line side) direction. A VT circuit newly created to the DS3XM-6 with no valid input signal to the port can cause this. A terminal loopback will not work because AIS-P is being transmitted towards the system direction. To avoid this issue, apply a valid signal to the input port for the DS3XM card for at least 10 seconds with no terminal or facility loopback applied to that particular port. After receiving a valid signal for this time period, the terminal loopback will function properly even if the input signal is disconnected from the DS3XM port. This issue is resolved in Release 4.6.
DDTS # CSCed05846
In Releases 4.0, 4.0.1, and 4.1 the standby TCC+, TCC2, or XTC card might reset automatically. This can occur at any time, but only rarely. This issue is resolved in Release 4.6, and maintenance releases 4.1.1 and 4.1.3.
Maintenance and Administration
DDTS # CSCdw66895
XCVTs (both active and standby) reboot continuously when the K3 byte is mapped to the E2 byte on one side of a WTR span. The rebooting occurs after the WTR timer expires. This has been seen on a two fiber BLSR with OC-48AS. To avoid this issue, if possible, change the K3 mapping on both ends of the span before creating the ring; or, alternatively, you can prevent the ring from reverting during the K3 mapping by setting the Ring Reversion time to "never." Once you have completed the mapping of the K3 byte to the E2 byte on both sides, return the Ring Reversion to its normal value. This issue is resolved in Release 4.6.
DDTS # CSCdz84149
If a user is logged into CTC as a superuser (or other higher level security type), and then another superuser changes the first user's security level to "retrieve" (or another lower level security type) without first logging the user out, the lower level user is then still able to perform some actions authorized only for the original login security level. For example, a "provisioning" level user demoted to "retrieve" level in this manner can still provision and edit MS-SPRings (BLSRs) while logged into the current session, though the same user may no longer provision DCCs. To ensure that a user's level is changed completely, the superuser must log the user out prior to changing the security level. This issue is resolved in Release 4.6.
DDTS # CSCdz90753
In the Maintenance > Cross Connect Resource Pane, the VT matrix port detail is inconsistent with the general VT matrix data. This can occur when a 1+1 protection scheme is in place. To avoid confusion, note that the VT matrix data counts the VTs for both the working and protect card, while the detail data counts the VTs only for the working card. This issue is resolved in Release 4.6.
DDTS # CSCdz35479
Rarely, CTC Network view can freeze following the deletion or addition of a node from or to a BLSR/MS-SPRing. This can result in the CTC Network view no longer updating correctly. If this occurs, restart CTC. This issue is resolved in Release 4.6.
DDTS # CSCea92969
The switch indicator does not clear on the Maintenance > Protection tabs when a revertive 1:1 protection group is provisioned to be non-revertive. If this occurs, from the Maintenance > Protection tabs, select the slot with the "Switch" indicator. Click the "Clear" button. This issue is resolved in Release 4.6.
DDTS # CSCea93638
Path level alarms are displayed on the CTC conditions pane for deleted circuits. This issue may occur on any circuit deletion case. The conditions may be cleared by a TCC side switch. This issue is resolved in Release 4.6.
DDTS # CSCea61887
Terminal loopback is provisionable even if the card is in transponder mode.
To see this, in the provisioning tab for a G1000 or G1K-4 card pick a pair of ports and set them to transpond with each other. The condition also holds true by picking one port and setting it to transpond with itself (one-port unidirectional). Once the transponder setting is provisioned, go to the Maintenance tab and attempt to provision terminal loopback on any of the ports that were previously provisioned for transponder functionality. CTC allows terminal loopback to be provisioned even though the setting has no effect due to the fact that the ports are performing transponder functions. If terminal loopback is truly intended, you should remove the transponder settings. A warning stating that terminal loopback has no effect if transponders are present is displayed in Release 4.6.
DDTS # CSCea74000
Rarely, a PLM-P alarm on an OC-12 card might remain after deleting the affected STS-1 circuit. This condition persists even after deleting the affected card. If this occurs, you can reset the TCC2s to remove the stuck alarm. This issue is resolved in Release 4.6.
DDTS # CSCea71675
Rarely, when nodes appear gray in CTC and you view the BLSR tab at the network level, the tab may be blank. When this occurs, all tabs on the same level will also become blank. To avoid this issue, do not enter into the BLSR tab at the network view until all of the nodes are some color other than gray. This issue is resolved in Release 4.6.
DDTS # CSCeb24771
A static route may be lost if SOCKS proxy server mode is turned on and then off on the node. If the workstation was communicating with the NE using static routing it will lose connectivity to the NE. If this happens, re-enter the static route. This issue is resolved in Release 4.6.
DDTS # CSCeb20996
While using the orderwire capability of the AIC-I, you must not input a station number with less than 4 digits. If you enter, for example, 123, CTC will display 0123; however, you will not be able to ring the node by dialing either *123, or *0123. This issue is resolved in Release 4.6.
DDTS # CSCeb63327
The High Temperature Alarm is raised at 50 degrees Celsius. This is, however, not optimal on an Itemp rated system, which can tolerate up to 65 degrees Celsius. To work around this issue, the alarm can be downgraded or suppressed, but note that this will result in no temperature alarm provided at all. Alternatively, Cisco TAC provides a method of retrieving the temperature from the node, which can thus be monitored periodically for temperature-related problems. This issue is resolved in Release 4.6.
DDTS # CSCeb45149
A 1+1 non-revertive system in which the protect card is reseated while the working card is present and active reverts back to working after you clear a Force to Protect or Manual to Protect. Affected cards are OC-3 8 port and OC-12 4 port. To work around this issue, soft-reset the working card with the protect card present and active. This issue is resolved in Release 4.6.
DDTS # CSCec48038
A PCA circuit might be displayed as INCOMPLETE after a span upgrade; for example, when a BLSR span that is carrying PCA traffic is upgraded from OC-48 to OC-192. Although the circuit is reported as INCOMPLETE in CTC, traffic should be unaffected in this instance. To correct the display, restart CTC. This issue is resolved in Release 4.6.
DDTS # CSCec58326
When switching to the protect card in EC1 during 1:1 protection, IPPM goes blank. This is the result of incorrect handling of STS Path PMs (IPPM) in EC1 1:1 protection. This issue is resolved in Release 4.6.
DDTS # CSCec84338
With multiple unnamed circuits (circuit name listed as "Unknown") on a node, where at least one is a path protection circuit, a cross-connect from one of these unnamed circuits will incorrectly appear on the Circuit Edit > UPSR Selectors, and Circuit Edit > UPSR Switch Counts tabs of the other unnamed circuits. Also, the State tab will show paths in the wrong column (for example, both source and destination in the CRS End B column).
This issue can manifest anytime you create multiple unnamed circuits (via TL1 or from CTC using the TL1-like option) on a node, where at least one is a path protection circuit. This issue is resolved in Release 4.6 and maintenance Releases 4.1.1 and 4.1.3.
DDTS # CSCeb63327
The High Temperature Alarm is raised at 50 degrees Celsius. This is not appropriate on an Itemp rated system, which can handle up to 65 degrees Celsius. The alarm can be downgraded or suppressed to work around the issue, but then no temperature alarm at all is provided. Cisco TAC is providing a method of retrieving the temperature from the node that enables you to periodically monitor temperature related problems. This issue is resolved in Release 4.6 and in maintenance Release 4.1.3.
DDTS # CSCeb34133
When provisioning a circuit as OOS, path level PM collecting is not disabled. To work around this issue, deselect the IPPM for the path. This issue is resolved in Releases 4.1.3 and 4.6.
DDTS # CSCeb34133
When provisioning a circuit as OOS, path level PM collecting is not disabled. To work around this issue, deselect the IPPM for the path. This issue is resolved in Releases 4.1.3 and 4.6.
DDTS # CSCeb84342
Occasionally, after both power sources are removed and plugged in with one power source (Battery A), the node reboots but does not raise PWR-B alarms. To correct this, remove PWR-B and plug it back. This issue is resolved in Releases 4.6 and 4.1.3.
DDTS # CSCec20521
After addition and deletion of a static route that overlaps with the internal IP addresses range, all cards in the shelf reboot. This can also happen after the node learns a similar route through OSPF or RIP updates. This issue is present in all releases through 4.1 and 4.5. To avoid this issue, do not provision static routes with a destination address in the subnet range 192.168.190.x, and avoid overlap between IP addresses in the network and the internal subnet range 192.168.190.x. If the issue does occur, reset your TCCs. This issue is resolved in Release 4.6 and in maintenance Release 4.1.3.
DDTS # CSCec16812
UNEQ-V alarms are incorrectly raised prior to connecting a TAP to a TACC, and also after disconnecting the TAP from the TACC. This issue is resolved in Releases 4.1.1, 4.1.3, and 4.6.
BLSR Functionality
DDTS # CSCdy56668
Ethernet circuits may appear in the CTC circuit table with an INCOMPLETE status after a BLSR/MSSP span is upgraded. The circuits, when this occurs, are not truly incomplete. They are unaffected and continue to carry traffic. To see the circuit status correctly, restart CTC. This issue is resolved in Release 4.6.
DDTS # CSCdy68207
Failing the working and protect spans on a four-fiber BLSR while an extra traffic circuit runs over the span and a lockout is on the span can cause the extra traffic to permanently fail, with no AIS.
The failure scenario is only reproducible by failing and restoring fibers in the following sequence.
Step 1
Step 2
Step 3
Step 4
If this issue occurs, clear the lockout span. All extra traffic is immediately restored. You may then reissue the lockout span. This issue is resolved in Release 4.6.
DDTS # CSCec74273
If a four-fiber BLSR execute MS-R or WTR coexists with SF-P on the same span and FS-R is issued on a different span in the ring, the FS-R preempts the MS-R or WTR, causing a traffic outage. The ring switch is removed, but one side remains in the ring switch state. To recover from this situation, issue a lockout of the protect span on the span that raised the ring switch event. This issue is resolved in Release 4.6.
DDTS # CSCeb24331 and CSCeb40119
If you create a four-fiber BLSR with a VT circuit on it, then delete the circuit and the ring, then created a two-fiber BLSR on the same ports, you may see an unexpected AIS-V on the path, even before any additional circuit is created. A soft switch of the TCC will clear the AIS-V condition. This issue is resolved in Release 4.6.
DDTS # CSCeb40296
IPPM counts for PCA (extra) traffic will not be displayed in CTC if the BLSR switches back to working after a failure recovery. To see this issue, perform the following steps in a two-fiber or four-fiber BLSR configuration.
Step 1
Enable IPPM on all OCn cards for this PCA circuit.
Step 2
Step 3
Step 4
To recover from this situation, lock out the ring by issuing the LockoutOfProtection (LK-S) command on both east and west for all nodes in the ring. Reboot the OCn card that is not showing PCA path level counts. This procedure needs to be performed whenever there is a switch in BLSR configuration. This issue is resolved in Release 4.6.
DDTS # CSCeb40296
IPPM counts for PCA (extra) traffic will not be displayed in CTC if a BLSR ring-switches back to working after a failure recovery. To work around this issue, lockout the ring by issuing a LockoutOfProtection (LK-S) user command on both east and west on all the nodes in the ring. Reboot the OCn card that is not showing PCA path level counts. This procedure needs to be done whenever there is a switch in BLSR configuration. This issue is resolved in Releases 4.1.3 and 4.6.
Performance Monitoring
DDTS # CSCeb40296
IPPM counts for PCA (extra) traffic will not be displayed in CTC if a BLSR switches back to working after a failure recovery. To avoid this issue, lock out the ring by issuing the LockoutOfProtection (LK-S) user command on both east and west on all nodes in the ring. Reboot the OCn card that is not showing PCA path level counts. This procedure needs to be done whenever there is a switch in BLSR configuration. This issue is resolved in Release 4.6.
DDTS # CSCea38791
In the CTC Performance > Statistics tab of the G1000-4 or G1000-2, there are no entries for Rx/Tx Multicast and Broadcast packets. This issue is resolved in Release 4.6.
TL1
DDTS # CSCdz86121
In one rare case, the ONS 15454/15327 times out a user session without communicating the timeout to TL1. If this happens, the TL1 user remains logged in, although the session is actually timed out. This can occur when you log into the node with a timeout of X minutes. If the user session sits idle for all but 5 seconds of the X minutes, then you have only 5 seconds to type in a command to notify the node that the session is active. If you try this, you will likely miss the five second window, in which case the node will respond as though the session is inactive and deny access. However, because you have typed a key, irrespective of the five second window, TL1 responds as though the session is active and does not log you out (time out). You will not have access to the node and will receive a "DENY" response to TL1 commands. The error message may vary depending on commands issued. To recover from this situation, log out and log back in to TL1. This issue is resolved in Release 4.6.
DDTS # CSCec10357
Release 4.1 and 4.5 TL1 cannot display/retrieve/delete a DS3Xm VT Non-STS-1 cross-connection/circuit. This applies to ONS 15454s with DS3XM VT cross-connection provisioning via TL1, on any STS or port other than STS-1 or PORT-1, and with the AID format of:
VT1-Slot#-Sts#-Group#-Vt#
The cross-connection is provisioned as expected; however, the connection STS number in the TL1 VT AID format is always shown as "1" for the RTRV-CRS::ALL command and RTRV-CRS-VT1 with the AID used in the creation command (the non-one STS).
This issue has an impact on any DS3Xm VT connection deletion via TL1 where the STS number is not actually 1. The displayed VT1 AID cannot be used to retrieve the connection, and also cannot be used to delete the created connection. Also, the VT alarms/events/conditions on such a DS3XM VT circuit/connection will have the same AID issue: the StsNumber in the AID is always 1.
To work around this issue, delete the TL1-created DS3XM VT non-STS-1 cross-connection using the provisioned DS3XM VT AID (non-STS-1) or using CTC. There is no workaround for the alarm/event reporting for the non-STS-1 DS3XM VT circuit in the impacted releases (4.1 and 4.5). This issue is resolved in Release 4.6 and in maintenance Release 4.1.3.
New Features and Functionality
This section highlights new features and functionality for Release 4.6. For detailed documentation of each of these features, consult the user documentation.
New Hardware
FC_MR-4 Card
The FC_MR-4 (Fibre Channel 4-port) card uses pluggable Gigabit Interface Converters (GBICs) to transport non-SONET/SDH-framed, block-coded protocols over SONET/SDH in virtually concatenated or contiguously concatenated payloads. The FC_MR-4 can transport Fibre Channel over SONET/SDH using Fibre-Channel client interfaces and allows transport of one of the following at a time:
•
•
•
•
In Software Release 4.6, only two of the four ports can be active at one time.
For further specifications of this card, consult the Cisco ONS 15454 Reference Guide, Release 4.6.
10-Gbps Multirate Transponder Card
The Cisco ONS 15454 Multiservice Provisioning Platform (MSPP) support for a 10-Gbps multirate transponder card simplifies the integration and transport of 10 Gigabit Ethernet, OC-192, and STM-64 interfaces and services into enterprises or metropolitan and regional service provider networks. The 10-Gbps multirate transponder card can transport 10 Gigabit Ethernet, SONET OC-192, and SDH STM-64 services over a 100-GHz spaced, 50GHz stabilized, ITU-compliant wavelength. The transponder card is a plug-in module to the Cisco ONS 15454 MSPP, enabling a cost-effective architecture for delivering high-rate 10-Gbps services as well as low-rate services down to 1.5 Mbps. The 10-Gbps transponder card architecture contains a single client interface that is mapped to a single line interface, without accessing the Cisco ONS 15454 shelf cross-connect fabric.
The client interface supports 10 Gigabit Ethernet LAN physical layer (PHY), 10 Gigabit Ethernet WAN PHY, SONET OC-192, and SDH STM-64 signals. The interface to the client is a short-reach/intra-office, 1310-nm optical interface using LC connectors supporting fiber distances of up to 2 km (with or without the Y-protection option).
The line interface provides one 10-Gbps, long-reach, ITU-compliant, 100-GHz-spaced optical interface using LC connectors supporting OC-192, STM-64, 10 Gigabit Ethernet LAN PHY, or 10 Gigabit Ethernet WAN PHY interfaces. The DWDM output line interface is tunable across two adjacent 100-GHz wavelengths, enabling support for 32 channel DWDM networks via 16 discrete card types. Using amplification and dispersion compensation, the 10-Gbps transponder card is capable of a 300-km reach. When operated within the outlined specifications each card will transport the 10-Gbps signal with a maximum bit error rate (BER) of 10E-15.
The 10-Gbps transponder card incorporates both a client and DWDM line interface on the same card. The 10-Gbps transponder cards are deployable in the 12 multiservice interface card slots of the Cisco ONS 15454 platform, in systems with or without cross-connect cards. The addition of a cross-connect card enables the platform to support hybrid applications, containing transparent 10-Gbps services as well as aggregation of other services supported by the Cisco ONS 15454 platform. The only required common card is the appropriate timing, communications, and control card.
The 10-Gbps transponder card provides many carrier-class features and advanced capabilities necessary to deliver 10-Gbps services, including the protocol transparency, wavelength tunability, flexible protection mechanisms, flow-through timing, management, and performance monitoring capabilities.
For further specifications of this card, consult the Cisco ONS 15454 Reference Guide, Release 4.6.
4 x 2.5-Gbps Muxponder Card
The Cisco ONS 15454 Multiservice Provisioning Platform (MSPP) support for a 4x 2.5-Gbps muxponder card expands the Cisco ONS platform's OC-48/STM-16 interface density. The card enables the delivery of transparent 2.5-Gbps-based services for enterprises or metropolitan and regional service provider networks. The Cisco ONS 15454 MSPP 4x 2.5-Gbps muxponder card can transport four OC-48/STM-16 payloads over an OC-192/STM-64-based, 100-GHz spaced, 50GHz stabilized, ITU-compliant wavelength with provisionable digital wrapper (G.709) and selectable forward error correction (FEC). The muxponder card is a plug-in module to the Cisco ONS 15454 MSPP, enabling a high-density, cost-effective solution for OC-48/STM-16 services transport over a platform capable of low-rate services down to 1.5 Mbps. The muxponder card architecture contains four client interfaces that are mapped to a single line interface, without accessing the Cisco ONS 15454 shelf cross-connect fabric.
Each client interface provides a 2.488-Mbps (OC-48/STM-16) SONET/SDH interface via a small-form-factor-pluggable (SFP) optics module with LC connectors, providing the flexibility to support several optical reaches, including short-reach/intra-office, intermediate-reach/short-haul, and long-reach/long-haul, with support for qualified DWDM and DWDM SFP modules. The muxponder card supports any mixture of SFP reach types and also supports in-service insertion or removal without affecting other active ports.
The DWDM line interface provides one 9.95328-Gbps (OC-192/STM-64) or 10.70923-Gbps (OC-192/STM-64 with G.709 digital wrapper enabled), long-reach/long-haul, ITU-compliant, 100-GHz spaced optical interface using LC connectors supporting OC-48/STM-64 interfaces. The DWDM output line interface is tunable across two adjacent 100-GHz wavelengths, reducing inventories for spares. Using amplification and dispersion compensation, the muxponder card is capable of a 300-km reach. When operated within the outlined specifications, each card will transport the 10-Gbps signal with a maximum bit error rate (BER) of 10E-15.
The muxponder card incorporates the four clients and one DWDM line interface on the same card. The muxponder cards are deployable in the 12 multiservice interface card slots of the Cisco ONS 15454 platform, in systems with or without cross-connect cards. The addition of a cross-connect card enables the platform to support hybrid applications, containing transparent 2.5-Gbps services as well as aggregation of the other services supported by the Cisco ONS 15454 platform. The only other common card required for operation is the timing, communications, and control (TCC2) card. The muxponder card provides many carrier-class features and capabilities necessary to deliver 2.5-Gbps services, including selectable protocol transparency, wavelength tunability, flexible protection mechanisms, flexible timing options, and management capabilities.
For further specifications of this card, consult the Cisco ONS 15454 Reference Manual, Release 4.6.
New Software Features and Functionality
DWDM and TDM Hybrid Node Support
Hybrid Nodes Overview
A hybrid node running Release 4.6 allows TDM cards and DWDM cards to be used in the same node, and is limited primarily by the slots available to the node. Hybrid functionality combines the abilities of nodes running software prior to Release 4.5 (in terms of tributary add/drop traffic including SONET, SDH, and Ethernet incorporated into linear, ring, and PPMN topologies) with the Release 4.5 DWDM functionality, supporting additional hybrid node types, in open ring, closed ring, and linear configurations.
DWDM and TDM Hybrid Node Types
The node type in a network configuration is determined by the type of card that is installed in an ONS 15454 hybrid node. The ONS 15454 supports the following hybrid DWDM and TDM node types.
1+1 Protected Flexible Terminal Node
The 1+1 protected flexible terminal node is a single ONS 15454 node equipped with a series of OADM cards acting as a hub node configuration. This configuration uses a single hub or OADM node connected directly to the far-end hub or OADM node through four fiber links. This node type is used in a ring configured with two point-to-point links. The advantage of the 1+1 protected flexible terminal node configuration is that it provides path redundancy for 1+1 protected TDM networks (two transmit paths and two receive paths) using half of the DWDM equipment that is usually required.
Scalable Terminal Node
The scalable terminal node is a single ONS 15454 node equipped with a series of OADM cards and amplifier cards. This node type is more cost effective if a maximum of 16 channels are used. This node type does not support a terminal configuration exceeding 16 channels because the 32-channel terminal site is more cost effective for 17 channels and beyond.
The OADM cards that can be used in this type of node are: AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, and AD-1B-xx.x. You can also use AD-4B-xx.x and up to four 4MD-xx.x cards. The OPT-PRE and/or OPT-BST amplifiers can be used. The OPT-PRE or OPT-BST configuration depends on the node loss and the span loss. When the OPT-BST is not installed, the OSC-CSM must be used instead of the OSCM card.
Hybrid Terminal Node
A hybrid terminal node is a single ONS 15454 node equipped with at least one 32 MUX-O card, one 32 DMX-O card, two TCC2 cards, and TDM cards. If the node is equipped with OPT-PRE or OPT-BST amplifiers, it is considered an amplified terminal node. The node becomes passive if the amplifiers are removed. The hybrid terminal node type is based on the DWDM terminal node type (see the Cisco ONS 15454 Reference Manual, R4.6).
Hybrid OADM Node
A hybrid OADM node is a single ONS 15454 node equipped with at least one AD-xC-xx.x card or one AD-xB-xx.x card, and two TCC2 cards. The hybrid OADM node type is based on the DWDM OADM node type (see the Cisco ONS 15454 Reference Manual, R4.6). TDM cards can be installed in any available slot.
Hybrid Line Amplifier Node
A hybrid line amplifier node is a single ONS 15454 node with open slots for both TDM and DWDM cards.
Amplified TDM Node
An amplified TDM node is a single ONS 15454 node that increases the span length between two ONS 15454 nodes that contain TDM cards and optical amplifiers. There are three possible installation configurations for an amplified TDM node. Scenario 1 uses client cards and OPT-BST amplifiers. Scenario 2 uses client cards, OPT-BST amplifiers, OPT-PRE amplifiers, and FlexLayer filters. Scenario 3 uses client cards, OPT-BST amplifiers, OPT-PRE amplifiers, AD-1C-xx.x cards, and OSC-CSM cards.
The client cards that can be used in an amplified TDM node are: TXP_MR_10G, MXP_2.5G_10G, TXP_MR_2.5G, TXPP_MR_2.5G,
OC-192 LR/STM 64 ITU 15xx.xx, and OC-48 ELR/STM 16 EH 100 GHz.
Support for Hybrid Networks
The hybrid network configuration is determined by the type of node that is used in an ONS 15454 network. Along with TDM nodes, the ONS 15454 supports the following hybrid node types: 1+1 protected flexible terminal, scalable terminal, hybrid terminal, hybrid OADM, hybrid line amplifier, and amplified TDM. For examples and details of hybrid network types, see the Cisco ONS 15454 Reference Manual, R4.6.
FC_MR-4 Fiber Channel Card Support
The FC_MR-4 card reliably transports carrier-class, private-line Fibre Channel/FICON transport service. Each FC_MR-4 card can support up to two 1-Gbps circuits or a single 2-Gbps circuit. A 1-Gbps circuit is mapped to an STS-24c/VC4-8c (STS-3c-8v) and 2-Gbps circuits are mapped to an STS-48c/VC4-24c. The FC_MR-4 card incorporates features optimized for carrier-class applications such as:
•
•
•
•
•
The FC_MR-4 payloads can be transported over the following protected circuit types, in addition to unprotected circuits:
•
•
•
•
The FC_MR-4 card supports high-order virtual concatenation (VCAT).
The FC_MR-4 uses pluggable GBICs for client interfaces and is compatible with the following GBIC types:
•
•
Security Enhancements
The following security enhancements are added or updated in Release 4.6. For specific details on these enhancements, consult the Cisco ONS 15454 SDH Reference Manual, Release 4.6.
•
•
•
•
•
•
•
•
New Default Superuser Password
As of Release 4.6 the default password for a superuser when you first log onto a new node is changed. The new default is "otbu+1" consistently across all ONS 15454, ONS 15454 SDH, ONS 15600, and ONS 15327 platforms. This change does not affect users upgrading from a previous release, who will continue to use the password they have selected that is stored in their previous release's database.
GNE Load Balancing
Release 4.6 provides fault tolerant GNE load balancing capability, allowing CTC to reach ENEs over multiple GNEs without the ENEs being advertised by the GNE over OSPF.
Automatic Laser Shutdown
Automatic Laser Shutdown (ALS) is a technique used to automatically shut down the output power of the transmitter in case of fiber break according to ITU-T G.664. If ALS is enabled, after at least 500 ms of continuous presence of an LOS defect, the transmitter is shut down. Once the ALS is engaged, a laser pulse is sent from the transmitter periodically in case of auto mode; or a single pulse is sent in case of manual mode for recovering from the fiber break.
Optical interfaces of ONS 15454 and ONS 15454 SDH support ALS, but due to hardware limitations of current optical cards, only OC192/STM64, OC48/STM16-ELR, and OC3/STM1-8 support the ALS feature.
The pulse recovery interval time for automatic restart is configurable within 60s and 300s. The default is 100s. The laser pulse recovery width is within 2s and 10s. This is to ensure proper operation of the ALS when connecting into long haul WDM systems. In some cases a pulse width of 2s is insufficient to consistently turn on all of the lasers in a given transmission path. In case of "manual restart for test" the pulse recovery width is 100s.
ALS is disabled by default in both the SONET and SDH implementations. The ALS can be disabled on each optical interface individually.
Configuration Management for Automatic Laser Shutdown
Release 4.6 allows you to configure the following options on ALS for optical cards on a per port basis.
•
•
•
•
Release 4.6 allows you to configure the pulse recovery width between 2s and 10s, and the pulse recovery interval between 60s and 300s. The default values are set to 2s and 100s correspondingly on a per port basis.
Release 4.6 allows you to send a restart command when manual restart or manual restart for test is chosen and ALS is engaged on a per optical card port basis.
DCC Capacity, Management, and Tunneling
With Release 4.6 the TCC2 supports up to 68 SDCC or 28 LDCC terminations. The TCC2 supports mapping of any available SDCC to a GCC, up to the maximum SDCC count supported by the NE.
Note
Any optical port can be provisioned to use either SDCC or LDCC termination, with the exception of 4-port OC-3, which only supports SDCC.
SDCC and LDCC termination can coexist on the same fiber, in which case there is only one link created in the topology.
The TCC2 supports 32-bit HDLC CRC for SDCC and 16-bit HDLC CRC for LDCC termination.
The TCC2 supports provisioning of two types of DCC tunnel, hardware transparent and IP encapsulated. IP encapsulated is only supported for SDCC tunnel.
The TCC2 supports up to 68 DCC tunnels to carry foreign DCC traffic.
The TCC2 supports up to 10 IP encapsulated SDCC tunnels.
If an ONS node is acting as a hub node that interconnects with third party nodes in a path protection, and two tunnels are provisioned on the two path protection links, one ONS node can have 10/2 = 5 path protection rings.
Cisco recommends the total number of IP encapsulated tunnels in a DCC network be 64; however, this recommendation is not enforced by the NMS.
The number of path protections supported is the maximum supported DCC terminations, divided by 2.
CTC Support
CTC supports provisioning of up to 68 SDCC terminations and 28 LDCC terminations per node.
CTC defaults the OSPF metric of an SDCC termination link to 100, and LDCC to 33.
CTC allows HDLC CRC provisioning for SDCC/LDCC termination to either 16-bit or 32-bit. For SDCC, the default is 32-bit; for LDCC, the default is 16-bit.
CTC issues a warning if both SDCC and LDCC are provisioned on the same port.
CTC supports provisioning of up to 68 DCC tunnels and 10 IP encapsulated tunnels per node.
CTC supports both transparent and IP encapsulated DCC tunnels. When creating a new tunnel you have the option of selecting whether to create a traditional (transparent) or IP encapsulated tunnel. You are prompted to pick the two end points and then the provisioning will be done on each end point node, and nodes along the path for the transparent tunnel. For the IP encapsulated tunnel, CTC supports provisioning of the throttling threshold, with 100% as the default. It is also possible to provision the maximum bandwidth of the IP encapsulated tunnel.
CTC supports upgrading an existing SDCC tunnel from transparent to IP encapsulated and vice versa.
If you have an SDCC tunnel between Node A and Node B, CTC allows you to select the tunnel and select to upgrade from transparent to IP encapsulated. CTC deletes the existing tunnel and create the terminations at the two end points for the IP encapsulated tunnel. Only tunnels that are in ACTIVE state are upgraded in this way. INCOMPLETE tunnels have the upgrade option disabled. You can also choose to manually delete the existing tunnel and then create an IP-encapsulated tunnel.
Alarms
With Release 4.6 an LDCC failure alarm is raised when an LDCC termination fails.
Legacy DCC Tunneling Support
With Release 4.6 you can select either Legacy DCC Tunneling or Encapsulated Tunneling as currently supported by your ONS system.
Go-and-Return Path Protection Routing
The go-and-return path protection routing option allows you to route the path protection working path on one fiber pair and the protect path on a separate fiber pair. The working path will always be the shortest path. If a fault occurs, neither the working nor the protection fibers are affected. This feature only applies to bidirectional path protection circuits. The go-and-return option appears on the Circuit Attributes panel of the Circuit Creation wizard.
BLSR Enhancements
BLSR Maximum Ring Support
Release 4.6 BLSR supports a maximum of five rings per node, with maximums of five two-fiber, and one four-fiber ring per node.
BLSR 6 Character Ring ID
The name can be from 1 to 6 characters in length. Any alphanumeric string is permissible, and upper and lower case letters can be combined. Do not use the character string "All" in either upper or lower case letters, this is a TL1 keyword and will be rejected. Do not choose a name that is already assigned to another BLSR.
CTC Enhancements
Performance Monitoring Enhancements for the FC_MR-4 Fiber Channel Card
CTC provides FC_MR-4 performance information, including line-level parameters, port bandwidth consumption, and historical statistics. The FC_MR-4 card performance information is divided into the Statistics, Utilization, and History tabbed windows within the card view Performance tab window.
FC_MR-4 Statistics Window
The statistics window lists parameters at the line level. The Statistics window provides buttons to change the statistical values shown. The Baseline button resets the displayed statistics values to zero. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval at which automatic refresh occurs. The Statistics window also has a Clear button. The Clear button sets the values on the card to zero. All counters on the card are cleared. For specific parameters see the Cisco ONS 15454 Reference Manual, R4.6.
FC_MR-4 Utilization Window
The Utilization window shows the percentage of Tx and Rx line bandwidth used by the ports during consecutive time segments. The Utilization window provides an Interval menu that enables you to set time intervals of 1 minute, 15 minutes, 1 hour, and 1 day.
FC_MR-4 History Window
The History window lists past FC_MR-4 statistics for the previous time intervals. Depending on the selected time interval, the History window displays the statistics for each port for the number of previous time intervals.
Alarms Window
Path Width Column
In alarm windows, the display now includes a column called "Path Width"
that indicates how many STSs are contained in the alarmed path.
CTC Enhanced Alarm Severity Profiles
Card and Node View
With Release 4.6 the profile name is more detailed for inherited profiles. Instead of "Inherited," the name now offers descriptive information that gives you a better idea of where the severity values are derived from. For example, the name might say "Inherited from Node profile."
Alarm Profile Editor in Card and Node Views
The "Alarm Profile Editor" tab has been added. You can create, download, clone, or delete alarm severity profiles now from the card view or node view in addition to the traditionally available network view capability.
Alarm Profile Editor, All Levels
The term "UNSET" has been replaced with "Use Default" to clarify where the severity value comes from.
If there is only one profile loaded, the store button is available and will autoselect that profile even if it is not selected.
Buttons have a horizontal layout.
There is a new check box option, "Only Show service-affecting severities." If checked this box does as the description says. If unchecked, each cell shows the service-affecting/non-service-affecting severities, if applicable. For example, if a cell contains a Major severity, checking the box will show "MJ," and unchecking the box will show "MJ/MN."
Permanent profiles (for example, "Default" and "Inherited") are not editable until the name is changed to a non-permanent-profile name.
Spanning Tree EtherBridge Circuits Window
Release 4.6 allows you to manage spanning tree information more easily by providing the EtherBridge Circuits window. To see the window, in node view, click the Maintenance > EtherBridge > Circuits tabs.
In the EtherBridge Circuits window you can view the following information:
•
•
•
•
Context-Sensitive Help
With Release 4.6 you can access context-sensitive help from any CTC window, dialog box, or wizard, affording you "What's this?" level information about CTC fields and table columns at the network, node, and card views.
Configurable Superuser Clear PM
On a configurable basis, where the current system behavior is the default, a superuser can configure the security level required to clear PMs. The ability to baseline PM remains unchanged. You can configure this feature in NE defaults.
PID/VID Visibility
With Release 4.6 CTC, TL1, SNMP, and the interface to CTM display the PID/VID information programmed into all components with PID/VIDs.
This applies to all platforms where PID/VID is stored on the components.
Release 4.6 supports setting the PID/VID in the factory.
Proxy ARP Enhancement
Release 4.6 enhances the ARP proxy function to perform proxy ARP for all target addresses in the system's routing table (not just for the DCC connected devices).
SNMP GNE Proxy
With Release 4.6 the TCC2 adds SNMP proxy capability for SNMP GET/SET commands and the responses to/from the ENE. The SNMP manager specifies the ENE address in the SNMP PDU, similar to the addressing for a shelf slot (for example, <GNE-community-string>{ENE-Address, ENE-community-string}).
K2 Bits Alarm Notification on 1+1 APS
With Release 4.6, K2 bits alarm notification on 1+1 APS supports uniform APS settings across your network. In the case, for example, where one ONS 15454/ONS 15454 SDH node is configured to have 1+1 APS protection on the OC-12 cards in Slots 1 and 2, and Slot 1 is connected to Slot 1 of another node that does not have APS 1+1 configured, an alarm will be raised to alert you to the incomplete provisioning.
Alarming on Duplicate Node IDs
A minor, non-service affecting (MN, NSA) alarm is raised if duplicate node names are detected when two nodes are in the same DCC area. The alarm clears when the duplicate node name is changed or the DCC link is broken.
Alarm on Firewall Turned Off
Release 4.6 raises a transient condition when the firewall feature (proxy) is disabled after having been enabled.
Rear Panel Ethernet Connection Detach Alarm
The rear panel Ethernet connection detach alarm, when raised, indicates that the backplane LAN connection has been disconnected from a GNE. This allows detection of anyone trying to use the connection to access a corporate DCN.
•
•
•
Note
The NE default parameter for this option is set to "off" (by a superuser only).
Port Status via Front Panel LCD
Release 4.6 introduces an enhancement to the fan tray LCD display/controls to increase visibility to the status of various ports on the NE. Prior to Release 4.6, a craft person local to the node could not determine which tributary OC-x port card was carrying traffic in a protection group. This enhancement will now allow a craft person determine which OC-x port cards are carrying traffic without having to log into CTC.
With Release 4.6, using the fan tray LCD buttons, you can drill down to specific slots and ports to display:
•
•
IP Tunnel Throttle Capability
An IP tunnel that will tunnel traffic from foreign nodes in the form of UDP-i packets can flood the network. With Release 4.6 you can throttle these tunnels. You can set the throttle bandwidth percentage in a text field labeled Max Bandwidth when you create an IP tunnel using the wizard. Once an IP Tunnel is created you can also edit the tunnel and set the throttle bandwidth. Alternatively, when you are changing an IP Tunnel from SDCC (traditional) to IP Encapsulated, you can set the throttle bandwidth at that time.
ML-Series
VCAT
VCAT significantly improves the efficiency of data transport by grouping the synchronous payload envelopes (SPEs) of SONET/SDH frames in a nonconsecutive manner into VCAT groups. VCAT group circuit bandwidth is divided into smaller circuits called VCAT members. The individual members act as independent circuits. Intermediate nodes treat the VCAT members as normal circuits that are independently routed and protected by the SONET/SDH network. At the terminating nodes, these member circuits are multiplexed into a contiguous stream of data. VCAT avoids the SONET/SDH bandwidth fragmentation problem and allows finer granularity for provisioning of bandwidth services.
Note
SW-LCAS
LCAS increases VCAT flexibility by allowing the dynamic reconfiguration of VCAT groups without interrupting the operation of non-involved members. SW-LCAS is the software implementation of a LCAS-type feature. SW-LCAS differs from LCAS because it is not errorless and uses a different handshaking mechanism. SW-LCAS on the ML-Series card allows the automatic addition or removal of a VCAT group member in the event of a failure or recovery on two-fiber BLSR. The protection mechanism software operates based on ML-Series card link events. SW-LCAS allows service providers to configure VCAT member circuits on the ML-Series as protection channel access (PCA). This PCA traffic is dropped in the event of a protection switch, but is suitable for excess or noncommitted traffic and can double total available bandwidth on the circuit.
Microcode Image Enhancements
With Release 4.6 you can choose from three microcode images for the ML-Series card. The default basic image has the same ML-Series base functionality as the Software Release 4.1 IOS image, Cisco IOS Release 12.1(19)EO, plus some additional non-microcode dependant R4.6 features, such as the ML-Series virtual concatenation (VCAT) circuits. The basic image also allows users to upgrade from Software R4.0 or R4.1 to Software R4.6 without changing the existing configurations on ML-Series cards.
Enhanced Performance Monitoring
Enhanced performance monitoring displays per-CoS packet statistics on the ML-Series card interfaces when CoS accounting is enabled. Per-CoS packet statistics are only supported for bridged services, not IP routing or MPLS. CoS-based traffic utilization is displayed at the FastEthernet or GigabitEthernet interface or subinterface (VLAN) level or the POS interface level but not at the POS subinterface level. RPR statistics are not available at the SPR interface level, but statistics are available for the individual POS ports that make up the SPR interface. EtherChannel (port-channel) and BVI statistics are available only at the member port level.
Combination VLAN-transparent Services and One or More VLAN-specific Services
In Software Release 4.6 and later, the ML-Series card supports combining VLAN-transparent services and one or more VLAN-specific services on the same port. All of these VLAN-transparent and VLAN-specific services can be point-to-point or multipoint-to-multipoint. This allows a service provider to combine a VLAN-transparent service, such as IEE 802.1Q tunneling (QinQ), with VLAN-specific services, such as bridging specific VLANs, on the same customer port. For example, one customer VLAN can connect to Internet access and the other customer VLANs can be tunneled over a single provider VLAN to another customer site, all over a single port at each site. VLAN-transparent service is also referred to as Ethernet Wire Service (EWS). VLAN-specific service is also referred to as Ethernet Relay Multipoint Service (ERMS).
Ethernet-over-MPLS (EoMPLS) Tunneling
EoMPLS provides Ethernet services across the MPLS backbone and core network. The ML series EoMPLS microcode image supports both VLAN and Port based point to point Ethernet tunnels across the MPLS network. The ML series EoMPLS feature enables Ethernet service delivery on the access SONET/SDH network over the RPR and transport that service across the core MPLS network without the need to create a separate bridged access network.
MST Protocol Tunneling
Release 4.6 MST Protocol Tunneling allows Multi-Spanning-Tree on an external bridge to be used to enable a redundant pair of ML-series cards without requiring a spanning-tree instance per VLAN.
DS3i-N-12 Card Support for SONET Platforms
Release 4.6 adds SONET support for the DS3i-N-12 card, as specified herein. For DS3i-N-12 card features and specifications, refer to the Cisco ONS 15454 Reference Manual, R4.6.
Compatibility and Interoperability
The DS3i-N-12 card is not compatible with the DS3 or the DS3E card. There is no in-service upgrade path from DS3 or DS3E to DS3i-N-12. Plugging a DS3i-N-12 card into a slot provisioned for DS3 will result in an MEA. Plugging a DS3 card into a slot provisioned for DS3i-N-12 will result in an MEA.
The DS3i-N-12 card operates with either the XC10G or the XCVT card. Future cross connect cards will be supported as they become available.
The DS3i-N-12 card operates with either the TCC+ or the TCC2 as the shelf controller as long as the particular type of TCC card is supported with the particular software release. Future shelf controller cards will be supported as they become available.
Caution
Circuit Provisioning
The following guidelines apply for circuit provisioning with the DS3i-N-12 card.
•
•
•
•
•
•
•
•
Note
Protection Group Support
For SONET nodes, the DS3i-N-12 card supports 1:1 and 1:N where 1 <= N <= 5. Any DS3i-N-12 card can function as a protect card in a 1:N protection group. The working and protect slots follow the convention for other 1:1 and 1:N electrical protection groups.
For 1:1 protection:
•
•
•
•
•
•
For 1:N protection, the protect Slot 3 can protect Slots 1, 2, 4, 5, and 6; and protect Slot 15 can protect Slots 12, 13, 14, 16, and 17.
Mixed protection groups between DS3 and DS3i-N-12 cards are not supported.
Protection switching for 1:1 and 1:N meets required 60 ms switch times.
Switch times for XCVT or XC10G side switches meet required 60 ms switch times.
The current equipment protection behavior of switch, lock on, and lock out are supported.
Performance Monitoring Support
Release 4.6 supports the following performance monitoring functions related to the DS3i-N-12.
•
•
•
•
•
Note
Alarm Support
SD/SF BER calculation is performed at the DS3 line level (similar to the DS3 cards). SD/SF alarming occurs if the BER exceeds the provisioned SD, or SF thresholds, respectively. The SF alarm suppresses the reporting of the SD alarm.
The DS3i-N-12 card supports the standard DS3 alarms, LOS and LOF.
Path Trace Support
The DS3i-N-12 card supports setting and reading of a 16 or 64 byte J1 path trace string.
Intermediate monitoring of the J1 path trace by the optical cards is not supported.
On a path trace mismatch, the TIM-P alarm is raised.
Generation of AIS on TIM-P is user-provisionable as "on" or "off."
Software Upgrade Support
Software upgrades are errorless for TCC2/XC10G systems.
Note
CTC Support
In Release 4.6 the column "Path Width" has been added to Alarms, Conditions and History panes. The Path Width column provides the width of the STS path on which the alarm is raised or cleared, in units of STS (how many STSs wide the path is). The path width only applies to the "STS-" alarmable object type. For any non-STS object, the column remains blank.
CTC also supports the following functionality for the DS3i-N-12 card for Release 4.6.
•
•
•
•
•
New TL1 Features
The following TL1 features are new for Release 4.6. For detailed instructions on using TL1 commands, consult the TL1 Command Guide for Release 4.6.
Functional Differences
FC-MR-4
The FC-MR-4 card is added in Release 4.6.
VCAT
VCAT/CCAT circuit provisioning is allowed from Release 4.6. Currently it is supported only on ML-series cards.
BLSR
Six character ring IDs are supported in BLSR/MSSP Rings.
Alarms
SF/SD alarms are supported on all electric cards. SFBER and SDBER parameters are introduced in the ED-T1, ED-T3, ED-EC1, and ED-DS3I commands.
Alarm on Fire wall can be turned On/Off using ALW-MSG-ALL/INH-MSG-ALL commands.
STS/VT cross-connections can now be retrieved at NE/Card/Port/Path level using new commands RTRV-STS and RTRV-VT.
TL1 Security Enhancements
The following security enhancements are available in Release 4.6
•
•
•
•
•
•
•
•
•
TL1 Additional Support Added
Optical PMs and ALS support is added in OC3-8 card.
Test Access support is added for SDH cards.
OPR/RLS-PROTNSW-<mod2> and EX-SW commands support <dirn> parameter.
Program ID and Version ID of all components which have PID/VID programmed in them are now displayed in RTRV-INV command's response.
COPY-RFILE is enhanced to perform Database backup and restore.
INIT-REG command can now clear individual montypes.
TL1 Commands Added
The following commands were added in Release 4.6:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
TL1 Commands Enhanced
ENT-EQPT and ED-EQPT were enhanced to add the CMDMDE name/value parameter
ENUM Differences
ALL_MONTYPE enum items dropped from Release 4.5:
•
ALL_MONTYPE enum items added to Release 4.6:
•
ALL_MONTYPE is used in the following commands:
•
•
•
•
•
ALL_THR enum items dropped from Release 4.5:
•
ALM_THR enum items added to Release 4.6:
•
•
•
•
•
•
•
•
•
•
•
ALM_THR is used in the following commands:
•
•
•
•
CRS_TYPE enum items added to Release 4.6:
•
CRS_TYPE is used in the following commands:
•
DATARATE enum items added to Release 4.6:
•
•
•
•
DATARATE is UNUSED in any command.
DS_LINE_TYPE enum items added to Release 4.6:
•
DS_LINE_TYPE is used in the following commands:
•
•
•
•
DWDM_RING_TYPE enum items added to Release 4.6:
•
DWDM_RING_TYPE is used in the following commands:
•
•
EQPT_TYPE enum items dropped from Release 4.5:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
EQPT_TYPE enum items added to Release 4.6:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
EQPT_TYPE is used in the following commands:
•
EQUIPMENT_TYPE enum items added to Release 4.6:
•
EQUIPMENT_TYPE is used in the following commands:
•
FC_LINKRATE enum items added to Release 4.6:
•
•
•
•
FC_LINKRATE is used in the following commands:
•
FRAME_FORMAT enum items added to Release 4.6:
•
•
FRAME_FORMAT is used in the following commands:
•
•
•
•
IMPEDANCE enum items added to Release 4.6:
•
IMPEDANCE is used in the following commands:
•
•
LINE_CODE enum items added to Release 4.6:
•
LINE_CODE is used in the following commands:
•
•
•
•
LPBK_TYPE enum items added to Release 4.6:
•
LPBK_TYPE is used in the following commands:
•
•
MOD2 enum items added to Release 4.6:
•
•
•
•
•
MOD2 is used in the following commands:
•
•
•
•
•
MOD2ALM enum items added to Release 4.6:
•
•
MOD2ALM is used in the following commands:
•
•
MOD2B enum items added to Release 4.6:
•
•
MOD2B is used in the following commands:
•
•
•
•
•
•
•
•
•
MOD2O enum items added to Release 4.6:
•
•
MOD2O is used in the following commands:
•
•
MOD2_IO enum items added to Release 4.6:
•
•
MOD2_IO is used in the following commands:
•
MOD_PATH enum items added to Release 4.6:
•
MOD_PATH is used in the following commands:
•
•
•
MOD_PORT enum items dropped from Release 4.5:
•
•
•
•
•
•
•
•
MOD_PORT is used in the following commands:
•
OPTICAL_BAND enum items dropped from Release 4.5:
•
OPTICAL_BAND enum items added to Release 4.6:
•
OPTICAL_BAND is used in the following commands:
•
•
•
OPTICAL_LINK_TYPE enum items added to Release 4.6:
•
•
•
•
OPTICAL_LINK_TYPE is used in the following commands:
•
•
REVERTIVE_TIME enum items added to Release 4.6:
•
REVERTIVE_TIME is used in the following commands:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
SA_BIT enum items added to Release 4.6:
•
•
•
•
•
SA_BIT is used in the following commands:
•
•
SST enum items added to Release 4.6:
•
SST is used in Most ED/RTRV commands.
STS_PATH enum items dropped from Release 4.5:
•
•
•
•
•
•
•
•
STS_PATH is used in the following commands:
•
•
•
TACC_MODE enum items added to Release 4.6:
•
TACC_MODE is used in the following commands:
•
•
•
TAPTYPE enum items added to Release 4.6:
•
•
TAPTYPE is used in the following commands:
•
•
•
•
•
•
•
•
•
•
•
TRCMODE enum items added to Release 4.6:
•
•
•
TRCMODE is used in the following commands:
•
•
•
•
•
•
•
USER_LOGINS enum items added to Release 4.6:
•
•
USER_LOGINS is used in the following commands:
•
WDM enum items dropped from Release 4.5:
•
•
•
•
•
•
•
WDM is UNUSED in any command.
COMMAND Syntax Changes
The syntax of the following commands was changed from Release 4.5 to Release 4.6:
CONN-TACC-DS1 syntax changed:
CONN-TACC-DS1[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-DS1[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
CONN-TACC-STS1 syntax changed:
CONN-TACC-STS1[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-STS1[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
CONN-TACC-STS12C syntax changed:
CONN-TACC-STS12C[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-STS12C[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
CONN-TACC-STS192C syntax changed:
CONN-TACC-STS192C[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-STS192C[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
CONN-TACC-STS24C syntax changed:
CONN-TACC-STS24C[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-STS24C[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
CONN-TACC-STS3C syntax changed:
CONN-TACC-STS3C[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-STS3C[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
CONN-TACC-STS48C syntax changed:
CONN-TACC-STS48C[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-STS48C[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
CONN-TACC-STS6C syntax changed:
CONN-TACC-STS6C[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-STS6C[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
CONN-TACC-STS9C syntax changed:
CONN-TACC-STS9C[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-STS9C[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
CONN-TACC-T1 syntax changed:
CONN-TACC-T1[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-T1[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
CONN-TACC-T3 syntax changed:
CONN-TACC-T3[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-T3[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
CONN-TACC-VT1 syntax changed:
CONN-TACC-VT1[:<TID>]:<aid>:<CTAG>[::<tap>]:MD=<md>;
CONN-TACC-VT1[:<TID>]:<aid>:<CTAG>::<tap>:MD=<md>;
COPY-IOSCFG syntax changed:
COPY-IOSCFG[:<TID>]:<src>:<CTAG>::SRC=<src1>,DEST=<dest>;
COPY-IOSCFG[:<TID>]:<aid>:<CTAG>::SRC=<src>,DEST=<dest>;
COPY-RFILE syntax changed:
COPY-RFILE[:<TID>]:<src>:<CTAG>::TYPE=<xfertype>,[SRC=<srcurl>,][DEST=<desturl>];
COPY-RFILE[:<TID>]:<src>:<CTAG>::TYPE=<xfertype>,[SRC=<srcurl>,][DEST=<desturl>,][OVWRT=<ovwrt>,][FTTD=<fttd>];
DLT-EQPT syntax changed:
DLT-EQPT[:<TID>]:<aid>:<CTAG>[:::];
DLT-EQPT[:<TID>]:<tap>:<CTAG>;
DLT-UCP-CC syntax changed:
DLT-UCP-CC[:<TID>]:<aid >:<CTAG>[::::];
DLT-UCP-CC[:<TID>]:<aid>:<CTAG>[::::];
ED-BITS syntax changed:
ED-BITS[:<TID>]:<aid>:<CTAG>[:::LINECDE=<linecde>,][FMT=<fmt>,][LBO=<lbo>,][SYNCMSG=<syncmsg>,][AISTHRSHLD=<aisthrshld>][:<pst>];
ED-BITS[:<TID>]:<aid>:<CTAG>[:::LINECDE=<linecde>,][FMT=<fmt>,][SABIT=<sabit>,][IMPEDANCE=<impedance>,][LBO=<lbo>,][SYNCMSG=<syncmsg>,][AISTHRSHLD=<aisthrshld>][:<pst>];
ED-CLNT syntax changed:
ED-CLNT[:<TID>]:<aid>:<CTAG>[:::NAME=<portname>,][SFBER=<sfber>,][SDBER=<sdber>,][ALSMODE=<alsmode>,][ALSRCINT=<alsrcint>,][ALSRCPW=<alsrcpw>,][COMM=<comm>,][MACADDR=<macaddr>,][SYNCMSG=<syncmsg>,][SENDDUS=<senddus>,][RLASER=<rlaser>,][SOAK=<soak>][:<pst>,][<sst>];
ED-CLNT[:<TID>]:<aid>:<CTAG>[:::NAME=<portname>,][SFBER=<sfber>,][SDBER=<sdber>,][ALSMODE=<alsmode>,][ALSRCINT=<alsrcint>,][ALSRCPW=<alsrcpw>,][COMM=<comm>,][MACADDR=<macaddr>,][SYNCMSG=<syncmsg>,][SENDDUS=<senddus>,][RLASER=<rlaser>,][SOAK=<soak>,][OSPF=<ospf>][:<pst>,][<sst>];
ED-DS1 syntax changed:
ED-DS1[:<TID>]:<aid>:<CTAG>[:::TACC=<tacc>];
ED-DS1[:<TID>]:<aid>:<CTAG>[:::TACC=<tacc>,][TAPTYPE=<taptype>];
ED-EQPT syntax changed:
ED-EQPT:[<TID>]:<aid>:<CTAG>:::[PROTID=<protid>,][PRTYPE=<prtype>,][RVRTV=<rvrtv>,][RVTM=<rvtm>][:];
ED-EQPT:[<TID>]:<aid>:<CTAG>:::[PROTID=<protid>,][PRTYPE=<prtype>,][RVRTV=<rvrtv>,][RVTM=<rvtm>,][CMDMDE=<cmdmde>][:];
ED-NE-SYNCN syntax changed:
ED-NE-SYNCN[:<TID>]::<CTAG>[:::TMMD=<tmmd>,][SSMGEN=<ssmgen>,][QRES=<qres>,][RVRTV=<rvrtv>,][RVTM=<rvtm>];
ED-NE-SYNCN[:<TID>]::<CTAG>;
ED-OCH syntax changed:
ED-OCH[:<TID>]:<aid>:<CTAG>[:::RDIRN=<rdirn>,][EXPWLEN=<expwlen>,][VOAATTN=<voaattn>,][VOAPWR=<voapwr>,][CALOPWR=<calopwr>,][CHPOWER=<chpower>,][NAME=<portname>,][SFBER=<sfber>,][SDBER=<sdber>,][ALSMODE=<alsmode>,][ALSRCINT=<alsrcint>,][ALSRCPW=<alsrcpw>,][COMM=<comm>,][GCCRATE=<gccrate>,][OSFBER=<sfber>,][OSDBER=<sdber>,][DWRAP=<drwap>,][FEC=<fec>,][MACADDR=<macaddr>,][SYNCMSG=<syncmsg>,][SENDDUS=<senddus>,][RLASER=<rlaser>,][SOAK=<soak>][:<pst>,][<sst>];
ED-OCH[:<TID>]:<aid>:<CTAG>[:::RDIRN=<rdirn>,][EXPWLEN=<expwlen>,][VOAATTN=<voaattn>,][VOAPWR=<voapwr>,][CALOPWR=<calopwr>,][CHPOWER=<chpower>,][NAME=<portname>,][SFBER=<sfber>,][SDBER=<sdber>,][OSDBER=<sdber>,][ALSMODE=<alsmode>,][ALSRCINT=<alsrcint>,][ALSRCPW=<alsrcpw>,][COMM=<comm>,][GCCRATE=<gccrate>,][DWRAP=<drwap>,][FEC=<fec>,][MACADDR=<macaddr>,][SYNCMSG=<syncmsg>,][SENDDUS=<senddus>,][RLASER=<rlaser>,][SOAK=<soak>,][OSPF=<ospf>][:<pst>,][<sst>];
ED-OTS syntax changed:
ED-OTS[:<TID>]:<aid>:<CTAG>[:::RDIRN=<rdirn>,][VOAATTN=<voaattn>,][VOAPWR=<voapwr>,][CALOPWR=<calopwr>,][CALTILT=<caltilt>,][OSRI=<osri>,][EXPGAIN=<gain>][:<pst>,][<sst>];
ED-OTS[:<TID>]:<aid>:<CTAG>[:::RDIRN=<rdirn>,][VOAATTN=<voaattn>,][VOAPWR=<voapwr>,][CALOPWR=<calopwr>,][CALTILT=<caltilt>,][OSRI=<osri>,][ALSMODE=<alsmode>,][ALSRCINT=<alsrcint>,][ALSRCPW=<alsrcpw>,][EXPGAIN=<gain>][:<pst>,][<sst>];
ED-T1 syntax changed:
ED-T1[:<TID>]:<aid>:<CTAG>[:::LINECDE=<linecde>,][FMT=<fmt>,][LBO=<lbo>,][TACC=<tacc>,][SOAK=<soak>,][SFBER=<sfber>,][SDBER=<sdber>][:<pst>,][<sst>];
ED-T1[:<TID>]:<aid>:<CTAG>[:::LINECDE=<linecde>,][FMT=<fmt>,][LBO=<lbo>,][TACC=<tacc>,][TAPTYPE=<taptype>,][SOAK=<soak>,][SFBER=<sfber>,][SDBER=<sdber>][:<pst>,][<sst>];
ED-T3 syntax changed:
ED-T3[:<TID>]:<aid>:<CTAG>[:::FMT=<fmt>,][LINECDE=<linecde>,][LBO=<lbo>,][TACC=<tacc>,][SOAK=<soak>,][SFBER=<sfber>,][SDBER=<sdber>][:<pst>,][<sst>];
ED-T3[:<TID>]:<aid>:<CTAG>[:::FMT=<fmt>,][LINECDE=<linecde>,][LBO=<lbo>,][INHFELPBK=<inhfelpbk>,][TACC=<tacc>,][TAPTYPE=<taptype>,][SOAK=<soak>,][SFBER=<sfber>,][SDBER=<sdber>][:<pst>,][<sst>];
ED-VT1 syntax changed:
ED-VT1[:<TID>]:<aid>:<CTAG>[:::RVRTV=<rvrtv>,][RVTM=<rvtm>,][HOLDOFFTIMER=<holdofftimer>,][TACC=<tacc>][:<pst>,][<sst>];
ED-VT1[:<TID>]:<aid>:<CTAG>[:::RVRTV=<rvrtv>,][RVTM=<rvtm>,][HOLDOFFTIMER=<holdofftimer>,][TACC=<tacc>,][TAPTYPE=<taptype>][:<pst>,][<sst>];
ED-WDMANS syntax changed:
ED-WDMANS[:<TID>]:<aid>:<CTAG>[:::POWER-IN=<powerIn>,][POWER-OUT=<powerOut>,][POWER-EXP=<powerExp>,][POWER-DROP=<powerDrop>,][SYS-TYPE=<sysType>,][RING-TYPE=<ringType>];
ED-WDMANS[:<TID>]:<aid>:<CTAG>[:::POWER-IN=<powerIn>,][POWER-OUT=<powerOut>,][POWER-EXP=<powerExp>,][POWER-DROP=<powerDrop>,][SYS-TYPE=<sysType>,][NTW-TYPE=<ringType>];
ENT-EQPT syntax changed:
ENT-EQPT:[<TID>]:<aid>:<CTAG>::<aidtype>:[PROTID=<protid>,][PRTYPE=<prtype>,][RVRTV=<rvrtv>,][RVTM=<rvtm>][:];
ENT-EQPT:[<TID>]:<aid>:<CTAG>::<aidtype>:[PROTID=<protid>,][PRTYPE=<prtype>,][RVRTV=<rvrtv>,][RVTM=<rvtm>,][CMDMDE=<cmdmde>][:];
ENT-UCP-CC syntax changed:
ENT-UCP-CC[:<TID>][:<aid>]:<CTAG>[:::NBRIX=<nbrix>,][CCTYPE=<cctype>,][PORT=<port>,][LOCALCCID=<localccid>,][LOCALIPCC=<localipcc>,][REMOTCCID=<remoteccid>,][REMOTEIPCC=<remoteipcc>,][LMPHELLOINT=<lmphelloint>,][LMPHELLODEADINT=<lmphellodeadint>,][MTU=<mtu>,][CRCMD=<crcmd>,][TUNMD=<tunmd>][:];
ENT-UCP-CC[:<TID>][:<aid>]:<CTAG>:::NBRIX=<nbrix>,CCTYPE=<cctype>,[PORT=<port>,][LOCALCCID=<localccid>,][LOCALIPCC=<localipcc>,][REMOTCCID=<remoteccid>,][REMOTEIPCC=<remoteipcc>,][LMPHELLOINT=<lmphelloint>,][LMPHELLODEADINT=<lmphellodeadint>,][MTU=<mtu>,][CRCMD=<crcmd>,][TUNMD=<tunmd>][:];
ENT-UCP-IF syntax changed:
ENT-UCP-IF[:<TID>]:<aid>:<CTAG>[:::NBRIX=<nbrix>,][CCID=<ccid>,][LOCALIFID=<localifid>,][REMOTEIFID=<remoteifid>,][TNATYPE=<tnatype>,][TNAADDR=<tnaaddr>,][CORENETWORKID=<corenetworkid>][:];
ENT-UCP-IF[:<TID>]:<aid>:<CTAG>:::NBRIX=<nbrix>,[CCID=<ccid>,][LOCALIFID=<localifid>,][REMOTEIFID=<remoteifid>,][TNATYPE=<tnatype>,][TNAADDR=<tnaaddr>,][CORENETWORKID=<corenetworkid>][:];
EX-SW-OC12 syntax changed:
EX-SW-OC12[:<TID>]:<aid>:<CTAG>[::<st>];
EX-SW-OC12[:<TID>]:<aid>:<CTAG>[::,<st>][,<dirn>];
EX-SW-OC192 syntax changed:
EX-SW-OC192[:<TID>]:<aid>:<CTAG>[::<st>];
EX-SW-OC192[:<TID>]:<aid>:<CTAG>[::,<st>][,<dirn>];
EX-SW-OC48 syntax changed:
EX-SW-OC48[:<TID>]:<aid>:<CTAG>[::<st>];
EX-SW-OC48[:<TID>]:<aid>:<CTAG>[::,<st>][,<dirn>];
INIT-REG-CLNT syntax changed:
INIT-REG-CLNT[:<TID>]:<src>:<CTAG>::,,[<location>,][<direction>,][<tmper>][,,];
INIT-REG-CLNT[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-DS1 syntax changed:
INIT-REG-DS1[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-DS1[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-EC1 syntax changed:
INIT-REG-EC1[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-EC1[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-G1000 syntax changed:
INIT-REG-G1000[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-G1000[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-OC12 syntax changed:
INIT-REG-OC12[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-OC12[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-OC192 syntax changed:
INIT-REG-OC192[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-OC192[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-OC3 syntax changed:
INIT-REG-OC3[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-OC3[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-OC48 syntax changed:
INIT-REG-OC48[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-OC48[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-OCH syntax changed:
INIT-REG-OCH[:<TID>]:<src>:<CTAG>::,,[<location>,][<direction>,][<tmper>][,,];
INIT-REG-OCH[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-OMS syntax changed:
INIT-REG-OMS[:<TID>]:<src>:<CTAG>::,,[<location>,][<direction>,][<tmper>][,,];
INIT-REG-OMS[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-OTS syntax changed:
INIT-REG-OTS[:<TID>]:<src>:<CTAG>::,,[<location>,][<direction>,][<tmper>][,,];
INIT-REG-OTS[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS1 syntax changed:
INIT-REG-STS1[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS1[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS12C syntax changed:
INIT-REG-STS12C[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS12C[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS192C syntax changed:
INIT-REG-STS192C[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS192C[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS24C syntax changed:
INIT-REG-STS24C[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS24C[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS3C syntax changed:
INIT-REG-STS3C[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS3C[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS48C syntax changed:
INIT-REG-STS48C[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS48C[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS6C syntax changed:
INIT-REG-STS6C[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS6C[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS9C syntax changed:
INIT-REG-STS9C[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-STS9C[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-T1 syntax changed:
INIT-REG-T1[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-T1[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-T3 syntax changed:
INIT-REG-T3[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-T3[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-VT1 syntax changed:
INIT-REG-VT1[:<TID>]:<aid>:<CTAG>::,,[<locn>,][<dirn>,][<tmper>][,,];
INIT-REG-VT1[:<TID>]:<aid>:<CTAG>::<montype>,,[<locn>,][<dirn>,][<tmper>][,,];
OPR-PROTNSW-OC12 syntax changed:
OPR-PROTNSW-OC12[:<TID>]:<aid>:<CTAG>::<sc>,[<switchType>][:];
OPR-PROTNSW-OC12[:<TID>]:<aid>:<CTAG>::<sc>[,<switchType>][:<dirn>];
OPR-PROTNSW-OC192 syntax changed:
OPR-PROTNSW-OC192[:<TID>]:<aid>:<CTAG>::<sc>,[<switchType>][:];
OPR-PROTNSW-OC192[:<TID>]:<aid>:<CTAG>::<sc>[,<switchType>][:<dirn>];
OPR-PROTNSW-OC3 syntax changed:
OPR-PROTNSW-OC3[:<TID>]:<aid>:<CTAG>::<sc>,[<switchType>][:];
OPR-PROTNSW-OC3[:<TID>]:<aid>:<CTAG>::<sc>[,<switchType>][:<dirn>];
OPR-PROTNSW-OC48 syntax changed:
OPR-PROTNSW-OC48[:<TID>]:<aid>:<CTAG>::<sc>,[<switchType>][:];
OPR-PROTNSW-OC48[:<TID>]:<aid>:<CTAG>::<sc>[,<switchType>][:<dirn>];
OPR-SYNCNSW syntax changed:
OPR-SYNCNSW[:<TID>][:<aid>]:<CTAG>::<switchto>,[<sc>];
OPR-SYNCNSW[:<TID>]::<CTAG>;
RLS-EXT-CONT syntax changed:
RLS-EXT-CONT[:<TID>]:<aid>:<CTAG>[::,];
RLS-EXT-CONT[:<TID>][:<aid>]:<CTAG>;
RLS-PROTNSW-OC12 syntax changed:
RLS-PROTNSW-OC12[:<TID>]:<aid>:<CTAG>[::];
RLS-PROTNSW-OC12[:<TID>]:<aid>:<CTAG>[::<dirn>];
RLS-PROTNSW-OC192 syntax changed:
RLS-PROTNSW-OC192[:<TID>]:<aid>:<CTAG>[::];
RLS-PROTNSW-OC192[:<TID>]:<aid>:<CTAG>[::<dirn>];
RLS-PROTNSW-OC3 syntax changed:
RLS-PROTNSW-OC3[:<TID>]:<aid>:<CTAG>[::];
RLS-PROTNSW-OC3[:<TID>]:<aid>:<CTAG>[::<dirn>];
RLS-PROTNSW-OC48 syntax changed:
RLS-PROTNSW-OC48[:<TID>]:<aid>:<CTAG>[::];
RLS-PROTNSW-OC48[:<TID>]:<aid>:<CTAG>[::<dirn>];
RTRV-ALM-ENV syntax changed:
RTRV-ALM-ENV[:<TID>]:<aid>:<CTAG>[::<ntfcncde>,][<almtype>];
RTRV-ALM-ENV[:<TID>]:<aid>:<CTAG>[::<ntfcncde>][,<almtype>];
RTRV-BITS response changes:
<aid>::[<linecde>],[<fmt>],[<lbo>],[<syncmsg>],[<aisthrshld>]:[<pst>]
<aid>::[<linecde>],[<fmt>],[<lbo>],[<syncmsg>],[<aisthrshld>],<saBit>:[<pst>]
RTRV-CLNT response changes:
<aid>:,,[<role>],[<status>]:[<plgtype>],[<serialnum>],[<partnum>],[<vendor>],[<vendorrev>],[<vendorid>],[<clei>],[<portname>],[<sfber>],[<sdber>],[<alsmode>],[<alsrcint>],[<alsrcpw>],[<comm>],[<macaddr>],[<syncmsg>],[<senddus>],[<lsrstat>],[<soak>],[<soakleft>]:<pst>,[<sst>]
<aid>:,,[<role>],[<status>]:[<plgtype>],[<serialnum>],[<vendorrev>],[<clei>],[<portname>],[<sfber>],[<sdber>],[<alsmode>],[<alsrcint>],[<alsrcpw>],[<comm>],[<partnum>],[<vendor>],[<vendorid>],[<macaddr>],[<syncmsg>],[<senddus>],[<lsrstat>],[<soak>],[<soakleft>],[<ospf>]:<pst>,[<sst>]
COMMAND Response Changes:
RTRV-DS1 response changes:
<aid>::[<tacc>]
<aid>::[<tacc>],[<taptype>]
RTRV-G1000 response changes:
<aid>::[<mfs>],[<flow>],[<lan>],[<optics>],[<soak>],[<als>],[<trans>],[<tport>],<lwmrk>,<hiwmrk>,[<buff>],[<soakleft>]:<pst>,[<sst>]
<aid>::[<mfs>],[<flow>],[<lan>],[<optics>],[<soak>],[<als>],[<trans>],[<tport>],<lwmrk>,<hiwmrk>,[<buff>]:[<soakleft>]:<pst>,[<sst>]
RTRV-INV response changes:
<aid>,<aidtype>::[<pn>],[<hwrev>],[<fwrev>],[<sn>],[<clei>],[<twl1=nwl in code>],[<twl2= wl1 in code>],[<twl3=wl2 in code>],[<twl4=wl3 in code>],[<pluginvendorid>],[<pluginpn>],[<pluginhwrev>],[<pluginfwrev>],[<pluginsn>],[<ilossref>]
<aid>,<aidtype>::[<plugtype>],[<vendor>],[<pn>],[<hwrev>],[<fwrev>],[<sn>],[<clei>],[<twl1=nwl in code>],[<twl2= wl1 in code>],[<twl3=wl2 in code>],[<twl4=wl3 in code>],[<pluginvendorid>],[<pluginpn>],[<pluginhwrev>],[<pluginfwrev>],[<pluginsn>],[<ilossref>],[<productId>],[<versionId>],[<fpgaVersion>]
RTRV-OCH response changes:
<aid>:,,[<role>],[<status>]:[<rdirn>],[<opticalPortType>],[<power>],[<expWlen>],[<actWlen>],[<iloss>],[<voamode>],[<voaattn>],[<voapwr>],[<voarefattn>],[<voarefpwr>],[<refopwr>],[<calopwr>],[<chpower>],[<portname>],[<sfber>],[<sdber>],[<alsmode>],[<alsrcint>],[<alsrcpw>],[<comm>],[<gccrate>],[<dwrap>],[<fec>],[<osfber>],[<osdber>],[<macaddr>],[<syncmsg>],[<senddus>],[<lsrstat>],[<soak>],[<soakleft>]:<pst>,[<sst>]
<aid>:,,[<role>],[<status>]:[<rdirn>],[<opticalPortType>],[<power>],[<expWlen>],[<actWlen>],[<iloss>],[<voamode>],[<voaattn>],[<voapwr>],[<voarefattn>],[<voarefpwr>],[<refopwr>],[<calopwr>],[<chpower>],[<portname>],[<sfber>],[<sdber>],[<alsmode>],[<alsrcint>],[<alsrcpw>],[<comm>],[<gccrate>],[<dwrap>],[<fec>],[<osfber>],[<osdber>],[<macaddr>],[<syncmsg>],[<senddus>],[<lsrstat>],[<soak>],[<soakleft>],[<ospf>]:<pst>,[<sst>]
RTRV-OTS response changes:
<aid>::<rdirn>,<opticalPortType>,[<power>],[<iloss>],[<voamode>],[<voaattn>],[<voapwr>],[<voarefattn>],[<voarefpwr>],[<laserst>],[<osri>],[<amplmode>],[<gain>],[<expgain>],[<refopwr>],[<calopwr>],[<reftilt>],[<caltilt>],[<dculoss>],[<awgst>],[<heatst>]:<pst>,[<sst>]
<aid>::<rdirn>,<opticalPortType>,[<power>],[<iloss>],[<voamode>],[<voaattn>],[<voapwr>],[<voarefattn>],[<voarefpwr>],[<laserst>],[<osri>],[<alsmode>],[<alsrcint>],[<alsrcpw>],[<amplmode>],[<gain>],[<expgain>],[<refopwr>],[<calopwr>],[<reftilt>],[<caltilt>],[<dculoss>],[<awgst>],[<heatst>]:<pst>,[<sst>]
RTRV-STS9C response changes:
<aid>::[<level>],[<sfber>],[<sdber>],[<rvrtv>],[<rvtm>],[<swpdip>],[<holdofftimer>],[<exptrc>],[<trc>],[<inctrc>],[<trcmode>],[<tacc>],[<upsrpthstate>],[<c2>],[<blsrpthstate>]:[<pst>],[<sst>]
<aid>::[<level>],[<sfber>],[<sdber>],[<rvrtv>],[<rvtm>],[<swpdip>],[<holdofftimer>],[<exptrc>],[<trc>],[<inctrc>],[<trcmode>],[<tacc>],[<taptype>],[<upsrpthstate>],[<c2>],[<blsrpthstate>]:[<pst>],[<sst>]
RTRV-T1 response changes:
<aid>::[<linecde>],[<fmt>],[<lbo>],[<tacc>],[<soak>],[<soakleft>],[<sfber>],[<sdber>]:<pst>,[<sst>]
<aid>::[<linecde>],[<fmt>],[<lbo>],[<tacc>],[<taptype>],[<soak>],[<soakleft>],[<sfber>],[<sdber>]:<pst>,[<sst>]
RTRV-T3 response changes:
<aid>::[<fmt>],[<linecde>],[<lbo>],[<tacc>],[<soak>],[<soakleft>],[<sfber>],[<sdber>]:<pst>,[<sst>]
<aid>::[<fmt>],[<linecde>],[<lbo>],[<inhfelpbk>],[<tacc>],[<taptype>],[<soak>],[<soakleft>],[<sfber>],[<sdber>]:<pst>,[<sst>]
RTRV-TRC-CLNT response changes:
<aid>,<aidtype>::[<trclevel>],[<exptrc>],[<trc>],[<inctrc>],[<trcmode>],[<trcformat>]
[<trclevel>],[<exptrc>],[<trc>],[<inctrc>],[<trcmode>],[<trcformat>]
RTRV-WLEN response changes:
<aid>::[<size>]:[<pst>],[<sst>]
<aid>::[<mode>],[<size>]:[<pst>],[<sst>]
SET-TOD syntax changed:
SET-TOD[:<TID>]::<CTAG>::<year>,<month>,<day>,<hour>,<minute>,<second>,[<difference>][:DST=<dst>];
SET-TOD[:<TID>]::<CTAG>;
Related Documentation
Release-Specific Documents
•
•
•
•
Platform-Specific Documents
•
•
•
•
•
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
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, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com
Cisco.com 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.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, 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 Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
•
•
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
Contacting TAC by Telephone
If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
•
•
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0304R)
Copyright © 2007, Cisco Systems, Inc.
All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)