mrouted.1m (2010 09)

m
mrouted(1M) mrouted(1M)
EXAMPLES
The routing tables look like this:
Virtual Interface Table
Vif Local-Address Metric Thresh Flags
0 36.2.0.8 subnet: 36.2 1 1 querier
groups: 224.0.2.1
224.0.0.4
pkts in: 3456
pkts out: 2322323
1 36.11.0.1 subnet: 36.11 1 1 querier
groups: 224.0.2.1
224.0.1.0
224.0.0.4
pkts in: 345
pkts out: 3456
2 36.2.0.8 tunnel: 36.8.0.77 3 1
peers: 36.8.0.77 (2.2)
boundaries: 239.0.1
: 239.1.2
pkts in: 34545433
pkts out: 234342
3 36.2.0.8 tunnel: 36.6.8.23 3 16
Multicast Routing Table (1136 entries)
Origin-Subnet From-Gateway Metric Tmr In-Vif Out-Vifs
36.2 1 45 0 1* 2 3*
36.8 36.8.0.77 4 15 2 0* 1* 3*
36.11 1 20 1 0* 2 3*
.
.
.
In this example, there are four vifs connecting to two subnets and two tunnels. The vif 3 tunnel is not in
use (no peer address). The vif 0 and vif 1 subnets have some groups present; tunnels never have any
groups. This instance of
mrouted is the one responsible for sending periodic group membership queries
on the vif 0 and vif 1 subnets, as indicated by the "querier" flags. The list of boundaries indicate the
scoped addresses on that interface. A count of the number of incoming and outgoing packets is also
shown at each interface.
Associated with each subnet from which a multicast datagram can originate is the address of the previous
hop router (unless the subnet is directly connected), the metric of the path back to the origin, the amount
of time since an update was received for this subnet, the incoming vif for multicasts from that origin, and
a list of outgoing vifs. The asterisk (
* ) indicates that the outgoing vif is connected to a leaf of the
broadcast tree rooted at the origin, and a multicast datagram from that origin will be forwarded on that
outgoing vif only if there are members of the destination group on that leaf.
The
mrouted command also maintains a copy of the kernel forwarding cache table. Entries are created
and deleted by mrouted.
4 Hewlett-Packard Company − 4 − HP-UX 11i Version 3: September 2010