Running The Packet Memory Scan Diagnostics On Summit Systems; Automatic Packet Memory Scan (Via Sys-Health-Check); Memory Scanning And Memory Mapping Behavior - Extreme Networks BlackDiamond 6804 Troubleshooting Manual

Diagnostics

Running the Packet Memory Scan Diagnostics on Summit Systems

To run the packet memory scan diagnostics on a Summit system, use this command:
run diagnostics packet-memory
When you enter the command, the system displays message
run diagnostics packet-memory
warning about potential impacts on your switch and network (because the module—in a BlackDiamond
switch—or the entire switch—for Alpine and Summit switches—will be taken offline during the time
the diagnostic is running) and prompts you to confirm or cancel the test.

Automatic Packet Memory Scan (via sys-health-check)

An automatic packet memory scan is set up when the system health check option is
auto-recovery
enabled (see "System (CPU and Backplane) Health Check" on page 69). When system health checks fail
at the specified frequency, packet memory scanning is invoked automatically.
Automatic mode status is listed in the "sys-health-check" field of the display for the
show switch
command.
When is configured, an automated background polling task checks every 20 seconds to
auto-recovery
determine whether any fabric checksums have occurred. Three consecutive samples must be corrupted
for any module to invoke autoscan.
CAUTION
If automatic packet memory scanning is invoked—regardless of platform type or number of
errors—there is an initial period where the device is taken offline so that the scan can be run.

Memory Scanning and Memory Mapping Behavior

Memory scanning and memory mapping behavior differs depending on the switch platform, whether
you run the diagnostics manually or configure the auto-recovery option of the system health checker,
and the mode you configure (online or offline).
For BlackDiamond systems, once the test is initiated (either automatically or by manual control), the
memory scanning feature takes the selected module offline and initiates a thorough memory write/read
operation to detect any permanent single-bit errors in the memory of the module. This scan takes
approximately 90 seconds and the module remains offline for the duration of the scan.
For Summit and Alpine systems, the test is initiated by manual command, the entire switch is taken
offline during the time test is running and is then rebooted.
Table 5 describes the behavior of the switch if you configure auto-recovery using the
CLI command. The scan behavior differs based on the hardware
config sys-health-check
configuration, the mode selected (online or offline), and the number of errors to be detected.
60 Advanced System Diagnostics and Troubleshooting Guide