VLANs are created on Layer 2 switches to control broadcasts and enforce the use of a Layer 3 device for communications. Each VLAN is created in the local switch's database for use. If a VLAN is not known to a switch, that switch cannot transfer traffic across any of its ports for that VLAN. VLANs are created by number, and there are two ranges of usable VLAN numbers (normal range 1-1000 and extended range 1025-4096). When a VLAN is created, you can also give it certain attributes such as a VLAN name, VLAN type, and its operational state. To create a VLAN, use the following steps.
1) Configure VTP. VTP is a protocol used by Cisco switches to maintain a consistent database between switches for trunking purposes. VTP is not required to create VLANs; however, Cisco has set it up to act as a conduit for VLAN configuration between switches as a default to make administration of VLANs easier. Because of this, you must first either configure VTP with a domain name or disable VTP on the switch.
2) Create the VLAN. VLANs are created by number. The two ranges of VLANs are as follows: The standard range consists of VLANs 1 to 1000. The extended range consists of VLANs 1025 to 4096. Extended VLANs are currently supported only on switches running COS software version 6.1 or greater. When you create a VLAN, you have many options to consider. Many options are valid only for FDDI and Token Ring VLANs. Some of the items configured deal with options, such as private VLANs, which are discussed in other sections in this book. VLANs are created using the set vlan command for COS devices or with the vlan command in vlan database mode for IOS switches.
Runetower.com
The name given to a VLAN on an IEEE 802.1Q trunk whose frames are not tagged is the "native VLAN." The native VLAN is used for untagged traffic on a trunk link, allowing devices that do not support VLAN tagging to communicate over the trunk. By default, VLAN 1 is designated as the native VLAN, but this can be changed to another VLAN as needed.
A VLAN is a virtual LAN. In technical terms, a VLAN is a broadcast domain created by switches. Normally, it is a router creating that broadcast domain. With VLANs, a switch can create the broadcast domain. This works by, you, the administrator, putting some switch ports in a VLAN other than 1, the default VLAN. All ports in a single VLAN are in a single broadcast domain. Because switches can talk to each other, some ports on switch A can be in VLAN 10 and other ports on switch B can be in VLAN 10. Broadcasts between these devices will not be seen on any other port in any other VLAN, other than 10. However, these devices can all communicate because they are on the same VLAN. Without additional configuration, they would not be able to communicate with any other devices, not in their VLAN.
The command "shutdown vlan 17" is used in network configuration to disable VLAN 17 on a network switch. When executed, it effectively prevents any traffic from being forwarded through this VLAN, rendering it inactive. This can be useful for network management purposes, such as troubleshooting or reconfiguring the VLAN. To reactivate the VLAN, the command "no shutdown vlan 17" would be used.
this would be called virtual local area connection or a vlan
Since VLAN's cannot communicate with other VLAN's directly, I believe you would have to set up a router to do that. I would check out how to set up a bridge between two VLAN's.
Reassigning a port to another VLAN before removing the VLAN from the VLAN database ensures that there is no disruption in network connectivity for devices connected to that port. If a port is removed from a VLAN without reassignment, it may result in loss of access to the network for those devices, causing potential downtime and disruption. Additionally, this practice helps maintain network organization and prevents configuration errors that could arise from deleting a VLAN that still has active ports.
VLAN: How are packets distributed with respect to the different classifications?
The native VLAN is untagged. If the VLAN 99 traffic to the router is untagged (as it would be, because that is native on the switches), the router cannot interpret the data because there is no VLAN information in the header as expected. In turn, the router tags all VLAN 99 traffic outbound, and leaves VLAN 1 data untagged, so the switches are unable to correctly interpret either. VLAN traffic to the other VLANs should not be affected by the assignment of the native VLAN.
It is the VLAN that supports untagged traffic on an 802.1Q trunk
no vlan XXX copy run star
VLAN is a group of hosts with a common set of requirements that communicate as if they were attached to the same broadcast domain, regardless of their physical location. Inter VLAN is defined as two VLANS connected to each other and communicating.