Configuring a trunk with an access command too?

Unanswered Question
Jul 12th, 2007
User Badges:

Hi, I am just curious to know, what does this do?


interface GigabitEthernet2/1

switchport access vlan 800

switchport trunk encapsulation dot1q

switchport trunk native vlan 50

switchport trunk allowed vlan 50,60,800

switchport mode trunk


The switchport is obviously a trunk (as per the last command), but then why is there also an access command to VLAN 800?


What I don't understand is that a trunk's purpose is to trunk multiple VLANs across a switchport so why does the above configuration specify access to a single VLAN?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
sundar.palaniappan Thu, 07/12/2007 - 19:40
User Badges:
  • Green, 3000 points or more

That's a misconfiguration. You can safely remove 'switchport access vlan 800' command from the interface config as it isn't doing anything. Is it possible that might be legacy config that someone forgot to remove after the port was configured as a trunk.


HTH


Sundar

voiper_99 Thu, 07/12/2007 - 20:27
User Badges:

Thank you for the reply, however, I read this at another forum:


"It sets the port VLAN for when the port is in access mode. If you set

the mode to access (switchport mode access) then the port VLAN would

switch to 800 from 50; if you switch to one of the sensing modes

(switchport mode dynamic ...) then the state the port negotiates into

will determine the port VLAN."


I have also heard that the "vlan access port" command acts as a trunk :S I hope someone can give me a firm answer as I have been given three different explanations so far.


Thank you for your time.

Actions

This Discussion