Dell Layer 3 switch - cant change out Firewall/Gateway
I am working on removing a Watchguard firewall that is acting as a default gateway & firewall for a network. It is getting replaced by a Cyberoam firewall.
I am unable to gain access to the WatchGuard's GUI/CLI as the person who supported this network before me is unwilling to give any of the credentials to the network owner or me.
Here is what I know for certain:
The WatchGuards IP is 10.1.0.254
It acts as the default gateway for all devices on all the VLANS, without it there is no internet connectivity
I believe its mask is /25 (judging by how one of the VLANs is setup)
The layer 3 switches have a default route of 0.0.0.0/0 via 10.1.0.254
The WatchGuard receives the incoming WAN connection via a bridged ISP cable modem
From the WatchGuard the next hop is a Dell Layer 3 switch's Gigabit "Stack" port
Here is the problem:
I configured the cyberoam's WAN interface to work with the public IP range which I have confirmed with the ISP. I configured the cyberoams LAN interface to be 10.1.0.254 /25. I removed the WatchGuard and put the Cyberoam in its place. At this point, the Cyberoam (with its 10.1.0.254 LAN interface) does not show up on the network. Ping'ing 10.1.0.254 from a workstation yields nothing. Pinging it from a L2 switch yields nothing. If I plug my laptop directly into the Cyberoams LAN port and configure my laptop to use it as my gateway I am able to A) ping the cyberoam and B) get out to the internet. The issue appears to be with the next hop (the Dell L3 switch).
Putting the WatchGuard back in place and powering it on restores connectivity. I have triple checked the gateway settings on the workstations, switches and the Cyberoam. I have manipulated settings on the cyberoam and the Dell L3 switch where possible, but I have been unable to resolve this.
I am assuming there is a setting/config in the L3 switch that I am not considering that is killing the incoming connection. Does anyone have any ideas?
I am unable to gain access to the WatchGuard's GUI/CLI as the person who supported this network before me is unwilling to give any of the credentials to the network owner or me.
Here is what I know for certain:
The WatchGuards IP is 10.1.0.254
It acts as the default gateway for all devices on all the VLANS, without it there is no internet connectivity
I believe its mask is /25 (judging by how one of the VLANs is setup)
The layer 3 switches have a default route of 0.0.0.0/0 via 10.1.0.254
The WatchGuard receives the incoming WAN connection via a bridged ISP cable modem
From the WatchGuard the next hop is a Dell Layer 3 switch's Gigabit "Stack" port
Here is the problem:
I configured the cyberoam's WAN interface to work with the public IP range which I have confirmed with the ISP. I configured the cyberoams LAN interface to be 10.1.0.254 /25. I removed the WatchGuard and put the Cyberoam in its place. At this point, the Cyberoam (with its 10.1.0.254 LAN interface) does not show up on the network. Ping'ing 10.1.0.254 from a workstation yields nothing. Pinging it from a L2 switch yields nothing. If I plug my laptop directly into the Cyberoams LAN port and configure my laptop to use it as my gateway I am able to A) ping the cyberoam and B) get out to the internet. The issue appears to be with the next hop (the Dell L3 switch).
Putting the WatchGuard back in place and powering it on restores connectivity. I have triple checked the gateway settings on the workstations, switches and the Cyberoam. I have manipulated settings on the cyberoam and the Dell L3 switch where possible, but I have been unable to resolve this.
I am assuming there is a setting/config in the L3 switch that I am not considering that is killing the incoming connection. Does anyone have any ideas?
Aaron Tomosky
What ip addresses do workstations get? If they are not in that subnet, they have a different gateway. Each subnet/vlan will have its own gateway in that vlan.
ASKER
My logic was that the current firewall has an IP address of 10.1.0.254 /25 in VLAN 999, so I thought I could configure the new firewall with identical settings and have it "plug + Play" essentially.
Is this not how it should work?
Is this not how it should work?
It's part of how it should work. You need to identify ALL the subnets and gateway addresses for all the interfaces on the router. To exit a subnet, you go out the gateway for that subnet.
Please post the Dell switch config
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Vendor resolved issue