Cisco 6506-E User Guide - Page 38

C65/76M Object States Chapter 2 Basic Concepts Perflostcomms State This state applies all physical objects that support Performance Logging. This state indicates that communication has been lost to an object that was formerly in the performance state. Two transistions can be made out of this state: • If communication is restored, the object transitions back to the performance state. • While this object is still in the perflostcomms state, if the object is stimulated to deactivate performance logging, then the transistion is immediately to the normal lostcomms state. If communication to an object is lost, it moves into the lostcomms state. In this state, performance polling (if activated) is stopped; however, heartbeat polling continues, until the object responds positively to a heartbeat request. Heartbeat polling polls an object every five minutes to verify its existence and current state. When the object can be contacted again, it responds positively to heartbeat requests, and then moves back into the previously held state. Discovery Lostcomms State The discovery lostcomms state applies to Network Element, Software and Chassis objects. This state is similar to the lostcomms state, except that it only occurs during the discovery process. When connectivity is established with the corresponding object in the device, the discovery is resumed and the object moves out of the discovery lostcomms state. Mismatched State The mismatched state occurs when a mismatch is found between the type of hardware discovered and what is predeployed in CEMF. For example, if a 48-port 10/100TX, RJ-45 module is expected, the module is predeployed in CEMF to prepare for that type of module. However, when the module becomes available and is placed into the chassis, it is not a 48-port 10/100TX, RJ-45 module, but an 8-port Gigabit Ethernet module. After the C65/76M detects the new module, it finds a mismatch. The module gets placed into the mismatched state and an alarm is raised against the module. To correct a mismatch problem, the source of the problem must be assessed. If the operator was at fault and predeployed an incorrect module, the operator should delete the predeployed module and deploy the correct module. If the engineer is at fault and inserted the wrong type of module into the chassis, then the module should be removed and replaced. The mismatched state applies to the following objects: • Network element • All modules • Port Adapters • Channelized SONET subinterfaces For the Network Element object, the mismatched state indicates that there is a major difference between the CEMF information and the actual Catalyst 6000 family switch or a Cisco 7600 series Internet Router. This mismatch can be in the major switch series (e.g. 6000, 6500 or 7600), the specific model of the switch (e.g. 6506, 6509 or 6513) or the type of software installation on the switch (Catalyst OS, Hybrid OS or Native IOS). 2-10 Cisco 6500/7600 Series Manager User Guide