Re: [nv-l] Cisco 3750's stackwised
2006-02-21 20:44:41
Thanks for that. Just checked the Community strings and names and those appear ok. Even tried changing the community string and still got the same problem. Any other ideas?
On 2/22/06, Evans, Bill <Bill.Evans AT hq.doe DOT gov> wrote:
I had a similar situation which resulted from case problems among the various configurations including xnmsnmpconf and the hostname
resolution. Somewhere after I added the node the case of the name changed in the /etc/hosts file and messed things up nicely. A0346K2 versus A0346k2 type of thing.
With the help of some very tolerent support folks and a lot of tracing
and debugging we eliminated everything else. It all came down to a bad community string resolution because of the names in different mixtures of case. Check it out.
Bill Evans
-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com] On Behalf Of Brett Sent: Tuesday, February 21, 2006 5:47 PM
To: nv-l AT lists.us.ibm DOT com Subject: [nv-l] Cisco 3750's stackwised
Greetings all,
Just wondering of anyone else has had this issue. We have two set's of
3750's stackwised. Each set is configure with two switches setup with the same loopback ip addr on each pair. Heres the issue:
We can snmp poll the device just fine, ping the loopback ok and the interface goes green. However whenever netmon polls the device it drops
the loopback down when its not. From here you can demand poll the switch and it shows the loopback down, but you can ping it back up, then do another demand poll and it reports the interface as being up and looking
ok. It will show green until netmon does the normal timed poll then drops it backdown again.
Anyone have any clues how to get this fixed or things I can try???
Sorry would call support but have to get the support contract reinstated
but that will take a few weeks to sort out within the company.
thanks all
|
|
|