asked on Can not ping from one Sonicwall to another through HP 1920-16g switch on different subnets
Hello all,
I am not quite sure what is going on here. We have our production NSA 2600 Sonicwall (10.10.0.0 network) and a Sonicwall TZ-215 (10.10.1.0 network), I have created the static route using the NSA of 10.10.1.0 with a next hop of 10.10.0.179 (the 1920's IP), then, on the the 1920 I have 2 static routes, one is 10.10.0.0 with next hop being 10.10.0.103 (the NSA's IP) and one of 10.10.1.0 with next hop being 10.10.1.1 (TZ 215's IP), then in the TZ215 I have a route of 10.10.0.0 with a next hop of 10.10.0.179 (the 1920's IP). I am getting no communication from the TZ-215 to anything within the 10.10.0.0. network, nor can I ping the directly attached 1920 at 10.10.0.179.
The NSA can, of course, communicate fine with the 1920, and everything else in the network, but can not get to the 10.10.1.0 network.
The TZ-215 will be going up to our other location out of state and will be communicating via MPLS eventually (soon), but I wanted to test this communication out here first on a more simple level, but can not seem to get even that to work.
Anyone have any ideas of what I could be missing?
Thanks!
I am not quite sure what is going on here. We have our production NSA 2600 Sonicwall (10.10.0.0 network) and a Sonicwall TZ-215 (10.10.1.0 network), I have created the static route using the NSA of 10.10.1.0 with a next hop of 10.10.0.179 (the 1920's IP), then, on the the 1920 I have 2 static routes, one is 10.10.0.0 with next hop being 10.10.0.103 (the NSA's IP) and one of 10.10.1.0 with next hop being 10.10.1.1 (TZ 215's IP), then in the TZ215 I have a route of 10.10.0.0 with a next hop of 10.10.0.179 (the 1920's IP). I am getting no communication from the TZ-215 to anything within the 10.10.0.0. network, nor can I ping the directly attached 1920 at 10.10.0.179.
The NSA can, of course, communicate fine with the 1920, and everything else in the network, but can not get to the 10.10.1.0 network.
The TZ-215 will be going up to our other location out of state and will be communicating via MPLS eventually (soon), but I wanted to test this communication out here first on a more simple level, but can not seem to get even that to work.
Anyone have any ideas of what I could be missing?
Thanks!
Switches / HubsRoutersNetworking
Last Comment
MostHated
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
The TZ-215 currently is only connected via X0 for lan only testing, but from the 1920, I attempted to ping our X1 IP address of the production NSA and it came up with the error of " Error: Ping: Unknown host ping xxx.xxx.xxx.xxx" (redacted of course, for security).
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
The X0 Lan interface of the NSA is in the 10.10.0.0 (10.10.0.103) subnet (X1 is WAN for Sonicwalls), as well as the primary IP of the 1920 (10.10.0.179), those can communicate just fine and everything has been working with no issues. I simply took our older TZ-215 that we replace with the NSA and changed its X0 lan IP to 10.10.1.1 and am trying to communicate entirely internally with these devices at the current moment, but the static routes I have between the 3 devices is not allowing for communication from the NSA through the 1920 to the TZ-215 and vice versa. Not even from the 1920, which is directly connected to the lan port of the TZ-215 will communicate.
ASKER
@Etienne Lau, I get what you meant and finally got it figure out, thank you much. I created a vlan on the 1920 and changed one of the port IP's to be 10.10.1.2 and then on the TZ215 changed the next hop to be that IP instead of the 10.10.0.179, then because of the routes I had everything started working perfect!
Thanks a bunch for the help.
Thanks a bunch for the help.