LINK-INCIDENT-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › LINK-INCIDENT-MIB

Organization: Brocade Communications Systems, Inc.,

Last Updated: 2012-06-04

Category: Alarm and Event Management, Vendor: Foundry/Brocade

Description: Brocade MIB defining SNMP notifications for link-level incidents such as degraded signal, link failures, and SFP events on Brocade/Foundry equipment.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is LINK-INCIDENT-MIB?

This is a Brocade Fibre Channel MIB supporting FICON on Fabric OS (FabOS) switches, addressing link-incident and link-failure data for FICON hosts/devices attached to a Brocade SAN switch. It exposes a node registration table (RNID) capturing connected-device identity, port WWNs, port ID, device type, model, manufacturer, plant, and serial number, alongside link incident/failure notifications for degraded signal, link failures, and SFP events. It is explicitly used to monitor the hardware status of attached FICON devices and their physical link health, flagging degraded optical signal, SFP transceiver problems, and link failures that indicate cabling or transceiver hardware issues rather than software faults. This module builds on Fibre Channel/FICON standards and Brocade's broader Fabric OS MIB tree for correlating incidents to physical ports. Typical deployment is on Brocade/Foundry SAN directors and switches in mainframe (FICON) storage networking environments. Network engineers evaluating or troubleshooting this functionality can download the LINK-INCIDENT-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in LINK-INCIDENT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Brocade/Foundry Fibre Channel SAN switch (FICON)

Monitoring Examples

An operator would poll nodeRNIDTable/nodeRNIDEntry, indexed by nodeRNIDIndex, to identify connected FICON devices by nodeRNIDIncidentPortWWN, nodeRNIDConnectedPortWWN, nodeRNIDModel, and nodeRNIDManufacturer. Repeated link-incident traps referencing the same nodeRNIDPID or port WWN typically point to a failing SFP or cable on that link. nodeRNIDFlags and nodeRNIDType help distinguish device capability/state when triaging which attached host or storage device is affected.

What Can Be Monitored

  • link incidents/failures
  • SFP/signal degradation events
  • connected device port WWNs
  • attached device model/manufacturer
  • device serial number
  • port ID and flags
Imported Objects

From Brocade-REG-MIB

fcSwitchOBJECT-IDENTITY

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using nodeRNIDTableNumEntries OID:

Select a Brocade/Foundry Fibre Channel SAN switch (FICON link incident/failure) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type nodeRNIDTableNumEntries into the Find box to locate it in the OID tree, then select it and click OK. The number of entries in Request Node Identification Data (RNID) table. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the count changes from its expected baseline, since that would indicate the underlying set of items changed unexpectedly. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

SNMP MIB for managing link-related incidents and trap configurations in network monitoring systems, used for handling incident notifications related to network link status changes and events.

Start monitoring Brocade/Foundry Fibre Channel SAN switch (FICON link incident/failure) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download LINK-INCIDENT-MIB