To bring this topic to a conclusion, here are the basic ideas for a vlan
tunneling lab exercise
Customer A and Customer B each use the same provider to carry network
traffic between their respective sites.
Necessary Equipment
To properly perform this Lab exercise, the following equipment is required
1) Four routers capable of 802.1Q trunking on their Ethernet interfaces. Two
such ethernet interfaces on each of the routers is preferable, but the Lab
can be modified to use routers with only one such ethernet port on each.
In fact, for my practice, I used two 2621's and two 2620's
2) Two Catalyst 3550 switches. Layer 3 capability is not required for this
Lab exercise.
3) Patch cables for connecting router ethernet ports to switches
4) Patch cables for connecting the two switches. These may be fiber via
GBIC, Gigastack, or Cat5 ethernet crossover cables.
General Configuration Information
All Customer routers are configured identically.
Two routing protocols are in place - OSPF and EIGRP
Networks 172.20.x.x/24 are OSPF routes
Networks 172.21.x.x/24 are EIGRP routes
The VLAN to subnet relationship is the same on both customer networks, as
follows:
VLAN 10 = 172.20.10.0/24
VLAN 20 = 172.20.20.0/24
VLAN 30 = 172.20.30.0/24
VLAN 40 = 172.21.40.0/24
VLAN 50 = 172.21.50.0/24
VLAN 60 = 172.20.60.0/24
As a sanity check, to assure that leaking is not taking place, each router
should be configured with two loopback interfaces, one placed into the OSPF
process and the other being placed into the EIGRP process. Something along
the lines of:
Customer A, Router 1
Loopback 1 = 192.168.1.0/24
Loopback 2 = 192.168.11.0/24
Customer A, Router 2
Loopback 1 = 192.168.101.0/24
Loopback 2 = 192.168.111.0/24
Customer B, Router 1
Loopback 1 = 192.168.2.0/24
Loopback 2 = 192.168.22.0/24
Customer B, Router 2
Loopback 1 = 192.168.202.0/24
Loopback 2 = 192.168.222.0/24
At the end of the day, thanks to VLAN tunneling, Customer_A routers saw
eachother, and the OSPF and EIGRP routes propagated properly. Same for
Customer_B
CUSTOMER_A_ROUTER_1#sh ip route
C 192.168.11.0/24 is directly connected, Loopback21
172.21.0.0/24 is subnetted, 4 subnets
C 172.21.60.0 is directly connected, FastEthernet0/1.60
C 172.21.50.0 is directly connected, FastEthernet0/1.50
C 172.21.40.0 is directly connected, FastEthernet0/1.40
C 172.21.0.0 is directly connected, FastEthernet0/1
172.20.0.0/24 is subnetted, 4 subnets
C 172.20.30.0 is directly connected, FastEthernet0/0.30
C 172.20.20.0 is directly connected, FastEthernet0/0.20
C 172.20.10.0 is directly connected, FastEthernet0/0.10
C 172.20.0.0 is directly connected, FastEthernet0/0
C 192.168.1.0/24 is directly connected, Loopback20
O IA 192.168.101.0/24 [110/2] via 172.20.30.2, 00:24:04, FastEthernet0/0.30
<<<========
[110/2] via 172.20.10.2, 00:24:04, FastEthernet0/0.10
[110/2] via 172.20.20.2, 00:24:05, FastEthernet0/0.20
D 192.168.111.0/24 [90/156160] via 172.21.50.2, 00:24:27,
FastEthernet0/1.50 <<<=======
[90/156160] via 172.21.40.2, 00:24:27,
FastEthernet0/1.40
[90/156160] via 172.21.60.2, 00:24:27,
FastEthernet0/1.60
CUSTOMER_B_ROUTER_1#sh ip route
D 192.168.222.0/24 [90/156160] via 172.21.50.2, 00:25:06,
FastEthernet0/1.50 <<<========
[90/156160] via 172.21.60.2, 00:25:06,
FastEthernet0/1.60
[90/156160] via 172.21.40.2, 00:25:06,
FastEthernet0/1.40
172.21.0.0/24 is subnetted, 4 subnets
C 172.21.60.0 is directly connected, FastEthernet0/1.60
C 172.21.50.0 is directly connected, FastEthernet0/1.50
C 172.21.40.0 is directly connected, FastEthernet0/1.40
C 172.21.0.0 is directly connected, FastEthernet0/1
172.20.0.0/24 is subnetted, 4 subnets
C 172.20.30.0 is directly connected, FastEthernet0/0.30
C 172.20.20.0 is directly connected, FastEthernet0/0.20
C 172.20.10.0 is directly connected, FastEthernet0/0.10
C 172.20.0.0 is directly connected, FastEthernet0/0
C 192.168.22.0/24 is directly connected, Loopback21
O IA 192.168.202.0/24 [110/2] via 172.20.30.2, 00:13:09, FastEthernet0/0.30
<<<=========
[110/2] via 172.20.10.2, 00:13:09, FastEthernet0/0.10
[110/2] via 172.20.20.2, 00:13:09, FastEthernet0/0.20
C 192.168.2.0/24 is directly connected, Loopback20
CUSTOMER_B_ROUTER_1#
The documentation I used for switch configurations can be found on the
following CCO link:
http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/1219ea1/3550scg/sw
tunnel.htm
--
TANSTAAFL
"there ain't no such thing as a free lunch"
Robert A. Heinlein
may his soul grumble in peace
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=52053&t=52053
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
