Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Peering to Virtual Device does not allow BGP peering to secondary members #232

Open
kingfetty opened this issue Dec 5, 2024 · 2 comments
Labels
type: bug Something isn't working as expected

Comments

@kingfetty
Copy link

Environment

  • Python version: 3.11
  • Nautobot version: 2.3.12
  • nautobot-bgp-models version: 2.2.0

Expected Behavior

Should be able to create a peering to any IP assigned to any member of the Virtual Device's interfaces

Observed Behavior

Unable to peer to an address assigned to an interface on a non-primary member of the virtual device despite the BGP routing instance in the real world being managed by the primary member of the virtual device.

Steps to Reproduce

  1. Create a virtual device consisting of more than 1 member.
  2. Assign an IP address to an interface owned by the non-primary member.
  3. Create a routing instance for the primary member of the virtual device
  4. Attempt to create a peering to the IP address assigned to the interface of the non-primary member
  5. Exception 'Peer IP not associated with Routing Instance' is thrown as the app does not account for virtual devices
@gsnider2195 gsnider2195 added the type: bug Something isn't working as expected label Dec 6, 2024
@mzbroch
Copy link
Contributor

mzbroch commented Dec 16, 2024

I assume You are referring to "VirtualChassis" model and a situation where a BGPRoutingInstance exists for member 1, but a peering is created for a member 2 of VC ?

@kingfetty
Copy link
Author

That is the situation sir.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working as expected
Projects
None yet
Development

No branches or pull requests

3 participants