I am having issues routing across the vlans on this switch which is running in Layer 3 mode to a 10.100.4.0 subnet being handles by an asa 5505. I suspect this is also why I cannot hit the Windows DHCP server that sites out in 10.100.4.42
Presently I have one SF300-24 configured as such below.
Ports 1-2 are on VLAN 53 setup as access ports (10.100.53.0)
Ports 4-18 are on VLAN 54 setup as access ports (10.100.54.0)
Ports 19-24 are on VLAN 1 setup as trunk ports which connect to a different subnet @ 10.100.4.0 via Port 24 on this switch. Port 24 connects to an ASA-5505.
Under IPv4 Interface on the switch I have...
vlan 1 to 10.100.4.5 which is the ip of the switch and is where data is being routed over port 24 to the asa.
vlan 53 to 10.100.53.1 mask 255.255.255.0
vlan 54 to 10.100.54.1 mask 255.255.255.0
Under IPv4 Static Routers I have...
10.100.4.0/24 local
10.100.53.0/24 local
10.100.54.0/24 local
0.0.0.0/0 next hop 10.100.4.45 (ASA-5505 Gateway IP) remote static 1
Under DHCP Relay it is enabled and tried with and without option 82
DHCP Server IP Address is set to 10.100.4.42
For Now I am focusing on getting 10.100.54.0 subnet up on DHCP so
DHCP Relay Interface Table...
vlan1 10.100.4.5 (Which is working on the trunk ports 19-24)
vlan54 10.100.54.1 (which is not getting DHCP. A scope has been created on the server @ 10.100.4.42)
So from the 10.100.54.0 subnet I have a test machine living there that cannot get DHCP. If I static the workstation (10.100.54.251) it I can access the ASA gateway (I put a static route in there to route traffic back to the sf300 via 10.100.4.5 which is the ip I have assigned to the switch). I can also get to the internet and so forth so I think what I have on the ASA is good. However I am not able to access most other hosts on that 10.100.4.0 network.
Very strange! Any help is appreciated. I figure if I can resolve what is going on with the 10.100.54.0 subnet I can apply the same to the 10.100.53.0 which is setup identically.
-carlos
