LINK-INCIDENT-MIB :: nodeRNIDTableNumEntries

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › LINK-INCIDENT-MIB › nodeRNIDTableNumEntries

nodeRNIDTableNumEntries

Module: LINK-INCIDENT-MIB

OID (symbolic): LINK-INCIDENT-MIB::nodeRNIDTableNumEntries

OID (numeric): 1.3.6.1.4.1.1588.2.1.1.50.2.1

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: The number of entries in Request Node Identification Data (RNID) table.

What is nodeRNIDTableNumEntries?

This reports the number of entries currently in the Request Node Identification Data (RNID) table, i.e. how many FICON nodes have registered with the switch. An admin polls this first to know how many rows to expect when walking nodeRNIDTable.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1588.2.1.1.50.2.1
snmpwalk -v2c -c public <target> LINK-INCIDENT-MIB::nodeRNIDTableNumEntries

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1588.2.1.1.50.2.1.1
snmpget -v2c -c public <target> LINK-INCIDENT-MIB::nodeRNIDTableNumEntries.1

Start monitoring Brocade/Foundry Fibre Channel SAN switch (FICON link incident/failure) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LINK-INCIDENT-MIB::nodeRNIDTableNumEntries OID value, configure state conditions and alerts, and monitor any Brocade/Foundry Fibre Channel SAN switch (FICON link incident/failure) from a single console.

How to Use in IPNetwork Monitor

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.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.1588bcsiBrocade-REG-MIB
1.3.6.1.4.1.1588.2commDevBrocade-REG-MIB
1.3.6.1.4.1.1588.2.1fibrechannelBrocade-REG-MIB
1.3.6.1.4.1.1588.2.1.1fcSwitchBrocade-REG-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1588.2.1.1.50linkIncidentMIBLINK-INCIDENT-MIB
1.3.6.1.4.1.1588.2.1.1.50.2ficonRNIDLINK-INCIDENT-MIB
1.3.6.1.4.1.1588.2.1.1.50.2.1nodeRNIDTableNumEntriesLINK-INCIDENT-MIB