课程3－GSR故障诊断方法01.ppt

GSR Troubleshooting System-level Troubleshooting The basics Show log Show gsr Show diag Execute-on Attach Running Commands on Line Cards execute-on slot [slot #] command, execute-on all command attach Only one session may be ‘attached’ at a time Running Commands on LCs GSR-2#exec slot 3 sh proc cpu | e 0.00 ========= Line Card (Slot 3) ======= CPU utilization for five seconds: 0%/0%; one minute: 0%; five minutes: 0% PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process GSR-2# System Commands Checking LC processor/memory rp-12008-11a#exec slot 0 sh mem sum Head Total(b) Used(b) Free(b) Lowest(b) Largest(b) Processor 613D60E0 113418016 103127888 102599324 102896756 Fast 613B60E0 131072 44792 86280 86280 86236 It’s very important to watch the “free” and “largest” blocks. If these numbers are continually decreasing, you have a memory leak. rp-12008-11a#exec slot 2 sh proc cpu ========= Line Card (Slot 2) ======= CPU utilization for five seconds: 5%/0%; one minute: 5%; five minutes: 5% PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process 1 0 118933 0 0.00% 0.00% 0.00% 0 Load Meter 2 1244 917761 1 0.00% 0.00% 0.00% 0 CEF process 3 161156 60440 2666 0.00% 0.02% 0.00% 0 Check heaps Remember that the number before the slash is the total CPU, the number after the slash is interrupt context. Interrupt context is not accounted individually, and includes packet switching, alignment corrections, etc. In the normal case on E0/E1 cards, CPU interrupt utilization will scale linearly with inbound packet rates. Normal case on E2,3,4 6 is VERY low CPU, as the ASICs should be making this decision, not the CPU. Field Diagnostics Starting with 12.0(22)S IOS, field diag image was too large. Field diags removed from IOS New CLI (to download from flash/tftp) Field Diagnostics diag slot [options]