HP StorageWorks 2/16V Brocade Fabric Watch Administrator's Guide - Supporting - Page 59

Configuring alarm notifications, Configuring Port Log Lock actions, Step 3: Con alarms

Page 59 highlights

Configuring notifications 3 • "Configuring SNMP notifications" on page 43 • "Configuring API notifications" on page 43 • "Configuring Port Log Lock actions" on page 44 • "Configuring E-mail notifications" on page 44 CONFIGURING ALARM NOTIFICATIONS When you use alarm notifications, error messages are sent to designated locations such as an error log, SNMP trap view, or e-mail. With an error log, you can log in to a particular switch to view the error messages that have been captured for that particular switch. You can parse the log file to make error message searches quicker and easier. To ensure that notifications appear in the error log, use the following command: swd77:admin> fwAlarmsFilterSet 1 The option 1 turns on the alarm notification. If you decide not to have notifications sent, use the following command: swd77:admin> fwAlarmsFilterSet 0 The option 0 turns the alarm notification off. All alarms are suppressed when alarm notifications are turned off, except for the Environment class and Resource class. To verify or view your current alarm notifications, use the fwAlarmsFilterShow command. swd77:admin> fwalarmsfiltershow FW: Alarms are enabled CONFIGURING SNMP NOTIFICATIONS In environments in which you have a high number of messages (for example, hundreds per day) coming from a variety of switches, you might want to receive them in a single location and view them using a graphical user interface (GUI). In this type of scenario, SNMP notifications might be the most efficient notification method. You can avoid having to log on to each switch individually as you would have to do for error log notifications. SNMP notifications are configured using snmpMibCapSet, and within Fabric Watch, using alarms. See "Step 3: Configure alarms" on page 37 for details about setting alarms. For details about SNMP configuration, including traps, see the agtCfgSet and snmpConFig commands in the Fabric OS Command Reference and the Fabric OS Administrator's Guide. CONFIGURING API NOTIFICATIONS In the Brocade Fabric OS API, notifications are triggered programatically. The Brocade Fabric OS API is an application programming interface (API) that provides the method for any application to access critical information about a Brocade SAN. Using Fabric OS API, an application can query or control individual switches or the entire fabric. You can also configure API notifications using the Brocade Fabric OS API. Fabric Watch Administrator's Guide 43 53-0000438-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

Fabric Watch Administrator’s Guide
43
53-0000438-01
Configuring notifications
3
“Configuring SNMP notifications”
on page 43
“Configuring API notifications”
on page 43
“Configuring Port Log Lock actions”
on page 44
“Configuring E-mail notifications”
on page 44
CONFIGURING ALARM NOTIFICATIONS
When you use alarm notifications, error messages are sent to designated locations such as an
error log, SNMP trap view, or e-mail. With an error log, you can log in to a particular switch to view
the error messages that have been captured for that particular switch. You can parse the log file to
make error message searches quicker and easier.
To ensure that notifications appear in the error log, use the following command:
swd77:admin>
fwAlarmsFilterSet
1
The option
1
turns on the alarm notification.
If you decide not to have notifications sent, use the following command:
swd77:admin>
fwAlarmsFilterSet
0
The option
0
turns the alarm notification off.
All alarms are suppressed when alarm notifications are turned off, except for the Environment
class and Resource class.
To verify or view your current alarm notifications, use the
fwAlarmsFilterShow
command.
swd77:admin>
fwalarmsfiltershow
FW: Alarms are enabled
CONFIGURING SNMP NOTIFICATIONS
In environments in which you have a high number of messages (for example, hundreds per day)
coming from a variety of switches, you might want to receive them in a single location and view
them using a graphical user interface (GUI). In this type of scenario, SNMP notifications might be
the most efficient notification method. You can avoid having to log on to each switch individually as
you would have to do for error log notifications.
SNMP notifications are configured using
snmpMibCapSet
, and within Fabric Watch, using alarms.
See
“Step 3: Configure alarms”
on page 37 for details about setting alarms.
For details about SNMP configuration, including traps, see the
agtCfgSet
and
snmpConFig
commands in the
Fabric OS Command Reference
and the
Fabric OS Administrator’s Guide
.
CONFIGURING API NOTIFICATIONS
In the Brocade Fabric OS API, notifications are triggered programatically.
The Brocade Fabric OS API is an application programming interface (API) that provides the method
for any application to access critical information about a Brocade SAN. Using Fabric OS API, an
application can query or control individual switches or the entire fabric. You can also configure API
notifications using the Brocade Fabric OS API.