22.10.2013 Views

7.8.1.0 - Force10 Networks

7.8.1.0 - Force10 Networks

7.8.1.0 - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Using FTSA for Event Handling<br />

The purpose of FTSA is to automatically send information about the switch to troubleshooters, so that, if a<br />

problem arises, that information can be used to help assess the problem. As mentioned in the chapter<br />

introduction, FTSA now has two parallel lines of functionality:<br />

• Inventory messages: After you start FTSA, FTSA runs in the background on the switch, periodically<br />

collecting status information and sending it by email to <strong>Force10</strong> Support or any recipients that you<br />

designate, as described above. After you start and configure FTSA, you should not need to do anything<br />

to manage inventory messages unless you want to modify the configuration. See Specifying the<br />

frequency of FTSA inventory messages on page 290.<br />

• Event-based messages: Starting with FTOS 7.7.1.0, FTSA can also send or log event-based<br />

information, of three types:<br />

• System log messages, discussed next<br />

• System failover: These kinds of events can be handled either with the Exception set of tests<br />

and actions, as described in Table 13 on page 295, or with a custom test and action set.<br />

• Capture and act upon system information based on test conditions. See Configuring Policies<br />

on page 292.<br />

Configuring the capture of system log messages<br />

FTSA can collect and send system log messages (in type-4 messages—see Figure 173 on page 303)<br />

containing a subset of information from the system log. The information stored with the FTSA server<br />

configuration that you selected in Configuring FTSA Communications on page 285. You can set the<br />

severity of the log messages to collect. Of course, FTSA cannot find messages to collect if you have set a<br />

system logging severity level lower than the severity level that you set with this command.<br />

Command Syntax Command Mode Purpose<br />

[no] log-messages [delay<br />

60–1440] [severity 0–7] [filter<br />

word]<br />

CONFIGURATION<br />

(conf-callhome-serv<br />

er-name)<br />

An example of a type-4 message is shown in Figure 173 on page 303.<br />

• delay: (OPTIONAL) Enter the keyword delay<br />

followed by the number of seconds to delay,<br />

between 60 and 1440, from the time of<br />

invoking the command after which FTSA will<br />

accumulate system log messages into a<br />

message.<br />

Default: 1440 seconds<br />

• severity: (OPTIONAL) Enter the keyword<br />

severity followed by the minimum severity<br />

level of system log messages that should be<br />

collected into the FTSA message.<br />

Default: severity level 0 (emergencies).<br />

• filter: (OPTIONAL) Enter the keyword filter<br />

followed by a character string that FTSA<br />

should seek in the system log. A search string<br />

containing spaces must be in quotes.<br />

Log messages containing that string will be<br />

included in the FTSA message.<br />

FTOS Configuration Guide, version <strong>7.8.1.0</strong> 291

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!