I have SXP domain customer1 with mapping for ip 22.214.171.124.
And i can not add static mapping for the same ip for different SXP domain:
I would call it a bug - not a feature (since we have VPN domains for SXP for such a separation - right ?).
Could you please confirm ?
Do we have the same problem for dynamic mappings ? (received from network devices which belong to different SXP domains)
Solved! Go to Solution.
I won't take this as a implicit feature as you mention. Unless the specific use case is tested & validated (& documented) it can't be declared as supported. Since I don't see it documented, I would say it is not supported.
Please feel free to reach out to the Segmentation PM team to further the discussion.
Agreed, this is all allowed on the switch infrastructure, it's just an ISE implementation anomaly.
You can of course just edit the one mapping entry in ISE and enter more SXP domain destinations.
A fix for individual entries needs to be tracked under CSCuz00603 (multiple exceptions in log with unified ip-sgt functional).
I don't see any reference where we claim overlapping IP support in ISE SXP. The only reference I could find is in VRF aware SXP in IOS.
Thanks for the help.
VRF for SXP is nice - but a bit different.
We do not mention explicitly that we do support overlapping IPs - but that might be the perception - because of support for multiple SXP VPN domains (and domain filters).
Why do we support SXP VPN domains + filters if those are not really separated/independent ?