| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 111964 | 2010-08-18 11:23:00 | PXE Boot across VLANs | jwil1 (65) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1129238 | 2010-08-18 11:23:00 | Hi all, At work we have just implemented a new VLAN setup but have discovered a couple of problems. One of which is that we can't PXE boot off the network when the PXE server is on a different VLAN to the client. It works fine if they are on the same VLAN. :help: |
jwil1 (65) | ||
| 1129239 | 2010-08-18 11:33:00 | (My response is from thinking you have a router with sub-interfaces setup) There should be some way on the router to allow that kind of traffic to traverse the vlans. (Wow 10:30 at night and I used a big word right, I think) |
nedkelly (9059) | ||
| 1129240 | 2010-08-18 13:33:00 | Hi all, At work we have just implemented a new VLAN setup but have discovered a couple of problems. One of which is that we can't PXE boot off the network when the PXE server is on a different VLAN to the client. It works fine if they are on the same VLAN. :help:VLANS are designed to logically split a single switched network into several completely isolated networks at layer 2. If the PXE server is on a different VLAN, then as far as the client is concerned it might as well not exist. If you want to make PXE available on other VLANs, then you will need to configure your router to pass BOOTP/DHCP/TFTP traffic across VLANs to / from the PXE server, as Nedkelly notes above. Alternatively, you can set the PXE server up for layer 2 multihoming - although this isn't really a good idea, as it adds another potential security hole and needlessly complicates your network topology. Getting the router to manage this is a better solution. Note that unless a particular resource is visible via the router, your clients will not be able to access that resource unless it's connected to the same VLAN. This applies to *every* piece of equipment connected to your network. It's also worth pointing out the obvious here - all traffic to / from VLANs other than the one the client is connected to will need to go via the router, so unless you're not doing much inter-VLAN communication your router could easily become a major bottleneck. |
Erayd (23) | ||
| 1129241 | 2010-08-18 21:29:00 | Hi all, At work we have just implemented a new VLAN setup but have discovered a couple of problems. One of which is that we can't PXE boot off the network when the PXE server is on a different VLAN to the client. It works fine if they are on the same VLAN. :help: VLAN for Virtual hosts?.....will yes that is correct, a virtual LAN means a separate network from the host network, device are not supposed to talk across VLANs! |
SolMiester (139) | ||
| 1129242 | 2010-08-18 21:50:00 | But a router can be set up to allow them to, sol | nedkelly (9059) | ||
| 1129243 | 2010-08-18 21:52:00 | But a router can be set up to allow them to, sol Yes, I didnt say you cant!.....is the OP talking a switch or router |
SolMiester (139) | ||
| 1129244 | 2010-08-19 03:15:00 | Yes, I didnt say you cant!.....is the OP talking a switch or router VLANs implies that there is at least one switch involved, and any setup that expects stuff to talk across VLANs should have a router. If the OP doesn't have both I'd be very surprised. :pf1mobmini: |
Erayd (23) | ||
| 1 | |||||