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

Port listing on cable connection #13088

Closed
deku-m opened this issue Jul 5, 2023 · 4 comments
Closed

Port listing on cable connection #13088

deku-m opened this issue Jul 5, 2023 · 4 comments
Labels
status: duplicate This issue has already been raised type: bug A confirmed report of unexpected behavior in the application

Comments

@deku-m
Copy link

deku-m commented Jul 5, 2023

NetBox version

v3.5.4

Python version

3.10.6

Steps to Reproduce

Steps:

  • Use device type C9200L-48P-4X from library for example and create a device named ITA-LN-ASW03-1, ITA-LN-ASW03-2
    See screenshots from ITA-LN-ASW03-1, ITA-LN-ASW03-2 no double stackports under their interfaces
    capture-device-0-1
    capture-device-1-1
  • create virtual chassis ITA-LN-ASW03
  • create members under it (ITA-LN-ASW03-1, ITA-LN-ASW03-2)
  • create a stack cable connection from a ITA-LN-ASW03-1 to ITA-LN-ASW03-2 (one member of virtual chassis).
    As seen in screenshot.
  • check the interface and select interface. You can see extra stackports which come from the member devices their interfaces i think.
    Which shouldnt be there as they are physical devices.

As you can see the list has double entries when creating i think a virtual switch. but the physical part is still the same you need to know in the list when you have a device member of the virtual chassis and it is member 2. That you need to select the second stackport1/2 in the list (see example about stackport).

The overview of the list makes it unclear which one to select but the entry will change when selecting the wrong Stackport for example and save it. Then the cable connection values change to the selected one.

See below:
list-ports

Expected Behavior

Some sort of knowhow perhaps so that the list is not unclear or only the interfaces that are from the physical device itself.
Not a mix with the other members.
As it looks like it is using the virtual chassis instead of physical device and interfaces itself.

Observed Behavior

list-ports-1

@deku-m deku-m added the type: bug A confirmed report of unexpected behavior in the application label Jul 5, 2023
@jsenecal
Copy link
Contributor

jsenecal commented Jul 5, 2023

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jsenecal jsenecal added the status: revisions needed This issue requires additional information to be actionable label Jul 5, 2023
@deku-m
Copy link
Author

deku-m commented Jul 5, 2023

I extended the method i used that showed me the "bug"

@DanSheps
Copy link
Member

DanSheps commented Jul 5, 2023

This is captured under #11478 however I would like to point out, your second chassis ports should be 2/1 and 2/2 not 1/1 and 1/2, likewise your third switch stack ports should be 3/1 and 3/2.

@DanSheps
Copy link
Member

DanSheps commented Jul 5, 2023

Duplicate of #11478

@DanSheps DanSheps marked this as a duplicate of #11478 Jul 5, 2023
@DanSheps DanSheps closed this as not planned Won't fix, can't repro, duplicate, stale Jul 5, 2023
@DanSheps DanSheps added status: duplicate This issue has already been raised and removed status: revisions needed This issue requires additional information to be actionable labels Jul 5, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue has already been raised type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

3 participants