I have 3 interfaces on a Juniper SSG-320M.
0/0 for the WAN
0/1 for 192.168.0.1/22
0/2 for 192.168.68.254/24
0/1 has an HP 4108gl as it's core switch.
192.168.0.3 is the DHCP/DNS server.
192.168.0.12 is the Windows Deployment Server (WDS).
0/2 has an HP 4104gl as it's core switch.
192.168.68.5 is the DHCP/DNS server.
I want clients on the 0/2 network to use the WDS server on the 0/1 network to image computers (pxe). Is there any way to make this happen? I can post in different category if that would be better. Thanks in advance!
Is there a route between 192.168.68.x and 192.168.0.x?
If so, add the following commands to the 192.168.68.x vlan:
ip forward-protocol udp 192.168.0.12 tftp
ip forward-protocol udp 192.168.0.12 4011
I have not tried this directly with WDS, but with SCCM which manages WDS.
I'm not sure... Does the route need to be setup on the core switch? Or on the Juniper? The commands you suggested do not work on the HP switches... Thoughts? Thanks!
Yes, the route needs to be on your core I think. I have a juniper vlaned system, and had to do this
I have a route setup on the core switch but it doesn't seem to be working...
ip route 0.0.0.0 0.0.0.0 192.168.68.254
ip route 192.168.0.0 255.255.252.0 192.168.0.1
The vlan (vlan 423) has a static IP of 192.168.0.72 255 255 252.0
If I statically assign an IP to a device and untag the port for the 423 vlan, I can ping 192.168.0.72 from that device. However, I cannot ping any other device on that vlan that resides on the other firewall interface (0/1). So I still can't communicate with 192.168.0.3... Does that make sense?
The 4100 series switches from a quick scan of their manuals seem to be edge switches, not core. I may be incorrect here, but routing does not seem to be a strong point which any core needs. Hence the forward-protocol commands I gave you will not work as you found.
When switches do not support PXE across VLANs, then you may need to revert back to DHCP options (minimum options 3, 6, 66, 67).
I am not familiar with the Juniper device at all, so TheScarfedOne may have better advice here. If you're seeing the gateway IP of the 192.168.0/22 to 192.168.0.72, then I think the route command needs to be ip route 192.168.0.0 255.255.252.0 192.168.0.72.