Dell Force10 E600i FTOS Version 8.4.1.5 Configuration Guide for ExaScale - Page 1112

www.dell.com | support.dell.com Respond to PCDFO events Troubleshooting PCDFO events requires applying some human intelligence to differentiate between transient and systematic failures. PCDFO events can be caused by several factors, including: • Backplane noise • Data corruption • Bad epoch timing • Mis-configuration of backplane There are two PCDFO error types: Transient and Systematic. Transient error are non-persistent events that occur as one-events during normal operation. Systematic errors are repeatable events. For example, some hardware device or component is malfunctioning in such a way that it persistently exhibits incorrect behavior. For the transient case, PCDFO errors are not reported to the log. The hardware system automatically recovers from the error state, and the dataplane continues to function properly. In persistent case, PCDFO errors will appear in the log, and the error state is likely to remain if not handled. With PCDFO error data alone, it is impossible to arrive at a conclusion which will pinpoint the cause for PCDFO error or reason for packets drop. For example, it is quite possible to have multiple line cards/RPM show different channels with PCDFO error. Nonetheless, PCDFO status is a very useful data point as an indication of the health of the dataplane, particularly when an error is persistent. To disable the PCDFO polling feature, use the following command in CONFIGURATION mode. Task Disable the PCDFO polling feature. To re-enable, use the no dataplane-diag disable dfo-reporting command. Command Mode dataplane-diag disable dfo-reporting CONFIGURATION Detection of a PCDFO event causes the system to generate a message similar to the following. Message 6 PCDFO Event Message %RPM1-P:CP %CHMGR-2-SFM_PCDFO: PCDFO error detected for SFM # Events are logged when PCDFO error first occurs on any SFM and when PCDFO error pattern changes. No automatic action is taken by the system when a DFO error is detected. If such an error is reported, note the SFM slot number identified in the message and contact Dell Force10 technical support. In addition, to confirm that the identified SFM needs to be replaced, use the diag sfm all-loopback to execute a manual dataplane loopback test. 1112 | E-Series ExaScale Debugging and Diagnostics