Summary of the content on the page No. 1
CHAPTER 3
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
Summary of the content on the page No. 2
Chapter 3 Deploying and Discovering Objects Automatic Discovery 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 descr
Summary of the content on the page No. 3
Chapter 3 Deploying and Discovering Objects Automatic Discovery 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 on page 5-4 and the “Commissioning Chassis” section on page 3-23 or on page 5-9. Automatically Discovering Modules Assuming the chassis, of which the module is part of, i
Summary of the content on the page No. 4
Chapter 3 Deploying and Discovering Objects Automatic Discovery inserted into a NM–2FE2W network module in slot 1 (i.e., NM–2FE2W–1), occupies a subslot and would be named WIC–2T–1–0 if it were in slot 1 subslot 0. It would be named WIC–2T–1–1 if it were in slot 1 subslot 1. The interfaces on a network module which contains subslots, such as the NM–2FE2W module, follows two different interface naming conventions. If the NM–2FE2W is in slot 1 (i.e., NM–2FE2W–1), the interfaces directl
Summary of the content on the page No. 5
Chapter 3 Deploying and Discovering Objects Automatic Discovery Figure 3-3 CPU–0 Naming Convention CPU–0 Container Ethernet Port Interface Type Slot–Port Interface Card Slot–SubSlot Interface Type Slot–Port To clarify, the physical processor module is always automatically named CPU––1, no matter the chassis. Cisco Access Router Manager User Guide OL-3597-01 3-5
Summary of the content on the page No. 6
Chapter 3 Deploying and Discovering Objects Pre–deployment Pre–deployment 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 to detec
Summary of the content on the page No. 7
Chapter 3 Deploying and Discovering Objects Deployment Deployment Manual deployment consists of three stages as shown in the following figure. Figure 3-4 Deployment Process Workflow Stage 1: Manually Deploy Generic Container Objects (e.g., Sites) Chassis Auto Discovery Chassis Manual Stage 2: Chassis Level Deployment Deployment (Quick Start) Chassis Manual Deployment Stage 3: Subchassis Level Discovery 1. The first deployment stage is to manually deploy a generic object (e.g., Site). A ge
Summary of the content on the page No. 8
Chapter 3 Deploying and Discovering Objects Deployment 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
Summary of the content on the page No. 9
Chapter 3 Deploying and Discovering Objects Deployment Figure 3-5 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-6 Deployment Wizard – Object Parameters Window (1 of 2) Cisco Access Router Manager User Guide OL-3597-01 3-9
Summary of the content on the page No. 10
Chapter 3 Deploying and Discovering Objects Deployment Step 6 Enter the number of (Site) objects to deploy. Step 7 Click Forward. A second Deployment Wizard – Object Parameters window appears. Figure 3-7 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
Summary of the content on the page No. 11
Chapter 3 Deploying and Discovering Objects Deployment Figure 3-8 Deployment Wizard – Views Window Step 10 Click Select to select a physical view. The Object Selector window appears. Figure 3-9 Object Selector Cisco Access Router Manager User Guide OL-3597-01 3-11
Summary of the content on the page No. 12
Chapter 3 Deploying and Discovering Objects Deployment 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-10 Deployment Wizard – Views Window Step 13 Click Forward. You are prompted to repeat Steps 8 to 13 if you are deploying
Summary of the content on the page No. 13
Chapter 3 Deploying and Discovering Objects Deployment Figure 3-11 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.
Summary of the content on the page No. 14
Chapter 3 Deploying and Discovering Objects Deployment 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 ob
Summary of the content on the page No. 15
Chapter 3 Deploying and Discovering Objects Deployment Figure 3-12 Deployment Wizard—Templates Quick Start Option 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-13 Deployment Wizard—Object Parameters (1 of 2) Cisco Access Router Manager User Guide OL-3597-01 3-15
Summary of the content on the page No. 16
Chapter 3 Deploying and Discovering Objects Deployment 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-14 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, “C2611”
Summary of the content on the page No. 17
Chapter 3 Deploying and Discovering Objects Deployment 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-15 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 c
Summary of the content on the page No. 18
Chapter 3 Deploying and Discovering Objects Deployment Configuration window, see the “Chassis Configuration” section on page 5-6. 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 informati
Summary of the content on the page No. 19
Chapter 3 Deploying and Discovering Objects Deployment 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 on page 3-14. Figure 3-17 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
Summary of the content on the page No. 20
Chapter 3 Deploying and Discovering Objects Deployment Figure 3-18 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, “C2611”) according to the chassis type selected for deployment. You can accept the default prefix or change this prefix, as desired. It is recommended t
