Performance State; Perflostcomms State; Discovery Lostcomms State - Cisco WS-C3550-12G User Manual

Chapter 2 Basic Concepts

Performance State

This state applies all physical objects that support Performance Logging. When you enable performance
logging on an object in the normal state, the object is moved into the performance state. Specific
performance data is collected on the object and can be viewed in the Performance Manager. You can
enable performance logging on a global scale or on an individual interface basis. Enabling global
performance logging puts all subchassis objects into the performance state.
Performance logging occurs at the specified interval. When you initially enable performance logging or
global performance logging on an object, it takes a period of time up to the length of the interval for the
data to be collected and become visible in Cisco Catalyst Switch Manager performance menus.
Heartbeat polling is performed on an object in the performance state. If the object moves into the
lostcomms state, it is returned to the performance state when the error is corrected. For example, if a
module is in the performance state and it fails, it moves into the lostcomms state. When heartbeat polling
finds the module is back up, it restores the module to the performance state.
There are three transitions out of the performance state:
•
•
•

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 transitions
can be made out of this 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.
OL-4930-01
If communication to the object is lost while the object is in the performance state, the state transition
is into the perflostcomms state.
To turn off the object's performance logging, you can send the object the normal stimulus. The
transition is to the normal state.
If heartbeat polling determines that connectivity is lost or changes have been made to the object, the
transition is to the discovery state. Once discovery is completed successfully, the object transitions
back to the performance 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 transition is immediately to the normal lostcomms state.
Cisco Catalyst Switch Manager Object States
Cisco Catalyst Switch Manager User Guide
2-13