Interface Configuration Guide 7705 SAR Interfaces
Edition: 01 3HE 11011 AAAC TQZZA 355
− high-priority: either cir = port_speed, which applies to all frames that are
scheduled via an in-profile scheduler, or round-robin (RR) for all other (network
egress queue) frames that are in-profile
− low-priority: either cir = 0, pir = port_speed, which applies to all frames that are
scheduled as out-of-profile, or RR for all other frames that are out-of-profile
• for network egress or access egress, where 4-priority scheduling is enabled:
− high-priority: either cir = port_speed, which applies to all frames that are
scheduled via an expedited in-profile scheduler, or RR for all other (network egress
queue) frames that reside in expedited queues and are in an in-profile state
− low-priority: either cir = 0, pir = port_speed, which applies to all frames that are
scheduled via a best effort out-of-profile scheduler, or RR for all other frames that
reside in best-effort queues and are in an out-of-profile state
• for the 8-port Gigabit Ethernet Adapter card, the 10-port 1GigE/1-port 10GigE X-Adapter
card, and for the v-port on the 2-port 10GigE (Ethernet) Adapter card and 2-port 10GigE
(Ethernet) module, for network egress, where 16-priority scheduling is enabled:
− high-priority: has higher priority than any user frames
− low-priority: has lower priority than any user frames
• for the physical ring ports on the 2-port 10GigE (Ethernet) Adapter card or 2-port 10GigE
(Ethernet) module, which can only operate as network egress, the priority of the LBR
frame is derived from the dot1p setting of the received LBM frame. Based on the
assigned ring-type network queue policy, dot1p-to-queue mapping is handled using the
same mapping rule that applies to all other user frames.
CFM loopback support on a physical ring port on the 2-port 10GigE (Ethernet) Adapter card
or 2-port 10GigE (Ethernet) module differs from other Ethernet ports. For these ports,
cfm-loopback is configured using dot1p and an optional list of up to 16 VLANs. The null
VLAN is always applied. The CFM Loopback Message will be processed if it does not contain
a VLAN header, or if it contains a VLAN header with a VLAN ID that matches one in the
configured match-vlan list.
The no form of the command disables the handling of CFM loopback frames.
Default no cfm-loopback
Parameters low — sets the queue parameters and scheduler mappings, as described above
high — sets the queue parameters and scheduler mappings, as described above
dot1p — sets the queue parameters and scheduler mappings on a physical ring port, as
described above
match-vlan — sets the matching VLAN IDs that will allow a CFM loopback on a physical
ring port when priority is set to dot1p, as described above
Values vlan-range: 1 to 4094 (for example, 1-10,33,2123)
none: only untagged CFM Loopback messages are accepted
Default none