MX84 Static Route

JawD
Comes here often

MX84 Static Route

MX84

WAN: ISP
LAN: 192.168.10.0/24
IP: 192.168.10.254

 

Connected through network at a different building.

 

Router A
WAN: 192.168.10.145
LAN: 192.168.20.0/24
IP: 192.168.20.1

 

I need to SSH from 192.168.10.2 ---> 192.168.20.62

 

Static Route Setup?

Subnet = ?
Next Hop = ?

 

Configure on both MX and Router A?

 

14 Replies 14
PhilipDAth
Kind of a big deal
Kind of a big deal

To get to 192.168.20.0/24 you go via your ISP - correct?

 

Is your ISP providing a WAN service to you (so you can route to the remote subnet) or just Internet (so you'll need a VPN)?

JawD
Comes here often

Modem  ---> MX84 (192.168.10.254) ----> Switch ------(fiber to another building)------> Switch ---->

Router A (192.168.20.1) 

 

I can go to the other building and connect to the 192.168.20.0/24 and ping back to my server on 192.168.10.0/24.

 

Router A is another network for some tenants that use it for an AP for wifi. 

Adam
Kind of a big deal

When you traceroute from 192.168.10.2 ---> 192.168.20.62 where does it die?  From what you said you can get from .20 to .10 just fine so conceptually you should be able to go from .10 to .20 if there isn't a firewall rule or routing issue in between.  Your 192.168.10.2 device will go to its gateway and that gateway should determine or know the route to 192.168.20.x. 

Adam R MS | CISSP, CISM, VCP, MCITP, CCNP, ITILv3, CMNO
If this was helpful click the Kudo button below
If my reply solved your issue, please mark it as a solution.
JawD
Comes here often

Tracert from 192.168.10.2

 

C:\>tracert 192.168.20.62

Tracing route to 192.168.20.62 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.

5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.

_______________________________________________________

Routing

VLANsDisabled: use a single LAN Enabled
Routes
Subnet Type Details    
192.168.10.0/24Local VLAN
NameDefault
MX IP192.168.10.254
VLAN1
 
10.0.0.0/22Local VLAN
NamePublic
MX IP10.0.0.254
VLAN2
PolicySocial
 

Wondering if I need to set something up in here? ^

 

____________________________________________________________

 

 

Route table 

         Subnet                      Name          Type                        Next hop
 192.168.10.0/24DefaultLocal VLAN192.168.10.254
 176.16.1.0/24Client VPNClient VPNClient VPN
 10.0.0.0/22PublicLocal VLAN10.0.0.254
 0.0.0.0/0DefaultDefault WAN routeWAN uplink
Adam
Kind of a big deal

I'm not seeing any route to 192.168.20.0/24.  So you may have to 'Add a Static Route' so it knows how to get to that network.  You can also gain some insights from Security Appliance>Route Table

Adam R MS | CISSP, CISM, VCP, MCITP, CCNP, ITILv3, CMNO
If this was helpful click the Kudo button below
If my reply solved your issue, please mark it as a solution.
JawD
Comes here often

That's the problem I'm having. I tried adding in different static routes but clearly I don't know the correct way to route it. I've been searching through tons of forums but can't seem to find an example of the correct way I should be putting in the IP's with the MX84. I think I understand since I studied up on it last night but not sure how to interpret it into the MX84. 

 

I tried this early this morning. 

192.168.20.0/24Static Route
NameFN_Building
Next hop IP192.168.10.145
Activealways

 

I figured since the Router A is connected to the 192.168.10.0/24 sub with 192.168.10.145, then that should be a hop to it. But from there do I need to add another route. Is this even right? This is what confuses me... Did a tracert from that and got this.

 

C:\>tracert 192.168.20.62

Tracing route to 192.168.20.62 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.10.254
2 <1 ms * * 192.168.10.145
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.

JawD
Comes here often

Route table
 
  Subnet Name Type Next hop
 Green192.168.10.0/24DefaultLocal VLAN192.168.10.254
 Green176.16.1.0/24Client VPNClient VPNClient VPN
Red 192.168.20.0/24FNStatic Route192.168.10.145
Green 10.0.0.0/22PublicLocal VLAN10.0.0.254
Green 0.0.0.0/0DefaultDefault WAN routeWAN uplink
 
Adam
Kind of a big deal

Without having a better idea of your topology it's hard to say what specifically is the issue but I think we are on the right track.  Notice the route not functioning. 

 

Red 192.168.20.0/24FNStatic Route192.168.10.145
Adam R MS | CISSP, CISM, VCP, MCITP, CCNP, ITILv3, CMNO
If this was helpful click the Kudo button below
If my reply solved your issue, please mark it as a solution.
JawD
Comes here often

TOPOidea.JPG

JawD
Comes here often

Dumb switches

Adam
Kind of a big deal

Is Router A 192.168.20.1?  If so then you probably need a route from the MX 84 to route 192.168.20.0/24 to 192.168.20.1.  But before you do that you should test that the MX 84 can ping 192.168.20.1 if that is Router A's IP. 

Adam R MS | CISSP, CISM, VCP, MCITP, CCNP, ITILv3, CMNO
If this was helpful click the Kudo button below
If my reply solved your issue, please mark it as a solution.
JawD
Comes here often

Can't ping to 192.168.20.1.

 

Also if you set route 192.168.20.0/24 to 192.168.20.1 it throws an error.

 

 

"There were errors in saving this configuration:

  • The static route "FN" has an invalid next hop IP. The IP address 192.168.20.1 is not on a configured subnet."
Adam
Kind of a big deal

Is 192.168.20.1 the IP of Router A?  If so you'll need to start working on troubleshooting why the MX can't ping Router A.  Possibly some tracert's etc to see where it is failing. 

Adam R MS | CISSP, CISM, VCP, MCITP, CCNP, ITILv3, CMNO
If this was helpful click the Kudo button below
If my reply solved your issue, please mark it as a solution.
MRCUR
Kind of a big deal

Your MX needs an IP in the subnet of router A, or some link so you can create a static route. Right now you're trying to create a static route pointing to a gateway the MX doesn't have a route to. This is also why you can't ping router A from the MX as there is no L2 or L3 connectivity between those devices. 

MRCUR | CMNO #12
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels