Brocade Fabric Manager Administrator's Guide (53-10000196-01-HP, November 2006)

Fabric Manager Administrator’s Guide 10-1

Publication Number: 53-1000196-01-HP

Chapter

Call Home Support

This chapter describes the call home feature of Fabric Manager and contains the following information:

• “About Call Home” on page 10-1

• “Configuring Call Home” on page 10-3

• “Editing Configurations” on page 10-4

• “Enabling or Disabling Call Home Globally” on page 10-5

• “Monitoring Call Home” on page 10-6

About Call Home

When you enable the call home feature, Fabric Manager monitors the status of switches continuously

and generates call home alerts whenever a call home triggering event occurs.

Triggering events include the following:

• Switch status changes to either marginal or down

• Switch status remains marginal or down but the reason for the status changes

• Switch reboots

• Switch is unreachable (complete loss of IP connectivity)

All qualifying events trigger a call home action, and the status of each call home action is recorded in

the following file:

<installdir>/server/server/fmserver/log/callhomehistory.log

You can view the call home alerts in Fabric Manager. You can also configure call home to send an email

message to a user-defined email address and run an external executable whenever a call home triggering

event occurs.

You can configure call home to optionally capture support information (supportShow or supportSave)

when a triggering event occurs. Fabric Manager can capture supportSave information only for switches

running Fabric OS v5.2.0 or higher. The supportShow and supportSave information is collected in the

location of the built-in or external FTP server.

Each call home alert includes the reason for the alert, a brief description of the failure, and detailed

switch information (including the name, IP address, WWN, domain ID, switch type, factory and

supplier serial numbers, firmware version, switch status, and other information). The alert also includes

the 100 most-recent events from the event log and supportShow command output in a text file.