- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Re: BGP4-MIB partial output on HPE 5510/5940/10508...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2017 03:53 PM - edited 09-29-2017 04:13 PM
09-29-2017 03:53 PM - edited 09-29-2017 04:13 PM
Good day, experts!
Recently faced strange problem with our 5510/5940/10508 boxes - BGP4-MIB shows partial output. When i made snmpwalk over this MIB, switches show me their BGP Version (oid 1.3.6.1.2.1.15.1), ASN (oid 1.3.6.1.2.1.15.2) and RID (oid 1.3.6.1.2.1.15.4) only. No other information at all. No peers, no peer states, no prefixes, etc...
We are using INTER-AS options A and B on this devices, so my question: how can we obtain detailed information about BGP sessions via SNMP?
Thanks in advance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2017 02:16 AM - edited 10-02-2017 02:17 AM
10-02-2017 02:16 AM - edited 10-02-2017 02:17 AM
Re: BGP4-MIB partial output on HPE 5510/5940/10508 (Comware 7)
MIB OIDs .1.3.6.1.2.1.15 related (as of latest MIB V9 for Comware here) can be easily found, as example:
.1.3.6.1.2.1.15 bgp MODULE-IDENTITY -- FROM BGP4-MIB DESCRIPTION "The MIB module for the BGP-4 protocol. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4273; see the RFC itself for full legal notices." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) 15 } .1.3.6.1.2.1.15.0 bgpNotification OBJECT-TYPE -- FROM BGP4-MIB ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) 0 } .1.3.6.1.2.1.15.0.1 bgpEstablishedNotification NOTIFICATION-TYPE -- FROM BGP4-MIB OBJECTS { bgpPeerRemoteAddr, bgpPeerLastError, bgpPeerState } DESCRIPTION "The bgpEstablishedNotification event is generated when the BGP FSM enters the established state. This Notification replaces the bgpEstablished Notification." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpNotification(0) 1 } .1.3.6.1.2.1.15.0.2 bgpBackwardTransNotification NOTIFICATION-TYPE -- FROM BGP4-MIB OBJECTS { bgpPeerRemoteAddr, bgpPeerLastError, bgpPeerState } DESCRIPTION "The bgpBackwardTransNotification event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state. This Notification replaces the bgpBackwardsTransition Notification." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpNotification(0) 2 } .1.3.6.1.2.1.15.1 bgpVersion OBJECT-TYPE -- FROM BGP4-MIB SYNTAX OCTET STRING (1..255) MAX-ACCESS read-only STATUS current DESCRIPTION "Vector of supported BGP protocol version numbers. Each peer negotiates the version from this vector. Versions are identified via the string of bits contained within this object. The first octet contains bits 0 to 7, the second octet contains bits 8 to 15, and so on, with the most significant bit referring to the lowest bit number in the octet (e.g., the MSB of the first octet refers to bit 0). If a bit, i, is present and set, then the version (i+1) of the BGP is supported." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) 1 } .1.3.6.1.2.1.15.2 bgpLocalAs OBJECT-TYPE -- FROM BGP4-MIB SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The local autonomous system number." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) 2 } .1.3.6.1.2.1.15.3 bgpPeerTable OBJECT-TYPE -- FROM BGP4-MIB MAX-ACCESS not-accessible STATUS current DESCRIPTION "BGP peer table. This table contains, one entry per BGP peer, information about the connections with BGP peers." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) 3 } .1.3.6.1.2.1.15.3.1 bgpPeerEntry OBJECT-TYPE -- FROM BGP4-MIB MAX-ACCESS not-accessible STATUS current INDEX { bgpPeerRemoteAddr } DESCRIPTION "Entry containing information about the connection with a BGP peer." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) 1 } .1.3.6.1.2.1.15.3.1.1 bgpPeerIdentifier OBJECT-TYPE -- FROM BGP4-MIB SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The BGP Identifier of this entry's BGP peer. This entry MUST be 0.0.0.0 unless the bgpPeerState is in the openconfirm or the established state." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 1 } .1.3.6.1.2.1.15.3.1.2 bgpPeerState OBJECT-TYPE -- FROM BGP4-MIB SYNTAX INTEGER {idle(1), connect(2), active(3), opensent(4), openconfirm(5), established(6)} MAX-ACCESS read-only STATUS current DESCRIPTION "The BGP peer connection state." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 2 } .1.3.6.1.2.1.15.3.1.3 bgpPeerAdminStatus OBJECT-TYPE -- FROM BGP4-MIB SYNTAX INTEGER {stop(1), start(2)} MAX-ACCESS read-write STATUS current DESCRIPTION "The desired state of the BGP connection. A transition from 'stop' to 'start' will cause the BGP Manual Start Event to be generated. A transition from 'start' to 'stop' will cause the BGP Manual Stop Event to be generated. This parameter can be used to restart BGP peer connections. Care should be used in providing write access to this object without adequate authentication." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 3 } .1.3.6.1.2.1.15.3.1.4 bgpPeerNegotiatedVersion OBJECT-TYPE -- FROM BGP4-MIB SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The negotiated version of BGP running between the two peers. This entry MUST be zero (0) unless the bgpPeerState is in the openconfirm or the established state. Note that legal values for this object are between 0 and 255." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 4 } .1.3.6.1.2.1.15.3.1.5 bgpPeerLocalAddr OBJECT-TYPE -- FROM BGP4-MIB SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The local IP address of this entry's BGP connection." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 5 } .1.3.6.1.2.1.15.3.1.6 bgpPeerLocalPort OBJECT-TYPE -- FROM BGP4-MIB SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The local port for the TCP connection between the BGP peers." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 6 } .1.3.6.1.2.1.15.3.1.7 bgpPeerRemoteAddr OBJECT-TYPE -- FROM BGP4-MIB SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The remote IP address of this entry's BGP peer." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 7 } .1.3.6.1.2.1.15.3.1.8 bgpPeerRemotePort OBJECT-TYPE -- FROM BGP4-MIB SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The remote port for the TCP connection between the BGP peers. Note that the objects bgpPeerLocalAddr, bgpPeerLocalPort, bgpPeerRemoteAddr, and bgpPeerRemotePort provide the appropriate reference to the standard MIB TCP connection table." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 8 } .1.3.6.1.2.1.15.3.1.9 bgpPeerRemoteAs OBJECT-TYPE -- FROM BGP4-MIB SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The remote autonomous system number received in the BGP OPEN message." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 9 } .1.3.6.1.2.1.15.3.1.10 bgpPeerInUpdates OBJECT-TYPE -- FROM BGP4-MIB SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of BGP UPDATE messages received on this connection." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 10 } .1.3.6.1.2.1.15.3.1.11 bgpPeerOutUpdates OBJECT-TYPE -- FROM BGP4-MIB SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of BGP UPDATE messages transmitted on this connection." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 11 } .1.3.6.1.2.1.15.3.1.12 bgpPeerInTotalMessages OBJECT-TYPE -- FROM BGP4-MIB SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of messages received from the remote peer on this connection." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 12 } .1.3.6.1.2.1.15.3.1.13 bgpPeerOutTotalMessages OBJECT-TYPE -- FROM BGP4-MIB SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of messages transmitted to the remote peer on this connection." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 13 } .1.3.6.1.2.1.15.3.1.14 bgpPeerLastError OBJECT-TYPE -- FROM BGP4-MIB SYNTAX OCTET STRING (2) MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpPeerTable(3) bgpPeerEntry(1) 14 }
...
...
...
.1.3.6.1.2.1.15.7.2
bgpBackwardTransition NOTIFICATION-TYPE
-- FROM BGP4-MIB
OBJECTS { bgpPeerLastError, bgpPeerState }
DESCRIPTION "The BGPBackwardTransition Event is generated
when the BGP FSM moves from a higher numbered
state to a lower numbered state."
::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) bgp(15) bgpTraps(7) 2 }
The list above isn't complete since I can't post a text longer than 25k characters.
I'm not an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2017 04:23 AM - edited 10-02-2017 04:36 AM
10-02-2017 04:23 AM - edited 10-02-2017 04:36 AM
Re: BGP4-MIB partial output on HPE 5510/5940/10508 (Comware 7)
Thanks for the answer, but this is not an MIB-FILE issue (IMHO).
I'm doing an snmpwalk on the entire subtree .1.3.6.1.2.1.15 with same results - getting only Version, ASN & RID:
As you can see, the rest of the BGP-related information is missing.
May be there are some configuration missing on my switches, that enable this kind of information visible through SNMP?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-03-2017 11:04 PM
10-03-2017 11:04 PM
Re: BGP4-MIB partial output on HPE 5510/5940/10508 (Comware 7)
Does anyone configured BGP on HPE 10508, 5940 or 5510?
If yes, is it possible to retrieve information about BGP peers (bgpPeerState, bgpPeerLocalAddr, bgpPeerRemoteAddr, etc.) via SNMP from this switches?
Thanks in advance for any help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2017 11:24 PM - edited 10-23-2017 11:25 PM
10-23-2017 11:24 PM - edited 10-23-2017 11:25 PM
SolutionFinally got desired information from L3 & L4 HPE engineers:
That is correct: only those three OIDs are supported.
But soon, new code: 2609 will support the following:
∙ hh3cMplsVpnVrfBgpNbrAddrTable
∙ hh3cMplsVpnVrfBgpNbrPrefixTable
This code is expected to be available sometime in November.
So the product is working as designed.
So at the moment this is known product limitation. Awaiting new releases to fix it...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2019 10:53 PM
05-16-2019 10:53 PM
Re: BGP4-MIB partial output on HPE 5510/5940/10508 (Comware 7)
Do you also get VRF peers?
Regarda
Christian