03-26-2009 08:24 AM - edited 03-06-2019 04:50 AM
Are there any pitfalls of having this command on interfaces that will never be used for trunks? i.e. any unneeded traffic etc.
Thanks in advance.
/rls
03-26-2009 08:28 AM
They can actually become trunking interfaces if connected to another switch with mode desirable or mode auto
If you don't want to ever have those interfaces in trunking mode, change it to mode access
HTH,
__
Edison.
03-26-2009 08:35 AM
The majority of our switch interfaces are configured as such:
interface FastEthernet1/0/6
switchport access vlan 120
switchport mode dynamic desirable
duplex full
speed 100
spanning-tree portfast
...so in this case, I should just be removing the 'switchport mode dynamic desirable' line, correct?
/rls
03-26-2009 08:39 AM
Removing the line won't fix the problem.
The switchport needs to have a mode to run on. It depends on the hardware but removing the line may set your switchport to dynamic auto. If you are connecting to hosts, the recommended macro to run is switchport host
HTH,
03-26-2009 08:48 AM
So just to be clear, the 'switchport host' command will replace the other command in the configuration once I enter it in config mode?
/rls
03-26-2009 10:24 AM
switchport host is a macro. The command is clearly explained on the link I posted. If the commands that are part of the macro are already under the switchport, they won't be removed. It's like a copy and paste of a template that you may have.
__
Edison.
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