Table Of Contents
Maintaining an Efficient Network
4.1 Overview
4.2 How Do I Manage the Database?
4.2.1 Viewing and Modifying Database Properties
4.2.2 Pruning the Database
4.2.3 Using the SQL*PLUS Client to Manage the Database
4.2.4 Understanding Basic SQL Commands for CTM Schema Objects
4.3 How Do I Manage the Network Software?
4.3.1 Managing Binaries Using the CTC Upgrade Table
4.3.2 Downloading Software Images
4.3.3 Using the Flash File Table
4.3.4 Viewing Software Versions and Restarting the NE with a New Software Image
4.3.5 Uploading Software Images
4.3.6 Adding a New NE Software Version to the CTM Domain
4.3.7 Deleting an NE Software Version from the CTM Domain
4.4 How Do I Modify the Network?
4.4.1 Changing IP Addresses for NEs
4.4.2 Updating the Configuration Files After Changing the CTM Server IP Address
4.4.3 Changing the Internal Subnet Address—ONS 15600
4.4.4 Viewing and Changing the Network Address—CTC-Based NEs
4.4.5 Configuring Proxy Server Settings—CTC-Based NEs
4.4.6 Changing the Operational State of an NE
4.4.7 Setting Date, Time, and Location on CTC-Based NEs
4.4.8 Configuring SNTP for Multiple NEs
4.4.9 Configuring Application-Specific Parameters
4.5 How Do I Manage Redundancy and Failover?
4.5.1 Backing Up Memory
4.5.2 Restoring Memory
4.5.3 Viewing and Modifying NE Service Properties
4.5.4 Restoring Server Configuration Files
4.5.5 Configuring Nodes for Database Restore—ONS 15600
4.5.6 Comparing Configuration Files—CRS-1
4.5.7 Managing Protection Groups
4.5.8 Restoring NE Defaults
4.6 How Do I Monitor the Network?
4.6.1 Monitoring Scheduled Tasks
4.6.2 Monitoring Service Status
4.6.3 Viewing the NE Discrepancy Table
4.6.4 Monitoring CTM Client and Server Configuration Details
4.6.5 Viewing the CTM Server and Client Version
4.7 How Do I Manage CTC Operations?
4.7.1 Functionality Provided in CTC that Is Not Available in CTM
4.7.2 Specifying CTC Partitions for CTC-Based NEs
Maintaining an Efficient Network
This chapter contains the following information to help you maintain an efficient network:
•
Overview
•How Do I Manage the Database?
•How Do I Manage the Network Software?
•How Do I Modify the Network?
•How Do I Manage Redundancy and Failover?
•How Do I Monitor the Network?
•How Do I Manage CTC Operations?
Note For information about configuring users and user-related parameters, creating and modifying advisory messages, and accessing logs, see Chapter 8, "Managing Security."
4.1 Overview
Maintaining your network focuses on tasks that will keep your network running smoothly. Examples include:
•Backing up and restoring memory and the database
•Creating and maintaining protection groups
•Restoring default settings when necessary
•Monitoring tasks and jobs
•Modifying basic server and NE information
•Finding modules or boards
•Updating software images and versions
•Exporting data and generating reports
•Performing administrative database operations
4.2 How Do I Manage the Database?
This section describes procedures for managing the Oracle database and deals specifically with CTM data stored in the database. For a complete description, refer to the Oracle documentation.
This section contains the following information:
•Viewing and Modifying Database Properties
•Pruning the Database
•Using the SQL*PLUS Client to Manage the Database
•Understanding Basic SQL Commands for CTM Schema Objects
4.2.1 Viewing and Modifying Database Properties
The Database Properties pane in the Control Panel shows and defines database pruning parameters and configuration that the CTM server uses to connect to the Oracle database. It contains the following tabs:
•Configuration—Defines the values used by the CTM server to log into the Oracle database. Fields are grouped into two columns: After Restart and Active. The After Restart column shows the values that the CTM server uses after the server is restarted. The Active column displays the values currently used by the CTM server.
•Pruning—Defines the CTM database pruning frequency. You can configure the performance monitoring (PM) pruning interval for 15-minute and 1-day data collection, giving you a finer level of control over the pruning of performance data from the system. Pruning frequency changes take effect as soon as you save them. You do not need to reboot the CTM server.
•Database Backup—Allows you to start a database backup from the Control Panel. After entering the password, click Start to begin the database backup. This tab is disabled if the database is not installed in ARCHIVELOG mode. The ARCHIVELOG mode is stored in the CTM_config_table by the server installer.
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 Click Database Properties to open the Database Properties pane. Table 4-1 provides descriptions.
Step 3 (Optional) Modify the values in the Configuration, Pruning, or Database Backup tab.
Note Fields in the Database Backup tab are disabled if the database is not installed with the ARCHIVELOG mode option set to true (see the Configuration tab for details).
Step 4 Click Save.
Table 4-1 Field Descriptions for the Database Properties Pane
Field
|
Description
|
Configuration Tab
|
Database Server Configuration
|
(Read-only) Displays the size of the database server.
|
Server Installed in ARCHIVELOG
|
(Read-only) If the value is true, CTM supports automatic pruning of the /db05 partition when the database is in ARCHIVELOG mode. If the value is false, the database is not installed with the ARCHIVELOG mode option.
|
Configuration Mode
|
Configuration Mode tells the CTM server the values to use to log into the Oracle database. When set to Auto, the CTM server uses the configuration that was set when CTM was installed. When set to Manual, the After Restart fields can be edited, and the CTM server will use the edited values when the server is rebooted.
Note If you change the configuration mode to Manual, enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables before logging into CTM again:
setenv ORACLE_HOME <Oracle_home_directory>
setenv ORACLE_SID CTM5_0
setenv LD_LIBRARY_PATH $ORACLE_HOME/lib
setenv PATH $PATH:$ORACLE_HOME/bin
Restart the CTM server after setting these environment variables.
Caution If you set the configuration mode to Auto and restart the CTM server, the CTMServer.cfg file is overwritten with the default values for username, password, location, port, system ID, and SQL network alias.
|
Username
|
Displays the username that the CTM server uses to access the Oracle database.
|
Password
|
Displays the password that gives the username access to the Oracle database.
|
Location
|
Displays the IP address that the CTM server uses to connect to the database.
|
Port
|
Displays the port number that is used to connect to the database.
|
System ID
|
Displays the Oracle system ID. The ORACLE_SID specifies the system identifier (SID) value of the database instance that you create with the CTM installer. For a single-instance database, the SID value should be the same as the name of the database it manipulates (initialization parameter DB_NAME), and no more than four characters.
Note During CTM installation, the default system ID is CTM5_0.
|
SQL Network Alias
|
Displays the SQL*Net listener alias set in the system listener.ora file. When the listener is running, entering the ps command displays the following output (not all systems display listener_alias):
tnslsnr [listener_alias] [-inherit]
Shadow processes (dedicated servers) spawned by the SQL*Net listener have the following syntax: oracleSID [(LOCAL=NO)]
|
Pruning Tab
|
PM Data (15 min)
|
Specifies the number of days to save 15-minute PM data before CTM runs the database pruning script. You can save from 1 to 1000 days of data. The default value is 7. You can also specify the time of day when the PM data will be saved by choosing the hour and minute from the Hour, Minutes, and AM/PM fields. Minutes are listed in 5-minute intervals. Check the Enable check box to activate the PM data pruning.
|
PM Data (1 day)
|
Specifies the number of days to save 1-day PM data before CTM runs the database pruning script. You can save from 1 to 1000 days of data. The default value is 7. You can also specify the time of day when the PM data will be saved by choosing the hour and minute from the Hour, Minutes, and AM/PM fields. Minutes are listed in 5-minute intervals. Check the Enable check box to activate the PM data pruning.
|
FM Data
|
Specifies the number of days to save fault management (FM) data before CTM runs the database pruning script. You can save from 1 to 1000 days of data. The default value is 7. You can also specify the time of day when the FM data will be saved by choosing the hour and minute from the Hour, Minutes, and AM/PM fields. Minutes are listed in 5-minute intervals. Check the Enable check box to activate the FM data pruning.
|
Audit Log Data
|
Specifies the number of days to save audit log data before CTM runs the database pruning script. You can save from 1 to 1000 days of data. The default value is 7. You can also specify the time of day when the audit log data will be saved by choosing the hour and minute from the Hour, Minutes, and AM/PM fields. Minutes are listed in 5-minute intervals. Check the Enable check box to activate the audit log data pruning.
|
Error Log Data
|
Specifies the number of days to save error log data before CTM runs the database pruning script. You can save from 1 to 1000 days of data. The default value is 7. You can also specify the time of day when the error log data will be saved by choosing the hour and minute from the Hour, Minutes, and AM/PM fields. Minutes are listed in 5-minute intervals. Check the Enable check box to activate the error log data pruning.
|
Audit Trail Data (for CTC-based NEs)
|
Specifies the number of days to save audit trail data before CTM runs the database pruning script. You can save from 1 to 1000 days of data. The default value is 7. You can also specify the time of day when the audit trail data will be saved by choosing the hour and minute from the Hour, Minutes, and AM/PM fields. Minutes are listed in 5-minute intervals. Check the Enable check box to activate the audit trail data pruning.
|
Self Monitor Data
|
Specifies the number of days to save self-monitoring data before CTM runs the database pruning script. You can save from 1 to 1000 days of data. The default value is 7. You can also specify the time of day when the self-monitoring data will be saved by choosing the hour and minute from the Hour, Minutes, and AM/PM fields. Minutes are listed in 5-minute intervals. Check the Enable check box to activate the self-monitoring data pruning.
|
Job Monitor Data
|
Specifies the number of days to save job monitoring data before CTM runs the database pruning script. You can save from 1 to 1000 days of data. The default value is 7. You can also specify the time of day when the job monitoring data will be saved by choosing the hour and minute from the Hour, Minutes, and AM/PM fields. Minutes are listed in 5-minute intervals. Check the Enable check box to activate the job monitoring data pruning.
|
Database Backup Tab
|
Password
|
The password for the system user.
|
Backup Status
|
The status of the database backup.
|
Archive Log Pruning Parameters
|
Displays the archive log pruning parameters.
|
4.2.2 Pruning the Database
This section describes how to set the time and date for automatic database pruning and how to use pruning scripts.
4.2.2.1 Setting the Time and Date for Automatic Pruning
Choosing to prune the database automatically prunes daily all PM data, FM data, audit log data, error log data, and audit trail data older than the specified retention period.
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 In the Control Panel window, click Database Properties.
Step 3 In the Database Properties pane, click the Pruning tab.
Step 4 Check the Enable check box for each field as desired, and set the number of days and time of pruning.
Step 5 After making the selections, click Save. Changes take effect immediately.
4.2.2.2 Using Pruning Scripts
Running database pruning scripts allows you to prune CTM data from the Oracle database at any given time. Pruning scripts allows you to prune the following types of data:
•Audit log data
•Audit trail data
•Error log data
•Event data
•All PM data
•NEs and all related information
•Server monitoring data
Note For information about pruning NEs in a high availability environment, refer to the Cisco Transport Manager High Availability Installation Guide.
Step 1 Log in as the root user on the Sun Solaris workstation where the CTM server is installed.
Step 2 Enter the following command to change to the CTM server bin directory:
cd /opt/CiscoTransportManagerServer/bin
Step 3 Enter the following command to see a list of pruning scripts:
Step 4 Select a script and a parameter (based on database pruning) and enter the corresponding command on the UNIX shell.
For example, to prune error log data older than 25 days, enter the following command:
Table 4-2 describes parameters that can be passed to the following scripts, and the tables that are affected:
•Prune audit log data
•Prune error log data
•Prune alarm and event data
•Prune audit trail data
•Prune admin job table data
•Prune server monitor table data
Table 4-2 Parameters for Database Pruning: Multiple Scripts
Tables Affected
|
Input Parameters
|
Remarks
|
Prune Audit Log Data Script (prune_auditlog.sh)
|
transaction_log_table
|
Number of days (1-31)
|
Removes all audit log entries that were created before n days.
|
Prune Error Log Data Script (prune_errlog.sh)
|
error_log_table
|
Number of days (1-31)
|
Removes all transaction log entries that were created before n days.
|
Prune Alarm and Event Data Script (prune_fm.sh)
|
alarm_event_table
|
Number of days (1-31)
|
Removes all alarm and event entries that were created before n days.
|
active_alarm_table
|
Prune Audit Trail Data Script (prune_audittrail.sh)
|
ne_audit_trail_table
|
Number of days (1-31)
|
Removes all NE audit trail entries that were created before n days.
|
Prune Admin Job Table Script (prune_admin_job_table.sh)
|
admin_job_table
|
Number of days (1-31)
|
Removes all admin job entries that were created before n days.
|
Prune Server Monitor Table Script (prune_server_monitor.sh)
|
server_monitor_table
|
Number of days (1-31)
|
Removes all server monitor entries that were created before n days.
|
Table 4-3 describes parameters that can be passed to the prune_pm.sh script, and the tables that are affected. The prune_PM.sh script removes all PM entries that were created before n days.
Note Based on the value of "Is 24 flag," CTM prunes 15-minute data, 1-day data, or both 15-minute and 1-day data. If the "Is 24 flag" value is blank, CTM prunes both 15-minute and 1-day data.
Table 4-3 Parameters for Database Pruning: Prune PM Data Script (prune_pm.sh)
Tables Affected
|
Input Parameters
|
ons15454_DS3_PM_table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454_SONET_PATH_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454_SONET_LINE_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454_SONET_SEC_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454_ENET_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454_DS1_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454_Sonet_VT_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454SDH_RS_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454SDH_MS_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454SDH_HO_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454SDH_LO_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454SDH_E1_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454SDH_E3_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454SDH_E4_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS155XX_SONET_SEC_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS155xx_Phy_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS155xx_Opt_Power_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15501_Opt_Power_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS155xx_CDL_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS155xx_Ether_Hist_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS155xx_FCM_PE_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_IOC_W_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_TRANSPONDER_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_LSM_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_SCF_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_AMPLIFIER_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_WD_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_OADM_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_WD_RX_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_OSU_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_BCS_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_OAD_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS158XX_CMP_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15600_Sonet_Sec_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15600_Sonet_Line_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15600_Sonet_Path_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454_PHY_LAYER_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454_POS_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454_OTN_SEC_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454_OTN_PATH_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15454_OTN_FEC_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15600SDH_RS_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15600SDH_MS_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS15600SDH_HO_PM_Table
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS1530x_RS_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS1530x_MS_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS1530x_HO_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS1530x_LO_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
ONS1530x_IP_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
HFR_INTERFACE_GC_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
HFR_INTERFACE_DRC_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
HFR_BGP_PEER_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
HFR_NODE_CPU_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
HFR_NODE_MEMORY_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
HFR_NODE_PROCESS_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
HFR_MPLS_TE_LINK_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
HFR_MPLS_TE_TUNNEL_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
HFR_MPLS_INTERFACE_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
HFR_MPLS_LDP_PM_TABLE
|
•Number of days (1-31)
•Is 24 flag (where 0 = 15 min, 1 = 1 day, and 2 = both 15 min and 1 day)
|
Table 4-4 describes parameters that can be passed to the prune_ne.sh script, and the tables that are affected. The prune_ne.sh script removes all information about the NE from the database. Use this script with extreme caution.
Caution Before running the script, shut down all CTM clients and the CTM server.
Table 4-4 Parameters for Database Pruning: Remove an NE Script (prune_ne.sh)
Tables Affected
|
Input Parameters
|
ACTIVE_ALARM_TABLE
|
NE SYS ID
|
ADDITIONAL_DEVICE_INFO
|
NE SYS ID
|
ADMIN_JOB_TABLE
|
NE SYS ID
|
ALARM_COUNT_TABLE
|
NE SYS ID
|
ALARM_EVENT_TABLE
|
NE SYS ID
|
APS_GROUP_TABLE
|
NE SYS ID
|
AUDIT_LOG_TABLE
|
NE SYS ID
|
CERENT_NE_GROUP_TABLE
|
NE SYS ID
|
CIRCUIT_DEST_TBL
|
NE SYS ID
|
CIRCUIT_SPAN_TBL
|
NE SYS ID
|
CIRCUIT_TBL
|
NE SYS ID
|
CIRCUIT_VCG_TBL
|
NE SYS ID
|
CIRCUIT_VLAN_TBL
|
NE SYS ID
|
DOMAIN_TABLE
|
NE SYS ID
|
EQPT_INFO_TABLE
|
NE SYS ID
|
EQPT_RELATIONSHIP_TABLE
|
NE SYS ID
|
HFR_ACL_POLICY_CONFIG
|
NE SYS ID
|
HFR_BGP_PEER_PM_TABLE
|
NE SYS ID
|
HFR_COMMON_INTERFACE_CONFIG
|
NE SYS ID
|
HFR_ETHER_INTERFACE_CONFIG
|
NE SYS ID
|
HFR_INTERFACE_DRC_PM_TABLE
|
NE SYS ID
|
HFR_INTERFACE_GC_PM_TABLE
|
NE SYS ID
|
HFR_INTERFACE_HELPER_ADDRESS
|
NE SYS ID
|
HFR_INTERFACE_MTU_LAYER2
|
NE SYS ID
|
HFR_INTERFACE_SECONDARY_ADDR
|
NE SYS ID
|
HFR_MPLS_INTERFACE_PM_TABLE
|
NE SYS ID
|
HFR_MPLS_LDP_PM_TABLE
|
NE SYS ID
|
HFR_MPLS_TE_LINK_PM_TABLE
|
NE SYS ID
|
HFR_MPLS_TE_TUNNEL_PM_TABLE
|
NE SYS ID
|
HFR_NODE_CPU_PM_TABLE
|
NE SYS ID
|
HFR_NODE_MEMORY_PM_TABLE
|
NE SYS ID
|
HFR_NODE_PROCESS_PM_TABLE
|
NE SYS ID
|
HFR_POS_INTERFACE_CONFIG
|
NE SYS ID
|
HFR_SONET_INTERFACE_CONFIG
|
NE SYS ID
|
HFR_SONET_INTERFACE_PATH
|
NE SYS ID
|
HFR_VERSION_INFO
|
NE SYS ID
|
IF_CROSS_CONNECT
|
NE SYS ID
|
IF_DWDM_CHANNEL_GROUP
|
NE SYS ID
|
IF_OPTICAL_PHY_CONFIG_TABLE
|
NE SYS ID
|
INTERFACE_APS_INFO
|
NE SYS ID
|
INTERFACE_DWDM_FREQUENCY
|
NE SYS ID
|
INTERFACE_STACK_TABLE
|
NE SYS ID
|
MANAGED_ET_TAB
|
NE SYS ID
|
MAP_CUST_TABLE
|
NE SYS ID
|
MIB2_INTERFACE_TABLE
|
NE SYS ID
|
NE_AUDIT_TRAIL_TABLE
|
NE SYS ID
|
NE_INVENTORY_TABLE
|
NE SYS ID
|
NE_PORT_STATUS_TABLE
|
NE SYS ID
|
NE_SWIMAGE_TABLE
|
NE SYS ID
|
ONS15216_ACTIVE_USER_TABLE
|
NE SYS ID
|
ONS15216_NE_INVENTORY_TABLE
|
NE SYS ID
|
ONS15216_USER_TABLE
|
NE SYS ID
|
ONS1530X_HO_PM_TABLE
|
NE SYS ID
|
ONS1530X_IP_PM_TABLE
|
NE SYS ID
|
ONS1530X_LO_PM_TABLE
|
NE SYS ID
|
ONS1530X_MS_PM_TABLE
|
NE SYS ID
|
ONS1530X_NE_INVENTORY_TABLE
|
NE SYS ID
|
ONS1530X_RS_PM_TABLE
|
NE SYS ID
|
ONS15454SDH_E1_PM_TABLE
|
NE SYS ID
|
ONS15454SDH_E3_PM_TABLE
|
NE SYS ID
|
ONS15454SDH_E4_PM_TABLE
|
NE SYS ID
|
ONS15454SDH_HO_PM_TABLE
|
NE SYS ID
|
ONS15454SDH_LO_PM_TABLE
|
NE SYS ID
|
ONS15454SDH_MS_PM_TABLE
|
NE SYS ID
|
ONS15454SDH_RS_PM_TABLE
|
NE SYS ID
|
ONS15454_327_NE_TABLE
|
NE SYS ID
|
ONS15454_8B10B_PM_TABLE
|
NE SYS ID
|
ONS15454_ACTIVE_USER_TABLE
|
NE SYS ID
|
ONS15454_CBQOS_INFO_TABLE
|
NE SYS ID
|
ONS15454_CLASSMAP_PM_TABLE
|
NE SYS ID
|
ONS15454_COS_PM_TABLE
|
NE SYS ID
|
ONS15454_DS1_PM_TABLE
|
NE SYS ID
|
ONS15454_DS3_PM_TABLE
|
NE SYS ID
|
ONS15454_ENET_PM_TABLE
|
NE SYS ID
|
ONS15454_FC_PM_TABLE
|
NE SYS ID
|
ONS15454_IFX_PM_TABLE
|
NE SYS ID
|
ONS15454_MATCH_STMT_PM_TABLE
|
NE SYS ID
|
ONS15454_NE_INVENTORY_TABLE
|
NE SYS ID
|
ONS15454_OTN_FEC_PM_TABLE
|
NE SYS ID
|
ONS15454_OTN_PATH_PM_TABLE
|
NE SYS ID
|
ONS15454_OTN_SEC_PM_TABLE
|
NE SYS ID
|
ONS15454_PHY_LAYER_PM_TABLE
|
NE SYS ID
|
ONS15454_POLICE_PM_TABLE
|
NE SYS ID
|
ONS15454_POS_PM_TABLE
|
NE SYS ID
|
ONS15454_SONET_LINE_PM_TABLE
|
NE SYS ID
|
ONS15454_SONET_PATH_PM_TABLE
|
NE SYS ID
|
ONS15454_SONET_SEC_PM_TABLE
|
NE SYS ID
|
ONS15454_SONET_VT_PM_TABLE
|
NE SYS ID
|
ONS15454_USER_TABLE
|
NE SYS ID
|
ONS15501_NE_EXPLORER_TABLE
|
NE SYS ID
|
ONS15501_OPT_POWER_PM_TABLE
|
NE SYS ID
|
ONS155XX_CDL_FLOW_CONFIG
|
NE SYS ID
|
ONS155XX_CDL_IF_CONFIG
|
NE SYS ID
|
ONS155XX_CDL_PM_TABLE
|
NE SYS ID
|
ONS155XX_CIRCUIT_CC_TBL
|
NE SYS ID
|
ONS155XX_CIRCUIT_PATH_TBL
|
NE SYS ID
|
ONS155XX_DCRP_TABLE
|
NE SYS ID
|
ONS155XX_DCRP_TABLE
|
NE SYS ID
|
ONS155XX_DISCOVERY_INFO_TABLE
|
NE SYS ID
|
ONS155XX_ETHER_HIST_PM_TABLE
|
NE SYS ID
|
ONS155XX_FCM_PE_PM_TABLE
|
NE SYS ID
|
ONS155XX_FLASH_DEVICE_TABLE
|
NE SYS ID
|
ONS155XX_IF_CIRCUIT_PARAMS_TBL
|
NE SYS ID
|
ONS155XX_IF_OPTICAL_POWER
|
NE SYS ID
|
ONS155XX_IF_PHY_INFO_TABLE
|
NE SYS ID
|
ONS155XX_NE_INFO_TABLE
|
NE SYS ID
|
ONS155XX_OPT_POWER_PM_TABLE
|
NE SYS ID
|
ONS155XX_PHY_PM_TABLE
|
NE SYS ID
|
ONS155XX_SONET_SEC_PM_TABLE
|
NE SYS ID
|
ONS15600SDH_HO_PM_TABLE
|
NE SYS ID
|
ONS15600SDH_MS_PM_TABLE
|
NE SYS ID
|
ONS15600SDH_RS_PM_TABLE
|
NE SYS ID
|
ONS15600_ENET_PM_TABLE
|
NE SYS ID
|
ONS15600_POS_PM_TABLE
|
NE SYS ID
|
ONS15600_SONET_LINE_PM_TABLE
|
NE SYS ID
|
ONS15600_SONET_PATH_PM_TABLE
|
NE SYS ID
|
ONS15600_SONET_SEC_PM_TABLE
|
NE SYS ID
|
ONS158XX_AMPLIFIER_PM_TABLE
|
NE SYS ID
|
ONS158XX_BCS_PM_TABLE
|
NE SYS ID
|
ONS158XX_CMP_PM_TABLE
|
NE SYS ID
|
ONS158XX_IOC_W_PM_TABLE
|
NE SYS ID
|
ONS158XX_LAC_ACTIVE_USER_TABLE
|
NE SYS ID
|
ONS158XX_LAC_LOG_STATUS_TABLE
|
NE SYS ID
|
ONS158XX_LAC_LOG_TABLE
|
NE SYS ID
|
ONS158XX_LAC_USER_TABLE
|
NE SYS ID
|
ONS158XX_LSM_PM_TABLE
|
NE SYS ID
|
ONS158XX_NE_IP_TABLE
|
NE SYS ID
|
ONS158XX_OADM_PM_TABLE
|
NE SYS ID
|
ONS158XX_OAD_PM_TABLE
|
NE SYS ID
|
ONS158XX_OSU_PM_TABLE
|
NE SYS ID
|
ONS158XX_PM_ACT_MOD_TABLE
|
NE SYS ID
|
ONS158XX_SCF_PM_TABLE
|
NE SYS ID
|
ONS158XX_TIMESTAMP_PM_TABLE
|
NE SYS ID
|
ONS158XX_TRANSPONDER_PM_TABLE
|
NE SYS ID
|
ONS158XX_WD_PM_TABLE
|
NE SYS ID
|
ONS158XX_WD_RX_PM_TABLE
|
NE SYS ID
|
OSS_ALARM_FLTR_TID_DENY_TBL
|
NE SYS ID
|
PM_HISTORICAL_APPOINTMENTS
|
NE SYS ID
|
PROXY_SERVER_TABLE
|
NE SYS ID
|
SERVER_MONITOR_TABLE
|
NE SYS ID
|
SWAY_USER_PORT_TABLE
|
NE SYS ID
|
TCA_EVENT_TABLE
|
NE SYS ID
|
TRANSACTION_LOG_TABLE
|
NE SYS ID
|
UNMANAGED_NE_INVENTORY_TABLE
|
NE SYS ID
|
USER_MAP_TABLE
|
NE SYS ID
|
USER_MAP_TABLE_TEMP
|
NE SYS ID
|
CIRCUIT_DEST_TBL
|
NE SYS ID
|
CIRCUIT_SPAN_TBL
|
NE SYS ID
|
ONS155XX_GRANULAR_CC_TBL
|
NE SYS ID
|
ONS155XX_CIRCUIT_CC_TBL
|
NE SYS ID
|
ONS155XX_PATH_TBL
|
NE SYS ID
|
link_table
|
NE SYS ID
|
ne_info_table
|
NE SYS ID
|
4.2.3 Using the SQL*PLUS Client to Manage the Database
To access the database and CTM schema objects, use the SQL*PLUS client that ships with Oracle products. The SQL*PLUS client is available for Microsoft Windows 2000 or NT 4.0 PCs or Sun Solaris 8 workstations. Refer to the Oracle documentation to install and run the SQL*PLUS client on a Windows 2000 or NT 4.0 PC.
On a Sun Solaris workstation, the SQL*PLUS client is installed as part of the Oracle server installation. The following guidelines are for logging into SQL*PLUS as a CTM user and managing CTM schema objects and data. Refer to Oracle's SQL*PLUS User Guide for a complete description.
Step 1 On the Sun Solaris workstation running Oracle, log in as the Oracle owner user. Use the username that was used when installing Oracle9i.
Note To verify the username, enter the id command on the shell.
Step 2 Verify that the following UNIX environment variables for the Oracle user are set correctly:
•ORACLE_HOME
•ORACLE_SID
•PATH variable has $ORACLE_HOME/bin in the path
•LD_LIBRARY_PATH
Step 3 On the command line, enter the following command:
sqlplus ctmanager/<password>
Note The default ctmanager password is ctm123!.
The message "Connected to: Oracle9i..." and the SQL> prompt should appear. If not, enter the username and password again.
Step 4 Enter any SQL command supported by Oracle upon connection to SQL*PLUS. For a list of SQL commands supported by Oracle, refer to the SQL*PLUS User Guide.
4.2.4 Understanding Basic SQL Commands for CTM Schema Objects
Table 4-5 lists commands that display, update, or modify CTM schema objects. Run each command in SQL*PLUS by entering the command at the SQL> prompt.
Table 4-5 SQL Commands for CTM Schema Objects
SQL Command
|
Description
|
select <table_name> from user_tables;
|
Returns a list of all table names owned by the ctmanager user.
|
select <view_name> from user_views;
|
Returns a list of all views owned by the CTM user.
|
describe <table_name>;
|
Takes a table_name as a parameter (valid table names are those returned by the previous two commands) and lists the name, type, and size of columns in the table.
|
describe <view_name>;
|
Takes a view_name as a parameter (valid view names are those returned by the previous two commands) and lists the name, type, and size of columns in the view.
|
select <col1, col2... coln> from <table_name>;
|
Takes col1....coln and table_name as parameters and displays data for all the columns listed. To display data for all columns, use an asterisk (*) instead of col1, col2, and so on.
|
select <col1, col2... coln> from <table_name> where
<col1> = <value1> and <col2> = <value2>...
|
Takes col1...coln and table_name as parameters and displays data for all the columns listed that meet the condition specified in the "where" clause. For example, the command:
select nedbaccessid from ne_info_table where
nesysid = 'ANGEL';
returns the value of column nedbaccessid from table ne_info_table for all rows for which nesysid = ANGEL.
|
select <col1, col2... coln> from <view_name> where
<col1> = <value1> and <col2> = <value2>...
|
Takes col1...coln and view_name as parameters and displays data for all the columns listed that meet the condition specified in the "where" clause.
|
delete <table_name>;
|
Takes table_name as a parameter and deletes the entire contents of the table. To make the change permanent, enter commit; at the SQL> prompt.
|
4.3 How Do I Manage the Network Software?
This section contains the following information:
•Managing Binaries Using the CTC Upgrade Table
•Downloading Software Images
•Using the Flash File Table
•Viewing Software Versions and Restarting the NE with a New Software Image
•Uploading Software Images
•Adding a New NE Software Version to the CTM Domain
•Deleting an NE Software Version from the CTM Domain
Follow the procedures described in this section to upgrade the Cisco Transport Controller (CTC) binary file and download new or modified images to supported NEs.
4.3.1 Managing Binaries Using the CTC Upgrade Table
Use the CTC Upgrade table to upgrade CTC binaries to the CTM database, to see which binary versions are available on the server, to make a particular CTC binary the active binary, or to delete a CTC binary.
Table 4-6 describes the fields in the CTC Upgrade table.
Table 4-6 Field Descriptions for the CTC Upgrade Table
Column Name
|
Description
|
Active
|
Indicates whether the selected CTC binary is the active binary.
|
Filename
|
Displays the filename of the binary that was uploaded to the CTM server.
|
Date and Time
|
Displays the date and time when the binary was uploaded to the CTM server.
|
User
|
Displays the username of the user who uploaded the binary to the CTM server.
|
4.3.1.1 Upgrading the CTC Binary File
If you have user privileges to do so, you can upgrade the CTC binary file independently of other CTM product upgrades.
Note If an updated CTC image becomes available after CTM is released, it is made available online to registered CCO users.
Caution The NE software packages (*.pkg files) for CTC are not the same as the NE software package (*.pkg files) used by the CTM client.
Step 1 In the Domain Explorer window, choose Administration > CTC Upgrade Table.
Step 2 Click the Add CTC Binary tool (or choose Edit > Add) to open the Upload CTC Binary File dialog box.
Step 3 In the Upload CTC Binary File dialog box, enter the complete name of the CTC package file to upload. Alternatively, click Browse to browse for a particular file. To make the upgraded CTC binary file the active file, check the Activate check box.
Step 4 Click OK. The CTC binary file appears in the CTC Upgrade table.
Step 5 If the binary file was not activated in Step 3, activate it now. Click the Activate CTC Binary tool (or choose Edit > Activate).
Note The CTM client synchronizes its local CTC files the next time it logs into the CTM server. Depending on the bandwidth available between the server and the client, the synchronization might take a few minutes to complete.
4.3.1.2 Deleting the CTC Binary File
Step 1 In the Domain Explorer window, choose Administration > CTC Upgrade Table.
Step 2 Select a CTC binary file to delete; then, click the Delete CTC Binary tool (or choose Edit > Delete).
Step 3 Click OK in the confirmation dialog box.
4.3.2 Downloading Software Images
Use the Software Download dialog box to download software to the following NEs:
•ONS 15216 EDFA2 (R2.3.0 and later)
•ONS 15216 EDFA3
•ONS 15302
•ONS 15305
•ONS 15310
•ONS 15327
•ONS 15454 SONET
•ONS 15454 SDH
•ONS 15501
•ONS 15530
•ONS 15540 ESP
•ONS 15540 ESPx
•ONS 15600 SONET
•ONS 15600 SDH
•ONS 15800
•ONS 15801
•ONS 15808
Note If a software download has a status of Queued, and if it has a task in the running list, the download cannot be canceled.
Caution If you mark an NE as an Out of Service while a software download is in progress on that NE, the software download might not complete successfully.
Caution To download software images to NEs, Cisco recommends that data communications network (DCN) bandwidth be 56 kbps or higher. If DCN bandwidth is less than 56 kbps, software download might take an extended period of time. For example, a typical ONS 15327 software image is approximately 2.5 MB. If a 2.5-MB file is downloaded to a single NE over a 19.2-kbps link, it will take 15 to 30 minutes depending on the volume of traffic. Performing software downloads in parallel increases the length of time by a multiple of the number of NEs targeted.
Note The latest ONS 15216 EDFA2 R2.4 hardware does not support software download to a software release other than 2.4.0. The ONS 15216 EDFA2 R2.3 hardware supports software download for NE software releases 2.2.1, 2.3, and 2.4.
Note For the ONS 15305 R2.0, a software download performed through CTM downloads only the agent software, not the entire network release. To download network release software, you must use Cisco Edge Craft.
Note The ONS 15800, ONS 15801, and ONS 15808 support software download of TL1 agent images. For firmware upgrade, see Cisco Photonics Local Terminal Software Administrator Manual for the ONS 1580x System.
4.3.2.1 Downloading Software Images to ONS 15216, ONS 153xx, ONS 15454, ONS 15501, ONS 15600, and ONS 1580x NEs
Step 1 In the Domain Explorer tree, select a management domain or group that contains NEs that are assigned an In Service or Under Maintenance operational state. Alternatively, select an NE that is assigned an In Service or Under Maintenance state.
Note Only one software download can occur on a specific NE at any given time.
Step 2 Choose Administration > Software Download. The Software Download dialog box opens. Table 4-7 provides descriptions.
Step 3 Enter the following information:
•NE model
•NEs
•Source
•Job comments
•Time
Caution If the CTM client and server run on the same machine and thus the local source directory is the same as the default destination directory, an error message is generated. To retrieve the software image selected from the local source directory, navigate to the appropriate path and restore it from the
<software_image_name>.old file.
Step 4 (For non-ONS 15501 NEs) Click Finish to initiate the software download to the standby memory on the NE.
Step 5 (For ONS 15501 NEs) Click Next.
Step 6 To activate the new image automatically, select Reboot and Activate. If Reboot and Activate is selected, the NE is rebooted with the newly downloaded image. If Reboot and Activate is not selected, you can activate the image later from the Flash File table. (See Using the Flash File Table.)
Step 7 Select the following information:
•NEs
•Flash banks
Note To view information about the files stored in the Flash Banks of the NE, click Flash File Table at the bottom of the dialog box. The Flash File table shows the Flash Bank names and the name and status for each stored file. For more information about the Flash File table, see Using the Flash File Table.
Note The currently active Flash bank is unavailable; users cannot download to the active Flash bank.
Step 8 Click Finish. The image will be downloaded to all of the NEs in the Selected Downloads list.
CTM stores two software versions: active and standby. When you download software, it is saved as the standby version. To activate the software download, use the NE Software table. (See Viewing Software Versions and Restarting the NE with a New Software Image.)
Note When you perform a software download on the ONS 15302, the node is restarted immediately with the new downloaded software. The result of the operation is sent to the Job Monitor table. In the NE Software table, the Switch/Revert operation is not allowed for the ONS 15302. The Commit operation, which is supported for the ONS 15302 R2.0 and later, switches to the standby software on the NE. The current standby software is not displayed for the ONS 15302.
Step 9 To check the status of the download job or verify that the download job was successful:
a. Check the Job Monitor table (Administration > Job Monitor).
b. Select the NE and check the Software Version field of the Equipment Inventory table (Configuration > <NE_model> > Equipment Inventory Table).
c. Select the NE and check the Active Software Filename field in the NE Software table (Administration > NE Software Table) for the software image version.
Note To download software to an ONS 15216 EDFA3 NE using the Server option, first choose Administration > Image Upload. The Image Upload dialog box opens. The image will be copied from the local file system in the directory specified in the CTM Server area. Choose Cisco ONS 15216 EDFA3 from the pull-down menu; then, click Upload. Then, choose Administration > Software Download. The Software Download dialog box opens with the Server radio button enabled.
Table 4-7 Field Descriptions for the Software Download Dialog Box
Field
|
Description
|
NE Model
|
Select the NE type to which you want to download software. The type you select determines the NEs that are displayed under Network Elements.
|
Network Elements
|
Use the Add and Remove buttons to move NEs to the Selected NEs list or remove NEs from the list. Software will be downloaded to NEs in the Selected NEs list.
|
Source
|
Specify the location of the software:
•Local allows you to select an image on the current client system.
•Server allows you to select an image on the CTM server to which your client is connected. The Server radio button is not active unless an image file exists on the server.
•Remote allows you to select an image on another network server that has TFTP configured and running. Specify the IP address of the server and the fully qualified pathname of the image, relative to the tftpboot directory. Remote is the only selectable source option for the following NEs: ONS 15302, ONS 15305, ONS 15501, ONS 15530 and ONS 15540, ONS 15800, ONS 15801, and ONS 15808.
Note If the Remote TFTP Server option is selected for ONS 15216 EDFA2, the software image that you are downloading must have been saved in the default directory, such as the tftpboot directory on the remote TFTP server.
Note The tftpboot directory must have read-write access, or the software download will fail. See Chapter 3, "Building the Network" for information about how to configure the tftp directory with read-write access.
|
Job Comments
|
Enter comments about the software download.
|
Time (time zone)
|
Set a time for the download. Click Now to begin download immediately, or click At Time and specify when to begin download, in 5-minute increments.
Note The time zone can be GMT, a user-defined offset from GMT, or local time, depending on what is specified in the User Preferences dialog box.
|
Software Download Dialog Box 2 for ONS 15501 NEs
|
Download Options For All Selected NEs
|
Reboot and Activate—Activates the new software image and reboots the NE, so the new image takes effect immediately.
|
Select Flash Partition
|
Selected NEs—NEs that will receive downloaded software.
Select Flash Bank—The flash banks available for storing the downloaded image on the selected NE.
|
Selected Downloads
|
The NEs selected for image download and the flash bank you selected for each NE.
To see details on the Flash Bank, select an NE and click Flash File table.
|
Software Download Dialog Box 2 for ONS 15530 and ONS 15540 NEs
|
Image File Size
|
The size of the image file. If you are downloading from a remote TFTP server, the size of the image file is not available.
|
Cancel job if CPU state changes
|
Cancel the job if the CPU state changes between the time the job is scheduled and the time the job is executed.
|
Activate image on next reload
|
Activates the image the next time the NE is rebooted.
|
Reload
|
Reboots the NE right after activation so the new image takes effect immediately. If an active CPU is reloaded, this option will cause a switchover if a standby CPU is present. Otherwise, service might be disrupted until the CPU reboots.
|
Switchover after downloading and reloading standby
|
(Available only when you choose the "Activate image on next reload" and "Reload" options.) This option applies only when downloading to the standby CPU. Switchover to standby occurs after downloading to and reloading the standby CPU; the standby CPU becomes active and runs the newly downloaded image.
|
Selected NEs
|
NEs that will receive downloaded software. When you select an NE from this list, information about the available flash partitions on the NE is displayed in the Flash Partition Data area, and you can select a partition.
|
Flash Partition Data
|
The flash partitions available for storing the downloaded image on the selected NE:
•CPU Slot No: Slot number of the CPU that contains the flash device.
•Status: Status of the CPU (active or standby).
•Name: Name of the flash partition; partitions on the standby CPU are indicated by "sby."
•Total Size: Total size of the partition, in bytes.
•Available: Number of free bytes in the partition. If you select a partition that does not have enough space to store the image, a warning message is displayed.
|
Selected Downloads
|
The NEs selected for image download and the flash bank you selected for each NE.
To see details about flash memory, select an NE and click Flash File table.
To remove an NE from the Selected Downloads list, select the NE and click Drop.
|
4.3.2.2 Downloading Software Images for ONS 15530 and ONS 15540 NEs
This section contains procedures for:
•Downloading Software Images on Single-CPU NEs
•Downloading Software Images for Dual-CPU NEs
Note Table 4-7 describes the fields in the Software Download dialog box.
Note Before downloading software on an ONS 155xx NE, verify that a read-write community string is available for the NE in the ONS 155xx SNMP Settings table. If there is no read-write community string available, the software download will fail with a "No write access" or "Request timed out" error message.
4.3.2.2.1 Downloading Software Images on Single-CPU NEs
Step 1 In the Domain Explorer tree, select one of the following:
•A management domain or group that contains ONS 15530 or ONS 15540 NEs that are in service or under maintenance.
•An ONS 15530 or ONS 15540 NE that is in service or under maintenance.
Step 2 Choose Administration > Software Download. The Software Download dialog box opens. Enter the following information:
•NE model
•NEs
•Source
•Job comments
•Time
Note The Server radio button is not active unless the relevant subdirectory in the /$CTMHOME/images/ directory contains an image file. The subdirectories are named Cisco_ONS15530, Cisco_ONS_15540_ESP, and Cisco_ONS_15540ESPx.
Caution If the CTM client and server run on the same machine and thus the Local source directory is the same as the default destination directory, an error message is generated. To retrieve the software image selected from the Local source directory, navigate to the appropriate path and restore it from the
<software_image_name>.old file.
Step 3 Click Next.
Step 4 Use the Image File Size field to determine which Flash partition has enough free space to hold the image.
Step 5 Select desired image download options.
Step 6 Select the following information:
•NEs
•Flash banks
•Flash partitions
Note To view information about the files stored in the Flash Banks of the NE, click Flash File Table at the bottom of the dialog box. The Flash File table shows the Flash Bank names and the name and status for each stored file. For more information about the Flash File table, see Using the Flash File Table.
Note The currently active Flash bank is unavailable; users cannot download to the active Flash bank.
Note If a Flash partition is selected before displaying the Flash File table, information is shown about the files on that partition only.
Step 7 Click Finish. Downloads will be performed for all the NEs in the Selected Downloads list.
Note If a partition that has insufficient space is selected, a warning message appears when the Finish button is clicked. Decide whether or not to proceed with the download. This check for free space is not performed for the remote server option.
After validating the image, the CTM server transfers the image to the selected Flash partition through TFTP. When the transfer is completed, the configuration register value is set to 0x02 for automatic booting and the boot command is modified to put the downloaded image first on the list.
If the reload option is selected, the NE is rebooted with the newly downloaded image.
If the image option is activated, the new software image is activated. If this option is not selected, activate the image from the Flash File table. (See Using the Flash File Table.)
Step 8 To check the status of the download job or verify that the download job was successful:
a. Check the Job Monitor table (Administration > Job Monitor).
b. Select the NE and check the Software Version field of the Equipment Inventory table (Configuration > ONS 155XX > Equipment Inventory Table).
c. Select the NE and check the Active Software Filename field in the NE Software table (Administration > NE Software Table) for the software image version.
4.3.2.2.2 Downloading Software Images for Dual-CPU NEs
Consider the following recommendations when downloading software images for dual CPUs:
•Update the standby CPU first and choose the switchover option. This ensures that the new image will run on an active CPU with minimum system interruption.
•Either update the second CPU immediately after updating the first one, or schedule the second CPU for downloading after the image has run successfully for some time on the first CPU.
Step 1 In the Domain Explorer tree, select one of the following:
•A management domain or group that contains ONS 15530 or ONS 15540 NEs that are in service or under maintenance.
•An NE that is in service or under maintenance.
Step 2 Select Administration > Software Download. The Software Download dialog box opens. Enter the following information:
•NE model
•NEs
•Job comments
•Source
•Time
Note The Server radio button is not active unless the relevant subdirectory in the /$CTMHOME/images/ directory contains an image file. The subdirectories are named Cisco_ONS15530, Cisco_ONS_15540_ESP, and Cisco_ONS_15540ESPx.
Caution If the CTM client and server run on the same machine and thus the Local source directory is the same as the default destination directory, an error message is generated. To retrieve the software image selected from the Local source directory, navigate to the appropriate path and restore it from the
<software_image_name>.old file.
Step 3 Click Next.
Step 4 Check the Image File Size field against the list of Flash partitions to determine which Flash partition has enough free space to hold the image.
Step 5 Select desired image download options.
Note Before the image is activated, the CTM server checks the state of the standby CPU. If the standby CPU is not in hot-standby mode, the update operation is aborted after the image is downloaded. For more information, refer to the hardware documentation for information about updating with system images that are not hot-standby compatible.
Note If the "Switchover after downloading and reloading standby" option is selected, the image will always be downloaded to the selected CPU slot number. For example, assume that slot 6 is standby and the sby-bootflash (standby) partition is chosen. If a switchover occurs between job scheduling and job execution and slot 6 becomes active, the image will be downloaded to the slot 6 bootflash partition.
Step 6 Select the following information:
•NEs
•Flash banks
•Flash partitions
Note To view information about the files stored in the Flash Banks of the NE, click Flash File Table at the bottom of the dialog box. The Flash File table is displayed, showing the Flash Bank names and the name and status for each stored file. For more information about the Flash File table (see Using the Flash File Table).
Note The currently active Flash bank is unavailable; users cannot download to the active Flash bank.
Note If a Flash partition is selected before displaying the Flash File table, information is shown about the files on that partition only.
Step 7 Click Finish. Downloads will be performed for all the NEs in the Selected Downloads list.
Note If a partition that has insufficient free space is selected, a warning message appears. Decide whether or not to proceed with the download. This check for free space is not performed for the remote server option.
After validating the image, the CTM server transfers the image to the selected Flash partition through TFTP. When the transfer is completed and the standby CPU is in hot standby mode, the configuration register value is set to 0x02 for automatic booting and the boot command is modified to put the downloaded image first on the list. If the reload option is chosen, the standby CPU is reloaded.
If the switchover option is selected, a switchover from the active CPU to the standby CPU is performed after reloading the standby CPU. The former standby CPU, which is now the active CPU, will run the newly downloaded image.
If the Activate option is not selected, activate the new image from the Flash File table. (See Using the Flash File Table.)
Step 8 After updating the standby CPU (which is now the active CPU), use the same procedure to update the formerly active CPU (which is now the standby CPU), with one difference: there is no need to select the switchover option because the current active CPU is already running the new image.
Step 9 To check the status of the download job and verify that the download job was successful:
a. Check the Job Monitor table (Administration > Job Monitor).
b. Select the NE and check the Software Version field of the Equipment Inventory table (Configuration > ONS 155XX > Equipment Inventory Table).
c. Select the NE and check the Active Software Filename field in the NE Software table (Administration > NE Software Table) for the software image version.
4.3.3 Using the Flash File Table
Use the Flash File table to activate a downloaded image and manipulate the files in the ONS 155xx NE Flash memory.
Step 1 From the Domain Explorer, select an NE; then, select Administration > ONS 155XX > Flash File Table. Table 4-8 describes the fields in the Flash File table.
Step 2 Perform any of the functions listed in Table 4-9.
Table 4-8 Field Descriptions for the Flash File Table
Column Name
|
Description
|
Flash Partition Name
|
Name of the flash partition that contains the flash file.
|
Filename
|
Name of the flash file.
|
File Status
|
Status of the flash file:
•Deleted: The file is marked as deleted.
•Invalid Checksum: The file has an invalid checksum.
•Valid: The file is valid.
•Active: (ONS 15501 only) The software in the file has been activated.
•Not active: (ONS 15501 only) The software in the file has not been activated.
|
File Size
|
Size of the file in bytes. This field is not applicable to the ONS 15501; the file size cannot be read.
|
File Checksum
|
File checksum stored in the file header. The checksum is computed and stored when the file is written into the flash partition and serves to validate the data in the file. A file is marked as having an invalid checksum if any checksum mismatch was detected while writing or reading the file.
Incomplete files (files truncated because of either a lack of free space or a network download failure) are also written with a bad checksum and marked as invalid.
This field is not applicable to the ONS 15501; the checksum cannot be read.
|
Table 4-9 Flash File Table Functions and Supported ONS 15501, ONS 15530, and ONS 15540 NEs
Function
|
Procedure
|
Supported on ONS 15501?
|
Supported on ONS 15530?
|
Supported on ONS 15540 ESP and ONS 15540 ESPx?
|
Activate an image
|
Select the file and choose Edit > Activate. The image is activated, and the NE reboots.
|
Yes
|
Yes
|
Yes
|
Verify file checksum
|
Select the file and choose Edit > Verify.
|
No
|
Yes
|
Yes
|
Mark a file as deleted
|
Select the file and choose Edit > Delete. The status of the file changes to Deleted. The file is not actually deleted until the Squeeze function is used.
|
No
|
Yes
|
Yes
|
Mark a file as undeleted
|
Select a file that is marked Deleted and choose Edit > Undelete.
|
No
|
Yes
|
Yes
|
Physically remove a file
|
Select a file that is marked Deleted and choose Edit > Squeeze.
|
No
|
Yes
|
Yes
|
4.3.4 Viewing Software Versions and Restarting the NE with a New Software Image
The NE Software table lists the software that is installed on an NE. Use the Edit menu options to restart an NE with a new software image.
Tip Back up the NE database before activating or reverting to the standby software image on the NE.
Note The Edit menu options are not available for the CRS-1. The NE Software table is not supported for the Catalyst 6509.
Step 1 In the Domain Explorer tree, select an NE and choose Administration > NE Software Table. Table 4-10 describes the fields in the NE Software table.
•For NEs other than the ONS 15216 EDFA and ONS 1580x, the NE Software table displays the active and standby software versions for the NE.
•For ONS 15216 EDFA and ONS 1580x NEs, the NE Software table displays the active, standby, and running software versions.
Note The NE Software table can also be launched from the Job Monitor table. From the Job Monitor table, choose Edit > NE Software Table.
Step 2 To activate new software on an NE, select the NE in the table and click the Commit tool (or choose Edit > Commit).
•For the ONS 15305 and CTC-based NEs, this makes the standby software version the active version (if the standby version is newer than the active version) and restarts the NE with the newer version.
•For the ONS 15800, ONS 15801, and ONS 15808, the running software version can assume the active or standby software version.
Note The Commit feature is not available for ONS 15216 EDFA NEs.
Step 3 To revert to the standby software version on an NE, select the NE and click the Revert/Switch tool (or choose Edit > Revert/Switch).
•For the ONS 15216 EDFA, ONS 15305, ONS 15310, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH, this reverts the active software version back to the standby version (if the standby version is older than the active version) and restarts the NE with the newer version.
•For the ONS 15600 SONET and ONS 15600 SDH, the Revert operation opens the Memory Restore dialog box, and you will need to provide a compatible database. For example, if the NE is running a software release 1.1 and you want to download a R1.0 package, you must provide a R1.0 database after downloading the software R1.0 package.
•For the ONS 15800, ONS 15801, and ONS 15808, the Revert/Switch operation makes the standby software version the running version.
Step 4 To accept the software version of an NE, select the NE and click the Accept tool (or choose Edit > Accept). The Accept command copies the downloaded software onto the standby Timing & Shelf Controller (TSC) and activates it.
Note The Accept feature is only available for the ONS 15600 SONET and ONS 15600 SDH.
Table 4-10 Field Descriptions for the NE Software Table
Field
|
Description
|
NE Model Name
|
Displays the model of the selected NE.
|
NE ID
|
Displays the ID name of the selected NE.
|
Active Software
|
Displays the active software version. For the ONS 15530 and ONS 15540, displays the software version on the active CPU.
|
Standby Software
|
Displays the standby software version. For the ONS 15302 and ONS 15305, it is the NE software version that has been downloaded. For the ONS 15530 and ONS 15540, displays the software version on the standby processor if a standby processor is present.
|
Running Software
|
(ONS 1580x only) Displays the running software version.
|
Busy Flag
|
Indicates whether the NE is rebooting to perform a software commit or revert. While the NE is rebooting, the value is true; when the NE has finished rebooting, the value is false.
|
4.3.5 Uploading Software Images
You can upload NE binary software images from the client file system into an appropriate NE software repository in the CTM server, to make the images available for selection when requesting a software download.
Use the Image Upload dialog box to upload software images to the following NEs:
•ONS 15216 EDFA2
•ONS 15216 EDFA3
•ONS 15302
•ONS 15305
•ONS 15310
•ONS 15327
•ONS 15454 SONET
•ONS 15454 SDH
•ONS 15501
•ONS 15530
•ONS 15540 ESP and ESPx
•ONS 15600 SONET
•ONS 15600 SDH
•ONS 15800
•ONS 15801
•ONS 15808
Step 1 In the Domain Explorer, select an NE and choose Administration > Image Upload. The Image Upload dialog box opens.
Step 2 Select the source files from the Local File Selection list. Click Browse to locate files that are not visible in the field. You can select multiple files from the local machine for the upload process.
Step 3 To remove a file from the Local File Selection list, select the file from the list and click Delete.
Step 4 Select the NE-specific folder from the CTM server drop-down list to choose where to transfer the image.
Step 5 To remove a file that is already present on the CTM server, select the file from the list and click Delete.
Step 6 Click Upload.
Note If you cancel the upload while it is in progress, only the files that have already been uploaded at the time of cancellation are retained. The current file being uploaded and other pending files are canceled.
4.3.6 Adding a New NE Software Version to the CTM Domain
The Supported NE table provides information about the software version that is currently supported on a selected NE.
Use this procedure only to apply a minor upgrade to the default, CTM-supported software on the supported NE. Major upgrades to NE software might require you to update CTM.
Caution Cisco recommends that this feature be used only at the advice of a Cisco technical support engineer. If incorrect modifications to data in the Supported NE table are made, the CTM server might not communicate with one or more NEs in the domain.
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table. Table 4-11 describes the fields in the Supported NE table.
Step 2 Select an NE.
Caution Make sure to select the correct NE row in the Supported NE table before proceeding. If the new software version is added to the wrong NE, the updated NE in the CTM domain will show erroneous behavior.
Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.
Step 4 The NE model and the NE version fields are initialized with the corresponding values in the selected row. Modify the version string to match the exact version string of the upgraded software; then, click OK.
If the NE with the modified version string exists in the CTM domain, the CTM server attempts to communicate with it. The server will manage the NE if communication is established.
Table 4-11 Field Descriptions for the Supported NE Table
Column Name
|
Description
|
NE Model
|
Displays the model of the selected NE.
Note The Supported NE table includes passive NEs, such as the ONS 15216 DCU and OSC. Passive NEs are shown in the Supported NE table for informational purposes only. The CTM server does not check the software validity of passive NEs.
|
Software Version
|
Specifies the software version that is supported on the selected NE.
Note You cannot delete the default NE software version. The default software version rows are created when the CTM server is installed. These rows are the factory-default settings and cannot be deleted.
Note For the ONS 1580x, this field shows the TL1 agent version, not the NE release version. If only the first two digits of the TL1 agent version are specified, all versions in that release will be managed. For example, if TL1 agent version 2.1 is specified, all 2.1.x versions will be managed.
|
Version Name
|
Specifies the software version name. For example, "15454 5.00" represents ONS 15454 SONET Release 5.0.
|
4.3.7 Deleting an NE Software Version from the CTM Domain
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select the NE for which you want to delete the software version; then, choose Edit > Delete (or click the Delete Supported NE Version tool).
Note NE images that were manually added can be deleted. Default NE images cannot be deleted.
Step 3 Click OK in the confirmation dialog box.
4.4 How Do I Modify the Network?
This section contains the following information:
•Changing IP Addresses for NEs
•Updating the Configuration Files After Changing the CTM Server IP Address
•Changing the Internal Subnet Address—ONS 15600
•Viewing and Changing the Network Address—CTC-Based NEs
•Configuring Proxy Server Settings—CTC-Based NEs
•Changing the Operational State of an NE
•Setting Date, Time, and Location on CTC-Based NEs
•Configuring SNTP for Multiple NEs
•Configuring Application-Specific Parameters
Note For information about setting up routing protocols, see 5.3 Configuring Routing Protocols on Optical NEs, page 5-6.
4.4.1 Changing IP Addresses for NEs
CTM supports an active IP address, a primary IP address, and a secondary IP address:
•Active IP address—Displays the active IP address of the selected NE. For all ONS 15000 NEs except the ONS 15800, ONS 15801, and ONS 15808, the active IP address field for ENEs is the IP address of the GNE that the NE is using.
•For the ONS 15800, ONS 15801, and ONS 15808, this field displays either the primary or secondary IP address, depending on which address is used to reach the NE.
•Primary IP address—(Applicable only to the ONS 15800, ONS 15801, and ONS 15808) Displays the primary IP address.
•Secondary IP address—(Applicable only to the ONS 15800, ONS 15801, and ONS 15808) Displays the backup IP address that the CTM server uses to reach the ONS 1580x NE when connectivity through the primary IP address is disrupted. For ONS 15800, ONS 15801, and ONS 15808 NEs:
–The secondary IP address points to a backup address that is remapped to the ONS 15800, ONS 15801, or ONS 15808 primary address. This backup address allows CTM to reach the ONS 1580x node through a different route by using Layer 3 routing instead of the less-secure Layer 2 routing. If the CTM server cannot connect to the NE through either the primary or secondary IP address, the NE is marked as unreachable. To disable the secondary IP address for the ONS 1580x, enter the same address for both the primary and secondary IP addresses.
–If the primary IP address is changed when the communication state is available and the operational state is In Service or Under Maintenance, the actual node IP address changes. CTM resets the NE automatically to activate the new IP address. After resetting the active IP address, the primary IP address and secondary IP address have the same value. Reset the network address translation (NAT) address on the router to map the NAT address to the new Control and Monitoring Processor (CMP) module address before resetting the secondary IP address.
–If the primary IP address is changed when the communication state of the ONS 1580x NE is unavailable (communication state is independent of the operational state), the primary, secondary, and active IP addresses are changed only in CTM. No IP address change requests are sent to the NE.
–If the active IP address is changed from a primary to a secondary IP address, an alarm is generated. The alarm is cleared when the IP address is switched back to the primary IP address.
4.4.1.1 Changing the NE IP Address on CTC-Based NEs
If you want to change the NE IP address on CTC-based NEs, complete the following steps.
Step 1 In the Domain Explorer window, click on the NE and choose Configuration > NE Explorer.
Step 2 In the property sheet of the NE Explorer, select the Network tab.
Step 3 Select the Address subtab.
Step 4 Change the IP address in the IP Address field. Make sure that the new IP address is not in use.
Step 5 If necessary, change the following fields:
•Default Router
•Subnet Mask
Step 6 Click Apply.
Step 7 A confirmation dialog box is displayed. It informs the user that the NE will reboot. Click Yes. CTM will lose connectivity to the NE. After several minutes, the NE will be back in service with the new IP addre
4.4.1.2 Changing the IP Address in CTM Only
You can change only the IP address of a GNE. The IP address of an ENE cannot be changed.
Step 1 In the Domain Explorer tree, select the NE that will be changed.
Step 2 Click the Address tab. In the Active IP Address field, enter the new IP address. For the ONS 15800, ONS 15801, and ONS 15808, in the Primary IP Address or Secondary IP Address field, enter the IP address. The IP address must be unique and in the form ddd.ddd.ddd.ddd, where ddd is a decimal octet expressed as an integer from 0 to 255. The first octet cannot be a zero.
Step 3 Click Save.
Caution For the ONS 15800, ONS 15801, and ONS 15808, be careful while entering the primary IP address. If the primary IP address for an in-service or under-maintenance ONS 15800, ONS 15801, or ONS 15808 is mistyped and saved, the NE becomes unreachable. This occurs because CTM resets the NE to make the new IP address effective. Use the TL1 interface to correct the mistake.
Note If the IP address is changed in CTM, the change is made only in CTM. For the ONS 15200, use the CLI (choose Configuration > ONS 15200 > Launch CLI in the Domain Explorer) to physically change the IP address on the NE. Also use the CLI if changes in the IP address need to be applied to the ONS 155xx NEs. Choose Configuration > ONS 155XX > Launch CLI in the Domain Explorer.
Note When the new primary IP address is set for the ONS 15800, ONS 15801, or ONS 15808, the secondary IP address is changed to the same address. Set a new address in the Secondary IP Address field.
Changing the active IP address of ONS 15800, ONS 15801, or ONS 15808 equipment is only possible if the ONS 15800, ONS 15801, or ONS 15808 NE has never been reached by CTM. Otherwise, the CTM user can set a different primary or secondary IP address.
4.4.1.3 Changing the IP Address when CTM and Oracle Are on the Same Server
To change the IP address of a standalone CTM server with a single IP interface when CTM and Oracle are on the same server, complete the following steps:
Step 1 Log into the CTM server as the root user.
Step 2 Enter the following command to shut down the CTM server:
Step 3 Enter the following commands to shut down Oracle:
Step 4 Complete the following substeps:
a. Enter the following command to change the IP address in the /etc/netmasks file:
b. Enter the following command to change the IP address in the /etc/hosts file:
c. Enter the following command to change the IP address in the etc/hostname.xxx file, where xxx is the IP interface that is defined in the Solaris server:
d. Enter the following command to change the default router file, if required:
e. Enter the following command to change the subnet mask on the CTM server:
Step 5 Complete the following application-level steps:
a. Enter the following command to change the IP address in the Oracle listener file:
# vi /oraclesw9i/product/9.2/network/admin/listener.ora
b. Enter the following command to change the IP address in the Oracle tnsnames file:
# vi /oraclesw9i/product/9.2/network/admin/tnsnames.ora
c. Enter the following command to change the IP address in the CTM server configuration file:
# vi /opt/CiscoTransportManagerServer/cfg/CTMServer.cfg
Note Make sure to change all IP addresses where they are referenced.
d. Enter the following command to change the IP address in the jacORB properties file:
# vi /opt/CiscoTransportManagerServer/openfusion/classes/jacorb.properties
e. Enter the following command to change the IP address in the web server configuration file:
# vi /opt/CiscoTransportManagerServer/webServer/conf/httpd.conf
Step 6 Enter the following commands to halt and reboot the CTM server:
4.4.1.4 Changing the IP Address on the ONS 15800, ONS 15801, and ONS 15808 NE
Step 1 In the Domain Explorer, select the ONS 15800, ONS 15801, or ONS 15808 NE and choose Configuration > NE Explorer.
Step 2 In the NE Explorer Properties pane, click the Address tab. Specify the following:
•Active IP Address—Primary or secondary IP address currently used to reach the NE
•Primary IP Address—Primary IP address of the NE
•Secondary IP Address—Backup IP address used to reach the NE
•Subnetwork Mask—Subnetwork mask for the NE
•Default Router—IP address of the default router for the NE
Note When the primary and secondary IP addresses are the same, the secondary IP address is not supported. For the ONS 15808 NEs, the secondary IP address points to a backup IP address that is remapped to the ONS 15808 primary IP address. This backup address allows CTM to reach the ONS 15808 node through a different route by using Layer 3 routing instead of the less-secure Layer 2 routing.
If you change the primary IP address when the ONS 15808 is in service or under maintenance, the actual node IP address changes. CTM resets the NE automatically to activate the new IP address. After resetting the active IP address, the primary IP address and secondary IP address have the same value. If you want to reset the secondary IP address, you should first reset the NAT address on the router to map the NAT address to the new CMP module address.
Step 3 Click Apply.
4.4.2 Updating the Configuration Files After Changing the CTM Server IP Address
If you change the CTM server IP address (as shown in section Changing the IP Address when CTM and Oracle Are on the Same Server), you must replace the old IP address with the new IP address in the configuration files shown in Table 4-12. Use a standard UNIX text editor such as vi to update the files. Changes in the configuration files take effect after rebooting the server.
Table 4-12 Configuration Files that Require Updating
Filename
|
Location
|
UNIX Configuration Files
|
hosts
|
/etc
|
netmasks
|
/etc
|
defaultrouter
|
/etc
|
Oracle Configuration Files
|
tnsnames.ora
|
/oraclesw9i/product/9.2/network/admin
|
listener.ora
|
/oraclesw9i/product/9.2/network/admin
|
CTM Server Configuration File
|
CTMServer.cfg
|
/opt/CiscoTransportManagerServer/cfg
|
jacorb.properties
|
/opt/CiscoTransportManagerServer/openfusion/classes
|
httpd.conf
Note There are two IP address instances that require modification:
Listen <IP_address>:51
ServerName <IP_address>:51
|
/opt/CiscoTransportManagerServer/webServer/conf
|
CTMServer.perm
|
/opt/CiscoTransportManagerServer/cfg/
|
NotificationService.xml
|
/opt/CiscoTransportManagerServer/openfusion/domains/
OpenFusion/localhost/NotificationService/
|
4.4.3 Changing the Internal Subnet Address—ONS 15600
To avoid IP address conflicts, change the class B subnet address if your internal network uses the same address range as the default subnet address. To change class B subnet address for the TSC cards, complete the following steps.
Caution All network changes should be approved by your network administrator.
Step 1 In the Domain Explorer tree, select an ONS 15600 SONET or ONS 15600 SDH NE.
Step 2 Choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 3 In the node properties pane of the NE Explorer, select the Network tab.
Step 4 Select the Internal Subnet subtab.
Step 5 Specify the following in the TSC section:
•TSC1—Class B subnet address for the first TSC.
•TSC2—If there are two TSCs are installed, enter the class B subnet address for the second TSC.
Step 6 Click Apply.
4.4.4 Viewing and Changing the Network Address—CTC-Based NEs
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer.
Step 2 In the node properties pane of the NE Explorer, select the Network tab.
Step 3 Select the Address subtab.
Step 4 Complete the following information:
•IP Address—IP address of the NE.
•Default Router—IP address of the default router.
•Subnet Mask—Subnetwork mask ID of the NE.
•MAC Address—Read-only. Address as identified in the IEEE 802 MAC layer.
•LCD IP Setting—(ONS 15454 SONET and SDH only) Select one of the following:
–Allow Configuration—Allows users to change the shelf IP address from the LCD screen.
–Display Only—Displays the shelf IP address in the LCD screen and does not allow any configuration.
–Suppress Display—Shelf IP address is not displayed in, and cannot be configured from, the LCD screen.
•Forward DHCP Requests—When checked, forwards the Dynamic Host Configuration Protocol (DHCP) requests to the IP address.
•DHCP Server—IP address of the DHCP server.
•CORBA (IIOP) Listener Port—Allows you to set a listener port to allow communication with the NE through firewalls. Select one of the following:
–Default-Fixed
–Standard Constant (683)
–Other Constant
Step 5 Click Apply.
4.4.5 Configuring Proxy Server Settings—CTC-Based NEs
CTC-based NEs have a proxy server feature set that allows networking these NEs in environments where visibility and accessibility are restricted. In the proxy server environment, CTC-based NEs are designated as either gateway NEs (GNEs) or end NEs (ENEs). The GNE is LAN-connected to the DCN, while the ENE is accessed through the proxy server feature on the GNE over the section DCC (SDCC). The ENE is not directly accessible through the IP address, while the GNE has an IP address that is valid for the DCN LAN. CTM can manage CTC-based NEs deployed in a proxy environment.
Step 1 In the Domain Explorer tree, select a CTC-based NE.
Step 2 Choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 3 In the Properties pane of the NE Explorer, select the Network tab.
Step 4 Select the Firewall/Proxy subtab.
Step 5 Check the Enable proxy server on port check box. When enabled, the NE serves as a proxy for connections between CTC clients and the NEs that are DCC-connected to proxy NEs. Uncheck the check box to disable the proxy. The on port field has a default value of 1080.
Step 6 You can enable the proxy on one of the following:
•ENE
•GNE
•Proxy-only
If ENE and GNE are in different IP subnets, or if ENE and GNE are in different Ethernet segments, proxy should be enabled in the GNE. If firewall is enabled on the GNE, it prevents communication between the laptop connected to the LAN port of the ENE and network operations center (NOC), even if proxy is enabled on both the ENE and GNE. Whenever firewall is enabled on a GNE, proxy should be enabled on the GNE as well.
Step 7 Click Apply.
4.4.5.1 Notes on Configuring Proxy Server Settings
Note the following when configuring proxy server settings:
•In a proxy environment, you can launch CTC from CTM for a proxy GNE if you are launching CTC for an ENE. CTC cannot be launched for a non-GNE if the proxy GNE is marked Out of Service or is not reachable from CTM. Launching CTC for NEs that are not reachable before CTM can determine whether they are reachable or not displays the error messages "Error in launching CTC node view for <NE>" and "Initializing Class Loaders Failed-Timeout opening <NE IP>:<Port>."
•In a proxy environment, you cannot launch a TL1 Telnet session directly for an NE. You can launch the Telnet window for the GNE and then enter the ACT-USER command, specifying the ENE as the TID.
•CTM can configure multiple GNEs but it can only associate a single GNE for a given ENE. If the GNE becomes inaccessible, CTM can automatically use one of the other available GNEs to reach the ENE.
•When a proxy-enabled GNE (named GNE1) is first added to CTM, CTM automatically discovers all associated NEs (through the topology discovery feature) and identifies them as ENEs associated with GNE1. If there are other proxy-enabled GNEs that are discovered from GNE1, CTM will still mark them as ENEs associated with GNE1. When proxy is enabled on any GNE, all ENEs lose connectivity and eventually regain it. In a multiple DCC-connected GNE scenario, NEs that do not regain connectivity should be marked Out of Service, then marked In Service again.
•If both LAN and DCC connections exist between the GNE and ENEs, the DCC connection takes precedence.
•In order to collect PM data on ENEs, PM collection on the GNE must be set to either 15 Min or 1 Day.
4.4.5.2 Configuring Proxy Server Settings for NEs Equipped with ML-Series Cards
CTM supports only the following configurations for NEs that are equipped with ML-series cards:
•GNE with SNMP v1 and v2
Note CTM considers an NE as a GNE if proxy-only is enabled, or if proxy with firewall is enabled.
•ENE with SNMP v1 and v2
Note CTM considers an NE as an ENE if proxy is not enabled, or if proxy/firewall and craft access are enabled.
For NE release 4.6 and earlier, see Table 4-13. For NE release 5.0, see Table 4-14. In order for CTM to support a proxy/firewall scenario, the scenario must have a "Yes" in all four columns of the table, and CLI launch must be supported.
For an explanation of proxy server settings on the NEs, refer to the NE hardware documentation.
Table 4-13 describes the proxy server settings for release 4.6 and earlier NEs.
Table 4-13 Proxy Server Settings for Release 4.6 and Earlier NEs
Proxy Scenario
|
FM
|
CM
|
PM
|
RMON Threshold
|
Proxy only, GNE (CLI launch is supported) 1
|
SNMP v1
|
No
|
Yes
|
Yes
|
Yes
|
SNMP v2
|
Yes
|
Yes
|
Yes
|
Yes
|
Proxy only, ENE (CLI launch is not supported) 2
|
SNMP v1
|
No
|
Yes
|
Yes
|
No
|
SNMP v2
|
No
|
Yes
|
Yes
|
No
|
Proxy and internal firewall, GNE (CLI launch is supported) 3
|
SNMP v1
|
No
|
Yes
|
Yes
|
Yes
|
SNMP v2
|
Yes
|
Yes
|
Yes
|
Yes
|
Proxy and internal firewall, ENE (CLI launch is not supported) 4
|
SNMP v1
|
No
|
Yes
|
Yes
|
No
|
SNMP v2
|
No
|
Yes
|
Yes
|
No
|
Proxy only, GNE, with external firewall and NAT (CLI launch is not supported) 5
|
SNMP v1
|
No
|
Yes
|
Yes
|
No
|
SNMP v2
|
Yes
|
Yes
|
Yes
|
No
|
Proxy only, GNE, with internal firewall, external firewall, and NAT (CLI launch is not supported) 6
|
SNMP v1
|
No
|
Yes
|
Yes
|
No
|
SNMP v2
|
No
|
Yes
|
Yes
|
No
|
Proxy only, ENE, with internal firewall, external firewall, and NAT (CLI launch is not supported) 7
|
SNMP v1
|
No
|
Yes
|
Yes
|
No
|
SNMP v2
|
No
|
Yes
|
Yes
|
No
|
External firewall and PAT 8 (CLI launch is not supported) 9
|
SNMP v1
|
No
|
No
|
No
|
No
|
SNMP v2
|
No
|
No
|
No
|
No
|
Table 4-14 describes the proxy server settings for release 5.0 NEs.
Table 4-14 Proxy Server Settings for Release 5.0 NEs
Proxy Scenario
|
FM
|
CM
|
PM
|
RMON Threshold
|
Proxy only, GNE (CLI launch is supported) 1
|
SNMP v1
|
Yes
|
Yes
|
Yes
|
Yes
|
SNMP v2
|
Yes
|
Yes
|
Yes
|
Yes
|
Proxy only, ENE (CLI launch is not supported) 2
|
SNMP v1
|
Yes
|
Yes
|
Yes
|
Yes
|
SNMP v2
|
No
|
Yes
|
Yes
|
Yes
|
Proxy and internal firewall, GNE (CLI launch is supported) 3
|
SNMP v1
|
Yes
|
Yes
|
Yes
|
Yes
|
SNMP v2
|
Yes
|
Yes
|
Yes
|
Yes
|
Proxy and internal firewall, ENE (CLI launch is not supported) 4
|
SNMP v1
|
Yes
|
Yes
|
Yes
|
Yes
|
SNMP v2
|
No
|
Yes
|
Yes
|
Yes
|
Proxy only, GNE, with external firewall and NAT (CLI launch is not supported) 5
|
SNMP v1
|
Yes
|
Yes
|
Yes
|
Yes
|
SNMP v2
|
Yes
|
Yes
|
Yes
|
Yes
|
Proxy only, GNE, with internal firewall, external firewall, and NAT (CLI launch is not supported) 6
|
SNMP v1
|
Yes
|
Yes
|
Yes
|
Yes
|
SNMP v2
|
Yes
|
Yes
|
Yes
|
Yes
|
Proxy only, ENE, with internal firewall, external firewall, and NAT (CLI launch is not supported) 7
|
SNMP v1
|
Yes
|
Yes
|
Yes
|
Yes
|
SNMP v2
|
No
|
Yes
|
Yes
|
Yes
|
External firewall and PAT (CLI launch is not supported) 8
|
SNMP v1
|
No
|
No
|
No
|
No
|
SNMP v2
|
No
|
No
|
No
|
No
|
4.4.6 Changing the Operational State of an NE
Step 1 In the Domain Explorer tree, select the NE that will be changed.
Step 2 In the Network Element Properties pane > Operational State field, choose one of the following operational states:
•Preprovisioned (not available if already provisioned)—The NE has been added to the database for provisioning but is not yet in service. CTM does not manage preprovisioned NEs.
•In Service—The NE is deployed and requires monitoring. CTM collects polling, fault management (FM), configuration management (CM), and PM data from in-service NEs and stores the data in the database.
•Out of Service—The NE has been marked Out of Service by a network administrator and does not require monitoring. The CTM database records the last known state of the NE when it was in service.
•Under Maintenance—The NE is temporarily under maintenance but requires monitoring. This state is the same as In Service except that CTM does not report alarms or events for under-maintenance NEs.
Tip You can also right-click an NE in the Domain Explorer tree or Subnetwork Explorer tree and choose Mark Under Maintenance, Mark In Service, or Mark Out of Service from the shortcut menu.
There are two additional states that you cannot choose. These operational states are changed by CTM based on the initialization tasks that are completed:
•In Service-Initializing—The NE is marked as In Service-Initializing when CTM reaches connectivity of the NE (Communication State is marked as Available) and the discovery process starts. The initialization process is completed when fault and inventory have been synchronized. The operational state changes from In Service-Initializing to In-Service Synch Configuration.
•In-Service Synch Configuration—The NE is marked as In-Service Synch Configuration when CTM uploads a configuration for that NE. You can change the operational state of an NE from In-Service Synch Configuration to Out of Service.
Step 3 Click Save.
Step 4 Click Yes in the confirmation dialog box.
Timesaver If an NE is brought down, mark it as Out of Service to prevent unnecessary polling traffic on the DCN.
Note When you mark an NE as Out of Service and then mark it as In Service, the CTM alarm time stamp in the Alarm Browser window is resynchronized with the time stamp when the NE is put back in service.
4.4.7 Setting Date, Time, and Location on CTC-Based NEs
Step 1 In the Domain Explorer, select an NE and choose Configuration > NE Explorer.
Step 2 In the node properties pane, click the Identification tab.
Step 3 In the Location area:
•Set the latitude of the NE by selecting North or South from the Latitude drop-down list; then, enter the degrees and minutes (or click the up or down arrow to increase or decrease each by 1 unit).
•Set the longitude of the NE by selecting East or West from the Longitude drop-down list; then, enter the degrees and minutes (or click the up or down arrow to increase or decrease each by 1 unit).
Step 4 In the Date and Time area:
•Time—Enter the date and time.
•Time Zone—From the drop-down list, select the time zone where the NE is located.
•Use Daylight Savings Time—When checked, Daylight Savings Time is observed.
Step 5 Click Apply.
4.4.7.1 Using the SNTP Server to Set the Date and Time
Simple Network Time Protocol (SNTP) is an internet protocol used to synchronize the clocks of computers to a time reference. Using the SNTP server ensures that all NEs use the same date and time reference. The server synchronizes the node's time after power outages or software upgrades. To use the SNTP server to set the date and time for CTC-based NEs, complete the following steps.
Step 1 In the Domain Explorer, select an NE and choose Configuration > NE Explorer.
Step 2 In the node properties pane, click the Identification tab.
Step 3 In the SNTP Settings area, do one of the following:
•Set up the SNTP server to set the date and time of the node:
–Check the Use NTP/SNTP Server check box.
–Enter the SNTP server's IP address.
•If you do not use the SNTP server, in the Date and Time area, enter the date and time in the Time field (for more information, see Setting Date, Time, and Location on CTC-Based NEs).
Step 4 Click Apply.
4.4.8 Configuring SNTP for Multiple NEs
Use the SNTP Configuration dialog box to provision a set of SNTP parameters on multiple NEs at the same time.
When the SNTP address setting on an NE fails, the reason for the failure is logged in the Error Log table. As part of a bulk SNTP operation, if the setting on an NE fails, CTM continues to set the SNTP server address on the remaining NEs that are part of the operation.
Note SNTP configuration is not available for ONS 15200, ONS 15216, CRS-1, or Catalyst 6509 NEs.
Step 1 In the Domain Explorer, choose Administration > SNTP Configuration. The SNTP Configuration dialog box opens. Table 4-15 provides descriptions.
Step 2 Enter the following information:
•NEs
•Job comments
•SNTP
•Time (time zone)
Step 3 Click Finish.
A job is scheduled for each NE that was assigned the SNTP server IP address. The job status is listed in the Job Monitor table. (For more details, see Viewing the Job Monitor Table.) The status of each SNTP set operation is updated as the job progresses. Job status can be one of the following:
•Queued—The job has been scheduled but has not yet been processed.
•Running—The job is being processed.
•Succeeded—The SNTP server IP address is set on the NE.
•Failed—The SNTP server IP address was not set on the NE. The reason for the failure is logged in the Error Log table.
•Waiting—The job is waiting for the NE to be in service.
Table 4-15 Field Descriptions for the SNTP Configuration Dialog Box
Field
|
Description
|
Network Elements
|
Use the Add and Remove buttons to move NEs to the Selected NEs list, or to remove NEs from the list. The SNTP server address is set on the NE(s) in the Selected NEs list.
|
Job Comments
|
Enter comments about the SNTP server address setting, if needed.
|
SNTP
|
Use the Resync Time (1530x only) field if you want the ONS 1530x NE to use the SNTP server to synchronize time information. The Resync Time field is the time passed between two synchronization operations. The NE uses this information to know when to synchronize with the SNTP server.
If you check the Use NTP/SNTP Server check box, CTM uses the NTP or SNTP server to set the date and time of the node. Using the NTP or SNTP server ensures that all NEs use the same date and time reference. After checking the check box, enter the server IP address in the SNTP IP Address field. If you do not check the Use NTP/SNTP Server check box, the NE stores the NTP or SNTP address but does not use it to synchronize time information.
|
Time (time zone)
|
Set a time for the SNTP address setting. Click Now to begin immediately, or click At Time and specify when to begin the SNTP set, specifying the month, day, year, hour, and minute in 5-minute increments.
Note The time zone can be GMT, a user-defined offset from GMT, or local time, depending on what is specified in the User Preferences dialog box.
|
4.4.9 Configuring Application-Specific Parameters
The UI Properties pane allows you to configure application-specific parameters.
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 In the Control Panel window, click UI Properties to open the UI Properties pane. Table 4-16 describes the fields in the UI Properties pane.
Step 3 Fill out the fields described in Table 4-16; then, click Save.
Table 4-16 Field Descriptions for the UI Properties Pane
Field
|
Description
|
Fault Management
|
•Alarm Acknowledgement—Allows you to specify automatic or manual alarm acknowledgement in the Alarm Browser window. If you choose manual alarm acknowledgment, you must manually acknowledge alarms. Cleared alarms move from the Alarm Browser to the Alarm Log. If you choose automatic alarm acknowledgment, the CTM server automatically acknowledges alarms when they are cleared and moves them from the Alarm Browser to the Alarm Log. Before alarms move to the Alarm Log, they must be both cleared and acknowledged.
Note You can still manually acknowledge alarms in automatic acknowledgement mode.
•Overwrite Alarm Notes—Enables or disables the ability to overwrite alarm notes created by another user.
•Alarm Unacknowledgement—Enables or disables the ability to unacknowledge alarms that have been acknowledged.
|
Circuit Management
|
Overwrite Circuit Notes: Enables or disables the ability to overwrite circuit notes created by another user.
|
Domain Management
|
Allows you to specify how node names longer than 25 characters are truncated in the Network Map. If a string is longer than 25 characters, the first 22 characters display followed by an ellipsis (...).You can choose to truncate the first or last characters of the node name.
|
CTC Management Domain
|
Allows you to manage the number of CTC instances for optimal CTC performance. The default is 10 CTC-based NEs.
Although CTM can support up to 2,500 CTC-based NEs, CTC cannot effectively manage more than a small subset of these NEs. Consequently, the CTM domain must be partitioned into smaller CTC domains with one instance of CTC launched per CTC domain. The specified number of CTC-based NEs determines the number of GNEs, or topology hosts, that constitute each CTC management domain. CTC uses the GNEs provided to discover and display other nodes that are physically connected to the GNEs. For example, if each CTC-based NE ring contains three NEs (including the GNE), CTC discovers and manages 3 x 10 = 30 nodes when the value is set to 10. In environments where most CTC-based NE rings or subnetworks contain 10 to 16 NEs, set this number to a smaller value, such as 3.
|
Subnetwork Grouping
|
Enables or disables the ability to automatically group NEs in subnetworks. If you check the Automatically Group NEs in Subnetworks check box, you cannot change the subnetwork of an NE, meaning:
•The option of selecting a subnetwork in the Add New NE wizard is disabled and shows <System Default>.
•The add NE process applies all automatic grouping rules.
•Drag-and-drop functionality is disabled on the Subnetwork Explorer.
•You cannot change the subnetwork assignment from the NE Properties pane.
Note During the transient period when this option is changed, any current operations (such as dropping an NE in a subnetwork) are completed.
|
Port State
|
If you check the Enable Port State Coloring check box, the NE Explorer shelf views and card-level views report the port and alarm status as a background color.
Note This feature is available only if the card is physically present on the NE and is provisioned in CTM.
|
4.5 How Do I Manage Redundancy and Failover?
This section contains the following information:
•Backing Up Memory
•Restoring Memory
•Viewing and Modifying NE Service Properties
•Restoring Server Configuration Files
•Configuring Nodes for Database Restore—ONS 15600
•Comparing Configuration Files—CRS-1
•Managing Protection Groups
•Restoring NE Defaults
4.5.1 Backing Up Memory
CTM allows you to back up memory for the following NEs:
•ONS 15216 EDFA2 (R2.3.0 and later)
•ONS 15216 EDFA3
•ONS 15310
•ONS 15327
•ONS 15454 SONET
•ONS 15454 SDH
•ONS 15530
•ONS 15540 ESP and ESPx
•ONS 15600 SONET
•ONS 15600 SDH
•CRS-1
Note The latest ONS 15216 EDFA2 R2.4 hardware does not support memory backup to a software release other than 2.4.0. The ONS 15216 EDFA2 R2.3 hardware supports memory backup for NE software releases 2.2.1, 2.3, and 2.4.
Note For the ONS 15530 and ONS 15540, the SNMP Community String table must have a valid write community string for the NE before memory can be backed up or restored. For more information, see Chapter 3, "Building the Network."
Note CTM R5.0 does not support memory backup for the ONS 15200, ONS 15302, ONS 15305, ONS 15501, ONS 15800, ONS 15801, ONS 15808, Catalyst 6509, or Not Managed/Other Vendor NEs.
The Memory Backup procedure backs up configuration and provisioning information residing in the flash memory of an NE. By default, the CTM server automatically backs up memory for NEs once a day for seven days and stores the backup files on the CTM server. After seven days, the oldest backup file is replaced by the current backup. For more information, see Configuring Automatic NE Backup Parameters.
Step 1 In the Domain Explorer tree, select a management domain or group that contains an NE that is assigned an In Service or Under Maintenance operational state. Alternatively, select an NE that is assigned an In Service or Under Maintenance state.
Note Memory backup is not allowed for preprovisioned or out-of-service NEs.
Step 2 Choose Administration > Memory Backup.
Step 3 The Memory Backup dialog box opens. Enter the following information (see Table 4-17 for details):
•NE model
•Selected NEs
•Job comments
•Tag name
•Time (time zone)
Note For the ONS 15216 EDFA2, the backup file must be saved in the default directory, such as the tftpboot directory on the remote TFTP server, in case the file will be restored from the remote TFTP server. The tftpboot directory must have read-write access, or the backup job will fail. See Chapter 3, "Building the Network" for information about how to configure the tftp directory with read-write access.
Note The time zone can be GMT, a user-defined offset from GMT, or local time, depending on what is specified in the User Preferences dialog box.
Step 4 Depending on the type of NE, do one of the following:
•For ONS 15530 and ONS 15540 NEs, proceed to Step 5.
•For ONS 15600 NEs, proceed to Step 6.
•For CRS-1, ONS 15216, ONS 15310, ONS 15327, ONS 15454 SONET, or ONS 15454 SDH NEs, click Finish to initiate the memory backup procedure.
•For the CRS-1, the backed up config files are archived in a directory under $CTM_HOME/admin/<NE_system_ID>. The following naming convention is used for versioning/tagging config files:
<NE_TYPE>-<USER_TAG>-<DATE_AND_TIME>-<JOB_TYPE>.cfg
where
–NE_TYPE is the type of managed NE.
–USER_TAG is the user-specified tag name. You can specify any string here.
–DATE_AND_TIME is the year, month, day, and time, in YYYYMMDDHHMMSS format. For example, 20030610151159 means that the file was archived on June 10, 2003 at 3:11:59 PM.
–JOB_TYPE is auto for automatic jobs, backup/restore for manually created jobs, and CONFIG-CHANGE when the configuration file is backed up after receiving a CONFIG_CHANGE notification.
•For the ONS 15216, the configuration file is copied to the $CTMHOME/admin/<NE_system_ID>/15216-<tag_name>-<time_stamp>-backup.cfg file.
•For the ONS 15310, the configuration file is copied to the $CTMHOME/admin/<NE_system_ID>/15310-<tag_name>-<time_stamp>-backup.cfg file.
•For the ONS 15327, the configuration file is copied to the $CTMHOME/admin/<NE_system_ID>/15327-<tag_name>-<time_stamp>-backup.cfg file.
•For the ONS 15454 SONET or ONS 15454 SDH, the configuration file is copied to the $CTMHOME/admin/<NE_system_ID>/15454-<tag_name>-<time_stamp>-backup.cfg file.
Note If System Default is chosen for the tag name, the tag is left blank and the filename is, for example, 15454--backup.cfg. If User Specified is chosen and hello is entered for the tag name, the filename is 15454-hello-<YYYYMMDDHHMM>-backup.cfg, where YYYYMMDDHHMM is the backup date, consisting of:
YYYY—Four-digit year
MM—Two-digit month
DD—Two-digit day
HH—Two-digit hour (in 24-hour format)
MM—Two-digit minute
Step 5 For ONS 15530 and ONS 15540 NEs:
a. Click Next to display memory backup options. Select an option (see Table 4-17 for details):
•Running Configuration
•Startup Configuration
•Save Running Config as Startup Config on NE
b. Click Finish to initiate the memory backup procedure.
The configuration file for each NE is copied to the $CTMHOME/admin/<NE_system_ID>/ 155xx-<tag>-<time_stamp>-<slot_number_of_active_CPU>-[ running | startup].cfg file, where:
•$CTMHOME is the installation directory (by default, the installation directory is /opt/CiscoTransportManagerServer).
•NE_system_ID is the hostname of the ONS 15501, ONS 15530, or ONS 15540.
•tag-time_stamp is the user-defined tag name and includes the time stamp. If System Default is selected, the tag is left blank and the filename is, for example, 15540-<time_stamp>-slot6-startup-backup.cfg. If User Specified is selected and hello is entered as the tag name, the filename is 15540-hello<YYYYMMDDHHMM>-slot6-startup.cfg, where YYYYMMDDHHMM is the time stamp.
The tag time stamp is ignored when the running configuration is saved as the startup configuration, because this operation is done on the NE itself and no backup file is saved on the CTM server.
•slot_number_of_active_CPU is the slot number of the active CPU at the time of job execution. If the slot number cannot be obtained, the filename is 15540-<tag>-<time_stamp>-[ running | startup ].cfg.
•running or startup is the memory backup option chosen.
Note The automatic backup files are named 155xx-<time_stamp>-<slot_number>-
[ running | startup ].cfg.
Step 6 For ONS 15600 SONET and ONS 15600 SDH NEs:
a. Click Next to display memory backup options. Select the category of data to back up (see Table 4-17 for details):
•Provisioning data (is selected by default and is read-only)
•Alarm data
•PM data
b. Click Finish to initiate the memory backup procedure.
The configuration file is copied to the $CTMHOME/admin/<NE_system_ID>/15600-<tag_name>-<time_stamp>-backup.cfg file.
After scheduling the backup, look at the Job Monitor table (Administration > Job Monitor) to see the job status. If the job fails, the Additional Information field in the Job Monitor table provides extra information.
If a memory backup job fails, the EMS raises an alarm. All prior memory backup failure EMS-generated alarms on an NE are cleared under the following conditions:
•After a successful memory backup operation on the NE
•When the operational state of the NE changes to Out of Service
Table 4-17 Field Descriptions for the Memory Backup Dialog Box
Field
|
Description
|
NE Model
|
Select the NE type that you want to back up. The type you select determines the NEs that are displayed in the Network Elements area.
|
Available NEs
|
Use the Add and Remove buttons to move the NEs that you want to back up to the Selected NEs list, or to remove NEs from the list.
|
Job Comments
|
Enter comments about the backup, if needed.
|
Tag Name
|
Add a tag to the system-generated filename. If you select System Default, no tag name is added. If you select User Specified, you can enter a tag name.
|
Time (time zone)
|
Set a time for the backup. Click Now to begin backup immediately, or click At Time and specify when to begin backup, in 5-minute increments.
Note The time zone can be GMT, a user-defined offset from GMT, or local time, depending on what is specified in the User Preferences dialog box.
|
Memory Backup Dialog Box 2 for ONS 15530 and ONS 15540 NEs
|
Running Configuration
|
Copies the running configuration of the active CPU to the backup file. The backup file is saved in the $CTMHOME/admin/<NE_system_ID> directory. The CPU slot number is included in the filename. If you selected a tag name, the tag and time stamp are included in the filename. For example, if the active CPU is in slot 6, the filename is 15540-<tag>-<time_stamp>-slot6-running-backup.cfg.
|
Startup Configuration
|
Copies the startup configuration of the active CPU to the backup file. The startup configuration is stored in NVRAM and used when the NE reboots. The backup file is saved in the $CTMHOME/admin/<NE_system_ID> directory. The CPU slot number is included in the filename. If you selected a tag name, the tag and time stamp are included in the filename. For example, if the active CPU is in slot 6, the filename is 15540-<tag>-<time_stamp>-slot6-startup-backup.cfg.
|
Save Running Config as Startup Config on NE
|
Saves the running configuration as the startup configuration on the NE itself. The user-defined tag name is ignored. This is the equivalent of the write mem CLI command.
|
Memory Backup Dialog Box 2 for ONS 15600 SONET and ONS 15600 SDH NEs
|
Provisioning Data
|
(Read-only) Backs up the ONS 15600 provisioning data.
|
Alarm Data
|
If checked, the ONS 15600 alarm data is backed up.
|
PM Data
|
If checked, the 15-minute and 1-day PM data for the ONS 15600 is backed up.
|
4.5.2 Restoring Memory
Use the Memory Restore dialog box to restore provisioning and configuration information stored in the flash memory of the following NEs. (This information is backed up by using the Memory Backup dialog box.)
•ONS 15216 EDFA2 (EDFA2 R2.3.0 and later)
•ONS 15216 EDFA3
•ONS 15310
•ONS 15327
•ONS 15454 SONET
•ONS 15454 SDH
•ONS 15530
•ONS 15540 ESP and ESPx
•ONS 15600 SONET
•ONS 15600 SDH
•CRS-1
Note The latest ONS 15216 EDFA2 R2.4 hardware does not support memory restore to a software release other than 2.4.0. The ONS 15216 EDFA2 R2.3 hardware supports memory restore for NE software releases 2.2.1, 2.3, and 2.4.
Note For the ONS 15530 and ONS 15540, the SNMP Community String table must have a valid write community string for the NE before memory can be restored. For more information, see Chapter 3, "Building the Network."
Note CTM R5.0 does not support memory restoration for the ONS 15200, ONS 15302, ONS 15305, ONS 15501, ONS 15800, ONS 15801, ONS 15808, Catalyst 6509, or Not Managed/Other Vendor NEs.
Step 1 In the Domain Explorer tree, select an NE that is assigned an In Service or Under Maintenance operational state.
Note Run the Memory Restore procedure for one NE at a time. Memory restore for preprovisioned or out-of-service NEs is not allowed.
Step 2 Choose Administration > Memory Restore. The Memory Restore dialog box opens.
Step 3 Enter the following information (see Table 4-19 for details):
•NE model
•NEs (select only one)
•Source
•Job comments
•Time
Step 4 Depending on the type of NE, do one of the following:
•For the ONS 15310, ONS 15327, ONS 15454 SONET, or ONS 15454 SDH, proceed to Step 5.
•For the ONS 15530 or ONS 15540, proceed to Step 6.
•For the ONS 15600 SONET or ONS 15600 SDH, proceed to Step 7.
•For the CRS-1, ONS 15216 EDFA2, or ONS 15216 EDFA3, click Finish.
Step 5 For the ONS 15310, ONS 15327, ONS 15454 SONET, or ONS 15454 SDH, click Next to verify the following file properties:
•Node description
•Node name
•Node type
•IP address
•Software version
CTM performs a compatibility check. Table 4-18 lists the compatibility factors and the corresponding action. The restore operation is not allowed if the NEs are of different types or if the software version is incompatible.
Table 4-18 Compatibility Factors for Memory Restore
Compatibility Factor
|
Action
|
Different NE type
|
Finish button is disabled; click Cancel.
|
Incompatible software version
|
Finish button is disabled; click Cancel.
|
Different node name
|
CTM displays a warning message. You can click Finish to proceed with the restore operation or Cancel to cancel the operation.
|
Different software version
|
CTM displays a warning message. You can click Finish to proceed with the restore operation or Cancel to cancel the operation.
|
Caution Restoring the memory of an NE using an incompatible or corrupted file might cause loss of traffic or loss of connectivity.
Step 6 For an ONS 15530 or ONS 15540:
a. Click Next to display the memory restore options. Select an option (see Table 4-19 for details):
•Running configuration
•Startup configuration
b. Click Finish to initiate the memory restore procedure.
Step 7 For the ONS 15600 SONET or ONS 15600 SDH:
a. Click Next to display the memory restore options. Select the category of data to restore (see Table 4-19 for details):
•Provisioning data (is selected by default and is read-only)
•Alarm data
•PM data
b. Click Finish to initiate the memory restore procedure.
To view the results of the memory restore operation, open the Job Monitor table. For information about the Job Monitor table, see Monitoring Scheduled Tasks.
Table 4-19 Field Descriptions for the Memory Restore Dialog Box
Field
|
Description
|
NE Model
|
Select the NE model that you want to restore. The model you select determines the NEs that are displayed in the Network Elements field.
|
Network Elements
|
Use the Add and Remove buttons to move the NE that you want to restore to the Selected NE list. You can run the Memory Restore procedure for only one NE at a time.
|
Source
|
Specify the location of the backup file that you want to use to restore the NE:
•Click Local to browse a local client directory for the backup file.
•Click Server to restore the file from the CTM server. The files shown are in the directory /opt/CiscoTransportManagerServer/admin/<NE_system_ID>.
Note The Server radio button is not active unless a file exists in that directory.
•Click Remote TFTP Server Address to restore from another network server. (The Remote option is not supported for CTC-based NEs.) In the first field, enter the IP address of the TFTP server. In the second field, enter the fully qualified pathname of the backup file to be restored, relative to the tftpboot directory. TFTP must be configured and running on the network server. The Remote option is supported for the ONS 15216 EDFA2 (EDFA2 R2.3.0 and later).
Note If the Remote TFTP Server option is selected for the ONS 15216 EDFA, the backup file that you are restoring must have been saved in the default directory, such as the tftpboot directory on the remote TFTP server.
Note The tftpboot directory must have read-write access, or the restore job will fail. See Chapter 3, "Building the Network" for information about how to configure the tftp directory with read-write access.
•Click Remote FTP Server Address to restore from any UNIX workstation that is running FTP. This option requires authentication. In the first field, enter the IP address of the FTP server. In the second field, enter the fully qualified pathname of the backup file to be restored, relative to the FTP directory. In the third field, enter the FTP username. In the last field, enter the FTP user password. The Remote FTP Server option is supported only for the ONS 15216 EDFA3.
|
Job Comments
|
Enter comments about the restore procedure, if needed.
|
Time (time zone)
|
Set a time for memory restore. Click Now to begin memory restore immediately, or click At Time and specify when to begin memory restore, in 5-minute increments.
Note The time zone can be GMT, a user-defined offset from GMT, or local time, depending on what is specified in the User Preferences dialog box.
|
Memory Restore Dialog Box 2 for ONS 15530 and ONS 15540 NEs
|
Running Configuration
|
Restores the currently running configuration of the NE.
Note Configuration file commands are added to the current running configuration on the NE. The running configuration is not replaced by the configuration file.
|
Startup Configuration
|
Restores the startup configuration of the NE. This operation entirely replaces the startup configuration file.
|
Memory Restore Dialog Box 2 for ONS 15600 SONET and ONS 15600 SDH NEs
|
Provisioning Data
|
(Read-only) Restores the ONS 15600 provisioning data.
|
Alarm Data
|
If checked, the ONS 15600 alarm data is restored.
|
PM Data
|
If checked, the 15-minute and 1-day PM data for the ONS 15600 is restored.
|
4.5.3 Viewing and Modifying NE Service Properties
The NE Service pane in the Control Panel window allows you to view and update CTM server configuration information, which includes port information, timing parameters, and NE backup parameters. You can also stop or start an individual NE service instance.
All server configuration changes take effect when you save them, with the exception of changes to the CTM server port. Port information changes require that you restart the CTM server before the change takes effect. The NE Service pane contains the following tabs:
•NE Poller—Allows you to change timing parameters and port information
•NE AutoBackup—Allows you to configure automatic NE backup parameters
•NE Manual Backup—Allows you to configure manual NE backup parameters
Note CTM is limited to running a maximum number of 23 Java processes. Enter the showctm command to view the current number of running processes.
4.5.3.1 Understanding the Unmanaged NE Service
Unmanaged NEs have their own NE Service. This Unmanaged NE Service allows CTM to support unmanaged NE devices that are not in the Supported NE Table. Unmanaged NEs can be Cisco or non-Cisco devices. The Unmanaged NE service is required for operations such as:
•Creating manual links between managed and unmanaged NEs
•Creating manual links between unmanaged NEs
•Changing the operational state of unmanaged NEs.
Note Passive NEs such as the ONS 15216 EDFA1 are not considered unmanaged NEs.
4.5.3.2 Changing Timing Parameters
Use the NE Service pane to tune timing parameters and accommodate different CTM server-to-NE connectivity scenarios. When timing parameters are tuned, network utilization and CTM server load are optimized. As a rule, timing parameters increase as the network slows.
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 In the Control Panel window, click NE Service to open the NE Service pane. Table 4-20 describes the fields in the NE Service pane.
Step 3 Click the NE Poller tab. Enter the following information:
•CTM server port
•NE health poll interval
Step 4 In the Control Panel window, expand the NE Service and click an NE. Table 4-21 describes the fields in the ONS NE Service pane.
Step 5 In the Resync Scheduling area of the ONS NE Service pane, enter the interval at which the configuration is retrieved and processed. This field is not available for CRS-1, unmanaged, or Catalyst 6509 NEs.
Note The default values are adequate for most network configurations. Decreasing the values of the parameters could have an adverse impact on server performance.
Step 6 Click Save. Changes take effect immediately.
Table 4-20 Field Descriptions for the NE Service Pane
Field
|
Subfield
|
Description
|
NE Poller Tab
|
Port Information
|
CTM Server Port
|
Displays the TCP port number of the CTM server. The Active field displays the current port; the After Restart field displays the port that is active after the server is rebooted.
|
Timing Parameters
|
NE Health Poll Interval
|
Displays the NE polling interval (in seconds). The default is 240 seconds (4 minutes).
|
NE AutoBackup Tab
|
Select Modify Mode
|
—
|
Allows you to specify whether the automatic backup should apply to a specific NE model (ONS 15216 EDFA2 [R2.3.0 and later], ONS 15216 EDFA3, ONS 15310, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS 15530, ONS 15540 ESP, ONS 15540 ESPx, ONS 15600 SONET, ONS 15600 SDH, or CRS-1) or to all applicable NE models.
|
Configuration Parameters
|
NE Model
|
If NE Model is selected under Select Modify Mode, this field allows you to specify the NE model that will be backed up automatically.
|
Enable Auto Backup
|
If checked, the system automatically backs up all NE models, or a specific NE model. When NE AutoBackup State is set to Enabled, an entry is added to the Job Monitor table with a new job ID and a new task ID for each NE. Scheduled Time is set to the selected autobackup time and Task Status is set to Queued. When the autobackup time is reached and the task begins, Task Status is set to Running. After the backup is complete, Task Status is set back to Queued and Scheduled Time is reset to the time and date of the next scheduled backup time. When NE AutoBackup State is set to Disabled, Task Status is set to Cancelled. The default state is Disabled.
|
Backup Frequency
|
(Read-only) Indicates the interval in days between subsequent backups. The backup frequency is set to 1, meaning that a backup is performed every day at the time specified in the Backup Time field.
|
No. of Backup copies
|
Allows you to specify the number of backup copies to keep (the default is 7). Only automatic backup copies count toward the total number of backup copies saved; manual backup copies do not count toward the total.
For ONS 15530 and ONS 15540 NEs, the total number of backup copies includes both running and startup configuration files. For example, if you want to keep 7 copies of each configuration file, you should set the number of copies to 14.
Each time CTM creates a new backup file, it checks the existing number of backup copies. CTM deletes files as needed, beginning with the oldest file, so as not to exceed the specified number of backup copies to keep.
|
Backup Time
|
Allows you to set the time when the automatic backup will be performed.
|
Backup Data (available only if ONS 15600 SONET or SDH is selected as the NE model)
|
—
|
Allows you to select provisioning data, alarm data, PM data, and/or audit log data to back up.
|
NE Manual Backup Tab
|
Select Modify Mode
|
—
|
Allows you to specify whether the manual backup should apply to a specific NE model (ONS 15216 EDFA2 [R2.3.0 and later], ONS 15216 EDFA3, ONS 15310, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS 15530, ONS 15540 ESP, ONS 15540 ESPx, ONS 15600 SONET, ONS 15600 SDH, or CRS-1) or to all applicable NE models.
|
Configuration Parameters
|
NE Model
|
If NE Model is selected under Select Modify Mode, this field allows you to specify the NE model that will be backed up manually.
|
No. of Backup Copies
|
Allows you to specify the number of backup copies to keep (the default is 7).
Each time CTM creates a new backup file, it checks the existing number of backup copies. CTM deletes files as needed, beginning with the oldest file, so as not to exceed the specified number of backup copies to keep.
|
Table 4-21 Field Descriptions for the ONS NE Service Pane
Field
|
Description
|
Service Status
|
Displays the current status of the service: Active or Not Active.
|
Service Action
|
Allows you to stop or start a process. Notice that the Service Action button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
|
Error Level
|
Allows you to choose the error level for alarms on the selected NE to include in the error log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Caution CTM performance will degrade significantly if the trace or debug option is left on. All operations will slow down and you may lose alarm and event notifications. Use trace or debug only when troubleshooting with a customer support engineer.
|
Threshold
|
Displays the maximum number of NEs that each NE service instance can manage. The threshold depends on the NE type, as follows:
•ONS 15200 NE Service can manage up to 1000 ONS 15200 NEs.
•ONS 15216 NE Service can manage up to 1000 ONS 15216 NEs.
•ONS 15302 NE Service can manage up to 1000 ONS 15302 NEs.
•ONS 15305 NE Service can manage up to 1000 ONS 15305 NEs.
•ONS 15310/ONS 15327/ONS 15454 SONET/ONS 15600 SONET NE Service can manage up to 400 ONS 15310, ONS 15327, ONS 15454 SONET, or ONS 15600 SONET NEs (for NE releases earlier than R5.0).
Note For NE release 5.0 in a large or high-end configuration, the NE Service can manage up to 500 NEs.
•ONS 15454 SDH/ONS 15600 SDH NE Service can manage up to 600 ONS 15454 SDH or ONS 15600 SDH NEs.
•ONS 155xx NE Service can manage up to 1000 ONS 155xx NEs.
•ONS 15800 NE Service can manage up to 1000 ONS 15800 NEs.
•ONS 15801 NE Service can manage up to 1000 ONS 15801 NEs.
•ONS 15808 NE Service can manage up to 1000 ONS 15808 NEs.
•CRS-1 NE Service can manage up to 1000 CRS-1 NEs.
•Unmanaged NE Service can manage up to 500 unmanaged NEs.
•Catalyst 6509 NE Service can manage up to 1000 Catalyst 6509 NEs.
|
Resync Scheduling (not applicable to CRS-1, unmanaged, or Catalyst 6509 NEs)
|
Allows you to specify a schedule for database resynchronization for each NE model. A schedule consists of the following configurable parameters:
•Days of the week to run: All, Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday. Check the check box next to the day(s) to run the configuration resynchronization.
•Time of day to initiate the resynchronization, in HH:MM AM/PM format (specific format based on locale).
•Interval between synchronizations, in HH:MM format. The maximum interval is 24:00; the minimum is 5:00. The resync interval is calculated only until the end of the day. The schedule for the next day takes effect after the end of the current day. For example, if you choose Wednesday with a start time of 10:00 AM and an interval of 6 hours, the resync occurs at 10:00 AM, 4:00 PM, and 10:00 PM on Wednesdays.
Note The Last Resync field shows when the NE was last synchronized.
|
Bandwidth Utilization Report (CTC-based NEs only)
|
Check the Enable Bandwidth Data Service Provisioning (DSP) check box to enable the bandwidth check during L2 service provisioning. The bandwidth utilization report shows available and used bandwidth for each L2 topology. This report can be used during L2 service provisioning to verify whether the requested Committed Information Rate (CIR) is available on the topology. Based on the report, an error is returned if there is not enough bandwidth available for a drop port.
|
Robust Fault Synchronization (CTC-based NEs only)
|
Allows you to enable or disable the robust fault synchronization for the ONS 15310, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS 15600 SONET, and ONS 15600 SDH.
|
BSLR-Ring/MS-SPRing Exercise Interval (CTC-based NEs only)
|
Allows you to set the BLSR or MS-SPRing exercise interval. The interval is measured in seconds. The default is 60 seconds.
|
Audit Trail Collection Interval (CTC-based NEs only)
|
Allows you to set the audit trail collection interval. The collection interval is measured in minutes.
|
L2 Service Resync Delay (CTC-based NEs only)
|
Allows you to configure the delay after which CTM performs an IOS configuration synchronization on ML cards to keep the NE and the CTM Data Provisioning Service synchronized.
Full Cisco IOS configuration synchronization is performed automatically by CTM to keep the NE and the CTM Data Provisioning Service synchronized. Full configuration resynchronization may be delayed depending on CTM server usage. For the CTM server deployed as the monitoring server, the recommended value for the delay parameter is 120 seconds. For the CTM server deployed as provisioning server, the recommended value for the delay parameter is 10 minutes (600 seconds).
|
NE Service Instance
|
Start Service Instance, Stop Service Instance
|
Allows you to stop or start an individual NE service instance. If you click Start Service Instance, the service status changes to Running. If you click Stop Service Instance, the status changes to Stopped.
The list of managed NEs shows which NEs are being managed by the selected service instance. If you stop the specified service instance, the NEs in the list are no longer managed.
|
4.5.3.3 Configuring Automatic NE Backup Parameters
CTM can be configured to automatically back up ONS 15216 EDFA2, ONS 15216 EDFA3, ONS 15310, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS 15530, ONS 15540 ESP, ONS 15540 ESPx, ONS 15600 SONET, ONS 15600 SDH, and CRS-1 NEs once a day.
Automatic backup files are saved in the following locations and have the following names:
•$CTMHOME/admin/<NE_system_ID>/15216-<YYYYMMDDHHMM>-auto.cfg
•$CTMHOME/admin/<NE_system_ID>/15310-<YYYYMMDDHHMM>-auto.cfg
•$CTMHOME/admin/<NE_system_ID>/Cisco_ONS_15327-<YYYYMMDDHHMM>-auto.cfg
•$CTMHOME/admin/<NE_system_ID>/15454-<YYYYMMDDHHMM>-auto.cfg
•$CTMHOME/admin/<NE_system_ID>/[ 15530 | 15540 ]-<YYYYMMDDHHMM>-
<Active_CPU_slot_number>-[ running | startup ]-auto.cfg
•$CTMHOME/admin/<NE_system_ID>/15600-<YYYYMMDDHHMM>-auto.cfg
•$CTM_HOME/admin/<NE_system_ID>/CRS1-<USER_TAG>-<DATE_AND_TIME>-auto.cfg
where:
•<YYYYMMDDHHMM> is the date of the backup:
–YYYY is the four-digit year
–MM is the two-digit month
–DD is the two-digit day
–HH is the two-digit hour (in 24-hour format)
–MM is the two-digit minute
For example, 4:01 p.m. on September 29, 2004 is represented as 200409291601.
•<Active_CPU_slot_number> is the slot number of the active CPU at the time of job creation.
•[ running | startup ] indicates whether the backup is of the NE's running configuration or startup configuration.
•<USER_TAG> is the user-specified tag name (for CRS-1).
•<DATE_AND_TIME> is the year, month, day, and time (for CRS-1). For example, 20030610151159 means that the file was backed up on June 10, 2003 at 3:11:59 PM.
Note Automatic backup is not available for the ONS 15200, ONS 15501, ONS 15800, ONS 15801, ONS 15808, or Catalyst 6509.
Use the NE Service pane to set automatic NE backup parameters.
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 In the Control Panel window, click NE Service to open the NE Service pane. Click the NE AutoBackup tab. Table 4-20 describes the fields in the NE AutoBackup tab.
Step 3 Enter the following information:
•Select Modify Mode
•NE Model
•Enable Auto Backup
•Backup Frequency
•No. of Backup Copies
•Backup Time
•Backup Data (available only if ONS 15600 SONET or SDH is selected as the NE model)
Step 4 Click Save. Changes take effect immediately; however, the backup already scheduled for the next 24 hours remains in effect. A backup with the new parameters will occur after the previously scheduled backup runs.
Note To verify whether CTM is automatically backing up the NE, go to the Job Monitor table, verify that the task is listed, and check its task status. If automatic backup for an NE failed, the task status will be "Failed." This failure is logged in the Audit Log and an alarm is generated.
Note If the CTM server restarts after the scheduled automatic backup time for that day, CTM automatically schedules a backup for all ONS 15327, ONS 15454 SONET, ONS 15530, and ONS 15540 NEs to take place five to ten minutes after the restart. Conversely, if the server restarts before the scheduled backup time for that day, the backup occurs at the regularly scheduled time. This behavior ensures that a backup is performed for each NE at least once a day.
For example, if the automatic backup time is set for 2:00 a.m. and the CTM server restarts at 8:00 p.m., the server schedules a backup five to ten minutes after the restart because the backup time is earlier than the restart time on the same day. As another example, if the automatic backup time is set for 11:00 p.m. and the CTM server restarts at 8:00 p.m., the server waits until 11:00 p.m. to run the backup because the backup time is later than the restart time.
An entry is added to the Audit Log for each successful completion or failed NE autobackup task.
4.5.3.4 Configuring Manual NE Backup Parameters
Use the NE Service pane to set manual NE backup parameters.
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 In the Control Panel window, click NE Service to open the NE Service pane. Click the NE Manual Backup tab. Table 4-20 describes the fields in the NE Manual Backup tab.
Step 3 Enter the following information:
•Select Modify Mode
•NE Model
•No. of Backup Copies
Step 4 Click Save. Changes take effect immediately; however, the backup already scheduled for the next 24 hours remains in effect. A backup with the new parameters will occur after the previously scheduled backup runs.
4.5.4 Restoring Server Configuration Files
Step 1 Log into the server workstation as the root user.
Step 2 On the command line, enter the following:
cd/opt/CiscoTransportManagerServer/bin
./restore_config.sh /_backup / <log_directory> ISHA
Note If the server is a high availability (HA) server, the ISHA value is 1. If the server is not an HA server, the ISHA value is 0.
4.5.5 Configuring Nodes for Database Restore—ONS 15600
Use the Configure Node dialog box to configure the selected ONS 15600 SONET or ONS 15600 SDH node. This feature is essentially a database restore without the check for a matching node ID, software version, and IP address. Additionally, you can specify that a new IP address overrides the IP address in the database. When the node reboots after the database has been downloaded, it uses the new IP address you specified. Only the provisioning database is restored from the ONS 15600 database file, which can contain provisioning, alarm, PM, and audit databases.
Step 1 In the Domain Explorer tree, select an ONS 15600 SONET or ONS 15600 SDH NE that is assigned an In Service or Under Maintenance operational state. You cannot configure nodes for preprovisioned or out-of-service NEs.
Step 2 Choose Configuration > CTC-based SONET NEs or CTC-based SDH NEs > Configure Node. The Configure Node dialog box opens. Table 4-22 provides descriptions.
Step 3 Enter the following information:
•NE model
•Selected NE
•Source
•Job comments
•Time
Step 4 Click Next.
Step 5 Verify the configuration. If necessary, change the IP address with which the new node will be configured.
Step 6 Click Finish.
To view the results of the node configuration, check the Job Monitor table. For more information about the Job Monitor table, see Monitoring Scheduled Tasks.
Table 4-22 Field Descriptions for the Configure Node Dialog Box
Field
|
Description
|
NE Model
|
Select the NE type that you want to configure. The type you select determines the NEs that are displayed in the Network Elements field.
Note You can only select ONS 15600 SONET or ONS 15600 SDH.
|
Network Elements
|
Use the Add and Remove buttons to move the NE that you want to configure to the Selected NE list. You can run the node configuration procedure for only one NE at a time.
|
Source
|
Specify the location of the backup file that you want to use to configure the NE:
•Click Local to browse to a local client directory for the backup file.
•Click Server to configure the file from the CTM server. The files shown are in the directory /opt/CiscoTransportManagerServer/admin/<NE_system_ID>. The Server radio button is not active unless a file exists in that directory.
Note The Remote options are disabled and do not apply.
|
Job Comments
|
Enter comments about the node configuration procedure, if needed.
|
Time (time zone)
|
Set a time for the node configuration. Click Now to begin node configuration immediately, or click At Time and specify when to begin node configuration (in 5-minute increments).
Note The time zone can be GMT, a user-defined offset from GMT, or local time, depending on what is specified in the User Preferences dialog box.
|
Current Node Configuration
|
(Read-only) Displays the NE software version and IP address of the current node.
|
Memory Configuration
|
(Read-only) Displays the NE software version and IP address in the database file provided for configuring the node. The check box shows that only provisioning data will be considered for restoration.
|
New Node Configuration
|
Displays the NE software version and IP address with which the new node will be configured. By default, the IP address is the same as that of the current node. You can modify the IP address.
|
4.5.6 Comparing Configuration Files—CRS-1
Use the Compare Configuration Files dialog box to view differences between:
•Two versions of a configuration file for a single NE
•Two versions of configuration files for different NEs
Step 1 In the Domain Explorer tree, select a CRS-1 and choose Administration > Compare Config Files. The Compare Configuration Files dialog box opens. Table 4-23 describes the fields in the dialog box.
Step 2 In the Compare Option area, specify whether you want to compare two configuration files on the same NE, or two configuration files on different NEs.
Step 3 In the Network Elements area, designate the first (and second, if applicable) NE for the file comparison.
Step 4 In the Configuration Files area, select the configuration filenames present in the archived directory for the first and second NEs.
Step 5 Click OK.
A fully configured CRS-1 could be several megabytes in size. The configuration file comparison should not take longer than 10 minutes. If the comparison takes longer than 30 seconds, a progress bar tracks the progress.
The Configuration Compare Output screen (see Figure 4-1) shows the results of the comparison, with the following conventions:
•Changed lines are shown in red.
•New lines are shown in blue.
•The toolbar contains Find and Find Next buttons to search for text.
•The toolbar contains Go First, Go Last, Go Back, and Go Forward buttons to page through the output file.
•A vertical scroll bar allows you to scroll through the output file.
•The output is titled with the device name. For example, to compare different devices, the title might be crs1-3:<Tag_Name>-<suffix> and crs1-4:<Tag_Name>-<suffix>, where suffix is backup or auto.
Table 4-23 Field Descriptions for the Compare Config Files Dialog Box
Area
|
Field
|
Description
|
Compare Option
|
Two archived versions of same NE
|
When selected, two configuration file versions on the same NE are compared. (Notice that the Second Network Element list items are grayed out.)
|
Two archived versions of different NEs
|
When selected, two configuration file versions on separate NEs are compared.
|
Network Elements
|
First Network Element
|
List of available NEs to select as the first NE for the configuration file comparison.
|
Second Network Element (not available if Two archived versions of same NE is selected)
|
List of available NEs to select as the second NE for the configuration file comparison.
|
Configuration Files
|
First Configuration File, Second Configuration File
|
List of configuration filenames present in the archived directory ($CTM_HOME/admin/<NE_system_ID>) for the first and second NEs.
Filenames have the following format:
<NE_TYPE>-<USER_TAG>-<DATE_AND_TIME>-<JOB_TYPE>.cfg
where
•NE_TYPE is the type of managed NE.
•USER_TAG is the user-specified tag name.
•DATE_AND_TIME is the time stamp that shows when the file was archived, in YEAR MONTH DAY TIME format. For example, 20040610151147 means the file was archived on June 10, 2004 at 3:11:47 PM.
•JOB_TYPE has one of the following values:
–auto: For automatic jobs.
–backup/restore: For manually created jobs.
–CONFIG-CHANGE-auto: A configuration change notification is received and automatic backup of the configuration file is enabled. The configuration file is backed up and stored with this tag.
|
Figure 4-1 Configuration Compare Output Screen
4.5.7 Managing Protection Groups
A protection group allows you to group modules together, so that if one module goes down for some reason, the other modules will be protected and will not go down as well. The following sections describe how to create, enable, edit, and delete protection groups.
4.5.7.1 Creating Protection Groups
Step 1 Select a CTC-based NE and choose Configuration > NE Explorer.
Step 2 In the NE Explorer window, click the Protection tab.
Step 3 In the Protection Groups subtab, click Create. The Create Protection Group dialog box opens. Table 4-24 provides descriptions. Fields shown depend on the type of NE that is selected.
Step 4 Specify the following information:
•Name
•Type
•Protect module
Caution If you are using CTM GateWay/CORBA, make sure that you do not create multiple protection groups with the same name. CTM GateWay/CORBA cannot distinguish between multiple protection groups with the same name while executing a delete protection group command or a perform protection switch command.
Note 1:N protection is not supported for the ONS 15327.
Based on these selections, a list of available working cards or ports is displayed.
Step 5 From the Available Entities list, choose the card or port that will be the working card or port. Click the arrow button to move each card or port to the Working Entities list.
Step 6 Complete the remaining information:
•Bidirectional switching
•Revertive
•Reversion time
•Recovery guard time
•Verification guard time
•Detection guard time
Step 7 Click OK.
Caution Before running traffic on a protected card within a protection group, enable the ports of all protection group cards.
Note After creating a protection group on DS3XM-6 cards, wait for two minutes while CTM receives updates for all of the ports supported by the DS3XM-6 cards. The protection group is not visible in CTM until the two-minute update period is complete.
Note The ONS 15600 SONET must have cards carrying live traffic in order to switch protection. Even a forced switch will be overridden by a failed signal. You cannot perform manual and forced switches on an ONS 15600 using preprovisioned cards. If you try to perform a switch using preprovisioned cards, the NE returns an error, and the protection operation does not switch from Active to Protect. An APS_CLEAR is generated, which can be cleared.
Table 4-24 Field Descriptions for the Create Protection Group Dialog Box
Field
|
Description
|
Name
|
Enter a name for the protection group. The name can have up to 32 alphanumeric characters.
|
Type
|
Choose the protection type from the drop-down list:
•1:1 [card]
•1:N [card]
•Y Cable [port]
•1+1 [port]
•1+1 Optimized (port)
The protection selected determines the cards that are available to serve as protect and working cards. For example, if you choose 1:N protection, only DS-1N-14 and DS-3N-12E cards are displayed.
|
Protect Module
|
Choose the protect module if using 1:1 or 1:N.
|
Available Entities
|
Displays a list of available entities. You can toggle between available and working entities.
|
Working Entities
|
Displays a list of working entities. You can toggle between working and available entities.
|
Bidirectional Switching
|
(Optical cards only) Click if you want both the transmit and the receive channels to switch if a failure occurs on one. This option is only available if you select 1+1 (port) type.
|
Revertive
|
If checked, the node reverts traffic to the working card or port after failure conditions remain corrected for the amount of time entered in Reversion Time. This option is not available if the 1:N (card) type has been selected.
|
Reversion Time
|
If Revertive is checked, choose the amount of time following failure condition correction that the node should switch back to the working card or port. Use half-minute increments. This option is only available if you select 1:1 (card) type.
|
Recovery Guard Time
|
Prevents rapid switches due to signal degrade (SD) or signal failure (SF) conditions. After the SD or SF condition is cleared on a facility protected by Optimized 1+1 protection, no switches are performed for the duration of the recovery guard timer.
|
Verification Guard Time
|
Specifies the amount of time that a user command has to complete. If a user command cannot be completed within the duration set by the verification guard timer, the command is cleared and an APS_CLEAR event is sent.
|
Detection Guard Time
|
Specifies the amount of time after a failure that the system has to complete a switch. After detecting an SD, SF, loss of signal (LOS), loss of frame (LOF), or alarm indication signal line (AISL) failure, the detection guard timer is started. If the detection guard timer is set to zero, the system completes a switch within 60 ms for failure events.
|
4.5.7.2 Enabling Ports of Protection Group Cards
Step 1 Select a CTC-based NE and choose Configuration > NE Explorer.
Step 2 In the tree view of the NE Explorer window, select the card.
Step 3 In the card slot properties pane, click the Line tab.
Step 4 In the Line Config subtab, under the Admin State column, select IS (in service).
Step 5 Click Apply.
4.5.7.3 Editing Protection Groups
Step 1 Select a CTC-based NE and choose Configuration > NE Explorer.
Step 2 In the node properties pane, click the Protection tab > Protection Groups subtab.
Step 3 In the Protection Groups section, choose a protection group.
Step 4 In the Selected Protection Group section, edit the fields as appropriate.
Step 5 In the Protection tab, click the Operations subtab.
Step 6 In the Protection Groups section, choose a protection group.
Step 7 In the Protection Group Details section, choose a protection group to switch. You can choose from among the following:
•Clear
•Manual
•Force
•Switch
•Unlock
•Lock Out
•Lock On
Step 8 Click OK in the confirmation dialog box.
Step 9 Click Apply.
4.5.7.4 Deleting Protection Groups
Step 1 Select a CTC-based NE and choose Configuration > NE Explorer.
Step 2 In the tree view of the NE Explorer window, select the NE node.
Step 3 In the node properties pane, click the Protection tab.
Step 4 In the Operations subtab, make sure that the protect card is in standby mode and the working card is in active mode. If the protect card is still active, do not continue.
Step 5 In the Protection Groups subtab, click a protection group.
Step 6 Click Delete.
Step 7 Click OK in the confirmation dialog box.
4.5.8 Restoring NE Defaults
The NE Defaults Management wizard allows you to choose an NE from which an NE defaults file can be loaded. Alternately, you can load the file from your local (client) disk. The wizard then provides you a list of NEs where you can download the file. When you click Finish, CTM schedules a job for this action. The NE defaults file downloaded to each selected NE is tracked as a separate task on the Job Monitor table.
Note If you are applying NE defaults from one NE to another, the NE versions must be identical. For example, you cannot apply NE defaults from an ONS 15454 R3.4.1 NE to an ONS 15454 R4.0 NE.
Note This feature is available for R3.4 NEs and later.
If you want to revert back to the default settings for an NE, you can download and apply a defaults override file to one or more selected NEs, described as follows.
Step 1 In the Domain Explorer window, choose Configuration > CTC-based SONET NEs or CTC-based SDH NEs > NE Defaults Management. The NE Defaults Management dialog box opens. Table 4-25 provides descriptions.
Step 2 Choose an NE from which a defaults override file can be loaded. The following options are available:
•From NE
•From File
Step 3 Click Next. A read-only list of NE defaults is displayed.
Step 4 Click Next.
Step 5 Select the NE(s) to which you want to download the default-override file. The following options are available:
•Save to NE
•Save to File
Step 6 Click Finish.
Table 4-25 Field Descriptions for the NE Defaults Management
Screen
|
Field
|
Description
|
Select an NE to View the Defaults
|
From NE
|
Select From NE if the NE defaults file is on an NE. If you select From NE, the From File options are not accessible.
|
Select NE
|
Select the NE where the NE defaults file exists.
|
From File
|
Select From File if the NE defaults file is on your PC or a server. If you select From File, the From NE options are not accessible.
|
Local
|
Select Local if the file is on your PC. Enter the path for the file, or click Browse to search for it.
|
Server
|
Select Server if the file is located on a server. Use the drop-down list to select a server.
|
NE Defaults
|
(Read-only) Use this screen to view the selected NE defaults.
|
Save the NE Defaults
|
Save to NE(s)
|
To save the defaults to one or more NEs, select Save to NE(s). If you select Save to NE(s), the Save to File options are not accessible.
|
Available NE(s)
|
Select one or more NEs in the Available NE(s) field and click Add to move them to the Selected NE(s) field.
|
Selected NE(s)
|
Select one or more NEs in the Selected NE(s) field and click Remove to move them to the Available NE(s) field.
|
Save to File
|
To save the defaults to a file on your PC or a server, select Save to File. If you select Save to File, the Save to NE(s) options are not accessible.
|
Local
|
Select Local to save the file on your PC. Enter the path for the file, or click Browse to search for it.
|
Server
|
Select Server to save the file on a server. Enter a server path in the field.
|
4.6 How Do I Monitor the Network?
This section contains the following information:
•Monitoring Scheduled Tasks
•Monitoring Service Status
•Viewing the NE Discrepancy Table
•Monitoring CTM Client and Server Configuration Details
•Viewing the CTM Server and Client Version
4.6.1 Monitoring Scheduled Tasks
The Job Monitor table provides information about scheduled administrative tasks: memory backup, memory restore, and software download. For example, you can see the system username of the person who entered a specific task, the time that the task began, and the time that the task ended.
Note A job consists of multiple tasks.
The Job Monitor table also monitors bulk operations: adding multiple users to multiple NEs, modifying a user on multiple NEs, and deleting multiple users on multiple NEs. (See 8.4.4 Managing NE User Access, page 8-44 for more information about bulk operations.) When a request is made to the CTM server to add, modify, or delete NE users, multiple entries are made in the Job Monitor table. Each entry consists of the following:
•Task Owner—User ID used during login.
•NE ID—NE ID on which the operation is executed.
•Task Creation Time—Server time when the request was made.
After these requests are executed, the job's status is updated accordingly in the Job Monitor table.
Another task that is monitored is the BLSR/MS-SPRing exercise scheduling. (See 7.3.7 Exercising a BLSR, page 7-100 or 7.4.9 Exercising an MS-SPRing, page 7-111.) When the exercise ring is scheduled, there are two tasks created: the BLSR/MS-SPRing exercise job in the west port and the BLSR/MS-SPRing exercise job in the east port. The schedule time difference between these two tasks is specified in the Control Panel. (See 7.4.10 Changing the MS-SPRing Exercise Interval, page 7-112.)
If you are able to schedule a BLSR/MS-SPRing exercise successfully, the corresponding task and its status are monitored in the Job Monitor table. If more than one BLSR exercise is scheduled at a certain time on the same ring, only one BLSR exercise will be successfully completed. Tasks are marked successful when the exercise command is accepted by the NE. If the exercise fails due to the unavailability of the NE or if the exercise command is rejected by the NE, an alarm is reported in the Alarm Browser and will be cleared on the next successful exercise or when the cross-connect is reset.
4.6.1.1 Viewing the Job Monitor Table
To view the Job Monitor table, choose Administration > Job Monitor in the Domain Explorer window. Table 4-26 provides descriptions.
Note Some fields in the Job Monitor table apply only to certain tasks, NEs, or NE versions.
Table 4-26 Field Descriptions for the Job Monitor Table
Field
|
Description
|
Job ID
|
ID number corresponding to the selected job.
|
Task ID
|
ID number corresponding to the task. If a job includes more than one NE, each NE has a separate task ID for the job.
|
Task Type
|
Type of task. Tasks include adding users, applying alarm profiles, creating BLSR/MS-SPRings, configuring nodes, creating alarm profiles, deleting users, logging out users, automatically backing up memory, manually backing up memory, restoring memory, modifying users, setting up SNTP, setting NE defaults, setting security advisory messages, activating software, downloading software, and reverting software.
|
Task Owner
|
System username of the person who entered the task.
|
NE ID
|
Name of the NE on which the task is scheduled to run.
|
Task Status
|
Current status of the task:
•Queued—The task is scheduled but has not yet begun.
•Running—The task is in progress.
•Canceled—The task has been canceled.
•Succeeded—The task succeeded.
•Failed—The task failed.
•Waiting—The node manager must be initialized before a task can begin. If the node manager is not initialized, the status of the task is Waiting. After the node manager becomes initialized, the task status changes to Queued.
|
Task Creation Time
|
Date and time when the task was entered into the system.
|
Task Scheduled Time
|
Date and time when the task is scheduled to begin.
|
Task Start Time
|
Date and time when the task began.
|
Task End Time
|
Date and time when the task ended.
|
Display Information
|
Information related to the Task Type column.
|
User Comments
|
Any user-entered comments relating to the task.
|
Additional Information
|
Any additional information.
|
4.6.1.2 Viewing the Job Monitor Filter Dialog Box
Use the Job Monitor Filter dialog box to filter job data according to criteria that you select and to display the results in the Job Monitor table. Table 4-27 provides descriptions.
Table 4-27 Job Monitor Filter Dialog Box Descriptions
Tab
|
Description
|
Creation Time (time zone)
|
Allows you to filter job monitor data for a specified time period, ranging from the past hour to the past 180 days. Additionally, you can click the User Specified radio button to specify an exact filter starting and ending time by month, day, year, and hour. The time zone can be GMT, a user-defined offset from GMT, or local time, depending on what is specified in the User Preferences dialog box. Click No Time Specified if you want to filter events and the time period is not important.
|
NE ID
|
Allows you to move NEs back and forth between the list of available NE IDs and selected NE IDs. The filter runs on the NEs in the Selected NE ID list.
|
Task Owner
|
Allows you to move owners back and forth between the list of available owners and selected owners. The filter runs on the owners in the Selected Task Owner list.
|
Job/Task ID
|
Allows you to filter jobs by job and task IDs. Jobs consist of multiple tasks. For example, if you perform a memory backup for multiple NEs, the backup operation is a job, and each NE is a task.
•If you specify a start and end ID range in the Job ID field but leave the Task ID field blank, the filter runs on the job ID range.
•If you specify a start and end ID range in the Task ID field but leave the Job ID field blank, the filter runs on the task ID range.
•If you specify a start and end ID range in both the Job ID and Task ID fields, the filter first applies the values in the Job ID field, then narrows the filter according to the values in the Task ID field. For example, if you specify that Job ID Start = 1, Job ID End = 3, Task ID Start = 1, and Task ID End = 2, the returned value is all entries with a Job ID of 1, 2, or 3 and a Task ID of 1 or 2.
|
Task Type
|
Allows you to move task types back and forth between the list of available task types and selected task types. The filter runs on the tasks in the Selected Task Types list.
|
Task Status
|
Allows you to filter tasks by status:
•Queued—The task is scheduled but has not yet begun.
•Running—The task is in progress.
•Canceled—The task has been canceled.
•Failed—The task failed.
•Succeeded—The task succeeded.
•Waiting—The node manager must be initialized before a task can begin. If the node manager is not initialized, the status of the task is Waiting. After the node manager becomes initialized, the task status changes to Queued.
|
4.6.1.3 Canceling a Scheduled Job or Task
Step 1 In the Domain Explorer window, choose Administration > Job Monitor.
Step 2 Select a task to cancel; then, click the Cancel Task or Cancel Job tool (or choose Edit > Cancel Task or Cancel Job).
Note Cancel is enabled only for jobs and tasks with a Queued status. When a job contains more than one task in a Queued status, choosing Cancel Job cancels all tasks with the same job ID.
Step 3 Click OK in the confirmation dialog box.
4.6.1.4 Adding Job Monitor Notes
The Job Monitor Note dialog box allows you to view and add notes to jobs displayed in the Job Monitor table. If a job has a note, a Job Monitor Note tool appears under the User Comments column.
Step 1 In the Domain Explorer window, choose Administration > Job Monitor.
Step 2 Select a task and choose Edit > User Note. Comments are visible to all users.
Table 4-28 Field Descriptions for the Job Monitor Note Dialog Box
Field
|
Description
|
Note
|
Provides space for you to type your comments about the selected job. To add comments to the previous comments, click the Append radio button. To overwrite the previous comments, click Replace. To delete the comments, click Delete.
|
History
|
Displays comments entered by previous users.
|
4.6.2 Monitoring Service Status
The Service Monitor table allows you to view the status of the services that are running on the CTM server. To view the Service Monitor table, choose Administration > Service Monitor in the Domain Explorer window. Table 4-29 provides descriptions.
Table 4-29 Field Descriptions for the Service Monitor Table
Column Name
|
Description
|
Service Name
|
Displays the name of the selected service.
|
Logged In At
|
Displays the last time the user logged in.
|
IP Address
|
Displays the IP address of the selected service.
|
Session ID
|
Displays the unique session ID.
|
Note The showctm command is an alternate way of viewing processes or services that are running on the CTM server.
4.6.3 Viewing the NE Discrepancy Table
The NE Discrepancy table shows all ONS 155xx misconfigurations detected by CTM.
Step 1 In the Domain Explorer or Subnetwork Explorer tree, select the ONS 155xx NE, group, or subnetwork for which to view misconfiguration data.
Step 2 Choose Configuration > ONS 155XX > NE Discrepancy Table. The NE Discrepancy table opens. Table 4-30 provides descriptions.
Table 4-30 Field Descriptions for the NE Discrepancy Table
Field
|
Description
|
Name
|
Type of discrepancy:
•Wavelength Mismatch—Wavelengths cannot be added to a MUX/DEMUX card while the same wavelengths that were added by another MUX/DEMUX card on the network are passing through this MUX/DEMUX card passively.
•Protection Mode Mismatch—The protection mode is configured differently at each end of a circuit or connection.
•Protocol Mismatch—The protocol type is misconfigured at the ends of a circuit or connection.
•Link Mismatch—A link has been configured to connect more than one device to the same port on a third device.
|
Description
|
Description of the discrepancy.
|
Perceived Severity
|
Severity level of the discrepancy:
•CR—Critical
•MJ—Major
•MN—Minor
•WN—Warning
|
Time Stamp
|
Date and time when the discrepancy was discovered.
|
Node 1
|
The first ONS 155xx involved in the discrepancy.
|
Node 2
|
The other ONS 155xx involved in the discrepancy. Discrepancies usually involve two devices.
|
Details
|
Details on the discrepancy, including its cause. If the text extends beyond the width of the field, use the pull-down arrow at the right side of the field to read the remaining text. Alternately, choose File > Show Discrepancy Details to read the full text.
|
4.6.4 Monitoring CTM Client and Server Configuration Details
The CTM Properties pane in the Control Panel window displays information about the CTM server and client configuration.
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 In the Control Panel window, click Cisco CTM to open the CTM Properties pane. The fields in the pane are read-only. Table 4-31 provides descriptions.
Table 4-31 Field Descriptions for the CTM Properties Pane
Tab
|
Field
|
Description
|
Server Configuration
|
Server Name
|
Displays the workstation name where the CTM server application resides.
|
IP Address
|
Displays the IP address of the CTM server.
|
Server Port
|
Displays TCP port number of the CTM server.
|
Software Version
|
Shows the CTM software version that is running.
|
Client Configuration
|
Host Name
|
Displays the workstation name where the CTM client application resides.
|
IP Address
|
Displays the IP address of the CTM client.
|
Version
|
Shows the CTM software version that is running.
|
Username
|
Displays the name that was used to log into the CTM client.
|
4.6.5 Viewing the CTM Server and Client Version
You can view the CTM server and client version in the Control Panel and in the About Cisco Transport Manager dialog box. You can also view the server version in the Management Domain Properties pane.
Step 1 To view the CTM server and client version in the Control Panel, complete the following substeps:
a. In the Domain Explorer window, choose Administration > Control Panel.
b. In the Control Panel window, click Cisco CTM to open the CTM Properties pane.
c. Click the Server Configuration tab. The CTM server version is shown in the Software Version field.
d. Click the Client Configuration tab. The CTM client version is shown in the Version field.
Step 2 To view the CTM server and client version in the About dialog box, choose Help > About Cisco Transport Manager in any window.
Step 3 To view the CTM server version in the Management Domain Properties pane, complete the following substeps:
a. In the Domain Explorer tree, click the management domain node to open the Management Domain Properties pane.
b. Click the Identification tab. The CTM server version is shown in the Software Version field.
4.7 How Do I Manage CTC Operations?
CTC is the software interface that provides provisioning and administrative functionality for the following NEs:
•ONS 15310
•ONS 15327
•ONS 15454 SONET
•ONS 15454 SDH
•ONS 15600 SONET
•ONS 15600 SDH
This section contains the following information:
•Functionality Provided in CTC that Is Not Available in CTM
•Specifying CTC Partitions for CTC-Based NEs
Note For information about upgrading and deleting the CTC binary file, see Managing Binaries Using the CTC Upgrade Table.
4.7.1 Functionality Provided in CTC that Is Not Available in CTM
Table 4-32 lists the CTC functions that are not supported in CTM through generic CTM features (such as PM, software download, or memory backup) or through the native NE Explorer (equipment provisioning) for CTC-based NEs. The table provides a brief description of each function and a reference to the location within CTC where the function is provided.
Table 4-32 CTC Functions that Are Not Supported in CTM R5.0
CTC Function
|
CTC Reference
|
Network Level
|
CTM does not support management of overhead circuits.
|
Network View > Provisioning > Overhead Circuits
|
Node Level
|
CTM does not support provisioning the node name and location attributes (description).
|
Node View > Provisioning > General
|
CTM does not support access to the EtherBridge MAC table (and related operations) or trunk utilization.
|
Node View > Maintenance > EtherBridge > MAC table
Node View > Maintenance > EtherBridge > Trunk Utilization
|
CTM does not support management of Unified Control Plane (UCP) parameters.
|
Node View > Provisioning > UCP
|
CTM does not support retrieval of the diagnostics file or operation of the lamp test.
|
Node View > Maintenance > Diagnostics
|
CTM does not support test access.
|
Node View > Maintenance > Test Access
|
Card Level—Performance Monitoring
|
CTM does not support the ability to clear or reset PM register statistics on the NE.
|
Card View > Performance
|
Card Level— AIC and AIC-I Card
|
CTM does not support the ability to provision the user data channels (UDCs) or line DCC, or perform virtual wire maintenance operations.
|
AIC Card View > Maintenance > Virtual Wires
AIC Card View > Maintenance > Overhead Termination
|
Circuit Management
|
CTM does not support the ability to create TL1-like cross-connections. CTM does not support specification of the interdomain SLA.
|
Circuit Creation wizard
|
CTM does not support the ability to edit path selector attributes of an existing circuit.
|
Tools > Circuits > Set Path Selector Attributes
|
CTM does not support the Spanning Tree Map for E-series Ethernet cards.
|
—
|
CTM does not support in-service topology upgrades.
|
Tools > Topology Upgrade > Convert UPSR to BLSR
Tools > Topology Upgrade > Convert Unprotected to BLSR
|
4.7.2 Specifying CTC Partitions for CTC-Based NEs
CTC-based NEs that are added to the CTM domain to access other CTC-based NEs are called GNEs, or topology hosts. When starting CTC for a particular CTC-based NE, the GNE for that NE is specified in CTC. CTC can take more than one GNE as input and discover the nodes behind those GNEs.
In a stable network, if CTC is started with a particular set of GNEs, the CTC view looks the same every time it is started with that set of GNEs. CTM tries to copy this behavior when starting CTC for a given NE.
You can choose Administration > Control Panel > UI Properties to specify the number of GNEs to provide to CTC when starting CTC. (The default is 10 GNEs.)
The CTM client smart-link feature maintains an association between the CTC instance and the list of CTC-based NEs that it can manage. You can navigate through NEs within the same CTC partition without relaunching CTC. This feature conserves memory resources and ensures a fast response time.
If you launch and exit one instance of CTC and then launch a second CTC instance from the same partition, the second CTC launch goes through a one-minute timeout period to ensure that the previous instance has exited. The one-minute timeout occurs even if you launched and exited the previous CTC instance for a different NE. After the timeout, CTC initializes and a new window is launched. There is a delay of 10 to 20 seconds while the CTC launch initializes.
Caution ONS 15454 SONET and ONS 15454 SDH NEs propagate VLANs whenever a node appears in the same network view as another node, regardless of whether or not the nodes are DCC-connected. When there is more than one CTC management domain in CTM, nodes that are not connected through DCC often appear in the same CTC view that is launched for that domain. The ONS 15454 NEs propagate VLAN information to these DCC-disconnected nodes. To prevent VLAN propagation, make sure that DCC-disconnected nodes do not appear in the same CTC view by making the CTC management domain equal to one.
