MIB Example

The table hwEntityStateTable describes the status of the device, including the status of management, operation, and backup, CPU usage and threshold, and memory usage and threshold. This topic describes how to query CPU usage of all components based on hwEntityCpuUsage in hwEntityStateTable and CPU usage of a specified component based on its entPhysicalIndex.

This topic describes how to query memory usage of all components based on hwEntityMemUsage in hwEntityStateTable and memory usage of a specified component based on its entPhysicalIndex.

This topic describes how to query the temperature of all components based on hwEntityTemperature in hwEntityStateTable and the temperature of a specified component based on entPhysicalIndex.

The hwBoardPowerMngtTable table describes power information about the device and power supplies. You can obtain the rated power of all boards and power supplies through hwBoardRatedPower in the hwBoardPowerMngtTable table.

The objects hwPowerConsumption, hwAveragePower, hwRatedPower, and hwCurrentPower respectively describe the historical power consumption, average power, rated power, power threshold, and current power of the device.

For example, you can query the average power through the hwAveragePower object. As shown in Figure 3-46, the average power of the device is 174,435 mW.

Figure 3-46 Querying the average power through the hwAveragePower object

This topic describes how to query the serial numbers (SNs) of all components based on entPhysicalSerialNum in entPhysicalTable and the SN of a specified component based on entPhysicalIndex.

The table hwOpticalModuleInfoTable provides basic information about optical modules, including temperature, voltage, receive power, and transmit power.

The table hwRUModuleInfoTable describes the electronic labels of components, including the component model, part number, and production date.

You can obtain voltage information about all components through hwEntityVoltage in hwEntityStateTable and obtain voltage information about a specified component through entPhysicalIndex.

You can obtain the status of all fans through hwEntityFanState in hwFanStatusTable.

You can query and set the system energy-saving mode through hwEnergySavingMode.

Figure 3-56 shows how to configure the system energy-saving mode. Currently, userDefined(1) is not supported.

Figure 3-56 Configuring the system energy-saving mode through hwEnergySavingMode

You can query and set the interval for collecting power consumption data through hwPowerStatPeriod.

Figure 3-57 shows how to configure the interval for collecting power consumption data.

Figure 3-57 Configuring the interval for collecting power consumption data through hwPowerStatPeriod

hwSysSlaveSwitchTable describes the active/standby switchover configuration, including the chassis ID, operation type, and whether the active/standby switchover is enabled. hwSysSlaveSwitchEnableStatus indicates whether the active/standby switchover is enabled on a device.

Figure 3-58 shows how to query the active/standby switchover status through hwSysSlaveSwitchEnableStatus.

Figure 3-58 Querying the active/standby switchover status through hwSysSlaveSwitchEnableStatus

This topic describes how to query whether an interface is Up or Down after obtaining the index of the interface based on ifDescr. Figure 3-59 is used as an example.

• The index of GE9/0/2 is 351.
• The index of GE9/0/3 is 352.
• The index of GE9/0/4 is 353.

Figure 3-59 Mapping between the interface and index

After obtaining the mapping between the interface and index, query interface status based on ifAdminStatus and ifOperStatus, as shown in Figure 3-60 and Figure 3-61.

• GE9/0/2 with the index of 351: The expected physical status is Down, and its configuration status is Down, indicating that the shutdown command has been configured on the interface.
• GE9/0/3 with the index of 352: The expected physical status is Up, and its configuration status is Down, indicating that the shutdown command has not been configured on the interface. The actual physical status is Down due to some reasons. For example, no network cable is connected to the interface.
• GE9/0/4 with the index of 353: The expected physical status is Up, its configuration status is Up, and the shutdown command has not been configured on the interface. Therefore, the actual physical status is Up.

Figure 3-60 Expected physical status of the interface

Figure 3-61 Current configuration status of the interface

ifOperStatus specifies the physical status of a Layer 2 physical interface. When you want to query the protocol status of an interface, note the following:

The protocol status of a Layer 2 physical interface is the same as the current configuration status of the interface.

Before querying statistics about packets on an interface, obtain the index of the interface based on ifDescr. As shown in Figure 3-62, the index of GE9/0/1 is 350.

Figure 3-62 Obtaining the interface index

After obtaining the mapping between the interface and index, query the statistics about incoming packets and dropped incoming packets on the interface based on ifInOctets and ifInDiscards, as shown in Figure 3-63 and Figure 3-64. The interface GE9/0/1 with the index of 350 receives 304,635,051 bytes of packets, among which no packet is dropped.

Figure 3-63 Total bytes of incoming packets

Figure 3-64 Number of dropped incoming packets

Before querying the MAC address of an interface, obtain the index of the interface based on ifDescr. As shown in Figure 3-65, the index of GE9/0/1 is 350.

Figure 3-65 Obtaining the interface index

After obtaining the mapping between the interface and index, query the MAC address of the interface based on ifPhysAddress. As shown in Figure 3-66, the MAC address of GE9/0/1 with the index of 350 is 00:E0:09:87:78:95.

Figure 3-66 MAC address of the interface

You can obtain the MAC address of a VLANIF interface in a similar way, as shown in Figure 3-67. The index of VLANIF 100 is 70, and its MAC address is 00:E0:09:87:78:95.

Figure 3-67 MAC address of the VLANIF interface

Before querying the rate of an interface, obtain the index of the interface based on ifDescr. Figure 3-68 is used as an example, and the index of GE9/0/4 is 353.

Figure 3-68 Mapping between the interface and index

After obtaining the mapping between the interface and index, query the estimated rate of the interface based on ifSpeed. As shown in Figure 3-69, the rate of GE9/0/4 with the index of 353 is 100 Mbit/s. After the query using command lines, the interface is configured with the rate of 100 Mbit/s.

Figure 3-69 Querying the rate based on ifSpeed

Figure 3-70 Configuration for querying the interface rate using command lines

As shown in Figure 3-71, the ifSpeed value of XGE6/0/1 with the index of 6 is 4294967295, which exceeds the threshold. In this case, query the interface rate based on ifHighSpeed (OID: 1.3.6.1.2.1.31.1.1.1.15; unit: Mbit/s) in ifXTable. As shown in Figure 3-72, the rate of XGE6/0/1 with the index of 6 is 10,000 Mbit/s.

Figure 3-71 The ifSpeed value is 4294967295

Figure 3-72 Querying the interface rate based on ifHighSpeed

hwTrunkIfTable describes some attributes of a trunk, including the index, ID, type, and minimum number of interfaces in Up state of a trunk. You can obtain the minimum number of interfaces in Up state of all trunks using hwTrunkIfMinLinkNum of hwTrunkIfTable, and query the minimum number of interfaces in Up state of a trunk using hwTrunkIfType, hwTrunkIfID, and hwTrunkIndex.

1. Query hwTrunkIndex based on hwTrunkIfType and hwTrunkIfID. As shown in Figure 3-73, the hwTrunkIndex of Eth-Trunk 10 is 1.
   Figure 3-73 Querying Trunk information
   
   
2. Query the minimum number of interfaces in Up state of a trunk in hwTrunkIfMinLinkNum based on hwTrunkIndex. As shown in Figure 3-74, the minimum number of interfaces in Up state of the trunk with the hwTrunkIndex being 1 is 1.
   Figure 3-74 Querying the minimum number of interfaces in Up state of a trunk
   
   

hwL2VlanMIBTable describes created VLAN information on the device, including the VLAN description and information about interfaces in VLANs.

You can query created VLAN information on the device through hwL2VlanDescr.

As shown in Figure 3-75, select hwL2VlanDescr and perform the Walk operation to query created VLAN information on the device.

For example, hwL2VlanDescr.2 (octet string) VLAN 0002 indicates that VLAN 2 has been created and the description of VLAN 2 is VLAN 0002. The following query result indicates that VLAN 1, VLAN 2, VLAN 3, VLAN 4, VLAN 10, and VLAN 11 have been created.

Figure 3-75 Querying VLAN information

hwL2VlanMIBTable describes created VLAN information on the device, including the VLAN description and information about interfaces in VLANs.

You can query information about all interfaces added to a VLAN in tagged and untagged modes through hwL2VlanPortList, excluding the Eth-Trunk.

To query information about the interfaces that join a VLAN, perform the following steps:

1. As shown in Figure 3-76, select hwL2VlanPortList and perform the Walk operation to query information about all created VLANs and interfaces that join the VLANs.
   The query result in red box is used as an example:

   • In the first column, the value 2 in hwL2VlanPortList.2 (octet string) indicates information about all interfaces in VLAN 2.
   • In the second column, 00.00.C0 is a set of indexes of interfaces in VLAN 2, which is displayed in hexadecimal notation. The value is converted into 00000000 00000000 11000000 in binary notation. The index starts from 0 in ascending order. The value 1 indicates that the corresponding interface joins VLAN 2. The query result indicates that interfaces 16 and 17 join VLAN 2.
   Figure 3-76 Querying information about interfaces in the VLAN
   

2. Query the mapping between interface names and interface indexes.

   hwL2IfTable describes information about Layer 2 interfaces. You can query the mapping between interface names and interface indexes through hwL2IfPortName.

   Table 3-8 Description of MIB objects

   Object	Description	OID
   hwL2IfPortName	This object indicates the interface name corresponding to the Layer 2 interface index.	1.3.6.1.4.1.2011.5.25.42.1.1.1.3.1.19

   As shown in Figure 3-77, select hwL2IfPortName and perform the Walk operation to query the interface names corresponding to all Layer 2 interface indexes on the device.

   The query result in red box is used as an example:

   hwL2IfPortName.16 (octet string) GigabitEthernet6/1/4 indicates that interface with index 16 corresponds to GigabitEthernet6/1/4, that is, GigabitEthernet6/1/4 joins VLAN 2.

   hwL2IfPortName.17 (octet string) GigabitEthernet6/1/5 indicates that interface with index 17 corresponds to GigabitEthernet6/1/5, that is, GigabitEthernet6/1/5 joins VLAN 2.

   Figure 3-77 Querying interface names
   

dot1dTpFdbTable describes existing MAC address entries on the device. dot1dTpFdbAddress describes MAC addresses, and dot1dTpFdbPort describes the Layer 2 interface indexes corresponding to the MAC addresses.

dot1dBasePortIfIndex in dot1dBasePortTable describes the mapping between Layer 2 interface indexes and interface indexes, and ifName describes the mapping between interface indexes and interface names.

Layer 2 interface indexes are a set of numbers that identify Layer 2 interfaces, and interface indexes are a set of numbers that identify all interfaces including Layer 2 and Layer 3 interfaces.

hwDynMacAddrQueryTable in the Huawei-specific MIB HUAWEI-L2MAM-MIB allows users to query dynamic MAC address entries on switches based on specified conditions. The first 11 objects are table indexes, and the remaining objects specify information about a MAC address table in hwDynMacAddrQueryTable.

Table 3-10 describes the rules for setting the values in hwDynMacAddrQueryConditionMode.

hwMstpStatus describes whether STP is enabled globally. When multiple processes are used, query the STP status in process 0.

hwMstpProTable describes MSTP process information, including the status, priority, and root bridge type. You can learn about the STP status of all processes using hwMstpProStpState in hwMstpProTable.

hwMstpProNewPortTable describes information about an interface, including the interface status and priority. You can learn about the STP status of an interface by using hwMstpProNewPortStpStatus in the hwMstpProNewPortTable.

The steps are as follows:

1. Perform the Get operation for hwMstpStatus to query the STP status globally.
   
   
2. Perform the Walk operation for hwMstpProStpState to query the STP status in a process.
   
   
3. Query the STP status on an interface.
   1. You can view the relationships between interface names and indexes by using hwL2IfPortName.
      
      

   2. You can learn about the STP status of an interface by using hwMstpProNewPortStpStatus in the hwMstpProNewPortTable. Deduct 1 from an interface index to obtain the hwMstpPortId1 value. For example, the interface index of XGigabitEthernet6/0/3 is 11. Deduct 1 from 11 to obtain the hwMstpPortId1 value 10 (0.0.hwMstpPortId1=10.0.0.0.0), that is hwMstpProNewPortStpStatus.0.0.10.0.0.0.0 (integer) enabled(1). Therefore, the STP status of XGigabitEthernet6/0/3 is Enabled.

      
      
      

hwMstpForceVersion describes the STP type. When multiple processes are used, query the STP type in process 0. The value 0 indicates STP; the value 2 indicates RSTP; the value 3 indicates MSTP.

hwMstpProTable describes MSTP process information, including the status, priority, and root bridge type. You can learn about STP types of all processes using hwMstpProForceVersion in hwMstpProTable. The value 0 indicates STP; the value 2 indicates RSTP; the value 3 indicates MSTP.

Use either of the following methods to query the STP type:

• Perform the Get operation for the hwMstpForceVersion object.

  
  
  

• Perform the Walk operation for the hwMstpProForceVersion object.

  
  
  

hwMstpProNewPortTable describes information about an interface, including the interface status and priority. You can learn about the forwarding status of an interface using hwMstpProNewPortState in hwMstpProNewPortTable.

The steps are as follows:

1. You can view the relationships between interface names and indexes by using hwL2IfPortName.
   
   

2. You can learn about the forwarding status of an interface using hwMstpProNewPortState in hwMstpProNewPortTable. Deduct 1 from an interface index to obtain the hwMstpPortId1 value. For example, the interface index of XGigabitEthernet6/0/3 is 11. Deduct 1 from 11 to obtain the hwMstpPortId1 value 10 (0.0.hwMstpPortId1=10.0.0.0.0), that is hwMstpProNewPortState.0.0.10.0.0.0.0 (integer) forwarding(5). Therefore, the forwarding status of XGigabitEthernet6/0/3 is Forwarding.

   
   
   

You can use the object ipAdEntAddr to query IP addresses of all interfaces, as shown in Figure 3-96.

Figure 3-96 Using the object ipAdEntAddr to query IP addresses of all interfaces

To query the IP address of an interface, perform the following operations:

1. Use the object ifDescr to query the interface index.

   As shown in Figure 3-97, the interface index of VLANIF100 is 59.

   Figure 3-97 Using the object ifDescr to query the interface index
   

2. Use the object ipAdEntIfIndex to query the interface IP address.

   As shown in Figure 3-98, the IP address of VLANIF100 is 172.16.1.3.

   Figure 3-98 Using the object ipAdEntIfIndex to query the interface IP address
   

vrrpOperTable describes VRRP group information, including the VRID of the VRRP group, virtual MAC address, and interval at which VRRP Advertisement packets are sent.

You can learn about the VRRP group status (initialize, master, or backup) using vrrpOperState in vrrpOperTable.

As shown in Figure 3-103, select vrrpOperState and perform the Walk operation to query the status of all VRRP groups.

In vrrpOperState.115.1 (integer) master(3), the value 115 is the index of the interface where the VRRP group is configured, the value 1 is the VRID of the VRRP group, and master(3) indicates that the VRRP group is in master state.

Figure 3-103 Querying VRRP group information

vrrpOperTable describes VRRP group information, including the VRID of the VRRP group, virtual MAC address, and interval at which VRRP Advertisement packets are sent.

You can learn about the virtual MAC addresses of all VRRP groups using vrrpOperVirtualMacAddr in vrrpOperTable.

As shown in Figure 3-104, select vrrpOperVirtualMacAddr and perform the Walk operation to query virtual MAC addresses of all VRRP groups.

In vrrpOperVirtualMacAddr.115.1 (octet string) 00:00:5E:00:01:01 [00.00.5E.00.01.01 (hex)], the value 115 is the index of the interface where the VRRP group is configured, the value 1 is the VRID of the VRRP group, and the value 00:00:5E:00:01:01 indicates the virtual MAC address of the VRRP group.

Figure 3-104 Querying the virtual MAC address of the VRRP group

The table hwXQosBaCfgInfoTable allows you to query a Diff-Serv profile and its application.

1. Query the index of the Diff-Serv profile by performing the Walk operation for the Walk hwXQosBaName object. As shown in Figure 3-105, the index of the Diff-Serv profile ISR is 1.

   Figure 3-105 Querying the index of the Diff-Serv profile
   

2. Query the application status of the Diff-Serv profile based on the index by performing the Walk operation for the hwXQosBaRowStatus object. As shown in Figure 3-106, the application status of the ISR profile is active.

   Figure 3-106 Querying the application status of the Diff-Serv profile
   

The table hwXQosBaPhbCfgInfoTable allows you to query the mapping from the external priority to the internal priority and color in a Diff-Serv profile.

1. Query the index of the Diff-Serv profile by performing the Walk operation for the Walk hwXQosBaName object. As shown in Figure 3-107, the index of the 1212 profile is 3.

   Figure 3-107 Querying the index of the Diff-Serv profile
   
2. Query the internal priority hwXQosBaPhbCos based on hwXQoSBaIndex, hwXQoSBaPhbType, and hwXQoSBaPhbPri by performing the Get operation for the hwXQosBaPhbCos object.

   • hwXQoSBaIndex: specifies the index of the Diff-Serv profile.
   • hwXQoSBaPhbType: specifies the priority field type, whose value is 1 for the 802.1p priority and 2 for the DSCP priority.
   • hwXQoSBaPhbPri: specifies the value of the priority field.
   • hwXQosBaPhbCos: specifies the value of the internal priority. For mapping between the internal priority and CoS, see hwXQosBaPhbCfgInfoTable.

   As shown in Figure 3-108, the value of hwXQosBaPhbCos is hwXQosBaPhbCos.A.B.C, among which A indicates hwXQoSBaIndex, B indicates hwXQoSBaPhbType, and C indicates hwXQoSBaPhbPri. hwXQoSBaIndex, hwXQoSBaPhbType, and hwXQoSBaPhbPri uniquely identify the value of the internal priority hwXQosBaPhbCos. In Figure 3-108, the value of hwXQosBaPhbCos.3.1.0 is 0, indicating that the 802.1p priority 0 is mapped to the internal priority BE in the inbound direction in the Diff-Serv profile 1212.

   Figure 3-108 Querying the internal priority
   

3. Query the packet color hwXQosBaPhbColour based on hwXQoSBaIndex, hwXQoSBaPhbType, and hwXQoSBaPhbPri by performing the Get operation for the hwXQosBaPhbColour object. As shown in Figure 3-109, the value of hwXQosBaPhbColour is hwXQosBaPhbCos.A.B.C, among which A indicates hwXQoSBaIndex, B indicates hwXQoSBaPhbType, and C indicates hwXQoSBaPhbPri. hwXQoSBaIndex, hwXQoSBaPhbType, and hwXQoSBaPhbPri uniquely identify the packet color hwXQosBaPhbColour. In Figure 3-108, the value of hwXQosBaPhbColour.3.1.0 is yellow, indicating that the 802.1p priority 0 is mapped to yellow in the inbound direction in the Diff-Serv profile 1212.

   Figure 3-109 Querying the packet color
   

The table hwXQoSBaMapCfgInfoTable allows you to query the mapping from the internal priority and color to the external priority in a Diff-Serv profile.

1. Query the index of the Diff-Serv profile by performing the Walk operation for the Walk hwXQosBaName object. As shown in Figure 3-110, the index of the 1212 profile is 3.

   Figure 3-110 Querying the index of the Diff-Serv profile
   
2. Query the value of hwXQosBaMapPri based on hwXQosBaIndex, hwXQosBaMapType, hwXQosBaMapCos, and hwXQosBaMapColour by performing the Get operation for the hwXQosBaMapPri object.

   • hwXQoSBaIndex: specifies the index of the Diff-Serv profile.
   • hwXQosBaMapType: specifies the external priority field type, whose value is 1 for the 802.1p priority and 2 for the DSCP priority.
   • hwXQosBaMapCos: specifies the value of the internal priority. For mapping between the internal priority and CoS, see hwXQosBaPhbCfgInfoTable.
   • hwXQosBaMapColour: specifies the packet color whose value is 1 for green packets, 2 for yellow packets, and 3 for red packets.
   • hwXQosBaMapPri: specifies the value of the external priority.

   As shown in Figure 3-111, the value of hwXQosBaMapPri is hwXQosBaMapPri.A.B.C.D, among which A indicates hwXQosBaIndex, B indicates hwXQosBaMapType, C indicates hwXQosBaMapCos, and D indicates hwXQosBaMapColour. hwXQosBaIndex, hwXQosBaMapType, hwXQosBaMapCos, and hwXQosBaMapColour uniquely identify the value of the external priority hwXQosBaMapPri. In Figure 3-111, the value of hwXQosBaPhbCos.3.1.2.2 is 7, indicating that the internal priority AF2 of yellow packets is mapped to the external priority 7 in the outbound direction in the Diff-Serv profile 1212.

   Figure 3-111 Querying the external priority
   

The table hwXQoSIfQueueRunInfoTable allows you to query statistics about eight queues on an interface.

1. Query the index hwXQoSIfQueueIfIndex of the interface by referring to Querying Interface Information. This topic assumes that the interface index on GE1/0/5 is 9.

2. Query the number of packets passing through a queue (hwXQoSIfQueuePassedPackets) based on hwXQoSIfQueueIfIndex, hwXQoSIfQueueVlanID, and hwXQoSIfQueueCosType by performing the Get operation for the hwXQoSIfQueuePassedPackets object.

   • hwXQoSIfQueueIfIndex: specifies the interface index.
   • hwXQoSIfQueueVlanID: specifies the VLAN ID, which is 0 currently because this parameter is invalid.
   • hwXQoSIfQueueCosType: specifies the queue number whose value is 1 for the BE queue, 2 for the AF1 queue, 3 for the AF2 queue, 4 for the AF3 queue, 5 for the AF4 queue, 6 for the EF queue, 7 for the CS6 queue, and 8 for the CS7 queue.

   As shown in Figure 3-112, the value of hwXQoSIfQueuePassedPackets is hwXQoSIfQueuePassedPackets.A.B.C, among which A indicates hwXQoSIfQueueIfIndex, B indicates hwXQoSIfQueueVlanID, and C indicates hwXQoSIfQueueCosType. hwXQoSIfQueueIfIndex, hwXQoSIfQueueVlanID, and hwXQoSIfQueueCosType uniquely identify the value of hwXQoSIfQueuePassedPackets. In Figure 3-112, the value of hwXQoSIfQueuePassedPackets.9.0.1 is 16975988764, indicating that 16,975,988,764 packets pass through the BE queue on GE1/0/5.

   Figure 3-112 Querying the number of packets passing through the queue
   
   

3. Query the bytes of packets passing through a queue (hwXQoSIfQueuePassededBytes) based on hwXQoSIfQueueIfIndex, hwXQoSIfQueueVlanID, and hwXQoSIfQueueCosType by performing the Get operation for the hwXQoSIfQueuePassededBytes object. The method is the same as that for querying the number of packets passing through a queue.

   In Figure 3-113, the value of hwXQoSIfQueuePassededBytes.9.0.1 is 4146197780262, indicating that 4,146,197,780,262-byte packets pass through the BE queue on GE1/0/5.

   Figure 3-113 Querying the bytes of packets passing through the queue
   
   

4. Query the number of dropped packets in a queue (hwXQoSIfQueueDiscardedPackets) based on hwXQoSIfQueueIfIndex, hwXQoSIfQueueVlanID, and hwXQoSIfQueueCosType by performing the Get operation for the hwXQoSIfQueueDiscardedPackets object. The method is the same as that for querying the number of packets passing through a queue.

   In Figure 3-114, the value of hwXQoSIfQueueDiscardedPackets.9.0.1 is 24754721880, indicating that 24,754,721,880 packets are dropped in the BE queue on GE1/0/5.

   Figure 3-114 Querying the number of dropped packets in the queue
   
   

5. Query the bytes of dropped packets in a queue (hwXQoSIfQueueDiscardedBytes) based on hwXQoSIfQueueIfIndex, hwXQoSIfQueueVlanID, and hwXQoSIfQueueCosType by performing the Get operation for the hwXQoSIfQueueDiscardedBytes object. The method is the same as that for querying the number of packets passing through a queue.

   In Figure 3-115, the value of hwXQoSIfQueueDiscardedBytes.9.0.1 is 5897696774720, indicating that 5,897,696,774,720-byte packets are dropped in the BE queue on GE1/0/5.

   Figure 3-115 Querying the bytes of dropped packets in the queue
   
   

The table hwCBQoSClassifierCfgInfoTable allows you to query information about a traffic classifier.

1. Query the index hwCBQoSClassifierIndex of the traffic classifier based on hwCBQoSClassifierName by performing the Walk operation for the table hwCBQoSClassifierCfgInfoTable. As shown in Figure 3-116, the index hwCBQoSClassifierIndex of the traffic classifier ISR is 2.

   Figure 3-116 Querying the index of the traffic classifier
   
2. Query information about the traffic classifier based on hwCBQoSClassifierRuleCount and hwCBQoSClassifierOperator by performing the Walk operation for the table hwCBQoSClassifierCfgInfoTable.

   • hwCBQoSClassifierRuleCount: specifies the number of matching rules in the traffic classifier.
   • hwCBQoSClassifierOperator: specifies the relationships between rules in the traffic classifier.

   As shown in Figure 3-117, the value of hwCBQoSClassifierRuleCount is hwCBQoSClassifierRuleCount.A, and the value of hwCBQoSClassifierOperator is hwCBQoSClassifierOperator.A. A indicates hwCBQoSClassifierIndex. hwCBQoSClassifierRuleCount and hwCBQoSClassifierOperator uniquely identify information about the traffic classifier. In Figure 3-117, the value of hwCBQoSClassifierRuleCount.2 is 3, indicating that the ISR traffic classifier has three rules. The value of hwCBQoSClassifierOperator.2 is or, indicating that the relationship between the two rules is OR. Information about hwCBQoSClassifierLayer can be ignored.

   Figure 3-117 Querying the relationship between the number of rules and relationship between rules in the traffic classifier
   
3. Query information about a rule in the traffic classifier based on hwCBQoSClassifierIndex and hwCBQoSMatchRuleIndex by performing the Walk operation for the table hwCBQoSClassifierCfgInfoTable.

   • hwCBQoSClassifierIndex: specifies the index of the traffic classifier.
   • hwCBQoSMatchRuleIndex: specifies the index of the rule.

   As shown in Figure 3-118, the value of hwCBQoSMatchRuleType is hwCBQoSMatchRuleType.A.B, and the value of hwCBQoSMatchRuleIntValue1 is hwCBQoSMatchRuleIntValue1.A.B. A indicates hwCBQoSClassifierIndex, and B indicates hwCBQoSMatchRuleIndex. hwCBQoSClassifierIndex and hwCBQoSMatchRuleIndex uniquely identify information about a rule, including hwCBQoSMatchRuleType, hwCBQoSMatchRuleStringValue, and hwCBQoSMatchRuleIntValue1.

   For the description and specifications of each object for a matching rule, refer to hwCBQoSMatchRuleCfgInfoTable.

   In Figure 3-118, hwCBQoSMatchRuleType.2.0 and hwCBQoSMatchRuleIntValue1.2.0 indicates that packets from VLAN 500 match the first rule in the traffic classifier ISR.

   Figure 3-118 Querying information about the rule
   

The table hwCBQoSCarCfgInfoTable allows you to query information about traffic policing.

The index of the table hwCBQoSCarCfgInfoTable is hwCBQoSBehaviorIndex. For details about the table, see hwCBQoSCarCfgInfoTable.

This topic describes how to query the committed information rate (hwCBQoSCarCir), committed burst size (hwCBQoSCarCbs), peak information rate (hwCBQoSCarPir), and peak burst size (hwCBQoSCarPbs).

1. Query the index of a traffic behavior by performing the Walk operation for the table hwCBQoSBehaviorCfgInfoTable. As shown in Figure 3-119, the index of traffic behavior ISR is 2.

   Figure 3-119 Querying the index of the traffic behavior
   
2. Query the traffic policing configuration of traffic behavior with the index of 2 by performing the Walk operation for the hwCBQoSCarCfgInfoTable. As shown in Figure 3-120, the CIR is 8,192 kbps, the CBS is 1,024,000 bytes, the PIR is 10,240 kbps, and the PBS is 1,280,000 bytes.
   Figure 3-120 Querying the traffic policing configuration
   

Query the remarking configuration (hwCBQoSRemarkCfgInfoTable), traffic filtering configuration (hwCBQoSFirewallCfgInfoTable), traffic mirroring configuration (hwCBQoSMirrorCfgInfoTable), and traffic count configuration (hwCBQoSCountCfgInfoTable) in the similar method. Query the index of the traffic behavior based on hwCBQoSBehaviorCfgInfoTable and then query the required information in corresponding tables.

The LLDP MIB provides functions including configuring LLDP, querying LLDP packet statistics, and querying information about the local device and neighbors. The LLDP MIB also allows traps of specified events to be sent to the NMS.

Root object:

iso(1).std(0).iso8802(8802).ieee802dot1(1).ieee802dot1mibs(1).lldpMIB(2)

The section "LLDP-MIB" in MIB Reference describes MIBs in details. This topic describes some MIB objects and parameters.

HUAWEI-LLDP-MIB is an extension of LLDP-MIB. HUAWEI-LLDP-MIB allows you to enable or disable global LLDP, configure management IPv4 addresses in the NMS, clear statistics about received and sent LLDP packets, and enable or disable the global trap function.

Root object:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).huawei(2011).huaweiMgmt(5).hwDatacomm(25).hwLldpMIB(134)

The section "HUAWEI-LLDP-MIB" in MIB Reference describes MIBs in details. This topic describes some MIB objects and parameters.

Search for the result of the corresponding test instance by using nqaAdminCtrlOwnerIndex and nqaAdminCtrlTestName, and then search for the result of the specified test instance by using nqaResultsIndex and nqaResultsHopIndex.

1. nqaAdminCtrlTable describes the configuration of NQA test instances. Figure 3-141 shows the NQA test instance information. The combination of nqaAdminCtrlOwnerIndex and nqaAdminCtrlTestName of test instance icmp01 is 5.97.100.109.105.110.4.105.99.109.112.
   Figure 3-141 Test instance information
   
2. nqaResultsTable describes the running results of NQA test instances. Figure 3-142 shows the NQA test instance running results. The combination of nqaAdminCtrlOwnerIndex and nqaAdminCtrlTestName of test instance icmp01 is 5.97.100.109.105.110.4.105.99.109.112, and the combination of nqaResultsIndex and nqaResultsHopIndex is 1.1.
   Figure 3-142 Test instance running results