level

cir-level

weight

cir-weight

SAP-ingress policy

SAP-egress policy

IP-criteria policy

Network-queue policy

Slope policy

Network policy

Ensure that traffic flows conform to their traffic profile.

Log violations of metered traffic flows exceeding the CIR value set on the entity across which the traffic is moving.

Provide fairness between traffic flows, so that conforming (in-profile) traffic flows are not starved of bandwidth and/or buffer space by non-conforming (out-of-profile) flows.

Minimize packet loss and reduce end to end latency.

Ensure that variable latencies do not cluster short bursts of originally conforming packets and render them nonconforming.

3

64

72

16

56

WRED monitors the shared buffer space utilization over a period of time.

WRED disables the TCP slow-start congestion control mechanism.

WRED uses two configurable slopes for each buffer pool: a high slope and a low slope.

WRED uses the shared buffer utilization, instead of the individual queue depth, to get a better picture of the average resource utilization of the shared buffer space.

WRED polices the shared buffer pool and marks all packets above a certain rate as "discard eligible."

NC, low

NC, high

BE, low

BE, high

It may exceed PIR of the queue.

It may be exceeded by the average servicing rate of the queue.

It varies depending on the traffic characteristics.

It is the rate at which packets are forwarded out of the queue.

It will be classified into forwarding class BE and stored in queue 1.

It will be classified into forwarding class BE and stored in queue 8.

It will be classified into forwarding class NC and stored in queue 1.

It will be classified into forwarding class NC and stored in queue 8.

TRUE

FALSE

During the allocation of within-CIR bandwidth.

During the allocation of above-CIR bandwidth.

During the allocation of both within-CIR and above-CIR bandwidth.

The port scheduler does not use the level of a child for making bandwidth allocation decisions

Packet drops in the local queue resulting from traffic congestion.

Packet drops on the downstream nodes resulting from traffic congestion.

Packet drops in the local queue resulting from traffic bursts.

Packet drops on the downstream nodes resulting from traffic bursts.

IOM3

FP3 based IMM

IOM1

IOM2

TRUE

FALSE

All out-of-profile traffic will be dropped before any in-profile is dropped.

The time average factor of 0 will discard all packets arriving in the shared buffer pool.

When the shared buffer utilization reaches 51%, in-profile packets might be dropped.

The highest probability with which an out-of-profile packet can be dropped is 20%.

When an in-profile packet arrives and the shared buffer utilization is at 69%, the packet will have approximately a 60% likelihood of being discarded.

Has the ability to distinguish traffic in 32 different ways.

Uses the RSVP protocol to create microflows through a network.

Has the ability to manually configure foiwarding classes through a network.

Uses the RSVP protocol to create macroflows through a network.

FC H1, high

FCH1, low

FCAF, high

FCAF, low

The default forwarding class for all traffic, including ICMP, is BE, which is placed in queue 1.

The SAP has been shut down.

The IP-match criteria has been misconfigured for ICMP traffic.

Queue 3 has no rate or CIR configured and thus cannot hold any packets.

The SAP-ingress policy has not been applied to the SAP.

SAP-ingress only

SAP-egress only

SAP-ingress and SAP-egress

Network ingress

Network egress

There are a maximum of 8 levels of priority serviced using a round-robin algorithm.

The default scheduler will spend an equal amount of time in each queue, as long as there is traffic present

The H1 internal forwarding class will receive its CIR before AF traffic.

Orphaned queues will be scheduled out of the BE queue.

A queue servicing EF and AF traffic will require explicit configuration to set the queue to expedited.

Classification rules must specify both an FC and a profile for the packets.

A network policy is applied at a physical port.

Classification is performed with behavior-aggregate statements only.

Match criteria can be chosen from dot1p, DSCP, and EXP fields in the packet.

It enables CFHP.

It more scalable than using policers.

It allows a separate set of queues/policers for each VLAN on a port.

It allows a set of queues to be shared among multiple SAPs.

Policing, expedited

Metering, marked discard eligible

Marking, marked discard eligible

Policing, discarded

Shaping, discarded

010011

100010

010001

001100

010010

Policer 3 forwards packets as out-of-profile when its PIR bucket has 4000 tokens.

Policer 3 starts discarding low-priority packets when its PIR bucket has at least 3000 tokens.

Policer 4 forwards all its packets as out-of-profile.

Policer 4 starts discarding low-priority packets when its PIR bucket has at least 3000 tokens.

64

8

3

16

1

TRUE

FALSE

The policy should be placed in a "shutdown" state before changes are made.

A new network policy should be created and applied to the interface, overwriting the previous policy.

The policy must first be removed from the interface, then modified and re-applied to the interface.

Before the policy can be changed, it must be deleted with the no network qos command.

Before any changes are made to the policy, all network interfaces where the policy is applied have to be shut down.

All in-profile packets in round-robin, then all out-of-profile packets in biased round-robin.

In-profile EF packets, then in-profile H2 packets, then in-profile AF packets, then out-of-profile EF packets, then out-of-profile H2 and AF packets, and then out-of-profile BE packets.

In-profile EF, H2 and AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

In-profile EF packets, then in-profile H2 and AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

In-profile EF and H2 packets, then in-profile AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

Once before going through each of the redundant switching fabrics.

To protect against failure of either ingress or egress card.

Once before going through the switching fabric, and once more before going onto the egress port.

Once to decide if the packet is in-profile or out-of-profile, and once more to process the packet according to its profile.

1

2

3

4

5

8

PIR = 4Mbps. CIR = 1Mbps

PIR = 1Mbps, CIR = 1 Mbps

PIR = 10Mbps, CIR = 1Mbps

PIR = 5Mbps, CIR = 1.25Mbps

PIR = 1.25Mbps, CIR = 1.25Mbps