CCIE Pursuit Blog

February 3, 2008

How To Look Like A Jackass

Filed under: Cisco,IOS,QoS,Work — cciepursuit @ 7:42 pm
Tags: ,

I was asked by a member of our NOC to take a look at the QoS configuration on a router to see if there were any issues.  I logged in and took a look: 

r1#show policy-map
  Policy Map FAKE
    Class FAKE1
      Strict Priority
      Bandwidth 512 (kbps) Burst 12800 (Bytes)
    Class FAKE2
      Bandwidth 128 (kbps) Max Threshold 64 (packets)
    Class FAKE3
      Bandwidth 128 (kbps) Max Threshold 64 (packets)
    Class class-default

r1#sh policy-map s0/0

r1#

The policy map exists on the router but is not assigned to the interface.  I told the NOC:

“There’s the problem.  Tell the site engineer that he did not apply the service-policy to the interface.”

A few minutes later I got a call from the engineer who supports that site:

“Why did you tell the NOC that I didn’t have QoS running on router r1?”
“Because I saw that the policy is there, but it is not applied to interface.”
“Yes it is.”
“No it isn’t.”
“Yes.  It.  Is.”

At that point I logged into the router and rechecked.  To my surprise, the policy was there:

r1#sh policy-map int s0/0

 Serial0/0

  Service-policy output: FAKE

    Class-map: FAKE1 (match-all)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: protocol edonkey
      Queueing
        Strict Priority
        Output Queue: Conversation 264
        Bandwidth 512 (kbps) Burst 12800 (Bytes)
        (pkts matched/bytes matched) 0/0
        (total drops/bytes drops) 0/0

    Class-map: FAKE2 (match-all)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: protocol dns
      Queueing
        Output Queue: Conversation 265
        Bandwidth 128 (kbps)Max Threshold 64 (packets)
        (pkts matched/bytes matched) 0/0
        (depth/total drops/no-buffer drops) 0/0/0

—OUTPUT TRUNCATED—

My first thought was that he had changed the configuration, but there were no configuration changes made.  An IOS bug?

In cases like this I have learned that the most likely suspect is myself.  This proved to be no exception.  Those of you with a good eye have already spotted my mistake:

r1#sh policy-map ?
  WORD           policy-map name
  control-plane  Show Control Plane policy
  interface      Show Qos Policy Interface
  session        Show session Qos Policy
  |              Output modifiers
  <cr>

‘show policy-map s0/0′ and ‘show policy-map int s0/0′ are not the same command.  :-)

‘show policy-map s0/0 looks for a policy-map named ‘s0/0′, while ‘show policy-map int s0/0′ shows the (inbound and outbound) policies assigned to interface s0/0.

DOH!!!!

As soon as I explained my mistake the flood of jokes at my expense began:

“Do they have QoS on the CCIE lab?  Good luck with that.”
“Why don’t you just take $1500 and light it on fire?  It’ll save you time and travel.”
“Did you hear?  Cisco has an undocumented command.  It’s called “show policy-map interface”!”
“Help!  All of my routers have lost their QoS configuration!”

And so on….all fucking day long.  :-)

It’s all in good fun.  Just be aware that if you announce that you are pursuing the CCIE, every mistake you make is going to be analyzed because you are supposed to be a guru.  :-)
 

The Rubric Theme. Blog at WordPress.com.

Follow

Get every new post delivered to your Inbox.

Join 109 other followers