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.

IPC Timeout In<strong>for</strong>mation Collection<br />

The CP monitors <strong>the</strong> health status of <strong>the</strong> o<strong>the</strong>r processors using heartbeat messaging exchange.<br />

<strong>FTOS</strong> automatically saves critical in<strong>for</strong>mation about <strong>the</strong> IPC failure to NVRAM. Such in<strong>for</strong>mation<br />

includes:<br />

• Status counters on <strong>the</strong> internal E<strong>the</strong>rnet interface<br />

• Traffic profile of <strong>the</strong> inter-CPU bus<br />

Upon <strong>the</strong> next boot, this in<strong>for</strong>mation is uploaded to a file in <strong>the</strong> CRASH_LOG directory. Use <strong>the</strong> following<br />

command sequence beginning in EXEC mode to capture this file <strong>for</strong> analysis by <strong>the</strong> <strong>Force10</strong> <strong>Networks</strong><br />

TAC.<br />

Step Task Command Mode<br />

1 Display <strong>the</strong> directories in flash memory. The<br />

output should include:<br />

1 drwx 2048 Jan 01 1980 00:00:06<br />

CRASH_LOG_DIR<br />

2<br />

3<br />

4<br />

dir flash:<br />

In a dual RPM system, <strong>the</strong> two RPMs send synchronization messages via inter-RPM communication<br />

(IRC). As described in <strong>the</strong> High Availability chapter, an RPM failover can be triggered by loss of <strong>the</strong><br />

heartbeat (similar to a keepalive message) between <strong>the</strong> two RPMs. <strong>FTOS</strong> reports this condition via syslog<br />

messages, as follows:<br />

20:29:07: %RPM1-S:CP %IRC-4-IRC_WARNLINKDN: Keepalive packet 7 to peer RPM is lost<br />

20:29:07: %RPM1-S:CP %IRC-4-IRC_COMMDOWN: Link to peer RPM is down<br />

%RPM1-S:CP %RAM-4-MISSING_HB: Heartbeat lost with peer RPM. Auto failover on heart beat lost.<br />

%RPM1-S:CP %RAM-6-ELECTION_ROLE: RPM1 is transitioning to Primary RPM.<br />

<strong>FTOS</strong> automatically saves critical in<strong>for</strong>mation, about <strong>the</strong> IRC failure, to NVRAM. Use <strong>the</strong> same three-step<br />

procedure to capture this file <strong>for</strong> analysis by <strong>Force10</strong> <strong>Networks</strong>.<br />

<strong>FTOS</strong> actually saves up to three persistent files depending upon <strong>the</strong> type of failure. When reporting an<br />

RPM failover triggered by a loss of <strong>the</strong> IPC or IRC heartbeats, look <strong>for</strong> failure records in <strong>the</strong> following<br />

directories:<br />

— Application or kernel core dump RP in <strong>the</strong> CORE_DUMP_DIR<br />

EXEC<br />

Change to <strong>the</strong> CRASH_LOG directory. cd CRASH_LOG_DIR EXEC<br />

View any saved files in <strong>the</strong> CRASH_LOG<br />

directory. The naming convention is:<br />

sysinfo_RPMIDProcessorID _ timestamp<br />

For example:<br />

sysinfo_RPM1CP_20060616_013125<br />

View <strong>the</strong> contents of <strong>the</strong> file. show file flash://CRASH_LOG_DIR/<br />

[file_name]<br />

694 C-<strong>Series</strong> Debugging and Diagnostics<br />

dir<br />

EXEC<br />

privilege<br />

EXEC<br />

privilege

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

Saved successfully!

Ooh no, something went wrong!