[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::netview-nt

Title:Notes Conference for TME 10 NetView for NT NT
Moderator:TUXEDO::BAKER
Created:Mon Apr 03 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:540
Total number of notes:1903

531.0. "object color stays green" by CSC32::PITT () Fri Mar 28 1997 10:45

    
    Customer states that the object color is not changing even though the
    event log states that the object has gone away/down/critical etc. 
    It never goes red. (that's a switch!!! at least it doesn't go BLUE!)
    
    Is this a known 'thing' or should I post the usual stuff and work it
    as a brand new problem?
    
    thanks
    
T.RTitleUserPersonal
Name
DateLines
531.1TUXEDO::BAKERFri Mar 28 1997 13:555
Don't think it is a "new" thing and I don't see the same thing here.
Anything changed at the customer or is it a new installation.
I presume this is still v3.1.

Bob...
531.2TUXEDO::ROMBERGSo many log files, so little documentation.....Fri Mar 28 1997 17:2010
    Cathy,
    
    What's the polling interval?  The node down events are generated by
    netmon, not by the down node, so [if my memory serves me correctly] 
    NetView (i.e. netmon) won't discover that the node is down until it 
    is polled.
    
    kathy
    
    
531.3CSC32::PITTMon Mar 31 1997 17:3917
    
    
    Yeah..I was thinking I remember the same thing....polling interval is
    default (15 minutes) but if a node goes critical enough for us to
    get a trap on it and report critical in the event window, I would
    *think* that netview would be smart enough to turn the object red....
    (why do I think I've had this discussion before???--wow .. deja vue!!!)
    
    so, if your memory DOES serve you correctly (I don't trust mine
    anymore!) then I have a question...I could understand a node going down
    and NOT going red until the polling interval goes off and the nms
    gets no response. BUT if it's the case of the node sending a trap
    (lets say one of his circuits goes down), then why would netview
    wait for the polling interval? We already KNOW there is a problem...
    the more I think about it....the confused-er I get....