08-17-2025 04:34 AM
Hello, can someone help me out please.
I like to use my new switch like to get rid of the interface naming convention that it has default, I think due to stack settings:
To configure a 1G ethernet switch port I have to do now:
conf t
tester(config)#int GE1/0/1
But i do not use a stack configuration
did already tried:
conf t
no stack configuration <cr>
restarted the switch but still the same behavior.
I liked to know, can this behavior changed so that I can use my old Cisco 350 syntax ? see example below:
Conf t
int GE1
Many thanks in advance !
Solved! Go to Solution.
08-17-2025 04:39 AM
gDay christian.sonnemans@xs4all.nl Alright so, that interface naming is normal on the newer Catalyst platforms, it isn’t from stacking, it’s just how IOS XE labels ports now. gig1/0/1 - the first number refers to slot/module/port. Meaning even if u don’t have a stack or multiple modules, the syntax is fixed. ALso, on older SG/300/350 SMB switches u could just type Gi1..... but on Catalyst/Enterprise switches u can’t change that convention.
There isn’t a CLI command to “shorten” the naming back to the old style, you’ll always need to use gig1/0/1. What you can do is:
Use abbreviations: int gi1/0/1 u only need the unique part.
Use range commands: int range gi1/0/1-4 if u want to configure several ports.
So my Cisco friend, as a short answer: it’s expected behavior, not stack-related, and there’s no way to revert to the 350-style syntax.
Hope it helps, and enjoy ur weekend!!!
-Enes
08-17-2025 04:39 AM
gDay christian.sonnemans@xs4all.nl Alright so, that interface naming is normal on the newer Catalyst platforms, it isn’t from stacking, it’s just how IOS XE labels ports now. gig1/0/1 - the first number refers to slot/module/port. Meaning even if u don’t have a stack or multiple modules, the syntax is fixed. ALso, on older SG/300/350 SMB switches u could just type Gi1..... but on Catalyst/Enterprise switches u can’t change that convention.
There isn’t a CLI command to “shorten” the naming back to the old style, you’ll always need to use gig1/0/1. What you can do is:
Use abbreviations: int gi1/0/1 u only need the unique part.
Use range commands: int range gi1/0/1-4 if u want to configure several ports.
So my Cisco friend, as a short answer: it’s expected behavior, not stack-related, and there’s no way to revert to the 350-style syntax.
Hope it helps, and enjoy ur weekend!!!
-Enes
08-17-2025 04:53 AM
WOW! that was quick
Thank you Enes for responding on my question. And yes it's sounds logic, I only thought that I did something wrong. I just have to get used to this naming convention. Thanks again for your clear explanation and yes I already used abbreviations, also on my 350's.
Have a nice day Enes, you made my day!
Greetings Christian Sonnemans
08-17-2025 04:44 AM
also read this document: https://www.cisco.com/c/en/us/td/docs/switches/campus-lan-switches-access/Catalyst-1200-and-1300-Switches/Admin-Guide/catalyst-1300-admin-guide.pdf
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide