HPE Aruba Networking & ProVision-based
1829595 Members
2141 Online
109992 Solutions
New Discussion

How the &$)# do I make this work?

 
SlimJC
Occasional Visitor

How the &$)# do I make this work?

Spent the day banging my head against the wall and figured I would defer to the experts. 

 

I'm working with a situation that I've never had to deal with before. We have two locations, A and B. Each of these locations currently operates independantly. Each has their own Internet provider and default route to a firewall. We have now put in place an MPLS circuit and wish to connect the two locations while still maintaining thier independent outboud lines. 

 

Site A has an HP 4208VL providing layer 3 VLAN routing and Site B has an HP 2920 at their core. 

 

The ISP has provided a gateway address for each end of the circuit, 100.65.0.1 for site A and 100.65.0.5 for site B, /30s. 

 

Each site has multiple VLANs configured, and we would like to be able to pass tagged traffic from one site to the other. How do we accomplish this on the Procurve equipment? These switches do not support PBR as far as I can tell. 

 

We set up a new VLAN 100 on both switches for this new subnet, site A with an interface of 100.65.0.2 255.255.255.252 and site B with an interface of 100.65.0.6 255.255.255.252. We then added a static route on switch A for 100.65.0.0/24 100.65.0.1 and 100.65.0.0/24 100.65.0.5 on switch B. This enabled us to ping back and forth to the switch vlan interfaces without a problem. 

 

So at this point I assume we would need to added the stratic routes for each VLAN. Attempting to add: ip route 192.168.18.30 (interface on switch B VLAN) 255.255.255.255 100.65.0.6 results in an error "next hop not directly connected" 

 

Appreciate any help. I'm sure I'm probably going at this wrong entirely. 

 

Thx

JC

3 REPLIES 3
Vince-Whirlwind
Honored Contributor

Re: How the &$)# do I make this work?

the route you need at site A should look like:

<SITE B subnet, eg 192.168.18.0/24> --> 100.65.0.1

 

At Site B you need:

<SITE A subnet> --> 100.65.0.5

 

Also, depending on how the MPLS provider is doing things, they may have to add routes for your site subnets pointing at the correct routers.

SlimJC
Occasional Visitor

Re: How the &$)# do I make this work?

That makes sense, but how do I configure the port the MPLS is coming over? Should it be untagged in a VLAN with an interface IP of 100.65.0.2 at site A for instance? And then how do I route traffic to that VLAN so it knows to hit 100.65.0.1 on that port? 

Vince-Whirlwind
Honored Contributor

Re: How the &$)# do I make this work?

1. Yes. You should have a point-to-point link from your device to the MPLS router with .2/30 at your end.

 

2. The route on the device that has the 10.65.0.2 address points at the .1 address. So that device's routing table will know how to get there for all subnets it is routing for.

If you have a seperate device, then it needs to point to your device that is in the 10.65.0. subnet.

 

Maybe explain your topology a bit better - including device models.