Jack, If I understand your problem correctly, the ISDN and T1 interfaces end up at the same far-side (farthest from the Servers Alive box) IP address. So pinging that address will be of no value.
Can you add a secondary IP address on the far-side interface you want to monitor and use that address just for monitoring? If you're out of addresses based on subnetting, you could add a new non-routable address to the far-side ISDN interface and a static route on the near-side router to that address, via the near-side ISDN interface. -David -----Original Message----- From: Jack Lyons [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 2:58 PM To: '[EMAIL PROTECTED]' Subject: [SA-list] Checking ISDN backup interface. I have Servers Alive monitoring a router on the remote end of a T1. I have an ISDN backup to that router, so if the line goes down it is picked up by the ISDN backup. I want servers alive to be able to monitor the ISDN link, but I can't ping the ip address of the ISDN link because it will appear up all the time. I started working on a batch file that did a tracert and find commands, but I was wondering if anyone had a smoother solution Thanks Jack This email and its contents may be confidential. If it is and you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please delete it immediately. Thank you. To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
