BLUEARC-SERVER-MIB :: fcRequests

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBLUEARC-SERVER-MIBfcRequests

fcRequests

Module: BLUEARC-SERVER-MIB

OID (symbolic): BLUEARC-SERVER-MIB::fcRequests

OID (numeric): 1.3.6.1.4.1.11096.6.1.1.1.3.6.1

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The total number of requests issued through the fibre channel interface.

What is fcRequests?

This reports the running total of requests issued through the fibre channel interface since the counter was last reset, giving a broad measure of overall storage I/O activity.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11096.6.1.1.1.3.6.1
snmpwalk -v2c -c public <target> BLUEARC-SERVER-MIB::fcRequests

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11096.6.1.1.1.3.6.1.1
snmpget -v2c -c public <target> BLUEARC-SERVER-MIB::fcRequests.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> fcRequests.1

Start monitoring BlueArc (Hitachi Data Systems) NAS storage servers (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BLUEARC-SERVER-MIB::fcRequests OID value, configure state conditions and alerts, and monitor any BlueArc (Hitachi Data Systems) NAS storage servers (legacy) from a single console.

How to Use in IPNetwork Monitor

Select a BlueArc (Hitachi Data Systems) NAS storage server (legacy) 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 fcRequests into the Find box to locate it in the OID tree, then select it and click OK. The total number of requests issued through the fibre channel interface. 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 a Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.11096blueArcBLUEARC-SERVER-MIB
1.3.6.1.4.1.11096.6blueArcPrivateBLUEARC-SERVER-MIB
1.3.6.1.4.1.11096.6.1blueArcServerBLUEARC-SERVER-MIB
1.3.6.1.4.1.11096.6.1.1blueArcServerObjsBLUEARC-SERVER-MIB
1.3.6.1.4.1.11096.6.1.1.1sysBLUEARC-SERVER-MIB
1.3.6.1.4.1.11096.6.1.1.1.3storageBLUEARC-SERVER-MIB
1.3.6.1.4.1.11096.6.1.1.1.3.6fcStatsBLUEARC-SERVER-MIB
1.3.6.1.4.1.11096.6.1.1.1.3.6.1fcRequestsBLUEARC-SERVER-MIB