HP StorageWorks MSA 2/8 HP StorageWorks Fabric Watch V3.1.x/4.1.x User Guide ( - Page 190

PortStatus, MissingSFPs, affect the state of the switch.

Page 190 highlights

Fabric Watch Telnet Commands Operands Any single contributor can force the overall status of the switch to MARGINAL or DOWN. For example, assuming that the switch contributor values are set to the default values, if there is 1 faulty port in a switch, then this contributor would set the overall switch status to MARGINAL. If 2 ports were faulty, then this contributor would set the overall switch status to DOWN. This command enables you to set a threshold for each contributor, so that a certain number of failures are required to change the overall status of the switch. If the value of a policy parameter is set to 0, it means that this factor is not used to determine the status of the switch. If the range of values for a particular contributor are set to 0 for both MARGINAL and DOWN, that contributor is not used in the calculation of the overall switch status. ISLStatus monitors ISLs that are part of a defined switch group. The status of other ISLs on the same switch but outside of the group definition will not be considered when calculating switch status. If no switch groups are defined on this switch, then these ISLStatus settings will have no effect on switch status. The ISLStatus does not affect the status of the switch as quickly as the other contributors. It may take a few minutes for a switch group ISL status change to affect the state of the switch. When PortStatus monitoring is set to values of (0,0), port status changes are not logged to the event log and console. Similarly, SFP removal does not generate a message to the event log and console if MissingSFPs is set to (0,0). By configuring these options, the user can more closely monitor for port status and/or removal of SFPs. None. 190 Fabric Watch Version 3.1.x/4.1.x User Guide

  • 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
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267

Fabric Watch Telnet Commands
190
Fabric Watch Version 3.1.x/4.1.x User Guide
Any single contributor can force the overall status of the switch to MARGINAL or
DOWN. For example, assuming that the switch contributor values are set to the
default values, if there is 1 faulty port in a switch, then this contributor would set
the overall switch status to MARGINAL. If 2 ports were faulty, then this
contributor would set the overall switch status to DOWN.
This command enables you to set a threshold for each contributor, so that a certain
number of failures are required to change the overall status of the switch.
If the value of a policy parameter is set to 0, it means that this factor is not used to
determine the status of the switch. If the range of values for a particular
contributor are set to 0 for both MARGINAL and DOWN, that contributor is not
used in the calculation of the overall switch status.
ISLStatus monitors ISLs that are part of a defined switch group. The status of
other ISLs on the same switch but outside of the group definition will not be
considered when calculating switch status. If no switch groups are defined on this
switch, then these ISLStatus settings will have no effect on switch status.
The ISLStatus does not affect the status of the switch as quickly as the other
contributors. It may take a few minutes for a switch group ISL status change to
affect the state of the switch.
When
PortStatus
monitoring is set to values of (0,0), port status changes are not
logged to the event log and console. Similarly, SFP removal does not generate a
message to the event log and console if
MissingSFPs
is set to (0,0). By
configuring these options, the user can more closely monitor for port status and/or
removal of SFPs.
Operands
None.