Cisco 78-16845-01 User Manual

CHAPTER

Building the Network

After you have planned your network,youcanbeginbuilding the network components: groups, network partitions, subnetworks, NEs, links, and network maps.

This chapter contains the following sections:

• 3.1 Overview, page 3-1

• 3.2 How Do I Build Groups?, page 3-2

• 3.3 How Do I Build Network Partitions?, page 3-4

• 3.4 How Do I Build Subnetworks?, page 3-6

• 3.5 How Do I Build NEs?, page 3-7

• 3.6 How Do I Build Links?, page 3-28

• 3.7 How Do I Use Network Maps?, page 3-46

• 3.8 How Do I Discover the Network for Optical and Routing Devices?, page 3-50

• 3.9 How Do I Discover the Network for MGX Voice Gateway Devices?, page 3-54

• 3.10 How Do I Synchronize the Network for Optical and Routing Devices?, page 3-55

• 3.11 How Do I Synchronize the Network for MGX Voice Gateway Devices?, page 3-64

• 3.12 How Do I Test Connectivity for Optical and Routing Devices?, page 3-66

• 3.13 How Do I Test Connectivity for MGX Voice Gateway Devices?, page 3-67

3.1 Overview

The CTM management domain is the top-level root node in the Domain Explorer tree. The management domain contains NEs and groups of NEs. You can add, delete, and modify the following network components:

• Groups—Collection of groups or collection of NEs. NEs are often grouped geographically or by

• Network Partitions—Logical segment of NEs (grouped in subnetworks) in which NEs of the same

• Subnetworks—Sets of NEs interconnected at a specific network layer (such as physical, section,

78-16845-01

domain.

model type are managed by a single NE service.

line, and so on). Subnetworks are contained within networkpartitions.NEsmustbelongtothesame subnetwork in order to create circuits between them.

Cisco Transport Manager Release 6.0 User Guide

3-1

3.2 How Do I Build Groups?

• Links—Physical or logical entities (for example, a fiber) between two physical points (for example,

ports). Circuits are provisioned through links.

• Network Maps—Geographicrepresentationofthe 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 and/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.

Chapter 3 Building the Network

Note You cannot add a new group to the Discovered NEs or Deleted NEs group.

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.

3-2

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.

Cisco Transport Manager Release 6.0 User Guide

78-16845-01

Chapter 3 Building the Network

Note A group cannot be pasted into the Discovered NEs or Deleted NEs group.

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.

3.2.3 Moving Groups

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 NEs or Deleted NEs 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.

78-16845-01

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.

Cisco Transport Manager Release 6.0 User Guide

3-3

3.3 How Do I Build Network Partitions?

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.

Chapter 3 Building the Network

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 for CTC-based NEs should contain fewer than 500 NEs. Multiple network

partitions are required when managing more than 500 CTC-based NEs or when 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

3.5.6 Automatically Grouping NEs in Subnetworks, page 3-24.

3.3.1 Adding Network Partitions

3-4

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.

Cisco Transport Manager Release 6.0 User Guide

78-16845-01

Chapter 3 Building the Network

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.

3.3.2 Modifying Network Partitions

Table 3-3 Field Descriptions for the Network Partition Properties Pane

Field Description

NetworkPartitionID 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.

78-16845-01

Cisco Transport Manager Release 6.0 User Guide

3-5

3.4 How Do I Build Subnetworks?

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 3.5.6 Automatically Grouping

NEs in Subnetworks, page 3-24.

Chapter 3 Building the Network

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

Subnetwork Type Type of subnetwork (SONET, SDH, other, or unknown). Subnetwork Topology Subnetwork topology. Description Description of the subnetwork.

alphanumeric or special characters.

3-6

Step 4 Click OK. The new subnetwork appears in the Subnetwork Explorer tree.

Cisco Transport Manager Release 6.0 User Guide

78-16845-01

Chapter 3 Building the Network

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 3.5.6 Automatically Grouping NEs in

Subnetworks, page 3-24.)

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.2 Moving Subnetworks

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 3.5.7.4 Removing a Deleted NE, page 3-27.

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.

78-16845-01

Cisco Transport Manager Release 6.0 User Guide

3-7

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

valueon the ONS 15216 EDFA2or EDFA3match. To ensure that these valuesmatch, 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 EDFA3only) 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 TFTP directory should have read-write access. To configure the default tftpboot directory:

Chapter 3 Building the Network

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.

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 inventoryinformation inthe Domain Explorer and add specificinformation (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.

3-8

Cisco Transport Manager Release 6.0 User Guide

78-16845-01

Chapter 3 Building the Network

3.5.1 Prerequisites for Adding NEs

Note To add an ONS 15302 or ONS 15305 NE to CTM, its SNMP Users table must contain the following row:

0.0.0.0 public true where, public is the community string. In addition, to obtain the trap events from the NE, the CTM Server IP address must be added to the NE. Refer to the Cisco Edge Craft User

Documentation for more information.

3.5.1.3 Prerequisites for Adding ONS 15310, ONS 15454 SONET, and ONS 15454 SDH NEs

Before adding ONS 15310, ONS 15454 SONET,or ONS 15454 SDH NEs with ML-series cards to CTM, make sure the NEs are properly set up according to the following:

• 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=CTM Server IP address, UDP Port=162, SNMP

version=SNMPv2, maximum Traps/second=0, and SNMP community string must be created and must allow SNMP sets to receive traps from ML-series modules.

• The Cisco IOS startup-config file must have the snmp-server enable traps command to receive

traps from ML-series modules.

• Whenever the user changes the trap destination for NE IP address and port=162 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, note the following SNMP configuration requirements in a

GNE/ENE scenario:

1. SNMPv1 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 ENEs have two possible configurations:

a. First configuration:

–

ENE trap destination: GNE IP address

–

ENE trap port: 391

–

ENE community string: Same as on GNE

–

ENE version: v1

b. Second configuration:

–

ENE trap destination: CTM server IP address

–

Relay A IP address: IP address of the NE that is directly connected to the ENE

–

Relay A community string: Same as on all other NEs

–

Relay B IP address: IP address of the NE that is directly connected to the Relay A NE

–

Relay B community string: Same as on all other NEs

–

Relay C IP address: IP address of the NE that is directly connected to the Relay B NE

–

Relay C community string: Same as on all other NEs

78-16845-01

Cisco Transport Manager Release 6.0 User Guide

3-9

3.5.1 Prerequisites for Adding NEs

–

Trap port: 162

–

Version: v1

–

Community string: Same as on the GNE

Note If there is a direct connection from the ENE to GNE, it becomes the Relay A NE. If there

are intermediate NEs between the ENE and GNE, these NEs must be specifiedas the relays. The community strings should be the same on all the NEs, including the relay NEs.

2. SNMP v2 uses the following configurations on GNEs and ENEs for traps:

GNE: Same as for SNMP v1 ENE: Same as for SNMP v2 on option b

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 properly set up. 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 for illustration purposes only. Refer to the relevant hardware documentation for detailed command information.

Chapter 3 Building the Network

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.

3-10

Cisco Transport Manager Release 6.0 User Guide

78-16845-01

Chapter 3 Building the Network

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

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. Step 6 Click OK.

3.5.1 Prerequisites for Adding NEs

ONS 15540 NEs that are configured with the default community string.

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.

78-16845-01

Cisco Transport Manager Release 6.0 User Guide

3-11

3.5.1 Prerequisites for Adding NEs

3.5.1.4.3 Topology Setup

Chapter 3 Building the Network

Appropriate topology information must be configuredon 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, topology can be configured in two ways: by using CDP learning or through IP using Ethernet. For the ONS 15501, topology must be configured manually.

CDP neighbor information exchanged between the Optical Supervisory Channel (OSC) ports of two adjacent NEs, or between the 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 issued 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 issued 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

3.5.1.4.4 Patch Setup

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

Optical patches must be set up on all NEs between through interfaces, WDM interfaces, and so on.

3-12

Cisco Transport Manager Release 6.0 User Guide

78-16845-01

Chapter 3 Building the Network

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 Unbundled CiscoView (Optional)

In CTM, CiscoViewis used for configuring and monitoring ONS 155xx NEs. Server-based (unbundled) CiscoView should be installed on the CTM server. Without unbundled CiscoView:

• You cannot launch CiscoView on ONS 15501 NEs.

• You can launch CiscoView on ONS 15530 and ONS 15540 NEs only if embedded CiscoView is

installed on these NEs.

For information about installing CiscoView on the CTM server, see the Cisco Transport Manager Release 6.0 Installation Guide.

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 I, “Using CiscoView to Configure and

Monitor ONS 15501, ONS 15530, and ONS 15540 NEs.”

3.5.1 Prerequisites for Adding 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 Cisco CRS-1 and XR 12000 NEs

Before adding a Cisco Carrier Routing System 1 (CRS-1) or XR 12000 NE to CTM, complete the following prerequisites:

• Enter the following CLI command to add the Manageability pie (if it is not already installed):

install add

• Enter the following CLI commands:

xml agent corba (to connect using CORBA) xml agent corba ssl (to connect in secure mode using SSL) domain ipv4 host logging events level informational

<PIE_file_location>to<device>

<EMS_server_name> <EMS_server_IP_address

activate

78-16845-01

Cisco Transport Manager Release 6.0 User Guide

3-13

3.5.1 Prerequisites for Adding NEs

• Create a username and password with appropriate privileges.

• 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

• 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.

Note 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.

Chapter 3 Building the Network

discovery process adds the discovered NEs to CTM; however, you must mark the NEs as In Service.

3.5.1.7 Prerequisites for Adding Cisco Catalyst 6509 NEs

Before adding a Cisco Catalyst 6509, configurethe NE with a valid community string. Then, add the NE to CTM. Network discovery is not supported for the Cisco Catalyst 6509. The Catalyst 6509 is supported only in terms of managing the Cisco CRS-1.

3.5.1.8 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.8.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 sync up

automatically (except at the initial stage when the community strings on the devices are at default).You have to explicitly change them on both sides (using the Network Element Property pane in the Domain Explorer on CTM and the command line interface (CLI) on the switch). See 3.5.1.8.3 Changing

Community Strings Using the Domain Explorer and 3.5.1.8.4 Changing Community Strings Using the CLI. If this is not done, all SNMP requests fail, and the CTM database is inconsistent with the network.

3-14

Cisco Transport Manager Release 6.0 User Guide

78-16845-01

Chapter 3 Building the Network

3.5.1 Prerequisites for Adding NEs

To configure the SNMP community string, you must change the community strings on the devices through the CLI.

Table 3-6 describes the various options involved in configuring SNMP.

Table 3-6 SNMP Conﬁguration Options

Option Description

Domain Explorer, Network Element Properties pane, NE Authentication tab

After saving the community strings information, the CTM processes use the new community strings for SNMP accesses.

Since users must configurethe community strings on both the devices through 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 Configuredcommunity 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.8.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 the NE Authentication tab in the Domain Explorer.

Note This method affects only CTM. Youmust make sure that community strings and passwords within CTM

match those on the switches.

3.5.1.8.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.8.4 Changing Community Strings Using the CLI

78-16845-01

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]

Cisco Transport Manager Release 6.0 User Guide

3-15

3.5.1 Prerequisites for Adding NEs

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 xxyyzz%

Step 4 Enter the following command to check that the community string has changed:

dspsnmp

You will see output similar to the following example:

xxyyzz.7.PXM.a > dspsnmp xxyyzz System Rev: 05.00 Dec. 14, 2004 20:04:14 GMT MGX8850 Node Alarm: MAJOR Community (rw): private Community (ro): public System Location: building 3 System Contact:

Chapter 3 Building the Network

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 xxyyzz%

Step 3 Enter the following command to check that the community string has changed:

dspsnmp

You will see output similar to the following example:

xxyyzz.7.PXM.a > dspsnmp xxyyzz System Rev: 05.00 Dec. 14, 2004 20:04:14 GMT MGX8850 Node Alarm: MAJOR Community (rw): private Community (ro): public System Location: building 3 System Contact:

3.5.1.8.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.

Cisco Transport Manager Release 6.0 User Guide

3-16

78-16845-01

Chapter 3 Building the Network

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. The following

example is shown:

xxyyzz.7.PXM.a > xxyyzz.7.PXM.a > cnfpasswd Enter existing password: Enter new password: Re-enter new password: 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.

Note Table 3-7 describes the fields in the Add New NE wizard.

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.

Note You cannot add a new NE to the Discovered Network Elements or Deleted Network Elements

group.

Step 2 Enter the following information:

a. NE model b. NE type c. NE addition—Click the Single NE Addition radio button d. IP address

Step 3 Click Next.

78-16845-01

Cisco Transport Manager Release 6.0 User Guide

3-17

3.5.2 Adding NEs

Step 4 Enter the following information. Fields shown depend on the NE type.

Note • Do not use “CTM” as an NE ID because the Alarm Browser might contain CTM alarms with the

Chapter 3 Building the Network

Note If you click Finish in this window, Cisco default values will be assigned to the remaining fields.

a. NE ID

source ID “CTM.” It will be difficultto 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.”

• 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.

• 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. Operational state c. SNMP community string d. SNMP set only community string e. NE service-level username

f. NE service-level password g. Description h. Location name

i. Subnetwork ID

j. Network partition ID

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 MDS 9000, Catalyst 6509, ONS 15216, ONS 15310, 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 Explorer tree.

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 Domain Explorer tree.

3-18

Cisco Transport Manager Release 6.0 User Guide

78-16845-01

Chapter 3 Building the Network

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.7 Adding a New NE Software Version

to the CTM Domain, page 4-37.

3.5.2.2 Adding Multiple NEs

Note Table 3-7 describes the fields in the Add New NE wizard.

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.

Note You cannot add a new NE to the Discovered Network Elements or Deleted Network Elements

group.

3.5.2 Adding NEs

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 will be assigned to the remaining fields.

Step 4 Enter the following information. Fields shown depend on the NE type.

a. NE ID—Read-only b. Operational state

78-16845-01

c. SNMP community string d. SNMP set only community string e. NE service level username

f. NE service level password

g. Description

Cisco Transport Manager Release 6.0 User Guide

3-19

3.5.2 Adding NEs

Step 5 Click Next if you are adding an ONS 15302, ONS 15305, ONS 15327, ONS 15454 SONET, ONS 15454

Step 6 Click Finish if you are adding a Cisco MDS 9000, Cisco MGX, Catalyst 6509, ONS 15310, ONS 15600

Step 7 Select the grouping option for the NE. Step 8 Click Finish to add the NEs to the Domain Explorer tree.

Step 9 Check to see if the communication state is correct. If CTM cannot connect to the NE, the NE displays

Step 10 Verify that the NE software version is listed in the Supported NE table (Domain Explorer >

Chapter 3 Building the Network

h. Location name

i. Subnetwork ID

j. Network Partition ID

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.

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.

SDH, ONS 15800, ONS 15801, ONS 15808, CRS-1, or XR 12000 NE.

Wait 2 to 5 minutes while the CTM server completes the node discovery. (Not applicable if the operational state is Preprovisioned.)

an unavailable communication state icon in the Domain Explorer tree.

Administration > Supported NE Table). If it is not listed, see 4.3.7 Adding a New NE Software Version

to the CTM Domain, page 4-37.

Table 3-7 Field Descriptions for the Add New NE Wizard

Field Description

NE Addition Panel

NE Model Select the NE model (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 15310 CL, 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 The Catalyst 6509 is supported only in terms of managing the Cisco CRS-1.

NE Type Select the type of NE.

Note Available types depend on the selected NE model.

NE Addition Select Single NE Addition to add only one NE. Select Bulk NE Addition to add several NEs

simultaneously. The available fields will change, depending on which item you select.

Cisco Transport Manager Release 6.0 User Guide

3-20

78-16845-01

Chapter 3 Building the Network

3.5.2 Adding NEs

Table 3-7 Field Descriptions for the Add New NE Wizard (continued)

Field Description

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

Enter the beginning IP address for the range of NEs you want to add.

bulk NE additions) 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 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.

NE Properties Panel

NE ID (Read-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 difficultto 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.

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.

SNMP Community String

Enter the SNMP community string for the NE. The Cisco default is public.

Note The SNMP community string applies only to the Catalyst 6509, ONS 15216 EDFA2,

ONS 15216 EDFA3, ONS 15302, ONS 15305, ONS 15310, 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

NE Service Level

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.

Enter the username that the CTM server uses to connect to NEs.

Username

78-16845-01

Cisco Transport Manager Release 6.0 User Guide

3-21

+ 47 hidden pages