Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
New Member

Metro Ethernet VLANs

Hello!

I've been digging through metroe best practices, but all I can find is ISP points of views on creating a metroe WAN rather than from an internal business standpoint. My company is getting a metroe circuit in two weeks so I'm labbing up a WAN in GNS3 and my configurations aren't working. The MetroE will be a point-to-point connection. The main site will have the MetE circuit going into a Cisco 3750 and the remote site has a 3750 as well. I am going to use 802.1q trunks for the metroe traffic. My problem is I can ping the gateway for the vlan 3 at the remote site (192.168.201.1) from corporate, but I can't ping the PCs. This could be a GNS3 limitation or a screwed up Metro VLAN design all together. Any input here would be much appreciated. Here is the configuration for the Cisco 3750 at corporate:

!

*output omitted*

!

vlan 200

name MetE-Point-to-Point

!

interface fa0/1

description Trunk2MetE

switchport mode trunk

!

interface vlan 200

ip address 10.10.200.1 255.255.255.252

!

ip route 192.168.201.0 255.255.255.0 10.10.200.2

Cisco 3750 Remote Site:

!

*output omitted*

!

!

vlan 3

name Comp-LAN

!

vlan 200

name MetE-Point-to-Point

!

interface fa0/1

description Trunk2MetE

switchport mode trunk

!

interface fa0/2-24

switchport access vlan 3

!

interface vlan 3

ip address 192.168.201.1 255.255.255.0

!

interface vlan 200

ip address 10.10.200.1 255.255.255.252

!

ip default-gateway 10.10.200.2

!

ip route 0.0.0.0 0.0.0.0 10.10.200.1

 

Everyone's tags (1)
1 REPLY
New Member

Correction on the remote site

Correction on the remote site:

vlan 200's ip is 10.10.200.2 not 10.10.200.1 like the config shows.

149
Views
0
Helpful
1
Replies
CreatePlease to create content