Traffic with the IP precedence value af21 ingresses the router and should be rewritten with the same value as it egresses; however, this traffic is rewritten to a different value. user@router# show class-of-service classifiers { inet-precedence ipp-test { import default; forwarding-class best-effort { loss-priority low code-points be; } forwarding-class expedited-forwarding { loss-priority low code-points af21; } forwarding-class assured-forwarding { loss-priority low code-points af11; } forwarding-class network-control { loss-priority low code-points nc1; } } } interfaces { ge-* { scheduler-map map-test; unit * { classifiers { inet-precedence ipp-test; } rewrite-rules { inet-precedence ipp-rw-test; inet-precedence default; } } } } ... rewrite-rules { inet-precedence ipp-rw-test { forwarding-class best-effort { loss-priority low code-point be; loss-priority high code-point af21; } forwarding-class expedited-forwarding { loss-priority high code-point af21; loss-priority low code-point be; } forwarding-class assured-forwarding { loss-priority low code-point af11; loss-priority high code-point af11; } forwarding-class network-control { loss-priority low code-point nc1; loss-priority high code-point nc1; } } } user@router show class-of-service ... Code point type: inet-precedence Alias Bit pattern af11 001 af21 010 af31 011 af41 100 be 000 cs6 110 cs7 111 ef 101 nc1 110 nc2 111 Referring to the exhibit, what is the source of this problem?

Question

Traffic with the IP precedence value af21 ingresses the router and should be rewritten with the same value as it egresses; however, this traffic is rewritten to a different value. user@router# show class-of-service classifiers { inet-precedence ipp-test { import default; forwarding-class best-effort { loss-priority low code-points be; } forwarding-class expedited-forwarding { loss-priority low code-points af21; } forwarding-class assured-forwarding { loss-priority low code-points af11; } forwarding-class network-control { loss-priority low code-points nc1; } } } interfaces { ge-* { scheduler-map map-test; unit * { classifiers { inet-precedence ipp-test; } rewrite-rules { inet-precedence ipp-rw-test; inet-precedence default; } } } } ... rewrite-rules { inet-precedence ipp-rw-test { forwarding-class best-effort { loss-priority low code-point be; loss-priority high code-point af21; } forwarding-class expedited-forwarding { loss-priority high code-point af21; loss-priority low code-point be; } forwarding-class assured-forwarding { loss-priority low code-point af11; loss-priority high code-point af11; } forwarding-class network-control { loss-priority low code-point nc1; loss-priority high code-point nc1; } } } user@router> show class-of-service ... Code point type: inet-precedence Alias Bit pattern af11 001 af21 010 af31 011 af41 100 be 000 cs6 110 cs7 111 ef 101 nc1 110 nc2 111 Referring to the exhibit, what is the source of this problem?

Accepted Answer

D. The BA classifier is assigning the traffic to the expedited forwarding queue with a low loss priority.

Answer

A. The BA classifier is assigning the traffic to the best-effort queue with a high loss priority.

Answer

B. The BA classifier is assigning the traffic to the best-effort queue with a low loss priority.

Answer

C. The BA classifier is assigning the traffic to the expedited forwarding queue with a high loss priority.

Traffic with the IP precedence value af21 ingresses the router and should be rewritten with the same value as it egresses; however, this traffic is rewritten to a different value. user@router# show…

Question

Options

How the community answered

Community Discussion