BLADETYPE2-PHYSICAL-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBLADETYPE2-PHYSICAL-MIB

Organization: Hewlett Packard Company

Last Updated: 2003-12-05

Category: Hardware and Environment, Vendor: HP/HPE

Description: Reports physical hardware inventory and status for HP BladeSystem Type 2 blade modules.

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 BLADETYPE2-PHYSICAL-MIB?

BLADETYPE2-PHYSICAL-MIB is a switch-vendor MIB (associated with "Blade Type 2" series Layer 2 switching modules) whose available data covers Layer 2 configuration, statistics, and redundancy-link ("hotlinks") behavior rather than general chassis hardware inventory. It exposes data organized under layer2Configs, layer2Stats, and layer2Info branches, plus a dedicated hotlinks feature for automatic link failover between a primary and backup uplink port. In terms of monitoring, it is used to track hardware/software operational status of the switching fabric, specifically whether the current hotlinks configuration is active, whether forwarding-database updates are enabled, and whether an individual redundancy trigger has failed over (preempted) to its backup master port. It complements bridge/interface standards (BRIDGE-MIB, IF-MIB) by adding vendor-specific Layer 2 redundancy behavior not covered by those standards. Typical deployment is on managed Layer 2 switch blades in an enterprise or carrier access closet where uplink redundancy to a distribution switch must be monitored for correct failover. Engineers can download the BLADETYPE2-PHYSICAL-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BLADETYPE2-PHYSICAL-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

  • Layer 2 managed switch / switch blade module (Blade Type 2 series)

Monitoring Examples

An operator would poll hotlinksCurCfgTriggerTable/hotlinksCurCfgTriggerEntry to check hotlinksCurCfgTriggerState and hotlinksCurCfgTriggerPreemptState for each configured trigger, confirming which port is currently the active hotlinksCurCfgTriggerMasterPort. A change in hotlinksCurCfgFdbUpdateState combined with a state flip on a trigger would reveal an uplink failover event, prompting investigation of the primary link. Comparing hotlinksCurCfgOnState against hotlinksNewCfgOnState also shows whether a pending configuration change has been applied.

What Can Be Monitored

  • hotlinks redundancy state
  • active vs backup master port
  • forwarding-database update status
  • trigger failover/preempt status
  • layer2 configuration and statistics
Imported Objects

From BRIDGE-MIB

BridgeId

From HP-SWITCH-PL-MIB

hpSwitchBladeType2-Mgmt

From SNMPv2-SMI

Counter32
Gauge32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

DisplayString
PhysAddress

How to Use in IPNetwork Monitor

Example using fdbStatsCreates OID:

Select a Layer 2 managed switches/blade module 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 fdbStatsCreates into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of entries created in the Forwarding Database. 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 Counter32-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.
OIDs

RFC description

Manages Layer 2 configuration, VLAN, spanning tree, and physical port settings on HP blade switches.

Start monitoring Layer 2 managed switches/blade modules 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 BLADETYPE2-PHYSICAL-MIB