RE: Class-Based Marking Verification -> AT DESTINATION

From: Dennis J. Hartmann (dennisjhartmann@hotmail.com)
Date: Wed Oct 05 2005 - 22:47:01 GMT-3

Next message: Andrew Lissitz \(alissitz\): "RE: OSPF routing loop"
Previous message: Niche: "Re: Class-Based Marking Verification -> AT DESTINATION"
Maybe in reply to: Dennis J. Hartmann: "Class-Based Marking Verification -> AT DESTINATION"
Next in thread: Henk de Tombe: "RE: Class-Based Marking Verification -> AT DESTINATION"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

    No Niche. That didn't work, but I must thank you because........

    For some strange reason, your suggestion prompted me to change my ACL
configuration to only permit traffic that matched DSCP 46 (EF).

    When I ran the following debug, I saw debug output. Even though i can
not see the TOS marking in the debug, just by getting debug output, I know
the markings are still intact. :-) :-) :-)

    I STRONGLY suggest EVERYONE verify their end-to-end QoS markings in the
CCIE lab, because if you forget the mls qos trust dscp command at an
intermeddiate switch, that switch will re-write ALL markings down to ZERO.
This is an easy way to verify your markings....... Good luck!

R3#show access-list 100
Extended IP access list 100
    10 permit ip any any dscp ef (10 matches)
R3#show debug
Generic IP:
  IP packet debugging is on (detailed) for access list 100

R3#
*Mar 1 02:01:52.250: IP: tableid=0, s=2.2.2.2 (Serial1/2), d=180.40.7.3
(Serial
1/2), routed via RIB
*Mar 1 02:01:52.250: IP: s=2.2.2.2 (Serial1/2), d=180.40.7.3 (Serial1/2),
len 1
00, rcvd 3
*Mar 1 02:01:52.250: ICMP type=8, code=0
*Mar 1 02:01:52.250: IP: tableid=0, s=180.40.7.3 (local), d=2.2.2.2
(Serial1/2)
, routed via FIB
*Mar 1 02:01:52.250: IP: s=180.40.7.3 (local), d=2.2.2.2 (Serial1/2), len
100,
sending
*Mar 1 02:01:52.254: ICMP type=0, code=0
*Mar 1 02:01:52.282: IP: tableid=0, s=2.2.2.2 (Serial1/2), d=180.40.7.3
(Serial
1/2), routed via RIB
*Mar 1 02:01:52.282: IP: s=2.2.2.2 (Serial1/2), d=180.40.7.3 (Serial1/2),
len 1
00, rcvd 3
*Mar 1 02:01:52.282: ICMP type=8, code=0
*Mar 1 02:01:52.286: IP: tableid=0, s=180.40.7.3 (local), d=2.2.2.2
(Serial1/2)
, routed via FIB
*Mar 1 02:01:52.286: IP: s=180.40.7.3 (local), d=2.2.2.2 (Serial1/2), len
100,
sending
*Mar 1 02:01:52.286: ICMP type=0, code=0
*Mar 1 02:01:52.314: IP: tableid=0, s=2.2.2.2
R3#(Serial1/2), d=180.40.7.3 (Serial1/2), routed via RIB
*Mar 1 02:01:52.318: IP: s=2.2.2.2 (Serial1/2), d=180.40.7.3 (Serial1/2),
len 1
00, rcvd 3
*Mar 1 02:01:52.318: ICMP type=8, code=0
*Mar 1 02:01:52.318: IP: tableid=0, s=180.40.7.3 (local), d=2.2.2.2
(Serial1/2)
, routed via FIB
*Mar 1 02:01:52.318: IP: s=180.40.7.3 (local), d=2.2.2.2 (Serial1/2), len
100,
sending
*Mar 1 02:01:52.318: ICMP type=0, code=0
*Mar 1 02:01:52.350: IP: tableid=0, s=2.2.2.2 (Serial1/2), d=180.40.7.3
(Serial
1/2), routed via RIB
*Mar 1 02:01:52.350: IP: s=2.2.2.2 (Serial1/2), d=180.40.7.3 (Serial1/2),
len 1
00, rcvd 3
*Mar 1 02:01:52.350: ICMP type=8, code=0
*Mar 1 02:01:52.350: IP: tableid=0, s=180.40.7.3 (local), d=2.2.2.2
(Serial1/2)
, routed via FIB
*Mar 1 02:01:52.350: IP: s=180.40.7.3 (local), d=2.2.2.2 (Serial1/2), len
100,
sending
*Mar 1 02:01:52.350: ICMP type=0, code=0
*Mar 1 02:01:52.382: IP: tableid=0, s=2.2.2.2 (Serial1/2), d=180.40.7.3
(Serial
1/2), routed via RIB
*Mar 1 02:01:52.382: IP: s=2.2.2.2 (Serial1/2), d=180.40.7.3 (Serial1/2),
len 1
00, rcvd 3
*Mar 1 02:01:52.382: ICMP type=8, code=0
*Mar 1 02:01:52.382: IP: tableid=0, s=180.40.7.3 (local), d=2.2.2.2
(Serial1/2)
, routed via FIB
*Mar 1 02:01:52.382: IP: s=180.40.7.3 (local), d=2.2.2.2 (Serial1/2), len
100,
sending
*Mar 1 02:01:52.386: ICMP type=0, code=0

Sincerely,

Dennis J. Hartmann

White Pine Communications

dh8@pobox.com

CCSI#23402 / CCVP / CCIP / CCNP

Cisco Optical, VPN & IDS Specialist

MCSE

_____

From: Niche [mailto:jackyliu419@gmail.com]
Sent: Wednesday, October 05, 2005 9:38 PM
To: Dennis J. Hartmann
Cc: Cisco certification
Subject: Re: Class-Based Marking Verification -> AT DESTINATION

Hi there,

Just a suggestion, use an access-list and check the log counter on the
destination interface works for you?

Cheers~
Jacky

On 10/6/05, Dennis J. Hartmann <dennisjhartmann@hotmail.com> wrote:

Does anyone know what debug command I can use to verify packet marking
at the destination of the traffic?

The policy is definetely working at the source, but the Networkers 2005
CCIE R&S Techtorial mentioned that a debug can be run at the destination to
verify that the packet was being marked.

The policy is definetely working (below), but a debug ip packet detail
does not decode the ToS byte value.... (the routers are connected by a
back-to-back serial cable).

R2#show policy-m int
Serial1/2

Service-policy output: ping

    Class-map: ping (match-all)
      30 packets, 3120 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: access-group name ping
      QoS Set
        dscp ef
          Packets marked 30

    Class-map: class-default (match-any)
      228 packets, 14965 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any

R2#ping 180.40.7.3 source 2.2.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 180.40.7.3, timeout is 2 seconds:
Packet sent with a source address of 2.2.2.2
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/32/32 ms
R2#

R3#sh debug
Generic IP:
IP packet debugging is on (detailed) for access list 2

R3#
*Mar 1 01:43:56.959: IP: tableid=0, s=2.2.2.2 (Serial1/2), d=180.40.7.3
(Serial
1/2), routed via RIB
*Mar 1 01:43:56.959: IP: s= <http://2.2.2.2> 2.2.2.2 (Serial1/2),
d=180.40.7.3 (Serial1/2),
len 1
00, rcvd 3
*Mar 1 01:43:56.959: ICMP type=8, code=0
*Mar 1 01:43:56.959: IP: tableid=0, s= 180.40.7.3 <http://180.40.7.3>
(local), d=2.2.2.2
(Serial1/2)
, routed via FIB
*Mar 1 01:43:56.992: IP: tableid=0, s=2.2.2.2 (Serial1/2), d=180.40.7.3
<http://180.40.7.3>
(Serial
1/2), routed via RIB
*Mar 1 01:43:56.992: IP: s=2.2.2.2 (Serial1/2), d=180.40.7.3 (Serial1/2),
len 1
00, rcvd 3
*Mar 1 01:43:56.992 : ICMP type=8, code=0
*Mar 1 01:43:56.992: IP: tableid=0, s=180.40.7.3 (local), d=2.2.2.2
(Serial1/2)
, routed via FIB
*Mar 1 01:43:57.024: IP: tableid=0, s= 2.2.2.2 (Serial1/2), d=180.40.7.3
(Serial
1/2), routed via RIB
*Mar 1 01:43:57.024: IP: s=2.2.2.2 (Serial1/2), d= <http://180.40.7.3>
180.40.7.3 (Serial1/2),
len 1
00, rcvd 3
*Mar 1 01:43:57.024: ICMP type=8, code=0
*Mar 1 01:43:57.024: IP: tableid=0, s=180.40.7.3 (local), d= 2.2.2.2
<http://2.2.2.2>
(Serial1/
R3#2), routed via FIB
*Mar 1 01:43:57.056: IP: tableid=0, s=2.2.2.2 (Serial1/2), d=180.40.7.3
(Serial
1/2), routed via RIB
*Mar 1 01:43:57.056: IP: s=2.2.2.2 (Serial1/2), d=180.40.7.3 (Serial1/2),
len 1
00, rcvd 3
*Mar 1 01:43:57.056: ICMP type=8, code=0
*Mar 1 01:43: 57.056: IP: tableid=0, s=180.40.7.3 (local), d=2.2.2.2
(Serial1/2)
, routed via FIB
*Mar 1 01:43:57.088: IP: tableid=0, s=2.2.2.2 <http://2.2.2.2>
(Serial1/2), d=180.40.7.3
(Serial
1/2), routed via RIB
*Mar 1 01:43:57.088: IP: s=2.2.2.2 (Serial1/2), d=180.40.7.3 (Serial1/2),
len 1
00, rcvd 3
*Mar 1 01:43:57.088: ICMP type=8, code=0
*Mar 1 01:43:57.092: IP: tableid=0, s=180.40.7.3 (local), d=2.2.2.2
(Serial1/2)
, routed via FIB
R3#