HH3C-IF-EXT-MIB Table View

This table contains objects to get statistic information
of interfaces on a device.

This table contains objects to get average speed information
in the specified interval for interfaces on a device.

This table contains objects to get statistic information
of interfaces on a device.

This table contains objects to get average speed information
in the specified interval for interfaces on a device.
          
This table is a 64-bit version of hh3cIfSpeedStatTable.

This table contains all interfaces that can create subinterfaces.

This table contains objects to create or delete subinterfaces.
To create a subinterface, a valid parent interface must be
specified by hh3cRTSubIfParentIfIndex, and hh3cRTSubIfOrdinal
must be in the range between hh3cRTMinSubIfOrdinal and
hh3cRTMaxSubIfOrdinal of the parent interface from
hh3cRTParentIfTable.
          
Subinterfaces are logical virtual interfaces configured on a
main interface.  The main interface can be either a physical
interface (such as a Layer 3 Ethernet interface) or a logical
interface (such as an MFR interface).  The subinterfaces on a
main interface share the physical layer parameters of the main
interface but can have link layer and network layer parameters
of their own.  Disabling or enabling a subinterface doesn't
affect the main interface, but the main interface status change
affects the subinterfaces.  The subinterfaces can't operate
correctly unless the main interface is connected.
Creating multiple subinterfaces on a single interface
enables you to plan network in a more flexible way.
          
You can create subinterfaces for the following physical
interfaces:
Ethernet interface.  An Ethernet subinterface associated with no
VLAN supports only IPX, while an Ethernet subinterface associated
with a VLAN supports both IP and IPX.
WAN interfaces with their data link layer protocols being frame
relay, whose subinterfaces support IP and IPX.
WAN interfaces with their data link layer protocols being X.25,
whose subinterfaces support IP and IPX.
ATM interface, whose subinterfaces support only IP.

This table contains objects to get or set the link mode of an
interface.
According to the layer at which the device processes received
data packets, Ethernet interfaces can operate in bridge or route
mode.

This table contains objects to get or set the port type
of an interface.

This table can set the inbound and outbound rate thresholds for the specified dot1p values.

This table contains objects to get the usage info, thresholds, and
statistics of queue buffers and to set the thresholds of queue buffers.

A list of interface entries.  The number of entries is given by
the value of IfNumber.

A table containing management information applicable to splitting
interfaces.  To improve port density, reduce costs, and improve network
flexibility, a high-bandwidth interface can be split into multiple
low-bandwidth breakout interfaces, and the breakout interfaces can be
combined into a higher-bandwidth interface.
For example, a 40-GE interface can be split into four 10-GE breakout
interfaces.  After the operation takes effect on a 40-GE interface, the
system deletes the 40-GE interface and creates four 10-GE breakout
interfaces.

The trap configuration table.

This table is about some types of statistics.

This table is about the upper threshold, lower threshold, CRC type, and inspection interval.
The upper threshold and lower threshold must be bound together.  If the CRC type is configured,
node hh3cIfMonCRCErrType must be carried.  If there is no current configuration for a type, all
attributes of this type must be carried.  After modification, the table hh3cIfMonAlarmDownEnableTable
will be changed.If there is configuration for the current type, setting all attributes of this type to
invalid values indicates that the configuration of this type is deleted, and the table hh3cIfMonAlarmDownEnableTable
will be changed.  Take CRC as an example.  If there is no CRC configuration, nodes hh3cIfMonCRCErrorLowThres,
hh3cIfMonCRCErrorLowThres, hh3cIfMonCRCErrorLowThres, and hh3cIfMonCRCErrorLowThres must be carried.
After modification, the node hh3cIfMonCRCErrorEnableDown becomes false.  If there is CRC configuration,
settings the nodes hh3cIfMonCRCErrorLowThres, hh3cIfMonCRCErrorHighThres, hh3cIfMonCRCErrorInterval,
and hh3cIfMonCRCErrorInterval to invalid values indicates the CRC configuration is deleted, and the
node hh3cIfMonCRCErrorEnableDown becomes invalid.

This table can set or get whether to enable the interface down function.