can't get sites to communicate

please see diagram. We have a remote network (10.24.2.0/24) which needs to speak to corporate (172.16.0.0/16). What do we need to do? why isnt this working. I have the following static routes:

static route for BRDG
172.16.0.0   255.255.0.0   10.240.2.2

static route for ESNG
172.16.0.0   255.255.0.0   10.24.1.2

static route in pix
10.24.2.0  255.255.255.0   10.24.1.1

I believe the wan technology is frame. There could be more than one router in between, but I think there is only one
scada.jpg
LVL 1
WERAracerAsked:
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.

that1guy15Commented:
The first thing i see is the ESNG router needs a route back to BRDG. ESNG has no clue how to return traffic to BRDG.

0
grimkinCommented:
The static routes seem fine but the router(s) in the middle need to know about these networks (10.24.2.0/24 and 172.16.0.0/16) as well otherwise it will simply drop the packets or forward them to its own default gateway, wherever that might be.

Are you running RIP / OSPF or how are these routes to be advertised to the inbetween router(s)?
0
WERAracerAuthor Commented:
thatguy, I didnt include the other static routes. But ESNG has full connectivity back to BRDG. THe route looks like this  10.24.0.0  255.255.0.0   10..240.1.2

grimkin, since we do not own the router(s) in the middle, I relied on our service provider to enter the proper static routes. This is what they entered:

172.16.0.0   255.255.0.0    10.24.1.1   and it is not working

any ideas?

Thanks
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

that1guy15Commented:
Traceroute to the 172 network from the remote site let us know how far you can get.
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
WERAracerAuthor Commented:
here is the tracert. Keeps bouncing back and forth
scad.JPG
0
that1guy15Commented:
Your ESNG server is pointing a route to the 172 network back to 10.240.2.2.

Doulbe check your routes on that router for errors or post your "sh ip route" and we will take a look at it.
0
WERAracerAuthor Commented:
The ESNG router has this:

172.16.0.0   255.255.0.0   10.24.1.2
10.24.0.0 255.255.0.0   10.240.1.2
0
WERAracerAuthor Commented:
that traceroute is from BRDG by the way
0
that1guy15Commented:
Those routes are correct but you are having a routing loop (hence the traceroute going back and forth). Please post your "Sh ip route" or a cleaned up "sh run"
0
WERAracerAuthor Commented:
the routers we control for this network, are actually not cisco. They are verilink wansuite (aka big POS).  The routers in between are controlled by our service provider
0
that1guy15Commented:
Since the traceroute keep bouncing back and forth on ESNG this is were i think the problem is. Do you control this router?

If so could you post something showing all your routes?
0
WERAracerAuthor Commented:
the ESNG router we own . However, isn't this bouncing between the router in the middle and BRDG?  The address bouncing in the tracert is 10.240 , not 10.24
0
that1guy15Commented:
Oh yes you are correct, My mistake.

Yeah your traceroute (and traffic) is making it to the router in the middle. But it is bouncing it back. Do you control this router? This is the router with the routing loop.

Run a traceroute from the 172 network to the BRDG network 10.24 to verify this is were your issue is.
0
WERAracerAuthor Commented:
Yes I have our provider looking at this.   We do not manage that router
0
that1guy15Commented:
To verify this is were the trouble is Run a traceroute from the 172 network to the BRDG network 10.24
0
WERAracerAuthor Commented:
Tracing route to 10.24.2.102
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  172.16.14.1
  2     1 ms     1 ms     1 ms  172.17.1.31
  3     1 ms     1 ms     2 ms  [10.24.1.1
  4     8 ms     7 ms     7 ms  10.240.1.2
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *
0
that1guy15Commented:
Here are several things I am seeing:

Routes on ESNG:

172.16.0.0   255.255.0.0   10.24.1.2 <-this looks good
10.24.0.0 255.255.0.0   10.240.1.2 < --points both 10.24.1 and .2 to the 10.240.1.2 router which is the ISP router. Traffic can not get to the 10.24.1 network because it is sent back to the ISP.

This is an issue since the two subnets are on either side of the router. So split that route into two seperate routes on ESNG.

10.24.1.0 255.255.255.0   10.24.1.2 <-points routes to your f/w
10.24.2.0 255.255.255.0   10.240.1.2 <-points routes to the ISP

ISP route (per earlier post):

172.16.0.0   255.255.0.0    10.24.1.1   and it is not working

This route is pointing to the wrong interface on ESNG. Your ISP most likley has no idea how to get to this subnet. You need to have them change the route to the next hop address.

172.16.0.0   255.255.0.0    10.2401.1 <--this will point all traffic for this network to ESNG

Also your ISP will need a route to point traffic to the 10.24.2 network at your remote location.

10.24.2.0   255.255.255.0    10.240.2.1

This should correct your routing issues.
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
Routers

From novice to tech pro — start learning today.