Discovery

This chapter describes the ViewRunner discovery process and lists the equipment and data elements that ViewRunner discovers.

This chapter includes the following sections:

The ViewRunner Discovery Process

In the discovery process, ViewRunner gathers details about the Cisco 6100 Series system configuration and status. By default, ViewRunner automatically discovers a node when you open the Chassis View. You can enable or disable this option in the ViewRunner Preferences dialog box. Access this dialog box by selecting ViewRunner Preferences from the Options menu.

In addition, you can manually invoke ViewRunner discovery by choosing Discover 6100 from the Edit menu or by clicking the Discover 6100 icon on the graphical user interface (GUI) Chassis View. When ViewRunner discovers a node, it redraws the Chassis View with the updated configuration.

ViewRunner queries the system controller module for the Management Information Bas e (MIB) values by using the Simple Network Management Protocol (SNMP) get command. ViewRunner makes this query when the system starts up or when you prompt it to query the system. After you have installed new modules, click the Discover 6100 icon or choose Discover 6100 from the Edit menu to view the discovered modules in the Chassis View.

Discovery of Cisco 6100 Series System Components

Discovery within the Cisco 6100 Series system is the automated process by which the system controller module captures inventory and configuration information about Cisco 6100 Series chassis and modules. ViewRunner performs discovery when you insert a module into the Cisco 6100 Series system, or when you reset the system controller module.

During discovery, the following process takes place within the Cisco 6100 Series system:

Each inserted module conducts a self-test to check for hardware malfunctions.
If a module detects any malfunctions, it does not send a message to the system controller module, and discovery fails. Faulty modules are recognizable by certain LED conditions on the module faceplate. For more information on LED indicators, refer to the Cisco 6100 Series with NI-1 User Guide.
If the system finds no malfunctions, the module notifies the system controller module that it is present by passing relevant inventory attributes to the system controller module.
After the system controller module acquires the inventory information, it captures the system configuration. The system controller then stores discovered attributes and other default configuration information in an MIB within the SNMP agent.

Discovered Attributes

Each module and chassis is equipped with a Flash erasable programmable read-only memory (EPROM). The EPROM is factory-programmed with the following read-only attributes:

CLEI code---BellCore's Common Language Equipment Identifier code
Serial number of the module
Hardware version of the module
Software version of the module

ViewRunner sends these attributes to the system controller module during the discovery process.

CAP ATU-C, DMT-2 ATU-C, and STU-C modules also return the following transceiver information:

Maximum upstream rate that the ATU-C and STU-C modules support

Maximum downstream rate that the ATU-C and STU-C modules support

Line Coding---ViewRunner determines the number of ports in each ATU-C module that is installed in a Cisco 6100 Series system. You can see this number on the Module Configuration tab.
Connect Mode---The jumper setting of a CAP ATU-C, DMT-2 ATU-C, or STU-C module, which indicates whether the system is configured as Digital Off-Hook (DOH) or Direct Connect.

Note CAP ATU-C, DMT-2 ATU-C, and STU-C module jumpering is related to configuration modes. Refer to the relevant Cisco 6100 with NI-1 installation guide for more information. You must jumper all modules in the same mode for the system to operate.

Discovered Configuration Defaults

After ViewRunner detects a chassis or module, the Cisco 6100 Series SNMP agent automatically creates a configuration for the chassis or slot if one is not already present. The Administrative state for this configuration is set to Locked.

A Cisco 6100 Series chassis or module configuration is created whenever all of the following conditions occur:

Hardware detects the presence of the chassis

The system controller detects the presence of the module when you insert it into the chassis or after Cisco 6100 Series software resets it.

Discovered Equipment

ViewRunner infers the presence of a Cisco 6100/6130 chassis if a system controller module is present. The Cisco 6100 Series system requires that a line interface module (LIM) controller module be equipped in the Cisco 6110 chassis if the chassis is present. The LIM controller module forwards all LIM notifications to the system controller module.

ViewRunner discovers the following Cisco 6100 Series system components:

Cisco 6100/6130 chassis
Cisco 6110 chassis
System controller module
DS3 subtend host module (STM)
OC-3c network interface module
DS3 network interface module
Quad-port flexi ATU-C (CAP or DMT) module
Dual-port CAP ATU-C modules or ports
Quad-port STU-C modules or ports---supported by the Cisco 6130 system only
Dual-port DMT-2 ATU-C modules or ports
LIMs or LIM ports
LIM controller modules

Deleting Modules with Discovered Attributes

The originally discovered module and its default configuration settings remain in the system configuration if you take either of the following actions:

Remove a module and leave the slot empty
Remove a module and insert a new module into the slot of the old module without unlocking the module

Likewise, if you modify a chassis ID dual in-line package (DIP) switch setting without following state management procedures, the Cisco 6100 Series SNMP agent stores only the original DIP switch settings.

In order for ViewRunner to discover the newly detected module with its correct configuration settings, you must first delete the old slot configuration. This deletion is necessary because the system controller module actively polls slots as part of fault detection. If you remove a module without following state management procedures, the system controller module assumes that the module is present, but has failed, and an alarm is generated. For more information on alarm management, refer to the Cisco 6100 Series with NI-1 Alarm Summary Guide.

For more detailed instructions on deleting modules, see "Deleting System Components."

How ViewRunner Presents Discovered Information

During discovery, ViewRunner queries the Cisco 6100 Series SNMP agent for the modules that have been discovered. After ViewRunner gets this information from the agent, ViewRunner displays the front chassis and module faceplates of the Cisco 6100 Series system on the GUI.

ViewRunner also supports querying the agent for discovered chassis or modules after the application has started. To use this option, click the Discover 6100 icon on the Chassis View, or choose Discover 6100 from the Edit menu. ViewRunner displays each of the chassis or module attributes described in the "Discovered Attributes" section.

Note ViewRunner does not display or support discovery of the Cisco 6120 POTS splitter chassis.

Figure 2-1 shows a sample display of discovered chassis and modules.

Figure 2-1: Cisco 6100 Series Chassis View

Table of Contents

Discovery