


Please leave comments and continue this discussion on Twitter and Slack. I hope you found this interesting and thought-provoking. Vocera MC MAC address is always 01:00:5e:66:xx:xx xx:xx matches up with the 3 rd and 4 th Octet in the IP address. Stopping and starting the server or a fail-over will reset the address’s space as well. The range we use has 230.230.0.1 – 230.230.15.254 when the server runs out of addresses it will start over. The Vocera Multicast group MAC address is normally The first session will have 230.230.0.1 and each session will increase by one. I work for Vocera so naturally, the packets I have captured are Vocera Multicast sessions.

Packet capture of a multicast MAC address Both MAC addresses would be 01:00:5e:66:00:01 I have never seen this cause an issue before but theoretically, it could. When we look at this a bit deeper you will see that since the 25 th bit is always 0 this MAC address for 230.230.0.1 and 230.102.0.1 would be the same. There is an issue when you convert multicast IP into a MAC address. The table below shows the MAC address for the multicast IP session of 230.230.0.1 This might be confusing at first but once you read it over a few times it makes perfect sense.Īll Multicast MAC addresses start 01:00:52:0 (the 25 th bit in the MAC address for a Multicast session is always 0) the next 23 bits are the IP address translated to binary or Hex. This blog will explain how the MAC address is created I will show you some screenshots displaying these multicast MAC addresses. The session would need this to move the traffic on a layer 2 network. I have always thought and talked about the multicast session in the form of an IP address like 230.230.0.1 but each MC session has a MAC address associated with it. How else would multicast traffic and packets get delivered? I guess I never took the time to even think about it before. This makes sense, but I was a bit surprised to find out the multicast sessions have their own MAC address. All packets on an IP network need to have a MAC address so the network can send the frames between layer 2 devices. The MAC address table for the switch requires static entries that map each port to the NLB Multicast MAC.description 'Display MAC address learned on a description 'Display MAC table for a Hopefully, this will help someone have a better understanding of multicast and how packets flow over the network. 1 day ago &0183 &32 The OSPF multicast group is a link-local multicast that gets sent to every switch interface, even with IGMP snooping enabled on the switch. This may or may not be particularly useful, but I found it interesting, so I decided to blog about it.
