Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
Community Member

Trying to PXE across VLANS

I'm trying to use Novell ZENworks Configuration Management to image machines I have on my campus.  The optimum setup for this is to have the clients PXE boot to check the server for work that needs to be done.  When I try to set this up I can only get it to work on the same VLAN.

Here is my setup:

We have a Cisco Cat. 6509 that does all our VLAN routing and our DHCP.  The PXE server is on VLAN 18 with an IP of it is running on a VMware host.  The VMware host is on VLAN 10 with a management IP of  The port this is plugged into is configured as follows:

description VM Netowrk
switchport trunk encapsulation dot1q
switchport trunk native vlan 10
switchport mode trunk
no ip address

The VMware host is configured to put the VMs on VLAN 18.  I'm not positive that this is the best method or configuration, but I have multiple servers setup up this way and  connectivity is working fine.  Please let me know if there is a better way, I do not claim to be an expert in VLANs or VMware in any way.  I have the helper-address set on the VLAN I'm trying to PXE  (VLAN 12), it is configured with (PXE server).  Here is the DHCP pool and VLAN interface configs.

ip dhcp pool VLAN12.IT.DATA
   netbios-node-type h-node
   lease 3

interface Vlan12

description IT DATA
ip address
ip helper-address
ip dhcp relay information trusted
ip pim sparse-dense-mode

If I put in  option 66 and 67 on the dhcp pool on the Cisco, I can PXE my machine,  but I get a problem with the imaging server address coming up as  I found Novell documentation which tells me option 66/67 are not  supported with the version of ZENworks I'm using.  If I remove these options, PXE tells me no boot  file specified.  I have set ip forward-protocol udp 67/68, per Novell instructions, on  the 6509.  If I move the same machine to VLAN 18, everything works fine.

Community Member

Re: Trying to PXE across VLANS

I rebuilt this DHCP scope on a Windows server, put in the correct helper address and it worked fine.  It must have something to do with running the 6509 as a DHCP server.

CreatePlease to create content