Two hubs same organization routing table.

SOLVED
JamesMutie
Getting noticed

Two hubs same organization routing table.

Since hubs within the same organization peer to each other automatically, will this cause a problem with crushing spoke IP subnets in different networks? 

 

 

Lets say spoke 1 peering with Hub 1  doesn't  need to communicate with spoke 2 peering with Hub 2.  Spoke 2 has similar IP Subnet like spoke 1. Am suspecting spoke 1 return traffic from hub 1 might be send to hub 2  hence causing a blackhole. Is this case. ? if for example spoke 2 decides to advertise a more specific route to HUB2.

 

I  am designing  for  several Hubs in one organization and each hub has over 30 networks. And there is possibility of similar IP Subnets in some networks

1 ACCEPTED SOLUTION
cmr
Kind of a big deal
Kind of a big deal

@JamesMutie yes, if you have two sites that both use, for example, 192.168.0.0/24, then change one to use a different range like 10.12.3.0/24.

 

If you move to the 10. range you can create almost as many sites as you like as there are 255 /16 networks with easy subdivisions to /24 (where you have large sites) or over 65,000 /24 networks.

 

You don't need to move all, just the ones that overlap.

View solution in original post

3 REPLIES 3
cmr
Kind of a big deal
Kind of a big deal

There is an option to translate remote subnets to different ones in this case, but I'd always go for renumbering despite the initial pain.

JamesMutie
Getting noticed

@cmr  Thanks,

 

Renumbering is changing the IP addresses to different ones right.

cmr
Kind of a big deal
Kind of a big deal

@JamesMutie yes, if you have two sites that both use, for example, 192.168.0.0/24, then change one to use a different range like 10.12.3.0/24.

 

If you move to the 10. range you can create almost as many sites as you like as there are 255 /16 networks with easy subdivisions to /24 (where you have large sites) or over 65,000 /24 networks.

 

You don't need to move all, just the ones that overlap.

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