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

Interface ordering Arista EOS #2879

New Issue
Closed
opened 2025-12-29 18:23:01 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:23:01 +01:00
Owner
Copy Link

Originally created by @maartenbollen on GitHub (Sep 16, 2019).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.5.12

Ordering of interfaces for Arista devices is not working as intended. Interface naming looks like it's based as newest first. Naming scheme is: "EthernetX" when interfaces are 100/1000/10000 mbit, and "EthernetX/Y" when using 25/40/100G interfaces.

In the DCIM overview I can see:
Ethernet53/1
Ethernet53/2
Ethernet53/3
Ethernet53/4
Ethernet1
Ethernet2
Loopback0

Proposed Functionality

Sorting to be:
Ethernet1
Ethernet2
Ethernet53/1
Ethernet53/2
Ethernet53/3
Ethernet53/4
Loopback0

Originally created by @maartenbollen on GitHub (Sep 16, 2019). ### Environment * Python version: 3.6.8 * NetBox version: 2.5.12 Ordering of interfaces for Arista devices is not working as intended. Interface naming looks like it's based as newest first. Naming scheme is: "EthernetX" when interfaces are 100/1000/10000 mbit, and "EthernetX/Y" when using 25/40/100G interfaces. In the DCIM overview I can see: Ethernet53/1 Ethernet53/2 Ethernet53/3 Ethernet53/4 Ethernet1 Ethernet2 Loopback0 ### Proposed Functionality Sorting to be: Ethernet1 Ethernet2 Ethernet53/1 Ethernet53/2 Ethernet53/3 Ethernet53/4 Loopback0
adam closed this issue 2025-12-29 18:23:01 +01:00
adam commented 2025-12-29 18:23:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 16, 2019):

NetBox version: 2.5.12

The current stable release is v2.6.3. Please ask to re-open this if you're able to replicate the issue on v2.6.3.

@jeremystretch commented on GitHub (Sep 16, 2019): > NetBox version: 2.5.12 The current stable release is v2.6.3. Please ask to re-open this if you're able to replicate the issue on v2.6.3.
adam commented 2025-12-29 18:23:01 +01:00
Author
Owner
Copy Link

@maartenbollen commented on GitHub (Sep 16, 2019):

Please reopen. Problem persists after upgrading to v2.6.3

Sent from my iPhone

On 16 Sep 2019, at 16:37, Jeremy Stretch notifications@github.com wrote:

NetBox version: 2.5.12

The current stable release is v2.6.3. Please ask to re-open this if you're able to replicate the issue on v2.6.3.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@maartenbollen commented on GitHub (Sep 16, 2019): Please reopen. Problem persists after upgrading to v2.6.3 Sent from my iPhone > On 16 Sep 2019, at 16:37, Jeremy Stretch <notifications@github.com> wrote: > > NetBox version: 2.5.12 > > The current stable release is v2.6.3. Please ask to re-open this if you're able to replicate the issue on v2.6.3. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread.
adam commented 2025-12-29 18:23:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 18, 2019):

Per the natural ordering tests, this is intended behavior. Interfaces with a single trailing numeric ID as ordered after those following a slot/port scheme. This is to ensure that interfaces like Loopback0 come after Ethernet1/1. Unfortunately, it is not feasible to accommodate every quirk of every platform, at least not with the current approach to natural ordering.

@jeremystretch commented on GitHub (Sep 18, 2019): Per the [natural ordering tests](https://github.com/netbox-community/netbox/blob/develop/netbox/dcim/tests/test_natural_ordering.py), this is intended behavior. Interfaces with a single trailing numeric ID as ordered after those following a slot/port scheme. This is to ensure that interfaces like `Loopback0` come after `Ethernet1/1`. Unfortunately, it is not feasible to accommodate every quirk of every platform, at least not with the current approach to natural ordering.
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#2879
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?