<P> </P><P>I have the same problem with 6.02.</P><P>All Routers with t=
his problem are Cisco2503. I can poll all other routers correctly. What for=
type is your Router? </P><P> </P><P>Uwe Richter</P><P>synthesis GmbH<=
/P><P><BR><BR><FONT SIZE=3D2><B>"Leslie Clark" <lclark@us.ibm.=
com></B></FONT><BR><FONT SIZE=3D2>Gesendet von: owner-nv-l@tkg.com</FONT=
><BR><FONT SIZE=3D2>07.09.2001 10:00 AST</FONT><BR><FONT SIZE=3D2>Bitte ant=
worten an IBM NetView Discussion</FONT><BR><BR> <FONT SIZE=3D2>An:</FONT> <=
FONT SIZE=3D2>NV-L@tkg.com</FONT><BR> <FONT SIZE=3D2>Kopie:</FONT> <FONT SI=
ZE=3D2>"Peter Raig" <praig@us.ibm.com></FONT><BR> <FONT SIZ=
E=3D2>Blindkopie:</FONT> <FONT SIZE=3D2>NVL/Synthesis</FONT><BR> <FONT SIZE=
=3D2>Thema:</FONT> <FONT SIZE=3D2>RE: [NV-L] Demand poll times out, but SNM=
P walk works.</FONT><BR> <BR><BR></P><P><FONT FACE=3D"Monospace,Courier">Ye=
ah, that's what it looks like to me, too, except that the<BR>'Monitor...' f=
unctions work, and those do real name resolution<BR>before checking xnmsnmp=
conf. Since it is an SNMP-polled<BR>node, I suspect that the node was=
discovered by an<BR>interface that is not up or something. For a node that=
is<BR>not polled via SNMP, it would normally try all interfaces<BR>before =
giving up (I think it used to work that way, anyway). It<BR>might work diff=
erently for snmp-polled nodes.<BR></FONT><BR><FONT FACE=3D"Monospace,Courie=
r">At any rate, there is NO penalty for sharing ideas on the<BR>listserver,=
Peter. I do it all the time. We are even allowed<BR>to be wrong - someone =
will correct us, count on it!<BR></FONT><BR><FONT FACE=3D"Monospace,Courier=
">Take note: the building concensus is that it probably<BR>has something to=
do with name resolution....<BR></FONT><BR><FONT FACE=3D"Monospace,Courier"=
>Cordially,<BR></FONT><BR><FONT FACE=3D"Monospace,Courier">Leslie A. Clark<=
BR>IBM Global Services - Systems Mgmt & Networking<BR>(248) 552-4968 Vo=
icemail, Fax, Pager<BR></FONT><BR><FONT FACE=3D"Monospace,Courier">=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR></FONT><BR><BR><BR><BR><BR><B=
R><FONT FACE=3D"Monospace,Courier">Leslie, I don't want to respond to this =
since I'm internal IBM and it could<BR>be misconstrued as Gospel. But=
I had this problem once as well. Turned out<BR>the problem was with name r=
esolution. That is, the servers name would<BR>resolve to the unreacheable i=
p address and Netview would try to use it.<BR></FONT><BR><FONT FACE=3D"Mono=
space,Courier">You could ask him to try to play games with name resol=
ution.<BR></FONT><BR><FONT FACE=3D"Monospace,Courier">Peter Raig<BR>IBM Glo=
bal Services, Service Delivery Center - South<BR>Consulting I/T Specialist =
- Senior<BR></FONT><BR><BR><FONT FACE=3D"Monospace,Courier">----- Forwarded=
by Peter Raig/Raleigh/IBM on 09/07/2001 09:09 AM -----<BR></FONT><BR><FONT=
FACE=3D"Monospace,Courier"> &nbs=
p; "Barr, Scott"<BR> &nb=
sp; <Scott=5FBarr@csgsy =
To: "'IBM NetView Discussion'"<=
BR> st=
ems.com> <nv-l@tkg.c=
om><BR> &=
nbsp;Sent by: cc:<B=
R> own=
er-nv-l@tkg.co Subject: RE: [NV-L]=
Demand poll times<BR> &nb=
sp; m =
out, but SNMP walk works.<BR></FONT><BR><BR><FON=
T FACE=3D"Monospace,Courier"> &nb=
sp; 09/07/2001 08:57<BR> &n=
bsp; AM<BR> &=
nbsp; Please respond to<BR> =
IBM NetView<BR> &nb=
sp; Discussio=
n<BR></FONT><BR><BR><BR><BR><BR><BR><FONT FACE=3D"Monospace,Courier">We hav=
e a problem open with support for SNMP status polls that fail because<BR>*s=
ome* of the SNMP requests are flowing to the wrong interface. For<BR>instan=
ce, we have 3 routers in our network that get marked down and the<BR>next<B=
R>status poll marks them back up.<BR></FONT><BR><FONT FACE=3D"Monospace,Cou=
rier">After exhaustive troubleshooting, we found that the packets were bein=
g<BR>directed to an interface that was not routable from the NetView server=
. We<BR>use a loop back interface in each router and the SNMP requests were=
flowing<BR>to an address in a subnet that NetView could not reach. On the =
surface it<BR>looked like NetView was not sending the packets at all but we=
finally found<BR>the packets were going out just to the wrong address.<BR>=
</FONT><BR><FONT FACE=3D"Monospace,Courier">I would set up a sniffer/snoop =
and try and catch the SNMP activity. You may<BR>be having this problem too.=
<BR></FONT><BR><FONT FACE=3D"Monospace,Courier">-----Original Message-----<=
BR>From: Brad Martin [mailto:bmartin@MetLife.com]<BR>Sent: Thursday, Septem=
ber 06, 2001 4:24 PM<BR>To: IBM NetView Discussion<BR>Subject: Re: [NV-L] D=
emand poll times out, but SNMP walk works.<BR></FONT><BR><BR><BR><BR><BR><F=
ONT FACE=3D"Monospace,Courier">Leslie,<BR></FONT><BR><FONT FACE=3D"Monospac=
e,Courier">1. Because the node is setup for SNMP management, I get the Curr=
ent Polling<BR>Parameters and then it jumps to the first SNMP request (Get =
system<BR>identifier) which times out.<BR></FONT><BR><FONT FACE=3D"Monospac=
e,Courier">2. The monitor -> mib values -> system information w=
orked fine.<BR></FONT><BR><FONT FACE=3D"Monospace,Courier">3. I've d=
eleted all references to the router and any IP addresses from<BR>the xnmsnm=
pconf. Yet the demand poll still times out on the snmpget system<BR>identif=
ier.<BR></FONT><BR><FONT FACE=3D"Monospace,Courier">Brad Martin<BR>MetLife<=
BR></FONT><BR><BR><BR><BR><BR><FONT FACE=3D"Monospace,Courier">"Leslie=
Clark" <lclark@us.ibm.com>@tkg.com on 09/06/2001 04:03:39 PM<BR=
></FONT><BR><FONT FACE=3D"Monospace,Courier">Please respond to "IBM Ne=
tView Discussion" <nv-l@tkg.com><BR></FONT><BR><FONT FACE=3D"Mon=
ospace,Courier">Sent by: owner-nv-l@tkg.com<BR></FONT><BR><BR><FONT F=
ACE=3D"Monospace,Courier">To: "IBM NetView Discussion" <=
;nv-l@tkg.com><BR>cc:<BR>Subject: Re: [NV-L] Demand poll times out=
, but SNMP walk works.<BR></FONT><BR><BR><FONT FACE=3D"Monospace,Courier">I=
s it timing out at the very beginning of the demandpoll, or<BR>is it showin=
g the current status of interfaces, and then<BR>failing on the first snmp r=
equest?<BR></FONT><BR><FONT FACE=3D"Monospace,Courier">Does 'Monitor...MIB =
Values..System Info' time out, or work?<BR></FONT><BR><FONT FACE=3D"Monospa=
ce,Courier">Regardless, I would do xnmsnmpconf and delete the<BR>entry for =
that node, check for other entries for that node<BR>and delete them as well=
, and then demandpoll it. The<BR>demandpoll should update it with the=
right entry. You are<BR>right, what you say you are seeing does not make s=
ense.<BR></FONT><BR><FONT FACE=3D"Monospace,Courier">And.... get to 6.0.2, =
of course:)<BR></FONT><BR><FONT FACE=3D"Monospace,Courier">Cordially,<BR></=
FONT><BR><FONT FACE=3D"Monospace,Courier">Leslie A. Clark<BR>IBM Global Ser=
vices - Systems Mgmt & Networking<BR>Detroit<BR></FONT><BR><BR><BR><BR>=
<FONT FACE=3D"Monospace,Courier"> =
"Brad Martin"<BR>  =
; <bmartin@METLI =
To: "IBM NetView Discussion"<BR> &nbs=
p; FE.COM>=
<nv-l@tkg.com><BR> =
Sent b=
y: cc:<BR> &=
nbsp; owner-nv-l@tkg =
Subject: [NV-L] Demand poll<BR>times out,<BR> =
.com &=
nbsp; but SNMP walk works.<=
BR></FONT><BR><BR><FONT FACE=3D"Monospace,Courier"> &n=
bsp; 09/06/01 03:32<BR> &nb=
sp; PM<BR> &n=
bsp; Please respond<=
BR> to=
IBM NetView<BR> &n=
bsp; Discussion<BR></FONT><BR><BR><BR><BR><BR><BR><BR><FONT FACE=3D"M=
onospace,Courier">We are using 6.01 and have one router that has an SNMP ti=
meout on the<BR>demand poll.<BR></FONT><BR><FONT FACE=3D"Monospace,Courier"=
>When I do an SNMP walk on the hostname and for all IP address everything i=
s<BR>OK.<BR>When I do an xnmsnmpconf -resolve hostname / IP address -=
-- > I get the<BR>correct community string & IP addresses.<BR>When I=
to a TEST --> IP/TCP/SNMP the results are OK<BR></FONT><BR><FONT =
FACE=3D"Monospace,Courier">I've tried doing an xnmsnmpconf -delete hostname=
& IP address with<BR>xnmsnmpconf -clearCache.<BR></FONT><BR><FONT FACE=
=3D"Monospace,Courier">Any ideas as to why the demand poll would timeout?<B=
R></FONT><BR><FONT FACE=3D"Monospace,Courier">Brad Martin<BR>MetLife<BR></F=
ONT><BR><BR><BR><BR><BR><FONT FACE=3D"Monospace,Courier">=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<BR>NV-L List informatio=
n and Archives: <A HREF=3Dhttp://www.tkg.com/nv-l>http://www.tkg.com/nv-l</=
A><BR></FONT><BR><BR><BR><FONT FACE=3D"Monospace,Courier">=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<BR>NV-L List informa=
tion and Archives: <A HREF=3Dhttp://www.tkg.com/nv-l>http://www.tkg.com/nv-=
l</A><BR></FONT><BR><BR><BR><BR><BR><BR><BR><FONT FACE=3D"Monospace,Courier=
">=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<BR=
>NV-L List information and Archives: <A HREF=3Dhttp://www.tkg.com/nv-l>http=
://www.tkg.com/nv-l</A><BR>=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F<BR>NV-L List information and Archives: <A HREF=3Dhttp=
://www.tkg.com/nv-l>http://www.tkg.com/nv-l</A><BR></FONT><BR><BR><BR><BR><=
BR><BR><BR><FONT FACE=3D"Monospace,Courier">=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<BR>NV-L List information and Archiv=
|