- About this Manual
- Chapter 1, Shelf and Backplane Hardware
- Chapter 2, Common Control Cards
- Chapter 3, Electrical Cards
- Chapter 4, Optical Cards
- Chapter 5, Ethernet Cards
- Chapter 6, Storage Access Networking Cards
- Chapter 7, Card Protection
- Chapter 8, Cisco Transport Controller Operation
- Chapter 9, Security
- Chapter 10, Timing
- Chapter 11, Circuits and Tunnels
- Chapter 12, SONET Topologies and Upgrades
- Chapter 13, Management Network Connectivity
- Chapter 14, Alarm Monitoring and Management
- Chapter 15, Performance Monitoring
- Chapter 16, SNMP
- Appendix A, Hardware Specifications
- Appendix B, Administrative and Service States
- Appendix C, Network Element Defaults
- 8.1 CTC Software Delivery Methods
- 8.2 CTC Installation Overview
- 8.3 PC and UNIX Workstation Requirements
- 8.4 ONS 15454 Connection
- 8.5 CTC Login
- 8.6 CTC Window
- 8.7 Using the CTC Launcher Application to Manage Multiple ONS Nodes
- 8.8 TCC2/TCC2P Card Reset
- 8.9 TCC2/TCC2P Card Database
- 8.10 Software Revert
Cisco Transport Controller Operation
This chapter describes Cisco Transport Controller (CTC), the software interface for the Cisco ONS 15454. For CTC set up and login information, refer to the Cisco ONS 15454 Procedure Guide.
Chapter topics include:
•
CTC Software Delivery Methods
•PC and UNIX Workstation Requirements
•Using the CTC Launcher Application to Manage Multiple ONS Nodes
8.1 CTC Software Delivery Methods
ONS 15454 provisioning and administration is performed using the CTC software. CTC is a Java application that is installed in two locations; CTC is stored on the Advanced Timing, Communications, and Control (TCC2) card or the Advanced Timing, Communications, and Control Plus (TCC2P) card, and it is downloaded to your workstation the first time you log into the ONS 15454 with a new software release.
8.1.1 CTC Software Installed on the TCC2/TCC2P Card
CTC software is preloaded on the ONS 15454 TCC2/TCC2P cards; therefore, you do not need to install software on the TCC2/TCC2P cards. When a new CTC software version is released, use the release-specific software upgrade document to upgrade the ONS 15454 software on the TCC2/TCC2P cards.
When you upgrade CTC software, the TCC2/TCC2P cards store the new CTC version as the protect CTC version. When you activate the new CTC software, the TCC2/TCC2P cards store the older CTC version as the protect CTC version, and the newer CTC release becomes the working version. You can view the software versions that are installed on an ONS 15454 by selecting the Maintenance > Software tabs in node view (Figure 8-1).
Figure 8-1 CTC Software Versions, Node View
Select the Maintenance > Software tabs in network view to display the software versions installed on all the network nodes (Figure 8-2).
Figure 8-2 CTC Software Versions, Network View
8.1.2 CTC Software Installed on the PC or UNIX Workstation
CTC software is downloaded from the TCC2/TCC2P cards and installed on your computer automatically after you connect to the ONS 15454 with a new software release for the first time. Downloading the CTC software files automatically ensures that your computer is running the same CTC software version as the TCC2/TCC2P cards you are accessing. The CTC files are stored in the temporary directory designated by your computer operating system. You can use the Delete CTC Cache button to remove files stored in the temporary directory. If the files are deleted, they download the next time you connect to an ONS 15454. Downloading the Java archive (JAR) files for CTC takes several minutes depending on the bandwidth of the connection between your workstation and the ONS 15454. For example, JAR files downloaded from a modem or a data communications channel (DCC) network link require more time than JAR files downloaded over a LAN connection.
During network topology discovery, CTC polls each node in the network to determine which one contains the most recent version of the CTC software. If CTC discovers a node in the network that has a more recent version of the CTC software than the version you are currently running, CTC generates a message stating that a later version of the CTC has been found in the network and offers to install the CTC software upgrade JAR files. If you have network discovery disabled, CTC will not seek more recent versions of the software. Unreachable nodes are not included in the upgrade discovery.
Note Upgrading the CTC software will overwrite your existing software. You must restart CTC after the upgrade is complete.
8.2 CTC Installation Overview
To connect to an ONS 15454 using CTC, you enter the ONS 15454 IP address in the URL field of Netscape Navigator or Microsoft Internet Explorer. After connecting to an ONS 15454, the following occurs automatically:
1. A CTC launcher applet is downloaded from the TCC2/TCC2P card to your computer.
2. The launcher determines whether your computer has a CTC release matching the release on the ONS 15454 TCC2/TCC2P card.
3. If the computer does not have CTC installed, or if the installed release is older than the TCC2/TCC2P card's version, the launcher downloads the CTC program files from the TCC2/TCC2P card.
4. The launcher starts CTC. The CTC session is separate from the web browser session, so the web browser is no longer needed. Always log into nodes having the latest software release. If you log into an ONS 15454 that is connected to ONS 15454s with older versions of CTC, or to Cisco ONS 15327s or Cisco ONS 15600s, CTC files are downloaded automatically to enable you to interact with those nodes. The CTC file download occurs only when necessary, such as during your first login. You cannot interact with nodes on the network that have a software version later than the node that you used to launch CTC.
Each ONS 15454 can handle up to five concurrent CTC sessions. CTC performance can vary, depending on the volume of activity in each session, network bandwidth, and TCC2/TCC2P card load.
Note You can also use TL1 commands to communicate with the Cisco ONS 15454 through VT100 terminals and VT100 emulation software, or you can telnet to an ONS 15454 using TL1 port 3083. Refer to the Cisco ONS SONET TL1 Command Guide for a comprehensive list of TL1 commands.
8.3 PC and UNIX Workstation Requirements
To use CTC for the ONS 15454, your computer must have a web browser with the correct Java Runtime Environment (JRE) installed. The correct JRE for each CTC software release is included on the Cisco ONS 15454 software CD. If you are running multiple CTC software releases on a network, the JRE installed on the computer must be compatible with the different software releases.
You can change the JRE version on the Preferences dialog box JRE tab. When you change the JRE version on the JRE tab, you must exit and restart CTC for the new JRE version to take effect. Table 8-1 shows JRE compatibility with ONS 15454 software releases.
|
|
|
|
|
|
|---|---|---|---|---|
ONS 15454 Release 2.2.1 and earlier |
Yes |
No |
No |
No |
ONS 15454 Release 2.2.2 |
Yes |
Yes |
No |
No |
ONS 15454 Release 3.0 |
Yes |
Yes |
No |
No |
ONS 15454 Release 3.1 |
Yes |
Yes |
No |
No |
ONS 15454 Release 3.2 |
Yes |
Yes |
No |
No |
ONS 15454 Release 3.3 |
Yes |
Yes |
No |
No |
ONS 15454 Release 3.4 |
No |
Yes |
No |
No |
ONS 15454 Release 4.0 1 |
No |
Yes |
No |
No |
ONS 15454 Release 4.1 |
No |
Yes |
No |
No |
ONS 15454 Release 4.5 |
No |
Yes |
No |
No |
ONS 15454 Release 4.6 |
No |
Yes |
Yes |
No |
ONS 15454 Release 5.0 |
No |
No |
Yes |
No |
ONS 15454 Release 6.0 |
No |
No |
Yes |
No |
ONS 15454 Release 7.0 |
No |
No |
Yes |
Yes |
ONS 15454 Release 7.2 |
No |
No |
Yes |
Yes |
ONS 15454 Release 8.0 |
No |
No |
No |
Yes |
1 Software Releases 4.0 and later notify you if an older version of the JRE is running on your PC or UNIX workstation. |
Note To avoid network performance issues, Cisco recommends managing a maximum of 50 nodes concurrently with CTC. The 50 nodes can be on a single DCC or split across multiple DCCs. Cisco does not recommend running multiple CTC sessions when managing two or more large networks.
To manage more than 50 nodes, Cisco recommends using Cisco Transport Manager (CTM). If you do use CTC to manage more than 50 nodes, you can improve performance by adjusting the heap size; see the "General Troubleshooting" chapter of the Cisco ONS 15454 Troubleshooting Guide. You can also create login node groups; see the "Connect the PC and Log Into the GUI" chapter of the Cisco ONS 15454 Procedure Guide.
Table 8-2 lists the requirements for PCs and UNIX workstations. In addition to the JRE, the Java plug-in is included on the ONS 15454 software CD.
8.4 ONS 15454 Connection
You can connect to the ONS 15454 in multiple ways. You can connect your PC directly the ONS 15454 (local craft connection) using the RJ-45 port on the TCC2/TCC2P card or the LAN pins on the backplane, connect your PC to a hub or switch that is connected to the ONS 15454, connect to the ONS 15454 through a LAN or modem, or establish TL1 connections from a PC or TL1 terminal. Table 8-3 lists the ONS 15454 connection methods and requirements.
8.5 CTC Login
After you have installed CTC, you can log in to a node using your browser. To log in, you must type the node IP address in the URL window. The CTC Login window appears.
The CTC Login window provides the following options to accelerate the login process.
•The Disable Network Discovery option omits the discovery of nodes with data communications channel (DCC) connectivity. To access all nodes with DCC connectivity, make sure that Disable Network Discovery is not checked. If you have network discovery disabled, CTC will not poll the network for more recent versions of the software. (For more information about the automatic download of the latest CTC JAR files, see the "CTC Software Installed on the PC or UNIX Workstation" section.)
•The Disable Circuit Management option omits the discovery of circuits. To view circuits immediately after logging in, make sure that Disable Circuit Management is not checked. However, if disabled, after you have logged in you can click the Circuits tab and CTC will give you the option to enable circuit management.
These options are useful if you want to log in to a node to perform a single task, such as placing a card in or out of service, and do not want to wait while CTC discovers DCC connections and circuits.
8.5.1 Legal Disclaimer
The CTC Login window currently displays the following warning message: "Warning: This system is restricted to authorized users for business purpose. Unauthorized access is a violation of the law. This service can be monitored for administrative and security reasons. By proceeding, you consent to this monitoring."
The ONS 15600 allows a user with Superuser privileges to modify the default login warning message and save it to a node using the Provisioning > Security > Legal Disclaimer > HTML tab. The login warning message field allows up to 250 characters of text (1600 characters total, including HTML markup).
8.5.2 Login Node Group
Login node groups display nodes that have only an IP connection. After you are logged into CTC, you can create a login node group from the Edit > Preferences menu. Login groups appear in the Additional Nodes list on the Login window.
For example, if you logged into Node 1, you would see Node 2 and Node 3 because they have DCC connectivity to Node 1. You would not see Nodes 4, 5, and 6 because DCC connections do not exist. To view all six nodes at once, you create a login node group with the IP addresses of Nodes 1, 4, 5, and 6. Those nodes, and all nodes optically connected to them, appear when you select the login group from the Additional Nodes list on the Login window the next time you log in.
8.6 CTC Window
The CTC window appears after you log into an ONS 15454 (Figure 8-3). The window includes a menu bar, a toolbar, and a top and bottom pane. The top pane provides status information about the selected objects and a graphic of the current view. The bottom pane provides tabs and subtab to view ONS 15454 information and perform ONS 15454 provisioning and maintenance. From this window you can display three ONS 15454 views: network, node, and card.
Figure 8-3 Node View (Default Login View)
8.6.1 Node View
Node view, shown in Figure 8-3, is the first view that appears after you log into an ONS 15454. The login node is the first node shown, and it is the "home view" for the session. Node view allows you to manage one ONS 15454 node. The status area shows the node name; IP address; session boot date and time; number of Critical (CR), Major (MJ), and Minor (MN) alarms; the name of the current logged-in user; and the security level of the user; software version; and the network element default setup.
8.6.1.1 CTC Card Colors
The graphic area of the CTC window depicts the ONS 15454 shelf assembly. The colors of the cards in the graphic reflect the real-time status of the physical card and slot (Table 8-4).
The wording on a card in node view shows the status of a card (Active, Standby, Loading, or Not Provisioned). Table 8-5 lists the card statuses.
|
|
|
Sby |
Card is in standby mode. |
Act |
Card is active. |
NP |
Card is not present. |
Ldg |
Card is resetting. |
Mis |
Card is mismatched. |
The port color in both card and node view indicates the port service state. Table 8-6 lists the port colors and their service states. For more information about port service states, see "Administrative and Service States."
|
|
|
|
|---|---|---|
Blue |
OOS-MA,LPBK |
(Out-of-Service and Management, Loopback) Port is in a loopback state. On the card in node view, a line between ports indicates that the port is in terminal or facility loopback (see Figure 8-4 and Figure 8-5). Traffic is carried and alarm reporting is suppressed. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. |
Blue |
OOS-MA,MT |
(Out-of-Service and Management, Maintenance) Port is out-of-service for maintenance. Traffic is carried and loopbacks are allowed. Alarm reporting is suppressed. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. Use OOS-MA,MT for testing or to suppress alarms temporarily. Change the state to IS-NR, OOS-MA,DSBLD, or OOS-AU,AINS when testing is complete. |
Gray |
OOS-MA,DSBLD |
(Out-of-Service and Management, Disabled) The port is out-of-service and unable to carry traffic. Loopbacks are not allowed in this service state. |
Green |
IS-NR |
(In-Service and Normal) The port is fully operational and performing as provisioned. The port transmits a signal and displays alarms; loopbacks are not allowed. |
Violet |
OOS-AU,AINS |
(Out-of-Service and Autonomous, Automatic In-Service) The port is out-of-service, but traffic is carried. Alarm reporting is suppressed. The node monitors the ports for an error-free signal. After an error-free signal is detected, the port stays in OOS-AU,AINS state for the duration of the soak period. After the soak period ends, the port service state changes to IS-NR. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. The AINS port will automatically transition to IS-NR when a signal is received for the length of time provisioned in the soak field. |
Figure 8-4 Terminal Loopback Indicator
Figure 8-5 Facility Loopback Indicator
8.6.1.2 Node View Card Shortcuts
If you move your mouse over cards in the graphic, popups display additional information about the card including the card type; the card status (active or standby); the type of alarm, such as Critical, Major, or Minor (if any); and the alarm profile used by the card. Right-click a card to reveal a shortcut menu, which you can use to open, reset, delete, or change a card. Right-click a slot to preprovision a card (that is, provision a slot before installing the card).
8.6.1.3 Node View Tabs
Table 8-7 lists the tabs and subtabs available in the node view.
|
|
|
|
|---|---|---|
Alarms |
Lists current alarms (CR, MJ, MN) for the node and updates them in real time. |
— |
Conditions |
Displays a list of standing conditions on the node. |
— |
History |
Provides a history of node alarms including date, type, and severity of each alarm. The Session subtab displays alarms and events for the current session. The Node subtab displays alarms and events retrieved from a fixed-size log on the node. |
Session, Shelf |
Circuits |
Creates, deletes, edits, and maps circuits and rolls. |
Circuits, Rolls |
Provisioning |
Provisions the ONS 15454 node. |
General, Ether Bridge, Network, OSI, BLSR, Protection, Security, SNMP, Comm Channels, Timing, Alarm Profiles, Cross-Connect, Defaults, WDM-ANS |
Inventory |
Provides inventory information (part number, serial number, Common Language Equipment Identification [CLEI] codes) for cards installed in the node. Allows you to delete and reset cards, and change card service state. For more information on card service states, see "Administrative and Service States." |
— |
Maintenance |
Performs maintenance tasks for the node. |
Database, Ether Bridge, Network, OSI, BLSR, Protection, Software, Cross-Connect, Overhead XConnect, Diagnostic, Timing, Audit, Test Access, DWDM |
8.6.2 Network View
Network view allows you to view and manage ONS 15454s that have DCC connections to the node that you logged into and any login node groups you have selected (Figure 8-6).
Figure 8-6 Network in CTC Network View
Note Nodes with DCC connections to the login node do not appear if you checked the Disable Network Discovery check box in the Login dialog box.
The graphic area displays a background image with colored ONS 15454 icons. A Superuser can set up the logical network view feature, which enables each user to see the same network view. Selecting a node or span in the graphic area displays information about the node and span in the status area.
8.6.2.1 Network View Tabs
Table 8-8 lists the tabs and subtabs available in network view.
8.6.2.2 CTC Node Colors
The color of a node in network view, shown in Table 8-9, indicates the node alarm status.
8.6.2.3 DCC Links
The lines show DCC connections between the nodes (Table 8-10). DCC connections can be green (active) or gray (fail). The lines can also be solid (circuits can be routed through this link) or dashed (circuits cannot be routed through this link). Circuit provisioning uses active/routable links.
8.6.2.4 Link Consolidation
CTC provides the ability to consolidate the DCC, general communications channel (GCC), optical transport section (OTS), provisionable patchcord (PPC), and server trail links shown in the network view. Link consolidation allows you to condense multiple inter-nodal links into a single link. The link consolidation sorts links by class; for example, all DCC links are consolidated together.You can access individual links within consolidated links using the right-click shortcut menu.
Each link has an associated icon (Table 8-11).
|
|
|
|---|---|
|
DCC icon |
|
GCC icon |
|
OTS icon |
|
PPC icon |
|
Server Trail icon |
Note Link consolidation is only available on non-detailed maps. Non-detailed maps display nodes in icon form instead of detailed form, meaning the nodes appear as rectangles with ports on the sides. Refer to the Cisco ONS 15454 Procedure Guide for more information about consolidated links.
8.6.3 Card View
The card view provides information about individual ONS 15454 cards. Use this window to perform card-specific maintenance and provisioning (Figure 8-7). A graphic showing the ports on the card is shown in the graphic area. The status area displays the node name, slot, number of alarms, card type, equipment type, and the card status (active or standby), card service state if the card is present, and port service state (described in Table 8-6). The information that appears and the actions you can perform depend on the card. For more information about card service states, see "Administrative and Service States."
Figure 8-7 CTC Card View Showing a DS1 Card
Note CTC provides a card view for all ONS 15454 cards except the TCC2, TCC2P, XCVT, XC10G, and XC-VXC-10G cards. Provisioning for these common control cards occurs at the node view; therefore, no card view is necessary.
Use the card view tabs and subtabs shown in Table 8-12 to provision and manage the ONS 15454. The subtabs, fields, and information shown under each tab depend on the card type selected. The Performance tab is not available for the Alarm Interface Controller-International (AIC-I) cards.
8.6.4 Print or Export CTC Data
You can use the File > Print or File > Export options to print or export CTC provisioning information for record keeping or troubleshooting. The functions can be performed in card, node, or network views. The File > Print function sends the data to a local or network printer. File > Export exports the data to a file where it can be imported into other computer applications, such as spreadsheets and database management programs.
Whether you choose to print or export data, you can choose from the following options:
•Entire frame—Prints or exports the entire CTC window including the graphical view of the card, node, or network. This option is available for all windows.
•Tabbed view—Prints or exports the lower half of the CTC window containing tabs and data. The printout includes the selected tab (on top) and the data shown in the tab window. For example, if you print the History window Tabbed view, you print only history items appearing in the window. This option is available for all windows.
•Table Contents—Prints or exports CTC data in table format without graphical representations of shelves, cards, or tabs. The Table Contents option prints all the data contained in a table with the same column headings. For example, if you print the History window Table Contents view, you print all data included in the table whether or not items appear in the window.
The Table Contents option does not apply to all windows; for a list of windows that do not support print or export, see the Cisco ONS 15454 Procedure Guide.
8.7 Using the CTC Launcher Application to Manage Multiple ONS Nodes
The CTC Launcher application is an executable file, StartCTC.exe, that is provided on Software Release 8.0 CDs for Cisco ONS products. You can use CTC Launcher to log into multiple ONS nodes that are running CTC Software Release 3.3 or higher, without using a web browser.
CTC Launcher provides two connection options. The first option is used to connect to ONS network elements (NEs) that have an IP connection to the CTC computer. The second option is used to connect to ONS NEs that reside behind third party, OSI-based gateway network elements (GNEs). For this option, CTC Launcher creates a TL1 tunnel to transport the TCP traffic through the OSI-based GNE.
The TL1 tunnel transports the TCP traffic to and from ONS ENEs through the OSI-based GNE. TL1 tunnels are similar to the existing static IP-over-CLNS tunnels, GRE and Cisco IP, that can be created at ONS NEs using CTC. (Refer to the Cisco ONS product documentation for information about static IP-over-CLNS tunnels.) However, unlike the static IP-over-CLNS tunnels, TL1 tunnels require no provisioning at the ONS ENE, the third-party GNE, or DCN routers. All provisioning occurs at the CTC computer when the CTC Launcher is started.
Figure 8-8 shows examples of two static IP-over-CLNS tunnels. A static Cisco IP tunnel is created from ENE 1 through other vendor GNE 1 to a DCN router, and a static GRE tunnel is created from ONS ENE 2 to the other vender, GNE 2. For both static tunnels, provisioning is required on the ONS ENEs. In addition, a Cisco IP tunnel must be provisioned on the DCN router and a GRE tunnel provisioned on GNE 2.
Figure 8-8 Static IP-Over-CLNS Tunnels
Figure 8-9 shows the same network using TL1 tunnels. Tunnel provisioning occurs at the CTC computer when the tunnel is created with the CTC Launcher. No provisioning is needed at ONS NEs, GNEs or routers.
Figure 8-9 TL1 Tunnels
TL1 tunnels provide several advantages over static IP-over-CLNS tunnels. Because tunnel provisioning is needed only at the CTC computer, they are faster to set up. Because they use TL1 for TCP transport, they are more secure. TL1 tunnels also provide better flow control. On the other hand, IP over CLNS tunnels require less overhead and usually provide a slight performance edge over TL1 Tunnels (depending on network conditions). TL1 tunnels do not support all IP applications such as SNMP and RADIUS Authentication. Table 8-13 shows a comparison between the two types of tunnels.
TL1 tunnel specifications and general capabilities include:
•Each tunnel generally supports between six to eight ENEs, depending on the number of tunnels at the ENE.
•Each CTC session can support up to 32 tunnels.
•The TL1 tunnel database is stored locally in the CTC Preferences file.
•Automatic tunnel reconnection when the tunnel goes down.
•Each ONS NE can support at least 16 concurrent tunnels.
8.8 TCC2/TCC2P Card Reset
You can reset the ONS 15454 TCC2/TCC2P card by using CTC (a soft reset) or by physically reseating a TCC2/TCC2P card (a hard reset). A soft reset reboots the TCC2/TCC2P card and reloads the operating system and the application software. Additionally, a hard reset temporarily removes power from the TCC2/TCC2P card and clears all buffer memory.
You can apply a soft reset from CTC to either an active or standby TCC2/TCC2P card without affecting traffic. If you need to perform a hard reset on an active TCC2/TCC2P card, put the TCC2/TCC2P card into standby mode first by performing a soft reset.
Note When a CTC reset is performed on an active TCC2/TCC2P card, the AIC-I cards go through an initialization process and also reset because AIC-I cards are controlled by the active TCC2/TCC2P.
8.9 TCC2/TCC2P Card Database
When dual TCC2/TCC2P cards are installed in the ONS 15454, each TCC2/TCC2P card hosts a separate database; therefore, the protect card database is available if the database on the working TCC2/TCC2P fails. You can also store a backup version of the database on the workstation running CTC. This operation should be part of a regular ONS 15454 maintenance program at approximately weekly intervals, and should also be completed when preparing an ONS 15454 for a pending natural disaster, such as a flood or fire.
A database backup may be restored in two ways, partial or complete. A partial database restore operation restores only the provisioning data. A complete database restore operation restores both system and provisioning data. For more information on restoring a database, refer to the Cisco ONS 15454 Procedure Guide.
Note The following parameters are not backed up and restored: node name, IP address, mask and gateway, and Internet Inter-ORB Protocol (IIOP) port. If you change the node name and then restore a backed up database with a different node name, the circuits map to the new node name. Cisco recommends keeping a record of the old and new node names.
Note To avoid a node IP and secure IP ending up in the same domain after restoring a database, ensure that the node IP stored in the database differs in domain from that of the node in repeater mode. Also, after restoring a database, ensure that the node IP and secure IP differ in domain.
8.10 Software Revert
When you click the Activate button after a software upgrade, the TCC2/TCC2P copies the current working database and saves it in a reserved location in the TCC2/TCC2P flash memory. If you later need to revert to the original working software load from the protect software load, the saved database installs automatically. You do not need to restore the database manually or recreate circuits.
Note The TCC2/TCC2P card does not carry any software earlier than Software R4.0. You will not be able to revert to a software release earlier than Software R4.0 with TCC2/TCC2P cards installed.
The revert feature is useful if a maintenance window closes while you are upgrading CTC software. You can revert to the protect software load without losing traffic. When the next maintenance window opens, complete the upgrade and activate the new software load.
Circuits created and provisioning done after a software load is activated (upgraded to a higher software release) will be lost with a revert. The database configuration at the time of activation is reinstated after a revert. This does not apply to maintenance reverts (for example, 4.6.2 to 4.6.1), because maintenance releases use the same database.
To perform a supported (non-service-affecting) revert from Software R8.0, the release you want to revert to must have been working at the time you first activated Software R8.0 on that node. Because a supported revert automatically restores the node configuration at the time of the previous activation, any configuration changes made after activation will be lost when you revert the software. Downloading Release 8.0 a second time after you have activated the new load ensures that no actual revert to a previous load can take place (the TCC2/TCC2P card will reset, but will not be traffic affecting and will not change your database).
Feedback