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

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

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Router down or link down


We are trying to manage a network

consisting of Cisco Routers in star configuration and Frame Relay links


ISDN backups. We have Management Station with Tivoli Netview. We have some expertise with Tivoli products but not with

Cisco Routers. We are creating Trouble Tickets automatically from Netview Events.

Nowadays, we are looking at frDLCIStatusChange trap coming from Cisco

routers. This trap, as far as we know, could be generated because of the

link is down or the remote router is down.

How could we know if the problem is originated by the remote router or the

link? Is there any other trap we could evaluate in order to generate the

proper Ticket, (Router Down or Link Down)?

Any ideas would be very appreciated.

Thanks in advance,

Juanjo Alonso

Soluziona Consultoria


New Member

Re: Router down or link down

If you have ISDN back-ups and get a DLCIStatusChange trap from your local router (as opposed to the far end) why not script TEC to ping the far end managed node. (Assuming you're using dialer-maps to bring up the ISDN circuits automagically.)

After you poll the far side, f you don't match a router marginal/down trap from nvcorrd, then I'd think you can clearly state it's a problem with the cloud rather then the far-end router....?

New Member

Re: Router down or link down

Thanks, it´s a good idea if the local router brings up the ISDN circuit automatically...