WAN Routing
1748275 Members
3924 Online
108761 Solutions
New Discussion

Multi-Hop Static Routing

 
jon-h_2212
Occasional Visitor

Multi-Hop Static Routing

Im having issues routing traffic using static multi-hop routing. Due to political reasons I'm limited to static routing rather than a dynamic protocol. I've called HP tech support but they couldn't figure it out even though they agreed that it should work.

 

I currently have a topology of 3 seperate sites:

     Site 1  (10.1.0.0/16): 3800 - IP Address 10.1.1.1/24

     Site 2 (10.2.0.0/16): 8212zl - IP Address 10.2.1.1/24

     Site 3: (10.3.0.0/16): 8206zl - IP Address 10.3.1.1/24

 

There is a 1Gbps fiber link from Site 1 to Site 2. 

There is a 10Gbps fiber link from Site 2 to Site 3.

 

Site 1 can reach Site 2 but not Site 3.

Site 2 can reach both Site 1 and Site 3.

Site 3 can reach Site 2 but not Site 1.


Site 1 config:

Vlan 1
IP Address 10.1.1.1/24
Vlan 2
IP Address 10.1.2.1/24
Vlan 101 #connected to site 2 via fiber
IP Address 192.168.1.1/30
IP Routing
IP Route 10.2.0.0/16 192.168.1.2
IP Route 10.3.0.0/16 192.168.1.2


Site 2 config:

Vlan 1
IP Address 10.2.1.1/24
Vlan 2
IP Address 10.2.2.1/24
Vlan 101 #connected to site 1 via fiber
IP Address 192.168.1.2/30
Vlan 102 #connected to site 3 via fiber
IP Address 192.168.1.5/30

IP Routing
IP Route 10.1.0.0/16 192.168.1.1
IP Route 10.3.0.0/16 192.168.1.6


Site 3 config:

Vlan 1
IP Address 10.3.1.1/24
Vlan 2
IP Address 10.3.2.1/24
Vlan 102 #connected to site 2 via fiber
IP Address 192.168.1.6/30

IP Routing
IP Route 10.1.0.0/16 192.168.1.5
IP Route 10.2.0.0/16 192.168.1.5

 


Anyone have any ideas?

2 REPLIES 2
Vince-Whirlwind
Honored Contributor

Re: Multi-Hop Static Routing

Double-check all your subnet masks.

 

It all looks pretty simple and should work.

 

Do a "show ip rout" on each switch and show us what appears.

rpiersan
Member

Re: Multi-Hop Static Routing

when you do your ping tests you use source IP address of site to site networks (192.168.0.0), that are out of your static routing plan (10.1/2/3.0.0). Add 192.168.0.0 static routes or make extended pings.

 

Actually it's normal your behavior, routers do what are configured for, they don't have 192.168.0.0 reachability information