Home

Cisco Systems ACCESS OL-3597-01 User's Manual

1. Cisco Access Router Manager User Guide OL 3597 01 E Chapter3 Deploying and Discovering Objects HT Deployment Step6 Enter the number of Site objects to deploy Step7 Click Forward A second Deployment Wizard Object Parameters window appears Figure 3 7 Deployment Wizard Object Parameters Window 2 of 2 Deployment Wizard Object Parameters 2 Object Parameters Site names Site 1 Forward gt gt Cancel Finish N J im te Pd Step8 Enter a Site object name Each object must have a unique name Step9 Click Forward One of the following occurs e If deployment was initiated from a view then the Deployment Wizard Views window appears see the following figure Proceed to Step 10 e Ifdeployment 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 Cisco Access Router Manager User Guide Eu OL 3597 01 Chapter3 Deploying and Discovering Objects Deployment W Figure 3 8 Deployment Wizard Views Window 80573 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 a 311 Chapter3 Deploying and Discovering Objects HT Deployment Step1
2. e Network modules and associated interfaces e Interface cards and associated interfaces e External interface cards and associated interfaces and Ethernet interfaces Network modules are named by type and slot number For example a NM 4T1 IMA module in slot 2 would be automatically named NM 4T1 IMA 2 If the same module were in slot 3 it would be named NM 4T1 IMA 3 The interfaces on each network module are named according to the interface type followed by slot port number For example interfaces on an ATM module such as the NM 4T1 IMA in slot 3 are named ATM 3 0 ATM 3 1 ATM 3 2 and ATM 3 3 The last number indicates the port The following figure captures this example as it appears in the physical hierarchy Figure 3 1 Network Module Interface Port Naming Convention E EE NH 4T1 IHA 3 i4 4 Network Module Name Slot Interface Type Slot Port While all network modules supported by Cisco Access Router Manager occupy full slots only some network modules can accommodate interface cards by way of integrated subslots The NM 1A OC3M NM 4T IMA and NM 1FE TX network modules for example do not accommodate interface cards therefore the subslot indicator is irrelevant to these module objects A WIC 2T module which may be I OL 3597 01 Cisco Access Router Manager User Guide gg Chapter3 Deploying and Discovering Objects HZ Automatic Discovery inserted into a NM 2FE2W network module in slot 1 i e
3. NW 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 directly on the module are named FastEthernet 1 0 and FastEthernet 1 1 indicating the interface type followed by the slot port number This interface naming convention is exactly the same as that described in the preceding paragraphs If the same NM 2FE2W module in slot 1 also contains an interface card in subslot 0 for example a WIC 2T i e WIC 2T 1 0 the associated interfaces would be named Serial 1 0 and Serial 1 1 In this case notice that the digits following the interface type indicate the slot port location and do not cite the subslot number of the WIC immediately above the serial interface in the physical hierarchy If there is another WIC 2T in subslot 1 i e WIC 2T 1 1 the associated interfaces are also named Serial 1 0 and Serial 1 1 Again the naming convention does not reflect the subslot number and reads the slot number from the parenting network module The following figure displays this example as the objects appear in the physical hierarchy Figure 3 2 Network Module Interface Port and Interface Card Port Naming Convention 6 FastEthernet
4. e The line card and active interfaces are placed in the normal state e Status data becomes available on the line card and interfaces Commissioning any supporting module initiates the following activities e Heartbeat polling begins on the object e The state changes to normal e Status data becomes available To commission a module proceed as follows Right click on a relevant object icon in the Map Viewer window or from an object pick list and choose Cisco Access Router Manager gt Configuration gt Module gt Configuration For information on which objects allow you to launch the Module Configuration window see Appendix A EM Windows The Module Configuration window appears I OL 3597 01 Cisco Access Router Manager User Guide gg Chapter3 Deploying and Discovering Objects WE Commissioning Step 2 Step 3 Step 4 Step 5 Step 6 Figure 3 23 Module Configuration Window Module Configuration 2 4 File Edit Options Window Actions Help sige BBY 2 amp C2611 172 18 101 19 Configuration C2611 172 18 101 34 C2611 172 18 101 62 Additional Descriptions C2621 172 18 101 33 C2651 172 18 101 32 Description 1 C2651 172 18 101 67 C3620 172 18 101 29 C3640 172 18 101 14 C3640 172 18 101 27 C3640 172 16 101 69 C36624C 172 16 101 70 Description 2 C3662AC 172 16 101 68 Chassis C3640 172 16 101 69 CPU C3640 172 18 101 69 NM 1 C3640 172 16 101 69 NM lt C3640 172 16 101 69 NM F
5. Edit Options Window Actions Help Mae BBY 2 amp ESME Configuration Additional Descriptions Device Management C2610 172 18 101 45 C2611 172 18 101 10 Validation Parameters C2611 172 18 101 11 C2611 172 18 101 12 Number of Slots 3 Max Number of Sub Modules per Slot 2 C2611 172 16 101 13 C2611 172 16 101 19 C2611 172 18 101 34 Unavailable Slots none C2611 172 18 101 62 C2621 172 18 101 33 C2651 172 18 101 32 N Cock C2651 172 16 101 67 C3620 172 16 101 29 C3640 172 16 101 14 C3640 172 16 101 27 C3640 172 16 101 69 C36624C 172 16 101 70 C36624C 172 16 101 68 Power Supply Actions Management Global Performance Logging Commission Decommission Start Stop Commission Status Status of last commission Chassis Status CiscoChassis decommissioned Dynamic updates are enabled 84179 Select the chassis you want to commission from the Chassis list box at left of the window Tip Step 3 Step 4 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 Ensure the chassis has proper configuration For information on chassis configuration attributes see the Chassis Configuration section on page 5 2 Click C
6. by devices is used to work out what kind of device has been found e 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 20 on page 3 22 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 Cisco Access Router Manager User Guide E OL 3597 01 _ Chapter 3 Deploying and Discovering Objects Automatic Discovery Hil Following chassis auto discovery you must manually enter the appropriate IOS password and commissio
7. 1 1 BElwic 21 1 0 25 a Serial 1 0 7 wn m 2 E T e e 69005 Managed objects which reside outside of the network module slots directly on the chassis rather than within a network module slot appear in the Physical view hierarchy beneath the CPU O object The CPU 0 object serves as a container for the external Fast Ethernet port s and interface card e g WICs VICs VWICs slot s and is not a physical object within the device itself Depending on the chassis there may be one to four Fast Ethernet ports directly on the chassis The related Ethernet interfaces appear directly beneath the CPU 0 module as Ethernet 0 0 Ethernet 0 1 etc when discovered Additionally depending on the chassis there may be zero to two supported interface card e g WICs VICs VWICs slots The interface cards which fill these slots also appear directly beneath the CPU 0 module and may support one or two ports each The ports on an interface card discover beneath the associated interface card object within the hierarchy and the name includes the interface type and port number on the interface card Similar to the naming convention of interface cards and associated ports previously described the interface card slot number is disregarded Instead the slot number is derived from the parenting CPU 0 object The CPU O slot number is a default value For example consider a Cisco 2611 chassis which can accommodate up to two external interface card
8. 1 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 Step12 Click Apply The Deployment Wizard Views window re appears with the selection displayed Figure 3 10 Deployment Wizard Views Window Deployment Wizard Views aj Select Relationships Physical Physical Forward gt gt Cancel Finish 80575 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 Cisco Access Router Manager User Guide Ea OL 3597 01 Chapter3 Deploying and Discovering Objects Deployment Figure 3 11 Deployment Wizard Summary Window liz Deployment Wizard Summary E ajl Summary Ready to deploy using the template Site 1 user selected objects 0 automatically added objects This gives a total of 1 object to be deployed This will take approximately 0 minutes amp 5 seconds Press lt Finish gt to continue Fervrarii gt Cancel Finish 80576 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 Step14 Click Finish to deploy the object and clos
9. C3640 172 18 101 69 PS 0 Commission Decommission NM HD 2 WIC 2MFT E Actions Commission Status Status of last commission Success Module Status CiscoModule normal CiscoChassis normal Dynamic updates are enabled 84200 Select a chassis from the Chassis list box at left of the window then select a module from the Module list box Ensure the module has proper configuration For information on module configuration attributes see the Module Configuration section on page 5 17 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 Click Close to close the Action Report window Choose File gt Close to close the Module Configuration window Cisco Access Router Manager User Guide e328 OL 3597 01 Chapter3 Deploying and Discovering Objects Commissioning W Decommissioning Modules Decommissioning modules also decommissions all objects beneath the card As a part of decommissioning heartbeat pollin
10. CHAPTER 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 e Automatic Discovery e Pre deployment e Deployment e Commissioning I OL 3597 01 Cisco Access Router Manager User Guide Chapter3 Deploying and Discovering Objects HZ Automatic Discovery Automatic Discovery Objects which are physically present in the network can be aut
11. 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 on page 3 29 or page 5 20 and the Decommissioning an Interface section on page 5 22 Commissioning Chassis Step 1 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 on page 1 23 To commission a chassis proceed as follows Right click on a relevant object icon in the Map Viewer window or from an object pick list and choose Cisco Access Router Manager gt Configuration gt Chassis gt Configuration For information on which objects allow you to launch the Chassis Configuration window see Appendix A EM Windows The Chassis Configuration window appears displaying the Configuration tab I OL 3597 01 Cisco Access Router Manager User Guide gg Chapter3 Deploying and Discovering Objects WE Commissioning Step 2 Figure 3 21 Chassis Configuration Window Chassis Configuration JE j File
12. ates 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 on page 3 3 Following subchassis discovery all objects enter a specific state For further information see the Object States section on page 1 23 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 I OL 3597 01 Cisco Access Router Manager User Guide gg Chapter3 Deploying and Discovering Objects HT 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 Step 1 Step 2 As aresult of ma
13. aush 84182 You can choose Cancel at any point to cancel the deployment Select the chassis type you want to deploy then click Forward The Deployment Wizard Object Parameters window appears Cisco Access Router Manager User Guide OL 3597 01 Chapter3 Deploying and Discovering Objects Deployment W 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 80567 Step3 Enter the number of chassis objects you want to deploy Step4 Click Forward A second Deployment Wizard Object Parameters window appears Cisco Access Router Manager User Guide OL 3597 01 TEN Chapter3 Deploying and Discovering Objects HT Deployment Step 5 Step 6 Figure 3 18 Deployment Wizard Object Parameters 2 of 2 Deployment Wizard Object Parameters E Object Parameters Chassis Name IP Address Subnet Mask SNMP V2e Read Community SNMP V2e Write Community Forward gt gt 2611 0 0 0 0 0 0 0 0 255 255 255 9 public pri vate Cancel Faush 84183 Enter the following information Chassis Name Name including prefix and suffix for the chassis you are deploying This chassis name must be uni
14. bchassis discovery The following figure shows a Cisco 3662 AC 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 20 Before Subchassis Discovery _ pann rr nao IL aii yy 4p ae P 84194 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 Cisco Access Router Manager User Guide M322 OL 3597 01 _ Chapter 3 Deploying and Discovering Objects Commissioning W 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
15. ber 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 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 on page 3 22 or the Commissioning a Chassis section on page 5 9 I OL 3597 01 Cisco Access Router Manager User Guide gg Chapter3 Deploying and Discovering Objects WE Commissioning Commissioning The Commissioning section covers the following areas e Chassis Commissioning and Subchassis Discovery e Module Commissioning and Discovery 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 su
16. de OL 3597 01 _ Chapter 3 Deploying and Discovering Objects Step 6 Step7 Deployment W 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 J Deployment Wizard Summary le ul Summary Ready to deploy using the template Cisco 2611 Chassis Quick Start 1 user selected objects 0 automatically added objects This gives a total of 1 object to be deployed This will take approximately 0 minutes amp 5 seconds Press lt Finish gt to continue Ferwani gt Cancel Finish 84186 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 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 initi
17. e 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 Cisco Access Router Manager User Guide OL 3597 01 SEE Chapter3 Deploying and Discovering Objects HT 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 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 on page 3 8 The Deploying Chassis section contains the following areas e Manually Deploying Chassis Using Quick Start e Manually Deploying Chassis Manually Deploying Chassis Using Quick Start fe 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 Step 1 It is recommended that you ping the router you intend to deploy before using the manual deploy
18. figuration window appears see Figure 3 23 Step 2 Select a chassis from the Chassis list box at left of the window then select a module from the Module list box Step3 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 Step4 Choose Close to close the Action Report window Step5 Choose File gt Close to close the Module Configuration window Cisco Access Router Manager User Guide OL 3597 01 a 3 29 Chapter3 Deploying and Discovering Objects HT Commissioning Cisco Access Router Manager User Guide M330 By OL 3597 01
19. g 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 e All interfaces and ATM connections on the line card are also decommissioned e Heartbeat polling stops on the line card and interfaces e The line card interfaces and ATM connections are placed in the decommissioned state e Status data is no longer available on the line card and interfaces e Performance polling stops on the line card and interfaces if enabled Decommissioning any supporting module initiates the following activities e Heartbeat polling stops on the object e The state changes to decommissioned e Status data is no longer available e 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 Step 1 Right click on a relevant object icon in the Map Viewer window or from an object pick list and choose Cisco Access Router Manager gt Configuration gt Module gt Configuration For information on which objects allow you to launch the Module Configuration window see Appendix A EM Windows The Module Con
20. ing a chassis you can configure and manage the chassis objects For further details see the Chassis Configuration section on page 5 2 Cisco Access Router Manager User Guide EE a 325 Chapter3 Deploying and Discovering Objects WE Commissioning Decommissioning Chassis Step 1 Step 2 Step 3 Step 4 Step 5 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 Right click on a relevant object icon in the Map Viewer window or from an object pick list and choose Cisco Access Router Manager gt Configuration gt Chassis gt Configuration For information on which objects allow you to launch the Chassis Configuration window see Appendix A EM Windows The Chassis Configuration window appears displaying the Configuration tab see Figure 3 21 Select the chassis you want to decommission in the Chassis list box on the left hand side of the window Click Decommission located in the Actions area The chassis and all objects contained within are decommissioned Decom
21. ment 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 In the Map Viewer right click on the generic site object under which you wish to deploy the chassis then choose Deployment gt Cisco Access Router Manager gt Chassis The Deployment Wizard appears Cisco Access Router Manager User Guide 31a OL 3597 01 Chapter3 Deploying and Discovering Objects Deployment W Figure 3 12 Deployment Wizard Templates Quick Start Option You can click Cancel at any point to cancel the deployment Step2 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 TE Chapter3 Deploying and Discovering Objects HT Deployment Step 3 Step 4 Step 5 Enter the number of chassis objects you want to deploy Click Forward A second Deployment Wizard Object Parameters window appears Figure 3 14 Deployment Wizard Object Parameters 2 of 2 Deployment Wizard Object Parameters mj Object Parameters Chassis Name C2611 0 0 0 0 IP Address 0 9 0 0 Subnet Mask 255 255 255 0 SNMP V2c Read Community public SNMP Y2c Write Community private User Name I Logi
22. missioned 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 Click Close to close the Action Report window Choose File gt Close to close the Chassis Configuration window Cisco Access Router Manager User Guide M326 i OL 3597 01 Chapter3 Deploying and Discovering Objects Commissioning W Module Commissioning and Discovery The Module Commissioning and Discovery section covers the following areas e Commissioning Modules e Decommissioning Modules Commissioning Modules Step 1 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 e All interfaces on the line card also commission e Heartbeat polling begins on the line card and interfaces
23. n Password I Exec Password I Forward gt gt Cancel Finish 84184 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 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 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 Cisco Access Router Manager User Gui
24. n 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 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 itis 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 on page 1 23 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 The Cisco Access Router Manager implements automatic naming conventions for the following objects
25. nual 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 on page 3 23 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 Access Router Manager routers support the quick start feature For further information see the Manually Deploying Chassis Using Quick Start section on page 3 14 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 In the Map Viewer right click on the generic site object under which you wish to deploy the chassis then choose Deployment gt Cisco Access Router Manager gt Chassis The Deployment Wizard appears Figure 3 16 Deployment Wizard Templates Deployment Wizard Templates 3 Template Choices Cisco 2610 Chassis Cisco 2610 Chassis Quick Start Cisco 2610KM Chassis Cisco 2610KM Chassis Quick Start Cisco 2611 Chassis Cisco 2611 Chassis Quick Start Cisco 2611XM Chassis Cisco 2611XM Chassis Quick Start Cisco 2612 Chassis Cisco 2612 Chassis Quick Start Cisco 2613 Chassis Cisco 2613 Chassis Quick Start Cisco 2620 Chassis Cisco 2620 Chassis Quick Start Forward gt gt Cancel F
26. omatically 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 e Automatically Discovering Chassis e Automatically Discovering Modules Automatically Discovering Chassis amp 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 amp 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 e 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 e 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
27. ommission 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 Cisco Access Router Manager User Guide OL 3597 01 Chapter3 Deploying and Discovering Objects Commissioning Ti 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 Step5 Click Close to close the Action Report window Step6 Choose File gt Close to close the Chassis Configuration window The following figure shows a Cisco 3662 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 on page 1 23 Figure 3 22 After Subchassis Discovery Cisco 3600 snes The Cisco 2600 series and 3620 3540 chassis maps do not look the same as the 3660 After commission
28. ow 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 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 3661 AC chassis and various modules with respective interfaces You can perform the following steps to perform both manual pre depl
29. oyment and offline configuration 1 Manually deploy a generic object For further information see the Deploying Generic Objects section on page 3 8 2 Manually deploy the chassis under a generic object For further information see the Manually Deploying Chassis section on page 3 18 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 on page 3 23 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 Cisco Access Router Manager User Guide E OL 3597 01 Chapter3 Deploying and Discovering Objects Deployment Deployment Manual deplo
30. que 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 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 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 Cisco Access Router Manager User Guide OL 3597 01 _ Chapter 3 Deploying and Discovering Objects Step7 Deployment W Figure 3 19 Deployment Wizard Summary Deployment Wizard Summary 2 all Summary Ready to deploy using the template Cisco 2611 Chassis 1 user selected objects 0 automatically added objects This gives a total of 1 object to be deployed This will take approximately 0 minutes amp 5 seconds Press lt Finish gt to continue Faryanil gt Cancel Finish 84185 The num
31. roxied Device Site This section provides an example that shows how to deploy a non technology specific site object 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 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 Press click and hold down the right mouse button Choose Deployment gt 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 Cisco Access Router Manager User Guide EN OL 3597 01 Chapter3 Deploying and Discovering Objects Deployment W Figure 3 5 Deployment Wizard Templates Window 80570 Step4 Select the generic object that you wish to deploy from the list supplied In this example select the deployment profile for a site object Step5 Click Forward The Deployment Wizard Object Parameters window appears Figure 3 6 Deployment Wizard Object Parameters Window 1 of 2
32. s and up to two external Ethernet interfaces Say that both Ethernet ports are occupied and one WIC 2T is present in the chassis as the following figure illustrates The Ethernet interfaces are automatically named Ethernet 0 0 and Ethernet 0 1 The WIC 2T is automatically named WIC 2T 0 1 indicating that it is present in the external interface card slot 1 The possible interfaces contained within the WIC 2T could be Serial 0 0 and Serial 0 1 Again notice that the interface card slot number is not included in the interface port naming convention on the external interface cards Cisco Access Router Manager User Guide OL 3597 01 Chapter3 Deploying and Discovering Objects Automatic Discovery W Figure 3 3 CPU 0 Naming Convention E SeScru 0 3 e CPU Container Ethernet 0 0 lt 4 Ethernet 0 1 9 lt _ Ethernet Port Interface Type Slot Port si BI 1c 21 0 4 2 Interface Card Slot SubSlot O Serial 0 0 4 r r Interface Type Slot Port Serial 0 1 lt 205 8 To clarify the physical processor module is always automatically named CPU 1 no matter the chassis I OL 3597 01 Cisco Access Router Manager User Guide gg Chapter3 Deploying and Discovering Objects E 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 kn
33. ubchassis Discovery section on page 3 22 Cisco Access Router Manager User Guide T OL 3597 01 TEN Chapter3 Deploying and Discovering Objects E Deployment Deploying Generic Objects Note Step 1 Step 2 Step 3 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 P
34. yment 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 gt Deployment Quick Start Stage 2 Chassis Level Deployment Chassis Manual Deployment Stage 3 Subchassis Level Discovery 80590 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 on page 3 8 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 on page 3 2 or the Manually Deploying Chassis section on page 3 18 You can also predeploy objects that is manually predeploy objects before the Cisco hardware arrives on site For further information see the Pre 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 S

Cisco Systems ACCESS OL-3597-01 User's Manual

Contents

Download Pdf Manuals

Related Search

Related Contents