Cisco 6400 Deployment Process

Deployment is the feature that informs the Cisco 6400 SCM of the presence of supported network elements.You perform the deployment process after starting the Cisco 6400 SCM for the first time or after installing new hardware or network elements.

The Cisco 6400 SCM objects can be deployed manually or automatically by launching a wizard-style deployment tool that enables you to automatically deploy a network modeled in Cisco EMF. The deployment wizard deploys objects in Cisco EMF in advance of actual deployment on a Cisco 6400 SCM in the field.

The Cisco 6400 SCM:

Detects the presence of previously deployed network equipment as soon as that equipment becomes operational.
Auto-discovers equipment as an alternative to manual deployment.

From the Deployment option, you can also delete a chassis and its defined objects within the relevant chassis. Deployment is the first stage of equipment provisioning. It is also referred to as pre-provisioning—meaning that part of the network hardware setup before the service is actually provisioned. After objects are deployed, the initial state of all objects is normal.

Pre-provisioning is the process of reserving and configuring a space in the system for network equipment that has not yet been physically slotted into the system rack. It refers to a particular state of the device or object. When an object or device is in a pre-provisioned state, the device or object is not present, but the system has been pre-provisioned to hold an object of similar type. Thus the node line cards in the Cisco 6400 SCM can exist in a state known as pre-provisioned and the Cisco 6400 SCM does not monitor their status.

When the cards are placed in the physical equipment, it is possible to change the node line card from the decommissioned state to the commissioned state by clicking the Commission button.

Note Objects try to achieve a Commissioned state after subchassis discovery. After manual deployment the initial state of all objects is Decommissioned, unless you selected the Cisco 6400 SCM Quick Start deployment option. See the "Quick Start Deployment" section on for further details.

You can create Site, Shelf, Chassis, NSP, NRP, NRP2, and Node Line Card objects manually from the MapViewer application. This is referred to as manual deployment. Manual deployment only creates the chassis but does not commission it. You must perform a commission (put deployed objects into service) on the deployed chassis after manual deployment.

Deployment Process Ou tline

Producing a manageable Cisco 6400 UAC in Cisco EMF is a three-stage process (Figure 4-1).

Figure 4-1: Deployment Process

First stage—Deploy the SCM at the chassis level. The Cisco 6400 chassis can be manually deployed or auto-discovered. You must deploy a Site object for each Cisco 6400 UAC.
Second stage—Deploy the SCM objects at subchassis level. This involves auto-discovering the subchassis or deploying additional subchassis objects manually.

The Cisco 6400 SCM software uses a Deployment Wizard to help simplify the process of manually deploying (or creating) new objects representing the network elements to be managed. The Deployment Wizard appears as a series of windows. Each Wizard window prompts you for the information that is required by the deployment process to deploy your new object.

Deployment Launch Points

Table 4-1 lists the various objects that can be deployed and the objects they can be deployed from. For example, you could deploy a chassis and associated NSP from a Site object.

Table 4-1: Deployment Launch Points

Object Type to be Deployed	Launch Point to Deploy Objects From						Menu Options to Select to Launch Deployment Wizard
Object Type to be Deployed	Cisco 6400 Views	Region,Site, Bay	Chassis	NSP	NRP	Node Line Card (NLC)	Menu Options to Select to Launch Deployment Wizard
Generic Objects	Yes	Yes	Yes	Yes	Yes	Yes	Deployment, Deploy Generic Objects...
Chassis and NSP	No	Yes	No	No	No	No	Deployment, Cisco 6400 UAC, Deploy Chassis and NSP
NRP and NRP2 and associated Ports	No	No	No	Yes	No	No	Deployment, Cisco 6400 UAC, Deploy NRP(s) and associated Port(s)
NLC and associated Ports	No	No	No	Yes	No	No	Deployment, Cisco 6400 UAC, Deploy Line Card(s) and associated Port(s)

M anual Deployment of Generic Objects

Generic objects are non-technology-specific objects. The Cisco 6400 SCM allows the following generic objects to be deployed: Bay, IP Device, Network, Region, SNMP Agent, SNMP MIB-2 Agent, SNMP Proxied Device, and Site.

Deploying a G eneric Object

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.

This section explains the deployment of a Site object as an example. The deployment process differs slightly for other types of generic objects.

To deploy a Generic object, follow these steps:

Step 1 Place the cursor over a relevant object. See Table 4-1 to determine the objects you can deploy from.

Step 2 Click and hold down the right mouse button.

Step 3 Choose the Deployment > Deploy Generic Objects... option.

The Deployment Wizard—Templates window appears (Figure 4-2) 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 4-2: Deployment Wizard—Templates Window

Step 4 Chose the generic object that you want to deploy from the list supplied. The example in Figure 4-2 shows a Site object deployment profile selected. The Deployment Wizard now steps through a series of windows that prompt you for the information required to deploy a Site object.

Step 5 Click Forward. The Deployment Wizard—Object Parameters window appears (Figure 4-3).

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

Step 6 Enter the number of sites required.

Note The information that you supply differs according to the type of generic object you are deploying. More than one Deployment Wizard—Object Parameters window can appear depending upon the type of generic object you are deploying. When deploying more than one generic object of the same type, you will have to enter the object parameters for each object.

Step 7 Click Forward. The next window of the Deployment Wizard appears (Figure 4-4).

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

Step 8 Enter a Site name.

Step 9 Click Forward. The Deployment Wizard—Views window appears (Figure 4-5).

Note Proceed to Step 17 when deploying a Network or Region object.

Figure 4-5: Deployment Wizard—Views Window

The Deployment Wizard—Views window allows you to select where your new objects are placed in the Physical and genericObjects views.

Step 10 Click Select (in the Select Relationships frame) to select a Physical relationship. This step only applies when the launch point was not a generic object; otherwise the generic object is selected as the parent object, (for example, a region). The Object Selector window might appear (Figure 4-6) with the Physical view displayed.

Figure 4-6: Deployment Wizard—Object Selector Window

Step 11 Select a location in the Physical view to place the generic object (when required).

Step 12 Click Apply. The Deployment Wizard—Views window appears with your selection displayed. The Cisco 6400 SCM automatically adds the same selection into the genericObjects box. Proceed to Step 14 when the selections are the same.

Step 13 Click Select (in the Select Relationships frame) to select a genericObjects relationship, when required. The Object Selector window appears with the genericObjects view displayed.

Step 14 Select a location in the genericObjects view to place the generic object.

Step 15 Click Apply. The Deployment Wizard—Views window appears (see Figure 4-5).

Step 16 Click Forward.

Note Repeat Steps 8 to 16 if you entered more than one Site in Step 6.

The Summary details appear in the Deployment—Wizard Summary window (Figure 4-7).

Figure 4-7: Deployment Wizard—Summary Window

Step 17 Click Finish (when the Deployment Summary information is correct) to complete deployment and close the Deployment Wizard—Summary window. The new objects are created and displayed in the Map Viewer window.

Note This deployment procedure can be applied to the deployment of any of the generic objects, although all of the steps might not apply to the particular generic object that you are deploying.

M anual Deployme nt of the Cisco 6400 UAC Shelf, C hassis, and N SP

Note A Cisco 6400 chassis and node switch processor (NSP) card must be deployed under a Shelf object. A shelf object is automatically deployed when you deploy a chassis and NSP objects.

Two NSPs can be deployed in either or both of two dedicated slots (0A and 0B) in the center of the Cisco 6400 chassis. One NSP is required for system operation, the second NSP provides fault tolerance.

Deploying a Cisco 6400 Shelf, Chassis, and NSP

Note You can deploy the Cisco 6400 SCM objects manually or automatically by launching a wizard-style deployment tool that enables you to automatically deploy a network modeled in Cisco EMF. The deployment wizard also enables you to (optionally) deploy objects in Cisco EMF in advance of actual deployment of a Cisco 6400 UAC in the field. For information about Quick Start Deployment, see "Quick Start Deployment."

To deploy a Cisco 6400 shelf, chassis, and NSP, follow these steps:

Step 1 Place the cursor over a relevant object. See Table 4-1 to determine the objects you can deploy from.

Note You can now deploy a number of Cisco 6400 chassis into a unique site or bay. However, you must have one shelf object deployed for each chassis. A shelf object is automatically deployed when you deploy a chassis object.

Step 2 Right-click Deployment > Cisco 6400 UAC > Deploy Cisco 6400 UAC option. The Deployment Wizard—Object Parameters window (1 of 3) appears (Figure 4-8).

Figure 4-8: Deployment Wizard—Object Parameters Window (1 of 3)

Step 3 Enter a Shelf name. A Shelf is an object that acts as a container for a chassis object. Each Site object must have a unique name for deployment to be successful.

Click Forward. The Deployment Wizard—Object Parameters window (2 of 3) appears (Figure 4-9).

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

Step 4 Enter the Chassis name, IP Address (for the primary NSP), SNMP Read Community, and SNMP Write Community, and then select the value for an SNMP Version.

Step 5 Click Forward. The Deployment Wizard—Object Parameters window (3 of 3) appears (Figure 4-10).

Figure 4-10: Deployment Wizard—Object Parameters Window (3 of 3)

Step 6 Enter the NSP name, SNMPv3 User Name, SNMPv3 Security Level, SNMPv3 Auth. Key, Username, Login Password, and Exec. Password.

Step 7 Click Forward. The Deployment Summary details appear in the Deployment Summary window (Figure 4-11).

Figure 4-11: Deployment Wizard—Summary Window

Step 8 Click Finish (when the Deployment Summary information is correct) to complete the deployment and close the Deployment Summary window. This creates the relevant objects in the Cisco EMF.

Manual Deployment of Subchassis Objects

The Cisco 6400 SCM software provides a Deployment Wizard to assist you in manually deploying subchassis objects.

The Deployment Wizard is the graphical interface used to create new objects representing the network elements to be managed. The Deployment Wizard prompts you to enter the information that is required by the deployment process.

Deploying N RP Cards and Associated Ports

Node route processor cards (NRP and NRP2) can be installed in any one or all of the eight chassis slots numbered 1 to 8. Figure 4-12 shows four NRPs installed in chassis slots 1, 2, 5, and 6.

To deploy an NRP and port, follow these steps:

Step 1 Place the cursor over a relevant NSP object in the network map, a relevant object in the Map Viewer, or by using an object list on an open Element Manager window. See Table 4-1 for information to determine which objects you can deploy from.

Step 2 Right-click Deployment > Cisco 6400 UAC > Deploy NRPs and Associated Port(s) option. The Deployment Wizard—Templates window appears (Figure 4-12) with a list of defined NRPs and NRP2s.

Figure 4-12: Deployment Wizard—Templates Window

Step 3 Choose NRP1 or NRP2.

Deploying an NRP

Follow these steps to deploy an NRP.

Step 1 From the Deployment Wizard—Templates (Figure 4-12) window, choose the NRP(s) and associated Port(s) item.

Step 2 Click Forward. The Deployment Wizard—Object Parameters (1 of 3) windows appears (Figure 4-13).

Figure 4-13: Deployment Wizard—Object Parameters (1 of 3) Window

Step 3 Enter the number of NRPs that you want to deploy. The number of NRPs that you can deploy in the selected chassis depends on the number of line cards installed.

Step 4 Click Forward. The Deployment Wizard—Object Parameters (2 of 3) window appears (Figure 4-14).

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

Step 5 Enter values for Slot Number, Username, Login Password, Exec Password, NRP IP Address, NRP SNMP Read Community, and NRP SNMP Write Community, and then choose an NRP SNMP Version.

Where:

Slot Number—Slot number of the specified NRP card
Username—Identifies the user who is executing this operation
Login Password—User's password
Exec Password—Encrypted password
NRP IP Address—NRP's IP address
NRP SNMP Read Community—A security mechanism for SNMP communications. Values are private or public.
NRP SNMP Write Community—A security mechanism for SNMP communications. Values are private or public.
NRP SNMP Version—Values are snmpv1, snmpv2c, snmpv3

Step 6 Click Forward. The Deployment The Deployment Wizard—Object Parameters (3 of 3) window appears (Figure 4-15).

Figure 4-15: Object Parameters (3 of 3) Window

Step 7 Enter values for Chassis IP Address, Chassis SNMP Read Community, Chassis SNMP Write Community, and Chassis SNMP Version.

Where:

Chassis IP Address—Identifies the chassis IP address
Chassis SNMP Read Community—Values are private or public
Chassis SNMP Write Community—Values are private or public
Chassis SNMP Version—Values are snmpv1, snmpv2c, snmpv3

Step 8 Click Forward. The Deployment Summary details appear in the Deployment Wizard—Summary window (Figure 4-16).

Figure 4-16: Deployment Wizard—Summary Window

Step 9 Click Finish (when the Deployment Summary information is correct).

Deploying an NRP2

To deploy an NRP2, follow these steps.

Step 1 From the Deployment Window—Templates window (Figure 4-12), choose the NRP2s and associated Port(s) item.

Step 2 Click Forward. The Deployment Wizard—Object Parameters (1 of 3) window appears (Figure 4-17).

Figure 4-17: Deployment Wizard—Object Parameters (1 of 2) Window

Step 3 Enter the number of NRP2s that you want to deploy. The number of NRP2s that you can deploy in the selected chassis depends on the number of line cards installed.

Step 4 Click Forward. The Deployment Wizard—Object Parameters (2 of 3) window appears (Figure 4-18).

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

Step 5 Enter values for Slot Number, SNMPv3 User Name, SNMPv3 Security Level, SNMPv3 Auth. Key, Chassis IP Address, Username, Login Password, Exec. Password, and Chassis SNMP Version.

Where:

Slot Number—Identifies the slot number of the NRP2

SNMPv3 User Name—User who is conducting the SNMP operation

SNMPv3 Security Level—A level of security at which SNMP messages can be sent. The three security levels that can be used are:
- noAuthNoPriv, SNMP messages are sent without authentication and without privacy
- authNoPriv, SNMP messages are sent with authentication but without privacy
- authPriv, SNMP messages are sent with authentication and with privacy
SNMPv3 Auth. Key—User's encrypted password key used in message authentication
Chassis IP Address—Identifies the chassis address
Username—Valid name of the user associated with the NRP2 card
Login Password—User's password
Exec. Password—Encrypted password
Chassis SNMP Version—Values are snmpv1, snmpv2c, snmpv3

Step 6 Click Forward. The Deployment Wizard—Object Parameters (3 of 3) window appears (Figure 4-19).

Figure 4-19: Deployment Wizard—Object Parameters (3 of 3) Window

Step 7 Enter values for Chassis SNMP V2c Read Community and Chassis SNMP V2c Write Community. Where:

Chassis SNMP V2c Read Community—Values are private or public
Chassis SNMP V2c Write Community—Values are private or public

Step 8 Click Forward. The Summary details appear in the Deployment Wizard—Summary window (Figure 4-20).

Figure 4-20: Deployment Wizard—Summary Window

Step 9 Click Finish (when the Deployment Summary information is correct).

D eploying an OC-3 Node Line Card and Ports

Half-height node line cards (NLCs) can be installed in any one or all of the eight slots numbered 1 to 8. One or two OC-3 NLCs can be installed in each slot, for a maximum of 16 per chassis.

To deploy an OC-3 node line card and ports, follow these steps:

Step 2 Right-click Deployment > Cisco 6400 UAC > Deploy OC-3 Line Card(s) and associated Port(s) option. The Deployment Wizard—Object Parameters (1 of 2) window appears (Figure 4-21).

Figure 4-21: Deployment Wizard—Object Parameters (1 of 2) Window

Step 3 Enter the Number of OC-3 node line cards you want to deploy.

Step 4 Click Forward. The Deployment Wizard—Object Parameters (2 of 2) window (Figure 4-22) appears.

Figure 4-22: Deployment Wizard—Object Parameters (2 of 2) Window

Step 5 Enter values for Slot Number, Sub-Slot Number, OC-3 Node Line Card name, Chassis IP Address, Chassis SNMP Read Community, and Chassis SNMP Write Community. Choose the Chassis SNMP Version.

Note You must enter an unused Slot and subslot number or deployment will fail.

Step 6 Click Forward.

Step 7 Repeat Steps 5 and 6 for the number of OC-3 node line cards entered in Step 3.

The Deployment Summary details appear in the Deployment Summary window (Figure 4-23).

Figure 4-23: Deployment Wizard—Summary Window

Step 8 Click Finish (when the Deployment Summary information is correct).

D eploying an OC-12 Node Line Card and Ports

The OC-12 node line card occupies a full slot in the chassis and has a single port.

To deploy an OC-12 node line card and port, follow these steps:

Step 1 Place the cursor over a relevant NSP object in the network map, a relevant object in Map Viewer, or by using an object list on an open Element Manager window. See Table 4-1 for information to determine which objects you can deploy from.

Step 2 Right-click Deployment > Cisco 6400 UAC > Deploy OC-12 Line Card(s) and associated Port(s) option. The Deployment Wizard—Object Parameters (1 of 2) window appears (Figure 4-24).

Figure 4-24: Deployment Wizard—Object Parameters (1 of 2) Window

Step 3 Enter the Number of OC-12 node line cards you want to deploy.

Step 4 Click Forward. The Deployment Wizard—Object Parameters (2 of 2) window appears (Figure 4-25).

Figure 4-25: Deployment Wizard—Object Parameters (2 of 2) Window

Step 5 Enter values for the Slot Number, OC-12 Node Line Card name, Chassis IP Address, Chassis SNMP Read Community, and Chassis SNMP Write Community. Choose the Chassis SNMP Version.

Step 6 Click Forward.

Step 7 Repeat Steps 5 and 6 for the number of OC-12 node line cards entered in Step 3.

The Deployment Summary details appear in the Deployment Summary window (Figure 4-26).

Figure 4-26: Deployment Wizard—Summary Window

Step 8 Click Finish (when the Deployment Summary information is correct).

De ploying a DS3 Node Line Card and Ports

Half-height node line cards (NLCs) can be installed in any one or all of the eight slots numbered 1 to 8. One or two NLCs can be installed in each slot, for a maximum of 16 per chassis.

To deploy DS3 node line cards and ports, follow these steps:

Step 2 Right-click Deployment > Cisco 6400 UAC > Deploy DS3 Line Card(s) and associated Port(s) option. The Deployment Wizard—Object Parameters (1 of 2) window appears (Figure 4-27).

Figure 4-27: Deployment Wizard—Object Parameters (1 of 2) Window

Step 3 Enter the Number of OC-3 node line cards you want to deploy.

Step 4 Click Forward. The Deployment Wizard—Object Parameters (2 of 2) window appears (Figure 4-28).

Figure 4-28: Deployment Wizard—Object Parameters (2 of 2) Window

Step 5 Enter values for Slot Number, Sub-Slot Number, DS3 Node Line Card name, Chassis IP Address, Chassis SNMP Read Community, and Chassis SNMP Write Community. Choose the Chassis SNMP Version.

Note You must enter an unused slot and sub-slot number or deployment will fail.

Step 6 Click Forward.

Step 7 Repeat Steps 5 and 6 for the Number of DS3 node line cards entered in Step 3. The Deployment Summary details appear in the Deployment Summary window (Figure 4-29).

Figure 4-29: Deployment Wizard—Summary Window

Step 8 Click Finish (when the Deployment Summary information is correct).

Deleting a Chassis and Its Objects

This section describes how to delete a chassis and objects within the chassis from your network configuration.

To delete a Cisco 6400 chassis from the configuration, you must perform the following functions:

Disconnect subscribers from services and disconnect each ATM port listed.
For every service that was created, you must decommission each service.
Decommission the chassis.
Delete the relevant chassis.

To disconnect subscribers from any Cisco 6400 chassis, follow these steps:

Step 1 Disconnect subscribers from services. Right-click Cisco 6400 UAC > Subscriber > Disconnect s option from an NSP card. The Service/Subscriber Disconnection window appears (Figure 4-30).

Figure 4-30: S ervice/Subscriber Disconnection Window—Disconnect

See the "Service/Subscriber Disconnection Window" section for further details on the parameters contained in the Service/Subscriber Disconnection window.

Step 2 Choose the Cisco 6400 chassis and ATM Port from the lists displayed on the left side of the window.

Step 3 Choose a Subscriber and Current Connections from the from the lists displayed in the Connection Details panel.

Step 4 Click Disconnect. A pop up window appears (Figure 4-31) to inform you that the selected subscriber is about to be disconnected.

Figure 4-31: About to Disconnect Subscriber

Step 5 Click Yes to disconnect the subscriber. The Action Report window appears (Figure 4-32) confirming that the subscriber was disconnected.

Figure 4-32: Action Report Window

Step 6 Review the Action Report and then click the Close button to close the Action Report window or click the Save button to save the Action Report. The Action Report can be saved and used for diagnostic purposes. The "*** No errors encountered *** " message appears to show that disconnection was successful.

Step 7 Repeat these steps for each subscriber and ATM port listed.

Step 8 For every service you created, you must decommission each service. (That is, the services defined in the Cisco IOS must be removed.)

To decommission services, follow these steps:

Step 1 Right-click on a relevant service in the Cisco6400Service View in the Map Viewer and choose the Cisco 6400 UAC > Service > Configure <service selected> option.

Step 2 From the list of services, choose each service and then click the Decommission Service button.

Step 3 After all services have been decommissioned, go to the next procedure and decommission the discovered chassis.

To decommission the chassis, follow these steps:

Step 1 Right-click a relevant chassis in the Map Viewer and choose the Cisco 6400 UAC > Chassis > Manage> Configuration option. The Chassis Configuration window appears (Figure 4-33).

Figure 4-33: Chassis Configuration Window

Step 2 Choose an appropriate Chassis from the Chassis selection list displayed at the left side of the Chassis Configuration window (Figure 4-33).

Step 3 Click Decommission. The state of the selected chassis and its objects changes to decommissioned.

Step 4 From the same Chassis Configuration window (Figure 4-33), click the appropriate entry in the chassis name list.

Step 5 Right- click Deployment > Delete Objects... option. The popup Deployment Wizard — Summary window appears prompting you to delete the chassis (Figure 4-34).

Figure 4-34: Deployment Wizard—Summary

Step 6 Click Finish to delete the relevant chassis and the objects within it. The chassis name is removed from the Chassis Name list. (Click the Cancel button if you do not want to delete the chassis.)

Auto-Discovery of the Cisco 6400 Chassis

Auto-discovery is used to discover an existing network. You can examine the network for IP and SNMP devices and create an object for each new device discovered.

Auto-discovery is also used to identify new SCM chassis and NSP cards within that chassis.

The Auto-discovery application has three mechanisms for discovering devices:

IP—ICMP pings are used to find devices 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 devices 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 devices and then SNMP requests are used to interrogate the devices to find out what kind of devices they are. This is the default mechanism.

Auto-discovery can detect devices on more than one subnetwork using multihop discovery. This option is available when using SNMP or IP and SNMP discovery. When Cisco EMF discovers a device that is connected to more than one network, it can run auto-discovery on the next network. This happens when the hop count is greater than zero. It can be scheduled to run at preset times. An option is available to specify the physical location under which discovered objects are created.

Note After Auto-discovery, you should launch IOS/Command Line Security information and then enter SNMP management information. See the "After Auto-Discovery" section on for further information.

Discovering IP and SNMP Devices

To auto-discover IP and SNMP devices, follow these steps:

Step 1 Auto-discovery can be opened from the Cisco EMF Launchpad window (Discover icon) or from a popup menu available on a selected object.

Step 2 Choose the object within the Map Viewer window that Auto-discovery will be launched from. Right-click Deployment > Auto Discovery... option. The Discover Network Devices window appears (Figure 4-35).

Figure 4-35: Discover Network Devices Window

The Discover Network Devices window (Figure 4-35) displays the object name and address in the Discovery Configuration panel.

Step 3 Enter the IP address of the chassis or the beginning address of a range of addresses in the Device Address field. To discover a single Cisco 6400 UAC, use the NSP address as the start address.

Step 4 Enter the appropriate mask value in the Device Subnet Mask field.

Step 5 Click the drop-down list next to Discovery Method and choose IP and SNMP (default value) from the displayed list.

Step 6 In the Hop Count data entry box, type the number of distant networks that you want to discover away from the local subnet that you can discover devices on. The maximum number is 16.

Step 7 In the SNMP Retries data entry box, enter the number retry attempts that the system should try to communicate with a device without receiving an expected reply, before it is discarded as not being an SNMP device. The maximum number is 10.

Note If SNMP Retries is left at zero, only the initial attempt to ping a device is made. If the device does not respond or responds with an error, the device is ignored.

Step 8 In the New Community data entry box, enter a new SNMP read community name, then click the Add button. The new community name displays along with the existing community names.

Note You can remove any of the displayed community names by choosing a name and then clicking the Remove button. There must be at least one community name.

Step 9 In the SNMP Timeout data entry box, enter the amount of time that you specify the system to time out before getting a response from a device. The default is 10 seconds.

Step 10 In the Physical Location panel, click the Use Physical Path button. Make sure the correct path is shown. Choose Get path and select the correct Physical View if required.

Note If the object used to launch Auto-discovery already has a physical location, it is shown by default. This path should be selected. Also, the Get Path selection allows you to use the hierarchical browser if you did not choose the Physical Path button.

Step 11 If you want to restrict or increase the IP address range, click the Refine Range button (Figure 4-35). The Discovery Interface window (Figure 4-36) appears. You can specify a range of IP addresses by entering a start address and an end address. Only IP addresses within the specified address range are discovered.

Figure 4-36: Discover Interface Window

Step 12 In the Ping Retries data entry box, type the number of retry attempts that the system should try to identify if an active machine is connected at a specified address. The maximum number is 10.

Note If IP Retries is left at zero, only the initial attempt to ping a device is made. If the device does not respond or responds with an error, the device is ignored.

Step 13 To add a second address, type in the new address and then press the Add Address button. This function allows you to add a second address to be discovered.

Note The Hop Count field must have a value of at least one for you to be able to add another address, otherwise the button is not active. To get distant subnets, you must enter a hop count value.

Step 14 To start the discovery process, choose the device from the Device Interfaces list, then click the Start button. The Discovery Progress window appears similar to Figure 4-37.

Figure 4-37: Discover Progress Window

The Discovery Progress window displays the progress of the auto-discovery process in two ways. The Device Data panel displays information on the number of devices found and information on the success of IP and SNMP queries performed on the devices. The data is presented in a spreadsheet format with each row representing a subnet being discovered. This provides an indication of the current state of the auto-discovery process.

Some messages that can display in the Discovery Progress window are: Starting Discovery, Total devices discovered, and Device object creation complete.

Note You can stop the discovery and creation of objects by clicking the Stop button.

Note When auto-discovery is started, the system checks for existing devices in a selected address range. Any existing devices are ignored by the discovery process and the Stop button is greyed out.

When all the relevant IP devices on the network have been discovered, an object class is created and stored under the Network view for each device. These devices can then be accessed by the Map Viewer.

Step 15 After all devices have been discovered, click the Close button.

After Auto-Discovery

At this point, the chassis is discovered with its NSP in a decommissioned state. After you auto-discover a chassis and before you commission that chassis, perform the following functions:

Enter the CLI password for the selected chassis.
Enter snmpv3 related information for NRP2s only.
Commission the chassis.

Note Auto-discovery from the Cisco 6400 UAC does not deploy NRPs (like manual deployment). The following procedures ensure that all NRPs are discovered in the correct state (commissioned).

To enter the CLI password for the relevant chassis, follow these steps:

Step 1 Right-click Cisco 6400 UAC > Chassis > Admin > Management Information option from the chassis selected for auto-discovery. The Management Information window (see Figure 5-51) appears with the Configuration tab displayed.

Step 2 From the Management Information window (see Figure 5-51), click the IOS/Command Line Security tab. The IOS/Command Line Security Tab window appears (Figure 4-38).

Figure 4-38: Management Information Window—IOS/Command Line Security Tab

Step 3 In the Security Details panel, enter the User Name (optional). If you enter a name in this field, then this name must match the user name specified in the Cisco IOS on the NSP card.

Step 4 Enter the Login Password. This password must match the Line tty password configured in the Cisco IOS on the NSP card.

Step 5 Enter the Exec.Password. This is the encrypted enable password and must match the enable password configured in the Cisco IOS for the NSP card.

Step 6 Choose Save from the File menu to save your parameters.

Step 7 Click the Save Locally button to save the configuration management information to the local SCM database.

Note If there are NRP2s defined in this chassis, then you must perform Step 7 and Step 8 before you commission the chassis.

Step 8 From the selected chassis, right-click Cisco 6400 UAC > Chassis > Manage > SNMP Management option. The SNMP Management window appears (see Figure 5-10).

Step 9 Enter values for the SNMPv3 Specific panel parameters. For details, refer to "Viewing the SNMP Management Window" section.

Step 10 Commission the chassis. See "Commissioning a Chassis" section. The NRP and NRP2 cards are discovered in the correct state.

C ommissioning a Chassis

Note Failure to set the CLI passwords causes subchassis-discovered NRPs to enter the alarmed state, leaves them decommissioned and does not set their IP addresses. NRP passwords must also be set before using the Service and Subscriber options on the Cisco 6400 SCM.

Commissioning a chassis within a shelf initiates subchassis discovery. Subchassis discovery discovers all of the cards installed in the chassis being commissioned.

Note Objects that are pre-provisioned but not in the chassis are shown as decommissioned (hatched). Any objects that are discovered but not pre-provisioned are created as new objects.

A selected chassis can be commissioned in two ways:

Quickly (without opening the Chassis Configuration window) by right-clicking on the chassis map in the Map Viewer window (in the c6400Manager view) and selecting the Cisco 6400 UAC > Chassis > State > Commission option. Selecting the Commission option commissions the chassis and the cards within the chassis. The state of the chassis and the cards within the chassis changes to Normal.
A slightly longer way, from the Chassis Configuration window by choosing the Cisco 6400 UAC > Chassis > Manage > Configuration option.

To commission a chassis (from the Chassis Configuration window), follow these steps:

Step 1 Right-click Cisco 6400 UAC > Chassis > Manage > Configuration option from a relevant network map, a relevant object in the Map Viewer, or by using an object list on an open Element Manager window to launch the Chassis Configuration window (Figure 4-39).

Figure 4-39: Chassis Configuration Window

Step 2 Choose an appropriate Chassis from the Chassis list displayed at the left side of the Chassis Configuration window.

Step 3 Configure the parameters displayed on the Configuration tab.

Note Validation Parameters are set at the time of deployment and represent the correct number of slots or subslots in the Cisco 6400 chassis. Changing these parameters will mean that slot restriction tests could fail deployment; for example, setting the number of slots to 7 and then attempting to deploy a card in slot 8.

Step 4 Enter additional descriptions when required (optional) on the Additional Descriptions tab. Descriptions 1 and 2 (optional) allow you to specify additional description information for a selected chassis. These data entry fields allow you to enter any additional text descriptions for identification purposes (for example, CLLI codes could be entered).

Step 5 Click the Commission button on the Chassis Configuration window. Subchassis discovery starts and all cards that were not pre-provisioned are discovered and added to the chassis Map Viewer. The NSP and all related cards are now in a commissioned state. Figure 4-40 shows a sample view of the chassis after subchassis discovery.

Figure 4-40: After Subchassis Discovery

D ecommissioning a Chassis

A selected chassis can be decommissioned in two ways:

Quickly (without opening the Chassis Configuration window) by right-clicking on the chassis map in the Map Viewer window (in the c6400Manager view) and selecting the Cisco 6400 UAC > Chassis > State > Decommission option. Selecting the Decommission option decommissions the chassis and the cards within the chassis. The state of the chassis and the cards within the chassis changes to Decommissioned.
From the Chassis Configuration window. By opening the Chassis Configuration window to decommission a chassis, you can configure the parameters displayed in the Chassis Configuration window (Figure 4-39).

To decommission a chassis (from the Chassis Configuration window), follow these steps:

Step 1 Right-click Cisco 6400 UAC > Chassis, Manage > Configuration option from a relevant network map, a relevant object in the Map Viewer, or by using an object list on an open Element Manager window. See Table 5-1 for information on which maps, nodes, or objects allow you to launch the Chassis Configuration window.

Step 2 Choose an appropriate Chassis from the Chassis list displayed at the left side of the Chassis Configuration window.

Step 3 Click Decommission. The state of the selected chassis and all related cards changes to decommissioned.

Note If you want to delete a Cisco 6400 device from the configuration, then you must first decommission that device.

Table of Contents

Cisco 6400 Deployment Process