starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

LLDP Question #452

New Issue
Closed
opened 2025-12-29 16:22:19 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:22:19 +01:00
Owner
Copy Link

Originally created by @r-2st on GitHub (Sep 28, 2016).

Have a question about getting LLDP to work.

I am putting a multi-slot chassis in Netbox. Specifically a Cisco 9508. Created a device for the chassis with 8 slots and put a mgmt IP on it. After that I created a new device for each line card but did not give them mgmt IP's as they would all have the same one as the chassis. Will Netbox still pull LLDP for the chassis and show the neighbor information for the individual line card interfaces?

Originally created by @r-2st on GitHub (Sep 28, 2016). Have a question about getting LLDP to work. I am putting a multi-slot chassis in Netbox. Specifically a Cisco 9508. Created a device for the chassis with 8 slots and put a mgmt IP on it. After that I created a new device for each line card but did not give them mgmt IP's as they would all have the same one as the chassis. Will Netbox still pull LLDP for the chassis and show the neighbor information for the individual line card interfaces?
adam closed this issue 2025-12-29 16:22:19 +01:00
adam commented 2025-12-29 16:22:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 28, 2016):

I created a new device for each line card

Line cards aren't devices; they don't have their own control plane. You should create a single device to represent the entire switch, and optionally create modules to represent the individual line cards.

I'm going to close this out as it doesn't pertain to the code base, but please feel free to raise the issue on the mailing list.

@jeremystretch commented on GitHub (Sep 28, 2016): > I created a new device for each line card Line cards aren't devices; they don't have their own control plane. You should create a single device to represent the entire switch, and optionally create modules to represent the individual line cards. I'm going to close this out as it doesn't pertain to the code base, but please feel free to raise the issue on the [mailing list](https://groups.google.com/forum/#!forum/netbox-discuss).
adam commented 2025-12-29 16:22:20 +01:00
Author
Owner
Copy Link

@r-2st commented on GitHub (Sep 28, 2016):

Ah! Thank you very much for answering my question. I will move over to the mailing list for future questions.

@r-2st commented on GitHub (Sep 28, 2016): Ah! Thank you very much for answering my question. I will move over to the mailing list for future questions.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#452
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?