HP StorageWorks 2/16V Brocade Fabric OS MIB Reference - Supporting Fabric OS 5 - Page 21

Understanding Snmp Traps, Fa Traps - san switch

Page 21 highlights

Understanding SNMP Basics 1 • read-only - Public You can only monitor information. • read-write - Private You can read or modify this variable. UNDERSTANDING SNMP TRAPS An unsolicited message that comes to the management station from the SNMP agent on the device is called a trap. Brocade switches send traps out on UDP port 162 only, therefore an SNMP management application must be running on UDP port 162. In order to receive traps, the management station IP address and severity level must be configured on the switch. Up to six trap recipients can be configured using Web Tools or the snmpConfig command. You can define a different message severity level for each recipient so that some recipients receive all trap messages and others receive only the most critical. There are two main MIB trap choices: • FibreAlliance MIB trap - Associated with the Fibre Alliance MIB (FA-MIB), this MIB manages SAN switches and devices from any company that complies with Fibre Alliance specifications. • Brocade-specific MIB trap - Associated with the Brocade-specific Brocade MIB (SW-MIB), manages Brocade switches only. There is some overlap in the functionality of these MIBs. If you enable both SW-MIB and FA-MIB traps, you could receive duplicate messages for the switch events that trigger the trap. You can also use these additional MIBs and their associated traps: HA-MIB; FICON-MIB; and SW-EXTTRA. You can use the snmpConfig command to disable the FA-MIB, HA-MIB, FICON-MIB, and SW_EXTTRA; but neither the SW-MIB or the FE-MIB can be disabled. An event trap (swEventTrap, connUnitEventTrap, or swFabricWatchTrap) is basically an error message (errShow output) that is SNMP-formatted and delivered. FA Traps Consider enabling the FA traps if you want to use SNMP to monitor multiple connectivity units, including Brocade switches. The switchStatusPolicySet command determines the FA-TRAP switch status-related outputs: • connUnitStatusChange • connUnitSensorStatusChange • connUnitPortStatusChange The MIB-II system description swEventTrapLevel determines the output for the connUnitEventTrap. Events in the Error Log of a severity at or above the configured threshold will generate SNMP traps. The Fibre Alliance Trap (FA-TRAP) can be configured to send traps using the snmpConfig command. See the Fabric OS Command Reference for more information on this command. Fabric OS MIB Reference 5 53-1000439-01

  • 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
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296

Fabric OS MIB Reference
5
53-1000439-01
Understanding SNMP Basics
1
read-only -
Public
You can only monitor information.
read-write -
Private
You can read or modify this variable.
UNDERSTANDING SNMP TRAPS
An unsolicited message that comes to the management station from the SNMP agent on the
device is called a
trap
. Brocade switches send traps out on UDP port 162 only, therefore an SNMP
management application must be running on UDP port 162. In order to receive traps, the
management station IP address and severity level must be configured on the switch. Up to six trap
recipients can be configured using Web Tools or the
snmpConfig
command. You can define a
different message severity level for each recipient so that some recipients receive all trap
messages and others receive only the most critical.
There are two main MIB trap choices:
FibreAlliance MIB trap - Associated with the Fibre Alliance MIB (FA-MIB), this MIB manages SAN
switches and devices from any company that complies with Fibre Alliance specifications.
Brocade-specific MIB trap - Associated with the Brocade-specific Brocade MIB (SW-MIB),
manages Brocade switches only.
There is some overlap in the functionality of these MIBs. If you enable both SW-MIB and FA-MIB
traps, you could receive duplicate messages for the switch events that trigger the trap.
You can also use these additional MIBs and their associated traps: HA-MIB; FICON-MIB; and
SW-EXTTRA. You can use the
snmpConfig
command to disable the FA-MIB, HA-MIB, FICON-MIB, and
SW_EXTTRA; but neither the SW-MIB or the FE-MIB can be disabled.
An event trap (swEventTrap, connUnitEventTrap, or swFabricWatchTrap) is basically an error
message (
errShow
output) that is SNMP-formatted and delivered.
FA Traps
Consider enabling the FA traps if you want to use SNMP to monitor multiple connectivity units,
including Brocade switches.
The
switchStatusPolicySet
command determines the FA-TRAP switch status-related outputs:
connUnitStatusChange
connUnitSensorStatusChange
connUnitPortStatusChange
The MIB-II system description swEventTrapLevel determines the output for the connUnitEventTrap.
Events in the Error Log of a severity at or above the configured threshold will generate SNMP traps.
The Fibre Alliance Trap (FA-TRAP) can be configured to send traps using the
snmpConfig
command.
See the
Fabric OS Command Reference
for more information on this command.