We have got a uplink to the 10 Gig port on 5900 switch, where in the uplink carries VLAN - Y from the core switch.
On the 5900 switch, on the uplink port we have executed the below commands
> interface TenGigbitEthernet 1/0/1
> port link-type trunk
> port trunk permit vlan Y
> save
Now we have added few other ports on 5900 switch to VLAN Y as well.
However when we connected a server to 5900 and assigned a VLAN Y IP, it doesnt seem to work
Is there anything that we have missed configuring on the switch ?
Please let me know.
Thanks
Solved! Go to Solution.
Thank you TerjeAFK
We were able to resolve the issue.
Your answer matches to the problem we faced, we made the uplink ports as untagged and it started working both on the core switch and on the uplink switch.
Basically we set the pvid on the ports to VLAN Y and not to the default vlan 1.
It would be helpful if you can let us know why the ports had to be untagged for it to work.
Why do we do tag and un-tag.
Hi, glad to hear that it worked out. Tagging is normally used on uplink ports that connect switches because we want to send more than one VLAN between the switches. Normally you can only have one untagged VLAN on a port, but you can have many tagged VLANs. So if you want more than just VLAN y on this 5900 switch then you need to used VLAN tagging.
Thanks.
One last question,
say the VLAN y on the core switch is "untagged", and then the uplink port on the access switch has VLAN y in "tagged" state.
Will the uplink work or not ?
That is switch dependent, I have seen this config both working and not working on various models. Best practice is to have the same config at both ends of an uplink.
Thanks TerjeAFK
Having that said untagged frame is untagged and shall be handled as suched. Compared to a tagged frame which should be handled as such aswell...