Brocade BigIron RX Series Configuration Guide - Manual (Page 1058)

980 BigIron RX Series Configuration Guide
53-1002484-04
Clearing IS-IS information
29
Clearing IS-IS information
To clear the IS-IS information that the device has accumulated since the last time you cleared
information or reloaded the software, use either of the following methods.
To clear IS-IS information, enter a command such as the following at any level of the CLI except the
User EXEC level.
BigIron RX# clear isis all
This command clears all the following.
• Neighbors (closes the BigIron RX’s adjacencies with its IS-IS neighbors)
• Routes
• PDU statistics
• Error statistics
Syntax: clear isis all | counts | neighbor | route [<ip-address> <subnet-mask> |
<ip-address>/<prefix>] | traffic
The all parameter clears all the IS-IS information. Using this option is equivalent to entering
separate commands with each of the other options.
The counts parameter clears the error statistics.
LSP Sequence Number Skipped The number of times the device received an LSP with a sequence
number that was more than 1 higher than the sequence number of the
previous LSP received from the same neighbor.
LSP Max Sequence Number Exceeded The number of times the device attempted to set an LSP sequence
number to a value higher than the highest number in the CSNP sent by
the Designated IS.
Level-1 Database Overload The number of times the Level-1 state on the device changed from
Waiting to On or from On to Waiting.
•
Waiting to On – This change can occur when the device recovers
from a previous Level-1 LSP database overload and is again ready
to receive new LSPs.
•
On to Waiting – This change can occur when the device’s Level-1
LSP database is full and the device receives an additional LSP, for
which there is no room.
Level-2 Database Overload The number of times the Level-2 state on the device changed from
Waiting to On or from On to Waiting.
•
The change from Waiting to On can occur when the device recovers
from a previous Level-2 LSP database overload and is again ready
to receive new LSPs.
•
The change from On to Waiting can occur when the device’s Level-2
LSP database is full and the device receives an additional LSP, for
which there is no room.
Our LSP Purged The number of times the device received an LSP that was originated by
the device itself and had age zero (aged out).
TABLE 154 IS-IS error statistics (Continued)
This field... Displays...