Supported Platforms
Related Documentation
Configuring 100-Gigabit Ethernet PICs
You can configure the following features on the 100-Gigabit Ethernet PIC:
- Flexible Ethernet services encapsulation
- Source address MAC filtering
- Destination address MAC filtering
- MAC accounting in RX
- Channels defined by two stacked VLAN tags
- Channels defined by flex-vlan-tagging
- IP service for stacked VLAN tags
- Layer 2 rewrite
The following features are not supported on the 100-Gigabit Ethernet PIC:
- Multiple TPID
- IP service for non-standard TPID
- MAC learning
- MAC policing
![]() | Note: For the 100-Gigabit Ethernet PIC, only the PIC0 online and offline CLI commands are supported. The PIC1 online and offline CLI commands are not supported. |
![]() | Note: Each 100-Gigabit Ethernet PIC creates two et- physical interfaces, defined as 50-gigabit physical interfaces in the Routing Engine and Packet Forwarding Engine. By default, these are independent physical interfaces and are not configured as an aggregated Ethernet interface. The 100-Gigabit Ethernet PIC supports aggregated Ethernet configuration to achieve higher throughput capability, whereby configuration is similar to the 1G/10G aggregated Ethernet interface configuration. The 100-Gigabit Ethernet PIC has the following restrictions for aggregated Ethernet configuration:
|
To configure a 100-Gigabit Ethernet PIC:
- Perform the media configuration:
The 100-Gigabit Ethernet PIC features a 100 gigabit per second pipe. The media-related configuration commands for et-x/0/0:0 and et-x/0/0:1 must both be configured at the same time and configured with the same value, otherwise the commit operation fails.
When configuring to activate or deactivate the interface, if the interface contains the described media-related configuration, it must activate and deactivate both units 0 and 1 at the same time, otherwise the commit operation fails.
The following media configuration commands have the above described restriction:
- # set interfaces et-x/0/0:1 disable
- # set interfaces et-x/0/0:1 gigether-options loopback
- # set interfaces et-x/0/0:1 mtu yyy
Due to an MTU restriction, the vlan-tagging and flexible-vlan-tagging configuration on et-x/0/0:0 and et-x/0/0:1 must be same, otherwise the commit operation fails.
- Specify the logical interfaces:
- Two physical interfaces are created when the 100-Gigabit Ethernet PIC is brought online (et-x/0/0:0 and et-x/0/0:1, where x represents the FPC slot number). Each physical interface represents two internal 50-gigabit Ethernet Packet Forwarding Engines.
- Two logical interfaces are configured under each physical interface: Packet Forwarding Engine 0 is physical interface 0 and Packet Forwarding Engine 1 is physical interface 1.
- Configure the 802.3 link aggregation:
- Two physical interfaces are created for each 100-Gigabit Ethernet PIC. To utilize bandwidth beyond 50 gigabits, an aggregated interface must be explicitly configured on the 100-Gigabit Ethernet PIC that includes these two 50-gigabit interfaces.
- Each 100-Gigabit Ethernet PIC aggregate consumes one of the router-wide aggregated Ethernet device pools. In Junos OS with 100-Gigabit Ethernet PICs, you cannot exceed the router limit of 128 Ethernet PICs.
- In each aggregated bundle, each 100-Gigabit Ethernet PIC consumes two aggregate members. Hence, an aggregated bundle consisting of only one 100-Gigabit Ethernet PIC supports only up to half of the Junos OS limit for the number of members. The Junos OS supports a maximum of 16 links for up to 8 100-Gigabit Ethernet PIC links.
- Configure the Packet Forwarding Engine features:
- The 100-Gigabit Ethernet PIC supports all classification, firewall filters, queuing model, and rewrite functionality features of the Gigabit Ethernet PICs. To configure these parameters, see Configuring Gigabit Ethernet Policers, Configuring MAC Address Filtering, and Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview.
![]() | Note: When using the show interfaces extensive command with a 100-Gigabit Ethernet PIC, the “Filter statistics” section will not be displayed because the hardware does not include those counters. |