Table Of Contents
Building the Network
3.1 Overview
3.2 How Do I Build Groups?
3.2.1 Adding Groups
3.2.2 Copying Groups
3.2.3 Moving Groups
3.2.4 Deleting Groups
3.3 How Do I Build Network Partitions?
3.3.1 Adding Network Partitions
3.3.2 Modifying Network Partitions
3.3.3 Deleting Network Partitions
3.4 How Do I Build Subnetworks?
3.4.1 Adding Subnetworks
3.4.2 Moving Subnetworks
3.4.3 Deleting Subnetworks
3.5 How Do I Build NEs?
3.5.1 Prerequisites for Adding NEs
3.5.2 Adding NEs
3.5.3 Copying an NE from One Group to Another
3.5.4 Moving an NE from One Group to Another
3.5.5 Moving an NE from One Network Partition to Another
3.5.6 Automatically Grouping NEs in Subnetworks
3.5.7 Deleting NEs
3.5.8 Restoring a Deleted NE
3.5.9 Searching for an NE
3.6 How Do I Build Links?
3.6.1 Setting Up CRS-1 and XR 12000 NEs for Link Discovery
3.6.2 Setting Up ONS 15501, ONS 15530, and ONS 15540 NEs for Link Discovery
3.6.3 Overview of Supported Links
3.6.4 Viewing the Link Table
3.6.5 Filtering the Link Table
3.6.6 Filtering Links in the Network Map
3.6.7 Creating Links
3.6.8 Modifying Links
3.6.9 Deleting Links
3.6.10 Viewing Link Utilization
3.6.11 Filtering the Link Utilization Table
3.7 How Do I Build Server Trails?
3.7.1 Creating Server Trails
3.7.2 Modifying Server Trails
3.7.3 Deleting Server Trails
3.8 How Do I Use Network Maps?
3.8.1 Customizing a Network Map
3.8.2 Viewing a Node in the Network Map
3.8.3 Adjusting the Zoom Level or Pan Position
3.8.4 Modifying a Node Icon or a Map Background Image
3.8.5 Saving Changes to the Network Map
3.9 How Do I Discover the Network for Optical, Routing, and MGX Devices?
3.9.1 Discovering CRS-1 and XR 12000 NEs
3.9.2 Discovering Cisco 7600 NEs
3.9.3 Discovering CTC-Based NEs
3.9.4 Discovering ONS 155xx NEs
3.9.5 Rediscovering ONS 155xx, CRS-1, and XR 12000 NEs
3.9.6 Resynchronizing CTM with CRS-1 and XR 12000 NEs
3.9.7 Resetting the Resync Interval
3.9.8 Discovering the Network for MGX Voice Gateway Devices
3.10 How Do I Test Connectivity for Optical and Routing Devices?
3.10.1 Pinging an NE
3.10.2 Testing NE Connectivity
3.11 How Do I Test Connectivity for MGX Voice Gateway Devices?
Building the Network
After you have planned your network, you can begin building the network components: groups, network partitions, subnetworks, NEs, links, and network maps.
This chapter contains the following sections:
•
Overview
•How Do I Build Groups?
•How Do I Build Network Partitions?
•How Do I Build Subnetworks?
•How Do I Build NEs?
•How Do I Build Links?
•How Do I Build Server Trails?
•How Do I Use Network Maps?
•How Do I Discover the Network for Optical, Routing, and MGX Devices?
•How Do I Test Connectivity for Optical and Routing Devices?
•How Do I Test Connectivity for MGX Voice Gateway Devices?
3.1 Overview
The CTM management domain is the top-level root node in the Domain Explorer tree. The management domain contains NEs and the following network components:
•Groups—Collection of groups or collection of NEs. NEs are often grouped geographically or by domain.
•Network Partitions—Logical segment of NEs (grouped in subnetworks) in which NEs of the same model type are managed by a single NE service.
•Subnetworks—Sets of NEs interconnected at a specific network layer (such as physical, section, line, and so on). Subnetworks are contained within network partitions. NEs must belong to the same subnetwork in order to create circuits between them.
•Links—Physical or logical entities (for example, a fiber) between two physical points (for example, ports). Circuits are provisioned through links.
•Network Maps—Geographic representation of the NEs in the domain, the circuits and links between NEs, and the number of alarms associated with NEs.
3.2 How Do I Build Groups?
NEs in the Domain Explorer are organized into groups, which consist of NEs or other groups. NEs are often grouped geographically or by domain. The same NE or group can be assigned to different groups. The following sections describe how to add, copy, move, and delete groups.
3.2.1 Adding Groups
Step 1 Select a node or group in the Domain Explorer tree.
Note You cannot add a new group to the Discovered Network Elements or Deleted Network Elements groups.
Step 2 Choose File > New Group (or click the Add a New Group tool). The New Group dialog box opens.
Step 3 Enter the following information in the New Group dialog box.
Table 3-1 Field Descriptions for the New Group Dialog Box
Field
|
Description
|
Group ID
|
Unique name for the group.
|
Location Name
|
Geographic location of the group.
|
Description
|
Description of the group.
|
Step 4 Click OK. The new group appears in the Domain Explorer tree.
3.2.2 Copying Groups
You can easily create domains for multiple users in CTM. Just copy the same groups in different domains, so that users who work different shifts can use the same group.
Step 1 In the Domain Explorer tree, select the group to be copied.
Step 2 Choose Edit > Copy (or click the Copy tool).
Step 3 Select the group where the group will be pasted and choose Edit > Paste (or click the Paste tool). This pastes the group under the selected group.
Note A group cannot be pasted into the Discovered Network Elements or Deleted Network Elements groups.
Tip The drag-and-drop feature can also be used to copy groups. Hold down the Ctrl key and use the mouse to drag and drop the group to a new location.
Since they cannot see the entire domain, users with the Assign NEs property (Provisioner, Operator, and some custom user profiles) are not allowed to modify the topology using copy, cut, paste, or drag and drop. See Chapter 8, "Managing Security" for information about the Assign NEs property.
3.2.3 Moving Groups
CTM provides drag-and-drop capabilities to easily move groups in the Domain Explorer tree.
Step 1 In the Domain Explorer tree, select the group to be moved.
Step 2 Use the mouse to drag and drop the selected group to a new location.
Note Groups cannot be moved into the Discovered Network Elements or Deleted Network Elements groups.
3.2.4 Deleting Groups
CTM allows you to delete a single group or multiple groups.
3.2.4.1 Deleting a Single Group
Step 1 In the Domain Explorer tree, select the group to be deleted.
Step 2 You can delete either the selected instance of the group or all instances of the group:
•To remove the selected instance of the group, choose Edit > Delete; then, click Yes in the confirmation dialog box.
•To remove all instances of the selected group, choose Edit > Delete All; then, click Yes in the confirmation dialog box.
Note Before deleting the last instance of a group, the group must be empty. Move all of the NEs and groups that the group contains to a different group.
3.2.4.2 Deleting Multiple Groups
Step 1 In the Domain Explorer tree, select the group to be deleted. Select multiple groups by pressing the Ctrl key, then click each group that will be deleted.
Step 2 You can delete either the selected instance of the groups or all instances of the groups:
•To remove the selected instance of the groups, choose Edit > Delete; then, click Yes in the confirmation dialog box.
•To remove all instances of the selected groups, choose Edit > Delete All; then, click Yes in the confirmation dialog box.
Note Before deleting the last instance of a group, the group must be empty. Move all of the NEs and groups that the group contains to a different group.
3.3 How Do I Build Network Partitions?
Network partitions are groups of subnetworks or groups of NEs that are managed by the same NE service. Different network partitions mean different NE services. You can add, modify, or delete network partitions in the Subnetwork Explorer window.
Note CTM contains one network partition by default.
Note A single network partition should contain fewer than 50 CRS-1 NEs, 200 XR 12000 NEs, and 500 CTC-based NEs. Multiple network partitions must be used if your NE counts exceed these limits or if you are managing ANSI and ETSI devices in the same CTM domain.
Note When automatic subnetwork grouping is enabled while performing operations on a network partition, NE visibility might be affected. Wait for a few minutes while CTM arranges the NEs and subnetworks in the correct network partition. For more information on automatic subnetwork grouping, see Automatically Grouping NEs in Subnetworks.
3.3.1 Adding Network Partitions
Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer.
Step 2 In the Subnetwork Explorer window, choose File > Add New Network Partition (or click the Add a New Network Partition tool). The Add New Network Partition dialog box opens.
Step 3 Enter the following information.
Table 3-2 Field Descriptions for the Add New Network Partition Dialog Box
Field
|
Description
|
Network Partition ID
|
ID of the network partition. The ID must contain a minimum of 1 and a maximum of 128 alphanumeric or special characters.
|
Description
|
Network partition description.
|
Step 4 Click OK. The new network partition appears in the Subnetwork Explorer tree.
3.3.2 Modifying Network Partitions
Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer. The Subnetwork Explorer opens.
Step 2 In the Subnetwork Explorer tree, select a network partition to modify.
Step 3 In the Network Partition Properties pane, click the Identification tab.
Step 4 Modify the following information as needed.
Table 3-3 Field Descriptions for the Network Partition Properties Pane
Field
|
Description
|
Network Partition ID
|
ID of the network partition. The ID must contain a minimum of 1 and a maximum of 128 alphanumeric or special characters.
|
Description
|
Network partition description.
|
Step 5 Click Save.
Step 6 In the confirmation dialog box, click Yes. The modifications are visible in the Subnetwork Explorer tree and Network Partition Properties pane.
3.3.3 Deleting Network Partitions
Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer. The Subnetwork Explorer opens.
Step 2 In the Subnetwork Explorer tree, select the network partition that you want to delete; then, choose Edit > Delete.
Note A network partition cannot be deleted if it is associated with any subnetwork in the domain, or if it is the last network partition in the domain. When the network partition is deleted, any running instances of the NE Service that were associated with the partition stop running.
Step 3 In the confirmation dialog box, click Yes. The network partition is removed from the Subnetwork Explorer tree.
3.4 How Do I Build Subnetworks?
Subnetworks are sets of NEs interconnected at a specific network layer (such as physical, section, line, and so on). Subnetworks are contained within network partitions. NEs must belong to the same subnetwork in order to create circuits between them.
The following sections describe how to add, move, and delete subnetworks. Users with the Assign NEs property (Provisioner, Operator, and some custom user profiles) can see only the subnetworks of the NEs that are assigned to them.
Note When automatic subnetwork grouping is enabled while performing operations on a subnetwork, NE visibility might be affected. Wait for a few minutes while CTM arranges the NEs in the correct subnetwork. For information on automatic subnetwork grouping, see Automatically Grouping NEs in Subnetworks.
3.4.1 Adding Subnetworks
Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer.
Note To open the Subnetwork Explorer, the domain must contain at least one NE. If the domain does not contain any NEs, the Subnetwork Explorer menu option is unavailable.
Step 2 In the Subnetwork Explorer tree, select the network partition where you will add the subnetwork and choose File > Add New Subnetwork (or click the Add a New Subnetwork tool). The Add New Subnetwork dialog box opens.
Step 3 Enter the following information in the Add New Subnetwork dialog box.
Table 3-4 Field Descriptions for the Add New Subnetwork Dialog Box
Field
|
Description
|
Subnetwork ID
|
Unique name for the subnetwork. The name can contain up to 32 alphanumeric or special characters.
|
Subnetwork Type
|
Type of subnetwork (SONET, SDH, other, or unknown).
|
Subnetwork Topology
|
Subnetwork topology.
|
Description
|
Description of the subnetwork.
|
Step 4 Click OK. The new subnetwork appears in the Subnetwork Explorer tree.
Note The Add New Subnetwork feature is not available for users with the Assign NEs property (Provisioner, Operator, and custom user profiles) because they cannot see the entire domain.
3.4.2 Moving Subnetworks
A subnetwork can be moved from one network partition to another if there are no routable links among the NEs that belong to that subnetwork and if automatic subnetwork grouping is disabled. (For information about automatic subnetwork grouping, see Automatically Grouping NEs in Subnetworks.)
Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer.
Step 2 In the Subnetwork Explorer tree, select the subnetwork to be moved.
Step 3 Use the mouse to drag and drop the selected subnetwork to a new network partition.
3.4.3 Deleting Subnetworks
Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer.
Step 2 In the Subnetwork Explorer tree, click the subnetwork that will be deleted.
Note Only an empty subnetwork can be deleted. An empty subnetwork is one that does not contain any NEs or deleted NEs. Trying to delete a subnetwork that contains deleted NEs will generate the error message: "Selected subnetwork has some deleted NEs. Prune those NEs to delete the subnetwork." Before deleting the subnetwork, remove the deleted NEs from the CTM database. For more information, see Removing a Deleted NE.
Step 3 Choose Edit > Delete.
Step 4 In the confirmation dialog box, click Yes to remove the subnetwork from the tree.
3.5 How Do I Build NEs?
When you add a new NE, you select the subnetwork to which you will add it. Consequently, the NE is added to the network partition that contains the selected subnetwork. This allows you to create circuits between NEs.
3.5.1 Prerequisites for Adding NEs
Before adding a new NE, you must enable the NE service for that NE. The NE service is enabled by default, but the service is not started as a process unless you activate an NE for that particular service. You must also meet certain other specific prerequisites depending on the type of NE you are adding.
Note There are no prerequisites for adding MDS 9000, ONS 15327, ONS 15600 SONET, or ONS 15600 SDH NEs.
3.5.1.1 Prerequisites for Adding ONS 15216 EDFA2 or EDFA3 NEs
Before adding ONS 15216 EDFA2 or EDFA3 to CTM, you must do the following:
•Configure the CTM SNMP community string with read-write access on the ONS 15216 EDFA2 or EDFA3. Refer to the NE documentation for more information.
•Ensure that the CTM SNMP community string value and the CommTrapEntry community string value on the ONS 15216 EDFA2 or EDFA3 match. To ensure that these values match, enter the value from the CommTrapEntry in the ONS 15216 EDFA2 or EDFA3 into the SNMP Community String field in the Domain Explorer.
•(For the ONS 15216 EDFA3 only) Start the FTP service. To verify that the FTP service has started, enter the ftp 0 command and enter the username and password specified during installation.
•(For the ONS 15216 EDFA2 only) Configure the TFTP service on the CTM server to publish the TFTP directory and start the TFTP service. The directory to be published as a TFTP directory should have read-write access.
To configure the default tftpboot directory:
Step 1 Start the TFTP service on the CTM server by uncommenting the tftp service entry from the /etc/inetd.conf file, and update the name of the directory to be published as a TFTP directory. For example:
tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot
Step 2 Stop and restart the inetd process.
The name of the ONS 15216 EDFA3 NE must be unique and cannot be a null value. To set the name of the ONS 15216 EDFA3 NE:
Step 1 Log into TL1 for that particular NE. For example, enter:
Step 2 Enter the username and password. For example, enter:
ACT-USER::<username>:123::<password>;
Step 3 Enter the following command to set the new name on the ONS 15216 EDFA3 NE:
ED-NE-GEN:::123:::NAME=<new_name>;
Step 4 Enter the following command to verify that the name is correct:
Step 5 Enter the following command to log out:
CANC-USER::<username>:123;
Note For passive ONS 15216 NEs, there is no communication between CTM and the NE itself and all the information is user-defined. For example, you can add inventory information in the Domain Explorer and add specific information (such as a serial number) in the NE Explorer. For passive ONS 15216 NEs with multiple slots, you can use the NE Explorer to specify the content of each slot. The information you define is maintained in the database and propagated to an external OSS by using CTM GateWay/CORBA.
3.5.1.2 Prerequisites for Adding ONS 15302 and ONS 15305 NEs
Before adding ONS 15302 and ONS 15305 NEs to CTM, make sure that a valid SNMP community string is set up on the ONS 15302 or ONS 15305 to allow performance monitoring and fault management data collection from the NE.
Note To add an ONS 15302 or ONS 15305 NE to CTM, its SNMP Users table must contain the row 0.0.0.0 public true, where public is the community string. In addition, to obtain trap events from the NE, the CTM server IP address must be added to the NE. See the Cisco Edge Craft user documentation for more information.
3.5.1.2.1 Important Note About Upgrading from ONS 15305 R2.0.2 or R2.0.3 to ONS 15305 R3.0
When upgrading from ONS 15305 R2.0.2 or R2.0.3 to ONS 15305 R3.0, note the following constraints:
•After the NE upgrade to ONS 15305 R3.0, you must delete the R2.0 NE (with NE model "ONS 15305") from CTM and readd it with the correct NE model attribute ("ONS 15305 CTC").
•All PM data that was collected before the upgrade will be lost.
These constraints exist because the NE service that manages the ONS 15305 R2.0.2 and R2.0.3 is different from the NE service that manages the ONS 15305 R3.0.
3.5.1.3 Prerequisites for Adding ONS 15310 CL, ONS 15310 MA, ONS 15454 SONET, and ONS 15454 SDH NEs
Before adding ONS 15310 CL, ONS 15310 MA, ONS 15454 SONET, or ONS 15454 SDH NEs with ML-series cards to CTM, make sure the NEs are set up as follows:
•A valid SNMP community string must be given when adding an NE with ML-series cards to resync Syslog and Configuration events. Audit log messages will be added in case of a resync failure.
•A trap destination with IP address equal to the CTM server IP address, UDP port 162, SNMP version as SNMPv2c, maximum traps per second set to 0, and SNMP community string must be created and must allow SNMP sets to receive traps from ML-series cards.
•The Cisco IOS startup-config file must have the snmp-server enable traps command to receive traps from ML-series cards.
•Whenever the user changes the trap destination for NE IP address and port=162/391 in either CTC or CTM, NEs must be out of service to resync the ML-series card events and be registered for traps. Change the operational state of the NE to In Service after making the changes.
•If your network contains ML cards, SNMPv1/SNMPv2c uses the following configurations on GNEs and ENEs for traps:
–GNE trap destination: CTM server IP address
–GNE trap port: 162
–GNE community string: public
–GNE version: v1 or v2c
–ENE trap destination: GNE IP address
–ENE trap port: 391
–ENE community string: Same as on GNE
–ENE version: v1 or v2c
Note Keep the SNMP version consistent across all the GNEs/ENEs in the ring.
3.5.1.3.1 Adding a DWDM Node to an Existing Multi-Service Transport Platform (MSTP) Network
Step 1 Mark the two NEs of the DWDM span (where you want to insert the new node) as Out of Service.
Step 2 Delete all invalid DWDM links between the two NEs from CTM.
Step 3 Complete the steps in the NTP-G129 Add a DWDM Node section, described in Cisco ONS 15454 DWDM Procedure Guide, Release 7.0.
Step 4 Mark the two NEs as In Service. The newly added NE will be automatically discovered when the new links are running.
3.5.1.4 Prerequisites for Adding ONS 15501, ONS 15530, and ONS 15540 NEs
Before adding ONS 15501, ONS 15530, and ONS 15540 NEs to CTM, verify that the NEs are set up correctly. You can perform most of the setup by using the NE CLI.
When adding NEs to the network, first add information to the SNMP Community String table; then, add one NE (in the Add New NE wizard) for each group of interconnected ONS 155xx NEs. This NE becomes the starting point for automatically discovering the other NEs. Immediately after you add this NE, the information in the SNMP Community String table is used to discover all other ONS 155xx NEs in the group.
The examples given in this section are provided as examples only. Refer to the relevant hardware documentation for detailed command information.
3.5.1.4.1 Hostnames and IP Addresses (Required)
All NEs must be configured with unique hostnames and IP addresses.
3.5.1.4.2 SNMP Community Strings (Required)
NEs must be reachable through SNMP. Use the snmp-server host command to add the CTM server to the list of SNMP trap destinations on each NE. Use the snmp-server enable traps command to enable trap generation for events and alarms.
Note Only SNMP version 2c traps are supported.
Each NE must have an entry in the SNMP Community String table, which is the basis for ONS 155xx autodiscovery and must contain valid community strings for each ONS 155xx in the network. Autodiscovery relies on Cisco Discovery Protocol (CDP) or on the configuring topology on the device.
There is one default entry in this table, which provides SNMP access to all ONS 155xx NEs in the network, provided you are using the default community strings.
You can add, modify, and delete entries in this table. All fields in an entry must be filled in; blank fields are not permitted.
To add entries to the SNMP Community String table:
Step 1 In the Domain Explorer window, choose Administration > ONS 155XX > ONS 155XX SNMP Settings Table. The SNMP Community String table opens. Table 3-5 provides descriptions.
Step 2 If the IP address of the NE is not already in the table, choose Edit > Add. The Add SNMP Parameters dialog box opens.
Note The SNMP Community String table contains a default entry for all ONS 15501, ONS 15530, and ONS 15540 NEs that are configured with the default community string.
Step 3 Add the IP address in the Target field; the IP addresses for all ONS 15501, ONS 15530, and ONS 15540 NEs must be specified in this table.
Step 4 Make sure that the correct community strings for each ONS 15501, ONS 15530, and ONS 15540 are in the table under the Read/Write field.
Step 5 (Optional) Configure the timeout and retry values.
Step 6 Click OK.
Table 3-5 Field Descriptions for the SNMP Community String Table
Field
|
Description
|
Target
|
IP address of the NE or range of NEs to which you are assigning the community strings in this entry. You can enter a specific IP address, wildcard characters (*) in any portion of the address, and ranges. For example:
•172.*.*.*
•172.20.[4-55].*
You can add a combination of general and specific entries, but the community strings are read from most specific to least specific. Wildcard characters cannot appear in ranges.
|
Read/Write
|
Community string that allows read/write access to the NEs in the entry.
|
Retry
|
Number of times the server attempts to communicate with the device before reporting that the device has timed out. By default, the server makes one retry. You can specify from 0 to 5 retries.
|
Timeout
|
Length of time the server waits for a response from the device before performing the first retry. The Cisco default timeout is 15 seconds. You can specify from 0 to 60 seconds.
|
Note•You can change SNMP Community String table entries at any time to match the community strings set on NEs. Routine community string changes take effect after the next health poll cycle or after a rediscovery. For information about the health poll or about discovery, see Chapter 4, "Maintaining an Efficient Network."
•You can modify SNMP parameters. In the SNMP Community String table, choose Edit > Modify to modify the SNMP parameters in the Modify SNMP Parameters window.
•You can delete SNMP parameters. In the SNMP Community String table, choose Edit > Delete to delete SNMP parameters.
3.5.1.4.3 Topology Setup
Appropriate topology information must be configured on ONS 15501, ONS 15530, and ONS 15540 NEs for automatic discovery of neighbors and discovery of physical links. For the ONS 15530 and ONS 15540, the topology can be configured in two ways: by using CDP learning or through IP using Ethernet. For the ONS 15501, the topology must be configured manually.
CDP neighbor information exchanged between the Optical Supervisory Channel (OSC) ports of two adjacent NEs, or between the wavelength division multiplexing (WDM) ports of two NEs that are directly connected, usually reflects the actual physical topology. CDP neighbor information can be used to populate the physical topology in these cases. To enable topology learning through CDP, you must first enable CDP on the corresponding OSC ports, and then enable topology learning via CDP. For example, assume that two ONS 15540 NEs are connected through the wdm0/0 port on each side, with OSC port Wave0 present on both sides:
1. The cdp enable CLI command, when entered in the interface configuration mode of interface Wave0 of both NEs, enables CDP on the two Wave0 interfaces.
2. The topology neighbor cdp proxy Wave0 CLI command, when entered in the interface configuration mode of interface wdm0/0 of both NEs, enables physical topology learning via CDP information exchanged between the Wave0 ports of the two NEs.
For NEs without OSC, manually configure the appropriate topology neighbors between all of the connected inter-NE links by using topology neighbor commands, as in the following examples:
•For the ONS 15530 and ONS 15540, if wdm0/0 of NE1 (IP address 1.1.1.1) is connected to wdm1/0 of NE2 (IP address 2.2.2.2) in a point-to-point topology, add the following commands to the configuration for interface wdm0/0 of NE1:
topology neighbor name NE2 port name Wdm1/0
topology neighbor agent ip-address 2.2.2.2
Add the following topology commands to the configuration for interface wdm1/0 of NE2:
topology neighbor name NE1 port name Wdm0/0
topology neighbor agent ip-address 1.1.1.1
•For the ONS 15501, configure unidirectional links on all connected NEs. For example, assume that two ONS 15540 NEs (NE1 with IP address 1.1.1.1 and NE2 with IP address 2.2.2.2) are connected to an ONS 15501 (EDFA1 with IP address 3.3.3.3) as follows:
NE1 wdm0/1 —> EDFA1 —> NE2 wdm0/2
Add the following commands to configure EDFA1:
neighbor-in host NE1 ip 1.1.1.1 port wdm0/1
neighbor-out host NE2 ip 2.2.2.2 port wdm0/2
Add the following commands to configure NE1:
topology neighbor name EDFA1 port name In-Port transmit
topology neighbor agent ip-address 3.3.3.3 transmit
Add the following commands to configure NE2:
topology neighbor name EDFA1 port name Out-Port receive
topology neighbor agent ip-address 3.3.3.3 receive
3.5.1.4.4 Patch Setup
Optical patches must be set up on all NEs between through interfaces, WDM interfaces, and so on.
For NEs with OSC, additional configuration is required. Add patches between the Wave and OSC filter interfaces. For example, if the Wave 0 interface is connected physically to the OSC filter 0/0 interface, add a patch using the following command:
patch Wave 0 Oscfilter 0/0
3.5.1.4.5 CiscoView (Optional)
At the time of the CTM R8.0 release, CiscoView is supported on Solaris 8 but not on Solaris 10. Therefore, CiscoView is not provided with CTM R8.0. Contact your Cisco account representative to obtain CiscoView for Solaris 10 once it becomes available.
3.5.1.4.6 Performance Monitoring (Optional)
Performance monitoring is optional, but you must enable it if you want to monitor threshold alarms and performance parameters.
You can enable performance monitoring by using the device CLI or CiscoView.
•For information about using the CLI, see the relevant hardware documentation.
•For information about using CiscoView, see Appendix J, "Using CiscoView to Configure and Monitor ONS 15501, ONS 15530, and ONS 15540 NEs."
3.5.1.5 Prerequisites for Adding ONS 1580x NEs
Before adding ONS 1580x NEs to CTM, complete the following prerequisites:
•For the ONS 15800, position the master Control and Monitoring Processor (CMP), named CTM-W or CMP-W-2E, in the physical location 01-01-15.
•For the ONS 15801 and ONS 15808, position the master CMP (named CTM-W or CMP-W-2E) in the physical location 01-01-13.
•For the ONS 15800, ONS 15801, and ONS 15808, the server must be able to telnet to port 1000 on the NEs. The network configuration must enable connectivity between the server machine and the ports on each managed NE.
3.5.1.6 Prerequisites for Adding CRS-1 and XR 12000 NEs
There are three parts to adding CRS-1 and XR 1200 NEs:
•Prerequisites
•Configuring a Communication Method
•Post Configuration
Prerequisites
Complete the following prerequisites before adding a CRS-1 or XR 12000 NE to CTM:
•Enter the following CLI command to add the Manageability pie (if it is not already installed):
install add <PIE_file_location> to <device> activate
•Enter the following CLI commands to enable CTM to establish initial communication with the NE:
telnet ipv4 server max-servers no-limit
domain ipv4 host <EMS_server_name> <EMS_server_IP_address>
logging events level informational
•Enable CDP on the NE for network discovery.
•If you are not using the username and password specified in the Control Panel > Security Properties > CRS-1 or XR 12000 tab, configure the username and password in the Domain Explorer > Network Element Properties > NE Authentication tab.
•All CRS-1 and XR 12000 NEs must be added in Domain Name System (DNS) or in the hosts file; otherwise, CTM cannot connect to the NEs. CTM uses DNS to look up the name of the NE and then connects to the NE through its name. Before adding the CRS-1 and XR 12000 NEs in DNS, do the following:
a. Enter the following command to verify the CRS-1 or XR 12000 NE's hostname:
The output of this command is the CRS-1 or XR 12000 NE's hostname.
b. In the CTM server CLI, ping the NE using the corresponding hostname. If the ping operation fails, configure the DNS with the correct NE hostname or edit the etc/hosts file.
Configuring a Communication Method
CTM communicates with Cisco IOS XR-based NEs using one of the following mechanisms: SSHV2, SSHV1, Telnet, CORBA, or CORBA SSL. The selected mechanism is determined by the configuration of the NE. When CTM establishes communication with an NE for management, it tries each method in the order listed, until it finds one that works.
Determine which method to use and make the appropriate router configuration before adding the NE to CTM.
•If communication between CTM and the NE is not over a secure network, choose an encrypted method such as SSH or CORBA SSL.
•If all communication is within a secure network, choosing a nonencrypted method may provide higher performance by avoiding encryption overhead.
Following are instructions for setting up each of the different methods:
•CORBA—To set up a router using the CORBA method, enter the following CLI command:
•CORBA SSL—To set up a router using the CORBA SSL method, do the following:
a. Generate RSA keys as shown in the following example:
RP/0/0/0:k2#crypto key generate rsa
The name for the keys will be: the_default
Choose the size of the key modulus in the range of 360 to 2048 for your General
Purpose Keypair. Choosing a key modulus greater than 512 may take a few minutes.
How many bits in the modulus [1024]: #### choose default.
Done w/ crypto generate keypair
b. Configure a trustpoint as shown in the following example:
RP/0/0/0:k2(config)#domain name cisco.com
RP/0/0/0:k2(config)#domain ipv4 host<certificate server name> <IP Address>
RP/0/0/0:k2(config)#commit
RP/0/0/0:k2(config)#crypto ca trustpoint root
enrollment url http://<cert_server>.cisco.com
RP/0/0/0:k2(config-trustp)#commit
RP/0/0/0:k2(config-trustp)#end
c. Authenticate the trustpoint (CA) as shown in the following example:
RP/0/0/0:k2#crypto ca authenticate root
Do you accept this certificate?? [yes/no]: yes
d. Enroll the certificate from the CA for the keys that were generated as shown in the following example:
RP/0/0/0:k2#crypto ca enroll root.
e. Use SSL on the router as shown in the following example, and make sure the router certificate has been procured:
RP/0/0/0:k2#sh crypto ca cert
Should show as `Available'
Now you are ready to run in SSL mode.
f. Enter the following CLI commands:
•Telnet—To set up a router using the Telnet method, enter the following CLI command:
•SSHV1—To set up a router using the SSHV1 method, do the following:
a. Generate RSA keys as shown in the following example:
RP/0/0/0:k2#crypto key generate rsa
The name for the keys will be: the_default
Choose the size of the key modulus in the range of 360 to 2048 for your General
Purpose Keypair. Choosing a key modulus greater than 512 may take a few minutes.
How many bits in the modulus [1024]: #### choose default.
Done w/ crypto generate keypair
b. Enter the following CLI command:
•SSHV2—To set up a router using the SSHV2 method, do the following:
a. Generate DSA keys as shown in the following example:
RP/0/0/0:k2#crypto key generate dsa
The name for the keys will be: the_default
Choose the size of the key modulus in the range of 360 to 2048 for your General
Purpose Keypair. Choosing a key modulus greater than 512 may take a few minutes.
How many bits in the modulus [1024]: #### choose default.
Done w/ crypto generate keypair
b. Enter the following CLI command:
Post Configuration
After configuring the NE, add a seed NE to CTM. CTM automatically discovers the interconnected CRS-1 or XR 12000 NEs.
Note The CRS-1 and XR 12000 discovery does not put the NE in service automatically. The discovery process adds the discovered NEs to CTM; however, you must mark the NEs as In Service.
3.5.1.7 Prerequisites for Adding Catalyst 6509 NEs
Before adding a Catalyst 6509, configure the NE with a valid community string. Then, add the NE to CTM. Network discovery is not supported for the Catalyst 6509.
Note CTM supports inventory and alarm management for the Cisco Catalyst 6509 in the context of supporting CRS-1 multichassis.
3.5.1.8 Prerequisites for Adding Cisco 7600 NEs
Before adding Cisco 7600 NEs to CTM, you must do the following:
•Configure SNMP on the Cisco 7600 NE:
–Use the snmp-server host command to add the CTM server to the list of SNMP trap destinations on each NE; for example:
snmp-server host <CTM_server_IP_address> version <#> <community_string>
–Use the snmp-server enable traps command to enable trap generation for events and alarms; for example:
snmp-server enable traps <trap_type>
•Configure the SNMP community string on the Cisco 7600 NE:
snmp-server community public RW
•Configure Syslog settings; perform the following steps:
–On the Cisco 7600, enter:
logging <CTM_server_IP_address>
–On the CTM server, add the following line to the /etc/syslog.conf file:
Note There must be a tab space between the filename and the logging level.
After modifying the /etc/syslog.conf file, restart the SyslogD process by entering the following commands in the order shown:
# /etc/init.d/syslog stop
# /etc/init.d/syslog start
•Configure the following traps by entering the snmpset command on the device:
–ciscoFlashCopyNotifyOnCompletion
–ciscoFlashDeviceInsertedNotif
3.5.1.9 Prerequisites for Adding Cisco MGX Voice Gateway Devices
Before adding a Cisco MGX NE, you must enable the NE service. You must also meet certain other specific prerequisites depending on the type of Cisco MGX NE you are adding. The following aspects must be configured before adding Cisco MGX NEs:
•Hostnames and IP addresses
•SNMP community strings
•Topology setup
•Performance monitoring (optional)
3.5.1.9.1 How Do I Configure the SNMP Community String?
CTM configures the community strings for SNMP management and supports various multiservice switching devices.
Caution The community strings on the devices and the community strings used by CTM do not synchronize automatically (except at the initial stage when the community strings on the devices are at default). You must explicitly change them on both sides (using the Network Element Properties pane in the Domain Explorer
on CTM and the CLI on the switch). See
Changing Community Strings Using the Domain Explorer and
Changing Community Strings Using the CLI. If this is not done, all SNMP requests fail, and the CTM database is inconsistent with the network.
To configure the SNMP community string, you must change the community strings on the devices through the CLI.
The following table describes the various options involved in configuring SNMP.
Table 3-6 SNMP Configuration Options
Option
|
Description
|
Domain Explorer > Network Element Properties pane > NE Authentication tab
|
After saving the community string information, the CTM processes use the new community strings for SNMP access.
Because users must configure the community strings on both of the devices through the CLI, and at the CTM stations through the Domain Explorer, there is a possibility of typing in mismatched community strings. This results in the node with the mismatched community strings becoming either not discovered or unreachable to CTM.
Note Configured community strings cannot contain underscore (_) or ampersand (@) characters. Also, spaces are not allowed in community strings and service-level passwords.
|
SNMP access security
|
Enter the cnfsnmp command on CTM by using a secured shell to change the community strings and passwords.
|
3.5.1.9.2 Setting Up Nonstandard Community Strings
The standard community strings are defined as default community strings. If you change the standard (default) community strings to a different value, the standard community strings become nonstandard.
To set up nonstandard community strings or to change a service-level password, use Domain Explorer > Network Element Properties pane > NE Authentication tab.
Note This method affects only CTM. You must make sure that community strings and passwords within CTM match those on the switches.
3.5.1.9.3 Changing Community Strings Using the Domain Explorer
To change the SNMP get and set community strings for selected nodes:
Step 1 In the Domain Explorer Hierarchy pane, select the node.
Step 2 In the NE Authentication tab, you can change the SNMP community string to change the SNMP get community string, or change the SNMP set only community string.
Step 3 Click Save.
3.5.1.9.4 Changing Community Strings Using the CLI
To change the SNMP get community strings for selected nodes:
Step 1 Open a terminal window and SSH or Telnet to the switch.
Step 2 Enter the cnfsnmp command to change the SNMP get community string for the selected nodes as follows:
xxyyzz% cnfsnmp community [ro|rw]
where ro is the SNMP get community string and rw is the SNMP set only community string.
Step 3 Enter the following command to configure the SNMP get community string:
xxyyzz% cnfsnmp community public ro
Step 4 Enter the following command to check that the community string has changed:
You will see output similar to the following example:
xxyyzz System Rev: 05.00 Dec. 14, 2004 20:04:14 GMT
MGX8850 Node Alarm: MAJOR
System Location: building 3
To change the SNMP set community strings for a node or switch:
Note The following procedure changes the SNMP set community string for the node that you SSH or Telnet to, not for all instances of that node. You must change the SNMP set community string on all instances of the node.
Step 1 Open a terminal window and SSH or Telnet to the switch.
Step 2 Enter the cnfsnmp command to change the SNMP set community string for all nodes as follows:
xxyyzz% cnfsnmp community private rw
Step 3 Enter the following command to check that the community string has changed:
You will see output similar to the following example:
xxyyzz System Rev: 05.00 Dec. 14, 2004 20:04:14 GMT
MGX8850 Node Alarm: MAJOR
System Location: building 3
3.5.1.9.5 Changing the Service-Level Passwords Using the CLI
To change the service-level password for the current service-level user:
Note The following procedure changes the service-level password for the node that you SSH or Telnet to, not for all instances of that node. You must change the service-level password on all instances of the node.
Step 1 Open a terminal window and SSH or Telnet to the switch.
Step 2 Enter the cnfpasswd command to change the service-level password for all nodes. For example:
xxyyzz.7.PXM.a > cnfpasswd
Local password for user cisco changed.
Step 3 When you are prompted for a password, you must:
a. Enter the existing password.
b. Enter the new password.
c. Re-enter the new password for confirmation.
3.5.2 Adding NEs
From the Domain Explorer or Subnetwork Explorer tree, you can use the Add New NE wizard to add a single NE or multiple NEs.
3.5.2.1 Adding a Single NE
Note If you are adding an ONS 155xx NE, first verify that the NE is covered by an entry in the SNMP Community String table.
Step 1 Select a node in the Domain Explorer or Subnetwork Explorer tree; then, choose File > Add Network Element(s) (or click the Add Network Element(s) tool). The Add New NE wizard opens. Table 3-7 provides descriptions.
Note You cannot add a new NE to the Discovered Network Elements or Deleted Network Elements groups.
Step 2 Enter the following information:
a. NE model
b. NE type
c. NE addition—Click one of the following radio buttons:
–Single NE Addition—To add only one NE.
–Single NE Addition (Use TL1 Tunnel)—To add only one tunnel NE (TNE). CTM can connect to a TNE that belongs to an OSI network behind a non-Cisco GNE.
d. IP address (when adding a single NE)
e. Gateway NE (when adding a single TNE)
Step 3 Click Next.
Note If you click Finish in this window, Cisco default values are assigned to the remaining fields. In addition, the NE is placed in a preprovisioned state, and discovery does not start automatically. If you want to add the NE in a nonpreprovisioned state, click Next and proceed to the next window; then, in the Operational State field, select a state other than Preprovisioned.
Step 4 Enter the following information. Fields shown depend on the NE type.
a. NE ID
Note Do not use "CTM" as an NE ID because the Alarm Browser might contain CTM alarms with the source ID "CTM." It will be difficult to distinguish between NE alarms and CTM alarms if they both have the same source ID ("CTM"). For the same reason, do not cause CTM to automatically populate an NE whose NE ID is "CTM."
Note If the NE ID field is left blank, it will default to the IP address. After communication is established, CTM discovers the NE ID from the NE.
Note For the CRS-1 and XR 12000, do not use special characters in the NE ID. Special characters should not be used in the router name, DNS/NIS, or /etc/hosts file.
b. Alias
c. Operational state
d. SNMPv1
e. SNMPv3
f. SNMP community string (Available if SNMPv1 is selected)
g. SNMP set only community string (Available if SNMPv1 is selected)
h. SNMPv3 request user (Available if SNMPv3 is selected)
i. SNMPv3 trap user (Available if SNMPv3 is selected)
Note The first MGX node that is added to CTM is always associated with the default user listed in the SNMPv3 request user and SNMPv3 trap user drop-down lists. The SNMPv3 Users Table is only available after an MGX node is added to CTM.
j. NE service-level username
k. NE service-level password
l. Description
m. Location name
n. Subnetwork ID
o. Network partition ID
p. Role type
Caution Make sure to specify the correct partition. If the wrong partition is specified, the new NE is not added and an error message appears.
Step 5 Click Next if you are adding an ONS 15302, ONS 15305, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS 15501, ONS 15530, ONS 15540, or ONS 15600 SONET NE.
Note If you click Finish in this window, Cisco default values will be assigned to the remaining fields.
Step 6 Click Finish if you are adding a Cisco 7600, Cisco MDS 9000, Catalyst 6509, ONS 15216, ONS 15310 CL, ONS 15310 MA, ONS 15600 SDH, ONS 15800, ONS 15801, ONS 15808, CRS-1, XR 12000, Cisco MGX, or Not Managed/Other Vendor NE.
Step 7 Select the grouping option for the NE.
Step 8 Click Finish to add the new NE to the domain.
Wait 2 to 5 minutes while the CTM server completes the node discovery. (Not applicable if the operational state is Preprovisioned.)
Step 9 Check to see if the communication state is correct. If CTM cannot connect to the NE, the NE displays an unavailable communication state icon in the tree.
Step 10 Verify that the NE software version is listed in the Supported NE table (Domain Explorer > Administration > Supported NE Table). If it is not listed, see 4.3.11 Adding a New NE Software Version to the CTM Domain, page 4-43.
3.5.2.2 Adding Multiple NEs
Step 1 Select a node in the Domain Explorer or Subnetwork Explorer tree; then, choose File > Add Network Element(s) (or click the Add Network Element(s) tool). The Add New NE wizard opens. Table 3-7 provides descriptions.
Note You cannot add a new NE to the Discovered Network Elements or Deleted Network Elements groups.
Step 2 Enter the following information:
a. NE model
b. NE type
c. NE addition—Click the Bulk NE Addition radio button.
Note Bulk NE addition does not apply to passive ONS 15216 NEs or Not Managed/Other Vendor NEs.
d. IP address range—Enter the IP addresses in the From and To fields; then, click Add.
Note The IP addresses must be from the same subnetwork.
e. IP address selection—Add or remove IP addresses using the Add and Remove buttons.
Step 3 Click Next.
Note If you click Finish in this window, Cisco default values are assigned to the remaining fields.
Step 4 Enter the following information. Fields shown depend on the NE type.
a. NE ID—Display only.
b. Alias—Display only.
c. Operational state
d. SNMPv1
e. SNMPv3
f. SNMP community string (Available if SNMPv1 is selected)
g. SNMP set only community string (Available if SNMPv1 is selected)
h. SNMPv3 request user (Available if SNMPv3 is selected)
i. SNMPv3 trap user (Available if SNMPv3 is selected)
Note The first MGX node that is added to CTM is always associated with the default user listed in the SNMPv3 request user and SNMPv3 trap user drop-down lists. The SNMPv3 Users Table is only available after an MGX node is added to CTM.
j. NE service-level username
k. NE service-level password
l. Description
m. Location name
n. Subnetwork ID
o. Network partition ID
p. Role type
Caution Make sure to specify the correct partition. If the wrong partition is specified, the new NE is not added and an error message appears.
Step 5 Click Next if you are adding an ONS 15302, ONS 15305, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS 15501, ONS 15530, ONS 15540, or ONS 15600 SONET NE.
Note If you click Finish in this window, Cisco default values are assigned to the remaining fields.
Step 6 Click Finish if you are adding a Cisco 7600, Cisco MDS 9000, Cisco MGX, Catalyst 6509, ONS 15310 CL, ONS 15310 MA, ONS 15600 SDH, ONS 15800, ONS 15801, ONS 15808, CRS-1, or XR 12000 NE.
Step 7 Select the grouping option for the NE.
Step 8 Click Finish to add the NEs to the domain.
Wait 2 to 5 minutes while the CTM server completes the node discovery. (Not applicable if the operational state is Preprovisioned.)
Step 9 Check to see if the communication state is correct. If CTM cannot connect to the NE, the NE displays an unavailable communication state icon in the tree.
Step 10 Verify that the NE software version is listed in the Supported NE table (Domain Explorer > Administration > Supported NE Table). If it is not listed, see 4.3.11 Adding a New NE Software Version to the CTM Domain, page 4-43.
Table 3-7 Field Descriptions for the Add New NE Wizard
Field
|
Description
|
NE Addition Panel
|
NE Model
|
Select the NE model (Cisco 7600, Cisco Catalyst 6509, Cisco CRS-1, Cisco XR 12000, Cisco MDS 9000, Cisco MGX Voice Gateway, Cisco ONS 15216 [all types], Cisco ONS 15302, Cisco ONS 15305, Cisco ONS 15305 CTC, Cisco ONS 15310 CL, Cisco ONS 15310 MA, Cisco ONS 15327, Cisco ONS 15454 SONET, Cisco ONS 15454 SDH, Cisco ONS 15501, Cisco ONS 15530, Cisco ONS 15540 ESP, Cisco ONS 15540 ESPx, Cisco ONS 15600 SONET, Cisco ONS 15600 SDH, Cisco ONS 15800, Cisco ONS 15801, Cisco ONS 15808, or Not Managed/Other Vendor).
Note CTM supports inventory and alarm management for the Cisco Catalyst 6509 in the context of supporting CRS-1 multichassis.
|
NE Type
|
Select the type of NE.
Note Available types depend on the selected NE model.
|
NE Addition
|
Click one of the following radio buttons. The available fields will change, depending on which option you select:
•Single NE Addition—To add only one NE.
•Bulk NE Addition—To add several NEs simultaneously.
•Single NE Addition (Use TL1 Tunnel)—To add only one TNE.
|
IP Address (for single NE additions)
|
Enter a unique IP address for the NE. It must be in the form ddd.ddd.ddd.ddd, where ddd is a decimal octet expressed as an integer between 0 and 255. The first octet cannot be a zero.
Note Prior to the NE ID discovery, CTM uses the NE IP address as a temporary NE ID.
Note The IP address field is unavailable when adding passive NEs and Not Managed/Other Vendor NEs.
|
From IP Address (for bulk NE additions)
|
Enter the beginning IP address for the range of NEs you want to add.
|
To IP Address (for bulk NE additions)
|
(Optional) Enter the ending IP address for the range of NEs you want to add. Click Add to add the range to the Selected IP field.
|
IP Address Selection (for bulk NE additions)
|
Select one or more IP addresses in the Deleted IP field and click Add to add them to the Selected IP field. Select one or more IP addresses in the Selected IP field and click Remove to remove them. Only the IP addresses in the Selected IP field are affected by clicking Next.
|
Gateway NE (for single TNE additions)
|
If you selected Single NE Addition (Use TL1 Tunnel) in the NE Addition area, the Gateway NE area becomes visible. Fill in the following fields to add a TNE to the CTM domain. The following NE models support TL1 tunnels: ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH.
•GNE IP Address—IP address of the non-Cisco GNE that supports the TL1 tunnel. This field is mandatory.
•Use Default TL1 Port—If selected, the default value for the TL1 port is used.
•Use Other TL1 Port—If selected, specify the TL1 port number in the text field.
•TL1 Encoding Mode—Specify the TL1 encoding mode:
–LV + Base64 Payload: (Default) If selected, and if Use Default TL1 Port is selected, TL1 port 3081 is used.
–LV + Binary Payload: If selected, and if Use Default TL1 Port is selected, TL1 port 3081 is used.
–Raw: If selected, and if Use Default TL1 Port is selected, TL1 port 3082 is used.
•GNE Login Required—If checked, a login is required on the non-Cisco GNE. The GNE login uses the following settings:
–GNE TID: The value specified in the GNE TID field.
–Username and password: The values specified in the Control Panel > Security Properties pane > CTC-Based SDH or CTC-Based SONET tab > CTM Server - GNE Connection (TL1 Tunnel) area.
|
NE Properties Panel
|
NE ID
(Display only for bulk NE addition)
|
Enter a unique name for the NE in the form of an ASCII text string. Apostrophes (') and quotation marks (") are not accepted. The NE ID you enter should be the same as the NE ID that is configured on the NE itself. If it is not the same, this field will be updated with the NE hostname.
Note Do not use "CTM" as an NE ID because the Alarm Browser might contain CTM alarms with the source ID "CTM." It will be difficult to distinguish between NE alarms and CTM alarms if they both have the same source ID ("CTM"). For the same reason, do not cause CTM to automatically populate an NE whose NE ID is "CTM."
Note If the NE ID field is blank, it will default to the IP address. After communication is established, CTM autodiscovers the NE ID from the NE.
Note For the CRS-1 and XR 12000, do not use special characters in the NE ID. Special characters should not be used in the router name, DNS/NIS, or /etc/hosts file.
|
Alias
(Display only for bulk NE addition)
|
Enter a unique alias name for the NE. The alias name can contain alphanumeric characters. It also supports international character sets.
|
Operational State
|
Specify the operational state of the NE. There are four states:
•Preprovisioned—The NE has been added to the database for provisioning but is not yet in service.
•Under Maintenance—The NE is temporarily under maintenance but requires monitoring.
•In Service—The NE is currently deployed and requires monitoring.
•Out of Service—The NE has been marked Out of Service and does not require monitoring.
|
SNMPv1
|
Sets the SNMP version of the NE to SNMPv1.
|
SNMPv3
|
Sets the SNMP version of the NE to SNMPv3.
|
SNMP Community String
|
(Available if SNMPv1 is selected) Enter the SNMP community string for the NE. The Cisco default is public.
Note The SNMP community string applies only to the Cisco 7600, Catalyst 6509, ONS 15216 EDFA2, ONS 15216 EDFA3, ONS 15302, ONS 15305, ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, and Cisco MGX NEs.
Note When adding an ONS 155xx NE, this field is unavailable. You must enter the community strings in the SNMP Community String table before adding the NE.
|
SNMP Set Only Community String
|
(Available if SNMPv1 is selected) Enter the set-only community string name used in SNMP messages. You must provide the community string name to give the user SNMP read access to the device.
|
SNMPv3 request user
|
(Available if SNMPv3 is selected) Select the request user that CTM uses to communicate with the switch when initiating SNMPv3 requests.
|
SNMPv3 trap user
|
(Available if SNMPv3 is selected) Select the trap user that CTM uses to validate the incoming SNMPv3 traps.
|
NE Service Level Username
|
Enter the username that the CTM server uses to connect to NEs.
|
NE Service Level Password
|
Enter the password to use for CTM server-to-NE connections.
|
Description
|
Enter a description of the NE.
|
Location Name
|
Enter the NE geographic location.
|
Subnetwork ID (not selectable if automatic subnetwork grouping is enabled)
|
Select the subnetwork ID associated with the NE.
|
Network Partition ID
|
Select the network partition associated with the NE.
|
Role Type
|
Select the role type associated with the NE. Options are:
•None
•P (Provider Backbone)
•PE (Provider Edge Router)
•RR (Router Reflector)
|
Group Properties Panel
|
Grouping Option for Discovered NEs
|
Select a grouping option for the discovered NEs. The groupings are as follows:
•Group discovered NEs in the Discovered Network Elements group
•Group NEs with the NE that discovered them (Cisco default)
•Group NEs by subnet
|
Note•For CTM to communicate with certain NE types, you must set the username and password that the CTM server uses to establish a session with the NE. To enter user information, choose Administration > Control Panel > Security Properties tab; then, enter the username and password on the Cisco 7600, ONS 15216 EDFA2, ONS 15216 EDFA3, ONS 15216 OADM, ONS 15305 CTC, ONS 15327, ONS 15454, CRS-1, XR 12000, ONS 15454 SDH, ONS 155XX, ONS 15600 SDH, ONS 15600, or ONS 158XX tab.
•Regardless of the actual size of the password, the Password and Confirm Password fields display only a fixed-length string. The fixed-length string is 12 asterisks (*).
•For the ONS 15800, ONS 15801, and ONS 15808, a misconfigured password setting can affect configuration, PM information collection, and CTM GateWay/TL1 services.
•For more information, see 8.3.3.14 Configuring CTM Security Parameters, page 8-33. For NEs that do not use SNMP, you can set the username and password in the NE Authentication tab of the Domain Explorer. For more information, see 8.4.1 Setting NE Authentication, page 8-45.
•When adding more than one DCC-connected, CTC-based NE, add one NE to a subnetwork and allow the other NEs to be automatically discovered and placed in the same subnetwork. When moving NEs from one subnetwork to another, move all DCC-connected NEs to the same subnetwork. Move the entire subnetwork instead of splitting DCC-connected NEs between subnetworks.
•Errors encountered while adding NEs are listed in the Error Log.
3.5.2.3 Adding the First MGX NE with a Non-Default User
Step 1 Add the MGX NE. See Adding NEs for more information.
Step 2 Add an SNMPv3 user. See 8.4.7.2 Adding an SNMPv3 User, page 8-73 for more information.
Step 3 Select the MGX NE in the Domain Explorer tree; then, click the NE Authentication tab in the Network Element Properties pane.
Step 4 Choose the SNMPv3 radio button.
Step 5 Select the SNMPv3 user listed in the SNMPv3 Request User and SNMPv3 Trap User drop-down lists.
Step 6 Click Save.
Note The SNMPv3 Users Table becomes available after adding the first MGX NE to CTM. You can add any number of SNMPv3 users using the SNMPv3 User Table. All the SNMPv3 users you added will be available in the SNMPv3 request user and SNMPv3 trap user drop-down lists of the Add New NE wizard so you can associate the succeeding MGX NEs with the corresponding SNMPv3 user in the Add New NE wizard instead of the Domain Explorer. For other modifications that are not SNMPv3-related, use the NE Authentication tab in the Domain Explorer.
3.5.2.4 Managing the SNMP Mode—Cisco MGX Voice Gateway Devices
One of the following occurs when an MGX NE is added to CTM:
•The MGX NE is in SNMPv1 mode and is added to CTM in SNMPv1 mode.
•The MGX NE is in SNMPv3 mode and is added to CTM in SNMPv3 mode.
•The MGX NE is in SNMPv1 mode and is added to CTM in SNMPv3 mode.
•The MGX NE is in SNMPv3 mode and is added to CTM in SNMPv1 mode.
The following table provides the MGX NE state when they are added to CTM.
Table 3-8 MGX NE State When Added to CTM
SNMP Mode on the MGX NE
|
SNMP Mode of the MGX NE in CTM
|
Communication State
|
Operational State
|
V1
|
V1
|
Available
|
In Service
|
V3 or V3 fully secured mode (FSM)
|
V3
|
Available
|
In Service
|
V1
|
V3
|
•Available—If the switch image is SNMPv3-capable
•Unavailable—If the switch image is not SNMPv3-capable
|
Not applicable
|
V3 or V3 FSM
|
V1
|
Unavailable
|
Not applicable
|
If an MGX NE already exists in CTM, you can change the SNMP mode on the NE or in CTM. See Table 3-9 for information on the MGX NE state when the SNMP mode is changed on the NE and Table 3-10 for information on the MGX NE state when the SNMP mode is changed in CTM.
Table 3-9 MGX NE State After Changing the SNMP Mode on the NE
Change of SNMP Mode on the MGX NE
|
SNMP Mode of the MGX NE in CTM
|
Communication State
|
Operational State
|
Changed from V1 to V3
|
V1
|
Available
|
In Service - Sync Fail1
|
Changed from V1 to FSM
|
V1
|
Unavailable
|
Not applicable
|
Changed from V3 to V1
|
V3
|
Available
|
In Service
|
Changed from FSM to V1
|
V3
|
Available
|
In Service
|
Table 3-10 MGX NE State After Changing the SNMP Mode in CTM
SNMP Mode on the MGX NE
|
Change of SNMP Mode of the MGX NE in CTM
|
Communication State
|
Operational State
|
V1
|
Changed from V1 to V3
|
•Available—If the switch image is SNMPv3-capable
•Unavailable—If the switch image is not SNMPv3-capable
|
Not applicable
|
V1
|
Changed from V3 to V1
|
Available
|
In Service
|
V3
|
Changed from V1 to V3
|
Available
|
In Service
|
V3
|
Changed from V3 to V1
|
Available
|
In Service - Sync Fail1
|
FSM
|
Changed from V1 to V3
|
Available
|
In Service
|
FSM
|
Changed from V3 to V1
|
Unavailable
|
Not applicable
|
3.5.3 Copying an NE from One Group to Another
Groups for multiple users can easily be created in CTM. Just copy the same NE into different groups.
Step 1 In the Domain Explorer tree, select the NE to be copied.
Step 2 Choose Edit > Copy (or click the Copy tool).
Step 3 Select the group or management domain node where the NE will be pasted and choose Edit > Paste (or click the Paste tool). This pastes the NE under the selected node.
Note An NE cannot be pasted into the Discovered Network Elements or Deleted Network Elements groups. Also, it cannot be pasted into a group where the same instance of the NE already exists.
Tip The drag-and-drop feature can also be used to copy NEs. Hold down the Ctrl key on the keyboard and use the mouse to drag and drop the NE to a new location.
Note Since they cannot see the entire domain, users with the Assign NEs property (Provisioner, Operator, and some custom user profiles) are not allowed to modify the topology using copy, cut, paste, or drag and drop.
3.5.4 Moving an NE from One Group to Another
CTM provides drag-and-drop capabilities to allow you to easily move NEs from one group to another.
Step 1 In the Domain Explorer tree, select the NE to be moved.
Step 2 Choose Edit > Cut, then Edit > Paste. You can also use the mouse to drag and drop the selected NE to a new location.
Note You cannot copy or move NEs into the Discovered Network Elements group.
Note Since they cannot see the entire domain, users with the Assign NEs property (Provisioner, Operator, and some custom user profiles) are not allowed to modify the topology using copy, cut, paste, or drag and drop.
3.5.5 Moving an NE from One Network Partition to Another
Caution CTM cannot manage circuits across network partitions. Make sure that all connected NEs are managed under the same network partition.
Note Do not add SONET and SDH NEs in the same network partition.
Step 1 In the Domain Explorer tree, select File > Subnetwork Explorer. The Subnetwork Explorer opens.
Step 2 Identify the network partition ID:
a. In the Subnetwork Explorer tree, click the new network partition where you will move the NE.
b. In the Network Partition Properties pane, click the Identification tab.
Step 3 Identify the subnetwork(s) assigned to the new network partition.
Note A subnetwork can only be assigned to one network partition.
Step 4 In the Domain Explorer, click the NE to be moved. In the Network Element Properties pane, click the Address tab.
Step 5 Change the subnetwork ID to a subnetwork ID assigned to the new network partition. Choose from the list of subnetwork IDs; then, click OK.
Step 6 Click Save.
3.5.6 Automatically Grouping NEs in Subnetworks
Note An NE can be assigned to only one subnetwork.
CTM allows you to automatically group NEs in a subnetwork. When this feature is enabled, CTM automatically creates the subnetwork, which consists of NEs that are connected by topological links; you cannot change the subnetwork of the NE. This means that:
•When adding a new NE, the option to select the subnetwork ID is disabled. The Subnetwork ID field displays <System Default>.
•In the Address tab of the Domain Explorer > Network Element Properties pane, you cannot change the subnetwork ID.
•You cannot drag and drop NEs in the Subnetwork Explorer tree.
Step 1 In the Domain Explorer window, choose Administration > Control Panel and click UI Properties.
Step 2 In the Subnetwork Grouping area, check the Automatically Group NEs in Subnetworks check box.
Step 3 Click Save.
Note If a topological link is deleted while NEs are automatically grouped in subnetworks, CTM deletes isolated NEs, creates a new subnetwork, and moves the deleted NEs to the new subnetwork.
If a topological link is discovered or added manually, it will result in a network that contains disjointed subnetworks. CTM deletes the NEs from the disjointed subnetwork that contains fewer NEs, deletes the disjointed subnetwork, and adds the deleted NEs to the subnetwork where the topological link was added manually.
3.5.7 Deleting NEs
From the Domain Explorer tree, you can delete a single NE, multiple NEs, or out-of-service NEs.
Note Before deleting an NE, make sure to delete all links from the NE. See Deleting Links.
3.5.7.1 Deleting a Single NE
Step 1 In the Domain Explorer tree, select the NE that will be deleted.
Step 2 In the Status tab of the Network Element Properties pane, set the Operational State field to Out of Service; then, click Save. Click Yes in the confirmation dialog box.
Note If there is more than one instance of an NE (that is, if the NE was copied so two versions exist), you do not need to move the NE to Out of Service before deleting it.
Step 3 You can delete either a selected instance of the NE or all instances of the NE:
•Deleting the selected instance of the NE—Only the specific NE that you selected in the Domain Explorer tree is deleted. To delete the selected instance of the NE, choose Edit > Delete; then, click Yes. If this is the last instance of the NE, the NE is placed in the Deleted Network Elements group.
Note A GNE that has associated subtending NEs cannot be deleted. A subtending NE can be disassociated from the GNE by removing the NE from the CTM domain or by assigning it to a different GNE.
•Deleting all instances of the NE—All NEs in the user domain that have the same NE ID are deleted. To delete all instances of the selected NE, choose Edit > Delete All; then, click Yes in the confirmation dialog box. The NE is placed in the Deleted Network Elements group.
Note Check the Audit Log to confirm that the selected NE has been successfully deleted from the database. The deletion is not complete until the following message is displayed in the Audit Log: AUD-5015 <NE ID> has been successfully purged. See "8.5.1 Viewing the Audit Log" section on page 8-76 for information on how to view the Audit Log.
No client views for an NE can be opened in the Deleted Network Elements group. Also, no properties of a deleted NE can be modified. The deleted NE and its associated data are removed from all client views except the Domain Explorer.
Note Only out-of-service or preprovisioned NEs can be placed in the Deleted Network Elements group.
Note If a CTC-based NE is deleted and then DCC connectivity to the deleted NE is removed, CTM rediscovers the deleted NE. If DCC connectivity is removed before deleting the NE, CTM does not rediscover the NE. Therefore, remove DCC connectivity to the NE before deleting the NE from CTM.
3.5.7.2 Deleting Multiple NEs
Step 1 For each NE that will be deleted:
a. In the Domain Explorer tree, select the NE that will be deleted.
b. In the Status tab of the Network Element Properties pane, set the Operational State field to Out of Service; then, click Save.
Step 2 In the Domain Explorer tree, select again all the NEs that will be deleted. To select multiple NEs, press and hold down the Ctrl button; then, click each NE that will be deleted.
Step 3 You can delete the selected instance of the NEs or all instances of the NEs:
•Deleting the selected instance of the NE—Only the specific NEs that you selected in the Domain Explorer tree will be deleted. To delete the selected instance of the NEs, choose Edit > Delete; then, click Yes in the confirmation dialog box. If the selected NEs are the last instance of the NE, the NEs are placed in the Deleted Network Elements group.
Note A GNE that has associated subtending NEs cannot be deleted. A subtending NE can be disassociated from the GNE by removing the NE from the CTM domain or by assigning it to a different GNE.
•Deleting all instances of the NEs—All NEs in the user domain that have the same NE ID as the NE being deleted will be deleted. To delete all instances of the selected NEs, choose Edit > Delete All; then, click Yes in the confirmation dialog box. The NEs are placed in the Deleted Network Elements group.
Note Both the Delete and Delete All menu options are enabled if at least one of the selected NEs can be deleted. The confirmation dialog box lists the NEs that can and cannot be deleted.
Note Check the Audit Log to confirm that the selected NEs have been successfully deleted from the database. The deletion is not complete until the following message is displayed in the Audit Log: AUD-5015 <NE ID> has been successfully purged. See "8.5.1 Viewing the Audit Log" section on page 8-76 for information on how to view the Audit Log.
Note You can use the mouse to drag and drop the selected NEs to the Deleted Network Elements group only if all the selected NEs can be deleted.
3.5.7.3 Using the prune_ne.sh Script to Remove an Out-of-Service NE from the Database
Note It is recommended that you delete an out-of-service NE from the CTM client (see Deleting a Single NE or Deleting Multiple NEs), because doing so does not involve stopping and starting the CTM server.
Aside from using the Domain Explorer to remove an out-of-service NE from the database, you can also use the prune_ne.sh script.
Note Shut down the CTM server and all CTM clients before running the prune_ne.sh script.
Step 1 In the Domain Explorer tree, select the NE that will be removed.
Step 2 In the Status tab of the Network Element Properties pane, set the Operational State field to Out of Service; then, click Save.
Step 3 Close the CTM client.
Step 4 Log into the CTM server as the root user and enter the following command to stop the server:
Step 5 Enter the following command to verify that all CTM processes have stopped:
a. If any processes are still running, enter the following command:
b. Re-enter the following command to verify that the processes have stopped:
Step 6 Change the directory to /opt/CiscoTransportManagerServer/bin and enter the following command:
Step 7 Enter the following command to start the CTM server:
3.5.7.4 Removing a Deleted NE
Step 1 In the Domain Explorer tree, click the Deleted Network Elements group.
Step 2 Click the NE that will be removed from the CTM domain.
Step 3 Choose Edit > Delete; then, click Yes. This removes the NE from the client view and deletes all records associated with the NE from the database.
Note•Wait until all records associated with the NE are deleted from the database before adding the NE back again.
•The amount of time it takes to prune NEs depends on the amount of data that needs to be removed, the amount of data in the database, the system performance, and so on. The Deleted Network Elements group is seen by users who have add_delete_NE_group operation permission. You can purge or undelete an NE that is in the Deleted Network Elements group only if that NE was assigned to you.
3.5.8 Restoring a Deleted NE
Step 1 In the Domain Explorer tree, click the Deleted Network Elements group.
Step 2 Click the NE that will be restored.
Step 3 Choose Edit > Undelete.
All instances of the NE are restored to their previous locations in the Domain Explorer tree.
Note If the original parent group no longer exists, CTM does not recreate the group. Instead, CTM restores the NE under the management domain node.
3.5.9 Searching for an NE
CTM allows you to search for a specific NE in the network. See 1.5.5.1 Finding Data in the Domain Explorer, page 1-38.
3.6 How Do I Build Links?
A link is a connection between two termination points (TPs). CTM represents the physical connectivity between NEs in the domain by defining the physical links between NEs. It is through these links that circuits (if supported on the NE) are provisioned. Links can be viewed, modified, created, and deleted. CTM automatically discovers links between CTC-based (including the ONS 15305 R3.0) and ONS 155xx NEs. For CTC-based NEs, links are autodiscovered only when the DCCs are created on both ends of the link. Autodiscovery requires configuration on ONS 15501, ONS 15530, and ONS 15540 NEs. For the CRS-1, Cisco 7600, ONS 15216, ONS 15302, ONS 15305, ONS 15800, ONS 15801, ONS 15808, and MDS 9000, links are manually added. For autodiscovery of links between Cisco 7600 NEs, CDP must be enabled on both NEs.
Note•An autodiscovered link between two TPs will override previously autodiscovered links and any manual links on any of the TPs.
•Link autodiscovery is supported on CRS-1 and XR 12000 NEs when CDP is enabled on the router or interface.
•For manual links on CRS-1 NEs, if a physical layer interface module (PLIM) port is used for one layer rate in a link, that port is not available for other links in the same layer. For example, if a PLIM port is used for a 10G-ITU link at the Physical layer, that port cannot be used for a 10 Gigabit Ethernet link at the Physical layer.
•Links are not supported for the Catalyst 6509.
3.6.1 Setting Up CRS-1 and XR 12000 NEs for Link Discovery
For the CRS-1 and XR 12000, links are physical connections between CRS-1s and XR 12000s. For autodiscovery of links and devices, CDP must be enabled. CTM queries the CRS-1 or XR 12000 for cdp neighbors and builds the topology if the neighboring NEs have the minimum configuration required for EMS support.
For Cisco IOS XR version 3.3.0 and 3.3.1, a new command has been added, which causes an NE to send messages about changes detected by CDP. If this command is enabled, CTM can receive the messages and update its representation of the network. For a link between two NEs that are managed by CTM, the command must be applied to both NEs.
For example, if there is a CDP link between Router 1 and Router 2, complete the following steps:
Step 1 Log into the CRS-1 or XR 12000 NE.
Step 2 Enter the following commands to configure Router 1:
Router1(config)# cdp log adjacency changes
Step 3 Enter the following commands to configure Router 2:
Router2(config)# cdp log adjacency changes
3.6.2 Setting Up ONS 15501, ONS 15530, and ONS 15540 NEs for Link Discovery
Links between ONS 15501, ONS 15530, and ONS 15540 NEs are automatically discovered and displayed, provided that physical topology is configured correctly on all ONS 15501, ONS 15530, and ONS 15540 NEs in the network. Each physical topology neighbor of an NE represents a physical link between the NE and its neighbor NE. The ONS 15501, ONS 15530, and ONS 15540 discovery service collects physical topology information and converts it into physical links displayed by CTM.
Links between ONS 15501, ONS 15530, and ONS 15540 devices can be bidirectional or unidirectional. A unidirectional link operates in the context of the transmit or receive side of a fiber connection and is represented by an arrowhead link in the Network Map. For example, an ONS 15501 connected to the transmit side of an ONS 15540 ESP WDM port is represented as a directional link from the transmit side of the ONS 15540 WDM port to the receive side of the ONS 15501.
Make sure that have you have set up the topology on all of the ONS 15501, ONS 15530, and ONS 15540 NEs in your network, as described in Prerequisites for Adding ONS 15501, ONS 15530, and ONS 15540 NEs.
3.6.3 Overview of Supported Links
Links can be created at different layer rates depending on the card type. See Table 3-11 for the links supported between NEs at compatible layer rates. See Table 3-12 for the supported links per layer rate.
Note Links can be created for an MDS 9000 or Not Managed/Other Vendor NE only if the NE is in service or under maintenance. Links created for CTC-based NEs are for circuit routing purposes only. Links created for MDS 9000 or Not Managed/Other Vendor NEs are not used for circuit routing.
Note Physical nonroutable links can be created between NEs that are in the same or a different network partition(s).
Links between TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, TXP_MR_10G, 2.5G_DM, 2.5G_DMP, TXP_MR_10E, or MXP_MR_10E cards are automatically discovered and cannot be manually created. They can exist if:
•The layer rate is OCH.
•Both cards support the same wavelength.
•The links are bidirectional.
Links between TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, TXP_MR_10G, 2.5G_DM, 2.5G_DMP, TXP_MR_10E, MXP_MR_10E cards or DWDM cards are manually created and cannot be automatically discovered. They can be created if:
•The layer rate is Physical.
•The link is unidirectional.
•The link rate is 10G ITU if a MXP_2.5G_10G, TXP_MR_10G, TXP_MR_10E or MXP_MR_10E card is used at one end of the link, or 2.5 G ITU if a TXP_MR_2.5G, TXPP_MR_2.5G, 2.5G_DM or 2.5G_DMP card is used at one end of the link.
•The link is unprotected.
•The link is created between TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, TXP_MR_10G, 2.5G_DM, 2.5G_DMP, TXP_MR_10E, or MXP_MR_10E trunk ports and DWDM channel ports.
•DWDM channel ports are unidirectional and can only be used as the link source if they are transmit ports and as the link destination if they are receive ports.
•The working wavelength of TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, TXP_MR_10G, 2.5G_DM, 2.5G_DMP, TXP_MR_10E, and MXP_MR_10E cards is equal to the expected wavelength set on the DWDM channel port on the other end of the link.
Table 3-11 Links Supported Between NEs at Compatible Layer Rates
NE Model
|
Supports Links with These NEs at Compatible Layer Rates
|
ONS 15216
|
ONS 15216
|
ONS 15327
|
ONS 15454 SONET/SDH
|
ONS 15600 SONET
|
CRS-1
|
XR 12000
|
ONS 15302
ONS 15305 (R2.x)
|
ONS 15302
|
ONS 15305
|
ONS 15327
|
ONS 15454 SONET/SDH
|
ONS 15600 SONET/SDH
|
ONS 15305 (R3.0)
|
ONS 15302
|
ONS 15305
|
ONS 15327
|
ONS 15454 SONET/SDH
|
ONS 15600 SONET/SDH
|
Unmanaged NEs
|
ONS 15310 CL
|
ONS 15310 CL
|
ONS 15310 MA
|
ONS 15327
|
ONS 15454 SONET/SDH
|
ONS 15600 SONET/SDH
|
ONS 15310 MA
|
ONS 15310 CL
|
ONS 15310 MA
|
ONS 15327
|
ONS 15454 SONET/SDH
|
ONS 15600 SONET/SDH
|
ONS 15327
ONS 15454 SONET
ONS 15454 SDH
|
ONS 15216
|
ONS 15302
|
ONS 15305
|
ONS 15310 CL
|
ONS 15310 MA
|
ONS 15327
|
ONS 15454 SONET/SDH
|
ONS 15600 SONET/SDH
|
ONS 15800
|
ONS 15801
|
ONS 15808
|
CRS-1
|
XR 12000
|
Unmanaged NEs
|
ONS 15501
ONS 15530
ONS 15540(ESP/ESPx)
|
ONS 15501
|
ONS 15530
|
ONS 15540(ESP/ESPx)
|
ONS 15600 SONET
ONS 15600 SDH
|
ONS 15216
|
ONS 15302
|
ONS 15305
|
ONS 15310 CL
|
ONS 15310 MA
|
ONS 15327
|
ONS 15454 SONET/SDH
|
ONS 15600 SONET/SDH
|
ONS 15800
|
ONS 15801
|
ONS 15808
|
ONS 15800
ONS 15801
ONS 15808
|
ONS 15454 SONET/SDH
|
ONS 15600 SONET/SDH
|
ONS 15800
|
ONS 15801
|
ONS 15808
|
CRS-1
|
ONS 15310
|
ONS 15327
|
ONS 15454 SONET/SDH
|
ONS 15600 SONET/SDH
|
MDS 9000
|
XR 12000
|
Unmanaged NEs
|
XR 12000
|
ONS 15310
|
ONS 15327
|
ONS 15454 SONET/SDH
|
ONS 15600 SONET/SDH
|
MDS 9000
|
CRS-1
|
Unmanaged NEs
|
MDS 9000
|
Unmanaged NEs
|
CTC-based NEs
|
Cisco 7600
|
Cisco 7600
|
Unmanaged NEs
|
CRS-1
|
XR 12000
|
ONS 15454 SONET/SDH
|
MGX
|
None.
|
Unmanaged NEs
|
CRS-1
|
ONS 15305 (R3.0)
|
ONS 15327
|
ONS 15454 SONET/SDH
|
MDS 9000
|
XR 12000
|
Unmanaged NEs
|
Table 3-12 Supported NE Links
NE Model
|
NE Card
|
Physical
|
OTS
|
OMS
|
OCH
|
SONET/SDH
|
Layer 2
|
ONS 15216
|
100-GHz Filter
|
X
|
|
X
|
|
|
|
100-GHz OADM 1/2/4
|
X
|
|
X
|
|
|
|
200-GHz Filter
|
X
|
|
X
|
|
|
|
200-GHz OADM 1/2
|
X
|
|
X
|
|
|
|
DCU
|
X
|
|
|
|
|
|
EDFA 1
|
X
|
X
|
|
|
|
|
EDFA2
|
X
|
X
|
|
|
|
|
EDFA3
|
X
|
X
|
|
|
|
|
FlexLayer
|
X
|
|
X
|
|
|
|
OSC
|
X
|
|
X
|
|
|
|
ONS 15302
|
STM-1
|
X
|
|
|
|
X
|
|
ONS 15305
|
STM-1
|
X
|
|
|
|
X
|
|
STM-4
|
X
|
|
|
|
X
|
|
STM-16
|
X
|
|
|
|
X
|
|
ONS 15310 CL
|
CTX-CL600 (OC-3 port)
|
X
|
|
|
|
X
|
|
CTX-CL600 (OC-12 port)
|
X
|
|
|
|
X
|
|
PoS
|
|
|
|
|
|
X
|
ONS 15310 MA
|
CTX-2500 (OC-3 port)
|
X
|
|
|
|
X
|
|
CTX-2500 (OC-12 port)
|
X
|
|
|
|
X
|
|
CTX-2500 (OC-48 port)
|
X
|
|
|
|
X
|
|
PoS
|
|
|
|
|
|
X
|
ONS 15327
|
E10/100-4
|
|
|
|
|
|
X
|
G1000-2
|
|
|
|
|
|
X
|
OC-3/STM-1
|
X
|
|
|
|
X
|
|
OC-12/STM-4
|
X
|
|
|
|
X
|
|
OC-48/STM-16
|
X
|
|
|
|
X
|
|
ONS 15454 SONET and ONS 15454 SDH
|
32MUX-O
|
X
|
|
|
|
|
|
32DMX-O
|
X
|
|
|
|
|
|
4MD-xx.x
|
X
|
|
|
|
|
|
AD-1C-xx.x
|
X
|
|
|
|
|
|
AD-2C-xx.x
|
X
|
|
|
|
|
|
AD-4C-xx.x
|
X
|
|
|
|
|
|
E100T-12
|
|
|
|
|
|
X
|
E100T-12-G
|
|
|
|
|
|
X
|
E1000-2
|
|
|
|
|
|
X
|
E1000-2-G
|
|
|
|
|
|
X
|
ML100-12
|
|
|
|
|
|
X
|
ML1000-2
|
|
|
|
|
|
X
|
MXP_2.5G_10G
|
X
|
|
|
X
|
|
|
OC-3/STM-1
|
X
|
|
|
|
X
|
|
OC-12/STM-4
|
X
|
|
|
|
X
|
|
OC-48/STM-16
|
X
|
|
|
|
X
|
|
OC-48/STM-16 ITU
|
X
|
|
|
X
|
|
|
OC-192/STM-64
|
X
|
|
|
|
X
|
|
OC-192/STM-64 ITU
|
X
|
|
|
X
|
|
|
OPT-BST
|
X
|
X
|
|
|
|
|
OSC-CSM
|
X
|
X
|
|
|
|
|
TXP_MR_2.5G and TXPP_MR_2.5G
|
X
|
|
|
X
|
|
|
TXP_MR_10G
|
X
|
|
|
X
|
|
|
ONS 15501
|
Amp
|
X
|
X
|
|
|
|
|
ONS 15530
|
10 Gbps Uplink
|
X
|
|
|
|
|
|
OADM
|
X
|
|
X
|
|
|
|
Nonsplitter 2.5 Gbps ITU Trunk
|
X
|
|
|
X
|
|
|
Nonsplitter 10 Gbps ITU Trunk
|
X
|
|
|
X
|
|
|
Splitter 10 Gbps ITU Trunk
|
X
|
|
|
X
|
|
|
ONS 15540
|
10 GE Transponder xx.x
|
X
|
|
|
X
|
|
|
32-channel Mux/Demux
|
X
|
|
X
|
|
|
|
OADM xx.x
|
X
|
|
X
|
|
|
|
Type 1 single-mode Transponder xx.x
|
X
|
|
|
X
|
|
|
Type 1 multi-mode Transponder xx.x
|
X
|
|
|
X
|
|
|
Type 2 extended range Transponder xx.x
|
X
|
|
|
X
|
|
|
ONS 15600 SONET
|
ASAP (OC-3 port)
|
X
|
|
|
|
X
|
|
ASAP (OC-12 port)
|
X
|
|
|
|
X
|
|
ASAP (OC-48 port)
|
X
|
|
|
|
X
|
|
OC-48
|
X
|
|
|
|
X
|
|
OC-192
|
X
|
|
|
|
X
|
|
ONS 15600 SDH
|
STM-16
|
X
|
|
|
|
X
|
|
STM-64
|
X
|
|
|
|
X
|
|
ONS 15800
|
Amp
|
X
|
X
|
|
|
|
|
Mux/Demux
|
X
|
|
X
|
|
|
|
PRE-L
|
X
|
X
|
|
|
|
|
RBA
|
X
|
X
|
|
|
|
|
RBA-10G
|
X
|
X
|
|
|
|
|
TPA-R
|
X
|
X
|
|
|
|
|
TT/RT
|
X
|
|
|
X
|
|
|
ONS 15801
|
Amp
|
X
|
X
|
|
|
|
|
Mux/Demux
|
X
|
|
X
|
|
|
|
PRE-L
|
X
|
X
|
|
|
|
|
RBA
|
X
|
X
|
|
|
|
|
RBA-10G
|
X
|
X
|
|
|
|
|
TPA-R
|
X
|
X
|
|
|
|
|
TT/RT
|
X
|
|
|
X
|
|
|
ONS 15808
|
Amp
|
X
|
X
|
|
|
|
|
BCS-LH
|
X
|
X
|
|
|
|
|
BCS-ELH
|
X
|
X
|
|
|
|
|
Mux/Demux
|
X
|
|
X
|
|
|
|
TT/RT
|
X
|
|
|
X
|
|
|
CRS-1
|
16-OC48
|
X
|
|
|
|
|
|
4-OC192
|
X
|
|
|
|
|
|
1-OC768
|
X
|
|
|
|
|
|
8x10GE
|
X
|
|
|
|
|
|
XR 12000
|
16-OC48
|
X
|
|
|
|
|
|
4-OC192
|
X
|
|
|
|
|
|
1-OC768
|
X
|
|
|
|
|
|
8x10GE
|
X
|
|
|
|
|
|
Cisco 7600
|
WS-X6704-10GE
|
X
|
|
|
|
|
|
WS-X6724-SFP
|
X
|
|
|
|
|
|
WS-X6748-GE-TX
|
X
|
|
|
|
|
|
WS-X6816-GBIC
|
X
|
|
|
|
|
|
MDS 9000
|
Supports links with CTC-based NEs and unmanaged NEs
|
X
|
|
|
|
|
|
3.6.4 Viewing the Link Table
The Link table shows information about each link attribute. Use the Link table to view, modify, and delete links. You can open the Link table for the CTM domain, network partition, subnetwork, group, or NE.
•If you select the CTM domain, network partition, subnetwork, or group, the Link table shows all links that terminate on any of the NEs contained in the CTM domain, subnetwork, or group.
•If you select an NE, the Link table shows all links that terminate on that particular NE.
Open the Link Table using one of the following methods:
•From the Network Map—In the Domain Explorer or Subnetwork Explorer, choose File > Network Map. In the Network Map, select a network partition, subnetwork, group, or NE; then, choose Configuration > Link Table.
•From the Network Map—Right-click a link or server trail and choose Link Table from the shortcut menu.
•From the Domain Explorer—Select the CTM domain, group, or NE; then choose Configuration > Link Table.
•From the Subnetwork Explorer—Select the CTM domain, network partition, subnetwork, or NE; then, choose Configuration > Link Table.
Note A link is visible in the Link table even if the source or destination NE has been deleted, but this same link is not visible in the Network Map. If the NE is deleted from the Deleted Network Elements group, the references to that NE are removed from the Link table.
Note When launching the Link table in a large or high-end network setup and on a larger scope (for example, for the Domain Explorer), a database timeout can occur due to the large volume of data that needs to be retrieved. As a workaround, launch the Link table on a smaller scope.
The following table describes the fields in Link table.
Table 3-13 Field Descriptions for the Link Table
Field
|
Description
|
Link Alarm Severity
|
Highest severity alarm associated with the selected link.
|
Link Source ID
|
ID of the link source.
|
Link Source Termination Point
|
PTP of the link source.
|
Link Destination ID
|
ID of the link destination.
|
Link Destination Termination Point
|
PTP of the link destination. Because a link can have up to two destinations on the same NE, a "DST1" or "DST2" label is affixed to the destination to indicate the destination number.
|
Layer Rate
|
Layer rate, defined as per ITU-T standard G.872 for multilayered optical networks. Values are Physical, Optical Transmission Section (OTS), Optical Multiplex Section (OMS), Optical Channel Layer (OCH), SONET/SDH, and L2.
|
Layer Detail
|
Bandwidth of the link as per the layer rate:
•For SONET links, the link rate is OC-3, OC-12, OC-48, OC-192, Layer 2, or Layer 3, depending on the NE configuration.
•For SDH links, the link rate is STM1, STM-4, STM-16, STM-64, Layer 2, or Layer 3.
•For DWDM links, the link rate is 40G ITU, 10G ITU, 2.5G ITU, or OTS.
•For OCH links, the link rate is 10G ITU or 2.5G ITU.
•For the ONS 15800, ONS 15801, and ONS 15808 NEs, the link rate is OTS.
•For links between Not Managed/Other Vendor NEs, the link rate is Not Applicable.
•For links between Not Managed/Other Vendor NEs and a CTC-based NE, the rate is that of the CTC-based NE. Links between a SONET/SDH link and a Not Managed/Other Vendor NE depend on the link source. If the link source is the Not Managed/Other Vendor NE, the layer rate is Not Applicable. If the link source is the SONET/SDH link, the layer rate is that of the SONET/SDH link.
For server trails, this field displays the server trail type and the number of server trails.
|
Link Direction
|
Whether the link is unidirectional or bidirectional.
|
Link Provision Type
|
Whether the selected link is automatically discovered by an NE. Values are:
•Manual—For manual links.
•Auto—For automatically discovered links.
•PatchCord—For patchcord links.
For server trails, the value displayed is Server Trail.
Note Autodiscovered links between transponder or muxponder cards on release 4.6 NEs are always reported with a constant size, regardless of payload type.
|
Is Link Valid
|
Validity of the link. Values are Valid or Invalid. For autodiscovered links, the value is Valid if both the terminating NEs are in service and the NEs are able to confirm the presence of the link. An autodiscovered link is invalid if (1) the DCC is disabled on either PTP; (2) either PTP is marked as Out of Service (OOS); (3) there is a fiber cut or transmitter/receiver failure; or (4) either NE is marked as OOS.
The following rules apply to link validity:
•All invalid links are shown as gray in the Network Map.
•Valid links are shown in the Network Map with a color corresponding to alarm severity, with green for no alarm, yellow for minor alarms, orange for major alarms, and red for critical alarms.
•Manual and unmanaged links can be valid or invalid.
•A link between an unmanaged NE and a managed NE can be valid or invalid. If the link is valid, it is shown with the same color as the PTP alarm on the managed NE.
•The delete link operation is available for all links except for valid, autodiscovered links. You can delete links of the following type:
–Manual (valid and invalid)
–Virtual (valid and invalid)
–Unmanaged (valid and invalid)
–Invalid autodiscovered
A 10G-ITU or 40G-ITU DWDM link between two CRS-1 NEs or between a CRS-1 NE and an ONS 15454 SONET or ONS 15454 SDH NE is valid if both the source and destination PTPs are configured with the same wavelength, and the CRS-1 ports are in the UP state.
Note For CRS-1 manual links, when the source or destination NE is in Initializing or Sync Configuration state, the validity of the link(s) might not reflect the correct value. The Is Link Valid field displays the correct value only when both the source and destination NEs are in the In Service state.
|
Link Connection Type
|
Whether the link connection is inter-NE or intra-NE.
An inter-NE link represents an external fiber connection between PTPs on different NEs. An intra-NE link represents a fiber connection between two PTPs on the same NE.
|
Link Protection Type
|
Whether the link protection is unprotected, 1+1, 1+1 with Y-cable protection, 2-fiber BLSR/MS-SPRing, 4-fiber BLSR/MS-SPRing, or not applicable.
For ONS 155xx NEs, protection types are Y-cable/line card protection, trunk protection, splitter protection, or no protection. The Y-cable protection type also applies to ONS 15454 SONET and ONS 15454 SDH NEs.
|
Used for Routing
|
Whether the selected link is used for routing. Values are Yes or No.
|
Link Name
|
Name of the selected link.
|
Link Description
|
User-entered description of the selected link. If you do not modify the <System Default> string in the Create Link wizard, the description is a string built from the endpoint information.
|
Alarm Counts
|
Total number of critical, major, minor, and warning alarms associated with the selected link.
Note This field does not apply to ONS 155xx NEs.
|
Link Cost
|
Numeric cost associated with the selected link. The link cost is used while routing a circuit. The lowest link cost is preferred in circuit routing. The Cisco default value is 1024. This attribute is editable for manual links in the SONET or SDH layer.
|
Shared Risk Link Groups
|
(SONET/SDH layer rates only) Free-format string that represents the shared risk link group (SRLG), or a group of links that share a common risk. For example, a set of links that originate at a node share the node as the common risk.
SRLGs allow you to classify links into logical groups. By grouping the links, you can specify diverse link routing for a circuit. That is, if the circuit is fully protected, it is routed on the working and protect paths with a diverse SRLG attribute.
The Shared Risk Link Groups field supports up to 5 comma-separated values, with 32 characters per value.
|
Link Utilization
|
Link utilization information for Layer 3 links. For non-Layer 3 links, this field shows Not Applicable.
|
Link Alias Name
|
Alias name of the link.
|
3.6.5 Filtering the Link Table
Step 1 In the Link table, choose File > Filter. The Filter dialog box opens.
Step 2 Specify the filter parameters described in the following table.
Step 3 Click OK to run the filter.
Table 3-14 Field Descriptions for the Link Table Filter Dialog Box
Field
|
Description
|
Source/Destination ID
|
Filters by source/destination IDs of the available NEs. Click Add and Remove to move NEs to and from the Selected NEs list.
|
Connection Type
|
Filters out inter-NE or intra-NE links. By default, all links are shown. Only the ONS 15530 and ONS 15540 have intra-NE connections. You can also filter on server trails.
|
Link Layer
|
Filters by layer combination. You can select any subset of the following layers: Physical, OTS, OMS, OCH, SONET/SDH, Layer 2, Layer 3, and OTU.
|
3.6.6 Filtering Links in the Network Map
You can filter the Network Map to show only a selected link layer rate and the nodes that are supported by that layer rate.
Step 1 In the Domain Explorer or Subnetwork Explorer, choose File > Network Map (or click the Open Network Map tool).
Step 2 In the Network Map toolbar, select the layer rate from the drop-down list. You can choose to view links supported by:
•All Layer Rates
•Physical
•OTS
•OMS
•OCH
•SONET/SDH
•Layer 2
•Layer 3
•OTU
Note When you customize the location of the NE icons in the Network Map, make sure to take account of the NEs that you cannot see due to the layer rate that you selected. If you customize the map on one layer rate and then change the layer rate, NE icons and links might overlap because of the layer rate discrepancies.
3.6.7 Creating Links
Step 1 Open the Create Link wizard by using one of the following methods:
•From the Network Map—Select the source NE and choose Configuration > Create Link (or right-click the NE and choose Create Link). Connect the line to the destination NE or click the map. The Create Link wizard opens. The Link Destination panel displays a list of NEs that support compatible layer rates with the source NE.
•From the Domain Explorer or Subnetwork Explorer—Select the source NE and choose Configuration > Create Link (or right-click the NE and choose Create Link). The pointer changes to a plus sign; select the destination NE or group. The Create Link wizard opens.
Note If you press the Esc key while the plus sign is enabled, the operation is canceled and the plus sign returns to a pointer.
Note Table 3-15 describes the fields in the Create Link wizard. Fields shown depend on the NE selected.
Step 2 Create the link, as follows:
a. Enter the following information in the Link Attributes panel:
•Name
•Link alias
•Description
•Provision type
•Layer
•Layer detail
Note Links from a Not Managed/Other Vendor NE to a CTC-based or Not Managed/Other Vendor NE will have a link rate of Not Applicable. Links from a CTC-based NE to a Not Managed/Other Vendor NE will have the link rate allowed for the CTC-based NE.
Note The layer details displayed in the Create Link wizard are based on the NE selected as the link source. For example, when you attempt to create a link from NE A to NE B, the link sizes displayed are based on the supported sizes and inventory of NE A. If the link is attempted in the reverse direction, from NE B to NE A, the link sizes displayed are based on the inventory and sizes for NE B. As a result, the link sizes displayed could differ when the operation is attempted differently. An error message is displayed in the Link Destination panel when the size displayed is not applicable for the destination NE.
•Wavelength (available only if the layer is Optical Channel, the provisioning type is Patchcord, and the direction is Unidirectional)
•Protection
•Direction
Note CTM allows creation of bidirectional SONET/SDH links as well as unidirectional and bidirectional physical links.
If the layer rate is SONET/SDH or Layer 2, only bidirectional links are available. For other layer rates, both unidirectional and bidirectional links are available.
•Cost
•Shared risk link groups
b. Click Next.
c. Enter the following information in the Link Source panel:
•Node
•PTP slot
•PTP port
•PTP value
•Name
d. Click Next.
e. Enter the following information in the Link Destination panel:
•Node
•PTP slot
•PTP port
•PTP value
•Name
Note A PTP can be associated with only one bidirectional link or two unidirectional links at a particular layer rate for all NEs except Not Managed/Other Vendor NEs. For Not Managed/Other Vendor NEs, a PTP can terminate in only one link.
Note If you are creating a SONET/SDH-layer manual link between two CTC-based NEs, verify that no DCC exists on the endpoints that are selected for the link termination.
f. Click Next.
Step 3 The Link Summary panel summarizes the attributes of the new link. To change the link summary information, click Back and change the selections as needed.
Step 4 Click Finish.
Table 3-15 Field Descriptions for the Create Link Wizard
Field
|
Description
|
Link Attributes Panel
|
Name
|
Enter a unique name for the new link. The link name is a free-format string, up to 256 characters.
|
Link Alias
|
Enter a unique alias name for the new link. The alias name can contain alphanumeric characters. It also supports international character sets.
|
Description
|
Enter a description of the new link. The link description is a free-format string, up to 256 characters.
|
Provision Type
|
Specify the type of link provisioning. Values are:
•Manual—The link is manually provisioned.
•Patchcord—(Applicable only to links involving transponders and DWDM modules) The link is an internode or intranode termination provisioned between homogeneous ports. A patchcord link represents the connection between a line card and a transponder, or the connection between a transponder and a DWDM card. Patchcord links can be provisioned by CTM or CTC users and are maintained by the NEs.
Note Protection groups are not recognized when creating patchcord or manual links.
|
Layer
|
Choose the link layer rate, defined as per ITU-T standard G.872 for multilayered optical networks. Values are Physical, OTS, OMS, OCH, SONET/SDH, and L2.
|
Layer Detail
|
Choose the bandwidth of the link as per the layer rate.
•For SONET links, the link rate is OC-3, OC-12, OC-48, OC-192, Layer 2, or Layer 3, depending on the NE configuration.
•For SDH links, the link rate is STM1, STM-4, STM-16, STM-64, Layer 2, or Layer 3.
•For DWDM links, the link rate is 40G ITU, 10G ITU, 2.5G ITU, or OTS.
•For OCH links, the link rate is 10G ITU or 2.5G ITU.
•For ONS 15800, ONS 15801, and ONS 15808 NEs, the link rate is OTS.
•For links between Not Managed/Other Vendor NEs, the link rate is Not Applicable.
•For links between Not Managed/Other Vendor NEs and CTC-based NEs, the rate is that of the CTC-based NE. Links between a SONET/SDH link and a Not Managed/Other Vendor NE depend on the link source. If the link source is the Not Managed/Other Vendor NE, the layer rate is Not Applicable. If the link source is the SONET/SDH link, the layer rate is that of the SONET/SDH link.
•For links between MDS 9000 NEs and CTC-based NEs, the rate is that of the CTC-based NE. Links between a SONET/SDH link and an MDS 9000 NE depend on the link source. If the link source is the MDS 9000 NE, the layer rate is Not Applicable. If the link source is the SONET/SDH link, the layer rate is that of the SONET/SDH link.
|
Wavelength
|
Filter the wavelength in the first drop-down list. In the second drop-down list, select the appropriate wavelength value according to the selected filter.
The Wavelength drop-down lists are available only if the layer is Optical Channel, the provisioning type is Patchcord, and the direction is Unidirectional.
Note When the layer is Optical Channel, the provisioning type is Patchcord, and the direction is Bidirectional, the Wavelength drop-down lists are disabled, but CTM executes an automatic wavelength check on the endpoints before creating the link. If the link endpoints do not have the same wavelength value, the link is not created and a wavelength error is generated.
|
Protection
|
Specify the link protection: Unprotected, 1+1, Y-Cable (meaning 1+1 with Y-cable protection), 2-Fiber BLSR/MS-SPRing, 4-Fiber BLSR/MS-SPRing, or Not Applicable. For CTC-based NEs, select Unprotected, 1+1, or Y-Cable. For ONS 1580x NEs, the only selectable value is Unprotected. For links between Not Managed/Other Vendor NEs, the link protection is Not Applicable. For links between Not Managed/Other Vendor NEs and CTC-based NEs, the link protection is that of the CTC-based NE. For links between MDS 9000 NEs and CTC-based NEs, the link protection is that of the CTC-based NE.
|
Direction
|
Specify whether the link is unidirectional or bidirectional. For the ONS 15501, ONS 15800, ONS 15801, and ONS 15808, only unidirectional links are available.
|
Cost
|
Specify a numeric cost associated with the SONET or SDH layer link. The cost range is 0 to 999999. This field applies only to links in the SONET or SDH layer between CTC-based NEs. For all other links, the Cisco default value is 1024. All autodiscovered links have the Cisco default cost 1024.
|
Shared Risk Link Groups
|
(SONET/SDH layer rates only) Enter a free-format string that represents the SRLG, or a group of links that share a common risk. For example, links that originate at a node share the node as the common risk.
The Shared Risk Link Groups field supports up to 5 comma-separated values, with 32 characters per value.
|
Link Source Panel
|
Node
|
Identify which NE serves as the source of the link.
|
Physical Termination Point
|
Identify the physical side, shelf, slot, subslot (if applicable), and port in the source NE. For the ONS 15216, identify the name of the PTP. For the ONS 15800, ONS 15801, and ONS 15808, identify the rack, subrack, slot, and direction (east-to-west or west-to-east).
Note The card type is shown adjacent to the slot number; for example, "1 (OC3_8)" represents the OC3_8 card in slot 1.
Note If the port name is available, it is shown adjacent to the port number.
|
PTP Value
|
(Not Managed/Other Vendor and MDS 9000 NEs only) Specify the PTP value. The maximum length is 30 characters; the minimum length is 1 character.
|
Name
|
For the ONS 15501, ONS 15530, and ONS 15540, identify the PTP as a single name, which includes a port type and slot number and might also include a subslot number and port number.
|
Link Destination Panel
|
Node
|
This is a display-only field if you selected an NE as the destination of the link. If you selected a group as the destination of the link, select from the drop-down list a specific NE that will be the destination of the link.
|
Physical Termination Point
|
Identify the physical side, shelf, slot, subslot (if applicable), and port in the destination NE. For the ONS 15216, identify the name of the PTP. For the ONS 15800, ONS 15801, and ONS 15808, identify the rack, subrack, slot, and direction (east-to-west or west-to-east).
Note The card type is shown adjacent to the slot number; for example, "1 (OC3_8)" represents the OC3_8 card in slot 1.
Note If the port name is available, it is shown adjacent to the port number.
|
PTP Value
|
(For Not Managed/Other Vendor and MDS 9000 only) Specify the PTP value. The maximum length is 30 characters; the minimum length is 1 character.
|
Name
|
For the ONS 15501, ONS 15530, and ONS 15540, identify the PTP as a single name, which includes a port type and slot number and might also include a subslot number and port number.
|
Link Summary Panel
|
Link Summary
|
Summarizes the selections you made. To change the Link Summary, click Back and change your selection(s).
|
Note•After the links are created, each link has a different color notation depending on the alarm status of the PTP on which the link is created. Links between Not Managed/Other Vendor NEs are always black. The color of the link between an MDS 9000 or a Not Managed/Other Vendor NE and a CTC-based NE is the color of the TP of the CTC-based NE. The colors are green for no alarm, yellow for minor alarms, orange for major alarms, and red for critical alarms. Invalid links (as reflected in the Is Link Valid field) are gray. An autodiscovered link can become invalid if (1) the DCC is disabled on either PTP; (2) either PTP is marked as Out of Service (OOS); (3) there is a fiber cut or transmitter/receiver failure; or (4) either NE is marked as OOS. Manual links are colored to match the highest alarm severity on either PTP. L2 links are always gray.
•Links that are supported in different layer rates can be created only if the link endpoints are compatible with the specified layer rate.
•If CTM discovers a link, it automatically assigns layer rates based on its endpoint.
The following table summarizes link color as it relates to link type and the involved NEs.
Table 3-16 Summary of Link Color
Link Type
|
Link Validity
|
Link Color
|
Can the Link Be Deleted?
|
Manual
|
Valid
|
Color of the highest severity alarm on the PTP.
|
Yes
|
Manual
|
Invalid
|
Gray.
|
Yes
|
Virtual
|
Valid
|
Color of the highest severity alarm on the PTP.
|
Yes
|
Virtual
|
Invalid
|
Gray.
|
Yes
|
Unmanaged
|
Valid
|
Black, if the link is between two unmanaged NEs. Otherwise, the color corresponds to the highest severity alarm on the PTP.
|
Yes
|
Unmanaged
|
Invalid
|
Gray.
|
Yes
|
Autodiscoverd
|
Valid
|
Color of the highest severity alarm on the PTP.
|
No
|
Autodiscovered
|
Invalid
|
Gray.
|
Yes
|
3.6.8 Modifying Links
Use the Modify Link wizard to modify the name, alias, description, cost, or SRLG (if applicable) of links displayed in the Link table. You can modify a link in the Link table or in the Network Map.
Note Table 3-17 describes the fields in the Modify Link wizard.
Step 1 Open the Modify Link wizard by using one of the following methods:
•In the Link table, select a link and choose Edit > Modify Link (or click the Modify Selected Link tool).
•In the Network Map, select a link and choose Configuration > Modify Link (or click the Modify Selected Link tool).
Step 2 In the Link Attributes panel, modify the following information, as needed:
•Name
•Link alias
•Description
•Direction
•Cost
•Shared risk link groups
Note If you modify the SRLG value, you receive the warning popup "There might be circuits routed with diverse SRLG constraints on this link. Changing risk link groups might affect the diversity constraint." Click OK; then, verify the SRLG value that you entered.
Step 3 Click Next until you reach the Finish panel.
Step 4 Verify the link summary and click Finish.
Note After certain topology reconfigurations that involve removing fiber, the Network Map might not report the correct links. This problem occurs because the CTM server is not synchronized with the new network topology and cannot retrieve network or link updates. This problem applies only to CTC-based NEs. The workaround is to remove the links completely by deleting the SDCC termination on the ports, rather than by simply unplugging the fiber cable.
Table 3-17 Field Descriptions for the Modify Link Wizard
Field
|
Description
|
Link Attributes Panel
|
Name
|
Modify the name of the selected link. The link name is a free-format string, up to 256 characters. The link name must be unique.
|
Link Alias
|
Modify the alias name of the selected link. The alias name can contain alphanumeric characters. It also supports international character sets.
|
Description
|
Modify the link description. The link description is a free-format string, up to 256 characters.
|
Provision Type
|
Display only. View the type of link provisioning (Manual or Patchcord).
|
Layer
|
Display only. View the link layer.
|
Layer Detail
|
Display only. View the link size.
|
Wavelength
|
Display only. View the link wavelength value.
|
Protection
|
Display only. View the link protection.
|
Direction
|
Modify whether the link is unidirectional or bidirectional.
|
Cost
|
Modify the numeric cost associated with the SONET or SDH layer link. The cost range is 0 to 999999. This field is editable only for links in the SONET or SDH layer. For all other links, the Cisco default value is 1024. All autodiscovered links have the Cisco default cost 1024.
|
Shared Risk Link Groups
|
(SONET/SDH layer rates only) Modify the strings that represent the SRLG. The SRLG attribute supports up to 5 comma-separated values, with 32 characters per value.
|
Link Summary Panel
|
Link Summary
|
Summarizes the changes you made to the editable fields. To change the Link Summary, click Back and change your selection(s).
|
3.6.9 Deleting Links
You can delete one or multiple links from the Link table. You can delete a single link from the Network Map.
Step 1 In the Link table, select one or multiple links and choose Edit > Delete Link (or click the Delete Selected Link tool). In the Network Map, select a single link and choose Configuration > Delete Link.
Step 2 Click OK in the confirmation dialog box.
Step 3 For multiple link deletion, complete the following substeps:
a. The Deleting Links dialog box tracks the progress of the deletion. If you selected links that cannot be deleted, you receive the message: "Some of the links can't be deleted, proceed anyway?" Review the links that you selected for deletion; then, click OK.
b. The Multiple Link Deletion Summary dialog box opens, summarizing the results of the deletion. Click the Details button to see which links were deleted, and which links could not be deleted.
The following rules apply to single and multiple link deletion:
•User-created links or invalid autodiscovered links can be deleted.
•Valid autodiscovered links cannot be deleted.
•An autodiscovered link is marked Invalid when CTM can no longer verify the link from either of the NEs at the ends of the link.
•To remove a valid autodiscovered link from CTM, you must remove the topology neighbors from both NEs at the end of the link.
•CTM can delete physical links even if there is an autodiscovered SONET/SDH link.
Note If you use CTM to delete invalid autodiscovered links, verify that the DCCs are deleted on both ends of the link. If you delete a partial link with a DCC up on one end, it might cause problems later with the creation of phantom links.
3.6.10 Viewing Link Utilization
The Link Utilization table displays utilization information for the selected links. Link utilization, shown as a percentage, displays the overall consumption of bandwidth. All bandwidths are in megabits per second (Mbps).
% Link utilization = ([Bandwidth consumed] / [Total bandwidth of link]) x 100
Example: In SONET, for an OC12 link, the total bandwidth is (12 x 51.84) Mbps, where STS-1/OC12 = 51.84 Mbps.
Depending on the number of provisioned circuits, the consumed bandwidth is totaled. Circuits such as VAP/LAP and virtual tributary (VT) tunnel are preprovisioned and are not included in the calculation. This is applicable to SONET and SDH.
Example: In SDH, for an STM4 link, the total bandwidth is (4 x 155) Mbps, where STM-1 = 155 Mbps.
Note Link utilization does not apply to server trails. An error message is displayed if you attempt to launch the Link Utilization table from a server trail.
To view the Link Utilization table:
Step 1 In the Domain Explorer window, choose Configuration > Link Table. The Link table opens.
Step 2 In the Link table, choose Configuration > Link Utilization Table (or click the Open Link Utilization Table tool). The following table provides descriptions.
Note You can launch the Circuit Trace window from a selected circuit in the Link Utilization table. Select a circuit in the Link Utilization table and then choose View > Circuit Trace. See 7.2.22 Tracing a Circuit on CRS-1 or CTC-Based NEs, page 7-135.
Table 3-18 Field Descriptions for the Link Utilization Table
Column
|
Description
|
STS ID (SONET only)
|
Displays the STS ID.
|
VT1.5 ID (SONET only)
|
Displays the VT 1.5 ID.
|
VT2 ID (SONET only)
|
Displays the VT2 ID.
|
VC4 ID (SDH only)
|
Displays the VC4 ID.
|
VC3/TUG3 ID (SDH only)
|
Displays theVC3/TUG3 ID.
|
TUG2 ID (SDH only)
|
Displays the TUG2 ID.
|
VC12 ID (SDH only)
|
Displays theVC12 ID.
|
VC11 ID (SDH only)
|
Displays theVC11 ID.
|
Circuit Name
|
Displays the name of any circuits passing through the link. When Unused appears in the Circuit Name field there is unused bandwidth available, and the Circuit Type, Circuit Protection Type, Customer ID, and Service ID fields are blank.
|
Circuit Alias
|
Displays a unique alias name for the new circuit. The alias name can contain alphanumeric characters. It also supports international character sets.
|
Circuit Type
|
Displays the circuit type.
|
Circuit Protection Type
|
Displays the circuit protection type.
|
Switch State
|
Displays the switch state for UPSR protected circuits only. Values are:
•CLEAR—Removes a previously set switch command.
•MANUAL—A manual switch is active on the span.
•FORCE—A force switch is active on the span.
•LOCKOUT_OF_PROTECTION—A protection lockout is active on the span; traffic cannot be switched to the span.
Note A force switch always overrides a manual switch. A protection lockout always overrides both a force switch and a manual switch.
To configure the span switch state see Configuring the Span Switch State on a UPSR Protected Circuit.
Note N/A is displayed for non-UPSR-protected circuits.
|
Customer ID
|
Displays the user-defined customer ID.
|
Service ID
|
Displays the user-defined service ID number.
|
3.6.10.1 Configuring the Span Switch State on a UPSR Protected Circuit
Note The span switch is applicable to all UPSR circuits in the Link Utilization table. The selection context has no impact on the switching. When you perform protection switching after selecting an unprotected circuit, the protection switch applies to only UPSR-protected circuits.
Step 1 In the Domain Explorer window, choose Configuration > Link Table. The Link table opens.
Step 2 In the Link table, choose Configuration > Link Utilization Table (or click the Open Link Utilization Table tool).
Step 3 In the Link Utilization table, choose Configuration > Span Switch > CLEAR, MANUAL, FORCE, or LOCKOUT_OF_PROTECTION.
Note Switch states that cannot be applied are dimmed.
The possible switch state that can be applied to the circuits in the Link Utilization table is decided by switch priority. The switch priority in ascending order is:
1. MANUAL
2. FORCE
3. LOCKOUT_OF_PROTECTION
4. CLEAR
Note The CLEAR switch state overrides all other switch states.
Example 3-1 Unprotected OC-48 Link
4 - VT Mapped (VTs 1-4 in use)
STS Utilization = 4/48 = 8.3%
VT Utilization = (3x28 + 4)/(28 x 48) = 6.5%
STS PCA Utilization = N/A
VT1.5 PCA Utilization = N/A
Example 3-2 2-Fiber BLSR OC-48 Link
4 - VT Mapped (VTs 1-4 in use)
25 - STS PCA Circuit In Use
26 - 8 VT1.5 PCA circuits In Use
STS Utilization = 4/24 = 16.7%
VT-1.5 Utilization = (3x28 + 4)/(28 x 24) = 13.1%
STS PCA Utilization = 2/24 = 8.2%
VT-1.5 PCA Utilization = (1x28 + 8)/(28 x 24) = 5.4%
3.6.11 Filtering the Link Utilization Table
Step 1 In the Link Utilization table, choose File > Filter (or click the Filter Data tool). The Filter dialog box opens.
Step 2 Specify the filter parameters described in the following table.
Step 3 Click OK to run the filter.
Table 3-19 Field Descriptions for the Link Utilization Table Filter Dialog Box
Payload Type
|
Description
|
SONET
|
You can filter on the STS ID to see circuits going through that STS only. Select All to see all the tributaries on that link.
|
SDH
|
You can filter on specific VC4, VC3/TUG3, and TUG2 IDs. The ALL option shows all tributaries. The None option is available on VC3/TUG3 and TUG2. Using None, you can select VC4 circuits (including VC LO Path Tunnel and LAP).
|
3.7 How Do I Build Server Trails?
A server trail is a subnetwork connection within a network that interconnects ONS 155xx edge connection termination points (CTPs). Some limitations of server trails are:
•A server trail connection should not cross the port boundary. For an NxVC4 server trail connection, all N-VC4 terminations must be on the same port.
•Users with permissions to manage links can also manage server trails. Link preferences and not circuit preferences are applied for server trail operations, even though the server trails terminate on CTPs. A user might therefore be allowed to create an STS-1 server trail but not able to create STS-1 circuits (if that circuit size is not allowed for the user).
•Server trail connections cannot be provisioned on DCC-enabled ports. If DCC is enabled on a port, you cannot use the port as the source or destination for the server trail.
•You cannot change the size of an existing server trail.
•Multiple server trails can start from the same PTP. On a given PTP, the server trail can be of different connection types.
•Only one server trail can start from a CTP. CTPs of multiple server trail connections should be of the same type.
•Server trail connections cannot overlap each other.
•The sum of server trail sizes for an existing port cannot exceed the size of the port.
Following are the differences between manual links and server trails:
•Manual links occupy an entire port while server trails occupy parts of a port. This means that a single port can terminate only one link but several server trails.
•Manual links can terminate on optical cards. Server trails can terminate on optical and electrical cards.
•Manual links can be created on DCC-enabled ports, while you cannot create server trails using DCC-enabled ports.
•The endpoints of manual links should be the same size. The endpoints of server trails can be different sizes and types.
3.7.1 Creating Server Trails
Step 1 Select the source NE in the Domain Explorer or Subnetwork Explorer and choose Configuration > Create Server Trail (or right-click the NE and choose Create Server Trail). The pointer changes to a plus (+) symbol; select the destination NE. The Create Server Trail wizard opens.
Step 2 In the Server Trail Attributes pane, specify the following:
•Type—Select the type of server trail to create.
•Size—Select the size of the server trail. The options displayed depend on the type selected.
•Protection—Select the server trail protection type.
•Number of Trails—Enter the number of trails.
•Shared Risk Link Groups—Enter a free-format string that represents the shared risk link group or a group of links that share a common risk.
•Cost—Specify the numeric cost associated with the server trail.
Step 3 Click Next.
Step 4 In the Source pane, set the server trail source. The options displayed depend on the server trail type selected in the Server Trail Attributes pane.
Step 5 Click Next.
Step 6 In the Destination pane, set the server trail destination. The options displayed depend on the server trail type selected in the Server Trail Attributes pane.
Step 7 Click Finish. The server trail is listed in the Link table. You can also view the server trail in the Network Map.
3.7.2 Modifying Server Trails
Step 1 Open the Modify Link wizard using one of the following methods:
•In the Link table, select a server trail and choose Edit > Modify Link (or click the Modify Selected Link tool).
•In the Network Map, select a server trail and choose Configuration > Modify Link (or click the Modify Selected Link tool).
Step 2 In the Link Attributes panel, modify the following information, as needed:
•Name
•Alias
•Description
•Cost
•Shared risk link groups
Note If you modify the SRLG value, you receive the warning popup "There might be circuits routed with diverse SRLG constraints on this link. Changing risk link groups might affect the diversity constraint." Click OK; then, verify the SRLG value that you entered.
Step 3 Click Next.
Step 4 Verify the link summary and click Finish.
3.7.3 Deleting Server Trails
Step 1 In the Link table, select a server trail and choose Edit > Delete Link (or click the Delete Selected Link tool). In the Network Map, select a server trail and choose Configuration > Delete Link.
Step 2 Click OK in the confirmation dialog box.
3.8 How Do I Use Network Maps?
The Network Map is organized into a multilevel hierarchy that corresponds to the structure of the Domain Explorer and Subnetwork Explorer trees. The Network Map hierarchy consists of management domains, subnetworks, groups, and NEs, which are displayed graphically.
Network map backgrounds are provided by default as part of CTM, and are used to display a geographical layout of the network.
The Network Map consists of three areas:
•The right side displays a map with the individual groups, NEs, and link icons.
•The upper left side displays the position of the map on the right side with respect to a larger world map.
•The lower left side displays the domain, or group properties, including the number of alarms and the ID.
3.8.1 Customizing a Network Map
Use the Edit menu and toolbar buttons to customize your network map. Use the Enable Drag tool to enable drag-and-drop functionality and easily display network partitioning. Other Edit menu options allow you to enable the display of off-view icons, change geographic backgrounds for the selected view, select a layout format for the icons, adjust the zoom level, or choose icons to represent specific nodes.
Step 1 In the Domain Explorer or Subnetwork Explorer tree, click a node and choose File > Network Map (or click the Open Network Map tool).
Note There is no Network Map for the Discovered Network Elements or Deleted Network Elements groups.
Step 2 Use the Edit menu in the Network Map window to customize the Network Map. Edit menu options include:
•Enable Drag—Enables the drag-and-drop functionality.
•Enable Offview—Enables the display of off-view icons in the selected Network Map window. If an NE has a link to an NE on a different map, the off-view NE is represented by an off-view icon.
Note The off-view icon serves as a hyperlink to the map that contains the NE at the opposite end of the link.
•Change Map Background—Allows you to choose a different geographic background image for the selected view. Choose one of the image files packaged with CTM, or use another image file.
•Change Node Icon—Allows you to choose a new icon for the selected node.
•Zoom In—Changes the magnification of the nodes by zooming in.
•Zoom Out—Zooms out to make all nodes visible.
•Zoom Area—Selects the area that you want to view. When selected, the pointer changes to a cross mark in the Network Map and allows you to select the area that you want to view.
•Find—Allows you to search for an NE or group by providing the full or partial identifier of the NE or group.
•Find Next—Searches for the next instance of the specified search object.
•Expand All Links—Shows links contained in an aggregate link.
•Collapse All Links—Hides links contained in an aggregate link.
•Circular Layout—Arranges and displays the nodes in a circle.
•Spring Layout—Arranges and displays the nodes according to the links that connect the NEs.
•Table Layout—Arranges and displays the nodes in such a way that the nodes are arranged in a grid, or table. The nodes are arranged as close together as possible.
•Declutter Layout—Arranges the existing nodes so that they do not overlap. This layout is used to handle nodes that appear on top of each other when you zoom out.
Step 3 The off-view icons in the Network Map can be enabled or disabled. In the User Preferences dialog box > Map Preferences tab, check the Show Off View Icons check box to show off-view icons in the Network Map, or leave the check box unchecked to hide off-view icons. Click OK.
Step 4 You can specify a fixed and locked pixel size for icons in the Network Map. In the User Preferences dialog box > Map Preferences tab, use the Minimum Icon Size drop-down list to specify the pixel size. Regardless of the zoom level, the map icon size does not change when it is set to a fixed size. Click OK. The icon size setting is saved with the other map settings.
Step 5 You can choose whether to use multiple windows or a single window for navigation. In the User Preferences dialog box > Map Preferences tab, check the Open Network Map in New Window check box to open a new window for subsequent map views, or uncheck the check box to open subsequent map frames in the same window. Click OK.
Note If you right-click a group icon, you can choose Open to open the map based on your selection in the User Preferences dialog box, or Open (New Window) to open the map in a new window. The File menu also contains Open and Open (New Window) options.
Step 6 You can choose whether CTM truncates long map node names by the first characters or by the ending characters.
a. Return to the Domain Explorer window and choose Administration > Control Panel.
b. Click UI Properties.
c. In the Domain Management area, click the Truncate Network Map Node Name First Characters or Truncate Network Map Node Name End Characters radio buttons.
d. Click Save.
3.8.2 Viewing a Node in the Network Map
Icons in the Network Map are displayed based on the nodes you select in the Domain Explorer or Subnetwork Explorer.
Launching the Network Map from the following nodes displays different results:
•From the CTM domain in the Domain Explorer—Displays all the groups in the CTM domain. If you double-click a group in the Network Map, another Network Map window opens and all the NEs that belong to that group are displayed.
•From a specific group in the Domain Explorer—Displays all NEs that belong to that group.
•From a specific NE in the Domain Explorer or Subnetwork Explorer—Displays the selected NE, the links that start from or terminate on that NE, and other NEs that the NE is connected to.
•From the CTM domain in the Subnetwork Explorer—Displays all the network partitions in the CTM domain. If you double-click a network partition in the Network Map, another Network Map window opens, showing all the subnetworks that belong to that network partition.
•From a specific network partition in the Subnetwork Explorer—Displays all the subnetworks in that network partition. If you double-click a subnetwork, another Network Map window opens, displaying all the NEs that belong to that subnetwork.
Note If the Network Map is open when the Cisco 7600 NE Service is deactivated, the Network Map continues to show the links and their status as they were before the NE Service was deactivated.
3.8.3 Adjusting the Zoom Level or Pan Position
When the Network Map is launched from the CTM domain, it displays a world map with the individual groups, network partitions, subnetworks, and NE icons. To view a particular region or icon, adjust the zoom level or pan position.
Step 1 In the Domain Explorer or Subnetwork Explorer tree, click a node and choose File > Network Map (or click the Open Network Map tool). The Network Map opens and the node is preselected.
Step 2 In the Network Map, choose Edit > Zoom In, Zoom Out, or Zoom Area to adjust the zoom level. You can also click the Zoom In, Zoom Out, or Zoom Area tools.
Step 3 To adjust the pan position, click the box on the upper-left side of the Network Map and use the mouse to drag and drop it to the desired region. Use the scroll bars to pan the view to a different region.
Step 4 You can also view the links contained in each link bundle (aggregate link). Click a link bundle and choose Edit > Expand All Links (or double-click a link bundle to show all the links). To hide the links from view in the Network Map, click a link bundle and choose Edit > Collapse All Links.
3.8.4 Modifying a Node Icon or a Map Background Image
Network map backgrounds are provided by default as part of CTM, and are used to display a geographical layout of the network. The icons in the Network Map can be customized. See Appendix A, "Icons and Menus Displayed in CTM" for details of all the icons displayed in the Network Map window.
Images smaller than 640 x 480 pixels by default appear surrounded by blank space in the upper-left corner of the window. Images larger than 1024 x 768 pixels by default appear with scroll bars. Icon images are 32 x 32 pixels. CTM supports nonanimated GIF and shapefile format icons and maps. Shapefile is a universal standard for data files that allows users to zoom in and zoom out without losing details.
Note The size of the map file should not exceed 100 KB.
3.8.4.1 Modifying a Node Icon
Step 1 In the Domain Explorer or Subnetwork Explorer tree, click a node and choose File > Network Map (or click the Open Network Map tool).
Step 2 In the Network Map window, click a node and choose Edit > Change Node Icon (or right-click a node and in the shortcut menu, choose Change Node Icon). The Select Node Icon File dialog box opens.
Step 3 Select a node icon from within the default file system at C:\Cisco\TransportManagerClient\images\mapicons for Windows systems or at /opt/CiscoTransportManagerClient/images/mapicons for UNIX systems.
Step 4 After choosing an icon, click Open. The new icon appears in the Network Map.
Step 5 Choose File > Save (or click the Save Changes tool) to save the changes.
3.8.4.2 Modifying a Map Background
Step 1 In the Domain Explorer or Subnetwork Explorer tree, click a node and choose File > Network Map (or click the Open Network Map tool).
Step 2 In the Network Map window, click in the map background and choose Edit > Change Map Background (or choose Change Map Background from the right-click shortcut menu). The Select Background Map dialog box opens.
Step 3 Select a background image from within the default file system at C:\Cisco\TransportManagerClient\images\mapbkgnds for Windows systems or at /opt/CiscoTransportManagerClient/images/mapbkgnds for UNIX systems. Add user-defined images in this file system, or click Create New Folder and save user-defined images in a customized folder within this directory.
Step 4 After choosing a map background, click Open. The new map background appears in the Network Map.
Step 5 Choose File > Save (or click the Save Changes tool) to save the changes.
Note When you add NEs or groups to a group or to the top-level domain, the coordinates of those objects on the related Network Map are initially null, so CTM automatically positions the objects. If you move an object manually and save the map, the object has fixed coordinates. Therefore, if you open a map and find an icon in an unexpected position, the object most likely was never positioned manually and saved and was therefore positioned automatically. To fix the icon location, manually move the object to the correct position and save the map.
3.8.5 Saving Changes to the Network Map
Step 1 In the Domain Explorer or Subnetwork Explorer tree, click a node and choose File > Network Map (or click the Open Network Map tool).
Step 2 After making the necessary changes to the map background, node icon, or node coordinates in the Network Map window, you can save your settings by using one of the following methods:
•Save—Choose File > Save (or click the Save Changes tool) to save your settings. Your settings become a custom map that does not affect the default map for the nodes currently displayed in the Network Map. Users who have not saved their custom map will still see the default map for those nodes.
•Save As Default—Choose File > Save As Default to save your settings (map background, node icons, and x and y coordinates) as the default settings. Your settings become the default map for the nodes currently displayed in the Network Map and this default map is seen by users who have not saved their custom map for those nodes. There can be only one default setting per group of nodes in the Network Map.
Note The Save As Default menu option is disabled for the root or CTM domain node. By default, the customized map background and node icons are saved on your local workstation under <client_install_directory>/images/mapbkgnds/custom/default and <client_install_directory>/images/mapicons/custom/default.
•Revert to Default—Choose File > Revert to Default to cancel your settings (map background, node icons, and x and y coordinates) and revert to previous settings. Any custom map you created for the nodes currently displayed in the Network Map will be erased. The Network Map reverts to the default map assigned to these nodes.
Note Revert to Default is only available for nodes under subgroups.
3.9 How Do I Discover the Network for Optical, Routing, and MGX Devices?
The CTM discovery service collects information from individual CTC-based, ONS 155xx, CRS-1, XR 12000, and MGX NEs; discovers new NEs added to the network; updates network-level information (such as physical topology, logical circuits, and discrepancies); and updates device-level information (such as inventory and alarms).
When you add a new NE to CTM, the discovery process starts. When the process finishes, all of the NE information (such as inventory, configuration, physical topology, and discrepancies) is collected and CTM is updated.
Note The Discovered Network Elements group can be viewed only by users who have all NEs assigned to them. Therefore, in the Add New NE wizard, the grouping option "Group discovered NEs in the Discovered Network Elements Group" is not available.
3.9.1 Discovering CRS-1 and XR 12000 NEs
CTM supports CDP-based and BGP neighbor discovery for CRS-1 and XR 12000 NEs. CDP-based discovery is always enabled, while BGP neighbor discovery can be enabled or disabled in the Control Panel. See Table 4-31.
Note During BGP neighbor discovery, CTM discovers only the CRS-1 and XR 12000 NEs. No unmanaged NEs are discovered. Also, CTM uses the username and password in the User Settings table, Domain Explorer (Network Element Properties pane > NE Authentication tab), or Control Panel (Security Properties pane > CRS-1 or XR 12000 tab).
Note You should configure the BGP neighbor router ID so that the newly discovered CRS-1 or XR 12000 NEs' management IP address information will be available for discovery. See 5.6.14.1.5 Router ID Subtab, page 5-124 for more information. If the BGP neighbor router ID is not available, CTM tries to match the BGP neighbor interface IP address with all pre-existing CRS-1 and XR 12000 NEs' interface addresses. If a match is found, a new link is added between the two NEs. The new link might be incorrect if the NEs involved have the same IP address configured in any two interfaces.
3.9.2 Discovering Cisco 7600 NEs
CTM supports CDP-based and BGP neighbor discovery for the Cisco 7600 NE. It is recommended that you do at least one of the following to discover the Cisco 7600 NE (using either CDP or BGP) and to add the NE to CTM with a management IP address:
•Set up DNS—Add the unique Cisco 7600 NE name and its management IP address to the DNS server.
•Set up the local host in the /etc/hosts file—Modify the /etc/hosts file to add the name of the Cisco 7600 NE and its management IP address.
3.9.3 Discovering CTC-Based NEs
When a CTC-based NE is added as a GNE, all NEs that are DCC-connected to the GNE are discovered automatically. The discovered NEs are added automatically to CTM. The location of the new NE depends on what you set up in the discovery wizard.
3.9.4 Discovering ONS 155xx NEs
When you add a new ONS 155xx NE to CTM, the discovery process starts. When the process finishes, all of the NE information (such as inventory, configuration, physical topology, logical circuits, and discrepancies) is collected and CTM is updated. In addition, neighbors of the added NE are discovered. To discover new neighbors, the discovery service relies on CDP neighbor information and topology neighbor information obtained from the NEs.
The CTM ONS 155xx discovery service uses the following measures to keep the NE and network information in CTM synchronized with the NEs themselves:
•Periodic rediscovery based on the resync interval. Periodic rediscovery brings the information in CTM up to date for all ONS 155xx NEs in the network and rediscovers any new neighbors. The resync interval can be viewed and reset in the Control Panel. (For information about resetting the resync interval, see Resetting the Resync Interval.) If at least one ONS 155xx is already in the system, the first periodic rediscovery starts when the ONS 155xx NE service starts. The NE service usually starts when the CTM server is restarted. If no ONS 155xx NEs are in the system when CTM restarts, the first periodic discovery starts when the first ONS 155xx is added.
•Event-triggered rediscovery launched by certain changes to ONS 155xx NEs. Event-triggered discovery incrementally updates CTM with the new information. New neighbors of the affected NE are discovered. The device changes that trigger rediscovery include, but are not limited to, the following: reboot, CPU switchover, patch and topology changes, and insertion and removal of physical components.
•User-requested rediscovery. Users can request rediscovery of selected ONS 155xx NEs or the entire ONS 155xx network at any time. This updates CTM with information about the NEs. For more information about using rediscovery commands, see Rediscovering ONS 155xx, CRS-1, and XR 12000 NEs.
Note Only active NEs (NEs that are in the In Service or Under Maintenance states) can participate in the rediscovery process.
3.9.4.1 Discovery Information Table
The Discovery Information table displays discovery information for individual devices and for main discovery. The main discovery includes the discovery of individual devices plus network-level computations for topology, discrepancies, and logical circuits. The Discovery Information table shows all types of discovery: periodic rediscovery, user-requested rediscovery, and update-triggered discovery. To view the table, choose Configuration > ONS 155XX > Discovery Info Table in the Domain Explorer.
The following table describes the fields in the Discovery Information table.
Table 3-20 Field Descriptions for the Discovery Information Table
Field
|
Description
|
Discovered NE
|
NE system ID of the NE selected for discovery, or Main for the main discovery.
|
Start Time (time stamp)
|
Discovery start time. When the element name is an NE system ID, the elapsed time between start time and end time represents the amount of time required to discover the individual device. When the element name is Main, the elapsed time between the start time and end time includes:
•The time required to discover all of the individual NEs that participated in the current discovery cycle
•The time required for the network-level computations for topology, discrepancy, and logical circuits
|
End Time (time stamp)
|
Discovery end time (if the discovery has completed).
|
Status
|
Status of the discovery (whether it succeeded, failed, or is in progress). The status "idle" means that no discovery has ever occurred on the NE.
|
Start Mode
|
How the discovery was started (periodic rediscovery, user-requested discovery, or discovery triggered by an update).
|
Description
|
Type of discovery that was performed. If the discovery fails, this column includes a description of the cause of the failure.
|
3.9.5 Rediscovering ONS 155xx, CRS-1, and XR 12000 NEs
The Rediscover and Rediscover All commands perform a rediscovery of selected ONS 155xx, CRS-1, or XR 12000 NEs or of the entire ONS 155xx, CRS-1, or XR 12000 network. Rediscovery updates CTM with current network-level information (such as physical topology, logical circuits, and discrepancies) and device-level information (such as inventory and alarms).
Note Periodic rediscovery occurs every 24 hours, and certain changes on the device can trigger incremental rediscovery.
Start rediscovery from any of the following windows:
•Domain Explorer
•Subnetwork Explorer
•Network Map
Note Only users with the appropriate privileges can use the Rediscover All command.
Step 1 To rediscover selected NEs, select NEs or groups of NEs and choose Configuration > ONS 155XX, Cisco CRS-1, or Cisco XR 12000 > Rediscover.
Note This command is unavailable unless at least one NE in the selection is in the In Service or Under Maintenance states.
Step 2 To rediscover all ONS 155xx, CRS-1, or XR 12000 NEs in the network, choose Configuration > ONS 155XX, Cisco CRS-1, or Cisco XR 12000 > Rediscover All.
Note This command is unavailable unless at least one NE in the network is in the In Service or Under Maintenance states.
Step 3 Click Yes in the confirmation dialog box to initiate rediscovery.
For CRS-1 and XR 12000 NEs, if the Rediscover or Rediscover All operation succeeds, the Audit Log records the following message:
Rediscover of the NE: <NE_IP_address> successfully completed.
Rediscover All of the NEs: <list_of_NE_IP_addresses> successfully completed.
Rediscover and Rediscover All operations are available only for in-service or under-maintenance NEs. If you try to initiate rediscovery for NE(s) that are not in service or under maintenance, the Error Log records the following minor error:
Skipping rediscover for: <NE_IP_address> as its state is neither In Service nor Under
Maintenance.
Note If a Rediscover process is already in progress on a single NE and you choose Rediscover again, the request will be accepted but not executed by CTM. Similarly, if a Rediscover All process is already in progress and you choose Rediscover All again, the request will be accepted but not executed by CTM.
3.9.6 Resynchronizing CTM with CRS-1 and XR 12000 NEs
To resynchronize CTM with CRS-1 and XR 12000 NEs after an error condition, select Configuration > Cisco CRS-1 or Cisco XR 12000 > Resync with NE in the Domain Explorer.
3.9.7 Resetting the Resync Interval
The Resync Interval setting displays the frequency at which the configuration is rediscovered, retrieved, and processed for the NEs. The following information is retrieved:
•General system information including node name, system time zone, SNTP configuration, and power monitoring information
•NE's network information including IP address, static routes, OSPF, and RIP configuration
•Card provisioning data
•DCC configuration
•Timing synchronization
•Protection group configuration
•Ethernet Spanning Tree configuration
•Alarm profiles
•Security configuration
•NE defaults
•Routing table and protocol information
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 Expand NE Service.
Step 3 Select an NE and change the Resync Interval field in the Resync Scheduling area.
Step 4 Click Save.
3.9.8 Discovering the Network for MGX Voice Gateway Devices
The CTM discovery service:
•Collects information from individual MGX NEs
•Discovers new NEs
•Updates device-level information (such as inventory and alarms)
CTM supports discovery for MGX chassis and subchassis components using IP addresses, address lists, or IP address ranges as input. See 6.11 MGX Voice Gateway Cards, page 6-25 for a list of MGX modules that are discovered and displayed in the GUI.
CTM provides subchassis component discovery (configuration upload and parse) and sync up, as well as autonomous trap processing of configuration changes. Sync up is initiated periodically.
3.10 How Do I Test Connectivity for Optical and Routing Devices?
The following sections describe how to test server connectivity to an NE. The following table explains the difference between pinging an NE and testing NE connectivity.
Table 3-21 Testing NE Connectivity
Method
|
Description
|
Ping NE
|
Pinging the NE uses the standard UNIX ping command to verify IP connectivity between the CTM server and an NE. If successful, the ping results include the NE's IP address, round-trip time, and packet loss statistics. A response of "Request timed out" means there was no response to the ping attempt. If the ping is unsuccessful, verify that the NE's IP address and SNMP settings are configured correctly.
|
Test NE connectivity
|
The Test NE Connectivity operation uses the appropriate management protocol (SNMP, TL1, or CORBA) to run the ping command to verify the server's IP connectivity to an NE. If the ping is successful, the Test NE Connectivity operation verifies that the management protocol is configured correctly. The results show whether the connection state of the NE is Available or Unavailable. If Available, the connection state of an NE is updated to Available in the CTM database. If the connection state of an NE is listed as Unavailable, a connectivity or configuration problem exists. Complete the steps in K.3.5 NE Connection State Is Listed as Unavailable, page K-7 to resolve the problem and retest NE connectivity.
|
3.10.1 Pinging an NE
Step 1 In the Domain Explorer tree, select the NE to ping.
Step 2 Choose Fault > Ping NE. The ping results include round-trip time and packet loss statistics.
Step 3 Click OK in the dialog box.
Note This function is enabled if the operational state of the NE is In Service or Under Maintenance. It is disabled if the operational state of the NE is Out of Service or Preprovisioned.
Note A link to the ping utility must be present in your PATH variable on the CTM server. The default location is /usr/sbin/ping. If a link to the ping utility is not present in your PATH variable, configure your PATH settings to include it.
3.10.2 Testing NE Connectivity
Step 1 In the Domain Explorer tree, select an NE.
Step 2 Choose Fault > Test NE Connectivity. The Test NE Connectivity operation runs the ping command to check the NE communication state. The results show whether the NE is available or unavailable:
•Available—If the CTM client can reach the NE through its management protocol, the communication state of the NE in the database is checked. If the NE communication state is Unavailable, it is changed to Available and an event is sent to the CTM client, stating that the communication state was changed. If the NE communication state is Available, there are no changes.
•Unavailable—If the CTM client cannot reach the NE through its management protocol, the communication state of the NE in the database is checked. If the NE communication state is Available, it is changed to Unavailable and an event is sent to the CTM client, stating that the communication state was changed. If the NE communication state is Unavailable, there are no changes.
Step 3 Click OK in the dialog box.
Note If you run the test NE connectivity operation for an ONS 1580x, CTM attempts to open a TL1 session to the NE, send a RTRV-HDR TL/1 command, and then close the session. Since the ONS 1580x agent has a limit of five concurrent TL1 sessions, the test NE connectivity operation requires the agent to have at least one TL1 session available to allow it to succeed.
3.11 How Do I Test Connectivity for MGX Voice Gateway Devices?
Note You can run a diagnostic check at the node level to verify that CTM is correctly managing the selected nodes. See 4.6.12.2 Running a Diagnostic Check at the Node Level, page 4-108.
Testing NE connectivity occurs at the management protocol level (SNMP or CORBA).
Step 1 In the Domain Explorer tree, select the MGX node and choose Fault > MGX Voice Gateway > Diagnostic Center.
Step 2 Click the Manageability tab to display the node login information.
Step 3 In the Node Login Information section, enter the user ID and password.
Step 4 Click Check Manageability. The following manageability check results are displayed:
•Node ID
•Node name
•IP connectivity
•FTP configuration
•Community string configuration
•Trap IP address configuration
•Trap manager configuration
•Time stamp
