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.

To configure a policy, you select from one of three test groups to monitor <strong>the</strong> system. You might select one<br />

test group and <strong>the</strong>n switch to ano<strong>the</strong>r test group if an issue occurs in that particular issue that warrants<br />

using ano<strong>the</strong>r o<strong>the</strong>r test group.<br />

You <strong>the</strong>n select from one of <strong>the</strong> three available actions, each of which is comprised of collecting data from<br />

various show commands and emailing (or logging) <strong>the</strong> results. The action must match <strong>the</strong> test group that<br />

you selected. This requirement <strong>for</strong> you to set up a match of tests and actions is designed this way partly in<br />

order to provide more functionality in future <strong>FTOS</strong> versions.<br />

Note that this event-driven process is separate from <strong>the</strong> routine timing of <strong>the</strong> inventory messages described<br />

above in Configuring FTSA on page 655.<br />

Tip: If you open a case with TAC, consider using <strong>the</strong> case number as <strong>the</strong> title of <strong>the</strong> policiy, test group,<br />

and corresponding action that you invoke to monitor <strong>the</strong> system in response to <strong>the</strong> case.<br />

Table 63 on page 664 shows <strong>the</strong> three test groups from which you can choose.<br />

Table 64 on page 664 shows <strong>the</strong> three action sets from which you can choose. Note that <strong>the</strong>y have been<br />

configured to match <strong>the</strong> three test groups.<br />

Step Command Syntax Command Mode Purpose<br />

1 policy-test-list word CONFIGURATION<br />

(conf-callhome)<br />

2<br />

3<br />

4<br />

5<br />

6<br />

7<br />

8<br />

default-test CONFIGURATION<br />

(conf-callhome-<br />

testlist-name)<br />

policy-action-list word CONFIGURATION<br />

(conf-callhome)<br />

default-action {hardware |<br />

software | exception}<br />

CONFIGURATION<br />

(conf-callhome-<br />

actionlist-name)<br />

policy word CONFIGURATION<br />

(conf-callhome)<br />

test-list word CONFIGURATION<br />

(conf-callhome-<br />

policy-name)<br />

action-list word CONFIGURATION<br />

(conf-callhome-<br />

policy-name)<br />

case-number word CONFIGURATION<br />

(conf-callhome-<br />

policy-name)<br />

Name a policy test list (up to 20 characters) and<br />

enter <strong>the</strong> config-callhome-testlist-name mode.<br />

Invoke one of <strong>the</strong> three system-monitoring test<br />

groups — hardware, software, or exception, as<br />

detailed below in Table 63. Type exit.<br />

Enter a name (up to 20 characters) <strong>for</strong> a new<br />

policy action list and enter <strong>the</strong><br />

config-callhome-actionlist-name mode.<br />

Select <strong>the</strong> in<strong>for</strong>mation collection action that<br />

matches <strong>the</strong> selected test group. The data<br />

collection sets are detailed below in Table 64.<br />

For example, if you selected <strong>the</strong> hardware test<br />

group, above, you must now select <strong>the</strong> hardware<br />

action group. Type exit..<br />

Name a policy (up to 20 characters) and enter <strong>the</strong><br />

config-callhome-policy-name mode.<br />

Enter <strong>the</strong> name of <strong>the</strong> test list that you entered in<br />

Step 1.<br />

Enter <strong>the</strong> name of <strong>the</strong> action list that you entered<br />

in Step 3.<br />

(OPTIONAL) Enter a case number to associate<br />

with this set of tests and actions. Type exit.<br />

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

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

Saved successfully!

Ooh no, something went wrong!