VLANs TABLE ISSUE(edited – lorraine)

Network Warrior; Written by Gary A. Donahue; Note – fix tables; Published by O’Reilly; Chapter 4



Virtual LANs, or VLANs, are virtual separations within a switch that provide distinct logical LANs that each behave as if they were configured on a separate physical switch. Before the introduction of VLANs, one switch could serve only one LAN. VLANs enabled a single switch to serve multiple LANs. Assuming no vulnerabilities exist in the switch’s operating system, there is no way for a frame that originates on one VLAN to make its way to another.

Connecting VLANs

Figure 4-1 shows a switch with multiple VLANs. The VLANs have been numbered 10, 20, 30, and 40. In general, VLANs can be named or numbered; Cisco’s implementation uses numbers to identify VLANs by default. The default VLAN is numbered 1. If you plug a number of devices into a switch without assigning its ports to specific VLANs, all the devices will be in VLAN 1.


Figure 4-1.  VLANs on a switch 

Frames cannot leave the VLANs from which they originate. This means that in the example configuration, Jack can communicate with Jill, and Bill can communicate with Ted, but Bill and Ted cannot communicate with Jack or Jill in any way.

For a packet on a layer-2 switch to cross from one VLAN to another, an outside router must be attached to each of the VLANs to be routed.  Figure 4-2 shows an external router connecting VLAN 20 with VLAN 40. Assuming a proper configuration on the router, Bill will now be able to communicate with Jill, but neither workstation will show any indication that they reside on the same physical switch.


Figure 4-2.  External routing between VLANs

When expanding a network using VLANs, the same limitations apply. If you connect another switch to a port that is configured for VLAN 20, the new switch will be able to forward frames only to or from VLAN 20. If you wanted to connect two switches, each containing four VLANs, you would need four links between the switches: one for each VLAN. A solution to this problem is to deploy trunks between switches. Trunks are links that carry frames for more than one VLAN.

Figure 4-3 shows two switches connected with a trunk. Jack is connected to VLAN 20 on Switch B, and Diane is connected to VLAN 20 on Switch A. Because there is a trunk connecting these two switches together, assuming the trunk is allowed to carry traffic for all configured VLANs, Jack will be able to communicate with Diane. Notice that the ports to which the trunk is connected are not assigned VLANs. These ports are trunk ports, and as such, do not belong to a single VLAN.

Trunks also allow another possibility with switches. Figure 4-2 showed how two VLANs can be connected with a router, as if the VLANs were separate physical networks. Imagine if you wanted to route between all of the VLANs on the switch. How would you go about such a design? Traditionally, the answer would be to provide a single connection from the router to each of the networks to be routed. On this switch, each of the networks is a VLAN, so you’d need a physical connection between the router and each VLAN.

Connecting VLANs


Figure 4-3.  Two switches connected with trunk

As you can see in Figure 4-4, with this setup, four interfaces are being used both on the switch and on the router. Smaller routers rarely have four Ethernet interfaces, though, and Ethernet interfaces on routers can be costly. Additionally, switches are bought with a certain port density in mind. In this configuration, a quarter of the entire switch has been used up just for routing between VLANs.


Figure 4-4.  Routing between multiple VLANs

Another way to route between VLANs is commonly known as the router on a stick configuration. Instead of running a link from each VLAN to a router interface, you can run a single trunk from the switch to the router. All the VLANs will then pass over a single link, as shown in Figure 4-5.

Deploying a router on a stick saves a lot of interfaces on both the switch and the router. The downside is that the trunk is only one link, and the total bandwidth available on that link is only 10 Mbps. In contrast, when each VLAN has its own


Figure 4-5.  Router on a stick

link, each VLAN has 10 Mbps to itself. Also, don’t forget that the router is passing traffic between VLANs, so chances are each frame will be seen twice on the same link—once to get to the router, and once to get back to the destination VLAN.

Using a switch with a router is not very common anymore because most vendors offer switches with layer-3 functionality built-in. Figure 4-6 shows conceptually how the same design would be accomplished with a layer-3 switch. Because the switch contains the router, no external links are required. With a layer-3 switch, every port can be dedicated to devices or trunks to other switches.


Figure 4-6.  Layer-3 switch

Configuring VLANs

VLANs are typically configured via the CatOS or IOS command-line interpreter (CLI), like any other feature. However, some IOS models, such as the 2950 and 3550 switches, have a configurable VLAN database with its own configuration mode and commands. This can be a challenge for the uninitiated, especially because the configuration for this database is completely separate from the configuration for the rest of the switch. Even a write erase followed by a reload will not clear the VLAN database on these switches.Configuring through the VLAN database is a throw back to older models that offered no other way to manage VLANs. All newer switches (including those with a VLAN database) offer the option of configuring the VLANs through the normal IOS CLI. Switches like the 6500, when running in native IOS mode, only support IOS commands for switch configuration.

Cisco recommends that the VLAN Trunking Protocol (VTP) be configured as a first step when configuring VLANs. This idea has merit, as trunks will not negotiate without a VTP domain. However, setting a VTP domain is not required to make VLANs function on a single switch. Configuring VTP is covered later (see Chapter 5 and Chapter 6).

CatOS

For CatOS, creating a VLAN is accomplished with the set vlan command:

  Switch1-CatOS# (enable) set vlan 10 name Lab-VLAN
 
VTP advertisements transmitting temporarily stopped,
  and will resume after the command finishes.
  Vlan 10 configuration successful

There are a lot of options when creating a VLAN, but for the bare minimum, this is all that’s needed. To show the status of the VLANs, execute the show vlan command:

  Switch1-CatOS# (enable) sho vlan

VLAN Name

Status

IfIndex Mod/Ports, Vlans

 

 

 

1

default

active

7

1/1-2

 

 

 

 

2/1-2

 

 

 

 

3/5-48

 

 

 

 

6/1-48

10

Lab-VLAN

active

112

 

20

VLAN0020

active

210

3/1-4

1002 fddi-default active

8

 

1003 token-ring-default active

11

 

1004 fddinet-default active

9

 

1005 trnet-default active

10

 

1006 Online Diagnostic Vlan1 active

0

internal

1007 Online Diagnostic Vlan2 active

0

internal

1008 Online Diagnostic Vlan3 active

0

internal

1009 Voice Internal Vlan active

0

internal

1010 Dtp Vlan active

0

internal

1011 Private Vlan Reserved Vlan suspend

0

internal

1016 Online SP-RP Ping Vlan active

0

internal

Notice that VLAN 10 has the name you assigned; VLAN 20’s name, which you did not assign, defaulted to VLAN0020. The output shows which ports are assigned to VLAN 20, and that most of the ports still reside in VLAN 1. (Because VLAN 1 is the default VLAN, all ports reside there by default.)

There are no ports in VLAN 10 yet, so add some, again using the set vlan command:

  Switch1-CatOS# (enable) set vlan 10 6/1,6/3-4
  VLAN 10 modified.
  VLAN 1 modified.
  VLAN   Mod/Ports
  —-  ———————-
 
10  6/1,6/3-4

You’ve now added ports 6/1, 6/3, and 6/4 to VLAN 10. A show vlan will reflect these changes:

  Switch1-CatOS# (enable) sho vlan

VLAN Name

Status

IfIndex Mod/Ports, Vlans

 

 

 

1

default

active

7

1/1-2

 

 

 

 

2/1-2

 

 

 

 

3/5-48

 

 

 

 

6/2,6/5-48

10

Lab-VLAN

active

112

6/1,6/3-4

20

VLAN0020

active

210

3/1-4

1002 fddi-default active

8

 

1003 token-ring-default active

11

 

1004 fddinet-default active

9

 

1005 trnet-default active

10

 

1006 Online Diagnostic Vlan1 active

0

internal

1007 Online Diagnostic Vlan2 active

0

internal

1008 Online Diagnostic Vlan3 active

0

internal

1009 Voice Internal Vlan active

0

internal

1010 Dtp Vlan active

0

internal

1011 Private Vlan Reserved Vlan suspend

0

internal

1016 Online SP-RP Ping Vlan active

0

internal

The output indicates that VLAN 1 was modified as well. This is because the ports had to be removed from VLAN 1 to be added to VLAN 10.

IOS Using VLAN Database

This method is included for the sake of completeness. Older switches that require this method of configuration are no doubt still deployed. Newer switches that support the VLAN database, such as the 3550, actually display this message when you enter VLAN database configuration mode:

  3550-IOS# vlan database
  % Warning: It is recommended to configure VLAN from config mode,
    as VLAN database mode is being deprecated. Please consult user
    documentation for configuring VTP/VLAN in config mode.

If you have an IOS switch with active VLANs, but no reference is made to them in the running configuration, it’s possible that they were configured in the VLAN database. Another possibility is that they were learned via VTP (we will cover this in Chapter6).

Configuring VLANs

To configure VLANs in the VLAN database, you must enter VLAN database configuration mode with the command vlan database. Requesting help ( ? ) lists the commands available in this mode:

  2950-IOS# vlan database
 
2950-IOS(vlan)# ?
 
VLAN database editing buffer manipulation commands:
    
abort  Exit mode without applying the changes
    apply  Apply current changes and bump revision number
    exit   Apply changes, bump revision number, and exit mode
    no     Negate a command or set its defaults
    reset  Abandon current changes and reread current database
    show   Show database information
    vlan   Add, delete, or modify values associated with a single VLAN
    vtp    Perform VTP administrative functions.

To create a VLAN, give the vlan command followed by the VLAN number and name:

  2950-IOS(vlan)# vlan 10 name Lab-VLAN
  VLAN 10 added:
      Name: Lab-VLAN

You can show the VLANs configured from within VLAN database mode with the command show . You have the option of displaying the current database ( show current ), the differences between the current and proposed database ( show changes ), or the proposed database as it will look after you apply the changes using the apply command or exit VLAN database configuration mode. The default behavior of the show command is show proposed :

  2950-IOS(vlan)# show
   
VLAN ISL Id: 1
      Name: default
      Media Type: Ethernet
      VLAN 802.10 Id: 100001
      State: Operational
      MTU: 1500
      Backup CRF Mode: Disabled
      Remote SPAN VLAN: No
 

    VLAN ISL Id: 10
      Name: Lab-VLAN
      Media Type: Ethernet
      VLAN 802.10 Id: 100010
      State: Operational
      MTU: 1500
      Backup CRF Mode: Disabled
      Remote SPAN VLAN: No

Nothing else is required to create a simple VLAN. The database will be saved upon exit:

  2950-IOS(vlan)# exit
 
APPLY completed.
  Exiting….

Now, when you execute the show vlan command in IOS, you’ll see the VLAN you’ve created:

  2950-IOS# sho vlan

 

VLAN Name

Status

Ports

 

 

 

1 default 10 Lab-VLAN

active active

Fa0/1, Fa0/2, Fa0/3, Fa0/4 Fa0/5, Fa0/6, Fa0/7, Fa0/8 Fa0/9, Fa0/10, Fa0/11, Fa0/12 Fa0/13, Fa0/14, Fa0/15, Fa0/16 Fa0/17, Fa0/18, Fa0/19, Fa0/20 Fa0/21, Fa0/22, Fa0/23, Fa0/24 Gi0/1, Gi0/2

1002 fddi-default

active

 

1003 token-ring-default 1004 fddinet-default

active active

 

1005 trnet-default

active

 

Adding ports to the VLAN is accomplished in IOS interface configuration mode, and is covered in the next section.

IOS Using Global Commands

Adding VLANs in IOS is relatively straightforward when all of the defaults are acceptable, which is usually the case. First, enter configuration mode. From there, issue the vlan command with the identifier for the VLAN you’re adding or changing. Next, specify a name for the VLAN with the name subcommand (as with CatOS, a default name of VLANxxxx is used if you do not supply one):

  2950-IOS# conf t
 
Enter configuration commands, one per line. End with CNTL/Z.
  2950-IOS(config)#
vlan 10
 
2950-IOS(config-vlan)# name Lab-VLAN

Exit configuration mode, then issue the show vlan command to see the VLANs present:

  2950-IOS# sho vlan

 

VLAN Name

Status

Ports

 

 

 

1 default 10 Lab-VLAN

active active

Fa0/1, Fa0/2, Fa0/3, Fa0/4 Fa0/5, Fa0/6, Fa0/7, Fa0/8 Fa0/9, Fa0/10, Fa0/11, Fa0/12 Fa0/13, Fa0/14, Fa0/15, Fa0/16 Fa0/17, Fa0/18, Fa0/19, Fa0/20 Fa0/21, Fa0/22, Fa0/23, Fa0/24 Gi0/1, Gi0/2

1002 fddi-default

active

 

1003 token-ring-default 1004 fddinet-default

active active

 

1005 trnet-default

active

 

Configuring VLANs

Assigning ports to VLANs in IOS is done in interface configuration mode. Each interface must be configured individually with the switchport access command (this is in contrast to the CatOS switches, which allow you to add all the ports at once with the set vlan command):

  2950-IOS(config)# int f0/1
  2950-IOS(config-if)# switchport access vlan 10
  2950-IOS(config-if)# int f0/2
  2950-IOS(config-if)# switchport access vlan 10

Newer versions of IOS allow commands to be applied to multiple interfaces with the interface range command. Using this command, you can accomplish the same result as before while saving some precious keystrokes:

  2950-IOS (config)# interface range f0/1 – 2
 
2950-IOS (config-if-range)# switchport access vlan 10

Now, when you execute the show vlan command, you’ll see that the ports have been assigned to the proper VLAN:

  2950-IOS# sho vlan  

 

VLAN Name

Status

Ports

 

 

 

1 default

active

Fa0/3, Fa0/4, Fa0/5, Fa0/6

 

 

Fa0/7, Fa0/8, Fa0/9, Fa0/10

 

 

Fa0/11, Fa0/12, Fa0/13, Fa0/14

 

 

Fa0/15, Fa0/16, Fa0/17, Fa0/18

 

 

Fa0/19, Fa0/20, Fa0/21, Fa0/22

 

 

Fa0/23, Fa0/24, Gi0/1, Gi0/2

10 Lab-VLAN

active

Fa0/1, Fa0/2

1002 fddi-default

active

 

1003 token-ring-default

active

 

1004 fddinet-default

active

 

1005 trnet-default

active

 

 

 

[gp-comments width="770" linklove="off" ]

chat sex hikayeleri Ensest hikaye