Configuring the Access Side of a Video Services Router Running JUNOS Software

The access (or customer) side of the JUNOS router operating in a video network uses IGMP and DHCP to manage video traffic to various clients. The interfaces on this side of the network use an unnumbered Ethernet configuration, as shown in Figure 7.

To implement video/IPTV applications on the access side of a video services router running JUNOS software, use the following procedures.

Note: To simplify this example, both video services routers (VSR1 and VSR2) use the same configuration except where otherwise specified.

1. Configure each access interface as an unnumbered Ethernet interface.

   [edit]

   interfaces {

   ge-1/0/0 {

   unit 0 {

   family inet {

   unnumbered-address lo0.0;

   }

   }

   }

   }

2. Specify that the interface use promiscuous mode.

   Note: You must specify that the IGMP interface use promiscuous mode if you define the unnumbered Ethernet donor interface as a loopback interface.

3. (Optional) Specify that the IGMP interface use immediate leave if you want the interface to do one of the following:
   • For IGMPv2: Immediately remove the group membership from the interface and suppress the sending of any group-specific queries for the multicast group.
   • For IGMPv3: Suppress the sending of group-and-source queries and rely on the JUNOS-supported host tracking mechanism to determine group membership removal.

     [edit]

     protocols {

     igmp {

     interface ge-1/0/0.0;

     promiscuous-mode;

     immediate-leave;

     }

     }

4. Configure DHCP relay.

   [edit]

   forwarding-options {

   dhcp-relay {

   server-group {

   DS1 {

   100.1.1.1; # IP address of DHCP server (DS1)

   }

   }

   active-server-group DS1;

   group one {

   interface ge-1/0/0.0; # interface to which DHCP clients send requests

   }

   }

   }

5. Configure PIM (required to configure PIM BFD).

   [edit]

   protocols {

   pim {

   rp {

   local {

   address 1.1.1.1;

   }

   }

   interface ge-1/0/0.0 {

   mode sparse;

   }

   }

   }

6. Configure PIM BFD to enable rapid failover detection for the PIM interfaces.

   [edit]

   protocols {

   pim {

   interface ge-1/0/0.0 {

   bfd-liveness-detection {

   minimum-interval 100;

   }

   }

   }

   }

7. Configure static routes over which each loopback interface can communicate with the other.
   • Configure a static route on Router VSR1 to the loopback interface on Router VSR2.

     [edit]

     routing-options {

     static {

     route 1.1.1.2/32 {

     qualified-next-hop ge-1/0/0.0;

     }

     }

     }

   • Configure a static route on Router VSR2 to the loopback interface on Router VSR1.

     [edit]

     routing-options {

     static {

     route 1.1.1.1/32 {

     qualified-next-hop ge-1/0/0.0;

     }

     }

     }

     Note: You must also configure static routes for the DSLAM devices to communicate with the unnumbered interfaces that are using a loopback interface.