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

Increase maximum value for VC position on the Device model #9501

New Issue
Closed
opened 2025-12-29 20:50:43 +01:00 by adam · 0 comments
adam commented 2025-12-29 20:50:43 +01:00
Owner
Copy Link

Originally created by @sleepinggenius2 on GitHub (Apr 18, 2024).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.7.5

Feature type

Change to existing functionality

Proposed functionality

The VC position on the Device model is currently limited to 255. My proposal would be to increase this to at least 65534, but it may need to be higher in other environments.

Use case

I recently ran into an issue within our network due to the 255 limit on VC position. Cisco ASR9K devices allow specifying a satellite ID up to 65534, which seems like the exact use case for the VC model, a master chassis and a subtended one, but that means we want to set position 0 for the main router and use the satellite's ID for it's position in the VC, as that is used in provisioning and in its port naming. I was able to change the maximum value in the model within our NetBox instance and it didn't seem to cause any issues for a value < 32767, but 65534 would overflow a small int, as the type is currently configured, due to its signed nature.

Example from the router configuration:

#nv satellite ?
  <100-65534>  Satellite ID

Database changes

The vc_position field on the Device model would need to be changed from a smallint to an integer type to support a value of 65534.

External dependencies

None

Originally created by @sleepinggenius2 on GitHub (Apr 18, 2024). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.7.5 ### Feature type Change to existing functionality ### Proposed functionality The VC position on the Device model is currently limited to 255. My proposal would be to increase this to at least 65534, but it may need to be higher in other environments. ### Use case I recently ran into an issue within our network due to the 255 limit on VC position. Cisco ASR9K devices allow specifying a satellite ID up to 65534, which seems like the exact use case for the VC model, a master chassis and a subtended one, but that means we want to set position 0 for the main router and use the satellite's ID for it's position in the VC, as that is used in provisioning and in its port naming. I was able to change the maximum value in the model within our NetBox instance and it didn't seem to cause any issues for a value < 32767, but 65534 would overflow a small int, as the type is currently configured, due to its signed nature. Example from the router configuration: ``` #nv satellite ? <100-65534> Satellite ID ``` ### Database changes The `vc_position` field on the Device model would need to be changed from a *smallint* to an *integer* type to support a value of 65534. ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 20:50:43 +01:00
adam closed this issue 2025-12-29 20:50:43 +01:00
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 status: accepted type: feature
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#9501
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?