Deploying and Discovering Objects

The first step toward managing a router is to deploy or predeploy the physical objects that you want to manage. Deploying a physical object creates a representative object in Cisco EMF and, as a result, makes the EM aware of the physical object's presence.

If all or most of your chassis objects are physically present and if you have a large amount of objects to deploy, you might want to automate these processes by using auto discovery. For example, if an EM is installed into an existing network of routers, auto discovery can dramatically reduce the amount of operator input required. If you only want to deploy a few objects or if many of your objects are not yet physically present, you might want to manually deploy or predeploy. Predeployment is used when a physical object is not yet connected to the network but is anticipated to be in the future. Predeploying objects allows you to create representative objects within the EM and partially configure them, saving time later.

Once objects deploy, you must commission (discover) them in order to manage them through the EM.

The following sections make up this chapter:

Automatic Discovery

Objects which are physically present in the network can be automatically discovered on the chassis and subchassis levels. You can choose to use the Cisco EMF Auto Discovery tool to detect devices based on IP and/or SNMP data. This capability applies to the chassis only. Similarly, modules automatically discover as a part of subchassis discovery and regular heartbeat polling.

The following sections describes each of these features in detail:

Automatically Discovering Chassis

Auto discovery is the application that discovers existing Cisco chassis, saving time and effort. Chassis automatic discovery requires user specification of IP and SNMP data, establishing a range of network elements that the tool then polls for.

The auto discovery window opens from the Viewer or Discovery icons on the Launchpad.

Note For further information regarding the Cisco EMF Launchpad, see the Cisco Element Management Framework User Guide Release 3.2 at the following URL:
http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/products_user_guide_book0918 6a0 0800ffd02.html

The Auto discovery application has three mechanisms for discovering chassis:

IP—ICMP pings are used to find chassis in a given IP address range. This finds which IP device exists, but does not discover what kind of device it is.
SNMP—SNMP get requests are used to find chassis in a given IP address range. Several SNMP community strings can be used so that equipment with different community strings can be discovered in the same discovery session. The SNMP information returned by devices is used to work out what kind of device has been found.
IP and SNMP—ICMP pings are used to find chassis and then SNMP requests are used to interrogate the chassis to find out what kind of chassis they are. This is the default mechanism.

Auto discovery can discover chassis on more than one subnetwork using multi-hop discovery. It can be scheduled to run at preset times. An option is also available to specify the physical location under which discovered objects are created.

Note For information on how to set the auto discovery schedule, see the Cisco Element Management Framework Installation and Administration Guide Release 3.2.

After the chassis is detected, an object representing the chassis creates and is placed under the site from which auto discovery was launched. A map of the chassis also creates, as shown in Figure 3-31.

If you wish to auto-discover a chassis that can be managed by the EM, then the Physical Path option must be enabled and an appropriate Physical Path (terminated with a generic object) must be selected. Providing the above is done, the auto discovery application will create a chassis below the selected Physical Path for each chassis discovered.

Following chassis auto-discovery, you must manually enter the appropriate IOS password and commission the chassis to fully manage the device, including enabling automatic module discovery. For information, see the "Managing Username and Passwords" section and the "Commissioning Chassis" section or on page 5-9.

Automatically Discovering Modules

Assuming the chassis, of which the module is part of, is commissioned and in a managed state (e.g., not the decommissioned or lost comms state), heartbeat polling detects modules (within five minutes' time) and alerts the EM to their presence. When the EM detects the presence of the new module, the chassis enters subchassis discovery to determine the type of module that was inserted. When the new module discovers, it is added to the appropriate views and automatically commissions. If the module is a port adapter which has interfaces, the interfaces discover during the subchassis discovery process. The commissioning process also determines what state the module should go into, which can be the normal, errored, or mismatched state.

Tip For information on individual states, see the "Object States" section. For more information on managing device, refer to the "Change Management" section.

Auto discovered modules are assigned standardized module naming conventions using an automatic naming scheme provided. Auto-generated module names consist of the slot and subslot numbers appended to the module type (subslot appended only when applicable).

Deployment

Manual deployment consists of three stages as shown in the following figure.

Figure 3-1 Deployment Process Workflow

1. The first deployment stage is to manually deploy a generic object (e.g., Site). A generic object can be looked upon as a container object where you can deploy further objects that represent the chassis, line cards and interfaces contained within the chassis. For further information, see the "Deploying Generic Objects" section.

2. The second deployment stage is at the chassis level. The chassis can be auto discovered or manually deployed. For further information, see the "Automatically Discovering Chassis" section or the "Manually Deploying Chassis" section. You can also predeploy objects (that is, manually predeploy objects before the Cisco hardware arrives on-site). For further information, see the "Deployment" section on the previous page.

3. The third deployment stage is subchassis level discovery. Subchassis discovery involves either chassis commissioning or auto discovery of objects within a managed chassis. For further information, see the "Chassis Commissioning and Subchassis Discovery" section.

Deploying Generic Objects

Some generic objects are technology specific (e.g., IP Device, SNMP Agent, SNMP MIB-2 Agent, SNMP Proxied Agent), while others are not (e.g., region, site, bay). Non-technology specific generic objects can be used to organize the components of your network when deployed beforehand. For example, you may ultimately choose to organize a number of bays within a generic region object, a number of sites within a generic bay object, and a number of chassis within a generic site object. In general you can organize generic objects as you wish. However, in order to support successful deployment of non-generic chassis objects, chassis objects must be deployed directly beneath a generic site object.

Generic object deployment uses the Cisco EMF Deployment Wizard templates. When deploying a generic object, the information you are prompted to provide differs according to the type and number of generic objects you are deploying.

The following table displays a list of generic objects that can be deployed using the generic deployment templates.

Table 3-1 Generic Object Deployment Templates

Object to be Deployed	Deployment Templates Available
Generic	Bay
	IP Device
	Region
	SNMP Agent
	SNMP MIB-2 Agent
	SNMP Proxied Device
	Site

This section provides an example that shows how to deploy a non-technology specific site object.

Note For additional information on deploying generic objects, including deployment from the Class Palette, see the Cisco Element Management Framework User Guide Release 3.2. Additionally, know that the Cisco Shelf object on the Class Palette is not applicable (not valid) to this EM.

To deploy a Generic (Site) object, proceed as follows:

Step 1 Place the cursor over a relevant object to determine the objects you can deploy from. In this example we will deploy a site object from the Physical view.

Step 2 Press (click and hold down) the right mouse button.

Step 3 Choose Deployment > Deploy Generic Objects.

The Deployment Wizard - Templates window appears displaying a list of available generic object deployment profiles. Deployment profiles are templates that prompt you for the appropriate information required to deploy the selected object successfully.

Figure 3-2 Deployment Wizard - Templates Window

Step 4 Select the generic object that you wish to deploy from the list supplied. In this example select the deployment profile for a site object.

Step 5 Click Forward.

The Deployment Wizard - Object Parameters window appears.

Figure 3-3 Deployment Wizard - Object Parameters Window (1 of 2)

Step 6 Enter the number of (Site) objects to deploy.

Step 7 Click Forward.

A second Deployment Wizard - Object Parameters window appears.

Figure 3-4 Deployment Wizard - Object Parameters Window (2 of 2)

Step 8 Enter a (Site) object name. Each object must have a unique name.

Step 9 Click Forward.

One of the following occurs:

If deployment was initiated from a view, then the Deployment Wizard - Views window appears (see the following figure). Proceed to Step 10.
If deployment was initiated from an existing object, then the EM automatically places the object you are currently deploying under the same view as the existing object. The Deployment - Wizard Summary window appears. Skip Step 10 through Step 13, and proceed to Step 14.

Figure 3-5 Deployment Wizard - Views Window

Step 10 Click Select to select a physical view.

The Object Selector window appears.

Figure 3-6 Object Selector

Step 11 Choose the object you want to place the generic object under within the Physical view. Objects which are not available for selection are greyed out. Click on the + sign to expand the view as required.

Step 12 Click Apply.

The Deployment Wizard - Views window re-appears with the selection displayed.

Figure 3-7 Deployment Wizard - Views Window

Step 13 Click Forward.

You are prompted to repeat Steps 8 to 13 if you are deploying more than one generic object.

The Deployment - Wizard Summary window appears. The Summary window provides details of the object you are about to deploy.

Figure 3-8 Deployment Wizard - Summary Window

The number of objects deployed reflects the number of sites entered in Step 6. This entry directly correlates to the number of objects listed in the deployment summary information.

Step 14 Click Finish to deploy the object and close the Summary window if the deployment information is correct. If the information is incorrect, click Cancel to stop deployment and close the Summary window.

The new object(s) deploy accordingly and display in the Map Viewer window.

Deploying Chassis

Chassis objects deploy by either automatic discovery or manual deployment. When manually deploying, you can choose to automatically commission a chassis immediately following deployment or you may choose to simply initiate commissioning activities at a later time.

Regardless of the chassis deployment method used, in order to successfully deploy a chassis object you must deploy the chassis beneath a generic site object. This means that you must deploy a site before deploying a chassis. For instruction on deploying a site object, see the "Deploying Generic Objects" section.

The Deploying Chassis section contains the following areas:

Manually Deploying Chassis Using Quick Start

The chassis manual deployment quick start method allows you to deploy a chassis object, then automatically begin commissioning and subchassis discovery activities on the deployed chassis.

Tip It is recommended that you ping the router you intend to deploy before using the manual deployment Quick Start method to ensure the device is contactable. If the device is not contactable, consider predeploying.

To deploy a chassis using the quick start method, proceed as follows:

Step 1 In the Map Viewer, right-click on the generic site object under which you wish to deploy the chassis, then choose Deployment > Cisco 7000 Series Manager > Chassis.

The Deployment Wizard appears.

Figure 3-9 Deployment Wizard—Templates

You can click Cancel at any point to cancel the deployment.

Step 2 Select the appropriate chassis type Quick Start option, then click Forward.

The Deployment Wizard - Object Parameters window appears.

Figure 3-10 Deployment Wizard—Object Parameters (1 of 2)

Step 3 Enter the number of chassis objects you want to deploy.

Step 4 Click Forward.

A second Deployment Wizard - Object Parameters window appears.

Figure 3-11 Deployment Wizard—Object Parameters (2 of 2)

Step 5 Enter the following information:

Chassis Name—Name (including prefix and suffix) for the chassis you are deploying. This chassis name must be unique within the generic object. A default prefix appears (for example, "Cisco7206VXR") according to the chassis type selected for deployment. You can accept the default prefix or change this prefix, as desired. It is recommended that you modify the "0.0.0.0" suffix with the appropriate IP address of the router.
IP Address—IP address for the chassis you are deploying.
Subnet Mask—Bit mask used to identify which bits in the IP address correspond to the network address and subnet portions of the address.
SNMP V2 Read Community—Community string used to retrieve attributes from the device using the SNMP V2 protocol.
SNMP V2 Write Community—Community string used to set attributes from the device using the SNMP V2 protocol.
SNMP Version—Need description.
User Name—Enter the user name for the device which, when combined with the passwords below, provides additional levels of security for accessing the device. If no user name exists on the device, leave this field blank.
Login Password—Enter the telnet access password which protects the device from access by unauthorized personnel.
Exec Password—Enter the access password for the chassis, enabling you to perform privileged operations on the chassis.

Step 6 Click Forward.

You are prompted to repeat Step 5 if you are deploying more than one chassis.

Deployment summary details appear in the Deployment Wizard - Summary window.

Figure 3-12 Deployment Wizard—Summary

The number of objects deployed is equal to the number of chassis entered in Step 3. This entry directly correlates to the number of objects listed in the deployment summary information.

Step 7 Click Finish to deploy the chassis and close the summary window if the deployment summary information is correct. If the Deployment Summary information is incorrect, click Cancel to stop deployment and close the summary window.

The deployed chassis object(s) appear in the left-hand pane of the Map Viewer beneath the generic object from which deployment was initiated and the corresponding icon(s) appear in the right-hand pane of the Map Viewer.

Commissioning activities start with chassis discovery. If successful, the chassis moves into the appropriate managed state then initiates subchassis discovery which begins to detect the physical objects (that is, modules and interfaces) within the chassis and places them onto the chassis map. Modules and interfaces are automatically named as described in the "Automatically Discovering Modules" section. Following subchassis discovery, all objects enter a specific state. For further information, see the "Object States" section.

Successful commissioning not only discovers the chassis and all the physical objects within the chassis, but also initiates heartbeat polling, which allows alarms to be raised on the chassis and all physical objects within the chassis.

Commissioning automatically starts active management (such as polling) on the chassis and all commissioned objects within the chassis. There is no indicator regarding the success or failure of the quick start commission. To optionally check the outcome of the commission, review the status of the Last Commission field on the Chassis Configuration window. For further information on the Chassis Configuration window, see the "Chassis Configuration" section. The chassis state is an additional indicator of a failed commission. If the state is lost comms or mismatched, the commissioning failed.

Manually Deploying Chassis

As a result of manual deployment, a chassis object creates within the EM. In order to manage the chassis through the EM, you must commission the chassis following deployment. For further information, see the "Commissioning Chassis" section or on page 5-9.

The EM also provides you with the option to deploy a chassis and commission it from the deployment operation (i.e., quick start deployment). All Cisco 7000 Series routers support the quick start feature. For further information, see the "Manually Deploying Chassis Using Quick Start" section.

The following procedure is appropriate for predeployment, where the device deployed is not yet available on the network.

To deploy a chassis, proceed as follows:

Step 1 In the Map Viewer, right-click on the generic site object under which you wish to deploy the chassis, then choose Deployment > Cisco 7000 Series Manager > Chassis.

The Deployment Wizard appears.

Figure 3-13 Deployment Wizard—Templates

You can choose Cancel at any point to cancel the deployment.

Step 2 Select the chassis type you want to deploy, then click Forward.

The Deployment Wizard - Object Parameters window appears.

Selecting a chassis type with "(Quick Start)" beside the name allows you to deploy a chassis object and automatically commission the chassis following deployment. For further information, see the "Manually Deploying Chassis Using Quick Start" section.

Figure 3-14 Deployment Wizard - Object Parameters (1 of 2)

Step 3 Enter the number of chassis objects you want to deploy.

Step 4 Click Forward.

A second Deployment Wizard - Object Parameters window appears.

Figure 3-15 Deployment Wizard - Object Parameters (2 of 2)

Step 5 Enter the following information:

Chassis Name—Name (including prefix and suffix) for the chassis you are deploying. This chassis name must be unique within the generic object. A default prefix appears (for example, "Cisco7206VXR") according to the chassis type selected for deployment. You can accept the default prefix or change this prefix, as desired. It is recommended that you modify the "0.0.0.0" suffix with the appropriate IP address of the router.
IP Address—IP address for the chassis you are deploying.
Subnet Mask—Bit mask used to identify which bits in the IP address correspond to the network address and subnet portions of the address.
SNMP V2 Read Community—Community string used to retrieve attributes from the device using the SNMP V2 protocol.
SNMP V2 Write Community—Community string used to set attributes from the device using the SNMP V2 protocol.
SNMP Version—Need description.

Step 6 Click Forward.

If you are deploying more than one chassis, you are prompted to repeat Steps 5 and 6.

The Deployment Summary details appear in the Deployment Summary window.

Figure 3-16 Deployment Wizard—Summary

The number of objects deployed is equal to the number of chassis entered in Step 3. This entry directly correlates to the number of objects listed in the deployment summary information.

Step 7 Click Finish to deploy the chassis and close the Summary window if the deployment summary information is correct. If the Deployment Summary information is incorrect, click Cancel to stop deployment and close the Summary window.

At any time following successful chassis deployment, you may initiate subchassis discovery by commissioning the chassis. Until you do so, the chassis remains in an unmanaged state (e.g., decommissioned). For further information, see the "Chassis Commissioning and Subchassis Discovery" section or the "Commissioning a Chassis" section.

Deploying ATM Connections

This section describes how to deploy ATM connection objects (such as VCLs and SVCs.) In order to deploy ATM connections, subchassis discovery on the parenting chassis object must be complete. Completion of subchassis discovery is necessary because you must deploy connections beneath an interface object.

A VCL is a permanent logical connection configured between two ATM interfaces that, typically, serve as conduits through which the connection passes. VCLs save processing overhead that is associated with establishing a channel when a virtual channel must exist all the time. You can(1) deploy a VCL (which creates the object within the EM), (2) apply a QoS profile (ATM traffic descriptor) to the VCL, and then (3) create the connection on the device. Deploying and creating a VCL using the EM creates a cross-connection within one device.

In lieu of deploying VCLs which already exist on the device, you may simply upload them to the EM. ATM connection profiles on the device also upload to the EM during this action. For detailed instructions on uploading ATM connections and profiles from the device, see the "Uploading Existing ATM Connections and ATM QoS Profiles" section.

Following deployment, ATM connection objects display within the Component Managed view.

Deploying SVCs

To deploy an SVC, proceed as follows:

Step 1 Right-click on the appropriate site or chassis object you want to deploy the connection under, then choose Deployment > Cisco 7000 Series Manager > Connection > SVC.

The Deployment Wizard appears.

Figure 3-17 Deployment Wizard—Templates

You can chose Cancel at any point to Cancel the deployment.

Step 2 Select the SVC type you want to deploy, then click Forward.

The Deployment Wizard - Object Parameters window appears. If you chose to deploy an SVC that will be named by the system (contains "Auto Named" in the template selection), Figure 3-18 displays. Figure 3-19 displays if you chose to name the SVC you are deploying (contains "User Named" in the template selection.)

Figure 3-18 Deployment Wizard - Object Parameters (1 of 2 - Auto Named)

Figure 3-19 Deployment Wizard - Object Parameters (1 of 2 - User Named)

Step 3 Enter the following information, depending upon the type of SVC you are deploying:

Number of Cisco SVC objects—Enter the number of SVC objects you want to create. Valid entries are 1 to 100 for an Auto Named SVC or 1 to 10 for a User Named SVC.
Name Suffix Start Number—Only applicable for an Auto Named SVC. If you are creating more than one SVC, enter a start number for inclusion in the SVC name. For example, if you are creating three SVC objects and you specify a start number of 1, the SVC numbers are 1, 2, and 3.

Note If, in the future, you deploy more SVCs on an interface in which other SVCs already exist, remember to not duplicate the starting number. For example, if three SVCs exist on an interface and their numbers are 1, 2, and 3 and you now want to deploy six more, begin your SVC object number at 4, where you left off previously. The six new SVC numbers will be 4, 5, 6, 7, 8, and 9.

Step 4 Click Forward to proceed.

A second Deployment Wizard - Object Parameters window displays. Figure 3-20 displays if you are deploying an Auto Named SVC. Refer to Figure 3-21 if you are deploying a User Named SVC.

Figure 3-20 Deployment Wizard - Object Parameters (2 of 2 - Auto Named)

Figure 3-21 Deployment Wizard - Object Parameters (2 of 2 - User Named)

Step 5 Enter the following information, depending upon the type of SVC you are deploying:

SVC Name—Only applicable for a User Named SVC. Enter a unique name (prefix and suffix) for the SVC (CiscoSVC by default.) If you are creating more than one SVC, enter a start number for inclusion in the SVC name. For example, if you are creating three SVC objects and you specify a start number of 1, the SVC numbers are 1, 2, and 3.

Profile Name—Enter the name of an ATM QoS configuration profile as necessary to automatically configure the connection upon deployment.
Destination NSAP Address—
Create connection—Enter 1 (yes) to create or 0 (no) to not create the connection on the device upon deployment.

Step 6 Click Forward to proceed.

The Deployment Wizard - Views window displays.

Figure 3-22 Deployment Wizard - Views

Step 7 Click Select beside either field. The first Component Managed field is the source endpoint of the connection and the second is the destination endpoint.

The Object Selector Window displays.

Figure 3-23 Deployment Wizard—Object Selector

Step 8 Choose the object under which you want to place the SVC within the Component Managed view. Objects not available for selection are greyed out. Click on the + sign to expand the view as required.

Step 9 Once you highlight your selection, click Apply.

The Deployment Wizard - Views window re-appears with the name of the port object in the corresponding view field. By default, your initial selection displays in both the Component Managed fields regardless of from which field you initiate the selection. The ATM interface cross-connection, however, must use different object selections.

Step 10 Repeat Steps 8 through 10 for the other end of the connection.

The Deployment Wizard - Views window re-appears again with the name of the port objects in the corresponding view fields. By default, your selections display in the appropriate Component Managed field. The top field represents the source port selection and the bottom field represents the destination port selection. These object selections, however, must be different.

Step 11 Click Forward to proceed.

The Deployment - Wizard Summary window appears. The Summary window provides details of the object(s) you are about to deploy.

Figure 3-24 Deployment Wizard - Summary

Step 12 Click Finish to deploy the SVC if the deployment information is correct. If the information is incorrect, click Cancel to stop deployment and close the Summary window.

The Deployment Wizard - Results window displays indicating the success or failure of the deployment. The new SVC object(s) deploy accordingly and display in the Component Managed view on the Map Viewer window. Depending on the options selected, deployment occurs as follows:

Configuration profile setting:

If a configuration profile name was assigned to the connection during deployment, the connect configuration QoS matches that of the profile identified.
If the Profile Name field was left blank during deployment, you must configure the ATM QoS parameters by applying a profile following deployment using the "Applying ATM QoS Profiles to Connections" section.

Creating the connection on the device:

If the create connection option was selected, the connection automatically creates within the EM and on the device immediately following deployment.
If you chose to connect the SVC object later, the connection does not create on the device, only within the EM, and you must activate the connection at a future time.

Step 13 Click Finish to close the Deployment Wizard window.

Deploying VCLs

You can deploy a VCL under a main interface or a subinterface.

To deploy a VCL, proceed as follows:

Step 1 Right-click on the appropriate site or chassis object you want to deploy the connection under, then choose Deployment > Cisco 7000 Series Manager > Connection > VCL.

The Deployment Wizard appears.

Figure 3-25 Deployment Wizard—Templates

You can chose Cancel at any point to Cancel the deployment.

Step 2 Select the VCL type you want to deploy, then click Forward.

The Deployment Wizard - Object Parameters window appears. If you chose to deploy a VCL that will be named by the system (contains "Auto Named" in the template selection), Figure 3-26 displays. Figure 3-27 displays if you chose to name the VCL you are deploying (contains "User Named" in the template selection.)

Figure 3-26 Deployment Wizard—Object Parameters (1 of 2 - Auto Named)

Figure 3-27 Deployment Wizard—Object Parameters (1 of 2 - User Named)

Step 3 Enter the following information, depending on the type of VCL you are deploying:

Number of CiscoVCL objects—Only applicable for an Auto Named VCL. Enter the number of VCL objects you want to create (valid entries range between 1 and 100.)
Name Suffix Start Number—If you are creating more than one VCL, enter a start number for inclusion in the VCL name. For example, if you are creating three VCL objects and you specify a start number of 1, the VCL numbers are 1, 2, and 3.

Note If, in the future, you deploy more VCLs on an interface in which other VCLs already exist, remember to not duplicate the starting number. For example, if three VCLs exist on an interface and their numbers are 1, 2, and 3 and you now want to deploy six more, begin your VCL object number at 4, where you left off previously. The six new VCL numbers will be 4, 5, 6, 7, 8, and 9.

Profile Name—Enter the name of an ATM QoS configuration profile as necessary to automatically configure the connection upon deployment.
Subscriber ID—Enter the subscriber ID if you choose to set one (you can leave undefined.)
Sub Interface Number—Only applicable for a User Named VCL.

Step 4 If desired, enter the source VPI and VCI values as follows:

VPI—Enter the virtual path identifier for the source port of the connection.
VCI—Enter the virtual channel identifier for the source port of the connection.

Step 5 Enter 1 in the Auto Allocate Source field if you want to enable the source auto allocation feature. Enabling the auto allocation feature automatically assigns VPI and VCI values upon deployment based on the availability within the device cross-connect table.

Note If you have chosen to disable the source auto allocation feature (by entering 0 in the corresponding field), you must enter VPI and VCI values in the corresponding fields. A VPI value of 0 and VCI values of 0 through 31 are reserved for ATM automatic allocation.

Step 6 Create connection—Enter 1 (yes) to create or 0 (no) to not create the connection on the device upon deployment.

Step 7 Click Forward to proceed.

The Deployment Wizard - Views window displays.

Figure 3-28 Deployment Wizard - Views

Step 8 Click Select.

The Object Selector Window appears.

Figure 3-29 Deployment Wizard—Object Selector

Step 9 Choose the object you want to place the VCL under within the Component Managed view. Objects which are not available for selection are greyed out. Click on the + sign to expand the view as required.

Step 10 Once you highlight your selection, click Apply.

The Deployment Wizard - Views window re-appears with the name of the port object in the corresponding view field.

Step 11 Click Forward to proceed.

The Deployment - Wizard Summary window appears. The Summary window provides details of the object(s) you are about to deploy.

Figure 3-30 Deployment Wizard - Summary

Step 12 Click Finish to deploy the VCL if the deployment information is correct. If the information is incorrect, click Cancel to stop deployment and close the Summary window.

The Deployment Wizard - Results window displays indicating the success or failure of the deployment. The new VCL object(s) deploy accordingly and display in the Component Managed view on the Map Viewer window. Depending on the options selected, deployment occurs as follows:

Configuration profile setting:

If a configuration profile name was assigned to the connection during deployment, the connect configuration QoS matches that of the profile identified.
If the Profile Name field was left blank during deployment, you must configure the ATM QoS parameters by applying a profile following deployment using the "Applying ATM QoS Profiles to Connections" section.

Creating the connection on the device:

If the create connection option was selected, the connection automatically creates within the EM and on the device immediately following deployment.
If you chose to connect the VCL object later, the connection does not create on the device, only within the EM, and you must activate the connection at a future time.

Step 13 Click Finish to close the Deployment Wizard window.

Commissioning

The Commissioning section covers the following areas:

Chassis Commissioning and Subchassis Discovery

After you deploy a chassis, the next step in creating a manageable system is to commission the chassis (which begins the process of subchassis discovery). The following figure shows a Cisco 7206VXR chassis map before subchassis discovery. Subchassis discovery identifies all physical objects (that is, modules and interfaces) within the chassis and places them into the chassis map.

Figure 3-31 Before Subchassis Discovery

:58028.bmp

Line cards and interfaces located within the chassis are discovered at this time. Commissioning not only discovers the chassis and all the physical objects within the chassis, but also initiates heartbeat polling, which allows alarms to be raised on the chassis and all physical objects within the chassis. Additionally, ATM connections upload from the device to the EM.

Because the chassis is the highest-level object, all objects under the chassis are commissioned as well when you commission the chassis. One level down, if you commission a module interface, you commission all physical objects underneath that level. If you commission a port adapter, you commission all interfaces on that port adapter, and so on. However, note that before you can commission any physical object within a chassis, the chassis object itself must be commissioned. This means that you must run subchassis discovery by commissioning the chassis before you can decommission or recommission any individual objects under the chassis. If you do not want to actively manage all objects within the chassis, you can decommission the objects you are not ready to manage.

For information on decommissioning subchassis objects, see the "Decommissioning Modules" section or page 5-32 and the "Decommissioning an Interface" section.

Commissioning Chassis

When you successfully commission a chassis, subchassis discovery begins automatically. Subchassis discovery discovers and commissions all objects within the chassis. Commissioning automatically starts active management (such as polling) on the chassis and all commissioned objects within the chassis.

If commissioning is unsuccessful, the chassis moves into the mismatched or lost comms state. To resolve the errors which results in these states, see the "Object States" section.

To commission a chassis, proceed as follows:

Step 1 Right-click (on a relevant object icon in the Map Viewer window or from an object pick list) and choose Cisco 7000 Series Manager > Configuration > (Chassis >) Configuration. For information on which objects allow you to launch the Chassis Configuration window, see "EM Windows".

The Chassis Configuration window appears displaying the Configuration tab.

Figure 3-32 Chassis Configuration Window

Step 2 Select the chassis you want to commission from the Chassis list box at left of the window.

Tip If commissioning several chassis at once, use the Shift or Ctrl key to select multiple chassis from the Chassis list box. To make a contiguous selection, select an initial item, press the Shift key, then select the last item. To make a non-contiguous selection, select an initial item, press the Ctrl key, then select other items as necessary.

Step 3 Ensure the chassis has proper configuration. For information on chassis configuration attributes, see the "Chassis Configuration" section.

Step 4 Click Commission (located in the Actions area).

The chassis commissions and all objects contained within commission through subchassis discovery. As subchassis objects discover, they display in the left-hand pane of the Map Viewer window and populate the chassis map in right-hand pane of the Map Viewer. An Action Report window appears displaying the outcome of the chassis commission. Additionally, status information displays in the Commission Status area of the Chassis Configuration window reiterating the outcome of the commissioning action as either Succeeded or Failed.

When viewing the Chassis Configuration window in future instances, the Commission Status area displays the result of the last commission action, either Succeeded or Failed.

Step 5 Click Close to close the Action Report window.

Step 6 Choose File > Close to close the Chassis Configuration window.

The following figure shows a Cisco 7206VXR chassis map in the Physical view after subchassis discovery. Modules and interfaces are automatically discovered within the chassis and enter the appropriate post-commissioning state. For details about object states, see the "Object States" section.

Figure 3-33 After Subchassis Discovery

:58027.bmp

After commissioning a chassis you can configure and manage the chassis objects. For further details, see the "Chassis Configuration" section.

Decommissioning Chassis

Decommissioning a chassis decommissions all objects within the chassis, and active management (such as polling) stops on the chassis and on all objects within the chassis.

Decommissioning a managed chassis object is necessary in order to delete a managed chassis object from the EM. Should you attempt to delete a managed chassis object from the EM without first decommissioning it, an error displays indicating that the action cannot complete successfully.

To decommission a chassis, proceed as follows:

The Chassis Configuration window appears displaying the Configuration tab (see Figure 3-32).

Step 2 Select the chassis you want to decommission in the Chassis list box on the left-hand side of the window.

Step 3 Click Decommission (located in the Actions area).

The chassis and all objects contained within are decommissioned. Decommissioned objects remain in the left-hand pane of the Map Viewer window and appear grayed out in the chassis map which displays in the right-hand pane of the Map Viewer. An Action Report window appears displaying the outcome of the chassis decommissioning. If decommissioning is successful, the state of the chassis and subchassis objects change to decommissioned.

Step 4 Click Close to close the Action Report window.

Step 5 Choose File > Close to close the Chassis Configuration window.

Module Commissioning and Discovery

The Module Commissioning and Discovery section covers the following areas:

Commissioning Modules

As previously described, there are several types of modules the EM supports, including line cards, processors, and supporting modules (e.g., power supplies). Commissioning modules discovers and commissions the module and all the objects within the module when applicable, and begins heartbeat polling. Overall, successful commissioning places the module in a manageable state (by the EM).

The following lists the activities which occur when commissioning line cards and processor modules.

Commissioning a module initiates the following activities:

All interfaces on the line card also commission
Heartbeat polling begins on the line card and interfaces
The line card and active interfaces are placed in the normal state
Status data becomes available on the line card and interfaces

Commissioning any supporting module initiates the following activities:

Heartbeat polling begins on the object
The state changes to normal
Status data becomes available

To commission a module, proceed as follows:

Step 1 Right-click (on a relevant object icon in the Map Viewer window or from an object pick list) and choose Cisco 7000 Series Manager > Configuration > (Module >) Configuration. For information on which objects allow you to launch the Module Configuration window, see "EM Windows".

The Module Configuration window appears.

Figure 3-34 Module Configuration Window

Step 2 Select a chassis from the Chassis list box at left of the window, then select a module from the Module list box.

Step 3 Ensure the module has proper configuration. For information on module configuration attributes, see the "Module Configuration" section.

Step 4 Click Commission (located in the Actions area).

The module and all objects it contains commission through discovery. An Action Report window appears displaying the outcome of the module commission. Additionally, status information displays in the Commission Status area of the Module Configuration window reiterating the outcome of the commissioning action as either Succeeded or Failed.

When viewing the Module Configuration window in future instances, the Commission Status area displays the result of the last commission action, either Succeeded or Failed.

Step 5 Click Close to close the Action Report window.

Step 6 Choose File > Close to close the Module Configuration window.

Decommissioning Modules

Decommissioning modules also decommissions all objects beneath the card. As a part of decommissioning, heartbeat polling, status gathering, and performance monitoring terminates. These activities put the module in a state that is unmanageable from the EM.

The following lists the activities which occur when decommissioning line cards and supporting modules.

Decommissioning a module initiates the following activities:

All interfaces and ATM connections on the line card are also decommissioned
Heartbeat polling stops on the line card and interfaces
The line card, interfaces, and ATM connections are placed in the decommissioned state
Status data is no longer available on the line card and interfaces
Performance polling stops on the line card and interfaces (if enabled)

Decommissioning any supporting module initiates the following activities:

Heartbeat polling stops on the object
The state changes to decommissioned
Status data is no longer available
Performance polling stops on the module (if enabled)

It is recommended that you decommission a module prior to physically removing it from a managed chassis. Decommissioning a module before physically removing it prevents alarms.

To decommission a module, proceed as follows:

The Module Configuration window appears (see Figure 3-34).

Step 2 Select a chassis from the Chassis list box at left of the window, then select a module from the Module list box.

Step 3 Click Decommission to decommission the selected module.

An Action Report window appears describing the outcome of the decommissioning action.

The module and all objects contained within are decommissioned. Decommissioned objects remain in the left-hand pane of the Map Viewer window and appear grayed out in the chassis map which displays in the right-hand pane of the Map Viewer. An Action Report window appears displaying the outcome of the module decommissioning. If decommissioning is successful, the state of the module and objects contained within change to decommissioned.

Step 4 Choose Close to close the Action Report window.

Step 5 Choose File > Close to close the Module Configuration window.

Table of Contents