Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Scaling of Per-VLAN Queuing on Non-Queuing MPCs

Support for per-VLAN (logical interface) queuing is introduced in Junos OS Release 13.2 on 16x10GE MPC and MPC3E line cards.

You can configure logical interface scheduling on the following MICs and MPCs:

  • 16x10GE MPC
  • MPC3E:
    • 10x10GE MIC with SFP+
    • 2x40GE MIC with QSFP+
    • 1x100GE MIC with CXP

To enable logical interface scheduling, you include the per-unit-scheduler statement at the [edit interfaces interface name] hierarchy level. When per-unit schedulers are enabled, you can define dedicated schedulers for logical interfaces by including the scheduler-map statement at the [edit class-of-service interfaces interface name unit logical unit number] hierarchy level. Alternatively, you can include the scheduler-map statement at the [edit class-of-service traffic-control-profiles traffic control profile name] hierarchy level and then include the output-traffic-control-profile statement at the [edit class-of-service interfaces interface name unit logical unit number] hierarchy level.

The following table shows the number of VLANs per port available in both 8-queue and 4-queue mode.

Table 1: Number of VLANs Per Port Available on Non-Queuing MPCs

MPC

MIC

VLANs/Port – 8-Queue Mode

VLANs/Port – 4-Queue Mode

16X10GE

No

21

44

MPC3E

10-Gigabit Ethernet MIC with SFP+ (10X10GE)

2

6

MPC3E

40-Gigabit Ethernet MIC with QSFP+ (2X40GE)

20

42

MPC3E

100-Gigabit Ethernet MIC with CXP (1X100GE)

20

42

Enabling per-unit schedulers on these interfaces adds additional output to the show interfaces interface name [detail | extensive] command. This additional output lists the maximum resources available and the number of configured resources for schedulers. Following is sample output showing the CoS scheduler resource information on a non-queuing line card:

root@R1# run show interfaces et-2/2/0 detail
Physical interface: et-2/2/0, Enabled, Physical link is Down
  Interface index: 165, SNMP ifIndex: 550, Generation: 168
  Link-level type: Ethernet, MTU: 1522, Speed: 100Gbps, BPDU Error: None, Loopback: Disabled, Source filtering: Disabled,
  Flow control: Enabled
  Device flags   : Present Running Down
  Interface flags: Hardware-Down SNMP-Traps Internal: 0x4000
  Link flags     : Scheduler
  CoS queues     : 8 supported, 8 maximum usable queues
  Schedulers     : 0
  Hold-times     : Up 0 ms, Down 0 ms
  Current address: 80:71:1f:10:e6:b4, Hardware address: 80:71:1f:10:e6:b4
  Last flapped   : 2013-05-07 16:17:01 PDT (03:16:41 ago)
  Statistics last cleared: Never
  Traffic statistics:
   Input  bytes  :                    0                    0 bps
   Output bytes  :                    0                    0 bps
   Input  packets:                    0                    0 pps
   Output packets:                    0                    0 pps
   IPv6 transit statistics:
    Input  bytes  :                   0
    Output bytes  :                   0
    Input  packets:                   0
    Output packets:                   0
  Egress queues: 8 supported, 4 in use
  CoS scheduler resource information:
    Maximum units supported per MIC/PIC: 20
    Configured units per MIC/PIC: 1
    Maximum units allowed per port: 20
    Configured units on this port: 1
  Queue counters:       Queued packets  Transmitted packets      Dropped packets
    0 best-effort                    0                    0                    0
    1 expedited-fo                   0                    0                    0
    2 assured-forw                   0                    0                    0
    3 network-cont                   0                    0                    0
  Queue number:         Mapped forwarding classes
    0                   best-effort

If you enable more VLANs than the previously mentioned MPC/MIC combinations support, VLANs up to the supported numbers receive dedicated queuing resources. The additional VLANs share port queues. Scheduling for port queues cannot be controlled. However, port queues are guaranteed 1 percent of the physical interface bandwidth to avoid queue starving and buffer holdup.

Note: The persistency of queuing resources for a set of VLANs cannot be maintained through the following events:

  • System reboot
  • MPC or MIC restart
  • A Routing Engine switch without graceful Routing Engine switchover (GRES)
  • Disabling then re-enabling per-unit scheduler
  • Deactivating then reactivating interfaces
  • Deactivating then reactivating class-of-service (CoS) interfaces

Published: 2013-07-31