H3C-FCOE-MIB

All MIBs › H3C-FCOE-MIB

Organization: Hangzhou H3C Technologies Co., Ltd.

Last Updated: 2012-03-28

Category: Fibre Channel and Storage, Vendor: H3C/HH3C

Description: H3C MIB for Fibre Channel over Ethernet (FCoE) managing virtual Fibre Channel interfaces and FCoE forwarders.

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 H3C-FCOE-MIB?

This is an H3C vendor MIB for managing Fibre Channel over Ethernet (FCoE) on H3C data center switches, covering configuration and monitoring of Virtual Fibre Channel (VFC) interfaces representing VF_Port or VE_Port roles on an FCoE Forwarder (FCF). It exposes FCoE global configuration (FC-MAP, dynamic VFC creation, default FCF priority, discovery advertisement timeout, addressing mode) as well as per-VLAN FCoE operational state. Its monitoring value focuses on the operational status of the FCoE fabric layer, whether FCoE VLANs and VFC interfaces are operationally up and whether FIP-based login/discovery is functioning, reflecting the software/protocol health of the converged storage network rather than physical disk hardware. It is built on and interoperates with the FC-BB-5 (FCoE) standard referenced in its description, and depends on underlying VLAN and Ethernet interface MIBs for the transport layer. It is deployed on H3C data center switches acting as FCoE Forwarders, converging Fibre Channel SAN traffic onto Ethernet fabric. Engineers can download the H3C-FCOE-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in H3C-FCOE-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 data center Ethernet switches acting as FCoE Forwarders (FCF)

Monitoring Examples

An administrator would poll h3cFCoECfgTable/h3cFCoECfgEntry to check h3cFCoECfgFcmap and h3cFCoECfgDefaultFCFPriority, confirming the correct FC-MAP and forwarder priority are set for FCoE fabric login negotiation. Checking h3cFCoEVLANTable/h3cFCoEVLANEntry and h3cFCoEVLANOperState per h3cFCoEFabricIndex would reveal whether a specific FCoE VLAN/fabric has gone operationally down, explaining storage connectivity loss to hosts on that VLAN. Reviewing h3cFCoECfgDATov (discovery advertisement timeout) helps troubleshoot FIP login timing issues during host re-registration or FLOGI.

What Can Be Monitored

FCoE VLAN operational state
VFC interface configuration
FC-MAP and FCF priority settings
FIP discovery advertisement timeout
addressing mode configuration

Imported Objects

From FC-MGMT-MIB

fcmInstanceIndex

OBJECT-TYPE

From HUAWEI-3COM-OID-MIB

h3cCommon

OBJECT-IDENTITY

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From Q-BRIDGE-MIB

VlanIndex

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

MacAddress
RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

From T11-TC-MIB

T11FabricIndex

OIDs

OID symbolic	OID numeric	Type	Access	Description
h3cFCoE	1.3.6.1.4.1.2011.10.2.120			This MIB module is for configuring and monitoring Fibre Channel over Ethernet (FCoE) related entities. This MIB defines a Virtual FC (VFC) Interface as an object that represents either a VF_Port or a VE_Port on a FCoE Forwarder (FCF). VFC interfaces can be created either statically (by management request) or dynamically (at the time of FIP based FLOGI or ELP request). Other terminologies used in this MIB are defined by the H3c FCoE standard, as defined in the FC-BB-5 specification. See www.h3c.com for more information. This MIB also supports configuration of the following objects: - Mapping of FCoE VLAN-ID used to carry traffic for a Fabric - FC-MAP value used by the FCF operating in FPMA mode - FIP snooping related objects
h3cFCoEObjects	1.3.6.1.4.1.2011.10.2.120.1
h3cFCoEConfig	1.3.6.1.4.1.2011.10.2.120.1.1
h3cFCoECfgTable	1.3.6.1.4.1.2011.10.2.120.1.1.1		not-accessible	This table facilitates configuration of FCoE parameters on a per Fibre Channel management instance.
h3cFCoECfgEntry	1.3.6.1.4.1.2011.10.2.120.1.1.1.1		not-accessible	There is one entry in this table for each Fibre Channel management instance.
OCT h3cFCoECfgFcmap	1.3.6.1.4.1.2011.10.2.120.1.1.1.1.1	OCTET STRING	read-write	This object configures the FC-MAP value used by the FCF when operating in FPMA mode. The default value is 0EFC00h, as written in the standard.
T/F h3cFCoECfgDynamicVfcCreation	1.3.6.1.4.1.2011.10.2.120.1.1.1.1.2	TruthValue	read-write	This object is set to 'true' to enable, or 'false' to disable, the dynamic creation of VFC interfaces on this FCF. When set to 'true', VFC interfaces are dynamically created as and when a FIP-based FLOGI or ELP request is received.
U32 h3cFCoECfgDefaultFCFPriority	1.3.6.1.4.1.2011.10.2.120.1.1.1.1.3	Unsigned32	read-write	The FIP priority value advertised by the FCF to ENodes by default. h3cFCoEStaticVfcFCFPriority configured for a VFC interface overrides this setting for the ENode associated with the VFC.
U32 h3cFCoECfgDATov	1.3.6.1.4.1.2011.10.2.120.1.1.1.1.4	Unsigned32	read-write	The Discovery_Advertisement_Timeout value configured for the FCF. This is used as the timeout value in seconds by the FCF to send periodic Discovery Advertisements.
INT h3cFCoECfgAddressingMode	1.3.6.1.4.1.2011.10.2.120.1.1.1.1.5	INTEGER	read-write	Addressing mode(s) supported by the FCF. Implementations should fail SetRequests for unsupported modes.
h3cFCoEVLANTable	1.3.6.1.4.1.2011.10.2.120.1.1.2		not-accessible	In fabrics in which VLANs are deployed, this table facilitates configuration of VLAN and Virtual Fabric associations in an FCoE network. In such fabrics, FCoE forwarding for a fabric is over a VLAN in a (Layer-2) Ethernet network. That is, reachability between the ENode/remote-FCF and an FCF for a given fabric is determined by the reachability provided by the Ethernet network on the corresponding VLAN. An active entry in this table indicates which VLAN is used to transport FCoE traffic for a particular Virtual Fabric. If VLANs are not deployed or not enabled, entries in this table are ignored by the bridge. Some implmentations may allow traffic from only one Virtual Fabric to be transported over a given VLAN. Such implementations should prevent multiple entries with the same VLAN-ID from being created in this table. Modifying existing VLAN-Virtual Fabric associations is not possible. The specific row must first be deleted and then a new one created.
h3cFCoEVLANEntry	1.3.6.1.4.1.2011.10.2.120.1.1.2.1		not-accessible	There is one entry in this table for each VLAN that is designated to transport FCoE traffic for a given Virtual Fabric.
VLA h3cFCoEVLANIndex	1.3.6.1.4.1.2011.10.2.120.1.1.2.1.1	VlanIndex	not-accessible	This object identifies the VLAN-ID that the FCoE FCF function is being enabled for.
T11 h3cFCoEFabricIndex	1.3.6.1.4.1.2011.10.2.120.1.1.2.1.2	T11FabricIndex	not-accessible	This object identifies the Fabric Index of the Virtual Fabric traffic which is to be transported over the VLAN identified by h3cFCoEVLANIndex.
INT h3cFCoEVLANOperState	1.3.6.1.4.1.2011.10.2.120.1.1.2.1.3	INTEGER	read-only	Operational state of this VLAN-Virtual Fabric association entry. The 'up' state is achieved when both the Virtual Fabric and VLAN are valid.
ROW h3cFCoEVLANRowStatus	1.3.6.1.4.1.2011.10.2.120.1.1.2.1.4	RowStatus	read-create	The status of this conceptual row. The RowStatus becomes active on successful creation of an entry.
h3cFCoEStaticVfcTable	1.3.6.1.4.1.2011.10.2.120.1.1.3		not-accessible	This table facilitates the creation and deletion of static VFC interfaces. While VFCs can be dynamically created based on FIP FLOGI/ELP requests, operators may want to associate certain pre-configured policy for a particular ENode or a remote-FCF. In such cases static VFC creation becomes necessary. In addition to being creating, a static VFC also needs to be associated to an ENode or remote-FCF. The VFC binding provides such an associaton. The binding does not need to be specified when the row for a VFC is created, but may be specified later.
h3cFCoEStaticVfcEntry	1.3.6.1.4.1.2011.10.2.120.1.1.3.1		not-accessible	There is one entry in this table for each statically created VFC Interface.
U32 h3cFCoEStaticVfcIndex	1.3.6.1.4.1.2011.10.2.120.1.1.3.1.1	Unsigned32	not-accessible	This index uniquely identifies a static VFC entry in this table.
U32 h3cFCoEStaticVfcFCFPriority	1.3.6.1.4.1.2011.10.2.120.1.1.3.1.2	Unsigned32	read-create	If this VFC is for a VF_Port this object is used to configure FCF priority to be advertised to the ENode associated with the VFC.
H3C h3cFCoEStaticVfcBindType	1.3.6.1.4.1.2011.10.2.120.1.1.3.1.3	H3cFCoEVfcBindType	read-create	The mechanism to identify the ENode associated with this VFC if it is of type VF_Port or to identify the remote-FCF associated with this VFC if it is of type VE_Port.
NUM h3cFCoEStaticVfcBindIfIndex	1.3.6.1.4.1.2011.10.2.120.1.1.3.1.4	InterfaceIndexOrZero	read-create	This object is applicable only when the local FCF is directly connected to an ENode or remote-FCF over a specific Ethernet interface, in which case this object contains the ifIndex of said Ethernet interface. If the ENode or remote-FCF is not directly connected to the FCF, this value of this object is zero.
MAC h3cFCoEStaticVfcBindMACAddress	1.3.6.1.4.1.2011.10.2.120.1.1.3.1.5	MacAddress	read-create	This object is applicable when the ENode or remote-FCF to which the local FCF is connected is identified by a MAC address. A FIP frame from a ENode or remote-FCF is associated with this VFC only if the source MAC address in the frame is the same as the value of this object.
NUM h3cFCoEStaticVfcIfIndex	1.3.6.1.4.1.2011.10.2.120.1.1.3.1.6	InterfaceIndex	read-only	The ifIndex of this Virtual FC interface.
TIM h3cFCoEStaticVfcCreationTime	1.3.6.1.4.1.2011.10.2.120.1.1.3.1.7	TimeStamp	read-only	The timestamp of this entry's creation time.
STR h3cFCoEStaticVfcFailureCause	1.3.6.1.4.1.2011.10.2.120.1.1.3.1.8	SnmpAdminString	read-only	The cause of failure for the last bind operation. This object will be zero length if and only if the bind is successful.
ROW h3cFCoEStaticVfcRowStatus	1.3.6.1.4.1.2011.10.2.120.1.1.3.1.9	RowStatus	read-create	The status of this conceptual row. The RowStatus becomes active on successful creation of a VFC. The VFC does not need to be bound for the row to be active, but the VFC must be bound before becoming operational.
h3cFCoEFIPSnoopingObjects	1.3.6.1.4.1.2011.10.2.120.1.2

RFC description

Fibre Channel over Ethernet (FCoE) configuration and Virtual FC interface management.

Start monitoring H3C data center Ethernet switches 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 H3C-FCOE-MIB

What Is H3C-FCOE-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description