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.

Inspecting files stored locally<br />

When you define an action list or test list, or when you invoke <strong>the</strong> log-only command, <strong>FTOS</strong> saves those<br />

files to local flash memory. You can inspect <strong>the</strong> files with <strong>the</strong> command show file flash://file_name.<br />

The action list is stored with <strong>the</strong> filename comprised of <strong>the</strong> action-list name and a time stamp (and with an<br />

.ftsa extension).<br />

The log file will have <strong>the</strong> same name as <strong>the</strong> action list and with ano<strong>the</strong>r time stamp appended, <strong>for</strong> example:<br />

flash:/hardwareAction- 02_16_34 423.ftsa<br />

FTSA event-handling configuration example<br />

Figure 464 shows an example of configuring <strong>the</strong> event-driven message, first entering <strong>the</strong> contact<br />

in<strong>for</strong>mation that will be included in <strong>the</strong> message (unless you set <strong>the</strong> log-only option in Step 9, above —<br />

Configuring FTSA event handling on page 662.) and <strong>the</strong>n <strong>the</strong> policy configuration.<br />

<strong>Force10</strong>(conf-callhome)#contact-name AllFTSAAdmin<br />

<strong>Force10</strong>(conf-callhome)#contact-phone 5551234567<br />

<strong>Force10</strong>(conf-callhome)#contact-email AllFTSAAdmin@mycompany.com<br />

<strong>Force10</strong>(conf-callhome)#contact-address 123 Main St, Your Town<br />

<strong>Force10</strong>(conf-callhome)#contact-notes AllFTSAAdmin is <strong>the</strong> alias <strong>for</strong> all MyCompany<br />

network admins!<br />

<strong>Force10</strong>(conf-call-home)#policy-test-list case#C12345<br />

<strong>Force10</strong>(conf-call-home-testlist-case#C12345)#default-test HARDWARE<br />

<strong>Force10</strong>(conf-call-home-testlist-case#C12345)#exit<br />

<strong>Force10</strong>(conf-call-home)#policy-action-list case#C12345<br />

<strong>Force10</strong>(conf-call-home-actionlist-case#C12345)#default-action HARDWARE<br />

<strong>Force10</strong>(conf-call-home-actionlist-case#C12345)#exit<br />

<strong>Force10</strong>(conf-callhome)# policy case#C12345<br />

<strong>Force10</strong>(conf-callhome-policy-case#C12345)#test-list case#C12345<br />

<strong>Force10</strong>(conf-callhome-policy-case#C12345)#action-list case#C12345<br />

<strong>Force10</strong>(conf-callhome-policy-case#C12345)#case-number c-12345<br />

<strong>Force10</strong>(conf-callhome-policy-case#C12345)#exit<br />

Figure 464 enable-all Command Example<br />

Figure 469 on page 669 shows <strong>the</strong> kind of type-5 message generated by this policy configuration.<br />

Interpreting Email Messages from FTSA<br />

FTSA sends email to all enabled recipients in <strong>the</strong> following situations:<br />

• On startup of FTSA (executing <strong>the</strong> call-home command)<br />

• On shutdown of FTSA (executing <strong>the</strong> no call-home command)<br />

• On <strong>the</strong> execution of <strong>the</strong> enable-all command<br />

• On <strong>the</strong> execution of <strong>the</strong> no enable-all command<br />

• At <strong>the</strong> designated time interval (frequency)<br />

FTSA sends an email to a particular recipient when you enable or disable email to that recipient by using<br />

<strong>the</strong> enable or no enable commands, respectively.<br />

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

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

Saved successfully!

Ooh no, something went wrong!