Configuring VLAN’s. Alcatel-Lucent Security Products Configuration Example Series . What is a VLAN?.
PowerPoint Slideshow about 'Configuring VLAN s' - shasta
An Image/Link below is provided (as is) to download presentation
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
A VLAN is a collection of hosts on different physical segments of a switched network that communicate with each other as if they were on the same segment. VLAN’s allow network administrators to define multiple LAN’s on a single collection of switches.
One useful way to think of VLAN’s is that the combination of the VLAN and the physical port form a virtual port. From this point of view, a trunk port is simply a collection of many virtual ports.
The most common reason is to segregate your broadcast domain keeping individual groups in their own broadcast domains, or on their own networks.
An example of a VLAN application would be if you have multiple departments in one location. You would put your Accounting Department on one VLAN and your Engineering Department on another.
You might have a case where you have part of both departments in two separate buildings or locations. You could then still keep them on their own network (broadcast domain) by assigning VLAN tags to their traffic. So for instance even though there are two locations you could have all of your accountants on VLAN 101 and all of your engineers on VLAN 102.
VLAN tags are generally assigned at Ethernet switches, though they can also be assigned at routers or firewalls.
Your rule set may be just as simple as this one where you are passing everything between those two groups of engineers.
Don’t worry about the VLAN Match here. You would use that if you had multiple VLAN’s going through one rule set, yet wanted to assign certain rules only to one VLAN. Leave that field with the wild card for now.
Once you save your work and do a save and apply to the Brick your engineers in Buffalo and NJ should be able to pass data to each other as if they are on the same LAN.
This is only one simple example. You can get a lot fancier than this. The VLAN features of the Brick are rich and leave room for great creativity.
If you now want to add another VLAN to your physical port one you would basically just go through the steps again. All you would need to do is modify the firewall. By adding a rule for all of the accountants, for example, to communicate you would just add a second rule to your rule set and add VLAN 102 to your VLAN Membership on Port 1.
This is a fairly simple example. Much more detail can be found in the Administrative Guide.