I have found the config to make a fast ethernet port on a 7204vxr a trunk port. Is there a way to make the same port an access port in order to receive untagged packets? (without using sub-interfaces?) For a trunk port I just use:
vlan-id or vlan-range and it works great. But there is no option for "native" with the IOS I am running. 12.4.24T
A Layer 2 port can function as either a trunk port, an access port, or a private VLAN port.
A trunk port can carry nontagged packets simultaneously with the 802.1Q tagged packets. When you assign a default port VLAN ID to the trunk port, all untagged traffic travels on the default port VLAN ID for the trunk port, and all untagged traffic is assumed to belong to this VLAN. This VLAN is referred to as the native VLAN ID for a trunk port. That is, the native VLAN ID is the VLAN that carries untagged traffic on trunk ports.
"When you assign a default port VLAN ID to the trunk port, all untagged traffic travels on the default port VLAN ID for the trunk port, and all untagged traffic is assumed to belong to this VLAN."
Not quite. Unless the native vlan is specifically defined on the trunk port (switchport trunk native vlan x), the native vlan will still default to vlan 1 while the port is trunking.
The default vlan configuration you are recommending (switchport access vlan x) is in the event that the trunk port stops trunking and reverts to being an access port that will be placed in a specific vlan. That vlan would normally be the native vlan of 1.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.