On 20/11/2008, at 5:16 AM, Stephen Stuart wrote:
This should probably not be a common case, but we do see it from
time to
time. It would be useful for us to be able to have this data.
Data regarding the state of configured peers are already available by
other means (the BGP 4 MIB described in RFC1657); correlating with
that data tells us that a peer has supplied no updates
(BGP4-MIB::bgpPeerInUpdates.A.B.C.D). If the update count is non-zero
and there are still no BMP messages indicating that the peer supplied
a prefix, then it's likely attributable to "state changes in the
interim" for that prefix.
having access to a feed of BGP data for research purposes and SNMP
access to the bgp speaker's MIB are invariably two entirely different
concepts, unfortunately, so while it may be in the MIB that does not
mean that a BMP client has a prayer of ever access that mib!
So, yes, it would be useful to have this data inband within the BMP
feed.
Geoff
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
