Configuring 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 ccc family only.
• inet—IP. You must configure this protocol family for the logical interface to support IP protocol traffic, including Open Shortest Path First (OSPF), Border Gateway Protocol (BGP), Internet Control Message Protocol (ICMP), and Internet Protocol Control Protocol (IPCP).
• inet6—IP version 6 (IPv6). You must configure this protocol family for the logical interface to support IPv6 protocol traffic, including Routing Information Protocol for IPv6 (RIPng), Intermediate System-to-Intermediate System (IS-IS), and BGP. For more information about IPv6, see IPv6 Introduction.
• iso—International Organization for Standardization (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 and voice services bundling.
• mlfr-end-to-end—Multilink Frame Relay end-to-end. You must configure this protocol or multilink Point-to-Point Protocol (MLPPP) for the logical interface to support multilink bundling.
• mlppp—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 routing platform's packet forwarding components. The JUNOS software automatically configures this protocol family on the routing platform's internal interfaces only, as discussed in Displaying the Internal Ethernet Interface.
• vpls—(M-series and T-series routing platforms only) 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) routing platforms 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 VPNs Configuration Guide and the JUNOS 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;

    multicast-only; 

    no-redirects;

    primary;

    address address {

        destination address;

        broadcast address;

        preferred;

        primary;

    }

}

You can include 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]