Link to home
Start Free TrialLog in
Avatar of AXISHK
AXISHK

asked on

Switch Configuration

I see three different configuration in my cisco switch. Does it mean any difference, especially on first and last one ?  Tks
 
interface FastEthernet3/0/16
 switchport access vlan 3

interface FastEthernet2/0/22
 switchport access vlan 3
 switchport mode access
 spanning-tree portfast

interface FastEthernet1/0/11
 switchport access vlan 3
 switchport mode access
SOLUTION
Avatar of arnold
arnold
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of AXISHK
AXISHK

ASKER

so some of the ports may connect to mini switch, should I configure the port with
 no spanning-tree portfast

tks
As long as the mini switch is not used to feed another switch which might feed another to a point where it might create a loop....

Guess the question should be the reverse what is it you want to do?
The second and last will only allow VLAN3 traffic to pass through it, while the first could dynamically allow other VLAN traffic to flow making the connection function as a trunk.
Avatar of AXISHK

ASKER

we will replace switches for customers,

so if spanning-tree portfast is binded in the interface, those mini switch will not work, correct
when the spanning-tree portfast is enabled if it detects a packet loop meaning it sees a mac address from the connection that it already knows from another source, it will lock out this port.


port 1 <=> remote Switch

Port 4 <=> another link

The switch sees the same MAC address on port 1 and port 4. port 1 with the spanning-tree portfast will be locked out to prevent packet loop, enters on port 1 leaves on port 4 reenters on port 1 leaves on port 4....

.
Avatar of AXISHK

ASKER

Do you mean"spanning-tree portfast" doesn't block the port to min-switch connection and it only disable the port when loop is detected, correct ?   ie. I can keep it in my configuration. Tks
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of AXISHK

ASKER

To test my understanding :

if a port connect to a PoE switch where IP phones are attached, it should not cause any harm to put spanning-tree portfast on the interfaces, correct?
Yes and No. If the PoE Switch is the only bridge connected there will probably be no harm but it is not recommanded to do portfast an inter-switch link.
Avatar of AXISHK

ASKER

can I say if I can ensure there is only one link connecting my Cisco switch to PoE switch, it shouldn't be any problem ? The only concern is there are two links connecting these two switch, where loop will be formed...

Tks
Yes you could, but there is really no reason to do so. You would save a few seconds in case spanning-tree needs to reconverge.
Avatar of AXISHK

ASKER

Tks
I believe part of the accepted solution is incorrect.  Specifically the premise that 'switchport mode access' is a redundant command.

First off, remember that if a command is set at it's default, it won't be shown.

Trunk port carries multiple vlans
Access port only carries one vlan

The default config for a switch port is to be a trunk.  ('switchport mode trunk')  So in order for a port to be an access port, which means it will only pass traffic from a specific VLAN, you have to issue 'switchport mode access' on that interface.  'switchport access vlan 3' is telling the switch WHICH vlan to restrict to and to tag with.  If you go from 'switchport mode access' to 'switchport mode trunk', the switch doesn't clear out your 'switchport access vlan 3' setting.  That way you can go from access to trunk and back to access without having to remember what vlan it was previously on.

If you set 'switchport mode access' with no corresponding 'switchport access vlan #' command, you are making it an access port on VLAN 1.
Ben,

I think what you mean by default trunk is on switches using DTP which have either switchport mode dynamic auto or on some other models switchport mode dynamic desireable enabled by default. That would not be equivalend to mode trunk since DTP would be used to negotiate if a trunk should be formed or not.

Nevertheless good explanation I left the bits and pieces about DTP out.
If the mode is not hardcoded "switchport mode access" the Interface can form a trunk if the switch supports DTP, therefore it is best practice to set switchport mode manually!