Configure the Protocol Family

For each logical interface, you can configure one or more of the following protocols that run on the interface:

• ccc—Circuit Cross-Connect (CCC). You can configure this protocol family for the logical interface of CCC physical interfaces. When you use this encapsulation type, you can configure the family ccc only.
• inet—IP (Internet Protocol). You must configure this protocol family for the logical interface to support IP protocol traffic, including OSPF, BGP, and ICMP.
• inet6—IP (Internet Protocol) version 6. You must configure this protocol family for the logical interface to support IPv6 protocol traffic, including RIPng, IS-IS, and BGP. For more information about IPv6, see IPv6 Introduction.
• iso—ISO. You must configure this protocol family for the logical interface to support IS-IS traffic.
• mlfr-uni-nni—Multilink Frame Relay (MLFR) FRF.16 user-to-network network-to-network (UNI NNI) . You must configure this protocol or mlfr-end-to-end for the logical interface to support link services bundling.
• mlfr-end-to-end—Multilink Frame Relay End-to-End. You must configure this protocol or MLPPP for the logical interface to support multilink bundling.
• mlppp—Multilink Point-to-Point Protocol (MLPPP). You must configure this protocol (or mlfr-end-to-end) for the logical interface to support multilink bundling.
• mpls—Multiprotocol Label Switching (MPLS). You must configure this protocol family for the logical interface to participate in an MPLS path.
• tcc—Translational Cross-Connect (TCC). You can configure this protocol family for the logical interface of TCC physical interfaces.
• tnp—Trivial Network Protocol. This protocol is used to communicate between the Routing Engine and the System Control Board (SCB), System and Switch Board (SSB), Forwarding Engine Board (FEB), or System and Forwarding Module (SFM), depending on router model, in the router's Packet Forwarding Engine. The JUNOS software automatically configures this protocol family on the router's internal interfaces only, as discussed in Configure the Internal Ethernet Interface.
• vpls—Virtual Private LAN Service (VPLS). You can optionally configure this protocol family for the logical interface on which you configure VPLS. VPLS provides an Ethernet-based point-to-multipoint Layer 2 VPN to connect customer edge (CE) routers across an MPLS backbone. When you configure a VPLS encapsulation type, the family vpls statement is assumed by default. For more information about VPLS, see the JUNOS Internet Software Configuration Guide: VPNs and the JUNOS Internet Software Feature Guide.

To configure the logical interface's protocol family, include the family statement, specifying the selected family. To configure more than one protocol family on a logical interface, include multiple family statements. Following is the minimum configuration:

family family { 

    mtu size;

    multicasts-only; 

    no-redirects;

    primary;

    address address {

        destination address;

        broadcast address;

        preferred;

        primary;

    }

}

You can configure these statements at the following hierarchy levels:

• [edit interfaces interface-name unit logical-unit-number]
• [edit logical-routers logical-router-name interfaces interface-name unit logical-unit-number]