Nokia 4A0-107 Dumps

All self-generated traffic is assigned into forwarding class NC by default.

Ingress self-generated traffic is stored in CPM queues and egress self-generated traffic is stored in IOM queues.

The self-generated packets will be marked with a default DSCP value.

The self-generated packets will be marked with default EXP bits.

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.

Classification

Marking

Queuing

Congestion management

Scheduling

A port scheduler can only be implemented on a network egress port when queue-groups are configured for that port.

A port scheduler can be implemented on an access ingress port.

A port scheduler can be implemented without HQoS on an access egress port.

A port scheduler can be implemented on a network ingress port.

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.

8

16

32

48

A packet is accepted into a queue based on its priority and forwarding class.

Buffer admission control limits the number of out-of-profile packets that enter the queue.

Both high priority-only buffer space and WRED can be used in a queue.

Priority is used when a packet enters a SAP-ingress queue.

Network ingress port

Epipe ingress SAP

ES egress SAP

Ingress MDA

VPRN ingress interface

Shared buffer space

If CIR = PIR, then all packets will be considered as in-profile.

CIR can be set to 0.

CIR can be larger than PIR.

CIR can be set to ‘max’.

Change the CIR-level value for the best-effort queue to 8.

Do not change anything; it is already guaranteed to receive its CIR

Change the CIR-level value for the best-effort queue to 1.

Change the CIR-weight value of the AF queue to 0.

Set the queue’s CBS to 0

Set the queue’s MBS equal to the CBS

Set the queue’s high-priority-only equal to the MBS

Set the queue’s MBS to 0

Set the queue’s high-priority-only to 0

The default scheduler spends an equal amount of time servicing each queue that has traffic to be sent out.

Queue-type can be configured as best-effort, expedite, or auto-expedite.

A queue will be serviced as expedited if its type is configured as expedited, regardless of the forwarding classes mapped to it.

A queue configured as auto-expedited will be an expedited queue as long as no Best Effort FC is mapped to it.

EF, in

H1, out

BE, out

L1, in

Packets marked with dscp = af33

Packets marked with dot1p = 4

All packets mapped to queue 2 have the same priority to enter this queue.

There are no packets mapped to queue 2.

512 MB ingress, 512 MB egress

256 MB ingress, 256 MB egress

1 GB dynamically allocated between ingress and egress.

768 MB dynamically allocated between ingress and egress.

768 MB, with a minimum of 256 MB ingress and egress, and an additional 256 MB dynamically allocated.

Negative jitter results in a smaller than expected interval between transmitted packets.

Jitter does not have any effect on the quality of video applications.

Serialization delay is not affected by congestion.

Queuing delay is a fixed form of delay in networks.

Defining the slope of the TCP slow-start mechanism for self generated traffic.

Defining the slope of the scheduling rate per forwarding class when using HQoS.

Defining the high and low slope values when deploying buffer admission control for UDP traffic in the committed buffer pool.

Defining the high and low slope values when deploying buffer admission control for TCP traffic in the shared buffer pool.

Defining the high and low slope values when deploying buffer admission control for TCP traffic in the committed buffer pool.

Burst-limit sets a limit on the maximum burst of packets transmitted during each scheduler visitation time.

Proper configuration of the burst-limit can prevent packet drops on the downstream nodes resulting from traffic bursts.

The lower the configured burst limit value, the lower the burst allowed to enter the queue.

If the burst-limit is not configured, a default burst-limit value will be used by the queue.

network

scheduling

slope

SAP-ingress

network-queue

The available bandwidth of the port is divided in a strict priority over its children.

Expedited queues must be serviced before best-effort queues.

Orphaned queues are serviced on the 8th scheduling priority.

The configured CIR dictates the maximum port bandwidth that can be allocated during the within-CIR pass for that level.

IOM3

FP3 based IMM

IOM1

IOM2

The process of delaying packets within a traffic stream to have them conform to a defined traffic profile.

The overall treatment of a defined subset of a customer's traffic within a DiffServ domain.

The process of discarding packets within a traffic stream in accordance with the state of a meter to enforce a defined traffic profile.

The action of setting the DiffServ codepoint of a packet prior to its entry into a downstream DiffServ domain.

A specified algorithm or operation that is implemented in a node in order to realize one or more per-hop behaviors.

A point in the network where EXP bits can be mapped to one of eight predefined FCs, each one with its own queue.

A logical point in a service tunnel where all of customer traffic is aggregated.

A point at which the initial classification of customer traffic occurs.

A point in the network where QoS parameters are discarded in favor of lower-level hardware queuing functions, such as LLI (Link Layer Interleave).

A point in the network where traffic flows from multiple different services are queued together, based on forwarding class.

Native IP Packets will not be remarked.

Native IP Packets will be remarked.

Packets associated with a VPRN service on an upstream node will not be remarked.

Packets associated with an ES service on an upstream node will be remarked.

True

False

Access ingress, access egress, network egress

Access ingress, network ingress, network egress

Port ingress, port egress, shared bi-directional

Port ingress, port egress, network egress

Port ingress, network ingress, network egress

Shapeless policing at SAP-ingress only.

Shapeless policing at SAP-ingress and egress.

Biased round robin queuing at ingress only.

Soft shaping at all network interfaces.

Soft shaping at network ingress only.

The first 3 bits of the DSCP value are copied directly into the EXP field on the first network egress.

The EXP bits are set on the first network egress, based on a combination of the SAP-ingress classification and the network policy applied.

The 3 priority bits are copied directly from the dot1p header into the EXP field of the first MPLS header.

The EXP bits are set based on a default map that translates DSCP codes into internal forwarding classes on SAP-ingress.

All incoming packets belonging to forwarding class “l2” are stored in the reserved buffer space.

All incoming packets belonging to forwarding class “af” are stored in the reserved buffer space.

All incoming packets belonging to forwarding class “l1” are stored in the reserved buffer space.

In-profile packets in the shared buffer space are being dropped.

512 MB ingress, 512 MB egress

256 MB ingress, 256 MB egress

1 GB dynamically allocated between ingress and egress.

768 MB dynamically allocated between ingress and egress.

768 MB, with a minimum of 256 MB ingress and egress, and an additional 256 MB dynamically allocated.

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.

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.

level

cir-level

weight

cir-weight