The static route on your laptop is to tell it how to get to the other subnets. Since those subnets are not connected via your Nighthawk, and your Nighthawk is your default gateway, you have to tell your client (source) how it can reach those networks. For devices in VLAN 2 and 3, they're using the ICX as the gateway. The ICX knows what networks are directly connected and can route them; then anything that does not match a direct connected network is sent to the ICX's default gateway, the Nighthawk.Hello LR, trying to understand something. I put the static route in my laptop and can now ping devices on VLAN 2, VLAN 3 and those VLANs can ping VLAN 1. Also, VLAN 2 and VLAN 3 can ping between themselves, however, they could do this before the static route was added.
What I am trying to figure out is why the static route would go on the source device and not the device doing the routing, i.e. Nighthawk or the ICX 6450?
In your specific case, this is required because the Nighthawk and the ICX are in the same subnet.
If your Nighthawk had the ability to do static routes, the more enterprise correct way of setting this up would be
- each VLAN has its own subnet (you have this)
- each VLAN has a VE with IP
- a dedicated VLAN between the ICX and firewall; this VLAN has its own subnet
- ICX uses firewall VLAN IP as its upstream gateway
- The firewall has reverse routes for each subnet using the ICX IP as its gateway