Effective switch system monitoring gives operations teams visibility into device health, network events and traffic behavior. On Extreme Networks Ethernet Routing Switch (ERS) 4900 and 5900 platforms, the available monitoring tools cover both routine operational checks and targeted troubleshooting. They include CPU and memory utilization views, local and remote logging, port mirroring, RMON, IPFIX, and diagnostics for ports and switch stacks.
These capabilities are useful to industrial automation engineers and system integrators responsible for maintaining the communications infrastructure that connects control systems, supervisory applications and plant networks. Monitoring does not replace network design or fault investigation; it provides information that helps teams identify where to look and understand what a switch is reporting.
Switch system monitoring: start with device health
CPU and memory utilization provide a view of the switch’s resource use. CPU data can be displayed across several periods, from recent intervals through longer-term views and the time since boot. Memory utilization reports the proportion of dynamic memory in use and the available amount. These are display-only functions, so they can be checked without first configuring a monitoring feature.
Physical indicators also matter. LEDs communicate diagnostic and operating information at the device, while environmental views can help users inspect switch conditions. For pluggable optics, digital diagnostics information (DDI) provides another source of module-related status. Together, these checks help distinguish a device or component concern from a broader network issue.
Use logs to build an operational record
The system event log records messages generated by the switch. Remote logging can replicate system messages to a syslog server, allowing messages from multiple switches to be collected centrally instead of requiring an operator to inspect each device independently. A central log can make it easier to review events across a network and correlate device reports during an investigation.
Remote logging depends on configuring the receiving syslog server to accept the intended messages. Teams should also decide which devices and messages need to be included in their operational review process. SNMP traps provide another mechanism for communicating events to network management systems, while the switch’s MIB web page supports access to management information.
Improve traffic visibility with port mirroring
Port mirroring copies selected traffic to a monitoring destination for analysis. This can help an engineer examine communications without relying only on counters or event messages. The ERS monitoring feature set includes port-based and address-based mirroring, as well as many-to-many and VLAN-based options. Remote SPAN (RSPAN) extends mirroring so that traffic can be delivered to a destination on another switch, subject to feature interactions and configuration restrictions.
In an industrial environment, a mirrored feed may help investigate whether expected traffic is present or examine a communication issue with an appropriate analyzer. The monitoring destination and the traffic selected should be planned carefully: mirroring is intended to expose copies of traffic, not to alter the original forwarding path. Available modes and restrictions should be checked against the switch release and network design before deployment.
RMON and IPFIX for statistics and flows
Remote Network Monitoring (RMON) provides tools for collecting and evaluating network statistics. RMON history and statistics can support ongoing observation of port activity, while alarms and events can be configured to respond to monitored conditions. This creates a framework for tracking selected measurements rather than relying solely on a one-time snapshot.
IPFIX provides flow-oriented monitoring. The ERS 4900 and 5900 documentation describes global IPFIX management, flow settings, exporters, collectors and port-level management. In practical terms, the feature set lets administrators configure how flow information is managed and sent to a collector. The exact settings and supported behavior should be confirmed for the deployed release and topology.
Check stack health and port operation
For switches operating as a stack, monitoring extends beyond individual ports. Stack Monitor and Stack Health Check features support observation of stack status, with diagnostic procedures such as stack loopback tests and stack-port counters available for troubleshooting. The platform also provides port operational status and port statistics, which help teams examine link state and reported activity.
These checks are particularly useful when investigating a problem that may involve stack connectivity rather than an endpoint or application. A disciplined sequence—review device health, inspect logs, check port status and counters, then use targeted diagnostics—can help narrow the scope of an issue. The appropriate sequence will depend on the symptoms and network configuration.
Make monitoring part of the operating process
The ERS 4900 and 5900 monitoring toolkit spans several complementary layers: resource utilization, device and event status, traffic inspection, historical statistics, flow information and stack diagnostics. CLI and Enterprise Device Manager (EDM) provide documented ways to view and configure a range of these functions.
For plant network teams, the practical step is to select monitoring methods that answer specific operational questions. Centralize logs where cross-device review is needed, use mirroring for targeted packet analysis, and apply statistics or flow monitoring where ongoing traffic visibility is important. Pair those tools with routine checks of utilization, port operation and stack health. This makes monitoring more actionable while keeping troubleshooting focused on the evidence the switch can provide.