HH3C-PEX-MIB

All MIBs › HH3C-PEX-MIB

Organization: Hangzhou H3C Technologies Co., Ltd.

Last Updated: 2012-11-12

Category: Technology: Stacking, Vendor: H3C/HH3C

Description: HH3C MIB for Port Extender (PEX) technology managing extended port modules on H3C switches.

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 HH3C-PEX-MIB?

HH3C-PEX-MIB is an H3C (Hangzhou Huawei-3Com) enterprise MIB for managing Port Extender (PEX) technology, which lets extended port modules attached to an H3C switch be controlled as if they were local ports. It exposes configuration data such as PEX port ID ranges, port-to-association-ID mappings, and per-port descriptions and status, along with a dedicated trap group for PEX events. Its main monitoring role is the software/hardware status of the extended ports themselves -- hh3cPexPortStatus reports operational state of each extended port, tying it back to the physical entity via hh3cPexPortEntPhysicalIndex -- giving visibility into remote line-card-like modules attached over PEX. It relies on the standard ENTITY-MIB (via entPhysicalIndex) to correlate PEX ports with physical inventory entries. It is typically deployed on H3C/HPE Comware switches acting as PEX controlling bridges with attached port-extender modules in data center or campus access layers. Engineers can download the HH3C-PEX-MIB file directly to load it into their MIB browser.

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

H3C/HPE Comware switch with Port Extender modules

Monitoring Examples

An administrator would poll hh3cPexPortTable/hh3cPexPortEntry indexed by hh3cPexPortId to check hh3cPexPortStatus and hh3cPexPortDescr for each extended port, confirming a remote PEX port is up and correctly associated via hh3cPexPortAssociateId. Cross-referencing hh3cPexPortEntPhysicalIndex against the switch's ENTITY-MIB physical table would let an operator map a PEX port back to a specific physical extender module, and hh3cPexTraps would notify on PEX port state changes such as an extender going offline.

What Can Be Monitored

extended port operational status
port-to-association ID mapping
port description
PEX port count limits
PEX port trap events

Imported Objects

From ENTITY-MIB

entPhysicalDescr	OBJECT-TYPE
entPhysicalIndex	OBJECT-TYPE

From HH3C-OID-MIB

hh3cCommon

OBJECT-IDENTITY

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString
RowStatus

OIDs

OID symbolic	OID numeric	Type	Access	Description
hh3cPex	1.3.6.1.4.1.25506.2.129			This MIB is used to manage Port Extender (PEX) information. This MIB is applicable to products that support PEX.
hh3cPexSpecInfo	1.3.6.1.4.1.25506.2.129.1
I32 hh3cPexPortMinId	1.3.6.1.4.1.25506.2.129.1.1	Integer32	read-only	Lowest PEX port ID that can be used to uniquely identify a PEX port.
I32 hh3cPexPortMaxId	1.3.6.1.4.1.25506.2.129.1.2	Integer32	read-only	Highest PEX port ID that can be used to uniquely identify a PEX port.
I32 hh3cPexMinAssociateId	1.3.6.1.4.1.25506.2.129.1.3	Integer32	read-only	Lowest ID that can be assigned to a port extender (PEX).
I32 hh3cPexMaxAssociateId	1.3.6.1.4.1.25506.2.129.1.4	Integer32	read-only	Highest ID that can be assigned to a PEX.
I32 hh3cPexMaxPortPerPexPort	1.3.6.1.4.1.25506.2.129.1.5	Integer32	read-only	Maximum number of ports that can be bound to a PEX port.
hh3cPexTable	1.3.6.1.4.1.25506.2.129.2
hh3cPexPortTable	1.3.6.1.4.1.25506.2.129.2.1		not-accessible	This table contains objects used to configure the PEX ports.
hh3cPexPortEntry	1.3.6.1.4.1.25506.2.129.2.1.1		not-accessible	Information about a PEX.
I32 hh3cPexPortId	1.3.6.1.4.1.25506.2.129.2.1.1.1	Integer32	accessible-for-notify	ID that can be used to uniquely identify a PEX port. The value range is hh3cPexPortMinId to hh3cPexPortMaxId.
I32 hh3cPexPortAssociateId	1.3.6.1.4.1.25506.2.129.2.1.1.2	Integer32	read-create	ID assigned to a PEX. The value range is hh3cPexMinAssociateId to hh3cPexMaxAssociateId. The value is 0xffff if the PEX is not assigned an ID. For a successful configuration, the ID should not be used by any other PEX.
I32 hh3cPexPortEntPhysicalIndex	1.3.6.1.4.1.25506.2.129.2.1.1.3	Integer32	read-only	Entity index of a PEX in the IRF. A value of zero indicates that the PEX is not online.
STR hh3cPexPortDescr	1.3.6.1.4.1.25506.2.129.2.1.1.4	DisplayString	read-create	Description for the PEX port. The default value is 'pex-port XXXX', where 'XXXX' is hh3cPexPortId. Writing a zero-length string to this object resets the value to the default.
INT hh3cPexPortStatus	1.3.6.1.4.1.25506.2.129.2.1.1.5	INTEGER	read-only	Status of the PEX. offline: The PEX is absent or its configuration is incomplete. loading: The PEX is loading software. online: The PEX is operating correctly.
ROW hh3cPexPortRowStatus	1.3.6.1.4.1.25506.2.129.2.1.1.6	RowStatus	read-create	The control that allows creation and deletion of entries. Values include createAndGo, active, and destroy. If the row to be created or modified already exists, an error message is returned. If the row to be deleted does not exist, a success message is returned.
hh3cPexPhyPortTable	1.3.6.1.4.1.25506.2.129.2.2		not-accessible	This table contains objects used to manage physical ports that can be bound or are already bound to a PEX port.
hh3cPexPhyPortEntry	1.3.6.1.4.1.25506.2.129.2.2.1		not-accessible	Information about a physical port that can be bound to or has been bound to a PEX port.
INT hh3cPexPhyPortStatus	1.3.6.1.4.1.25506.2.129.2.2.1.1	INTEGER	read-only	Status of the physical port that is bound to a PEX port. The following are status values: unknown: The physical port is not bound to any PEX port. down: The physical port is link down. blocked: The physical port is blocked and cannot forward traffic. forwarding: The physical port can forwarding traffic.
I32 hh3cPexPhyPortBelongToPexPort	1.3.6.1.4.1.25506.2.129.2.2.1.2	Integer32	read-write	ID of the PEX port to which the physical port belongs. The value range is hh3cPexPortMinId to hh3cPexPortMaxId. A value of zero indicates that the port doesn't belong to any PEX port.
I32 hh3cPexPhyPortNeighborEntIndex	1.3.6.1.4.1.25506.2.129.2.2.1.3	Integer32	read-only	Entity index of a physical port that connects the PEX to the parent device. This value is identical to entPhysicalIndex in ENTITY-MIB. A value of zero indicates that the physical port is not bound to any PEX port or is not up.
hh3cPexTraps	1.3.6.1.4.1.25506.2.129.3
hh3cPexTrapPrefix	1.3.6.1.4.1.25506.2.129.3.0
NTF hh3cPexPortOnline	1.3.6.1.4.1.25506.2.129.3.0.1			An hh3cPexPortOnline trap is sent when the PEX transitions to online state.
NTF hh3cPexPortOffline	1.3.6.1.4.1.25506.2.129.3.0.2			An hh3cPexPortOnline trap is sent when the PEX transitions to offline state.
NTF hh3cPexPhyPortForwarding	1.3.6.1.4.1.25506.2.129.3.0.3			An hh3cPexPhyPortForwarding trap is sent when the PEX physical port transitions to forwarding state.
NTF hh3cPexPhyPortBlocked	1.3.6.1.4.1.25506.2.129.3.0.4			An hh3cPexPhyPortBlocked trap is sent when the PEX physical port transitions from forwarding state to blocked state.
hh3cPexTrapObjects	1.3.6.1.4.1.25506.2.129.4
I32 hh3cPexEntPhysicalIndexBind	1.3.6.1.4.1.25506.2.129.4.1	Integer32	accessible-for-notify	This index is identical to entPhysicalIndex in ENTITY-MIB.

RFC description

Manages Port Extender (PEX) specifications and port binding configurations on H3C network devices.

Start monitoring H3C/HPE Comware switch with Port Extender 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 HH3C-PEX-MIB

What Is HH3C-PEX-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description