Compaq Armada 6500 Compaq Storage Hub 12 Management Utilities Hardware and Sof - Page 39

Broadcast Storm Diagnostic, Initialization Frequency, Consecutive Windows, Loop Init Count

Get Compaq Armada 6500 - Notebook PC PDF manuals and user guides View all Compaq Armada 6500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 39 highlights

2-16 Compaq Storage Hub 12 Management Utilities Hardware and Software User Guide Initialization Frequency is the second criterion. This trigger is designed to detect a loop that is continuously initializing and consists of three parts: Initialization Count is the number of times loop initialization detection must occur within a defined window of time in order to trigger the diagnostic. A defined parameter of zero disables the diagnostic process, and should not be used. Initialization Window (sec) is the definition of just how long a window lasts in seconds. Consecutive Windows is the number of consecutive initialized windows that are detected in the Loop Init Count parameter in order to trigger the diagnostic. An example of Initialization Frequency criterion using specific values is the detection of at least one loop initialization for five consecutive one second periods. When this condition is detected, the Loop Initialization Diagnostic will be spawned. NOTE: The use of zero effectively disables the diagnostics, so always use a value of 1 or greater. Broadcast Storm Diagnostic Like the Loop Initialization Diagnostic, the Broadcast Storm Diagnostic appears whenever there is trouble. However this diagnostic is specifically designed to find whatever device is broadcasting a continuous stream of primitives. Continuous streams of primitives represent atypical behavior and will keep the network from initializing. This diagnostic tool will lead the user through a step-by-step set of actions to identify and isolate the faulty node.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
2-16
Compaq Storage Hub 12 Management Utilities Hardware and Software User Guide
■
Initialization Frequency
is the second criterion. This trigger is
designed to detect a loop that is continuously initializing and
consists of
three parts:
Initialization Count
is the number of times loop initialization
detection must occur within a defined window of time in order to
trigger the diagnostic. A defined parameter of zero disables the
diagnostic process, and should not be used.
Initialization Window
(sec) is the definition of just how long a
window lasts in seconds.
Consecutive Windows
is the number of consecutive initialized
windows that are detected in the
Loop Init Count
parameter in
order to trigger the diagnostic.
An example of
Initialization Frequency
criterion using specific values is the
detection of at least one loop initialization for five consecutive one second
periods. When this condition is detected, the Loop Initialization Diagnostic
will be spawned.
NOTE:
The use of zero effectively disables the diagnostics, so always use a value of 1 or
greater.
Broadcast Storm Diagnostic
Like the Loop Initialization Diagnostic, the Broadcast Storm Diagnostic
appears whenever there is trouble. However this diagnostic is specifically
designed to find whatever device is broadcasting a continuous stream of
primitives. Continuous streams of primitives represent atypical behavior and
will keep the network from initializing. This diagnostic tool will lead the user
through a step-by-step set of actions to identify and isolate the faulty node.