I will do some testing to verify the values when the line is up or not, but I think I have it correct now.
Thanks for your help. ----- Original Message ----- From: "Peter Hoermann" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, December 12, 2002 5:01 AM Subject: RE: [SA-list] Checking ISDN backup interface. > Just so we don't confuse the issue, servers alive tells me my isdn is "Down" > (in reality in means the isdn link is up or connected, which is what I want > to be warned about) > > Jack > > I have a mixture of Cisco 3640, 2509, 2621 7509, 800 > > The oid is the same up to this point > > 1.3.6.1.2.1.2.2.1.8. > > After that, the interface number for the last digit changes depending on how > many interfaces are in the router and what number the isdn channels are > given. > > ON some, eg 800 it's 2 & 3 after the 8 above BRI0/0:1 & BRI0/0:2 , 1 being > the BRI0/0 Link access Protocol D > > Full length - 1.3.6.1.2.1.2.2.1.8.2 > ON another router, the last digit is 12 & 13. > > I ended up double checking entry numbers by bringing the link up and > individually checking the entries using the check button (the little icon > with 5 computers bottom right on the setup of entry Checks\SNMP panel. Some > of the routers returned a 5 when up, some returned a 2, again it depended on > what model of router. Once the link was up and I had the value, my check > was then via SNMP to alert me as down when the return value was not = to 2 > > By checking both sides of the router, I am alerted by servers alive that my > T1 is down (which puts the isdn BRI checks into down on the remote side, but > also tells me when back up and routing at both ends across isdn. Then the > reverse status when all comes back up. Lets not address dependencies, that > is dependant on your topology and location of the servers alive box. I've > only chosen the critical items to SMS to me (in case I'm out for the > evening) on downs and ups (since we run VPN over internet, there are > occasionally some little flaps occurring form time to time bringing the isdn > up, although dialler time schedules help stop that over the weekend and > evenings) > > Hope this helps and we can put this one to rest > > Peter > > -----Original Message----- > From: Dirk Bulinckx [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, 11 December 2002 23:18 > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Checking ISDN backup interface. > > > The B channels of the ISDN? If they are down, then the ISDN connection is > actualy not running. So if you would check these via SA, you could get an > alert when they are not down (aka UP). > > > dirk. > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of Jack Lyons > Sent: Wed Dec 11 11:13 PM > To: '[EMAIL PROTECTED]' > Subject: RE: [SA-list] Checking ISDN backup interface. > > > When I check the status of > .iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry.ifOperStatus for > the BRI3/3 interface it returns a value of 5 which I assume means it is up > (spoofing). I assume it will go to status up when it is actually connected. > > I also noticed that I can monitor both B-channels independently and they are > both listed as down? > > Jack > > > -----Original Message----- > > From: Jack Lyons [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, December 11, 2002 5:09 PM > > To: '[EMAIL PROTECTED]' > > Subject: RE: [SA-list] Checking ISDN backup interface. > > > > 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 > > > 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 > 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
