Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Policy-map question

Hi,

I'm trying to resolve an issue with phones on remote routers thet keep re-registering throughout the day. I changed the:

policy-map shaper

class class-default

    shape average 2000000

  service-policy voice_and_video

To:

          

policy-map shaper

class class-default

    shape average 8000000

  service-policy voice_and_video

Not sure what I have just done but it didn't break it. The Comcast bandwidth is atleast 8000000 so, I figured I would match it with this.

What does this command effect?

Thanks, Pat.

20 REPLIES

Policy-map question

The change you made affects all outbound traffic and shapes it from 2Mb to 8Mb. That would allow more outbound traffic out, but it doesn't control what's coming inbound because shaping only affects outbound. The service policy that's attached to it is possibly the cause of the issue, but we need to know a little more about what the issue really is. What type of phones are they and where is the call server that they attach to? Is it over a tunnel?

HTH,

John

HTH, John *** Please rate all useful posts ***
New Member

Policy-map question

The phone s are 7965s and they are attached to a call manager at the Main site via a DMVPN tunnel. So, I've affected outbound but, not inbound. Could I have made that value too large as the upload speeds are generally slower  on a Internet connection.

policy-map mark_incoming_traffic

class discover_voip

  set dscp ef

class discover_signaling

  set dscp cs3

class discover_video

  set dscp cs2

class non_voip

  set dscp default

!

Thanks, Pat.

Re: Policy-map question

Could I have made that value too large as the upload speeds are generally slower  on a Internet connection.

Not really. If it was too large, the provider will drop you on inbound anyway, so you're really not affecting much. The only time that you really need to shape is if you're link speed is faster than the CIR. For example if you have a 100Mb FE connection and you had a 10Mb CIR. The provider will drop your incoming traffic to a 10Mb rate, but if you shape it outbound toward them to 10Mb you'll better your chances of not being dropped.

policy-map mark_incoming_traffic

class discover_voip

  set dscp ef

class discover_signaling

  set dscp cs3

class discover_video

  set dscp cs2

class non_voip

  set dscp default


I see that you're marking your traffic, but what are you doing with it on the other end? Are you pre-classifying the traffic on the tunnel interface with "qos pre-classify"?

HTH,

John

HTH, John *** Please rate all useful posts ***
New Member

Policy-map question

Yes we have qos pre-classify on both tunnel interfaces on each 881 router.

Thanks, Pat.

New Member

Policy-map question

John,

Not so sure that this means much but, a user I am woking with noticed that every time his CPU process spikes in task manager, he notices the phone starts re-registering.

Policy-map question

That's interesting. What's causing the spike, and have you noticed this on other phones as well?

HTH, John *** Please rate all useful posts ***
New Member

Policy-map question

One time was when he was opening his Outlook

Policy-map question

Is it this one user having a problem, or are there multiple users having the same problem?

HTH, John *** Please rate all useful posts ***
New Member

Policy-map question

I've seen the issue in several routers

Policy-map question

Can you post "sh policy-map interf" from one of the routers? You said that you see it in several routers. Is this all at the same time or is it at different times between sites? Within a site, do all phones try to reregister or is it only a couple of phones?

HTH, John *** Please rate all useful posts ***
New Member

Re: Policy-map question

These are remote 881s with only one 7965 attached. As far as I know, they re-register at different times - not all at once. Don't know if I can confirm this though.          

Hope this is what you wanted:

sh policy-map interface
FastEthernet4

  Service-policy output: shaper

    Class-map: class-default (match-any)
      870208 packets, 215404021 bytes
      5 minute offered rate 101000 bps, drop rate 0 bps
      Match: any
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 0/145/0
      (pkts output/bytes output) 870021/216862901
      shape (average) cir 8000000, bc 32000, be 32000
      target shape rate 8000000

      Service-policy : voice_and_video

        queue stats for all priority classes:

          queue limit 64 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 511560/150398640

        Class-map: call_setup (match-any)
          23011 packets, 3360404 bytes
          5 minute offered rate 0 bps, drop rate 0 bps
          Match: ip dscp cs3 (24)
            23011 packets, 3360404 bytes
            5 minute rate 0 bps
          Match: ip precedence 3
            0 packets, 0 bytes
            5 minute rate 0 bps
          Queueing
          queue limit 64 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 23011/3365682
          bandwidth 32 kbps

        Class-map: internetwork_control (match-any)
          93561 packets, 13603082 bytes
          5 minute offered rate 3000 bps, drop rate 0 bps
          Match: access-group name isakmp_acl
            2151 packets, 212786 bytes
            5 minute rate 0 bps
          Match: ip precedence 7
            0 packets, 0 bytes
            5 minute rate 0 bps
          Match: ip precedence 6
            91410 packets, 13390296 bytes
            5 minute rate 3000 bps
          Queueing
          queue limit 64 packets
          (queue depth/total drops/no-buffer drops) 0/0/0
          (pkts output/bytes output) 93559/15198032
          bandwidth 32 kbps

        Class-map: voice (match-any)
          511560 packets, 150398640 bytes
          5 minute offered rate 96000 bps, drop rate 0 bps
          Match: access-group name voice_acl
            511560 packets, 150398640 bytes
            5 minute rate 96000 bps
          Match: ip dscp ef (46)
            0 packets, 0 bytes
            5 minute rate 0 bps
          Match: ip precedence 5
            0 packets, 0 bytes
            5 minute rate 0 bps
          Priority: 128 kbps, burst bytes 3200, b/w exceed drops: 0


        Class-map: video (match-any)
          0 packets, 0 bytes
          5 minute offered rate 0 bps, drop rate 0 bps
          Match: ip precedence 2
            0 packets, 0 bytes
            5 minute rate 0 bps
          Match: ip dscp cs2 (16)
            0 packets, 0 bytes
            5 minute rate 0 bps
          Priority: 460 kbps, burst bytes 11500, b/w exceed drops: 0


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

          queue limit 64 packets
          (queue depth/total drops/no-buffer drops) 0/145/0
          (pkts output/bytes output) 241891/47900547
Vlan10

  Service-policy input: mark_incoming_traffic

    Class-map: discover_voip (match-any)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: protocol rtp payload-type "0"
        0 packets, 0 bytes
        5 minute rate 0 bps
      Match: protocol rtp payload-type "18"
        0 packets, 0 bytes
        5 minute rate 0 bps
      Match: protocol rtp audio
        0 packets, 0 bytes
        5 minute rate 0 bps
      QoS Set
        dscp ef
          Packets marked 0

    Class-map: discover_signaling (match-any)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: protocol skinny
        0 packets, 0 bytes
        5 minute rate 0 bps
      Match: protocol sip
        0 packets, 0 bytes
        5 minute rate 0 bps
      QoS Set
        dscp cs3
          Packets marked 0

    Class-map: discover_video (match-any)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: protocol cuva
        0 packets, 0 bytes
        5 minute rate 0 bps
      Match: protocol rtp video
        0 packets, 0 bytes
        5 minute rate 0 bps
      QoS Set
        dscp cs2
          Packets marked 0

    Class-map: non_voip (match-all)
      220471 packets, 50773746 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: access-group name non_voip_traffic_acl
      QoS Set
        dscp default
          Packets marked 220471

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

  Service-policy input: mark_incoming_traffic

    Class-map: discover_voip (match-any)
      511560 packets, 109473840 bytes
      5 minute offered rate 65000 bps, drop rate 0 bps
      Match: protocol rtp payload-type "0"
        0 packets, 0 bytes
        5 minute rate 0 bps
      Match: protocol rtp payload-type "18"
        0 packets, 0 bytes
        5 minute rate 0 bps
      Match: protocol rtp audio
        511560 packets, 109473840 bytes
        5 minute rate 65000 bps
      QoS Set
        dscp ef
          Packets marked 511560

    Class-map: discover_signaling (match-any)
      23304 packets, 1784332 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: protocol skinny
        23304 packets, 1784332 bytes
        5 minute rate 0 bps
      Match: protocol sip
        0 packets, 0 bytes
        5 minute rate 0 bps
      QoS Set
        dscp cs3
          Packets marked 23304

    Class-map: discover_video (match-any)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: protocol cuva
        0 packets, 0 bytes
        5 minute rate 0 bps
      Match: protocol rtp video
        0 packets, 0 bytes
        5 minute rate 0 bps
      QoS Set
        dscp cs2
          Packets marked 0

    Class-map: non_voip (match-all)
      31919 packets, 2333518 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: access-group name non_voip_traffic_acl
      QoS Set
        dscp default
          Packets marked 31893

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

Re: Policy-map question

I see drops from the main shaper class. What's the bandwidth at this location?

Service-policy output: shaper

    Class-map: class-default (match-any)
      870208 packets, 215404021 bytes
      5 minute offered rate 101000 bps, drop rate 0 bps
      Match: any
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 0/145/0
      (pkts output/bytes output) 870021/216862901
      shape (average) cir 8000000, bc 32000, be 32000
      target shape rate 8000000

This is shaping the cir to 8Mb. If the offered rate is higher than the cir and the router can't buffer it, it will drop the traffic. Do you have any servers or hosts that could possibly be uploading a ton of data to your main site? Can you also post "sho proc cpu | inc five"? These counters are cumulative though. If this is the router that you changed the cir on from your previous post, it could be from your router shaping to 2Mb instead of the 8.

HTH, John *** Please rate all useful posts ***
New Member

Re: Policy-map question

John, this is the router I changed from 2mbs to 8mbs. When I issued this output it was at 8mbs and still is. I will wait another hour to post the output of the sho proc cpu | inc five till there is some traffic. No, there shouldn't be any remote users uploading a ton of traffic. There is only about ten of them using the DMVPN.. I'm a little confused about the sentence,"sho proc cpu | inc five". Should I keep the shaping at 8mbs of put it to the offered rate or put it back to 2mbs?

Thanks, Pat.

Re: Policy-map question

Pat,

The "sho proc cpu | inc five" command will only give us the very first line that deals with processor utilization. It will show if there have been any spikes in cpu utilization that could be causing the router to stop processing traffic. It really depends on what the cir is for your connection. If you have a 15Mb down/8Mb up connection, by all means keep it at 8mb. If it's 15Mb down/2Mb up, you'll want to change it back to 2Mb because the provider is forcefully dropping anything over the cir ( anything > 2Mb).

HTH,

John

HTH, John *** Please rate all useful posts ***
New Member

Re: Policy-map question

John is it possible that the CIR could be less than 2mbs on a Business line? What am I losing by making my shaper less than the CIR? If the CIR is 4mbs up and I set my CIR to 2, I am limiting the router, correct? So if the line is 10 up and 3 down, what would be the right setting for the shaper?

sh processes cpu | i 5

PID Runtime(uS)     Invoked      uSecs   5Sec   1Min   5Min TTY Process

   2      148000       59092          2  0.00%  0.00%  0.00%   0 Load Meter

   4   341420000       44956       7594  0.00%  0.13%  0.11%   0 Check heaps

   5        4000          15        266  0.00%  0.00%  0.00%   0 Pool Manager

  10   178504000        4923      36259  0.00%  0.07%  0.05%   0 Licensing Auto U

  14      128000       59059          2  0.00%  0.00%  0.00%   0 IPC Service NonC

  15       44000      288521          0  0.00%  0.00%  0.00%   0 IPC Periodic Tim

  16       32000      288521          0  0.00%  0.00%  0.00%   0 IPC Deferred Por

  19        8000       59093          0  0.00%  0.00%  0.00%   0 IPC Loadometer

  24   438248000     3137588        139  0.15%  0.17%  0.16%   0 ARP Input

  25      204000      307739          0  0.00%  0.00%  0.00%   0 ARP Background

  35           0           1          0  0.00%  0.00%  0.00%   0 RMI RM Notify Wa

  37       32000      295457          0  0.00%  0.00%  0.00%   0 GraphIt

  42     4984000      105003         47  0.00%  0.00%  0.00%   0 Net Background

  45      256000      295277          0  0.00%  0.00%  0.00%   0 TTY Background

  46     2816000      295468          9  0.00%  0.01%  0.00%   0 Per-Second Jobs

  50           0           2          0  0.00%  0.00%  0.00%   0 AggMgr Process

  51      452000      149102          3  0.00%  0.00%  0.00%   0 Fast Throttle Ti

  52           0           1          0  0.00%  0.00%  0.00%   0 Token Daemon

  53           0           2          0  0.00%  0.00%  0.00%   0 Transport Port A

  54     3224000       61354         52  0.00%  0.00%  0.00%   0 HC Counter Timer

  55           0           1          0  0.00%  0.00%  0.00%   0 dev_device_inser

  56           0           1          0  0.00%  0.00%  0.00%   0 dev_device_remov

  57           0           2          0  0.00%  0.00%  0.00%   0 AUX

  58           0           2          0  0.00%  0.00%  0.00%   0 LED Timers

  59      212000           4      53000  0.00%  0.00%  0.00%   0 ESWPPM

  62      556000        2715        204  0.00%  0.00%  0.00%   0 i2c console redi

  63       16000      295443          0  0.00%  0.00%  0.00%   0 Console redirect

  65     3868000      105627         36  0.00%  0.00%  0.00%   0 OSPF-1 Hello

  68       60000      295469          0  0.00%  0.00%  0.00%   0 Crypto Device Up

  71      216000         436        495  0.00%  0.00%  0.00%   0 crypto engine pr

  75  2364548000      488426       4841  1.27%  1.28%  1.27%   0 ILPM

  82       36000      288512          0  0.00%  0.00%  0.00%   0 Ethernet Timer C

  84      116000      295279          0  0.07%  0.00%  0.00%   0 PI MATM Aging Pr

  85           0          16          0  0.00%  0.00%  0.00%   0 AAA Server

  89     6992000       44727        156  0.00%  0.00%  0.00%   0 CDP Protocol

  95           0           2          0  0.00%  0.00%  0.00%   0 IPAM/ODAP Events

  96      864000     9215542          0  0.07%  0.07%  0.07%   0 IPAM Manager

  98        4000          57         70  0.00%  0.00%  0.00%   0 IP ARP Adjacency

100    52900000      265318        199  0.23%  0.10%  0.02%   0 IP Input

101           0          57          0  0.00%  0.00%  0.00%   0 ICMP event handl

105           0           2          0  0.00%  0.00%  0.00%   0 PPP Bind

107      256000        9411         27  0.00%  0.00%  0.00%   0 CRYPTO IKMP IPC

111      208000     1154167          0  0.07%  0.01%  0.00%   0 SSS Feature Time

112     4888000      333058         14  0.07%  0.02%  0.00%   0 Spanning Tree

113           0           1          0  0.00%  0.00%  0.00%   0 X.25 Encaps Mana

115           0           1          0  0.00%  0.00%  0.00%   0 AC Switch

116           0         985          0  0.00%  0.00%  0.00%   0 Authentication P

121      164000        5734         28  0.00%  0.00%  0.00%   0 CEF background p

125           0           2          0  0.00%  0.00%  0.00%   0 L2X Switching Ev

130        4000         458          8  0.00%  0.00%  0.00%   0 TCP Timer

131           0          15          0  0.00%  0.00%  0.00%   0 TCP Protocols

133        4000         985          4  0.00%  0.00%  0.00%   0 HTTP CORE

135       36000        4931          7  0.00%  0.00%  0.00%   0 IP Background

137      188000          85       2211  0.00%  0.00%  0.00%   0 IP RIB Update

145           0          13          0  0.00%  0.00%  0.00%   0 Collection proce

150           0           1          0  0.00%  0.00%  0.00%   0 IP IRDP

151           0           1          0  0.00%  0.00%  0.00%   0 IPv6 Inspect Tim

152           0           1          0  0.00%  0.00%  0.00%   0 MQC Flow Event B

153     6424000    72783522          0  0.47%  0.48%  0.45%   0 HQF Shaper Backg

154           0           3          0  0.00%  0.00%  0.00%   0 RBSCP Background

155        4000           3       1333  0.00%  0.00%  0.00%   0 SCTP Main Proces

156           0           1          0  0.00%  0.00%  0.00%   0 VPDN call manage

157           0           1          0  0.00%  0.00%  0.00%   0 IPS Process

158           0           2          0  0.00%  0.00%  0.00%   0 IPS Auto Update

159           0           2          0  0.00%  0.00%  0.00%   0 SDEE Management

160       44000      577004          0  0.00%  0.00%  0.00%   0 Inspect process

163       36000      577004          0  0.00%  0.00%  0.00%   0 CCE DP URLF cach

165           0           2          0  0.00%  0.00%  0.00%   0 URL filter proc

171           0           1          0  0.00%  0.00%  0.00%   0 X.25 Background

175           0           1          0  0.00%  0.00%  0.00%   0 IDMGR CORE

178       36000         457         78  0.00%  0.00%  0.00%   0 LOCAL AAA

183      444000        2960        150  0.00%  0.00%  0.00%   0 Crypto Support

185           0           4          0  0.00%  0.00%  0.00%   0 Crypto CA

188    85644000        6211      13789  0.00%  0.11%  0.21%   0 crypto sw pk pro

191    15732000       35340        445  0.00%  0.00%  0.00%   0 Crypto IKMP

193      340000       15655         21  0.00%  0.00%  0.00%   0 IPSEC key engine

195        4000          34        117  0.00%  0.00%  0.00%   0 Crypto ACL

202       32000      180795          0  0.00%  0.00%  0.00%   0 PM Callback

205        4000           3       1333  0.00%  0.00%  0.00%   0 EEM ED Resource

207       36000       29529          1  0.00%  0.00%  0.00%   0 RMON Recycle Pro

215        4000         101         39  0.00%  0.00%  0.00%   0 EEM Server

225           0           2          0  0.00%  0.00%  0.00%   0 EEM ED SNMP Noti

234        8000         146         54  0.00%  0.00%  0.00%   0 Syslog

235           0           3          0  0.00%  0.00%  0.00%   0 EEM ED RPC

236     1540000     9230593          0  0.15%  0.12%  0.10%   0 PPP manager

PID Runtime(uS)     Invoked      uSecs   5Sec   1Min   5Min TTY Process

237      920000     9230598          0  0.00%  0.06%  0.07%   0 PPP Events

238       12000      295450          0  0.00%  0.00%  0.00%   0 Multilink PPP

242      964000       59094         16  0.00%  0.00%  0.00%   0 Compute load avg

245           0           2          0  0.00%  0.00%  0.00%   0 Key Proc

250       56000        4923         11  0.00%  0.00%  0.00%   0 DFS flush period

251           0         167          0  0.00%  0.00%  0.00%   0 SSH Event handle

252       72000         428        168  0.00%  0.00%  0.00%   0 DHCPD Receive

253     2660000     2958941          0  0.07%  0.05%  0.04%   0 IGMP Input

254     3948000     6148381          0  0.15%  0.12%  0.09%   0 PIM Process

255      932000     2954526          0  0.00%  0.02%  0.01%   0 Mwheel Process

256        4000        4937          0  0.00%  0.00%  0.00%   0 MRIB Trans

PID Runtime(uS)     Invoked      uSecs   5Sec   1Min   5Min TTY Process

257           0           4          0  0.00%  0.00%  0.00%   0 MFIB_cable

258     2388000    14742727          0  0.15%  0.15%  0.15%   0 MFIB_mrib_write

259        4000          10        400  0.00%  0.00%  0.00%   0 MFIB_mrib_read

261     1844000       38528         47  0.00%  0.00%  0.00%   0 NHRP

262        8000          85         94  0.00%  0.00%  0.00%   0 Tunnel Security

264      188000      295291          0  0.00%  0.00%  0.00%   0 DHCP Client

266       60000      577009          0  0.07%  0.00%  0.00%   0 IP NAT Ager

275           0           2          0  0.00%  0.00%  0.00%   0 SNMP Traps

Re: Policy-map question

Pat,

You'll need to spell out the word "five" for the show command to get the right output "sho proc cpu | inc five"

John is it possible that the CIR could be less than 2mbs on a Business  line?

Probably not, but it's best if you find the actual rate.

What am I losing by making my shaper less than the CIR? If the CIR  is 4mbs up and I set my CIR to 2, I am limiting the router, correct? So  if the line is 10 up and 3 down, what would be the right setting for  the shaper?

You are limiting the router when shaping, but you're also somewhat protecting your traffic from being dropped at the PE router. Down speeds are generally higher than the up speed from most providers (I've never seen one the opposite direction, but I guess it could be possible). In your scenario, if you had 3Mb down/10Mb up, and you had a fastethernet connection of 100Mb, you'd want to shape your traffic to 10Mb (10000000).

HTH, John *** Please rate all useful posts ***
New Member

Re: Policy-map question

No, it is 10 down and 3 up. I Screwed up. Knowing that, would I still want to shape 10000000?

So if it is 3 up, shouldn't I be shaping 3, as the shaping is done in the outgoing direction(Ithink) and that would be the upload direction correct?

sh proce cpu | i five

CPU utilization for five seconds: 8%/3%; one minute: 9%; five minutes: 8%

sh proce cpu | i five

CPU utilization for five seconds: 8%/3%; one minute: 9%; five minutes: 8

sh proce cpu | i five

CPU utilization for five seconds: 9%/3%; one minute: 9%; five minutes: 8%

shproce cpu | i five

CPU utilization for five seconds: 9%/3%; one minute: 9%; five minutes: 8%

sh proce cpu | i five

CPU utilization for five seconds: 9%/3%; one minute: 9%; five minutes: 8%

sh proce cpu | i five

CPU utilization for five seconds: 9%/3%; one minute: 9%; five minutes: 8%

sh proce cpu | i five

CPU utilization for five seconds: 9%/3%; one minute: 9%; five minutes: 8%

sh proce cpu | i five

CPU utilization for five seconds: 9%/3%; one minute: 9%; five minutes: 8%

Thanks, Pat

Re: Policy-map question

CPU utilization looks fine. I would shape to 3Mb since that's the cir and you'll get the full amount that you're paying for. Can you post the actual policy from the router?

HTH, John *** Please rate all useful posts ***
New Member

Re: Policy-map question

Here it is with 3000000:

policy-map voice_and_video

class call_setup

    bandwidth 32

class internetwork_control

    bandwidth 32

class voice

    priority 128

class video

    priority 460

class class-default

policy-map shaper

class class-default

    shape average 3000000

  service-policy voice_and_video

policy-map mark_incoming_traffic

class discover_voip

  set dscp ef

class discover_signaling

  set dscp cs3

class discover_video

  set dscp cs2

class non_voip

  set dscp default

!

Thanks, Pat.

Re: Policy-map question

Pat,

One thing that I see is that your video is in the priority class along with your voice. This usually isn't recommended because there's only 1 LLQ. You can put multiple types of traffic in the queue, but in reality the video and voice will share the single LLQ. The problem with this is when someone is watching a video that's classified by this, the queue can get filled with video and then phones will fall behind in the queue and quite possibly be dropped or at least create latency. I would recommend taking your video out of the LLQ and create a bandwidth statement for it instead.

HTH,

John

HTH, John *** Please rate all useful posts ***
707
Views
45
Helpful
20
Replies
CreatePlease to create content