Discovery

This chapter explains the discovery process and gives a list of equipment and data elements that are discovered for this release.

ViewRunner discovery is the process of ViewRunner learning the 6100 configuration and status details. By default, ViewRunner automatically discovers a node when the user opens a chassis view window. This option may be enabled or disabled on the Options >ViewRunner Preferences menu.

In addition, ViewRunner discovery can be manually invoked via the Discovery menu option. When ViewRunner discovers a node, it redraws the chassis view with the updated configuration.

ViewRunner for Windows queries the SC (using the SNMP get command) for the MIB values when the system starts up or when prompted by the user. After new modules are installed, the user must use the Discover menu option in ViewRunner for them to appear in the chassis view.

2.2 Cisco 6100 Auto-Discovery

Auto-discovery within the Cisco 6100 is the automated process by which the SC captures inventory and configuration information about Cisco 6100 chassis and modules. Auto-discovery is performed whenever a module is inserted into the Cisco 6100 system, or when the system controller (SC) is reset.

During auto-discovery, the following steps take place within the Cisco 6100 system:

Each inserted module conducts a self test to check for hardware malfunctions.
If malfunctions are found, the module does not send a message to the SC, and auto-discovery fails. Faulty modules are recognizable by certain LED conditions on the module faceplate. For more information on LED indicators, see the Cisco 6100 Set Up and Installation Manual.
If no malfunctions are found, the module notifies the SC that it is present by passing relevant inventory attributes to the SC.
Once the SC gets inventory information, it captures the system configuration and stores auto-discovered attributes and other default configuration in a Management Information Base (MIB) within the SNMP agent.

2.2.1 Auto-Discovered Attributes

Each module and chassis is equipped with a Flash memory EEPROM programmed at the factory with the following read-only attributes:

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

These attributes are sent to the SC during the auto-discovery process.

ATU-C modules also return the following transceiver information:

: Max Upstream Rate Supported - Maximum upstream rate supported by the ATU-C module.
: Max Downstream Rate Supported - Maximum downstream rate supported by the ATU-C module.
: Line Coding - Modulation technique supported by modem ports (CAP).
: Connect Mode - the jumper setting of ATU-C module indicating whether the system is configured as Digital Off-Hook (DOH standard) or Direct Connect.

Note ATU-C module jumpering is related to configuration styles. See the Cisco 6100 Set Up and Installation Manual for more information. All ATU-C cards must be jumpered in the same mode for the system to operate.

2.2.2 Auto-Discovered Configuration Defaults

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

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

Chassis presence is detected by hardware.
Module presence is detected at insertion time or after a module has been reset by Cisco 6100 software.

2.2.3 Auto-Discovered Equipment

The ViewRunner infers the presence of a Cisco 6100 multiplexer chassis (MC) if a SC is present. The Cisco 6100 requires that a LIM controller module be equipped in the 6110 line concentration chassis (LCC) if the LCC is present. The line interface module (LIM) controller forwards all LIM notifications to the SC.

The following table lists Cisco 6100 components that are auto-discovered by ViewRunner

.
Table 2-1: Auto-Discovered Components

Auto-Discovered Equipment

MC¹ (6100 multiplexer chassis)

LCC (6110 line concentration chassis)

SC module (system controller)

DS3 STM²

OC3 NI module (network interface)

DS3 NI module (network interface)

ATU-C modules/ports

LIM modules/ports

LIM controller modules

¹multiplexer chassis
²subtend host module

Auto-Discovered Equipment
MC¹ (6100 multiplexer chassis)
LCC (6110 line concentration chassis)
SC module (system controller)
DS3 STM²
OC3 NI module (network interface)
DS3 NI module (network interface)
ATU-C modules/ports
LIM modules/ports
LIM controller modules

2.3 Adding and Deleting Modules with Auto-Discovered Attributes

If you remove a module and either leave the slot empty or insert a new module into the slot of the old module without following state management procedures (see "Cisco 6100 and ViewRunner State Management"), the originally auto-discovered module and its default configuration settings remain in the system configuration. Likewise, if you modify a chassis ID DIP switch setting without following state management procedures, only the original DIP switch settings are stored by the Cisco 6100 SNMP agent.

For the newly-detected module to be correctly discovered with its correct configuration settings, it is necessary to first delete the old slot configuration because the SC actively polls slots as part of fault detection. If a module has been removed without following state management procedures, the SC assumes the module is present, but has failed, and an alarm will be generated. For more information on alarm management, see the Cisco 6100 Maintenance and Troubleshooting Manual.

For instructions on adding and deleting modules, see "Adding and Deleting System Components."

2.4 ViewRunner Presentation of Auto-Discovered Information

During discovery, ViewRunner for Windows queries the Cisco 6100 SNMP agent (MIB) for the modules that have been auto-discovered. Once ViewRunner for Windows gets this information from the agent, it displays the front chassis and module faceplates of the Cisco 6100 in its graphical user interface.

ViewRunner for Windows also supports querying the agent for auto-discovered chassis/modules after the application has started. This is done by selecting the Discover menu option on the main menu of the ViewRunner or from the Discover icon in the Chassis View. ViewRunner for Windows displays each of the chassis/module attributes described above.

Note ViewRunner does not support auto-discovery or a display of the POTS splitter chassis (PSC).

The following diagram shows an example display of auto-discovered chassis and modules:

Figure 2-1: Cisco 6100 Chassis View

Table of Contents

Discovery