Login
- Table of Contents
-
- 08-Layer 3 - IP Services
- 01-HH3C-ARP-RATELIMIT-MIB
- 02-HH3C-ARP-SUPPRESSION-MIB
- 03-HH3C-ARP-TRAP-MIB
- 04-HH3C-BPA-MIB
- 05-HH3C-DHCP-SNOOP2-MIB
- 06-HH3C-DHCP4-CLIENT-MIB
- 07-HH3C-DHCP4-MIB
- 08-HH3C-DHCP6-MIB
- 09-HH3C-FIB-MIB
- 10-HH3C-IP-ADDRESS-MIB
- 11-HH3C-IPFW-MIB
- 12-HH3C-IPV6-ADDRESS-MIB
- 13-HH3C-NAT-MIB
- 14-HH3C-ND-TRAP-MIB
- 15-HH3C-SESSION-MIB
- 16-HH3C-TCP-MIB
- 17-HH3C-DNS-MIB
- 18-IP-MIB
- 19-IPV6-ICMP-MIB
- 20-IPV6-MIB
- 21-IPV6-TCP-MIB
- 22-IPV6-UDP-MIB
- 23-TCP-MIB
- 24-UDP-MIB
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 11-HH3C-IPFW-MIB | 130.99 KB |
Contents
hh3cIpfwIfIndex (1.3.6.1.4.1.25506.2.211.2.1.1)
hh3cIpfwPeerAddress (1.3.6.1.4.1.25506.2.211.2.1.2)
hh3cIpfwInterfaceName (1.3.6.1.4.1.25506.2.211.2.1.3)
hh3cIpfwChassis (1.3.6.1.4.1.25506.2.211.2.1.4)
hh3cIpfwSlot (1.3.6.1.4.1.25506.2.211.2.1.5)
hh3cIpfwVsysID (1.3.6.1.4.1.25506.2.211.2.1.6)
hh3cIpfwIPv4FragBufSrcAddress (1.3.6.1.4.1.25506.2.211.2.1.7)
hh3cIpfwIPv4FragBufDstAddress (1.3.6.1.4.1.25506.2.211.2.1.8)
hh3cIpfwIPv6FragBufSrcAddress (1.3.6.1.4.1.25506.2.211.2.1.9)
hh3cIpfwIPv6FragBufDstAddress (1.3.6.1.4.1.25506.2.211.2.1.10)
hh3cIpfwMbufAllocFailedNum (1.3.6.1.4.1.25506.2.211.2.1.11)
HH3C-IPFW-MIB
About this MIB
Use this MIB to obtain IP forwarding information and configure IP forwarding.
MIB file name
hh3c-ipfw.mib
Root object
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cIpfw(211)
Scalar objects
hh3cIpfwIfIndex (1.3.6.1.4.1.25506.2.211.2.1.1)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cIpfwIfIndex (1.3.6.1.4.1.25506.2.211.2.1.1) |
accessible-for-notify |
InterfaceIndex |
Integer32 (1..2147483647) |
Index of the interface from which packets are received. |
As per the MIB. |
hh3cIpfwPeerAddress (1.3.6.1.4.1.25506.2.211.2.1.2)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cIpfwPeerAddress (1.3.6.1.4.1.25506.2.211.2.1.2) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..255) |
Destination IP address of received packets. |
As per the MIB. |
hh3cIpfwInterfaceName (1.3.6.1.4.1.25506.2.211.2.1.3)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cIpfwInterfaceName (1.3.6.1.4.1.25506.2.211.2.1.3) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..255) |
Name of the interface from which packets are received. |
As per the MIB. |
hh3cIpfwChassis (1.3.6.1.4.1.25506.2.211.2.1.4)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cIpfwChassis (1.3.6.1.4.1.25506.2.211.2.1.4) |
accessible-for-notify |
Unsigned32 |
Unsigned32(0..2147483647) |
Chassis number. |
As per the MIB. |
hh3cIpfwSlot (1.3.6.1.4.1.25506.2.211.2.1.5)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cIpfwSlot (1.3.6.1.4.1.25506.2.211.2.1.5) |
accessible-for-notify |
Unsigned32 |
Unsigned32(0..2147483647) |
Slot number. |
As per the MIB. |
hh3cIpfwVsysID (1.3.6.1.4.1.25506.2.211.2.1.6)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cIpfwVsysID (1.3.6.1.4.1.25506.2.211.2.1.6) |
accessible-for-notify |
Unsigned32 |
Unsigned32(0..2147483647) |
vSystem ID. |
As per the MIB. |
hh3cIpfwIPv4FragBufSrcAddress (1.3.6.1.4.1.25506.2.211.2.1.7)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cIpfwIPv4FragBufSrcAddress (1.3.6.1.4.1.25506.2.211.2.1.7) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..255) |
Source IPv4 address of the packet that triggered the alarm notification. |
As per the MIB. |
hh3cIpfwIPv4FragBufDstAddress (1.3.6.1.4.1.25506.2.211.2.1.8)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cIpfwIPv4FragBufDstAddress (1.3.6.1.4.1.25506.2.211.2.1.8) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..255) |
Destination IPv4 address of the packet that triggered the alarm notification. |
As per the MIB. |
hh3cIpfwIPv6FragBufSrcAddress (1.3.6.1.4.1.25506.2.211.2.1.9)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cIpfwIPv6FragBufSrcAddress (1.3.6.1.4.1.25506.2.211.2.1.9) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..255) |
Source IPv6 address of the packet that triggered the alarm notification. |
As per the MIB. |
hh3cIpfwIPv6FragBufDstAddress (1.3.6.1.4.1.25506.2.211.2.1.10)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cIpfwIPv6FragBufDstAddress (1.3.6.1.4.1.25506.2.211.2.1.10) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..255) |
Destination IPv6 address of the packet that triggered the alarm notification. |
As per the MIB. |
hh3cIpfwMbufAllocFailedNum (1.3.6.1.4.1.25506.2.211.2.1.11)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cIpfwMbufAllocFailedNum (1.3.6.1.4.1.25506.2.211.2.1.11) |
accessible-for-notify |
Unsigned32 |
Standard MIB values. |
Number of MBUF allocation failures. |
As per the MIB. |
Notifications
hh3cIpfwPktNumExcAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.211.2.0.1 |
Disordered packets detected. |
Error |
Warning |
1.3.6.1.4.1.25506.2.211.2.0.2 (hh3cIpfwPktNumExcAlarmResume) |
ON |
Notification triggers
This notification is generated when the length of the buffered packet queue exceeds the alarm threshold because the device receives a large number of fragments that require reassembly.
System impact
The device received too many fragments, some of which are disordered, and the device cannot complete fragment reassembly in time. This might cause packet loss and affect service operation.
Status control
ON
CLI: Use the snmp-agent trap enable ip-forwarding command.
OFF
CLI: Use the undo snmp-agent trap enable ip-forwarding command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.211.2.1.1 (hh3cIpfwIfIndex) |
Index of the interface from which the packets are received. |
N/A |
InterfaceIndex |
Integer32 (1..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.2 (hh3cIpfwPeerAddress) |
IP address of the interface from which the packets are received. |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
|
1.3.6.1.4.1.25506.2.211.2.1.3 (hh3cIpfwInterfaceName) |
Name of the interface from which the packets are received. |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
Recommended action
Use the IP address and interface information in the alarm message to identify the fragment source and verify if the fragments are valid. If the fragments are invalid, enable anti-attack measures against the source as a best practice to avoid effect on service operation.
hh3cIpfwPktNumExcAlarmResume
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.211.2.0.2 |
Disordered packet alarm removal |
Recovery |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when the threshold exceeding alarm (buffered packet queue length threshold) is removed.
System impact
No negative impact on services.
Status control
ON
CLI: Use the snmp-agent trap enable ip-forwarding command.
OFF
CLI: Use the undo snmp-agent trap enable ip-forwarding command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.211.2.1.1 (hh3cIpfwIfIndex) |
Index of the interface from which the packets are received. |
N/A |
InterfaceIndex |
Integer32 (1..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.2 (hh3cIpfwPeerAddress) |
IP address of the interface from which the packets are received. |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
|
1.3.6.1.4.1.25506.2.211.2.1.3 (hh3cIpfwInterfaceName) |
Name of the interface from which the packets are received. |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
Recommended action
No action is required.
hh3cIpfwIPv4VfrExcAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.211.2.0.3 |
IPv4 VFR buffer limit violation. |
Error |
Warning |
1.3.6.1.4.1.25506.2.211.2.0.4 (hh3cIpfwIPv4VfrExcAlarmResume) |
ON |
Notification triggers
This notification is generated when one of the following items exceeds the limit:
Quantity of the fragments buffered by IPv4 VFR.
Quantity of entries in the IPv4 fragment fast forwarding table.
System impact
Service interruption will occur because the device discards the fragments that IPv4 VFR cannot reassemble.
Status control
ON
CLI: N/A
OFF
CLI: N/A
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.211.2.1.4 (hh3cIpfwChassis) |
Chassis number. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.5 (hh3cIpfwSlot) |
Slot number. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.6 (hh3cIpfwVsysID) |
vSystem ID. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.7 (hh3cIpfwIPv4FragBufSrcAddress) |
Source IPv4 address of the packet that triggered the alarm notification. |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
|
1.3.6.1.4.1.25506.2.211.2.1.8 (hh3cIpfwIPv4FragBufDstAddress) |
Destination IPv4 address of the packet that triggered the alarm notification. |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
Recommended action
To resolve this issue:
1.Identify whether the number of IPv4 fragments in the current system is correct by capturing packets from the system.
2.Repeat the display system internal ip packet-drop statistics command in probe view, and observe the values of the following fields in the command output:
- Fragments in queue for virtual reassembly reach the limit
- Virtual fragment reassembly failed
3.Collect the results of the steps above, and then contact H3C Support.
hh3cIpfwIPv4VfrExcAlarmResume
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.211.2.0.4 |
Recovery from IPv4 VFR buffer limit violation. |
Recovery |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when the device recovers from a condition of IPv4 VFR buffer limit violation.
System impact
No negative impact on the system.
Status control
ON
CLI: N/A
OFF
CLI: N/A
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.211.2.1.4 (hh3cIpfwChassis) |
Chassis number. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.5 (hh3cIpfwSlot) |
Slot number. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.6 (hh3cIpfwVsysID) |
vSystem ID. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
Recommended action
No action is required. Please contact H3C Support.
hh3cIpfwIPv6VfrExcAlarm
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.211.2.0.5 |
IPv6 VFR buffer limit violation. |
Error |
Warning |
1.3.6.1.4.1.25506.2.211.2.0.6 (hh3cIpfwIPv6VfrExcAlarmResume) |
ON |
Notification triggers
This notification is generated when one of the following items exceeds the limit:
Quantity of the fragments buffered by IPv6 VFR.
Quantity of entries in the IPv6 fragment fast forwarding table.
System impact
Service interruption will occur because the device discards the fragments that IPv6 VFR cannot reassemble.
Status control
ON
CLI: N/A
OFF
CLI: N/A
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.211.2.1.4 (hh3cIpfwChassis) |
Chassis number. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.5 (hh3cIpfwSlot) |
Slot number. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.6 (hh3cIpfwVsys) |
vSystem ID. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.9 (hh3cIpfwIPv6FragBufSrcAddress) |
Source IPv6 address of the packet that triggered the alarm notification. |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
|
1.3.6.1.4.1.25506.2.211.2.1.10 (hh3cIpfwIPv6FragBufDstAddress) |
Destination IPv6 address of the packet that triggered the alarm notification. |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
Recommended action
To resolve this issue:
1.Identify whether the number of IPv6 fragments in the current system is correct by capturing packets from the system.
2.Repeat the display system internal ipv6 packet-drop statistics command in probe view, and observe the values of the following fields in the command output:
- Fragments in queue for virtual reassembly reach the limit
- Virtual fragment reassembly failed
3.Collect the results of the steps above, and then contact H3C Support.
hh3cIpfwIPv6VfrExcAlarmResume
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.211.2.0.6 |
Recovery from IPv6 VFR buffer limit violation. |
Recovery |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when the device recovers from a condition of IPv6 VFR buffer limit violation.
System impact
No negative impact on the system.
Status control
ON
CLI: N/A
OFF
CLI: N/A
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.211.2.1.4 (hh3cIpfwChassis) |
Chassis number. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.5 (hh3cIpfwSlot) |
Slot number. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
|
1.3.6.1.4.1.25506.2.211.2.1.6 (hh3cIpfwVsysID) |
vSystem ID. |
N/A |
Unsigned32 |
Integer32 (0..2147483647) |
Recommended action
No action is required. Please contact H3C Support.
hh3cIpfwMbufAllocFailed
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.211.2.0.7 |
MBUF allocation failure |
Error |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated due to memory insufficiency.
System impact
Packet failure occurs, interrupting services.
Status control
ON
CLI: snmp-agent trap enable ip-forwarding
OFF
CLI: undo snmp-agent trap enable ip-forwarding
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.211.2.1.11 (hh3cIpfwMbufAllocFailedNum) |
Number of MBUF allocation failures. |
N/A |
Unsigned32 |
As per the MIB. |
Recommended action
1.Check the device for memory insufficiency.
2.Stop unused services and downsize services with high memory usage.
