HP 2920 and Sonicwall NSA 4500 - Weird Routing Issue

Just looking to see if there are any known issue's here.  Really odd one.  Was having an aging Enterasys stack replaced in a remote office with a HP 2920.  Site has a Sonicwall NSA 4500.  All my other sites have comparable hardware (NSA's, Procurves/HC3).  Note: No running-config below, as I did not grab before taking offline.

Quick Topology (for sake of simplicity, this setup as tried):

WAN VLAN (VLAND ID 10): 192.168.200.0/24
HP 2920 - 192.168.200.1
Sonicwall - 192.168.200.2
Cisco Router for MPLS - 192.168.200.254
Data VLAN:
192.168.201.0/24
VLAN interface IP on HP: 192.168.201.1

Devices on the Data VLAN point at 192.168.201.1 for gateway.
HP has
ip route 0.0.0.0 0.0.0.0 192.168.200.2
ip route x.x.x.x 255.255.255.0 192.168.200.254 (where x.x.x.x is the remote subnets across my MPLS)
IP routing is enabled.
All tagging is assumed correct.

My end users cannot reach the internet.  They can reach anything that is on a separate subnets* on the HP.  They can traverse the MPLS to other sites via the 192.168.200.254 gateway.  So we are routing on the HP, but not to the Sonicwall?

Sonicwall does have the proper return routes for the subnets, pointing back at 192.168.200.1  (ie, 192.168.201.0/24 uses 192.168.200.1).  Also, the HP has the same IP as the old Enterasys.  

Some oddities:
Reboots of the HP and sonicwall will return internet access for a short period
Odd entry in the HP's arp table :
192.168.201.145  000000-000000
(with no port)
LVL 1
JamesonJendreasAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mjhangiani2Commented:
I would suggest that you confirm that the switch port that the Sonicwall is connected to is in vlan 10.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JamesonJendreasAuthor Commented:
Yeah, the uplink is in a port that is untagged in VLAN 10.
mjhangiani2Commented:
Do you see the mac address for 192.168.200.1 on the Sonicwall and the mac address for 192.168.200.2 on the HP? If yes can you confirm that the MAC addresses are correct. Also ensure that Proxy-arp is disabled on the interfaces of the SOnic-wall, HP and Cisco on vlan 10
Benjamin Van DitmarsSr Network EngineerCommented:
did you add a route in the sonicwall for the way back like

192.168.201.0/24 gw 192.168.200.1

else the firewall doesn't know the way back to 192.168.201.0 because this network is not know.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Switches / Hubs

From novice to tech pro — start learning today.