HP-UX Routing Services Administrator's Guide HP-UX 11i v2, HP-UX 11i v3 (B2355-91153, November 2011)

The primary use of the boundary option is to allow concurrent use of the same IP multicast
addresses on downstream subnets, without interfering with multicast broadcasts using the same IP
multicast addresses on subnets that are upstream from the mrouted gateway.
The cache_lifetime value determines the amount of time that a cached multicast route remains
in the kernel before timing out. This value is specified in seconds and must be between 300 (5
minutes) and 86400 (24 hours). The default value is 300.
You can use the pruning off command to explicitly configure mrouted as a nonpruning router.
When pruning is off, IP multicast datagrams are forwarded to leaf subnets of the broadcast
routing tree even when those leaf subnets do not contain members of the multicast destination
group. Use only nonpruning mode for testing. The default mode for pruning is on.
You can use the name command to assign a name (boundary-name) to a boundary (a
scoped-addr/mask-len pair) to simplify the configuration task.
mrouted terminates if it has less than two enabled virtual interfaces (VIFs), where a VIF is either
a physical multicast-capable interface or a tunnel. It logs a warning message if all the VIFs are
tunnels. HP recommends that you replace such configuration settings with more direct tunnels.
Starting mrouted
You can start mrouted from the HP-UX prompt or from within a shell script by issuing the following
command:
/etc/mrouted [-p] [-c config_file] [-d debug_level]
The -p option disables pruning by overriding the pruning on statement within the
/etc/mrouted.conf configuration file. You must use this option for testing purposes only.
The -c option overrides the default configuration file /etc/mrouted.conf. Use config_file
to specify an alternate configuration file.
The -d debug_level option specifies the debug level. debug_level can be in the range 0 to
3. To know more about debug_level values, type man 1M mrouted at the HP-UX prompt.
By default, mrouted always writes warning and error messages to the system log daemon. You
can retrieve these messages from the system log file, syslog.log, located in the
/var/adm/syslog directory.
For convenience in sending signals, mrouted writes its pid to the /var/tmp/mrouted.pid
file upon startup.
Verifying mrouted Operation
You can use one or more of the following methods to verify mrouted operation:
• Retrieve the virtual interface table and the multicast routing table to verify if appropriate virtual
interfaces (vifs) are configured. See “Displaying mrouted Routing Tables” (page 17) for
information on retrieving these tables.
• Retrieve the routing cache table to verify if the routing and cache information is appropriate
for your configuration of mrouted. See “Displaying mrouted Routing Tables” (page 17) for
information on retrieving this table.
• Examine the syslog file /var/adm/syslog/syslog.log for warning and error messages
that indicate the status of mrouted. Upon startup, mrouted logs a startup message in the
syslog file that indicates the mrouted version number, such as mrouted version 3.8.
• Issue the following ps (process status) command to search for the string “mrouted”, using
grep, to determine if the mrouted program is running:
ps -ef | grep mrouted
16 Configuring mrouted