- 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-TUNNEL-TRAP-MIB
- 18-HH3C-DNS-MIB
- 19-IP-MIB
- 20-IPV6-ICMP-MIB
- 21-IPV6-MIB
- 22-IPV6-TCP-MIB
- 23-IPV6-UDP-MIB
- 24-TCP-MIB
- 25-UDP-MIB
- Related Documents
-
Title | Size | Download |
---|---|---|
16-HH3C-TCP-MIB | 51.00 KB |
Contents
hh3cTcpConnLocalAddressTCP (1.3.6.1.4.1.25506.2.215.1.1.1)
hh3cTcpConnLocalPortTCP (1.3.6.1.4.1.25506.2.215.1.1.2)
hh3cTcpConnRemAddressTCP (1.3.6.1.4.1.25506.2.215.1.1.3)
hh3cTcpConnRemPortTCP (1.3.6.1.4.1.25506.2.215.1.1.4)
hh3cTcpProtocol (1.3.6.1.4.1.25506.2.215.1.1.5)
hh3cTcpVrfNameVRF (1.3.6.1.4.1.25506.2.215.1.1.6)
HH3C-TCP-MIB
About this MIB
Use this MIB to test whether the MD5 authentication for the current TCP connection is successful.
MIB file name
hh3c-tcp.mib
Root object
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cTcp(215)
Scalar objects
hh3cTcpConnLocalAddressTCP (1.3.6.1.4.1.25506.2.215.1.1.1)
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cTcpConnLocalAddressTCP (1.3.6.1.4.1.25506.2.215.1.1.1) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..255) |
Local IP address of the TCP connection |
As per the MIB. |
hh3cTcpConnLocalPortTCP (1.3.6.1.4.1.25506.2.215.1.1.2)
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cTcpConnLocalPortTCP (1.3.6.1.4.1.25506.2.215.1.1.2) |
accessible-for-notify |
Integer32 |
Integer32(0..65535) |
Local port number of the TCP connection |
As per the MIB. |
hh3cTcpConnRemAddressTCP (1.3.6.1.4.1.25506.2.215.1.1.3)
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cTcpConnRemAddressTCP (1.3.6.1.4.1.25506.2.215.1.1.3) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..255) |
Remote IP address of the TCP connection |
As per the MIB. |
hh3cTcpConnRemPortTCP (1.3.6.1.4.1.25506.2.215.1.1.4)
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cTcpConnRemPortTCP (1.3.6.1.4.1.25506.2.215.1.1.4) |
accessible-for-notify |
Integer32 |
Integer32(0..65535) |
Remote port number of the TCP connection |
As per the MIB. |
hh3cTcpProtocol (1.3.6.1.4.1.25506.2.215.1.1.5)
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cTcpProtocol (1.3.6.1.4.1.25506.2.215.1.1.5) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..255) |
Name of the upper layer protocol of TCP |
As per the MIB. |
hh3cTcpVrfNameVRF (1.3.6.1.4.1.25506.2.215.1.1.6)
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cTcpVrfNameVRF (1.3.6.1.4.1.25506.2.215.1.1.6) |
accessible-for-notify |
OCTET STRING |
OCTET STRING (0..255) |
Name of the VRF of the TCP connection |
As per the MIB. |
Notifications
hh3cTcpMD5AuthenFail
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.215.1.0.1 |
TCP connection MD5 authentication failed. |
Error |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when the MD5 keys of the two ends of a TCP connection are different or only one end is configured with an MD5 key.
System impact
The TCP connection cannot be established, upper-layer routing protocols, such as LDP and BGP, cannot establish sessions.
Status control
ON
CLI: Use the snmp-agent trap enable tcp command.
OFF
CLI: Use the undo snmp-agent trap enable tcp command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.4.1.25506.2.215.1.1.1 (hh3cTcpConnLocalAddressTCP) |
Local IP address of the TCP connection |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
1.3.6.1.4.1.25506.2.215.1.1.2 (hh3cTcpConnLocalPortTCP) |
Local port number of the TCP connection |
N/A |
Integer32 |
Integer32(0..65535) |
1.3.6.1.4.1.25506.2.215.1.1.3 (hh3cTcpConnRemAddressTCP) |
Remote IP address of the TCP connection |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
1.3.6.1.4.1.25506.2.215.1.1.4 (hh3cTcpConnRemPortTCP) |
Remote port number of the TCP connection |
N/A |
Integer32 |
Integer32(0..65535) |
1.3.6.1.4.1.25506.2.215.1.1.5 (hh3cTcpProtocol) |
Name of the upper layer protocol of TCP |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
1.3.6.1.4.1.25506.2.215.1.1.6 (hh3cTcpVrfNameVRF) |
Name of the VRF of the TCP connection |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
Recommended action
To resolve this issue:
1.Use the display current-configuration command on each end to check whether an MD5 key is configured.
- If only one end is configured with an MD5 key, configure an MD5 key on the other end. If the issue persists, go to step 3.
- If the MD5 keys configured on the two ends are different, go to step 2.
2.Configure the same MD5 key on the two ends.
3.Collect alarm information and configuration data, and then contact H3C Support for help.