Has anyone successfully used milticasting to deploy an OS over VLANs incorporating the following hardware/configuration?
We have a large Avaya (Nortel) infrastructure, with Passport 8600’s at the core and various Avaya (Nortel) switches in the wiring closets.
We have multicast enabled on the Avaya switches. We have PIM-SM enabled on the Passport at layer 3 and IGMP enabled on the vlans in the closets that we want to multicast over. We cannot get SCCM to deploy using multicast over this configuration. SCCM using unicast works ok.
Multicast with deployment server and clients on same subnet works, deployment server and clients on different subnets multicast fails to start.
Running a trace with the two different set ups we have observed the following. When the deployment server and client are on the same subnet we see the client sending a udp packet to address 224.0.0.252 with a destination port of 5355. The deployment server responds to this packet and then we see a mulicast group being created and the image is deployed.
When the deployment server and client are on different subnets we see the client sending a udp packet to address 224.0.0.252 with a destination port of 5355. The deployment server fails to respond to this packet.
224.0.0.x is local network control address block. According to multicast rules, addresses with in this range should never be forwarded by any mulicast routers. This is what we are seeing.