Clients have asked me to configure PXE boot across vlans for setting up a Symantec server for re-imaging the desktops and laptops. We have IP-helper address in place.can you please let me know how i can accomplish this. below is the running configuration of the SVI interface.
To my best knowledge, no further configuration shall be necessary. You have correctly configured the ip helper-address on the interface facing the client stations.
Assuming that at least one of the 10.1.108.1-3 is a DHCP server, the remaining configuration has to be performed on the DHCP server itself which must specify the TFTP server from which the PXE bootloader is to be downloaded, and the name of the file that shall be downloaded via TFTP.
Has the DHCP server been correctly configured? Is it possible to verify this configuration whether it works?
Using multicasts in Symantec Ghost has been problematic.
Most issues relate to the fact that the DOS IP driver used by older Symantec Ghost versions did not send proper IGMP Membership Report messages. Basically, the stations did not properly subscribe to the multicast group used to send the image. As a result, there could have been issues with the multicast flow delivery to the stations. It was necessary to have the imaging server in the same VLAN as the stations being restored to avoid the multicast routing, and at the same time, the IGMP Snooping which is active by default on Catalyst switches had to be deactivated. Perhaps the newest Symantec Ghost version uses an improved IP driver that properly implements IGMP so that both IGMP Snooping and multicast routing can work nicely but this is something you must test yourself, as I do not have the most recent Ghost version available for testing.
If your imaging servers are in different VLANs than the restored stations then if you want to use multicasting, you absolutely have to configure IP multicast routing.
Assuming you have a single GhostCast server from which the multicast streaming is performed, you will definitely need to activate multicast routing, as the clients are - according to your own words - located in different VLANs.
There is actually one possibility of circumventing the multicast routing with a Cisco-specific feature called Multicast VLAN Registration, or MVR. It basic idea is to enclose the entire multicast traffic into a single specific VLAN, and whenever a station in a different VLAN subscribes to a particular multicast group, the switch will start "leaking" that particular group from the multicast VLAN into the user's VLAN. However, this feature may still require multicast routing in order to get the multicast traffic from the GhostCast server into the multicast VLAN (unless you place the server into the multicast VLAN directly), and must be supported by the individual switches where clients are connected. You may want to read more about this feature here:
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...