Skip to main content

1E 23.7 (SaaS)

MultiCastMADCAPScope

The MADCAP scope for multicast.

Warning

The Multicast feature is not supported in the Tachyon 5.2 release. This feature is under consideration for re-design and may be available in future versions of Nomad.

Registry value

Default value

Notes

Installer property

MultiCastMADCAPScope

SMSNomad

Values may be set using either of the formats in the table below.

MODULE.NOMAD.MADCAPSCOPE

Format

Description

<ScopeName>

<ScopeName> is the name of a scope defined in the DHCP (if you are using the Microsoft implementation of MADCAP). Use this format if you have multiple MADCAP servers. This method uses the time to live settings for the scope.

<MADCAP_ServerIP>

<MADCAP_Scope_IP>

<TTL>

  • <MADCAP_ServerIP> is the IP address of a specific MADCAP server

  • <MADCAP_ScopeIP> is the starting IP address for a MADCAP scope defined in the DHCP (if you are using the Microsoft implementation of MADCAP)

  • <TTL> is the time to live for the multicast packets

    Note

    Using a TTL greater than 1 is not recommended unless you have ensured that multicast traffic cannot leak back upstream through any intervening routers. The valid range for TTL is a number between 1 and 255

Nomad is also capable of performing control multicast without a MADCAP server installation on the network. In order to use this feature, the <MADCAP_ServerIP> must be set to 0.0.0.0. For example, the following supports MADCAP server not being present, with a scope of 239.0.9.0 and a time to live of 3.

0.0.0.0,239.0.9.0,3
In this section: