Problems with IP Routing over Point-to-Point Ethernet Connection

Hello all -

We have two locations, HQ and a Datacenter.  We've been using a site-to-site VPN over the public Internet to connect the two locations.

We recently had a point-to-point ethernet circuit installed by FPL Fibernet and want to utilize that and remove the site-to-site VPN.  Here is the equipment at each end:

ASA 5510s providing Internet access and site-to-site VPN
2 Cisco 3750s as core switch stack in each location, directly connected to the inside interface on the ASA
Dell Servers/SAN hanging off various ports on the 3750s at each location

Each location is a separate VTP domain with it's own VLANs.  The FPL connection is plugged into int gig 2/0/47 in the Datacenter and int gig 1/0/48 in HQ.  Here's my problem...

I'm unclear how each site will see the other if both interfaces are merely configured as trunk ports.  Since the HQ switches don't know where the vlans/subnets live in the Datacenter, how will they know to pick up the L2 traffic off the trunk and route it?

I thought that perhaps it would be better to configure the interface on each end to be an IP port, then add static routes on each switch to point to the subnets/VLANs on the other side.  However, when I do this I'm unable to ping the interface on the other side or any subnets in the other site.

Could you help point me in the right direction?  Happy to provide configs or diagrams if needed.
paclaiborneAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Soulja53 6F 75 6C 6A 61 Commented:
Diags and configs please. :)
0
paclaiborneAuthor Commented:
Here's the HQ config.  May take me a little bit to get the datacenter one but it is essentially the same, just without all the QOS for voice since we don't have voice up there.
HQconfig.txt
0
rauenpcCommented:
Port 1/0/48 is not configured as a trunk but rather an l3 routed interface. To make this all work, you have essentially three choices. Use static routing to get each site to point to the other for their respective subnets. Use dynamic routing such as eigrp or ospf to accomplish the same as static except it's dynamic. Third, you could reconfigure the ports as a trunk and each site would need to have all vlans configured (ALL vlans).
I guess a fourth option would combine things. Make the link a trunk and configure routing over one of the vlan interfaces.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

paclaiborneAuthor Commented:
Thanks - I've go them set up as just l3 interfaces right now and intended to do static routing, but I can't even ping the l3 interface on the other side.  So 1/0/48 on the hq side is 172.16.0.65 and ip on the other end is .66 but no ping traffic goes through.  I don't have any acls in place and the vendor assured me the connection would pass l3 and l2 traffic.  If I went the trunk route and had to configure all vlans on each side, how would I do that since the vlan ids on each side overlap.? I guess change the vlan ids and access ports on one side so that they don't overlap?
0
rauenpcCommented:
I guess I forgot to mention... Configuring all the vlans at every site is an option... But a poor one. routing is the better choice whether done via l3 interface or l3 vlan.

If the interfaces are up on both sides and you cannot ping, I would contact the ISP. If you want to be very diligent, connect a laptop to the layer 3 port and do a ping test to make sure the port can ping altogether. This takes away the ISP link from the situation.
0
paclaiborneAuthor Commented:
Thanks - your responses helped us confirm the different options available to us.  I agree with you that we'd prefer to do L3 routing via interface or vlan.  We contacted the ISP and there were separate issues with the Tier 2 providers on both ends - one issue with a cross connect in the data center and one issue with all the VLAN tags not being stripped off.  Closing the question and awarding points...
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cisco

From novice to tech pro — start learning today.