"ERR: No such name" means that the remote SNMP agent doens't know the requested OID. The other issue, not sure why it happens (it could be a timeout because of the "wrong" community)
dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Don Brown Sent: Fri Dec 13 3:29 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Checking ISDN backup interface. When I click on the button, I get "Working...please wait..." then it disappears. What's strange is that my routers' community is "public" but if I use "public" on SA I get "ERR: No Such Name". When I change it to "PUBLIC" in SA, I get "Working...please wait..." Could this have any effect? Don -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Dirk Bulinckx Sent: Thursday, December 12, 2002 3:41 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Checking ISDN backup interface. Before running the actual check from SA, click on the "button" with the checks's setup, it will show the value SA retrieves from the (remote) system. dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Don Brown Sent: Thu Dec 12 8:08 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Checking ISDN backup interface. I've been watching this thread and trying to do the same thing (unsuccessfully). The only difference is that I use modems for backup. I have one router currently on dial and I see that GetIf reports .1.3.6.1.2.1.2.2.1.8.1 = down and that down is 2. So, I configure SA with that OID number, check the "Alarm when" box, and set it as "is = to" 2. Community string is PUBLIC and retries are 1. (When I click on the LAN icon, something happens, but what?) When it tests, it returns as OK (which it currently shouldn't do). I change the IP address to a different router that is working properly and I get the same result. What am I doing wrong? Don -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jack Lyons Sent: Thursday, December 12, 2002 9:41 AM To: '[EMAIL PROTECTED]' Subject: RE: [SA-list] Checking ISDN backup interface. Yes and it is pingable also. The ICMP packets go through the T1 and hit the other BRI interface. I think the SNMP check is going to work for me. > -----Original Message----- > From: James Nunnerley [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 12, 2002 7:11 AM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Checking ISDN backup interface. > > Does the other end of the interface have an IP address? > > James > > -----Original Message----- > From: Jack Lyons [mailto:[EMAIL PROTECTED]] > Sent: 12 December 2002 12:05 > To: [EMAIL PROTECTED] > Subject: Re: [SA-list] Checking ISDN backup interface. > > > The problem is that the ISDN interface is pingable whether or not it > is connected. > > Jack > ----- Original Message ----- > From: "James Nunnerley" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, December 12, 2002 3:34 AM > Subject: RE: [SA-list] Checking ISDN backup interface. > > > Surely, there is a simpler solution to this. If you have ISDN > back-up, does the ISDN interface not have an IP Address? > > If so, why not set the Dependency on the ISDN IP Address to checking > only if the normal one is DOWN. The check will then make sure the > interface is up, when everything else is down - or is that too simple? > ;) > > James > > -----Original Message----- > From: Jack Lyons [mailto:[EMAIL PROTECTED]] > Sent: 11 December 2002 20: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.ifAdminSta > tus > 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 > > 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 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
