Brocade FC Switch
Plugin: go.d.plugin Module: snmp
Overview
Monitor Brocade FC Switch (switch) with Netdata over SNMP. Netdata recognizes the device automatically by its sysObjectID (recognized across 16 device identifiers) and collects the metrics this profile declares — on top of the generic SNMP baseline — with no manual OID configuration.
Netdata's SNMP collector matches the device to the brocade-fc-switch.yaml profile via sysObjectID/sysDescr, then polls the OIDs it declares.
This integration is supported on all platforms.
This integration supports multiple instances configured side-by-side.
Default Behavior
Auto-Detection
Auto-detected as Brocade FC Switch via sysObjectID/sysDescr.
Limits
The default configuration for this integration does not impose any limits.
Performance Impact
The default configuration for this integration is not expected to impose a significant performance impact on the system.
Setup
You can configure the snmp collector in two ways:
| Method | Best for | How to |
|---|---|---|
| UI | Fast setup without editing files | Go to Nodes → Configure this node → Collectors → Jobs, search for snmp, then click + to add a job. |
| File | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit go.d/snmp.conf and add a job. |
UI configuration requires paid Netdata Cloud plan.
Prerequisites
SNMP access
SNMP must be enabled on the device and reachable from the Netdata Agent acting as the site's SNMP hub.
Configuration
Options
Configure the SNMP collector with the device hostname and SNMP credentials. See the SNMP collector reference for all options.
via UI
Configure the snmp collector from the Netdata web interface:
- Go to Nodes.
- Select the node where you want the snmp data-collection job to run and click the ⚙ (Configure this node). That node will run the data collection.
- The Collectors → Jobs view opens by default.
- In the Search box, type snmp (or scroll the list) to locate the snmp collector.
- Click the + next to the snmp collector to add a new job.
- Fill in the job fields, then click Test to verify the configuration and Submit to save.
- Test runs the job with the provided settings and shows whether data can be collected.
- If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
via File
The configuration file name for this integration is go.d/snmp.conf.
The file format is YAML. Generally, the structure is:
update_every: 1
autodetection_retry: 0
jobs:
- name: some_name1
- name: some_name2
You can edit the configuration file using the edit-config script from the
Netdata config directory.
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/snmp.conf
Examples
There are no configuration examples.
Alerts
There are no alerts configured by default for this integration.
Metrics
On top of the generic SNMP baseline (the Generic SNMP Device integration — interfaces, system, IP/TCP/UDP, host resources), this Brocade FC Switch profile adds the metrics below. Each is collected only where the device exposes the matching OID — inclusion means the profile requests it; availability depends on the device model and software.
27 metrics in 5 groups; each row is a chart context usable in alerts.
| Group | Metrics |
|---|---|
| Network / FibreChannel | 20 |
| Network / Interface | 4 |
| System / CPU | 1 |
| System / Memory | 1 |
| System / Uptime | 1 |
Network / FibreChannel
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_fcFxPortAdminMode | {status} | per fc_fe_module_index, fc_fx_port_index | Desired operational mode of the FxPort |
snmp.device_prof_fcFxPortBbCreditAvailable | {buffer} | per fc_fe_module_index, fc_fx_port_index | Buffers currently available for receiving frames from the attached port in the buffer-to-buffer flow control |
snmp.device_prof_fcFxPortOperMode | {status} | per fc_fe_module_index, fc_fx_port_index | Operational mode of the FxPort |
snmp.device_prof_fcFxPortPhysAdminStatus | {status} | per fc_fe_module_index, fc_fx_port_index | Desired state of the FxPort |
snmp.device_prof_fcFxPortPhysOperStatus | {status} | per fc_fe_module_index, fc_fx_port_index | Current operational status of the FxPort |
snmp.device_prof_swFCPortC3Discards | {frame}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of Class 3 frames discarded by the port. |
snmp.device_prof_swFCPortNoTxCredits | {time}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of times when the transmit credit has reached zero |
snmp.device_prof_swFCPortRcTruncs | {frame}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of truncated frames received by the port |
snmp.device_prof_swFCPortRxBadEofs | {frame}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of received frames with bad EOF delimiter |
snmp.device_prof_swFCPortRxBadOs | {error}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of invalid Ordered Sets received |
snmp.device_prof_swFCPortRxC2Frames | {frame}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of Class 2 frames received by the port |
snmp.device_prof_swFCPortRxC3Frames | {frame}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of Class 3 frames received by the port |
snmp.device_prof_swFCPortRxCrcs | {error}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of CRC errors detected for frames received |
snmp.device_prof_swFCPortRxEncInFrs | {error}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of encoding or disparity errors inside frames received. |
snmp.device_prof_swFCPortRxEncOutFrs | {error}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of encoding or disparity errors outside frames received |
snmp.device_prof_swFCPortRxFrames | {frame}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of Fibre Channel frames received by the port |
snmp.device_prof_swFCPortRxLCs | {frame}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of Link Control frames received by the port |
snmp.device_prof_swFCPortRxTooLongs | {frame}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of received frames that are too long |
snmp.device_prof_swFCPortTooManyRdys | {time}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of times when RDYs exceeds the frames received |
snmp.device_prof_swFCPortTxFrames | {frame}/s | per sw_fc_port_name, sw_fc_port_specifier | Number of Fibre Channel frames transmitted by the port |
Network / Interface
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_ifAdminStatus | {status} | per interface, interface | Current administrative state of the interface |
snmp.device_prof_ifHighSpeed | bit/s | per interface, interface | Estimate of the interface's current bandwidth |
snmp.device_prof_ifNumber | {interface} | device | Number of network interfaces regardless of their current state present on this system |
snmp.device_prof_ifOperStatus | {status} | per interface, interface | Current operational state of the interface |
System / CPU
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_cpu_usage | % | device | The current CPU utilization |
System / Memory
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_memory_usage | % | device | System's memory usage |
System / Uptime
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_systemUptime | s | device | Time since the system was last rebooted or powered on. |
Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.