|
Max Hold Time elapsed
|
Maximum amount of time that has passed since the last BGP keepalive message was received from a neighbor before a BGP session is considered to be down.
|
|
Max Hold Time elapsed was 6001 msec at Sep 12 17:02:36.954, crossed 40%: 2, 70%: 0
|
Maximum amount of time that has passed since the last BGP keepalive message was received from a neighbor before a BGP session is considered to be down.
In this specific output, the fields indicate the following:
Max Hold Time elapsed was 6001 msec: indicates that the maximum time interval between receiving keepalive messages from the neighbor was 6001 milliseconds or approximately 6 seconds.
at Sep 12 17:02:36.954: Timestamp when this maximum hold time was observed.
crossed 40%: 2, 70%: 0: Number of times the hold time crossed certain thresholds. The hold time crossed the 40% threshold twice and the 70% threshold zero times, suggesting that the hold time reached a significant portion of its configured value but did not exceed it by a large margin.
|
|
Max Hold Time elapsed before reset was 9001 msec at Sep 12 17:01:53.397, crossed 40%: 7, 70%: 2
|
Maximum duration between receiving BGP (Border Gateway Protocol) keepalive messages from a neighbor before the BGP session was reset.
In this specific output, the fields indicate the following:
Max Hold Time elapsed before reset was 9001 msec: Maximum time interval between receiving keepalive messages from the neighbor before the BGP session reset was 9001 milliseconds or approximately 9 seconds.
at Sep 12 17:01:53.397: Timestamp when this maximum hold time before reset was observed.
crossed 40%: 7, 70%: 2: Number of times the hold time crossed certain thresholds. The hold time crossed the 40% threshold seven times and the 70% threshold two times, suggesting that the hold time frequently approached significant portions of its configured maximum value before the BGP session reset
|
|
First message received at Sep 12 16:45:00.973, sent at Sep 12 16:45:00.975
|
Timestamp when the first message from a BGP neighbor was received by the local router.
In this specific output, the fields indicate the following:
First message received at Sep 12 16:45:00.973: First message from the BGP neighbor was received at 16:45:00 on September 12th
sent at Sep 12 16:45:00.975: Timestamp when the corresponding message was sent by the BGP neighbor, which was nearly simultaneously, just 0.002 seconds later.
|
|
First message before reset received at Sep 12 16:42:16.573, sent at Sep 12 16:42:16.574
|
Timestamp when the first message from a BGP neighbor was received by the local router before a reset occurred.
In this specific output, the fields indicate the following:
First message before reset received at Sep 12 16:42:16.573: first message from the BGP neighbor was received at 16:42:16 on September 12th, before a reset occurred.
sent at Sep 12 16:42:16.574: Timestamp when the corresponding message was sent by the BGP neighbor, which was nearly simultaneous, just 0.001 seconds later.
|
|
Max read throttled duration was 6769 msec starting at Sep 12 16:45:01.487, max InQ 1000 processed 930
|
Maximum duration during which the read process was throttled, indicating a restriction or limitation on the rate of reading data.
In this specific output, the fields indicate the following:
Max read throttled duration was 6769 msec: Maximum duration of throttling for reading data was 6769 milliseconds (approximately 6.769 seconds).
starting at Sep 12 16:45:01.487: Timestamp when this maximum throttling duration started, which was at 16:45:01 on September 12th.
max InQ 1000 processed 930: Maximum input queue (InQ) size was 1000, and during the throttled duration, 930 items were processed.
|
| Start Time |
Timestamp when the read throttle period started.
|
|
Dry Run elapsed time(ms)
|
Time taken for the dry run in milliseconds.
|
|
Duration
|
Duration of the throttle period in milliseconds, indicating how long the read process was restricted or limited.
|
|
Max InQ
|
Maximum size of the input queue during the throttle period. The input queue typically holds incoming data packets waiting to be processed.
|
|
Messages
|
Number of messages or data packets processed during the throttle period.
|
|
Max read throttled duration before reset was 5013 msec starting at Sep 12 16:42:17.079, max InQ 76 processed 0
|
Maximum duration of a read throttle period on the network device.
In this specific output, the fields indicate the following:
Max read throttled duration before reset: Maximum duration of the read throttle period, which was 5013 milliseconds or approximately 5.013 seconds.
Starting at Sep 12 16:42:17.079: Timestamp when the read throttle period started, which was at 16:42:17 on September 12th
Max InQ 76 processed 0: The segment Max InQ 76 indicates that the maximum size of the input queue during the throttle period was 76. The segment processed 0 indicates that no messages or data packets were processed during this throttle period.
|
|
Max write throttled duration was 685 msec starting at Sep 12 16:45:08.486, max OutQ 1501 queued 57
|
Maximum duration of the write throttle period, which was 685 milliseconds.
In this specific output, the fields indicate the following:
Max write throttled duration: Maximum duration of the write throttle period, which was 685 milliseconds.
Starting at Sep 12 16:45:08.486: Timestamp when the write throttle period started, which was September 12th at 16:45:08.486.
Max OutQ: Maximum size of the output queue during the throttle period. In this case, it was 1501, which typically holds data packets waiting to be transmitted.
Queued: Number of items queued in the output queue during the throttle period. In this case, it was 57.
|
|
Max write throttled duration before reset was 205 msec starting at Sep 12 16:42:21.849, max OutQ 1003 queued 1
|
Maximum duration of a write throttle period on a network device before a reset occurred.
In this specific output, the fields indicate the following:
Max write throttled duration before reset: Maximum duration of the write throttle period before a reset occurred, which was 205 milliseconds.
Starting at Sep 12 16:42:21.849: Timestamp when the write throttle period started, which was on September 12th at 16:42:21.849.
Max OutQ: Maximum size of the output queue during the throttle period. In this case, it was 1003, indicating the maximum number of items that were waiting to be transmitted.
Queued: Number of items queued in the output queue during the throttle period. In this case, it was 1.
|
|
Start Time:
|
Timestamp when the write throttle period started.
|
|
Duration
|
Duration of the write throttle period in milliseconds.
|
|
Max OutQ
|
Maximum size of the output queue during the throttle period. The output queue typically holds data packets waiting to be transmitted.
|
|
Messages
|
Number of messages or data packets transmitted during the throttle period.
|