[Top] [All Lists]

Re: [nv-l] Cisco 3750's stackwised

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Cisco 3750's stackwised
From: James Shanks <jshanks@us.ibm.com>
Date: Wed, 22 Feb 2006 09:30:46 -0500
Delivery-date: Wed, 22 Feb 2006 14:31:24 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <747d654a0602211744t16da8c5dtabe2da478d99d067@mail.gmail.com>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Are you certain that this is not a Cisco issue?
You said that when you do the demandpoll, the loopback shows as down, but
comes back up after a ping.  So it's entirely possible from what you've
described that Cisco is dropping the loopback interface after some period
of inactivity, isn't it?  Or did I miss something in your description?

If they are dropping the loopback after some period of time, then  no
amount of tinkering with netmon is going to change that  fact,  unless, of
course, you poll so frequently that they don't get a chance to drop it.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

             com>                                                       To 
             Sent by:                  nv-l@lists.us.ibm.com               
             owner-nv-l@lists.                                          cc 
                                       Re: [nv-l] Cisco 3750's stackwised  
             02/21/2006 08:44                                              
             Please respond to                                             

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@hq.doe.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@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]
  On Behalf Of Brett
  Sent: Tuesday, February 21, 2006 5:47 PM
  To: nv-l@lists.us.ibm.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

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web