Beruflich Dokumente
Kultur Dokumente
Ref: http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960/software/release/12-
2_58_se/configuration/guide/2960scg/swvlan.html
What is VLAN?
A VLAN is a switched network that is logically segmented by function, project team, or
application, without regard to the physical locations of the users. VLANs have the same
attributes as physical LANs, but you can group end stations even if they are not physically
located on the same LAN segment. Any switch port can belong to a VLAN, and unicast,
broadcast, and multicast packets are forwarded and flooded only to end stations in the VLAN.
Each VLAN is considered a logical network, and packets destined for stations that do not
belong to the VLAN must be forwarded through a router.
VLANs are often associated with IP subnetworks. For example, all the end stations in a
particular IP subnet belong to the same VLAN. Interface VLAN membership on the switch is
assigned manually on an interface-by-interface basis. When you assign switch interfaces to
VLANs by using this method, it is known as interface-based, or static, VLAN membership.
Ref: [Cisco.com]
In the exhibit above, two hosts (Sales Person and Manager) are inter-connected on the
same switch. In this scenario, two hosts with different role (or belonging to different
department) are physical connected on the same device/network which allows access
between the hosts.
There are a few security implications below that should to be addressed to ensure the
separation of duties and/or isolation of risk.
1. Virus/Worm infection
2. Data Theft / Hacking
3. Broadcast Traffic
Getting Started
Before you begin, ensure the following
1. All hosts are connected to the switch port as shown.
2. Layer 3 Protocol on each host is configured. E.g. Usable IP address in the same
network is assigned on each host. You may use any Private IP address.
3. Verify the network connectivity. E.g. Ping from a host to another host.
In this scenario, VTP is used to distribute the same VLAN on all the switches. DIST1 switch will
be used as [VTP Server] switch to distribute new VLANs on other switches that are [VTP
Client].
About VTP
Ref: http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-
2_52_se/configuration/guide/3560scg/swvtp.html
Before you create VLANs, you must decide whether to use VTP in your network. Using VTP,
you can make configuration changes centrally on one or more switches and have those
changes automatically communicated to all the other switches in the network. Without VTP,
you cannot send information about VLANs to other switches.
VTP is designed to work in an environment where updates are made on a single switch and
are sent through VTP to other switches in the domain. It does not work well in a situation
where multiple updates to the VLAN database occur simultaneously on switches in the same
domain, which would result in an inconsistency in the VLAN database.
You can configure a switch to operate in any one of these VTP modes:
ServerIn VTP server mode, you can create, modify, and delete VLANs and specify
other configuration parameters, such as VTP version and VTP pruning, for the entire
VTP domain. VTP servers advertise their VLAN configuration to other switches in
the same VTP domain and synchronize their VLAN configuration with other switches
based on advertisements received over trunk links. VTP server is the default mode.
Getting Started
Before you begin, ensure the following
1. All switch ports connecting between the switches are configured as [Trunk] ports.
2. No new VLANs are created as this will be done later. E.g. Dont create any VLAN on
any switches.
Repeat this procedure on all switches except [DIST1] switch. DIST1 switch will be used for
distribution of VLANs on all [VTP Client] switches.
Create VLANs
Now you may create required VLANs on [VTP-Server] switch. Then show VLAN on other
switches.