Supported Platforms
Understanding PIP and CBP Interfaces on MX Series Routers
The Junos OS supports provider backbone bridging (PBB) described in the IEEE 802.1ah standard. When configuring PBB in carrier Ethernet networks, configure new pseudo-logical interfaces to provide a connection between customer routing instances (PBBN I-component) and provider routing instance (PBBN B-component).
The interfaces cpb and pip are pseudo-logical interfaces in a PBBN network. A customer backbone port (CBP) is a backbone edge bridge (BEB) port that receives and transmits I-tagged frames for multiple customers, and assigns B-VIDs and translates I-SIDs on the basis of a received I-SID. A provider instance port (pip) logical interface in a PBBN can transmit and receive S-tagged frames and map them to a service identifier (I-SID) while optionally stripping the S-VLAN tag.
Multiple customer routing instances must be associated with a single PBBN provider routing instance. To do this, configure a cpb pseudo-logical interface in the B-component of the BEB and a pip pseudo-logical interface in each of the I-components of the BEB.
Configure cpb and pip pseudo-logical interfaces in the same way that you configure other logical interfaces in the Junos OS.
To configure a cbp or a pip pseudo-logical interface, include the cbp or pip statement at the [edit interface interface-name unit logical-unit-number] hierarchy level, then associate the interface to a routing instance by including the interface [cbp | pip] statement at the [edit routing-instances instance-name] hierarchy level.
