Question

ADSL Sub Interface down on router

Asked by: MartynLawson

I have been experiencing some issues recently at locations where we have routers with ADSL Interfaces as the primary interface. Basically it seems that the primary interface is up and does not appear to drop, but the sub interface is showing as down/down. I have tried reloading the device, but this does not appear to have resolved the issue.

Does any one have ideas as to what might be causing this issue and how to resolve the problem?

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2009-09-07 at 02:30:19ID24712171
Tags

Cisco

,

Networking

,

ADSL

Topics

Asyncronous Transfer Mode (ATM)

,

Miscellaneous Networking

,

Network Routers

Participating Experts
3
Points
500
Comments
23

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. Routers and ADSL
    Hi We would like replace our existing dial-up ISP with ADSL. We have a 10 computer, Win98 peer to peer file/printer sharing network. It is configured using TCP/IP. Each computer has its own IP address with a common sub-ip address. I understand that to make the dsl con...
  2. adsl router
    if i use an adsl router to share a connection between multiple pc's is there anyway the isp would know the connection is being shared?
  3. router 3620 adsl
    hi could you please help we have cisco router3620 is working as adsl router the problem is the adsl or the router stop fonnctioning alone 2 or 3 times per day when i restart the router everything back to normal again,i don't know where is the problem can you help? here is the...
  4. ADSL router
    Hi, I have an ADSL connection on which I use a Speedtouch USB modem. I want to get a cheap ADSL router with an integrated modem, so I was wondering if the SMC 7904BRA (http://www.smc.com/index.cfm?event=viewProduct&localeCode=EN_PRT&cid=1&scid=&pid=1398) will...
  5. ADSL Router
    Hi Experts. I have a D-Link DSL-500T router. It keeps disconnecting to get me a new IP. Why is it doing this so often? It defeats the point of ADSL if my connection is interupted so often. This router is only temporary until my other router is fixed but i'd like to get this...

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: ikalmarPosted on 2009-09-07 at 02:34:12ID: 25273752

could you show me the logs, and the configm and interface status?

 

by: MartynLawsonPosted on 2009-09-07 at 02:55:03ID: 25273853

Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet0/0            xxx.xxx.x.x     YES NVRAM  up                    up      
FastEthernet0/1            unassigned      YES NVRAM  administratively down down    
ATM0/0/0                   unassigned      YES NVRAM  up                    up      
ATM0/0/0.1                 unassigned      YES unset  down                  down    
BRI0/1/0                   unassigned      YES NVRAM  up                    up      
BRI0/1/0:1                 unassigned      YES unset  up                    up      
BRI0/1/0:2                 unassigned      YES unset  down                  down    
Virtual-Access1            unassigned      YES unset  up                    up      
Virtual-Access2            unassigned      YES unset  down                  down    
Dialer1                    xxx.xx.xx.xxx   YES TFTP   up                    up      
Dialer2                    xx.xxx.xxx.xxx  YES NVRAM  up                    up      
Dialer255                  xxx.xxx.xxx.x   YES NVRAM  up                    up      
Loopback0                  xxx.xx.xx.xxx   YES NVRAM  up                    up      
Loopback20                 unassigned      YES NVRAM  up                    up      
=====================================================================

*Sep  7 09:22:19.023: %SNMP-5-COLDSTART: SNMP agent on host fgrp-r-esx150161-01 is undergoing a cold start
*Sep  7 09:22:19.195: %SYS-6-BOOTTIME: Time taken to reboot after reload =   63 seconds
*Sep  7 09:22:19.343: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 116 changed to down
*Sep  7 09:22:19.351: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to down
*Sep  7 09:22:19.355: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to down
*Sep  7 09:22:19.499: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 115 changed to up
*Sep  7 09:22:19.887: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up
*Sep  7 09:22:20.011: %LINK-5-CHANGED: Interface FastEthernet0/1, changed state to administratively down
*Sep  7 09:22:20.219: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up
*Sep  7 09:22:20.219: %DIALER-6-BIND: Interface BR0/1/0:1 bound to profile Di2
*Sep  7 09:22:20.219: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to 02920641933 N/A
*Sep  7 09:22:21.327: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to up
*Sep  7 09:22:51.726: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to up
*Sep  7 09:22:51.726: %DIALER-6-BIND: Interface BR0/1/0:2 bound to profile Di2
*Sep  7 09:22:51.726: %ISDN-6-CONNECT: Interface BRI0/1/0:2 is now connected to 02920641933 N/A
*Sep  7 09:22:52.809: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to up
*Sep  7 09:23:05.629: %LINK-3-UPDOWN: Interface ATM0/0/0, changed state to up
*Sep  7 09:23:06.629: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/0/0, changed state to up
*Sep  7 09:23:06.633: Di2 DDR: dialer shutdown complete
*Sep  7 09:23:06.649: %ISDN-6-DISCONNECT: Interface BRI0/1/0:2  disconnected from 02920641933 fgrp-h-crp150141-01, call lasted 14 seconds
*Sep  7 09:23:06.653: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1  disconnected from 02920641933 fgrp-h-crp150141-01, call lasted 46 seconds
*Sep  7 09:23:06.809: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to down
*Sep  7 09:23:06.813: %DIALER-6-UNBIND: Interface BR0/1/0:2 unbound from profile Di2
*Sep  7 09:23:06.861: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to down
*Sep  7 09:23:06.865: %DIALER-6-UNBIND: Interface BR0/1/0:1 unbound from profile Di2
*Sep  7 09:23:07.633: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to down
*Sep  7 09:23:07.633: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to down
*Sep  7 09:23:08.633: %LINK-5-CHANGED: Interface Dialer2, changed state to standby mode
*Sep  7 09:23:14.080: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
*Sep  7 09:23:14.084: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
*Sep  7 09:23:20.004: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
*Sep  7 09:23:20.004: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
*Sep  7 09:23:20.332: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up
*Sep  7 09:23:20.332: %DIALER-6-BIND: Interface BR0/1/0:1 bound to profile Di2
*Sep  7 09:23:20.332: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to xxxxxxxxxxx N/A
*Sep  7 09:23:21.420: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to up
*Sep  7 09:23:21.632: %LINK-3-UPDOWN: Interface Dialer2, changed state to up
*Sep  7 09:24:23.884: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to up
*Sep  7 09:24:23.884: %DIALER-6-BIND: Interface BR0/1/0:2 bound to profile Di2
*Sep  7 09:24:23.884: %ISDN-6-CONNECT: Interface BRI0/1/0:2 is now connected to xxxxxxxxxxx N/A
*Sep  7 09:24:24.984: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to up
*Sep  7 09:26:58.619: Di2 DDR: dialer shutdown complete
*Sep  7 09:26:58.635: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1  disconnected from xxxxxxxxxxx fgrp-h-crp150141-01, call lasted 218 seconds
*Sep  7 09:26:58.639: %ISDN-6-DISCONNECT: Interface BRI0/1/0:2  disconnected from xxxxxxxxxxxfgrp-h-crp150141-01, call lasted 154 seconds
*Sep  7 09:26:58.651: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
*Sep  7 09:26:58.651: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
*Sep  7 09:26:58.819: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to down
*Sep  7 09:26:58.823: %DIALER-6-UNBIND: Interface BR0/1/0:1 unbound from profile Di2
*Sep  7 09:26:58.851: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to down
*Sep  7 09:26:58.851: %DIALER-6-UNBIND: Interface BR0/1/0:2 unbound from profile Di2
*Sep  7 09:26:59.619: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to down
*Sep  7 09:26:59.619: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to down
*Sep  7 09:27:00.619: %LINK-5-CHANGED: Interface Dialer2, changed state to standby mode
*Sep  7 09:27:51.856: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
.Sep  7 09:16:34.558: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
.Sep  7 09:16:34.558: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
.Sep  7 09:16:34.990: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up
.Sep  7 09:16:34.990: %DIALER-6-BIND: Interface BR0/1/0:1 bound to profile Di2
.Sep  7 09:16:34.990: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to xxxxxxxxxxx N/A
.Sep  7 09:16:35.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
.Sep  7 09:16:36.086: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to up
.Sep  7 09:16:36.230: %LINK-3-UPDOWN: Interface Dialer2, changed state to up
.Sep  7 09:17:08.344: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to up
.Sep  7 09:17:08.348: %DIALER-6-BIND: Interface BR0/1/0:2 bound to profile Di2
.Sep  7 09:17:08.348: %ISDN-6-CONNECT: Interface BRI0/1/0:2 is now connected to xxxxxxxxxxx N/A
.Sep  7 09:17:09.452: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to up
.Sep  7 09:17:58.225: Di2 DDR: dialer shutdown complete
.Sep  7 09:17:58.245: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1  disconnected from xxxxxxxxxxx fgrp-h-crp150141-01, call lasted 83 seconds
.Sep  7 09:17:58.249: %ISDN-6-DISCONNECT: Interface BRI0/1/0:2  disconnected from xxxxxxxxxxx fgrp-h-crp150141-01, call lasted 49 seconds
.Sep  7 09:17:58.429: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to down
.Sep  7 09:17:58.433: %DIALER-6-UNBIND: Interface BR0/1/0:1 unbound from profile Di2
.Sep  7 09:17:58.477: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to down
.Sep  7 09:17:58.481: %DIALER-6-UNBIND: Interface BR0/1/0:2 unbound from profile Di2
.Sep  7 09:17:58.945: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
.Sep  7 09:17:58.945: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
.Sep  7 09:17:59.225: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to down
.Sep  7 09:17:59.225: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to down
.Sep  7 09:18:00.225: %LINK-5-CHANGED: Interface Dialer2, changed state to standby mode
.Sep  7 09:18:52.142: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
.Sep  7 09:19:24.672: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
.Sep  7 09:19:24.672: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
.Sep  7 09:19:24.936: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up
.Sep  7 09:19:24.936: %DIALER-6-BIND: Interface BR0/1/0:1 bound to profile Di2
.Sep  7 09:19:24.936: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to xxxxxxxxxxx N/A
.Sep  7 09:19:25.672: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
.Sep  7 09:19:26.020: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to up
.Sep  7 09:19:26.220: %LINK-3-UPDOWN: Interface Dialer2, changed state to up
.Sep  7 09:20:34.348: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to up
.Sep  7 09:20:34.348: %DIALER-6-BIND: Interface BR0/1/0:2 bound to profile Di2
.Sep  7 09:20:34.348: %ISDN-6-CONNECT: Interface BRI0/1/0:2 is now connected to xxxxxxxxxxx N/A
.Sep  7 09:20:35.436: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to up
.Sep  7 09:21:28.213: Di2 DDR: dialer shutdown complete
.Sep  7 09:21:28.229: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1  disconnected from xxxxxxxxxxx fgrp-h-crp150141-01, call lasted 123 seconds
.Sep  7 09:21:28.233: %ISDN-6-DISCONNECT: Interface BRI0/1/0:2  disconnected from xxxxxxxxxxx fgrp-h-crp150141-01, call lasted 53 seconds
.Sep  7 09:21:28.265: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
.Sep  7 09:21:28.265: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
.Sep  7 09:21:28.389: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to down
.Sep  7 09:21:28.389: %DIALER-6-UNBIND: Interface BR0/1/0:1 unbound from profile Di2
.Sep  7 09:21:28.437: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to down
.Sep  7 09:21:28.441: %DIALER-6-UNBIND: Interface BR0/1/0:2 unbound from profile Di2
.Sep  7 09:21:29.213: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to down
.Sep  7 09:21:29.213: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to down
.Sep  7 09:21:30.213: %LINK-5-CHANGED: Interface Dialer2, changed state to standby mode
.Sep  7 09:22:21.458: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
Sep  7 09:23:53.580: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Sep  7 09:23:53.580: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
Sep  7 09:23:53.924: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up
Sep  7 09:23:53.924: %DIALER-6-BIND: Interface BR0/1/0:1 bound to profile Di2
Sep  7 09:23:53.924: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to xxxxxxxxxxx  N/A
Sep  7 09:23:54.580: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
Sep  7 09:23:55.016: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to up
Sep  7 09:23:55.204: %LINK-3-UPDOWN: Interface Dialer2, changed state to up
Sep  7 09:24:25.359: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to up
Sep  7 09:24:25.359: %DIALER-6-BIND: Interface BR0/1/0:2 bound to profile Di2
Sep  7 09:24:25.363: %ISDN-6-CONNECT: Interface BRI0/1/0:2 is now connected to xxxxxxxxxxx  N/A
Sep  7 09:24:26.454: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to up
Sep  7 09:25:17.199: Di2 DDR: dialer shutdown complete
Sep  7 09:25:17.199: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Sep  7 09:25:17.199: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
Sep  7 09:25:17.219: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1  disconnected from xxxxxxxxxxx  fgrp-h-crp150141-01, call lasted 83 seconds
Sep  7 09:25:17.219: %ISDN-6-DISCONNECT: Interface BRI0/1/0:2  disconnected from xxxxxxxxxxx  fgrp-h-crp150141-01, call lasted 51 seconds
Sep  7 09:25:17.387: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to down
Sep  7 09:25:17.391: %DIALER-6-UNBIND: Interface BR0/1/0:1 unbound from profile Di2
Sep  7 09:25:17.435: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to down
Sep  7 09:25:17.439: %DIALER-6-UNBIND: Interface BR0/1/0:2 unbound from profile Di2
Sep  7 09:25:18.199: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to down
Sep  7 09:25:18.199: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to down
Sep  7 09:25:19.199: %LINK-5-CHANGED: Interface Dialer2, changed state to standby mode
Sep  7 09:26:05.925: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up
Sep  7 09:26:05.929: %DIALER-6-BIND: Interface BR0/1/0:1 bound to profile Di2
Sep  7 09:26:05.929: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to xxxxxxxxxxx  N/A
Sep  7 09:26:06.029: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Sep  7 09:26:06.029: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
Sep  7 09:26:07.012: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to up
Sep  7 09:26:07.196: %LINK-3-UPDOWN: Interface Dialer2, changed state to up
Sep  7 09:26:43.286: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to up
Sep  7 09:26:43.286: %DIALER-6-BIND: Interface BR0/1/0:2 bound to profile Di2
Sep  7 09:26:43.290: %ISDN-6-CONNECT: Interface BRI0/1/0:2 is now connected to 02920641933 N/A
Sep  7 09:26:44.382: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to up
Sep  7 09:27:38.191: Di2 DDR: dialer shutdown complete
Sep  7 09:27:38.207: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1  disconnected from xxxxxxxxxxx  fgrp-h-crp150141-01, call lasted 92 seconds
Sep  7 09:27:38.211: %ISDN-6-DISCONNECT: Interface BRI0/1/0:2  disconnected from xxxxxxxxxxx  fgrp-h-crp150141-01, call lasted 54 seconds
Sep  7 09:27:38.379: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to down
Sep  7 09:27:38.379: %DIALER-6-UNBIND: Interface BR0/1/0:1 unbound from profile Di2
Sep  7 09:27:38.411: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to down
Sep  7 09:27:38.411: %DIALER-6-UNBIND: Interface BR0/1/0:2 unbound from profile Di2
Sep  7 09:27:38.739: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Sep  7 09:27:38.739: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
Sep  7 09:27:39.191: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to down
Sep  7 09:27:39.191: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to down
Sep  7 09:27:40.191: %LINK-5-CHANGED: Interface Dialer2, changed state to standby mode
Sep  7 09:28:31.932: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
Sep  7 09:29:14.309: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Sep  7 09:29:14.309: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
Sep  7 09:29:14.897: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up
Sep  7 09:29:14.897: %DIALER-6-BIND: Interface BR0/1/0:1 bound to profile Di2
Sep  7 09:29:14.897: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to xxxxxxxxxxx  N/A
Sep  7 09:29:15.309: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
Sep  7 09:29:15.985: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to up
Sep  7 09:29:16.185: %LINK-3-UPDOWN: Interface Dialer2, changed state to up
Sep  7 09:29:48.443: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to up
Sep  7 09:29:48.443: %DIALER-6-BIND: Interface BR0/1/0:2 bound to profile Di2
Sep  7 09:29:48.443: %ISDN-6-CONNECT: Interface BRI0/1/0:2 is now connected to xxxxxxxxxxx  N/A
Sep  7 09:29:49.535: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to up
.Sep  7 09:36:15.160: Di2 DDR: dialer shutdown complete
.Sep  7 09:36:15.180: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1  disconnected from xxxxxxxxxxx fgrp-h-crp150141-01, call lasted 420 seconds
.Sep  7 09:36:15.180: %ISDN-6-DISCONNECT: Interface BRI0/1/0:2  disconnected from xxxxxxxxxxx fgrp-h-crp150141-01, call lasted 386 seconds
.Sep  7 09:36:15.364: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to down
.Sep  7 09:36:15.364: %DIALER-6-UNBIND: Interface BR0/1/0:1 unbound from profile Di2
.Sep  7 09:36:15.388: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
.Sep  7 09:36:15.388: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
.Sep  7 09:36:15.392: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to down
.Sep  7 09:36:15.396: %DIALER-6-UNBIND: Interface BR0/1/0:2 unbound from profile Di2
.Sep  7 09:36:16.160: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to down
.Sep  7 09:36:16.160: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to down
.Sep  7 09:36:17.160: %LINK-5-CHANGED: Interface Dialer2, changed state to standby mode
.Sep  7 09:37:08.573: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
.Sep  7 09:37:41.354: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up
.Sep  7 09:37:41.354: %DIALER-6-BIND: Interface BR0/1/0:1 bound to profile Di2
.Sep  7 09:37:41.358: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to xxxxxxxxxxx  N/A
.Sep  7 09:37:41.474: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
.Sep  7 09:37:41.474: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
.Sep  7 09:37:42.442: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to up
.Sep  7 09:37:42.474: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
.Sep  7 09:37:42.630: %LINK-3-UPDOWN: Interface Dialer2, changed state to up
.Sep  7 09:38:14.744: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to up
.Sep  7 09:38:14.748: %DIALER-6-BIND: Interface BR0/1/0:2 bound to profile Di2
.Sep  7 09:38:14.748: %ISDN-6-CONNECT: Interface BRI0/1/0:2 is now connected to xxxxxxxxxxx  N/A
.Sep  7 09:38:15.836: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to up
.Sep  7 09:40:09.621: Di2 DDR: dialer shutdown complete
.Sep  7 09:40:09.637: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1  disconnected from xxxxxxxxxxx  fgrp-h-crp150141-01, call lasted 148 seconds
.Sep  7 09:40:09.641: %ISDN-6-DISCONNECT: Interface BRI0/1/0:2  disconnected from xxxxxxxxxxx fgrp-h-crp150141-01, call lasted 114 seconds
.Sep  7 09:40:09.841: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to down
.Sep  7 09:40:09.841: %DIALER-6-UNBIND: Interface BR0/1/0:1 unbound from profile Di2
.Sep  7 09:40:09.873: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to down
.Sep  7 09:40:09.873: %DIALER-6-UNBIND: Interface BR0/1/0:2 unbound from profile Di2
.Sep  7 09:40:09.941: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
.Sep  7 09:40:09.941: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
.Sep  7 09:40:10.621: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to down
.Sep  7 09:40:10.621: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to down
.Sep  7 09:40:11.621: %LINK-5-CHANGED: Interface Dialer2, changed state to standby mode
.Sep  7 09:41:29.737: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
.Sep  7 09:41:29.737: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
.Sep  7 09:41:30.369: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up
.Sep  7 09:41:30.369: %DIALER-6-BIND: Interface BR0/1/0:1 bound to profile Di2
.Sep  7 09:41:30.369: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to xxxxxxxxxxxx N/A
.Sep  7 09:41:31.457: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:1, changed state to up
.Sep  7 09:41:31.617: %LINK-3-UPDOWN: Interface Dialer2, changed state to up
.Sep  7 09:42:01.891: %LINK-3-UPDOWN: Interface BRI0/1/0:2, changed state to up
.Sep  7 09:42:01.891: %DIALER-6-BIND: Interface BR0/1/0:2 bound to profile Di2
.Sep  7 09:42:01.891: %ISDN-6-CONNECT: Interface BRI0/1/0:2 is now connected to xxxxxxxxxx N/A
.Sep  7 09:42:02.991: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed state to up
================================================================================

Building configuration...

Current configuration : 5818 bytes
!
! No configuration change since last restart
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname fgrp-r-esx150161-01
!
boot-start-marker
boot system flash:c1841-broadband-mz.124-8.bin
boot-end-marker
!
logging buffered 64000 debugging
enable secret 5 $1$UPqa$IihAgcwdgsjd8PuWXzMgd0
enable password 7 011501064F5B54
!
aaa new-model
!
!
aaa authentication login default local group tacacs+ enable
aaa authentication enable default enable
 --More--
.Sep  7 09:49:19.801: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/1/0:2, changed saaa accounting exec default start-stop group tacacs+
aaa accounting connection default start-stop group tacacs+
!
aaa session-id common
!
resource policy
!
clock timezone GMT 0
clock summer-time BST recurring last Sun Mar 2:00 last Sun Oct 2:00
ip cef
!
!
!
!
ip tftp source-interface Loopback0
no ip domain lookup
isdn switch-type basic-net3
username
username
!
!
track 1 interface ATM0/0/0.1 line-protocol
!
!
interface Loopback0
 description ** BT Management add back to PE router ***
 ip address
!
interface Loopback20
 no ip address
!
interface FastEthernet0/0
 description **** Local LAN ****
 ip address secondary
 ip address
 duplex auto
 speed auto
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface ATM0/0/0
 description
 bandwidth 576
 no ip address
 snmp trap link-status permit duplicates
 no atm ilmi-keepalive
 dsl operating-mode auto
!
interface ATM0/0/0.1 point-to-point
 backup interface Dialer2
 no snmp trap link-status
 pvc 0/38
  ubr 288
  oam-pvc manage
  encapsulation ppp dialer
  dialer pool-member 1
 !
!
interface BRI0/1/0
 no ip address
 encapsulation ppp
 dialer pool-member 10 max-link 2
 snmp trap link-status permit duplicates
 isdn switch-type basic-net3
 isdn point-to-point-setup
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 isdn caller
 ppp authentication chap
 ppp multilink
!
interface Dialer1
 ip unnumbered Loopback0
 encapsulation ppp
 dialer pool 1
 dialer-group 1
!
interface Dialer2
 ip address
 encapsulation ppp
 dialer pool 10
 dialer remote-name
 dialer idle-timeout 0
 dialer string
 dialer load-threshold 2 either
 dialer-group 1
 ppp authentication chap
 ppp multilink
!
interface Dialer255
 description
 ip address
 encapsulation ppp
 dialer pool 10
 dialer remote-name bt_dis
 dialer idle-timeout 600
 dialer-group 2
 peer default ip address pool bt_dis_maintain
 ppp authentication chap
!
router rip
 version 2
 passive-interface default
 no passive-interface Dialer2
 network
 network
 distribute-list 99 out
 no auto-summary
!        
ip local pool  
ip route 0.0.0.0 0.0.0.0 Dialer1 track 1
ip route 0.0.0.0 0.0.0.0 Dialer2 200
!
no ip http server
ip http authentication local
ip http timeout-policy idle 5 life 86400 requests 10000
!
logging origin-id hostname
access-list 55 permit
access-list 55 permit
access-list 55 permit
access-list 56 permit
access-list 56 permit
access-list 56 permit
access-list 99 permit
access-list 99 permit
dialer-list 1 protocol ip permit
snmp-server community
snmp-server community
snmp-server community
snmp-server trap-source Loopback0
snmp-server system-shutdown
snmp-server enable traps snmp linkdown linkup coldstart warmstart
snmp-server host  snmp
snmp-server host  snmp
tacacs-server host
tacacs-server host
tacacs-server directed-request
tacacs-server key
!
control-plane

^C
alias configure ro router ospf
alias configure rb router bgp
alias exec ct configure terminal
alias exec si show ip route
alias exec six show ipx route
alias exec sb show ip bgp
alias exec sib show ip interface brief
alias exec sixb show ipx interface brief
alias exec ci clear ip route *
alias exec cix clear ipx route *
alias exec cib clear ip bgp
alias exec sbn show ip bgp nei
alias exec sbs show ip bgp summ
alias exec son show ip ospf nei
alias exec soi show ip ospf int
alias exec sen show ip eigrp nei
alias exec sei show ip eigrp int
!
line con 0
line aux 0
line vty 0 4
 exec-timeout 20 0
 password 7 104D000A0618
 transport input telnet
line vty 5 15
 transport input telnet
!
scheduler allocate 20000 1000
ntp clock-period 17178851
ntp server
ntp server
end


 

by: rochey2009Posted on 2009-09-07 at 05:37:19ID: 25274604

Hi,

Was this working before? Is this something thats happened recently?

 

by: MartynLawsonPosted on 2009-09-07 at 07:39:32ID: 25275356

Yeah, there have been no config changes on the router. The sub interface just dropped this morning

 

by: rochey2009Posted on 2009-09-07 at 07:43:04ID: 25275380

Have you spoken to your service provider to see if they've made any changes or if there's a problem at their end?

 

by: MartynLawsonPosted on 2009-09-07 at 14:40:42ID: 25277397

I have and they are telling me that there is nothing wrong with there equipment and there are no errors on the circuit that it transmits over

 

by: rochey2009Posted on 2009-09-07 at 15:11:25ID: 25277512

please can you post the results of

show atm vc

 

by: rochey2009Posted on 2009-09-07 at 15:58:02ID: 25277719

show atm pvc 0/38

 

by: MartynLawsonPosted on 2009-09-08 at 04:10:59ID: 25280559

Yeah sure,

Description: N/A
ATM0/0/0.1: VCD: 1, VPI: 0, VCI: 38
UBR, PeakRate: 288 (680 cps)
AAL5-MUX, etype:0x9, Flags: 0x24, VCmode: 0x0, Encapsize: 4
OAM frequency: 10 second(s), OAM retry frequency: 1 second(s)
OAM up retry count: 3, OAM down retry count: 5
OAM END CC Activate retry count: 3, OAM END CC Deactivate retry count: 3
OAM END CC retry frequency: 30 second(s),
OAM SEGMENT CC Activate retry count: 3, OAM SEGMENT CC Deactivate retry count: 3
OAM SEGMENT CC retry frequency: 30 second(s),
OAM Loopback status: OAM Sent
OAM VC Status: Not Verified
ILMI VC status: Not Managed
VC is managed by OAM.
InARP DISABLED
InPkts: 6738, OutPkts: 6901, InBytes: 1261511, OutBytes: 569239
InPRoc: 3623, OutPRoc: 258, Broadcasts: 0
InFast: 3115, OutFast: 2959, InAS: 0, OutAS: 0
InPktDrops: 0, OutPktDrops: 0/0/0 (holdq/outputq/total)
CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0
Out CLP=1 Pkts: 0
OAM cells received: 888
F5 InEndloop: 888, F5 InSegloop: 0,
F5 InEndcc: 0, F5 InSegcc: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 2489
F5 OutEndloop: 2489, F5 OutSegloop: 0,
F5 OutEndcc: 0, F5 OutSegcc: 0, F5 OutAIS: 0, F5 OutRDI: 0
F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0
OAM cell drops: 0
Status: DOWN, State: NOT_VERIFIED
PPP: Virtual-Access2 from Dialer1
PPPoA Current State = DOWN
PPPoA Latest  Event = Vaccess Down
PPPoA Latest  Error = None
PPPoA Session ID    = 0
PPPoA  Handle = 0x2D000001, SSS Handle = 0x00000000
Switch Handle = 0x00000000, PPP Handle = 0x00000000
AAA Unique ID = 0x00000000, AIE Handle = 0x00000000

 

by: rochey2009Posted on 2009-09-08 at 04:25:53ID: 25280662

OAM cells received: 888
F5 InEndloop: 888, F5 InSegloop: 0,
F5 InEndcc: 0, F5 InSegcc: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 2489

Can you perform the command again and check to make sure that OAM cells are being sent and received.

 

by: MartynLawsonPosted on 2009-09-08 at 04:30:39ID: 25280682

I have just checked and the cells are being sent and received

 

by: rochey2009Posted on 2009-09-08 at 04:35:51ID: 25280719

Can a do a

term mon

debug atm oam

and post the results

 

by: rochey2009Posted on 2009-09-08 at 04:36:19ID: 25280724

Please can you do:

term mon

debug atm oam

and post the results

 

by: rochey2009Posted on 2009-09-08 at 04:38:28ID: 25280744

no debug all

will switch off the debug when you've finished

 

by: MartynLawsonPosted on 2009-09-08 at 04:45:36ID: 25280802

.Sep  8 11:41:50.149: ATM OAM LOOP(ATM0/0/0) I: VCD#1 VC 0/38 LoopInd:0 CTag:0xA9E OAM Cell Type 5
.Sep  8 11:41:50.149: atm_oam_setstate - VCD#1, VC 0/38: newstate = Up Retry
.Sep  8 11:41:51.145: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:2 CTag:0xA9E Tries:0
.Sep  8 11:41:51.145: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xA9F
.Sep  8 11:41:52.145: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xA9F Tries:0
.Sep  8 11:41:52.145: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAA0
.Sep  8 11:41:53.141: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAA0 Tries:1
.Sep  8 11:41:53.141: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAA1
.Sep  8 11:41:54.137: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAA1 Tries:2
.Sep  8 11:41:54.137: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAA2
.Sep  8 11:41:54.145: ATM OAM LOOP(ATM0/0/0) I: VCD#1 VC 0/38 LoopInd:0 CTag:0xAA2 OAM Cell Type 5
.Sep  8 11:41:55.141: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:2 CTag:0xAA2 Tries:0
.Sep  8 11:41:55.141: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAA3
.Sep  8 11:41:56.141: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAA3 Tries:0
.Sep  8 11:41:56.141: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAA4
.Sep  8 11:41:57.141: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAA4 Tries:1
.Sep  8 11:41:57.141: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAA5
.Sep  8 11:41:58.137: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAA5 Tries:2
.Sep  8 11:41:58.137: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAA6
.Sep  8 11:41:58.145: ATM OAM LOOP(ATM0/0/0) I: VCD#1 VC 0/38 LoopInd:0 CTag:0xAA6 OAM Cell Type 5
.Sep  8 11:41:59.145: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:2 CTag:0xAA6 Tries:0
.Sep  8 11:41:59.145: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAA7
.Sep  8 11:41:59.153: ATM OAM LOOP(ATM0/0/0) I: VCD#1 VC 0/38 LoopInd:0 CTag:0xAA7 OAM Cell Type 5
.Sep  8 11:42:00.153: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:2 CTag:0xAA7 Tries:0
.Sep  8 11:42:00.153: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAA8
.Sep  8 11:42:01.152: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAA8 Tries:0
.Sep  8 11:42:01.152: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAA9
.Sep  8 11:42:02.152: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAA9 Tries:1
.Sep  8 11:42:02.152: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAAA
.Sep  8 11:42:02.160: ATM OAM LOOP(ATM0/0/0) I: VCD#1 VC 0/38 LoopInd:0 CTag:0xAAA OAM Cell Type 5
.Sep  8 11:42:03.152: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:2 CTag:0xAAA Tries:0
.Sep  8 11:42:03.152: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAAB
.Sep  8 11:42:03.160: ATM OAM LOOP(ATM0/0/0) I: VCD#1 VC 0/38 LoopInd:0 CTag:0xAAB OAM Cell Type 5
.Sep  8 11:42:04.152: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:2 CTag:0xAAB Tries:0
.Sep  8 11:42:04.152: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAAC
.Sep  8 11:42:05.152: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAAC Tries:0
.Sep  8 11:42:05.152: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAAD
.Sep  8 11:42:06.152: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAAD Tries:1
.Sep  8 11:42:06.152: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAAE
.Sep  8 11:42:07.152: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAAE Tries:2
.Sep  8 11:42:07.152: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAAF
.Sep  8 11:42:08.152: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAAF Tries:3
.Sep  8 11:42:08.152: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAB0
.Sep  8 11:42:09.148: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAB0 Tries:4
.Sep  8 11:42:09.148: ATM OAM LOOP(ATM0/0/0.1) O: VCD#1 VC 0/38 CTag:0xAB1
.Sep  8 11:42:10.144: ATM OAM(ATM0/0/0.1): Timer: VCD#1 VC 0/38 Status:1 CTag:0xAB1 Tries:5
.Sep  8 11:42:10.144: atm_oam_setstate - VCD#1, VC 0/38: newstate = Not Verified

 

by: rochey2009Posted on 2009-09-08 at 05:16:48ID: 25281021

Hi,

OAM is a loopback mechanism which checks the status of the pvc. If OAM messages are not being recieved frequently enough the router will take the interface down. Notice your retry count is hitting 5 reties. You need to talk to your service provider and tell them that your not receiving OAM messages properly.

 

by: rochey2009Posted on 2009-09-08 at 05:20:28ID: 25281042

Can you also post a

show int ATM0/0/0

to make sure that you don't have any input errors, frame errors or CRC errors

 

by: rochey2009Posted on 2009-09-08 at 06:05:29ID: 25281406

Hi,

You could try to turning off OAM with the following commands

interface ATM0/0/0.1 point-to-point
 pvc 0/38
  no oam-pvc manage
 !

 

by: rochey2009Posted on 2009-09-08 at 06:13:54ID: 25281479

Please ignore my previous post. Only disable OAM under the instruction of your service provider.

 

by: rochey2009Posted on 2009-09-08 at 07:31:24ID: 25282215

Did you have any joy with your service provider?

 

by: MistralolPosted on 2009-09-08 at 10:08:45ID: 25283932


you could try something along the line that rochey2009 said

interface ATM0/0/0.1 point-to-point
 oam-pvc manage keep-vc-up

This should stop oam from taking the sub interface down. It doesnt however mean traffic will work on the interface if it is down at the other end. If this is in the UK dealing with BT (the 0/38) just disble oam ;) they dont use it for anything special.



 

by: rochey2009Posted on 2009-09-08 at 11:05:57ID: 25284500

There isn't any OAM originating from the remote end so you could probably disable OAM like I said earlier

interface ATM0/0/0.1 point-to-point
 pvc 0/38
  no oam-pvc manage

 

by: MartynLawsonPosted on 2009-09-09 at 01:38:20ID: 31625633

After several lengthy and heated calls they seem to have found an issue with the circuit we utilise. After this they appear to have resolve the problem and my service has now been restored.

Many thanks for your assistance :)

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...