Router down or link down

[jalonso]

Hi:

We are trying to manage a network

consisting of Cisco Routers in star configuration and Frame Relay links

with

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

Spain

[j-lau]

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....?

[jalonso]

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

JJ.-