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-4and the “Commissioning Chassis” section on page 3-23or on page 5-9.

Automatically Discovering Modules

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

Tip For information on individual states, see the “Object States” section 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:

Network modules (and associated interfaces)

Interface cards (and associated interfaces)

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

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

Cisco Access Router Manager User Guide

 

OL-3597-01

3-3

 

 

 

Page 3
Image 3
Cisco Systems OL-3597-01 manual Automatically Discovering Modules, Network Module/Interface Port Naming Convention