H3C-FCOE-MIB: View SNMP OID List / Download MIB

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

This table facilitates configuration of FCoE parameters on a per Fibre Channel management instance.

There is one entry in this table for each Fibre Channel management instance.

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.

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.

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.

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.

Addressing mode(s) supported by the FCF. Implementations should fail SetRequests for unsupported modes. Enumeration: 'fpmaAndSpma': 3, 'fpma': 1, 'spma': 2.

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.

There is one entry in this table for each VLAN that is designated to transport FCoE traffic for a given Virtual Fabric.

This object identifies the VLAN-ID that the FCoE FCF function is being enabled for.

This object identifies the Fabric Index of the Virtual Fabric traffic which is to be transported over the VLAN identified by h3cFCoEVLANIndex.

Operational state of this VLAN-Virtual Fabric association entry. The 'up' state is achieved when both the Virtual Fabric and VLAN are valid. Enumeration: 'down': 2, 'up': 1.

The status of this conceptual row. The RowStatus becomes active on successful creation of an entry.

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.

There is one entry in this table for each statically created VFC Interface.

This index uniquely identifies a static VFC entry in this table.

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.

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.

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.

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.

The ifIndex of this Virtual FC interface.

The timestamp of this entry's creation time.

The cause of failure for the last bind operation. This object will be zero length if and only if the bind is successful.

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.