Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Gateway Routing - multiple gateways

Posted on 2006-11-02
12
808 Views
Last Modified: 2013-12-12
Current HQ Subnet:  172.16.77.XXX
Company A Gateway Router: 172.16.77.1
Company B Gateway Router: 172.16.77.245
Remote subnet for Company B:  172.16.60.XXX  [Where I want to route the 172.16.60.XXX traffic to]

We are going to be changing our WAN providers.  We use Company A right now and our default gateway points through their router.

We have just brought in Company B's router and it is supposed to connect to our first MPLS site [the Remote Subnet above]

We are going to be using the same subnets for existing sites for obvious reasons, however I need to make sure that traffic routing to the new site is sent and routed to that site using Company B's router.

I tried adding a static IP route 172.16.60.0 255.255.255.0 172.16.77.245  to the routing table on Company A's router.  However if I perform a trace route 172.16.60.1 off of Company A's router it traverses the gateway and heads out our internet router.

We use EIGRP.

How can I route the 172.16.60.XXX traffic through the Company B router and vice versa?

Thank You!

0
Comment
Question by:EnclosAdmin
  • 5
  • 5
12 Comments
 
LVL 50

Expert Comment

by:Don Johnston
ID: 17874638
I'm not sure I understand what you're doing.

Are company A and B connected to each other or is A and B different providers?

Can you post a topology diagram?
0
 
LVL 2

Author Comment

by:EnclosAdmin
ID: 17875515
Widgets is the Customer who has been using Customer A as a WAN provider for 6 years.

Widgets is switching to company B slowly.  So Widgets has opened a new office in Utah and it will be the first office conected to Widgets by Company B.  Of course Company B has to place a Router at Widgets HQ office for connectivity to the Utah site.

So now both WAN providers have routers at Widgets HQ location.  What that means for users at Widgets is that they now have two distinct gateways.  They will need to route traffic between the sites.  So all of the original users still on Company A's WAN need to get to resources in Company B's WAN and vice versa.

We use EIGRP, so everybody in the Widget company has a default gateway that brings them back to the Widget HQ office.  I can create a static route to the Company B router.  A traceroute shows that the traffic routed to Utah does indeed hit the Company B router in Widgets HQ office but it then comes right back into the Wiget HQ office and tried heading out the internet.
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 17876156
>tried heading out the internet.

Where does the internet come in??? Do you have a seperate router somewhere that connects to the internet?

Are you sure a PVC has been established by Company B?
0
VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

 
LVL 2

Author Comment

by:EnclosAdmin
ID: 17876947
There are 5 Global T1's coming into Widgets and now a new Broadwing T1.

It only complicates the issue to add them.  They are internet T's and a PRI for DID and caller ID.  However the problem isn't any of them, it is routing to the Company B router through Widgets HQ site to the site in Utah.  Obviously traffic returned from the Company B router that never made it to Utah in the first place will traverse towards the internet because the router will see that as traffic that has no route and route it to the internet.

The Company B router can PING its Utah router and the Utah router can PING COmpany B's router in the HQ office.  I can route the traffic from any Company A router to the Company B HQ router but the traffic fails to traverse through that router to the Utah site.
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 17877663
Can you post the routing table for the HQ and Utah routers?
0
 
LVL 2

Author Comment

by:EnclosAdmin
ID: 17885173
Company B's EAGAN router:
EAGAN_RTR#sho ip ro
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 10.0.132.41 to network 0.0.0.0

     172.16.0.0/24 is subnetted, 1 subnets
C       172.16.77.0 is directly connected, FastEthernet0/0
     172.26.0.0/32 is subnetted, 1 subnets
C       172.26.77.245 is directly connected, Loopback0
     10.0.0.0/30 is subnetted, 1 subnets
C       10.0.132.40 is directly connected, Serial0/0/0:0.1
S*   0.0.0.0/0 [1/0] via 10.0.132.41

Company B's UTAH Router:
ST_GEORGE_RTR#sho ip ro
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 10.0.132.21 to network 0.0.0.0

     172.16.0.0/24 is subnetted, 1 subnets
C       172.16.60.0 is directly connected, FastEthernet0/0
     172.26.0.0/32 is subnetted, 1 subnets
C       172.26.60.1 is directly connected, Loopback0
     10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C       10.0.132.20/30 is directly connected, Serial0/0/0
C       10.0.132.21/32 is directly connected, Serial0/0/0
S*   0.0.0.0/0 [1/0] via 10.0.132.21

Company A Catalyst 4506 switch:
[This has a static IP route to the Company B EAGAN router for UTAH's SUBNET]
MSPSR1#sho ip ro
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 172.16.200.2 to network 0.0.0.0

S    172.17.0.0/16 [1/0] via 172.16.200.2
     172.16.0.0/16 is variably subnetted, 28 subnets, 3 masks
D       172.16.254.64/30 [90/21024256] via 172.16.77.253, 4d04h, Vlan77
D       172.16.254.68/30 [90/11024128] via 172.16.77.253, 4d04h, Vlan77
C       172.16.177.0/24 is directly connected, Vlan177
D       172.16.254.80/30 [90/7178752] via 172.16.77.253, 3d05h, Vlan77
D       172.16.254.84/30 [90/2178816] via 172.16.77.253, 4d04h, Vlan77
D       172.16.254.100/30 [90/2178816] via 172.16.77.253, 4d04h, Vlan77
D       172.16.254.108/30 [90/2178816] via 172.16.77.253, 4d04h, Vlan77
D       172.16.254.116/30 [90/11024128] via 172.16.77.253, 4d04h, Vlan77
D       172.16.250.4/30 [90/17800192] via 172.16.200.105, 7w0d, Vlan200
D       172.16.250.8/30 [90/16316672] via 172.16.200.105, 7w0d, Vlan200
D       172.16.254.28/30 [90/2178816] via 172.16.77.253, 4d04h, Vlan77
D       172.16.217.0/24 [90/2181376] via 172.16.77.253, 4d04h, Vlan77
D       172.16.254.40/30 [90/2178816] via 172.16.77.253, 4d04h, Vlan77
D       172.16.214.0/24 [90/2181376] via 172.16.77.253, 4d04h, Vlan77
C       172.16.200.0/24 is directly connected, Vlan200
D       172.16.254.56/30 [90/2178816] via 172.16.77.253, 4d04h, Vlan77
S       172.16.60.0/24 [1/0] via 172.16.77.245
D       172.16.55.0/24 [90/2181376] via 172.16.77.253, 4d04h, Vlan77
D       172.16.254.132/30 [90/5512192] via 172.16.77.253, 4d04h, Vlan77
D       172.16.195.176/32 [90/24820992] via 172.16.77.11, 04:06:59, Vlan77
D       172.16.108.0/24 [90/2181376] via 172.16.77.253, 4d04h, Vlan77
D       172.16.106.0/24 [90/2181376] via 172.16.77.253, 4d04h, Vlan77
D       172.16.107.0/24 [90/5514752] via 172.16.77.253, 19:37:36, Vlan77
D       172.16.101.0/24 [90/2181376] via 172.16.77.253, 3d02h, Vlan77
D       172.16.102.0/24 [90/5514752] via 172.16.77.253, 4d04h, Vlan77
D       172.16.103.0/24 [90/7181312] via 172.16.77.253, 3d05h, Vlan77
C       172.16.77.0/24 is directly connected, Vlan77
D       172.16.66.0/24 [90/5512192] via 172.16.77.253, 2d12h, Vlan77
S    172.21.0.0/16 [1/0] via 172.16.200.21
S    172.22.0.0/16 [1/0] via 172.16.200.105
     172.26.0.0/32 is subnetted, 11 subnets
D       172.26.77.254 [90/130816] via 172.16.77.254, 7w0d, Vlan77
D       172.26.77.253 [90/130816] via 172.16.77.253, 4d04h, Vlan77
D       172.26.214.1 [90/2306816] via 172.16.77.253, 4d04h, Vlan77
D       172.26.217.1 [90/2306816] via 172.16.77.253, 4d04h, Vlan77
D       172.26.55.1 [90/2306816] via 172.16.77.253, 4d04h, Vlan77
D       172.26.103.1 [90/7306752] via 172.16.77.253, 3d05h, Vlan77
D       172.26.102.1 [90/5640192] via 172.16.77.253, 4d04h, Vlan77
D       172.26.101.1 [90/2306816] via 172.16.77.253, 4d04h, Vlan77
D       172.26.108.1 [90/2306816] via 172.16.77.253, 4d04h, Vlan77
D       172.26.107.1 [90/5640192] via 172.16.77.253, 19:37:36, Vlan77
D       172.26.106.1 [90/2306816] via 172.16.77.253, 4d04h, Vlan77
     10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks
D       10.16.107.0/24 [90/5514752] via 172.16.77.253, 19:37:36, Vlan77
D       10.16.102.0/24 [90/5514752] via 172.16.77.253, 4d04h, Vlan77
D       10.16.103.0/24 [90/7181312] via 172.16.77.253, 3d05h, Vlan77
D       10.26.177.9/32 [90/130816] via 10.16.177.9, 7w0d, Vlan377
D       10.26.177.8/32 [90/130816] via 10.16.177.8, 7w0d, Vlan377
C       10.16.177.0/24 is directly connected, Vlan377
S    198.17.220.0/24 [1/0] via 172.16.200.22
S*   0.0.0.0/0 [1/0] via 172.16.200.2
S    192.168.0.0/16 [1/0] via 172.16.200.2

Company A Frame Relay Router
[This also has a Static IP Route to Company B's EAGAN router for UTAH's subnet]
MSPRT1#sho ip ro
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is 172.16.77.1 to network 0.0.0.0

D EX 172.17.0.0/16 [170/28416] via 172.16.77.1, 4d04h, FastEthernet0/0.77
     172.16.0.0/16 is variably subnetted, 28 subnets, 3 masks
D       172.16.254.64/30 [90/21024000] via 172.16.254.58, 1w2d, Serial0/0.101
D       172.16.254.68/30 [90/11023872] via 172.16.254.42, 2w0d, Serial0/0.106
                         [90/11023872] via 172.16.254.30, 2w0d, Serial1/0.155
D       172.16.177.0/24 [90/28416] via 172.16.77.1, 4d04h, FastEthernet0/0.77
C       172.16.254.80/30 is directly connected, Serial0/0.160
C       172.16.254.84/30 is directly connected, Serial0/0.114
C       172.16.254.100/30 is directly connected, Serial0/0.117
C       172.16.254.108/30 is directly connected, Serial1/0.162
D       172.16.254.116/30
           [90/11023872] via 172.16.254.102, 2w0d, Serial0/0.117
D       172.16.250.4/30
           [90/17802752] via 172.16.77.1, 4d04h, FastEthernet0/0.77
D       172.16.250.8/30
           [90/16319232] via 172.16.77.1, 4d04h, FastEthernet0/0.77
C       172.16.254.28/30 is directly connected, Serial1/0.155
D       172.16.217.0/24 [90/2181120] via 172.16.254.102, 2w3d, Serial0/0.117
C       172.16.254.40/30 is directly connected, Serial0/0.106
D       172.16.214.0/24 [90/2181120] via 172.16.254.86, 2w0d, Serial0/0.114
D       172.16.200.0/24 [90/28416] via 172.16.77.1, 4d04h, FastEthernet0/0.77
C       172.16.254.56/30 is directly connected, Serial0/0.101
S       172.16.60.0/24 [1/0] via 172.16.77.245
D       172.16.55.0/24 [90/2181120] via 172.16.254.30, 2w0d, Serial1/0.155
C       172.16.254.132/30 is directly connected, Serial1/0.163
D       172.16.195.176/32
           [90/24823296] via 172.16.77.11, 04:08:50, FastEthernet0/0.77
D       172.16.108.0/24 [90/2181120] via 172.16.254.110, 2w0d, Serial1/0.162
D       172.16.106.0/24 [90/2181120] via 172.16.254.42, 2w0d, Serial0/0.106
D       172.16.107.0/24 [90/5514496] via 172.16.66.2, 19:39:27, Serial0/0.161
D       172.16.101.0/24 [90/2181120] via 172.16.254.58, 3d02h, Serial0/0.101
D       172.16.102.0/24 [90/5514496] via 172.16.254.134, 2w0d, Serial1/0.163
D       172.16.103.0/24 [90/7181056] via 172.16.254.82, 3d05h, Serial0/0.160
C       172.16.77.0/24 is directly connected, FastEthernet0/0.77
C       172.16.66.0/24 is directly connected, Serial0/0.161
D EX 172.21.0.0/16 [170/28416] via 172.16.77.1, 4d04h, FastEthernet0/0.77
D EX 172.22.0.0/16 [170/28416] via 172.16.77.1, 4d04h, FastEthernet0/0.77
     172.26.0.0/32 is subnetted, 11 subnets
D       172.26.77.254 [90/156160] via 172.16.77.254, 4d04h, FastEthernet0/0.77
C       172.26.77.253 is directly connected, Loopback0
D       172.26.214.1 [90/2306560] via 172.16.254.86, 2w0d, Serial0/0.114
D       172.26.217.1 [90/2306560] via 172.16.254.102, 2w3d, Serial0/0.117
D       172.26.55.1 [90/2306560] via 172.16.254.30, 2w0d, Serial1/0.155
D       172.26.103.1 [90/7306496] via 172.16.254.82, 3d05h, Serial0/0.160
D       172.26.102.1 [90/5639936] via 172.16.254.134, 2w0d, Serial1/0.163
D       172.26.101.1 [90/2306560] via 172.16.254.58, 1w2d, Serial0/0.101
D       172.26.108.1 [90/2306560] via 172.16.254.110, 2w0d, Serial1/0.162
D       172.26.107.1 [90/5639936] via 172.16.66.2, 19:39:27, Serial0/0.161
D       172.26.106.1 [90/2306560] via 172.16.254.42, 2w0d, Serial0/0.106
     10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks
D       10.16.107.0/24 [90/5514496] via 172.16.66.2, 19:39:27, Serial0/0.161
D       10.16.102.0/24 [90/5514496] via 172.16.254.134, 2w0d, Serial1/0.163
D       10.16.103.0/24 [90/7181056] via 172.16.254.82, 3d05h, Serial0/0.160
D       10.26.177.9/32 [90/156416] via 172.16.77.1, 4d04h, FastEthernet0/0.77
D       10.26.177.8/32 [90/156416] via 172.16.77.1, 4d04h, FastEthernet0/0.77
D       10.16.177.0/24 [90/28416] via 172.16.77.1, 4d04h, FastEthernet0/0.77
D EX 198.17.220.0/24 [170/28416] via 172.16.77.1, 4d04h, FastEthernet0/0.77
D*EX 0.0.0.0/0 [170/28416] via 172.16.77.1, 4d04h, FastEthernet0/0.77
D EX 192.168.0.0/16 [170/28416] via 172.16.77.1, 4d04h, FastEthernet0/0.77


So here's waht we get:

User if they are plugged into the Catalyst switch in EAGAN they can get to Utah's resources.  If they are not plugged into that switch they cannot get to Utah's resources.  The Company A Frame Relay Router can ping both of the Company B routers but nobody routing through that router can get there.

Utah users coming to Eagan from Company B's UTAH router can't get to anything on the Company A side.
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 17885710
I can't determine how your HQ and Utah sites are connected. There doesn't appear to be a common network between them.

Can you provide a topology diagram so I see how there four routers/switches are connected?
0
 
LVL 2

Author Comment

by:EnclosAdmin
ID: 17885875
How can I post a diagram on this site?
0
 
LVL 50

Expert Comment

by:Don Johnston
ID: 17886270
Here's one way:

F/R router                                                         4500
     |                                                                     |
----------------- HQ----------------------------Utah------------------  
172.16.1.0           ^                              ^           172.16.2.0
                           |                               |
                    172.16.3.1                  172.16.3.2
0
 
LVL 2

Author Comment

by:EnclosAdmin
ID: 17931576
Problem solved:

I set up redistribution for EIGRP from company A to OSPF on Company B - and redistribution for OSPF from Company B to EIGRP on Company A.

Company B wanted to utilize static IP's and were reluctant to allow a routing protocol.  They have since seen the light and have allowed OSPF.  Not as good as EIGRP but vastly superior and less complicated than static routing with so many subnets involved.

Thank you to those that had tried to figure this out.
0
 

Accepted Solution

by:
CetusMOD earned 0 total points
ID: 18059337
Closed, 500 points refunded.
CetusMOD
Community Support Moderator
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Cable Modem Provisioning from DPoE compliant server  This Article is to support CMTS administrators to provide an overview of DOCSIS compliance configuration file, and to provision a cable modem located at customer place from a Back office serve…
Sometimes you have to pull out old tricks to get a new firewall to work… While we were installing a new Sonicwall at a customers site we found that sites they were able to visit before were not working.  It seemed random and we could not understa…
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question