Cisco Systems 8500 manual Lost Comms No Poll, Discovery Lost Comms, Mismatched

Chapter 1 Concepts

Object States

Lost Comms

The lost comms (lost communications) state indicates that the object is not responding to heartbeat polling. The EM can apply this state to a chassis, module, or interface. When an object is in the lost comms state, heartbeat polling occurs on the object. When the object responds to heartbeat polling, it moves out of the lost comms state. For example, say an ATM module in the EM was predeployed. When you perform device synchronization (commissioning a chassis), the ATM module is not yet physically present in the hardware. In this situation, the EM places the ATM module into the lost comms state, where it continues to poll for the presence of the module. When the ATM module is inserted into the chassis, the EM detects its presence and moves the module out of the lost comms state and into a respective state (typically normal).

Lost Comms No Poll

The lost comms (lost communications) no poll state occurs when the router is not contactable. When the EM loses connectivity with a device, the representative chassis object remains in the lost comms state so that heartbeat polling continues on the chassis. However, all modules and interfaces within that chassis move into a lost comms no poll state. There is no point in polling modules and interfaces within a device that is not contactable. If the connection with the device is down, all modules and interfaces will be down. When the device becomes contactable again, the chassis, modules, and interfaces are moved out of the lost comms no poll state.

Discovery Lost Comms

The discovery lost comms state occurs only during subchassis discovery. If, for example, you commission a chassis (which begins the process of subchassis discovery) and a module discovers with a faulty connection, the module goes into the discovery lost comms state. When connectivity establishes with the corresponding object in the device, subchassis discovery resumes, and the object moves out of the discovery lost comms state.

Mismatched

The mismatched state occurs when a mismatch is found between what hardware is in the device and that which is deployed in the EM. For example, say you are expecting an ATM OC–3 module so you predeploy and perform offline configuration in the EM to prepare for that type of module. However, when the module becomes available in the chassis, it is not an ATM OC–3 module but an OC–12 module. When the EM detects the new module, it finds a mismatch. The module is put into the mismatch state and a major alarm raises against the module.

To rectify a mismatch problem, first you must assess the source of the problem. If the operator was at fault and predeployed an incorrect module, the operator should delete the predeployed module and re–deploy the correct module. If the person who inserted the module is at fault because they inserted the wrong type of module into the chassis, the module should be removed. When you remove a module, the EM moves the module into a lost comms state. Inserting the correct module enables the EM to find the new module and download the correct pre–deployment and offline configuration information, then places the module into its respective state (typically normal).

Mismatch can also occur on a chassis. If, during deployment of a chassis, an incorrect IP address is entered, the EM cannot discover the chassis due to an erroneous IP address that was entered during the commissioning process. Because of this, discovery fails, a major alarm is raised against the chassis, and

Cisco Catalyst 8500 Manager User Guide

1-19