Hi,
Problem is as stated in the topic. I have two ipv6 BGP sessions on JunOS with the same source ID.
Router Config:
neighbor 2001:7f8:1::a500:6777:1 {
description "ams-ix routeserver 1";
family inet6 {
unicast {
prefix-limit {
maximum 25000;
teardown idle-timeout 30;
}
}
}
peer-as 6777;
}
neighbor 2001:7f8:1::a500:6777:2 {
description "ams-ix routeserver 2";
family inet6 {
unicast {
prefix-limit {
maximum 25000;
teardown idle-timeout 30;
}
}
}
peer-as 6777;
}
Sessions are up and receiving prefixes:
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped
2001:7f8:1::a500:6777:1 6777 37897057 604765 0 21 28w6d 1:48:17 Establ
inet6.0: 4320/12762/12717/16
2001:7f8:1::a500:6777:2 6777 3266190 44788 0 27 2w0d 22:48:30 Establ
inet6.0: 856/12728/12688/11
LibreNMS BGP session overview:
2001:7f8:1::a503:4756:1
r1.ams.am5 » 2001:7f8:1::a500:6777:1 eBGP AS6777
AMS-IX-RS, NL running
established 5 days, 20h 24m 22s
Updates 1.240M 105.000
2001:7f8:1::a503:4756:1
r1.ams.am5 » 2001:7f8:1::a500:6777:2 eBGP ipv6.unicast AS6777
AMS-IX-RS, NL running
established 14 days, 22h 43m 53s
Updates 3.220M 273.000
Poller/Discovery output:
(looks like the same identifier is being used for the sessions, so it gets overwritten by the last entry during the table/sql/rrd update)
jnxBgpM2PeerIndex.0.ipv6."...........GV... ...........gw.." = 141 <- Not working
jnxBgpM2PeerIndex.0.ipv6."...........GV... ...........gw.." = 142 <- Working
[0.ipv6............GV... ...........gw..] => Array
(
[jnxBgpM2PeerIdentifier] => 80.249.209.0
[jnxBgpM2PeerState] => established
[jnxBgpM2PeerStatus] => running
[jnxBgpM2PeerConfiguredVersion] => 4
[jnxBgpM2PeerNegotiatedVersion] => 0
[jnxBgpM2PeerLocalAddrType] => ipv6
[jnxBgpM2PeerLocalAddr] => 20 01 07 F8 00 01 00 00 00 00 A5 03 47 56 00 01
[jnxBgpM2PeerLocalPort] => 63161
[jnxBgpM2PeerLocalAs] => 34756
[jnxBgpM2PeerRemoteAddrType] => ipv6
[jnxBgpM2PeerRemoteAddr] => 20 01 07 F8 00 01 00 00 00 00 A5 00 67 77 00 02
[jnxBgpM2PeerRemotePort] => 179
[jnxBgpM2PeerRemoteAs] => 6777
[jnxBgpM2PeerIndex] => 142
[jnxBgpM2PeerRoutingInstance] => 0
)
This leads to an empty AFI in the overview page and consequently the values are not exported to InfluxDB either.