?
Solved

Can not ping from one Sonicwall to another through HP 1920-16g switch on different subnets

Posted on 2016-10-07
5
Medium Priority
?
76 Views
Last Modified: 2016-10-10
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!
0
Comment
Question by:MostHated
[X]
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
  • 3
  • 2
5 Comments
 
LVL 3

Assisted Solution

by:Etienne Lau
Etienne Lau earned 2000 total points
ID: 41833915
Can you ping WAN interfaces of either firewall from the 1920?
0
 
LVL 1

Author Comment

by:MostHated
ID: 41833925
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).
0
 
LVL 3

Accepted Solution

by:
Etienne Lau earned 2000 total points
ID: 41833938
The X1 Interface of NSA and the 1920 Interface must be on the same subnet in order for any traffic to occur. For example:

X1: 10.10.2.2/30
1920 Interface: 10.10.2.3/30
0
 
LVL 1

Author Comment

by:MostHated
ID: 41833959
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.
0
 
LVL 1

Author Comment

by:MostHated
ID: 41837220
@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.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

During and after that shift to cloud, one area that still poses a struggle for many organizations is what to do with their department file shares.
This article is in regards to the Cisco QSFP-4SFP10G-CU1M cables, which are designed to uplink/downlink 40GB ports to 10GB SFP ports. I recently experienced this and found very little configuration documentation on how these are supposed to be confi…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Suggested Courses

777 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