Configuring FabricWatch

---

DRAFT

---

First, setup your Email relay system:

SanSW1:admin> fwMailCfg
1  : Show Mail Configuration Information
2  : Disable Email Alert
3  : Enable Email Alert
4  : Send Test Mail
5  : Set Recipient Mail Address for Email Alert
6  : Relay Host IP Configuration
7  : Quit
Select an item  => : (1..7) [7]

Select 6 to configure the relay host:

1 Display Relay Host configuration
2 Set Relay Host IP
3 Remove Relay Host configuration
4 Quit

Select 2 to configure the Host IP (and I do mean IP, not the DNS name):

enter the Relay Host IP:
192.168.1.1
Setting 192.168.1.1 as Relay Host..
enter the Domain Name:
domain.net

And, select 4 to exit to the main fwMailCfg screen. Next, set the Email recipient, select 5 from the main fwMailCfg screen:

Mail Config  Menu
___________________________
1  : Environment class
2  : SFP class
3  : Port class
4  : Fabric class
5  : E-Port class
6  : F/FL Port (Optical) class
7  : ALPA Performance Monitor class
8  : End-to-End Performance Monitor class
9  : Filter Performance Monitor class
10 : Security class
11 : Resource Monitor class
12 : FRU class
13 : Quit
Select an item  => : (1..13) [13]

Select the class you want to monitor (Port class has a lot of good errors in it), and enter the Email address of the recipient:

Mail To: [patrickv@domain.net] my@email.com

Be sure to select 3 from the main screen to enable Email alerts, then you can select 4 to send a test Email. With any luck you’ll get an email within a minute or two.

Next, we need to configure the alarm levels.

OpsSanSW2:admin> fwconfigure

1  : Environment class
2  : SFP class
3  : Port class
4  : Fabric class
5  : E-Port class
6  : F/FL Port (Optical) class
7  : Alpa Performance Monitor class
8  : EE Performance Monitor class
9  : Filter Performance Monitor class
10 : Security class
11 : Resource class
12 : Quit
Select a class => : (1..12) [12]

Select the class to modify

Select a class => : (1..12) [12] 3

1  : Link loss
2  : Sync loss
3  : Signal loss
4  : Protocol error
5  : Invalid words
6  : Invalid CRCS
7  : RXPerformance
8  : TXPerformance
9  : State Changes
10 : return to previous page
Select an area => : (1..10) [10]

Select the area of the class to modify:

1 : refresh
2 : disable a threshold
3 : enable a threshold
4 : advanced configuration
5 : return to previous page
Select choice => : (1..5) [5]

Select advanced configuration:

Threshold boundary level is set at : Default

                 Default        Custom
      Unit      Error(s)      Error(s)
 Time base        minute        minute
       Low             0             0
      High          1000          1000
   BufSize           100           100

Threshold alarm level is set at : Default

Errlog-1, SnmpTrap-2, PortLogLock-4
RapiTrap-8, EmailAlert-16, PortFencing-32

Valid alarm matrix is 63

                 Default        Custom
   Changed             0             0
     Below             0             0
     Above             0             0
 InBetween             0             0

1  : change behavior type             11 : change threshold alarm level
2  : change behavior interval         12 : change changed alarm
3  : change threshold boundary level  13 : change below alarm
4  : change custom unit               14 : change above alarm
5  : change custom time base          15 : change inBetween alarm
6  : change custom low                16 : apply threshold alarm changes
7  : change custom high               17 : cancel threshold alarm changes
8  : change custom buffer             18 : return to previous page
9  : apply threshold boundary changes
10 : cancel threshold boundary changes
Select choice => : (1..18) [18]

Set the high threshold:

Select choice => : (1..18) [18] 7
Enter high threshold => : (0..999999999) [1000] 100

The buffer setting isn’t very well described in some of the books. The way I read it is that the alarm won’t trigger another alert until the level has hit between the high threshold – the buffer and the low threshold + the buffer. It’s a way to to reduce the number of alarms generated. Set the buffer:

Select choice => : (1..18) [18] 8
Enter buffer size => : (0..50) [50] 5

Set the alarm action:

Select choice => : (1..18) [18] 14

Errlog-1, SnmpTrap-2, PortLogLock-4
RapiTrap-8, EmailAlert-16, PortFencing-32

Valid alarm matrix is 63
Enter above alarm matrix => : (0..63) [0] 21

Set the threshold boundry and alarm levels to custom:

Select choice => : (1..18) [18] 3
1  : Default
2  : custom
Enter boundary level type => : (1..2) [2] 2
...
Select choice => : (1..18) [18] 11
1  : Default
2  : custom
Enter alarm level type => : (1..2) [1] 2

Apply changes ( 9 and 16).

Configure FabricWatch for FRU’s to be notified of power supply, fan, or blade failures:

OpsSanSW1:admin> fwfrucfg

The current FRU configuration:
                  Alarm State     Alarm Action
-----------------------------------------------
            Slot       27               17
    Power Supply       24               17
             Fan       24               17
             WWN        1                1

Note that the value 0 for a parameter means that
it is NOT used in the calculation

Configurable Alarm States are:
Absent-1, Inserted-2, On-4, Off-8, Faulty-16

Configurable Alarm Actions are:
Errlog-1, E-mail-16
Slot Alarm State: (0..31) [27]