Hi,
On 31/03/2026 11:50, [email protected] wrote:
Hi Chongfeng,
Thanks for your comments.
Although the controller knows the configurations on each PE, e.g.,
flows received from port 1 are directed to VPN instance 2 on PE2,
flows with DA1 are sent to PE3, if there's no VPN SID/next hop
information, the controller requires different information(e.g., the
receiving port or the DA of the payload) and different rules to obtain
the target PE information of each traffic flow, according to different
VPN configuration policies.
So it is more straightforward and generic to simply looking at the
SRv6 VPN SID in the packet.
I would add to Yao's answer that the controller knows the intent and
sets the control plane accordingly.
What is key is to double-check that the data plane follows accordingly.
The data plane/control plane discrepancies are a pretty good starting
for troubleshooting.
Regards, Benoit (as a contributor)
Best Regards,
Yao
Original
*From: *ChongfengXie <[email protected]>
*To: *刘尧00165286;opsawg <[email protected]>;
*Date: *2026年03月18日 15:57
*Subject: **Export of BGP VPN Information in IPFIX*
Hi Yao,
You mentioned in your presentation that this draft intend to deal with
the following case,
"When monitoring traffic flows on the ingress PE in a network with BGP
VPN deployed, we want to know: Which egress PE is the flow forwarded to?
In the context of SRv6-based VPN, a VPN instance can be configured by
network controller, I'd like to know such information can be collected
from network controller, instead of being reported from network device
via IPFix?
Best regards
Chongfeng
_______________________________________________
OPSAWG mailing list [email protected]
To unsubscribe send an email [email protected]
_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]
