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

Loss of IP connectivity due to Qos on ATM PVC

Hi all,

I have a 2921 series router w 15.1M series IOS. The platform has HWIC-2SHDSL module installed, which is used for point-to-point G.SHDSL connectivity. When I apply a service-policy on atm pvc, after 10 to 20 minutes I lose IP connectivity on ATM interface and tunnel interface also goes to down state. If I remove the service policy on ATM PVC IP connectivty returns back.

Interestingly I use exactly the same config on 2821 platform (w. WIC-1SHDSL installed) and I do not live such an issue on that platform.

I tried to carry the Qos config on to Tunnel interface with shaping enabled and "no qos-preclassify" command issued, but the result is the same.

What may be the cause of that issue?

policy-map MetroDSL-llq

class sna-dsl

    bandwidth percent 10

class netbios-dsl

    bandwidth percent 10

class class-default

    fair-queue

!

interface ATM0/0/0.1 point-to-point

ip address x.x.x.x 255.255.255.0

no snmp trap link-status

atm route-bridged ip

pvc 0/35

  vbr-nrt 1024 1024

  encapsulation aal5snap

  service-policy output MetroDSL-llq

3 REPLIES
Hall of Fame Super Silver

Re: Loss of IP connectivity due to Qos on ATM PVC

Hello Selman,

I would suggest to open a Service Request for this issue with TAC.

From the information you have provided you have probably hit a SW defect on the newer router

Hope to help

Giuseppe

New Member

Loss of IP connectivity due to Qos on ATM PVC

I have the same issue. I want to know if you solved this problem. I have a case in the TAC, but I have not had the solution.

New Member

Loss of IP connectivity due to Qos on ATM PVC

Hi Samuel,

Yes we solved it

In our case, there was a compatibility issue with HWIC series G.SHDSL cards and ATM DLSAMs in which our ISP uses.

We solved our issue by carrying the the DSLAM ports to another vendors devices, and also to IP DSLAMs.

Hope it helps.

552
Views
0
Helpful
3
Replies
CreatePlease login to create content