The Integrity History section lists: the integrity of nodes and subsystems for the current session that initially had faulty integrity; and all integrity transitions such as going good, going bad; and the time the integrity transition occurred. This list can be printed and saved to a file. Possible values for integrity include:
|
Value |
Indicator |
|
Good |
None |
|
Bad |
|
|
No Configuration |
|
|
Not Connected |
|
|
Unknown |
|
|
Logic Solver Integrity Bad |
|
Typically, integrity problems originate below the node and then "bubble up" to the node level. For example, integrity of a channel affects integrity of a card, which affects integrity of the I/O subsystem, which affects integrity of the node. Each transition is logged in the Integrity History section.
The Integrity History saves up to 500 messages. When 490 messages are detected, Diagnostics posts a message in the Integrity History section informing you that after 10 more messages older messages will automatically be deleted from the display unless you Save or Delete the messages. If you do not save or delete after 500 messages, Diagnostics overwrites the older messages and precedes new messages with an asterisk (*), indicating that older messages are being deleted to make room for newer messages.