No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

MIB Reference

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document provides the function overview, relationships between tables, description of single objects, description of MIB tables, and description of alarm objects.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
hwBgpPeerTable

hwBgpPeerTable

This table contains information about the connections for BGP peers.

The index of this table is none.

OID

Object Name

Syntax

Max Access

Description

Implemented Specifications

1.3.6.1.4.1.2011.5.25.177.1.1.2.1.1

hwBgpPeerNegotiatedVersion

Unsigned32

Read-only

The version negotiated with the remote BGP peer.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.177.1.1.2.1.2

hwBgpPeerRemoteAs

Unsigned32

Read-only

The AS number of the remote BGP peer.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.177.1.1.2.1.4

hwBgpPeerRemoteAddr

InetAddress

Read-only

The IP address of the remote BGP peer.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.177.1.1.2.1.5

hwBgpPeerState

INTEGER { idle(1), connect(2), active(3), opensent(4), openconfirm(5), established(6) }

Read-only

The status of the remote BGP peer:

  • 1: Idle(1)

  • 2: Connect(2)

  • 3: Active(3)

  • 4: Opensent(4)

  • 5: Openconfirm(5)

  • 6: Established(6)

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.177.1.1.2.1.6

hwBgpPeerFsmEstablishedCounter

Unsigned32

Read-write

The counter that records the times the remote BGP peer is correctly connected.

The counter is increased by one if the remote BGP peer is correctly connected once.

The counter could be set to zero.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.177.1.1.2.1.7

hwBgpPeerFsmEstablishedTime

Gauge32

Read-only

The counter that records the times the remote BGP peer is correctly connected.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.177.1.1.2.1.8

hwBgpPeerGRStatus

INTEGER{ peerNotBeingHelped(1), peerRestarting(2), peerFinishRestart(3), peerHelping(4)}

accessible-for-notify

The graceful restart status of the BGP peer, including:
  • 1: peerNotBeingHelped, indicating that the BGP peer will not be helped during restarting.
  • 2: peerRestarting, indicating that the BGP peer is detected restarting.
  • 3: peerFinishRestart, indicating that the BGP peer finishes the latest GR.
  • 4: peerHelping, indicating that the BGP peer is helping the local end to perform GR.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.177.1.1.2.1.9

hwBgpPeerLastError

OctetString

read-only

The last error code and subcode seen by this peer on this connection.
  • If no error has occurred, this field is zero.
  • Otherwise, the first byte of this two byte OCTET STRING contains the error code, and the second byte contains the subcode.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.177.1.1.2.1.10

hwBgpPeerUnAvaiReason

Unsigned32

read-only

The BGP peer down reason, including:
  1. Configuration lead peer down: The configuration causes the peer disconnection.

  2. Receive notification: Notification packets are received.

  3. Receive error packet: Error packets are received.

  4. Hold timer expire: The Hold timer expires.

  5. Remote peer not reachable: The remote peer is unreachable.

  6. Direct connect-interface down: The directly connected interface is Down.

  7. Route limit: The number of routes exceeds the upper limit.

This object is implemented as defined in the corresponding MIB files.

Creation Restriction

The entries in this table cannot be created.

Modification Restriction

The hwbgpPeerFsmEstablishedCounter can only set the count to 0.

Deletion Restriction

The entries in this table cannot be deleted.

Access Restriction

By default, only the BGP peers in the IPv4 public network are read.

Translation
Download
Updated: 2019-06-05

Document ID: EDOC1000097213

Views: 100583

Downloads: 654

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next