I understand that the native vlan(untagged) traffic will be vlan 100. However, if the port negotiates to be used as a trunk due to DTP frames – vlans 100-105 will be tagged going over the trunk link.
But, what I do not understand – “what happens if the port does not negotiate as a trunk link”? If the latter occurs, will the port come up as an ‘access’ port, part of VLAN 100 since it is ‘native’ being ‘untagged’ traffic? If this is the case, then the port is part of vlan 100 as an ‘access’ port, since vlan access ports are untagged?
If the the interface fails to negotiate a trunk, the operational mode will be access and none of your trunk commands will apply. With this configuration, the interface will be on the default VLAN (1) if a trunk isn't negotiated. If you want to make sure that the port uses a native VLAN of 100 regardless of which mode is negotiated, you'll need to add "switchport access vlan 100" to your interface configuration so that VLAN 100 is selected either way.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...