Extreme Networks ExtremeWare Version 7.8 Instrukcja Naprawy Strona 30
- Strona / 122
- Spis treści
- ROZWIĄZYWANIE PROBLEMÓW
- BOOKMARKI
Oceniono. / 5. Na podstawie oceny klientów
30 Advanced System Diagnostics and Troubleshooting Guide
Packet Errors and Packet Error Detection
described in the section “System (CPU and Backplane) Health Check” on page 70. For example, the
system health check facility can be configured such that ExtremeWare will insert a message into the
system log that a checksum error has been detected.
Failure Modes
Although packet errors are extremely rare events, packet errors can occur anywhere along the data path,
along the control path, or while stored in packet memory. A checksum mismatch might occur due to a
fault occurring in any of the components between the ingress and egress points—including, but not
limited to, the packet memory (SRAM), ASICs, MAC, or bus transceiver components.
There are many causes and conditions that can lead to packet error events. These causes and conditions
can fall into one of these categories:
• Transient errors
• Systematic errors
— Soft-state errors
— Permanent errors
The failure modes that can result in the above categories are described in the sections that follow.
Transient Failures
Transient failures are errors that occur as one-time events during normal system processing. These types
of errors will occur as single events, or might recur for short durations. Because these transient events
usually occur randomly throughout the network, there is usually no single locus of packet errors. They
are temporary (do not persist), do not have a noticeable impact on network functionality, and require no
user intervention to correct: There is no need to swap a hardware module or other equipment.
Systematic Failures
Systematic errors are repeatable events: some hardware device or component is malfunctioning in such a
way that it persistently exhibits incorrect behavior. In the context of the ExtremeWare Advanced System
Diagnostics, the appearance of a checksum error message in the system log—for example—indicates
that the normal error detection mechanisms in the switch have detected that the data in a packet has
been modified inappropriately. While checksums provide a strong check of data integrity, they must be
qualified according to their risk to the system and by what you can do to resolve the problem.
Systematic errors can be subdivided into two su/jointfilesconvert/483568/bgroups:
• Soft-state failures
• Permanent, or hard failures
Soft-State Failures
These types of error events are characterized by a prolonged period of reported error messages and
might, or might not, be accompanied by noticeable degradation of network service. These events require
user intervention to correct, but are resolved without replacing hardware.
- Advanced System 1
- Diagnostics and 1
- Troubleshooting Guide 1
- Contents 3
- Chapter 5 Diagnostics 4
- Terminology 9
- Conventions 9
- Related Publications 10
- 1 Introduction 11
- Introduction 12
- Supported Hardware 13
- Diagnostics Support 15
- The BlackDiamond Systems 16
- The BlackDiamond Backplane 17
- BlackDiamond I/O Modules 18
- Management Switch Modules 19
- BlackDiamond MSM Redundancy 20
- Alpine Systems 22
- Summit “ 23
- ” Series Systems 23
- Detection 25
- Definition of Terms 26
- Errors Between Wires 27
- ASICASIC 28
- Soft-State Failures 30
- Permanent Failures 31
- Alert Messages 33
- Checksum Error Messages: 34
- Corrective Behavior Messages 35
- 4 Software Exception Handling 37
- Redundant MSM Behavior 38
- Related Commands 40
- Usage Notes 41
- Software Exception Handling 42
- Dumping the “ 45
- ” Series Switch System Memory 45
- 5 Diagnostics 49
- Diagnostics 50
- Diagnostic Test Functionality 51
- Diagnostic Suite Components 52
- Modes of Operation 54
- Runtime Diagnostics on “ 57
- ” Switches 60
- Limited Operation Mode 64
- Switches 67
- Health Check Packet Types 70
- Backplane Health Check States 70
- Alarm-Level Response Action 71
- Auto-Recovery Response Action 71
- Backplane Health Check 72
- command 73
- I/O module slot 76
- Analyzing the Results 78
- CPU Health Check 79
- Transceiver Diagnostics 82
- Viewing Diagnostics Results 84
- Example—show switch Command 86
- FDB Scan 88
- Enabling FDB Scanning 89
- Disabling FDB Scanning 89
- Syslog Servers 94
- Adding a Syslog Server 95
- Running Cable Diagnostics 97
- {detail} 98
- Cable Diagnostics 99
- Additional Diagnostics Tools 100
- Cable Diagnostics for “ 101
- ” Series Switches 101
- 7 Troubleshooting Guidelines 103
- EMEA TAC 104
- Japan TAC 104
- Asia TAC 104
- Analyzing Data 105
- Diagnostic Troubleshooting 106
- Customer 107
- Troubleshooting Guidelines 108
- A Limited Operation Mode and 111
- Minimal Operation Mode 112
- B Reference Documents 115
- Reference Documents 116
- Index of Commands 121
Powiązane produkty i podręczniki dla Oprogramowanie Extreme Networks ExtremeWare Version 7.8
(758 strony)Integra-lifesciences Sutures, Coated, Braided Polygycolic Acid, Absorba Handbücher
Bedienungsanleitungen und Benutzerhandbücher für Gesundheit und Hygiene Integra-lifesciences Sutures, Coated, Braided Polygycolic Acid, Absorba.
Wir stellen 1 PDF-Handbücher Integra-lifesciences Sutures, Coated, Braided Polygycolic Acid, Absorba zum kostenlosen herunterladen nach Dokumenttypen zur Verfügung Bedienungsanleitung
Komentarze do niniejszej Instrukcji