Brocade Mobility RFS7000-GR Controller System Reference Guide (Supporting software release 4.1.0.0-040GR and later) - Manual (Page 18)

4 Brocade Mobility RFS7000-GR Controller System Reference Guide
53-1001944-01
Software overview
1
Text based configuration
The configuration is stored in a human readable format (as a set of CLI commands).
Diagnostics
The following diagnostics are available:
1. In-service Diagnostics – In-service diagnostics provide a range of automatic health monitoring
features ensuring both the system hardware and software are in working order.
In-service-diagnostics continuously monitor available physical characteristics (as detailed
below) and issue log messages when warning or error thresholds are reached. There are three
types of in-service diagnostics:
• Hardware – Ethernet ports, chip failures, system temperature via the temperature sensors
provided by the hardware, etc.
• Software – CPU load, memory usage, etc.
• Environmental – CPU and air temperature, fans speed, etc.
2. Out-of-service Diagnostics – Out-of-service diagnostics are a set of intrusive tests run from the
user interface. Out-of-service diagnostics cannot be run while the switch is in operation.
Intrusive tests include:
Ethernet loopback tests
RAM tests, Real Time Clock tests, etc.
3. Manufacturing Diagnostics – Manufacturing diagnostics are a set of diagnostics used by
manufacturing to inspect quality of hardware.
Serviceability
A special set of Service CLI commands are available to provide additional troubleshooting
capabilities for service personnel (access to Linux services, panic logs, etc.). Only authorized users
or service personnel are provided access to the Service CLI.
A built-in Packet Sniffer enables service personnel and users to capture incoming and outgoing
packets in a buffer.
The switch also collects statistics for RF activity, Ethernet port activity etc. RF statistics include
roaming stats, packet counters, octets tx/rx, signal, noise SNR, retry, and information for each MU.
Tracing / logging
Log messages are well-defined and documented system messages with various destinations. They
are numbered and referenced by ID. Each severity level group, can be configured separately to go
to either the serial console, telnet interface, log file or remote syslog server.
Trace messages are more free-form and are used mainly by support personnel for tracking
problems. They are enabled or disabled via CLI commands. Trace messages can go to a log file, the
serial console, or the current tty.
Log and trace messages are interleaved in the same log file, so chronological order is preserved.
Log and trace messages from different processes are similarly interleaved in the same file for the
same reason.