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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Enabling <strong>the</strong> sending of FTSA emails to selected or all recipients<br />

You can use ei<strong>the</strong>r <strong>the</strong> enable-all command or <strong>the</strong> enable command to enable FTSA messages. Use <strong>the</strong><br />

enable-all command at <strong>the</strong> (conf-callhome) prompt to enable <strong>the</strong> sending of FTSA messages to all<br />

recipients. Alternatively, at a server-specific prompt, you can use <strong>the</strong> enable command to enable messages<br />

<strong>for</strong> a specific recipient.<br />

The use of <strong>the</strong> enable or enable-all commands causes FTSA to send a status email message to <strong>the</strong> affected<br />

recipients, as shown in Figure 463:<br />

<strong>Force10</strong>(conf-callhome)#enable-all<br />

<strong>Force10</strong>(conf-callhome)#Aug 3 13:06:36: %RPM1-P:CP %CALL-HOME-3-CALLHOME: Callhome<br />

service sent a message to <strong>Force10</strong> at ftsa@<strong>for</strong>ce10networks.com<br />

Aug 3 13:06:37: %RPM1-P:CP %CALL-HOME-3-CALLHOME: Callhome service sent a message<br />

to helen at helenh@yourco.com<br />

Figure 463 enable-all Command Example<br />

To disable (end) <strong>the</strong> sending of FTSA email messages to all designated recipients, use <strong>the</strong> no enable<br />

command. Alternatively, if you used <strong>the</strong> enable-all command and <strong>the</strong>n want to disable messages to a<br />

specific recipient, you can use <strong>the</strong> no enable command at that server-specific prompt.<br />

Command Syntax Command Mode Purpose<br />

enable-all CONFIGURATION<br />

(conf-callhome)<br />

enable CONFIGURATION<br />

(conf-callhome)<br />

[no] log-only CONFIGURATION<br />

(conf-callhome-actionlistname)<br />

Specifying <strong>the</strong> frequency of FTSA inventory messages<br />

Optionally, use <strong>the</strong> frequency command at <strong>the</strong> (conf-callhome) prompt to select <strong>the</strong> time interval with<br />

which email messages containing inventory in<strong>for</strong>mation will be sent to all designated recipients. If you do<br />

not select a time interval, FTSA will send messages every 24 hours after FTSA is started.<br />

If you set <strong>the</strong> frequency to an interval o<strong>the</strong>r than <strong>the</strong> default, you can use <strong>the</strong> no frequency command to<br />

return to <strong>the</strong> default, or you can enter <strong>the</strong> command again to select ano<strong>the</strong>r interval.<br />

There is no interval setting override <strong>for</strong> individual recipients.<br />

Command Syntax Command Mode Purpose<br />

frequency minutes CONFIGURATION<br />

(conf-callhome)<br />

The default condition is disabled (no FTSA email messages to<br />

any recipients). Any recipient email that is in <strong>the</strong> default state of<br />

disabled will be enabled with this command.<br />

Enable FTSA emails to a specific recipient. Recipient emails in<br />

<strong>the</strong> disabled state, ei<strong>the</strong>r by default or because <strong>the</strong> no enable-all<br />

command was executed, can be enabled with this command.<br />

For type 5 messages, you have this way of diverting <strong>the</strong>m to a<br />

local log, ra<strong>the</strong>r than sending <strong>the</strong>m to FTSA recipients.<br />

(OPTIONAL STEP) Enter <strong>the</strong> time interval, in<br />

minutes, that you want between FTSA status<br />

emails.<br />

Range: 2 to 10080 minutes<br />

Default: 1440 minutes (24 hours)<br />

660 <strong>Force10</strong> Service Agent

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

Saved successfully!

Ooh no, something went wrong!