|
|
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 application 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:
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 application's 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:
Auto discovery is the Cisco EMF 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. |
The Auto discovery application has three mechanisms for discovering chassis:
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-30.
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 commission the chassis to fully manage the device, including enabling automatic module discovery. For information, see the "Commissioning Chassis" section or on page 5-9.
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. |
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). For example, a C85MS-SCAM-2P module in slot 0 would be automatically named Carrier Module-0. If the same module were in slot 1, it would be named Carrier Module-1. Carrier modules do not reflect a subslot number because carrier modules are full slot objects, therefore the subslot is not relevant. A WAI-E1C-4BNC module, which may be contained by said Carrier Module-0, occupies only a half slot and would be named WAI-E1C-4BNC-0-0 if it were in slot 0 subslot 0. It would be named WAI-E1C-4BNC-0-1 if it were in slot 0 subslot 1.
The interfaces on each module are named according to the lowest supported protocol layer. For example, interfaces on an ATM module, such as a WAI-EIC-4BNC, in slot 0 subslot 0 are named: ATM 0-0-0, ATM 0-0-1, ATM 0-0-3, and ATM 0-0-4. The last number indicates the port. Interface names for the same ATM module in slot 0 subslot 1 would be ATM 0-1-1, ATM 0-1-2, etc. Interfaces on an (Ethernet) C85FE-16F-16K module in slot 3 would have names Ethernet 3-0-0, Ethernet 3-0-1, and so on. Notice that even though this particular module occupies a full slot, the default subslot entity of 0 is reflected in the interface names.
EM chassis objects can be manually pre-deployed before the equipment arrives on-site. Pre deployment is useful if, for example, you know that you will be receiving a certain device, you can manually deploy the specific chassis before it is actually present.
Pre-deployment can save future time and effort. When the device becomes available in the network, you must commission the chassis in order for the EM application to detect its presence. Assuming that the chassis successfully moves into a managed state (e.g., not the decommissioned or lost comms state), subchassis discovery begins. If the device is not present at the time of commissioning, the EM chassis object moves into the lost comms state (i.e., is not managed). The discovered chassis object adopts all the configuration parameters you pre-applied to it (e.g., name).
Pre-deployment is desirable in a situation where the expected hardware is known, but configuration information is perhaps not readily available. If you want to manually predeploy only, follow only the pre-deployment procedure following, then perform device synchronization. Manually pre-deployed objects assume whatever configuration is currently on the device, and this information displays in the appropriate EM configuration windows.
Currently, only the chassis object is available for (manual) pre-deployment. Modules, processor, and supporting modules are not available for manual deployment.
For instance, say that you are expecting a Cisco Catalyst 8540 MSR chassis and various modules (with respective interfaces). You can perform the following steps to perform both manual pre-deployment and offline configuration:
1. Manually deploy a generic object. For further information, see the "Deploying Generic Objects" section.
2. Manually deploy the chassis under a generic object. For further information, see the "Manually Deploying Chassis" section.
Now you have pre-deployed and thus created representative objects in the EM for your expected hardware. All of these objects will remain in the Decommissioned state until the hardware is physically present on the network.
When all of your pre-deployed objects become available, you can synchronize the EM to the device. This process synchronizes the information on the device with the pre-deployment information in the EM. Synchronization is achieved by commissioning the chassis object. Chassis commissioning allows the EM to detect the presence of the chassis. When you commission the chassis, the EM discovers not only the presence of the chassis, but the presence of all existing objects within the chassis. For further information, see the "Commissioning Chassis" section or on page 5-9.
Synchronization effectively tells the EM that you now have a real working system. All objects typically pass through the following state sequence: decommissioned to discovery to normal to sync to normal.
Note that device synchronization does not recreate all objects present in the hardware. Some existing objects cannot be recreated, or need to be uploaded manually. ATM connections are not recreated. You can, however, upload existing ATM connections. For further information, see the "Uploading Existing ATM Connections and ATM QoS Profiles" section.
Manually deployment consists of three stages as shown in the following figure.
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 "Predeployment" 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.
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. 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.
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 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.
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.
Step 6 Enter the number of (Site) objects to deploy.
Step 7 Click Forward.
A second Deployment Wizard - Object Parameters window appears.
Step 8 Enter a (Site) object name. Each object, must have a unique name.
Step 9 Click Forward.
Step 10 Click Select, to select a physical view.
The Object Selector Window appears.
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.
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.
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.
Chassis objects deploy by either automatic discovery or manually 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:
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:
The Deployment Wizard appears.
You can click Cancel at any point to cancel the deployment.
Step 2 Select the appropriate chassis type Quick Start option, then click Forward.
Step 3 Enter the number of chassis objects you want to deploy.
Step 4 Click Forward.
Step 5 Enter the following information:
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.
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.
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 Catalyst 8500 routers supported by C8500MGR 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:
The Deployment Wizard appears.
You can choose Cancel at any point to cancel the deployment.
Step 2 Select the chassis type you want to deploy, then click Forward.
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.
Step 3 Enter the number of chassis objects you want to deploy.
Step 4 Click Forward.
Step 5 Enter the following information:
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.
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.
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.
This section describes how to deploy ATM connection objects (that is, PVC and SPVC objects). 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 PVC is a permanent logical connection is configured between two ATM interfaces (or an incoming and outgoing VCL) that, typically, serve as conduits through which the connection passes. PVCs save processing overhead that is associated with establishing a channel when a virtual channel must exist all the time. You can(1) deploy a PVC or SPVC (which creates the PVC/SPVC within the EM), (2) apply a QoS profile (ATM traffic descriptor) to the PVC or SPVC, and then (3) create the connection on the device. Deploying and creating a PVC using the EM creates a cross-connection within one device; deploying and creating an SPVC creates a connection between the ATM interface on one device and the ATM interface on another device.
Service provisioning for ATM must adhere to a variety of configuration standards which help prevent errors when establishing ATM connections. The EM includes service provisioning logic to ensure valid combinations of configuration data.
Consider the following guidelines before you configure ATM virtual channels:
In lieu of deploying PVCs 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.
You can deploy a PVC under a main interface or a subinterface.
To deploy a PVC on a main interface or a subinterface, proceed as follows:
The Deployment Wizard appears.
Step 2 Enter the following information:
If, in the future, you deploy more PVCs on an interface in which other PVCs already exist, remember to not duplicate the starting number. For example, if three PVCs exist on an interface and their numbers are one, two, and three; and you now want to deploy six more, begin your PVC object number at four, where you left off previously. The six new PVC numbers will be four, five, six, seven, eight, and nine.
Step 3 Determine whether to enable or disable the source auto allocation feature by entering 0 to disable or 1 to enable in the Auto Allocate Source field. Enabling the auto allocation feature automatically assigns VPI and VCI values based on the availability within the device cross-connect table.
Depending on the entry, the following must occur:
Step 4 If the source VPI and VCI auto allocation entry is 0 (disabled), enter the source VPI and VCI values as follows:
Step 5 Determine whether to utilize the destination auto allocation feature. Enabling the auto allocation feature automatically assigns VPI and VCI values based on the availability within the device cross-connect table.
If you choose to automatically allocate the destination VPI and VCI values, leave the Destination VPI and Destination VCI fields blank. The subsequent window allows you to enable the destination auto allocate setting.
To specify the destination VPI and VCI values, enter the corresponding fields as follows:
Step 6 Click Forward to proceed.
A second Deployment Wizard - Object Parameters window appears, providing the opportunity to automatically create the connection on the device upon deployment and, if the corresponding fields were left blank on the previous window, to enable destination auto allocation. If the destination VPI and VCI values were provided on the previous window, the corresponding field does not display on the second Object Parameters window. Skip Step 7 and proceed to Step 8.
Step 7 Enter 1 to enable the automatic destination auto allocate feature in the corresponding field.
Although you may enter 0, indicating disabled, in the Destination Auto Allocate field, deployment will fail because the destination VPI and VCI values were not specified in Step 5. Should you want to indicate destination VPI/VCI values at this point, you must cancel the current deployment and begin deployment over.
Step 8 Enter 1 (yes) to create or 0 (no) to not create the connection on the device in the Create Connection field.
Step 9 Click Forward to proceed.
The Deployment Wizard - Views window appears.
Step 10 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 appears.
Step 11 Choose the object you want to place the PVC 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 12 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. Note that both of the VCLs, which make up the PVC, should be within one chassis.
Step 13 Repeat Steps 10 through 12 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 14 Click Forward to proceed.
The Deployment - Wizard Summary window appears. The Summary window provides details of the object(s) you are about to deploy.
The number of objects deployed reflects the number of PVC objects deployed plus two VCLs per PVC. For example, if you deploy one PVC object, three objects deploy in total. The three objects are two VCLs plus the logical PVC object itself.
Step 15 Click Finish to deploy the PVC 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 PVC object(s) deploy accordingly and display in the Component Managed view on the Map Viewer window. Depending on the configuration profile and activation options selected, deployment occurs as follows:
Step 16 Click Finish to close the Deployment Wizard window.
You can deploy an SPVC using the Cisco EMF endpoint or non-Cisco EMF endpoint templates. The Cisco EMF endpoint template is for use when deploying SPVCs where both of the cross-connect's ATM interfaces are managed objects within the Cisco EMF application. The non-Cisco EMF endpoint template is for use when only the source endpoint of the connection is within Cisco EMF.
To deploy an SPVC object on a main interface, proceed as follows:
The Deployment Wizard appears.
Step 2 Choose a template, either an SPVC with a Cisco EMF endpoint or an SPVC with a non-Cisco EMF endpoint, then click Forward to proceed.
The following window examples use the Cisco EMF endpoint template.
The Deployment Wizard - Object Parameters window appears.
Step 3 Enter the following information:
If, in the future, you deploy more SPVCs on this same interface, remember to not duplicate this starting number. For example, if you already have three SPVCs deployed on this interface and they are numbered one, two, and three, and you now want to deploy six more, begin your SPVC object number at four, where you left off previously. The six new SPVCs will be numbered four, five, six, seven, eight, and nine.
Step 4 Determine whether to enable or disable the source auto allocation feature by entering 0 to disable or 1 to enable in the Auto Allocate Source field. Enabling the auto allocation feature automatically assigns VPI and VCI values based on the availability within the device cross-connect table.
Depending on the entry, the following must occur:
Step 5 If the source VPI and VCI auto allocation entry is 0 (disabled), enter the source VPI and VCI values as follows:
Step 6 Determine whether to utilize the destination auto allocation feature. Enabling the auto allocation feature automatically assigns VPI and VCI values based on the availability within the device cross-connect table. For deployment of an SPVC using the non-Cisco EMF endpoint template, you must enter the destination and VCI values. Automatic allocation for destination VPI/VCI is not possible.
If you choose to automatically allocate the destination VPI and VCI values, leave the Destination VPI and Destination VCI fields blank.
To specify the destination VPI and VCI values, enter the corresponding fields as follows:
Step 7 Click Forward to proceed.
A second Deployment Wizard - Object Parameters window appears.
Step 8 Enter the following information:
Although you may enter 0, indicating disabled, in the Auto Allocate Destination field, deployment will fail because the destination VPI and VCI values were not specified in Step 5. Should you want to indicate destination VPI/VCI values at this point, you must cancel the current deployment and begin deployment over.
Step 9 Click Forward to proceed.
The Deployment Wizard - Views window appears.
When using the Cisco EMF endpoint template, two fields display on the Views window. Each field represents one Cisco EMF endpoint of the SPVC connection. The first Component Managed field is the source endpoint of the connection and the second is the destination endpoint.
For non-Cisco EMF endpoint deployment, a single field displays representing the one Cisco EMF (source) endpoint selection.
Step 10 Click the Select button opposite the Component Managed field to choose where you wish to place the object within the view.
The Object Selector window appears.
Step 11 Choose the object you want to place the SPVC 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 12 Once you have highlighted your selection, click Apply.
The Deployment Wizard - Views window re-appears with the location where the object will be placed in the corresponding view field.
If deploying a non-Cisco EMF endpoint SPVC, continue to Step 14.
If deploying a Cisco EMF endpoint SPVC, by default, your initial selection displays in both the Component Managed View fields regardless of which field you initiated the selection. The two ports, however, must use different object selections. Note that both the source and destination ports of an SPVC should be within two different chassis.
Step 13 If you are using the Cisco EMF endpoint template, repeat Steps 10 through 12 for the second Cisco EMF endpoint.
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 endpoint selection and the bottom field represents the destination endpoint selection. These object selections, however, must be different.
Again, note that only one Component Managed field displays when deploying through the non-Cisco EMF endpoint template.
The Deployment Wizard - Summary window appears.
The number of objects deployed reflects the number of SPVC object deployed plus each of the Cisco EMF VCLs that represent the logical connection. For example, if you deploy one SPVC object with Cisco EMF endpoints, three objects deploy in total. The three objects are two VCLs plus the logical PVC object itself. A single SPVC connection with non-Cisco EMF endpoints deploy only two objects; one for the single VCL within Cisco EMF and the other for the logical object.
Step 15 Click Finish to deploy the SPVC 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 SPVC object(s) deploy accordingly and display in the Component Managed view on the Map Viewer window. Depending on the configuration profile and activation options selected, deployment occurs as follows:
When deploying a non-Cisco EMF endpoint SPVC object, the connection does not create on the device even if the option was selected. To create the actual connection, you must manually activate the connection.
Step 16 Click Finish to close the Deployment Wizard window.
The Commissioning section covers the following areas:
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 Catalyst 8540 MSR 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.
The Cisco Catalyst 8510 and LS1010 chassis maps look different than the 8540 example in the preceding figure.
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.
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-45 and the "Decommissioning an Interface" section.
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 theses states, see the "Object States" section.
To commission a chassis, proceed as follows:
The Chassis Configuration window appears displaying the Configuration tab.
Step 2 Select the Chassis you want to commission from the Chassis list box at left of the window.
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 Catalyst 8540 MSR 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.
The Cisco Catalyst 8510 MSR and LS1010 chassis maps do not look the same as the 8540.
After commissioning a chassis you can configure and manage the chassis objects. For further details, see the "Chassis Configuration" section.
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.
To decommission a chassis, proceed as follows:
The Chassis Configuration window appears displaying the Configuration tab (see Figure 3-31).
Step 2 Select the chassis you want to decommission in the Chassis list box at left 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.
The Module Commissioning and Discovery section covers the following areas:
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:
Commissioning any supporting module initiates the following activities:
To commission a module, proceed as follows:
The Module Configuration window appears.
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 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:
Decommissioning any supporting module initiates the following activities:
To decommission a module, proceed as follows:
The Module Configuration window appears (see Figure 3-33).
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.
Posted: Wed Feb 26 03:52:36 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
