Channelizing interfaces on QFX5200
The 32 ports on Juniper QFX5200 can operate as 100G or 40G, based on the optic inserted in the port.
The 100G ports can work as 100G or they can be channelized to 50G or 25G.
The 40G ports can work as 40G or they can be channelized to 10G.
The 100G/40G appeat as et-fpc/pic/port and the channelized interfaces as et-fpc/pic/port:channel.
There is a 100G link between these two QFX5200:
{master:0}[edit] root@jtac-QFX5200-32C-4# run show chassis hardware Hardware inventory: Item Version Part number Serial number Description FPC 0 650-059719 WH0216160014 QFX5200-32C-32Q CPU BUILTIN BUILTIN FPC CPU PIC 0 BUILTIN BUILTIN 32X40G/32X100G-QSFP Xcvr 2 EV01 740-061000 1PC4021064G QSFP28-100G-CU1M
Without any configuration, the port operates at 100G:
{master:0}[edit] root@jtac-QFX5200-32C-4# run show interfaces terse | match et-0/0/2 et-0/0/2 up up et-0/0/2.16386 up up {master:0}[edit] root@jtac-QFX5200-32C-4# run show interfaces et-0/0/2 Physical interface: et-0/0/2, Enabled, Physical link is Up Interface index: 656, SNMP ifIndex: 515 Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 100Gbps, BPDU Error: None, Loop Detect PDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Media type: Fiber
Let’s channelize this interface to 50G and confirm that each interface is 50G(the configuration is done on both QFX5200):
{master:0}[edit] root@jtac-QFX5200-32C-4# show chassis fpc 0 { pic 0 { port 2 { channel-speed 50g; } } } {master:0}[edit] root@jtac-QFX5200-32C-4# run show interfaces terse | match et-0/0/2 et-0/0/2:0 up up et-0/0/2:1 up up {master:0}[edit] root@jtac-QFX5200-32C-4# run show interfaces et-0/0/2:0 Physical interface: et-0/0/2:0, Enabled, Physical link is Up Interface index: 656, SNMP ifIndex: 522 Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 50Gbps, BPDU Error: None, Loop Detect PDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Media type: Fiber
Now to 25G(notice that now we have 4 interfaces, 4 times 25G is 100G):
{master:0}[edit] root@jtac-QFX5200-32C-4# show chassis fpc 0 { pic 0 { port 2 { channel-speed 25g; } } } {master:0}[edit] root@jtac-QFX5200-32C-4# run show interfaces terse | match et-0/0/2 et-0/0/2:0 up up et-0/0/2:1 up up et-0/0/2:2 up up et-0/0/2:3 up up {master:0}[edit] root@jtac-QFX5200-32C-4# run show interfaces et-0/0/2:0 Physical interface: et-0/0/2:0, Enabled, Physical link is Up Interface index: 656, SNMP ifIndex: 522 Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 25000mbps, BPDU Error: None, Loop Detect PDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Media type: Fiber
These channelized interfaces are standalone interfaces and you can work with them as they are separate interfaces.
Let’s configure OSPF for each of them:
{master:0}[edit] root@jtac-QFX5200-32C-r1004# show interfaces et-0/0/2:0 { unit 0 { family inet { address 1.1.0.4/24; } } } et-0/0/2:1 { unit 0 { family inet { address 1.1.1.4/24; } } } et-0/0/2:2 { unit 0 { family inet { address 1.1.2.4/24; } } } et-0/0/2:3 { unit 0 { family inet { address 1.1.3.4/24; } } } {master:0}[edit] root@jtac-QFX5200-32C-r1004# show protocols ospf area 0.0.0.0 { interface et-0/0/2:0.0; interface et-0/0/2:1.0; interface et-0/0/2:2.0; interface et-0/0/2:3.0; } {master:0}[edit] root@jtac-QFX5200-32C-r1004#
You should have four neighbors:
{master:0}[edit] root@jtac-QFX5200-32C-r1004# run show ospf neighbor Address Interface State ID Pri Dead 1.1.0.5 et-0/0/2:0.0 Full 1.1.0.5 128 39 1.1.1.5 et-0/0/2:1.0 Full 1.1.0.5 128 38 1.1.2.5 et-0/0/2:2.0 Full 1.1.0.5 128 37 1.1.3.5 et-0/0/2:3.0 Full 1.1.0.5 128 37 {master:0}[edit] root@jtac-QFX5200-32C-r1004#
This applies to 40G interfaces, with the note that you can channelize to 10G(therefore 4 times 10G).
And this would be all about channelized interfaces on QFX5200 and Ihope you found this information useful.
Paris ARAU
Latest posts by Paris ARAU (see all)
- Junos Fusion – Part IV – Satellite policies and uplink failure detection - 30 July 2018
- Junos Fusion – Part III – Satellite commands and traffic forwarding - 16 July 2018
- Junos Fusion – Part II – Configuration, Administration and Operation - 16 July 2018
- Junos Fusion – Part I – Overview, Components, Ports and Software - 11 July 2018
- Vagrant – Part IV – Network topology using Juniper and Cumulus - 26 April 2018
excellent, just what I was looking for, a easy and clear example
Thank you very much