Dave,
Is your router showing as down or maybe in alarm mode? I have a similar
issue with many end nodes sporadically going into alarm mode due to
packet loss but when I check into it I can't find anything wrong and
everything is working fine. I have come to the best guess conclusion
that it's probably the NIC card on the PC I have Intermapper running on.
If the NIC card is losing packets then it will probably show as a
mis-reading on the map. Now I could be totally wrong but because of this
I have decided to move Intermapper to an empty blade server I have along
with all my other tools. I had to find an excuse to fill it up with
something anyway...

Don Goodhue
Union Bank of Vermont

-----Original Message-----
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Stewart
Sent: Tuesday, November 27, 2007 6:55 PM
To: InterMapper Discussion
Subject: [IM-Talk] reboot machine saves network?


Hi everyone!

I have an interesting observation I've been making recently and am  
wondering if anyone else has an idea about this. We're running  
Intermapper 4.6.4 (build 7A221) on a 1.42GHz G4 mini with 512MB RAM  
and running OSX 10.4.11. I've occasionally noticed our map complaining  
that our main router was bouncing (down/up) 10 times within a half an  
hour and dropping 36% of it's packets, but no one seems to notice a  
degradation on the network (everything seems fine, network is  
definitely up and running). I can even ping the router (in fact I can  
even ping *through* this router to public servers) from this machine  
through one of these dropouts and my ping tests don't lose even one  
packet. The map continues making this claim until I restart the  
machine itself, then the complaints go away and the router looks fine  
for roughly another week, when the pattern repeats.

I've taken a look into the Intermapper detailed logs for network  
events, but that doesn't reveal many surprises - it's logging the  
router going down (usually for 24 or 27 seconds, occasionally 57  
seconds) until the reboot, then the problem magically goes away.  
Admittedly some of the logs are flashing by so quickly it's hard to  
catch them all (it's a busy map:)), but I don't think it's revealing  
*why* it's having a problem.

Interesting and revealing is the fact that it doesn't complain about  
the routers at remote sites, which all end up going through our main  
router to get to our server.

Anyone have any ideas what this could be? I'm starting to doubt that I  
have a networking issue that no one has noticed yet and am starting to  
think that Intermapper is having some issue it hasn't had before. I  
haven't noticed any other symptoms on this machine (nor have I noticed  
any issues with the network, which I would since this is our main  
router), although it's not a very busy box (Intermapper, secondary DNS  
and gathering some performance characteristics from another server are  
it's only real functions).

Looking forward to investigating any ideas that come my way ...


Dave Stewart
Aqua~Flo Supply (Goleta CA)
dstewart at aquaflo dot com

"10 percent of computer users are Mac users,
but remember, we are the top 10 percent."
     - Douglas Adams



____________________________________________________________________
List archives: 
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]

____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]

Reply via email to