This is a good point. I did get burned when I first installed the ISDN backup. The T1 was down for 3 days, but I had defined NTP as interesting traffic, so for 3 days the ISDN line stayed up due to NTP traffic, even though the night.
I will give try changing the OID to match the interface status. > -----Original Message----- > From: Peter Hoermann [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 11, 2002 4:17 PM > To: '[EMAIL PROTECTED]' > Subject: RE: [SA-list] Checking ISDN backup interface. > > also, > > just cause I been thinking about it > > the way you've done it, both links could still be up, but the metric would > route packets via t1 and not isdn, therefore isdn could well be connected, > but still return an "up" in servers alive, since the route as far as its > concerned is good, which has nothing to do with the isdn interface being > up > or down > > sorry to harp, but I use isdn as our links between our European offices > and > used to do a trace from servers alive using a batch file and look for an > ip > address in that trace (being the isdn interface ip add on that router), > but > as I found out when I got the isdn bill on one router which kept the link > up > (but the route as far as servers alive was good - hence returning an up), > it > wasn't really a reliable check for an isdn interface on a router > (considering the slap I gave myself on the wrist when I had to justify the > cost to my manager - for what? for nothing!) > > Peter > > -----Original Message----- > From: Jack Lyons [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, 11 December 2002 21:56 > To: '[EMAIL PROTECTED]' > Subject: RE: [SA-list] Checking ISDN backup interface. > > > I was working on this solution when I got your email. I still had the > problem of the interface appearing up even when not connected - the value > for > .iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry.ifAdminStatus > showed up for the ISDN interface. > > After thinking about it and poking around in GETIF, I found the following > OID that seems like it will work. For each route, it has a the ifIndex of > the interface that the packets will go out of to get to that destination. > I > have created a SNMP check for the specific route and set it to alarm when > the interface is set to the BRI interface. > > .iso.org.dod.internet.mgmt.mib- > 2.ip.ipRouteTable.ipRouteEntry.ipRouteIfIndex > > > -----Original Message----- > > From: Peter Hoermann [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, December 11, 2002 3:09 PM > > To: '[EMAIL PROTECTED]' > > Subject: RE: [SA-list] Checking ISDN backup interface. > > > > snmp Jack, use getif to get the oid. You can check the specific bri > > interface > > Peter > > > > -----Original Message----- > > From: Jack Lyons [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, 11 December 2002 20:58 > > 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 > > > 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 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
