Invalid BGP peer state via SNMP

[AdamBogdan26228]

Hi

I have a strange issue with reading BGP peer state status via SNMP.
On the router (ASR1001-X, 17.6.3a) I have over 150 bgp sessions - all of them are established.
When I use OID .1.3.6.1.2.1.15.3.1.2.<peer_ip> I get almost 120 results with "1" - which means "Idle"
rest of the outputs (a bit over 30) have correct value "6" (established) 
All BGP sessions are configured in the same way.
Is there any special config or something to receive correct status via SNMP - it's especially annoying in monitoring system.

Thanks in advance

[balaji.bandi]

Can you post the output of snmp walk and BGP output :

i know you may have this information - just for reference :

1 = IDLE
2 = CONNECT
3 = ACTIVE
4 = OPENSENT
5 = OPENCONFIRM
6 = ESTABLISHED

[AdamBogdan26228]

Here is the output - the neighbors are in vpnv4 AF so the output is from "sh ip bgp vpnv4 all summary" command

*172.x.y.18 4 <AS> 2078760 4161827 22442 0 0 7w0d 2
*172.x.y.34 4 <AS> 2090681 4186169 22442 0 0 7w0d 2
*172.x.y.50 4 <AS> 2090797 4186783 22442 0 0 7w0d 4
*172.x.y.66 4 <AS> 231287 463530 22442 0 0 5d11h 2
*172.x.y.74 4 <AS> 1356673 27160x 22442 0 0 4w4d 2
*172.x.y.98 4 <AS> 2090706 4186240 22442 0 0 7w0d 2
*172.x.y.106 4 <AS> 259854 520704 22442 0 0 6d03h 2
*172.x.y.114 4 <AS> 2090729 4186354 22442 0 0 7w0d 4
*172.x.y.122 4 <AS> 437859 877266 22442 0 0 1w3d 4
*172.x.y.146 4 <AS> 2090833 4188609 22442 0 0 7w0d 2

.1.3.6.1.2.1.15.3.1.2.172.x.y.18 = INTEGER: 1
.1.3.6.1.2.1.15.3.1.2.172.x.y.34 = INTEGER: 1
.1.3.6.1.2.1.15.3.1.2.172.x.y.50 = INTEGER: 1
.1.3.6.1.2.1.15.3.1.2.172.x.y.66 = INTEGER: 1
.1.3.6.1.2.1.15.3.1.2.172.x.y.74 = INTEGER: 1
.1.3.6.1.2.1.15.3.1.2.172.x.y.98 = INTEGER: 1
.1.3.6.1.2.1.15.3.1.2.172.x.y.106 = INTEGER: 1
.1.3.6.1.2.1.15.3.1.2.172.x.y.114 = INTEGER: 1
.1.3.6.1.2.1.15.3.1.2.172.x.y.122 = INTEGER: 1
.1.3.6.1.2.1.15.3.1.2.172.x.y.146 = INTEGER: 1

But like I wrote - for some neighbors it's working 

*172.x.y.66 4 <AS> 2091081 4193952 22442 0 0 7w0d 12
*172.x.y.74 4 <AS> 2091050 4192250 22442 0 0 7w0d 9
*172.x.y.90 4 <AS> 2069829 4143843 22442 0 0 7w0d 12
*172.x.y.98 4 <AS> 2091055 4192387 22442 0 0 7w0d 12

.1.3.6.1.2.1.15.3.1.2.172.x.y.66 = INTEGER: 6
.1.3.6.1.2.1.15.3.1.2.172.x.y.74 = INTEGER: 6
.1.3.6.1.2.1.15.3.1.2.172.x.y.90 = INTEGER: 6
.1.3.6.1.2.1.15.3.1.2.172.x.y.98 = INTEGER: 6

[MHM Cisco World]

I think your SNMP is right 
to check 
show ip bgp neighbor summary <<- this give you how many session is idle, then you can compare result with what you get from SNMP.

[AdamBogdan26228]

Hi

I'm using "sh ip bgp vpnv4 all summary" to check peers status and all of them are up - I don't have anything in Idle/Active state

Router#sh ip bgp vpnv4 all summary | i Active|Idle
Router# 

[MHM Cisco World]

neighbor not vpnv4.

we talking about session not table version 

[AdamBogdan26228]

all sessions are up - even if I will check with full neighbors output and searching for "BGP state" - established state everywhere
I don't understand why snmp is returning wrong state

[Georg Pauwen]

Hello,

which monitoring system are you using ?

[AdamBogdan26228]

Hi

I think this is irrelevant in this case but I'm using logicmonitor - monitoring system is using the same OID's which I used in snmpwalk