HP FlexFabric 11000 Switch Products : R211x-HP Flexfabric 11900 IP Multicast Command Reference : Page 80

73

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

register-tunnel: Displays information about the register-tunnel interface. If this keyword is not specified,

the command displays information about all interfaces on the device.

interface-number: Specifies a register-tunnel interface by its number. The device has only one

register-tunnel interface and its number is fixed at 0. The command with the register-tunnel keyword

displays information about Register-Tunnel 0 with or without this argument.

brief: Displays brief information. If this keyword is not specified, the command displays detailed

information.

down: Displays information about the interfaces in down state and the causes. If this keyword is not

specified, the command displays information about interfaces in all states.

description: Displays the full interface description. If this keyword is not specified, only the first 27

characters of the interface description are displayed.

Usage guidelines

The register-tunnel interface is a virtual interface that is automatically created by the system. You cannot

configure it or delete it, but you can display the interface information by using this command. The

physical state and link state of the register-tunnel interface are always down.

In the initial stage of multicast source registration, the register-tunnel interface is used to establish a

channel between the source-side DR and the RP for transmitting multicast register messages. The process

of initial source registration is as follows:

1. After the source-side DR receives the first multicast data from the source, the DR encapsulates the

multicast data into a register message and forwards it to the RP through the register-tunnel

interface.

2. The register message reaches the register-tunnel interface on the RP. The RP decapsulates the

register message and forwards the multicast data to the receiver hosts. Meanwhile, the RP knows

the IP address of the multicast source.

3. The RP sends a join message to the multicast source to build an SPT.

4. After the SPT is built, the multicast data travels to the RP along the SPT rather than through the