02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - 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<br />

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

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

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

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

collecting status in<strong>for</strong>mation 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 />

unless you want to modify <strong>the</strong> configuration. See Figure 467 on page 667.<br />

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

in<strong>for</strong>mation, of three types:<br />

• Capture system log messages, as discussed next.<br />

• Notify FTSA recipients of a system failover. See Figure 466 on page 666.<br />

• Capture system in<strong>for</strong>mation based on test conditions. See Configuring Action List<br />

(Event-based Type-5) Messages on page 662.<br />

Configuring <strong>the</strong> capture of system log messages<br />

FTSA can collect and send system log messages (in type-4 messages) containing a subset of in<strong>for</strong>mation<br />

from <strong>the</strong> system log. The in<strong>for</strong>mation stored with <strong>the</strong> FTSA server configuration that you selected in<br />

Configuring FTSA on page 655.<br />

You can set <strong>the</strong> severity of <strong>the</strong> log messages to collect. Of course, FTSA cannot find messages to collect if<br />

you have set a system logging severity level lower than <strong>the</strong> 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]<br />

[filter word]<br />

CONFIGURATION<br />

(conf-callhome-ser<br />

ver-name)<br />

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

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

delay followed by <strong>the</strong> number of seconds<br />

to delay, between 60 and 1440, from <strong>the</strong><br />

time of invoking <strong>the</strong> command after which<br />

FTSA will accumulate system log<br />

messages into a message.<br />

Default: 1440 seconds<br />

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

severity followed by <strong>the</strong> minimum severity<br />

level of system log messages that should<br />

be collected into <strong>the</strong> FTSA message.<br />

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

For details on system message logging,<br />

see System Log Management on page 65.<br />

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

filter followed by a character string that<br />

FTSA should seek in <strong>the</strong> system log. Log<br />

messages containing that character string<br />

will be included in <strong>the</strong> FTSA message.<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 661

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

Saved successfully!

Ooh no, something went wrong!