08-Layer 3 - IP Services

HomeSupportRoutersCR16000-M SeriesReference GuidesMIB CompanionH3C CR16000-M Routers MIB Reference-R838x-6W10008-Layer 3 - IP Services
16-HH3C-TCP-MIB
Title Size Download
16-HH3C-TCP-MIB 51.00 KB

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.

 

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Intelligent Storage
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
  • Technical Blogs
All Support
  • Become A Partner
  • Partner Policy & Program
  • Global Learning
  • Partner Sales Resources
  • Partner Business Management
  • Service Business
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网