Hi Jim,
> I was a bit confused about the "L3VPN Instance Peer". What does it
> mean to set the Peer Distinguisher to the Route Distinguisher of the
> L3VPN instance that the peer belongs to?
EBGP session you are monitoring will belong to either global table or
some VRF on a given PE. Adding RD makes it easier to find out which VRF
given routes belong. If the session is to the global table the field
will be zero.
> Are you assuming that the RD is different for every instantiation of
> the VPN on each PE? It is possible that the same RD is used across all
> PEs that a VPN belongs to.
There is no need to make such assumption. The addition of the RD should
be used at the management station along with Peer BGP ID which would
then used in tuple identify PE/VRF for a given session. Peer BGP ID is
already part of BMP header.
Cheers,
R.
"o Peer Distinguisher (8 bytes): Routers today can have multiple
instances (example L3VPNs). This field is present to distinguish
peers that belong to one address domain from the other.
If the peer is a "Global Instance Peer", this field is zero
filled. If the peer is a "L3VPN Instance Peer", it is set to the
route distinguisher of the particular L3VPN instance that the peer
belongs to."
I was a bit confused about the "L3VPN Instance Peer". What does it mean
to set the Peer Distinguisher to the Route Distinguisher of the L3VPN
instance that the peer belongs to? Are you assuming that the RD is
different for every instantiation of the VPN on each PE? It is possible
that the same RD is used across all PEs that a VPN belongs to.
Jim Uttaro
------------------------------------------------------------------------
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
