Cisco Media Gateway Controller Node Manager User Guide, Release 2.8(1)

Deploying Your Network in Cisco MNM

This chapter provides information about deployment in the following sections:

•Overview of Deployment

•Information Needed for Deployment

–Deployment Rules

•Seed File Deployment

–Seed File Example and Syntax

–Deploying a Network Using a Seed File

•Manual Deployment

–Overview of Steps to Deploy a Cisco PGW 2200 Softswitch Node Manually

–Overview of Steps to Deploy a Cisco PGW 2200 Softswitch Farm Manually

–Deploying a Physical Site

–Deploying a Cisco PGW 2200 Softswitch Node Object

–Deploying Network Devices

•About the Discovery Process

–Discovery of Cisco PGW 2200 Softswitch Host, Cisco HSI Server, and Cisco BAMS Components

–Discovery of Cisco Catalyst 2900XL Components

–Discovery of Cisco Catalyst 5500 and 6509 Components

•Keeping the Cisco MNM Network Model Up to Date

–SNMP Traps for Configuration Changes

–Synchronizing the Cisco MNM with Device Changes

–Modifying or Deleting Deployed Objects

•Exporting Deployment Information to an Inventory or Seed File

Note For information on troubleshooting deployment errors, see Appendix C, "Troubleshooting Cisco MNM."

Overview of Deployment

Cisco MNM uses the term deployment to refer to the addition of objects to the network model. For Cisco MNM to be able to manage your network, the Cisco PGW 2200 Softswitch node and its devices must first be deployed. When the device is deployed, an object for each device is created automatically. This created object represents a real object in the network and is accessible under the Physical and device-specific views in the Map Viewer.

Note•The other task in setting up the management of your network is configuration of the managed devices so that they forward alarms to Cisco MNM. Typically, this is done by the system administrator. Deployment tells Cisco MNM how to communicate with the managed devices; configuration tells the devices how to communicate with Cisco MNM. See Chapter 2, "Configuring Network Devices for Management" for details.

•Cisco IP Transfer Point LinkExtender (ITP-L) is the new name for Cisco Signaling Link Terminal (SLT). Over time, ITP-L will replace SLT in publications and the product.

Deploy an object by giving Cisco MNM the basic information needed to manage the device, such as the IP address and login ID and password. If you are using SSH in your managed network and have installed SSH for Cisco MNM, also specify the security policy of components that can be SSH-enabled:

•Cisco PGW 2200 Softswitch host

•Cisco BAMS

•Cisco HSI server

•Cisco ITP-L

•Cisco Integrated ITP-L

•Cisco Catalyst 5500 and 6509 LAN switches

You can deploy a Cisco PGW 2200 Softswitch node and its devices in two ways:

•Manually, using a deployment template to fill in details for each device individually

•With a seed file, specifying deployment information for a group of devices in an external seed file that is read by Cisco MNM

After you deploy a device, whether manually or with a seed file, Cisco MNM contacts the device and discovers information about its configuration. For example, when a Cisco ITP-L is deployed, Cisco MNM discovers any TDM (DS1) interfaces. When a Cisco LAN Switch is deployed, Cisco MNM discovers ports and modules. When the Cisco PGW 2200 Softswitch host is deployed, Cisco MNM discovers the system components as well as signaling and trunking components.

Note Dial plan components on Cisco PGW 2200 Softswitch are no longer supported on Cisco MNM 2.8(1).

Carry out the deployment for the entire Cisco PGW 2200 Softswitch node or farm when you first set up Cisco MNM. Later, deploy a new device to the network on a device-by-device basis. To keep the Cisco MNM model synchronized with changes in device configurations, define a frequency for auto-rediscovery or manually rediscover device components after making changes. The default frequency for rediscovery is 6 hours.

You can also save a copy of your deployed network model as a seed file to use when adding new devices to the network. The seed file can be modified with a text editor to copy or add new device addresses and passwords, and export the network information in an inventory file. For more information, see the "Exporting Deployment Information to an Inventory or Seed File" section.

Information Needed for Deployment

Whether you are deploying components with a seed file or manually, Cisco MNM needs the same information about the network. Table 5-1 summarizes the information needed. The first column shows the attribute name in the seed file, and the second column shows the field name in the Deployment template.

Deployment Rules

Cisco PGW 2200 Softswitch Hosts

You can define a maximum of two hosts per Cisco PGW 2200 Softswitch node: the active and standby Cisco PGW 2200 Softswitch hosts. You do not have to specify which host is active or standby; it is determined automatically by Cisco MNM. You must specify the name for each Cisco PGW 2200 Softswitch node.

Caution Although Cisco MNM does not prevent you from deploying more than two hosts per node, the system is not designed to support this configuration.

Cisco PGW 2200 Softswitch Farms

You can define one or more Cisco PGW 2200 Softswitch nodes under a Cisco PGW 2200 Softswitch farm.

Physical Locations and Deployment

When a device is deployed, it is placed into the Physical containment tree for its location. For example, all devices with location=Chicago are placed under a site object named Chicago. If the specified location does not exist, Cisco MNM automatically deploys a site object with the specified location name. If you do not specify a physical location for a device, it is deployed in the same location as its logical parent. If no location is specified for the parent, the objects are deployed to a site called Default.

Cisco PGW 2200 Softswitch node objects and farm objects are not physical devices and, as such, are not deployed into the Physical containment tree. You can specify a location for the Cisco PGW 2200 Softswitch node or farm, however, so that children of the node can, by default, be placed in the specified location. For example, if you specify that a Cisco PGW 2200 Softswitch node is in the site Cincinnati, all of its children that do not specify a location are, by default, placed in the Cincinnati site.

Seed File Deployment

A seed file is a text file containing the names and IP addresses of all the devices in the Cisco PGW 2200 Softswitch network, together with the relationship (hierarchy) between the devices. For bulk deployment, use a seed file to deploy an entire Cisco PGW 2200 Softswitch network consisting of one or more Cisco PGW 2200 Softswitch nodes or farms. Using this file, Cisco MNM automatically deploys all the elements in the network.

Note A seed file requires the name and IP address for each device to be deployed, and it can optionally contain the userid and password necessary to log in to the device.

To perform seed file deployment, launch a dialog from an MGC-Node-View node or other type of object in the Map Viewer. This dialog prompts you for the name of the seed file and, if not specified in the seed file, for the login ID and password for each device type. You also specify SNMP read- and write-community strings for the Cisco ITP-L and Cisco LAN Switch.

Note A sample seed file is located at <CEMF Root>/samples/seedfile.txt and in Example 5-1.

Seed File Example and Syntax

Sample seed files are shown in Example 5-1 (seed file for Cisco PGW 2200 Softswitch node) and Example 5-2 (seed file for Cisco PGW 2200 Softswitch farm).

The examples are followed by an explanation of the required syntax. You can also view a sample seed file at <CEMF Root>/samples/seedfile.txt.

Note By default, Cisco MNM looks for the seed file in the <CEMF_ROOT>/bin/.mgcController sysmgr folder. If you place the file elsewhere, note the location. The location needs to be specified in the Deploy Network dialog box.

Seed File Examples

Example 5-1 Sample Seed File for Cisco PGW 2200 Softswitch Node

# Sample MGC Network Seed File

MGC (name = mgc-node-1) {

   HOST (name = mgc-host-1, location = Site-1,  ip = 10.1.1.1, securitypolicy = none)

   HOST (name = mgc-host-2, location = Site-1,  ip = 10.1.2.1, securitypolicy = none)

   2600 (name = slt-1,  location = Site-1, ip = 10.1.1.2, securitypolicy = none)

   2600 (name = slt-2,  location = Site-1, ip = 10.1.2.2, securitypolicy = none)

}

2900xl (name = lanswitch-1,  location = Site-1, ip = 10.1.1.3, securitypolicy = none)

5500 (name = lanswitch-2,  location = Site-1, ip = 10.1.2.3, securitypolicy = none)

MGC (name = mgc-node-2) {

   HOST (name = mgc-host-3,   location = Site-1, ip = 10.1.3.1)

   HOST (name = mgc-host-4,   location = Site-1, ip = 10.1.4.1)

   INTEGRATED_SLT (name = slt-3,  location = Site-1, ip = 10.1.1.3, securitypolicy = ssh)

   INTEGRATED_SLT_CORESIDENT (name = slt-4,  location = Site-1, ip = 10.1.2.4, 
securitypolicy = SSH)

}

6509 (name = lanswitch-5,  location = Site-1, ip = 10.1.4.3, securitypolicy = ssh)

BAMS (name = bams-1, location = Site-1, ip = 10.10.3.1, securitypolicy = ssh)

HSI (name = gwing-1, location = Site-1, ip = 10.10.3.2, securitypolicy = ssh)

Example 5-2 Sample Seed File for Cisco PGW 2200 Softswitch Farm

# Sample MGC Seed File including a Farm

BAMS (name = bams-mast, location = bams-mast, ip = 10.18.126.102, securitypolicy = none)

FARM (name=MGCFarm-1)

 {

  MGC (name=MGC-vsc9)

   {

     HOST (name = nssuvsc9, location = nssuvsc9, ip = 10.18.126.59, securitypolicy = none)

   }

 }

BAMS (name = bams-sla, location = bams-sla, ip = 10.18.126.103, securitypolicy = none)

HSI (name = HSI-218, location = HSI-218, ip = 10.18.126.218, securitypolicy = none)

5500 (name = 5509, location = 5509, ip = 10.18.126.5, securitypolicy = none)

MGC (name=MGC-slt)

 {

  2600 (name = slt-b, location = slt-b, ip = 10.18.126.10, securitypolicy = none)

Seed File Syntax

The specifications for each Cisco PGW 2200 Softswitch host, Cisco ITP-L, Cisco Integrated ITP-L, and LAN switch are grouped under the relevant Cisco PGW 2200 Softswitch node.

For a Cisco PGW 2200 Softswitch farm, the specifications for each Cisco PGW 2200 Softswitch node in the farm are grouped under the farm specification. The specifications for each Cisco PGW 2200 Softswitch host are grouped under the appropriate node.

Note A node associated with a farm includes Cisco PGW 2200 Softswitch hosts only.

The specification for each Cisco BAMS or Cisco HSI server must be specified on its own line. The Cisco MNM then determines the node with which the Cisco HSI server or Cisco BAMS is associated at deployment.

For each Cisco PGW 2200 Softswitch node:

MGC (name=mgcnodename, location=Physical site) {Values for Cisco MGC node devices}

For each Cisco PGW 2200 Softswitch farm:

FARM (name=mgcfarmname, location=Physical site) {Values for Cisco MGC node and host}

Enclosed in braces under a node, the values for Cisco PGW 2200 Softswitch node devices:

•For each Cisco PGW 2200 Softswitch host:

HOST ([name=Cisco MGC host name,] ip=IP address, [read=public,] [write=private,] 
[location=Physical site,] [securitypolicy=Securitypolicy])

•For each Cisco ITP-L:

2600 ([name=Cisco SLT name,] ip=IP address, [read=public,] [write=private,] 
[location=Physical site,] [securitypolicy=Securitypolicy])

•For each Cisco INTEGRATED ITP-L:

INTEGRATED_SLT ([name=Cisco SLT name,] ip=IP address, [read=public,] 
[write=private,] [location=Physical site,] [securitypolicy=Securitypolicy])

•For each co-resident Cisco INTEGRATED ITP-L:

INTEGRATED_SLT_CORESIDENT([name=Cisco SLT name,] ip=IP address, [read=public,] 
[write=private,] [location=Physical site,] [securitypolicy=Securitypolicy])

•For each Cisco 2900XL LAN Switch, on its own line:

2900XL ([name=Cisco LAN Switch name,] ip=IP address, [read=public,] 
[write=private,] [location=Physical site,] [securitypolicy=Securitypolicy])			

•For each Cisco 5500XL LAN Switch, on its own line:

5500 (ip=IP address, [name=Cisco LAN Switch name,] [read=public,] [write=private,] 
[location=Physical site,] [securitypolicy=Securitypolicy])

•For each Cisco 6509XL LAN Switch, on its own line:

6509 (ip=IP address, [name=Cisco LAN Switch name,] [read=public,] [write=private,] 
[location=Physical site,] [securitypolicy=Securitypolicy])

•For each Cisco HSI server, on its own line:

HSI ([name=HSI host name,] ip=IP address, [location=Physical site,] 
[securitypolicy=Securitypolicy]) 

•For each Cisco BAMS, on its own line:

BAMS ([name=BAMS name,] ip=IP address, [location=Physical site,] 
[securitypolicy=Securitypolicy]) 

Note If the Cisco BAMS has been configured to collect call detail records (CDRs) for a Cisco PGW 2200 Softswitch host, the Cisco BAMS is deployed in the node containing that host. To appear in that node, it must be actively polling CDRs.

Deploying a Network Using a Seed File

Use the following procedure to deploy a network using a seed file:

Step 1 Create a seed file manually or generate a seed file with the Cisco VSPT. For seed file attributes, see Table 5-1. For seed file syntax, see the "Seed File Example and Syntax" section. Note the location of the seed file.

Step 2 From the Map Viewer screen, click the MGC-Node-View icon.

Step 3 Right-click, and choose Deployment > Deploy Network Seed File.

The Deploy Network window opens, as shown in Figure 5-1.

Figure 5-1 Deploy Network Window—Seed File Tab

Step 4 In the Filename field, enter the name of the seed file.

Note If the file is not in the default location, <CEMF Root>/bin/.mgcControllerx.sysmgr, include the path.

Step 5 Enter the software login information for each type of device.

Step 6 (Optional) To enter advanced information, such as SNMP configuration parameters, click the Advanced tab. Click the Seed File tab when you are done.

Step 7 Click Deploy. You are prompted to confirm the deployment.

Step 8 Click Yes.

The system displays the message "The network has been successfully deployed," and Cisco MNM goes on to discover the device subcomponents. See the "About the Discovery Process" section for details on what occurs during discovery.

Note If you receive an error message, see Table C-2 in Appendix C, "Troubleshooting Cisco MNM."

Manual Deployment

Cisco MNM defines a number of templates that allow you to manually configure Cisco PGW 2200 Softswitch nodes and other objects including:

•Cisco PGW 2200 Softswitch node

•Cisco PGW 2200 Softswitch host or host pair as a child of the Cisco PGW 2200 Softswitch node

•Top-level BAMS

•HSI server

•Cisco ITP-L as a child of a Cisco PGW 2200 Softswitch node

•Cisco LAN switch

•Cisco PGW 2200 Softswitch farm

•Cisco PGW 2200 Softswitch node or multiple nodes as children of the Cisco PGW 2200 Softswitch farm

The Deployment Wizard reads the templates and presents screens prompting you for information about the devices.

Overview of Steps to Deploy a Cisco PGW 2200 Softswitch Node Manually

Task 1. If one does not already exist, deploy a physical site as the container for the node.

Task 2. Deploy a Cisco PGW 2200 Softswitch node object.

Task 3. Deploy each of the devices that the node contains (Cisco PGW 2200 Softswitch host, ITP-L, LAN Switch).

Task 4. If applicable, deploy the BAMS.

Task 5. If applicable, deploy the HSI server.

Note Only one deployment wizard per user can be open at any time. If you attempt to open a second wizard, a message advises you that the deployment wizard is already active. Complete the first deployment task before proceeding.

Overview of Steps to Deploy a Cisco PGW 2200 Softswitch Farm Manually

Task 1. If one does not already exist, deploy a physical site as the container for the node.

Task 2. Deploy a Cisco PGW 2200 Softswitch farm object.

Task 3. Deploy each of the Cisco PGW 2200 Softswitch nodes that the farm contains.

Task 4. For each node, deploy each of the devices that the node contains (Cisco PGW 2200 Softswitch host, ITP-L, LAN Switch).

Task 5. If applicable, deploy the BAMS.

Task 6. If applicable, deploy the HSI server.

Note Only one deployment wizard per user can be open at any time. If you attempt to open a second wizard, a message advises you that the deployment wizard is already active. Complete the first deployment task before proceeding.

Deploying a Physical Site

Use the following procedure to deploy a physical site as the container for a Cisco PGW 2200 Softswitch node:

Step 1 Open the Map Viewer.

Step 2 In the left pane, right-click the Physical view icon.

Step 3 Choose Deployment > Deploy Generic Objects.

The Deployment Wizard Templates window opens showing a list of templates.

Step 4 Select Site, and click Forward.

The Object Parameters window opens.

Step 5 Specify the number of sites you are creating, or accept 1 as the default, and click Forward.

Step 6 Enter the name you want to use for the physical site (no spaces). Click Forward.

The Deployment Wizard Views window opens.

Step 7 Click Select.

Step 8 In the Object Selector window, select the Physical object, and click Forward.

A screen displays summarizing the deployment you have created.

Note

Step 9 Click Finish.

You are informed if the deployment was successful, and a physical site icon displays in the right pane of the Map Viewer window.

Step 10 Deploy the Cisco PGW 2200 Softswitch node object as described in the "Deploying a Cisco PGW 2200 Softswitch Node Object" section.

Deploying a Cisco PGW 2200 Softswitch Node Object

Use the following procedure to deploy a Cisco PGW 2200 Softswitch node object:

Step 1 Open the Map Viewer.

Step 2 In the left pane, right-click the MGC-Node-View icon.

Step 3 Choose Deployment > Deploy MGC Node.

The Deployment Template opens.

Step 4 Enter the name for the Cisco PGW 2200 Softswitch node (no spaces). Click Forward.

A screen displays summarizing the deployment you have created and allows you to commit or reject the deployment.

Step 5 Click Finish.

You are informed if the deployment was successful, and a Cisco PGW 2200 Softswitch node icon displays in the right pane of the Map Viewer window.

Step 6 Deploy the devices in the node as described in the "Deploying Network Devices" section.

Deploying Network Devices

Use the following procedure to deploy a Cisco PGW 2200 Softswitch host, ITP-L, LAN Switch, HSI server, or BAMS:

Step 1 Open the Map Viewer.

Step 2 In the left pane, expand the MGC-Node-View icon and click to select the desired Cisco PGW 2200 Softswitch node.

Note Although you can alternatively begin deployment from the device-specific view, starting from the appropriate node avoids having to specify the node relationship in the deployment template.

Step 3 Right-click the Cisco PGW 2200 Softswitch node icon and choose Deployment > Deploy MGC Node Component.

The Deployment Wizard Templates window opens listing these template types:

•BAMS

•2900XL Switch

•Catalyst 5500 Switch

•Catalyst 6509 Switch

Note Although the Cisco Catalyst switches listed above can be deployed using the Deploy MGC Node Component Wizard, when deployed they do not appear as children of the node.

•Cisco HSI Host

•Cisco PGW 2200 Softswitch Host

•Cisco PGW 2200 Softswitch Node

•Cisco ITP-L

•Integrated ITP-L

•Integrated ITP-L for Coresident EMs

Note You cannot deploy an ITP-L or integrated ITP-L in a node that is under a farm object.

Step 4 Select the desired device type, and click Forward.

The Deployment Wizard Object Parameters window opens.

Step 5 Enter device data. See Table 5-1 for descriptions of the fields.

Step 6 Click Forward.

The Deployment Wizard Views window opens.

Step 7 Click Select.

The Object Selector displays.

Step 8 Click the + (shown in Figure 5-2) to show the physical site(s) in the Physical View.

Figure 5-2 Expanding the Physical Site View

Step 9 Select the physical site for the current node, and click Apply.

Step 10 Click Finish.

An icon for the new device displays in the right pane of the Map Viewer. Cisco MNM begins discovering the device, as shown by the crosshatching of the object icon, and the discovering status indicator attached to it. Here is an example:

Figure 5-3 Device in Discovering State

For a Cisco PGW 2200 Softswitch host, ITP-L, or LAN Switch, the device icon also displays in the left pane in the MGC-Node-View as a child of the current Cisco PGW 2200 Softswitch node. If the Cisco BAMS is configured to send call detail records (CDRs) to the Cisco PGW 2200 Softswitch host, and is actively polling CDRs, the BAMS icon also displays as a child of the node.

When discovery is complete, Cisco MNM sends a "Discovery is now complete" alarm that can be viewed in the Event Manager.

See the "About the Discovery Process" section for details on what occurs during discovery.

Note•The icon for the new object also displays in the Physical View and the device-specific view for its device type.

•For information on troubleshooting deployment errors, see Appendix C, "Troubleshooting Cisco MNM," "Solving Deployment and Discovery Errors" section on page C-5.

About the Discovery Process

After you deploy a device, Cisco MNM contacts the device and discovers information about its configuration. For example, when you deploy a Cisco ITP-L, Cisco MNM discovers any Ethernet and TDM (DS1) interfaces and their IP addresses. When you deploy a Cisco LAN Switch, Cisco MNM discovers interfaces, ports, and modules. When you deploy the Cisco PGW 2200 Softswitch host, Cisco MNM discovers the system components, as well as signaling, trunking, and dial plan components. Figure 5-4 shows how the Cisco PGW 2200 Softswitch host appears in the Map Viewer after discovery.

Figure 5-4 Map Viewer Display of the Cisco PGW 2200 Softswitch Host After Discovery

The various subcomponent discovery mechanisms are described in the following sections.

Note After initial deployment, Cisco MNM automatically rediscovers each device at a predefined interval and keeps track of the time that each device was last discovered. The default interval for automatic rediscovery is every 6 hours. When the specified interval has elapsed, Cisco MNM automatically rediscovers the device. See the "Synchronizing the Cisco MNM with Device Changes" section for details.

Discovery of Cisco PGW 2200 Softswitch Host, Cisco HSI Server, and Cisco BAMS Components

The Cisco PGW 2200 Softswitch host, Cisco HSI server, and Cisco BAMS discovery mechanism processes the ifTable of the device and deploys an object to represent each supported interface. Cisco BAMS also uses the CIAgent system component discovery mechanism. In addition, an object representing each (non-loopback) IP address is deployed as a child of its corresponding interface as shown in Figure 5-5.

Figure 5-5 Cisco PGW 2200 Softswitch Host, Cisco HSI Server, and Cisco BAMS Discovery

For a Cisco BAMS to be deployed into the correct node, you must perform the following actions:

•Configure the Cisco BAMS to collect CDRs for the relevant Cisco PGW 2200 Softswitch host residing in the same node.

For the procedure of configuration, see the section, "Configuring the Cisco MGC for Using BAMS", of the Cisco Billing and Measurements Server User's Guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/bams/3.30/guide/330_ug.html

•Configure the Cisco BAMS to actively poll CDRs from that Cisco PGW 2200 Softswitch host (set the "activate" flag to "1" in the Cisco BAMS to start the process).

For more information on Cisco BAMS configuration, See the section, "Cisco BAMS Server Configuration", of the Cisco Media Gateway Controller Software Release 9 Provisioning Guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/provisioning/guide/prvgde.html

For more information on Cisco BAMS parameter definitions and values, see the Cisco Billing and Measurements Server User's Guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/bams/3.30/guide/330_ug.html

•Add the following line to the /etc/inet/hosts file:

<IP Address> <hostname> 

This action associates the IP address of the Cisco PGW 2200 Softswitch host with the Cisco PGW 2200 Softswitch host name.

Then you can use the command ping hostname to see if the device is reachable.

When you deploy the configuration, the Cisco BAMS is then automatically placed in the node containing that host, which is dynamically updated. If the BAMS object does not appear in the node view immediately, rediscover the Cisco BAMS; Otherwise the Cisco MNM will do a rediscovery at a predefined interval. The default interval for an automatic rediscovery is six hours. If you deactivate polling, Cisco MNM removes the BAMS object from the node. When you reactivate polling, it restores the BAMS object to the node.

Note For information on troubleshooting Cisco BAMS discovery problems, see Appendix C, "Troubleshooting Other Issues," "Troubleshooting Other Issues" section on page C-7.

Discovery of System Components

For the Cisco PGW 2200 Softswitch host, Cisco HSI server, and Cisco BAMS, system components are deployed that represent logical components of the UNIX system, as shown in Table 5-2.

.

Each entry in the c2900ModuleTable is modeled as a switch2900XLSlot object. The attribute SNMP:CISCO-C2900-MIB.c2900ModuleIndex serves as an index into the table.

Each entry in the c2900PortTable is modeled as a switch2900XLPort object. In the Cisco MNM object model, it is placed under its dependent slot. The c2900PortTable is indexed by two attributes, the module index and the port index. The module index indicates on which slot the port resides. Module index zero indicates that the ports are dependent on the chassis rather than a slot. The attribute c2900PortIfIndex is used to correlate the c2900PortTable to the ifTable.

Each entry in the vtpVLANTable is modeled as a switch2900XLVLAN. In addition, each interface associated with the VLAN is displayed as a child of its corresponding VLAN. In order to correlate interfaces from the ifTable to their corresponding VLANS in the vtpVLanTable, Cisco MNM uses the description of the ifTable entry, which is of the form:

VLANx

Where x is the index of the corresponding entry in the vtpVlanTable.

The Cisco 2900XL subrack component displays, as shown in Figure 5-6.

Figure 5-6 Cisco 2900XL Chassis Discovery

Discovery of Cisco Catalyst 2900XL Components

Cisco MNM models slots, VLANs, and ports on Cisco Catalyst 2900XL series devices. During auto discovery, Cisco MNM retrieves the tables shown in Table 5-3.

Cisco MNM models ports and modules (slots) on Cisco 2900XL series devices. The Cisco 2900XL has 24 ports built into the chassis. In addition, the Cisco 2900XL has two slots into which different cards can be installed.

Each entry in the c2900ModuleTable is modeled as a switch2900XLSlot object. The attribute SNMP:CISCO-C2900-MIB.c2900ModuleIndex serves as an index into the table.

Each entry in the c2900PortTable is modeled as a switch2900XLPort object. In the Cisco MNM object model, it is placed under its dependent slot. The c2900PortTable is indexed by two attributes, the module index and the port index. The module index indicates on which slot the port resides. Module index zero indicates that the ports are dependent on the chassis rather than a slot. The attribute c2900PortIfIndex is used to correlate the c2900PortTable to the ifTable.

Each entry in the vtpVLANTable is modeled as a switch2900XLVLAN. In addition, each interface associated with the VLAN is displayed as a child of its corresponding VLAN. In order to correlate interfaces from the ifTable to their corresponding VLANS in the vtpVLanTable, Cisco MNM uses the description of the ifTable entry, which is of the form:

VLANx

Where x is the index of the corresponding entry in the vtpVlanTable.

The Cisco 2900XL subrack component displays, as shown in Figure 5-7.

Figure 5-7 Cisco 2900XL Chassis Discovery

Discovery of Cisco Catalyst 5500 and 6509 Components

Cisco MNM models slots, VLANs, and ports on Cisco Catalyst 5500 and 6509 (similar to 5500) series devices. During auto discovery, Cisco MNM retrieves the tables shown in Table 5-4.

Each entry in the moduleTable is modeled as a switch5500Slot object, and every entry in the portTable is modeled as a switch5500Port object. To correlate the information, the attribute portModuleIndex defines the slot on which the port is located, and the portIfIndex is used to correlate the portTable to its corresponding interface in the ifTable.

Each entry in the vlanTable is modeled as a switch5500VLAN object. The attribute vlanIfIndex associates each element in the VLAN table to its corresponding interface in the ifTable. The associated interface is shown as a child of its corresponding VLAN.

The SC0 and SL0 interfaces are modeled directly under the chassis object. In the MIB, one interface has a valid IP address while the other has an IP address of 0.0.0.0. While both interfaces are modeled, only the valid IP is shown.

The Catalyst 5500 subrack component is shown in Figure 5-8.

Figure 5-8 Catalyst 5500 Chassis Discovery

Keeping the Cisco MNM Network Model Up to Date

Through periodic rediscovery of the components of each deployed device, Cisco MNM ensures that its database and the Cisco MNM network model are synchronized with the underlying network elements. The default interval at which automatic rediscovery occurs is every 6 hours, but you can change the interval, and you can manually invoke rediscovery when needed. These tasks are described in the "Synchronizing the Cisco MNM with Device Changes" section.

If basic account information about a device (such as its password) changes, you can modify the information in the device Accounts dialog box. If the device is no longer in the network, you can delete it. This is described in the "Modifying or Deleting Deployed Objects" section

SNMP Traps for Configuration Changes

All relevant management data in the Cisco MNM database is automatically updated on receipt of a modification trap from the various network elements in the Cisco PGW 2200 Softswitch node.

The traps in Table 5-5 are used to signal changes in the network elements.

When Cisco MNM receives a POM:DynamicReconfiguration trap from the active Cisco PGW 2200 Softswitch host, it resynchronizes its view of the connectivity network with that of the device.

Synchronizing the Cisco MNM with Device Changes

You can change the interval at which Cisco MNM checks deployed devices for any changes to their components. You can also rediscover a device immediately when needed.

Auto-discovery frequency applies to all devices of the same type.

For SSH-enabled components (defined as the Security Policy at deployment or in the Accounts dialog box), Discovery uses SSH.

To Change the Automatic Rediscovery Interval

Use the following procedure to change the frequency of automatic rediscovery for a particular device type:

Step 1 In the Map Viewer, right-click the desired object, and choose States.

The States dialog box opens.

Step 2 On the Polling tab, change the frequency for Auto-Discovery. The default is every 6 hours.

Note Setting very frequent discovery can place a heavy demand on system resources.

Step 3 Click the Save tool or choose File > Save.

Step 4 Close the dialog box.

When the device is rediscovered, if the Event Browser is open, it displays the message, "Discovery is now complete". With each new discovery, any earlier discovery messages are cleared; only the most recent discovery message displays.

To Manually Rediscover a Device

Use the following procedure to rediscover a device on demand:

Step 1 In the Map Viewer, select the object, and right-click.

Step 2 Choose States. The States dialog box opens.

Step 3 On the States tab, click Rediscover. You are asked if you want to rediscover the device.

Step 4 Click Yes. Cisco MNM rediscovers the device. During discovery, Current State is "discovering." When the discovery is complete, Current State changes to Active (for the Cisco HSI server, Cisco BAMS, and Cisco PGW 2200 Softswitch host) or Normal (for the Cisco ITP-L and LAN Switch).

Note When discovery completes, the message "Discovery is now complete" displays. Earlier discovery messages are cleared; only the most recent discovery message displays.

Step 5 Close the dialog box.

Modifying or Deleting Deployed Objects

Modify a deployed object when either of the following is changed:

•The device password

•SNMP community strings

If an object's IP address changes, delete the object, and redeploy it. Also delete a deployed object when the device is removed from the network or when you want to redeploy the object.

Modifying a Deployed Object

You can change device login, password, and SNMP community strings in the Accounts dialog box. Use the following procedure to modify deployment information:

Step 1 In the Map Viewer, right-click the device you want to modify, and choose Accounts.

The Accounts dialog box opens.

Step 2 Modify the information, as needed:

•Use the Accounts tab to change Host Login ID, Login Password, and Host Root Password.

•Use the SNMP tab to change community strings.

Step 3 When you are done, choose File > Save or click the Save tool, and close the dialog box.

The new information is saved. When Cisco MNM rediscovers the object at the next scheduled interval, this information is used to discover the device components.

Note To immediately rediscover the device components, right-click the device, and choose States. On the States tab, click Rediscover. All components of the device are rediscovered.

Deleting a Deployed Object

You can delete a single object or multiple objects if:

•The device has been removed from the network.

•There was something wrong in the seed file, but it did not cause deployment to fail.

•The device's IP address has changed.

In the last two cases, redeploy the device after deleting the object representing it.

Caution Do not delete the object that represents a component of a device, such as an interface. Instead, let Cisco MNM rediscover the device. In rediscovery, removed components are deleted automatically.

Use the following procedure to delete one or more deployed objects:

Step 1 In the Map Viewer, do one of the following:

•Right-click a single object to delete it.

•To delete multiple objects, Ctrl-click to select objects in different areas of a window, or Shift-click to select a block of objects, and then right-click.

Step 2 Choose Deployment > Delete Objects. The Deployment Wizard Summary window opens with the message "Ready to delete (n) object(s)," where n is the number of objects selected.

Step 3 Click Finish.

The selected object or group of objects is deleted. A message informs you that one or more objects have been deleted from the system.

Exporting Deployment Information to an Inventory or Seed File

You can export deployment information to an inventory or seed file. A seed file includes information similar to that shown in Example 5-1. An inventory file covers only the Cisco PGW 2200 Softswitch node devices but includes detailed system information obtained during discovery. For each device, it captures the current

•IP address

•Hardware type

•Operating system, host version, and software versions

Note Inventory information for the BAMS is included if the BAMS has been configured to collect call detail records for a Cisco PGW 2200 Softswitch host.

An inventory file might be used by software that tracks inventory data about the network. A seed file can be used to capture a snapshot of your network deployment at a particular time, to be used for later deployment or to replicate a deployed network.

An example of an inventory file is shown here:

Example 5-3 Example of Exported Inventory File

MGC (Name = MGC-1) { 

HOST (Name = Host-1, SysName = nssuvsc21, IpAddr = 10.10.10.71, HardwareModel = 
SUNW,UltraSPARC-IIi-Engine, HostId = 80d1bd49, HostVersion = 9.0(0.16), HostVendor = 
"Cisco Systems, Inc.", Switch_Type = Switched-VSC, OS_Version = Generic_105181-23, 
OS_Release = 5.6) 

2600 (Name = SLT, SysName = n2600a.cisco.com, IpAddr = 10.10.10.72, ChassisId = 
"JAB032101S4 (3076808945)", ChassisType = 89, ChassisVersion = 0x202, ROM_Sys_Version 
= "Cisco Internetwork Operating System Software  IOS (tm) C2600 Software 
(C2600-IPSS7-M), Version 12.1(3)T,  RELEASE SOFTWARE (fc1) Copyright (c) 1986-2000 by 
cisco Systems, Inc. Compiled Wed 19-Jul-00 19:49 by ccai", ROM_Monitor_Version = " 
System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1) Copyright (c) 1999 by 
cisco Systems, Inc. TAC:Home:SW:IOS:Specials for info ", Sys_Config_Name = 
flash:c2600-ipss7-mz.121-3.T.bin) 

5500 (Name = Switch-1, SysName = nssu-cat5500-1, IpAddr = 10.10.10.74, 
Chassis_Serial_No. = 9999999, ChassisModel = WS-C5509, ChassisType = 14, 
Sys_Booted_Image = bootflash:cat5000-sup3.5-5-4b.bin) 

}

Table 5-6 shows the attributes exported for the various device types.

Use the following procedure to export deployment information to an inventory or a seed file:

Step 1 From the Map Viewer screen, click the MGC-Node-View icon.

Step 2 Right-click, and choose Deployment > Deploy Network Seed File.

The Deploy Network dialog box opens.

Step 3 Click the Advanced tab.

Step 4 In the Export section for Filename, enter a name for the file to be created.

Step 5 Do one of the following:

•To export the information as an inventory file, click Export Inventory.

•To export the information as a seed file, click Export Seed File.

A message prompting you for confirmation displays.

Step 6 Click Yes.

A message confirming the file creation displays.

Note By default, the file is saved in the <CEMF Root>/bin/.mgcControllerx.sysmgr folder. Specify the path if you want to save it to a different location.

Step 7 Click Close.

Step 8 Close the Deploy Network dialog box.