question

nvn1202 avatar image
nvn1202 asked

Spirent not allowing BGP session to come up with our DUT

Hi,

Here is the topology.

[DUT] --------------------------[Spirent]

DUT is configured with Multiprotocol BGP with capability to carry IPv6 over a IPv4 BGP session. On the Spirent side, it's just IPv4 BGP.


As per the RFC, even though there is a capability mismatch between DUT and Spirent, BGP session should have come up with ability to exchange IPv4 prefixes. However, we have found that Spirent is terminating the session by sending NOTIFICATION packet with error code as Mismatching capability.

slx_spirent.pcap


I have attached the packet capture between DUT and Spirent.

Are we missing something? Any explanation on Spirent behavior will be appreciated.


Thanks

Navin



bgpipv6overipv4dual-stackbgp sessionmulti protocol bgp
slx-spirent.pcap (14.1 KiB)
10 |950
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

0 Answers

·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.