Multiple Default route & Symantec Ghost in vlan

[Ashok K Gurung]

Hi

we now have two wan connection(Point to point and IPSEC VPN) between offices so we were thinking to utilze both of them by following methods

We are thinking to do following
Our core switch will forward traffic to different link depending on their status. we currently have procurve 5308xl switch as a core switch. we read some where that this switch is not capable of providing policy base routing but we were wondering if there is a way to set two default gateway and set switch such way that if it doesn't detect on default gateway it should fall to second one.

we are also having some problem with Symantec ghost. we use ghost floppy disk to get the image from server but once we setup vlan it stoped working. it can not even get dhcp address, we also tried assigning static ip address for ghost client(we assign static ip address in floppy disk). if we bring client computer to vlan where all servers are everything works with out any problem.

We wondering if you any one of you could give us some advice.

Thank you

[daniel wright_1]

for the first one you really want to be using a dynamic routing protocol such as ospf, you could alternatively set up static routes with different costs, it will try and use the point to point, if t cant use that it will use the VPN.

the second problem, can any pcs on the vlan your using for ghosting connect to the ghost server or any other server on that vlan?

have you enabled inter vlan routing? you will need to set the gateway on all of the devices to the management address of the vlan they are on.

it could also be something to do with how the ghost client communicate with the server, if they use broadcasts or multicasts they wont be passed through the vlan, we use altiris for our imaging and there is an option to use specific ports instead of broadcast and multicasts, there should be a similar option in ghost.

to get an IP address on the other vlan you will need to setup the dhcp-helper command.

[Joel Belizario]

On a side note you may want to enable IGMP in those client VLANs if you haven't done so already.

[Ashok K Gurung]

Hi

Thanks for the reply

we tried adding second default static gateway, we are not quite sure exact command to add gateway address with different cost. we will appreciate if you could help us our here. we will deffinately investigate more in using dynamic route.

In regards to symantec ghost and vlan, all our vlans are working without any problem, they can get ip address from server, connect to server so on as long as they are using windows.

We do not use ghost server, we just have one server that has all the images for workstations and we use network boot floppy which is created by ghost. All it does is it gets ip address and map drive to share folder in server and we run ghost command to download images, we are doing this manually.

we haven't enabled igmp, we will try enabling and see that helps.

Thank you

[OLARU Dan]

Add a second ip-helper statement to each VLAN interface that points to the IP of the image server. It works on Cisco IOS - should work in the ProCurve firmware, too.

[Ashok K Gurung]

Hi Thanks for the reply

Now we also set ip helper address for image server but still same problem. Problem we are having at first place is we are not able to get IP address from DHCP server itself.

We can get ip address when we boot windows client though? we also found out today that even if we put client computer and image server in same vlan we can only connect one client at a time. if we run another computer with network boot disk, it gives us that ip address is already assigned to some other client.

Looks like we are going to strugle bit here.

Thank you again

[Ashok K Gurung]

Hi Guys

We finally found the reason behind our symantec problem, it was DHCP-Snooping function that was blocking whole thing. we disabled it, whole ghosting thing works like charm.

We wish there was some better way of handling this as DHCP-Snooping being one of the security feature we would like them to be on. for the time being we have made a decision that this remains off at the time of imaging and will on once we finish with imaging.

Thank you again

[daniel wright_1]

from what i remember, pxe uses bootp instead of dhcp and dhcp snooping blocks bootp, even if its to an allowed dhcp server, i was going to implement dhcp snooping but found loads of people having problems with pxe and dhcp snooping.

[Ashok K Gurung]

thanks guys for all those reply