blumj
1 Nickel

Correct multicast address?

Correct multicast address?

My WSM server has an IP address = 10.107.8.144 Subnet mask = 255.255.252.0

When I checked the "Enable Multicast" box under the Operating System tab in the WSM console, it prefilled the Multicast address with 233.107.8.144


Is this correct? If not what would the correct address be?

Tags (2)
0 Kudos
1 Reply
mhaase-2015
2 Iron

RE: Correct multicast address?

You can either use the preset value or use any valid Multicast IP Address you like: http://en.wikipedia.org/wiki/Multicast_address.

The upcoming WSM Advanced Administration Guide will cover multicast in detail.
Here's an excerpt:

In Internet Protocol version 4 (IPv4), the Class D addresses, 224.0.0.0 to
239.255.255.255, are used for multicasting. It is recommended that you use the multicast
IP address range 239.0.0.0 to 239.255.255.255 for WSM multicast streaming. The
Internet Assigned Numbers Authority (IANA) has reserved this address range as
Administratively Scoped addresses for use in private multicast domains. Network
administrators are free to use multicast IP addresses in this range inside of their domain
without fear of conflicting with others elsewhere in the Internet, so long as such multicast
traffic will not be passed to the Internet cloud. In fact, it has become a common practice to
block multicast traffic in these ranges from entering or leaving an Autonomous Domain.
The Administratively Scoped addresses can be reused in different regions of the network.
Network administrators should configure their multicast routers to insure that multicast
traffic in the Administratively Scoped address range does not cross into or out of their
multicast domain.

It is also recommend that you assign a distinct multicast IP address for different virtual
disk images to avoid possible multicast address collisions. For example:
Vdisk1 - 239.1.0.0
Vdisk2 - 239.2.0.0
Vdisk3 - 239.3.0.0

This practice ensures that all WSM multicast sessions can be run in parallel without
interfering with each other, regardless of how your WSM environment is set up (see "WSM
Multicast Q&A" for scenarios where problems can occur if distinct multicast addresses are
not used).

For virtual disk version 3.0 or later, if the 3rd and/or 4th multicast IP address octet is
configured as 255, the WSM multicast server and client will automatically replace it with
corresponding octet(s) of the WSM streaming server IP from which the virtual disk image
is streamed.
For example:
•If VDisk’s multicast IP is configured as 239.1.255.255:
·When this image is streamed from WSM streaming server 192.168.1.99, the multicast address will be 239.1.1.99.
·When this image is streamed from WSM streaming server 192.168.2.98, the multicast address will be 239.1.2.98.
•If VDisk’s multicast IP is configured as 239.1.0.255:
·When this image is streamed from WSM streaming server 192.168.1.99, the multicast address will be 239.1.0.99.
·When this image is streamed from WSM streaming server 192.168.2.98, the multicast address will be 239.1.0.98.
•If VDisk’s multicast IP is configured as 239.1.255.0:
·When this image is streamed from WSM streaming server 192.168.1.99, the multicast address will be 239.1.1.0.
·When this image is streamed from WSM streaming server 192.168.2.98, the multicast address will be 239.1.2.0.

This process allows a single image to be multicast from different servers over different
multicast sessions.

Tags (2)
0 Kudos