This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Interface down status icon on node icon even when interface is not monitored

We only want to monitor and show status on critical interfaces (links to other switches and non-transient network devices) on our switches; so we list the resources on the switch and deselect all but the critical links which supposedly turns off monitoring of those interfaces.  But if one of those non-monitored interfaces goes down, we sometimes get a red icon on the node icon.  If you expand (from Managed Node View, for instance) the interfaces on the device, they all show green (because all monitored interfaces are up), but the red icon is still overlayed on the node icon.

Any ideas why this is happening and maybe how to stop that behavior?

  • Just to see if this is what you are doing,

    Pick up a switch X and navigate to the "Node Details" page

    Then select "list resources" and say pick one of them and deselecting it.

    Then you submit and get back to the Node details page for the same Switch X.

    There you see the "Node is Down"(red color).

    If this is exactly the problem then I would recommend to open a support ticket to investigate further.If not please explain the steps involved .At the same time are you able to ping the switch from the NPM server.

  • Correct except the last line: it's not "node down", it's "child" (interface) down (if the interface de-selected is in fact down).

     

    In other words: Why is the node showing interface down when the interface that is down is not being monitored?

  • Got it.I tried to replicate this on my lab.Here is what I observed.

    I followed the steps mentioned in my last thread response.Just a recap,I selected a switch and moved to Node details page.I did list resources wherein I went on and deselected one of its child interface.Then I logged into the database quickly and looked up for the table "Interface".I found the child interface was no more in the interface table.

    Coming back to the GUI and also referring to the statement in your last thread " Why is the node showing interface down when the interface that is down is not being monitored?".I did a list resource and found the interface which I unselected appeared unselected itself.Coming to the exact problem,I unselected a child interface which was up(green) at the first place.And then when I came back after this interface disappeared from the "Interface" table in the database,it still showed unselected Up(green) in the GUI.

    So I am not sure if you had time to test just one interface or a few more interface before reporting the problem.I would like you to go-head and test a few more,probably try unselecting a down(red) and a up(green) interface and get back with the results.

  • I'm still not sure you have this.  It's pretty simple:

     

    1. Monitor a switch which has devices connected to it (so that interfaces are up)
    2. select the switch in Managed Node view
    3. List Resources
    4. uncheck (deselect) all of the interfaces and submit
    5. go to the switch and disconnect one of the interfaces so that it is 
    6. The Managed Node view for the switch should show the node up, but a child (interface) down (small red icon overlaying larger green icon.
    That's what happens for me.

  • Karl,

    I need you to run the following SQL query and record the results.

    SELECT * FROM Nodes WHERE GroupStatus like 'Up-%.gif' and not exists(SELECT 1 FROM Interfaces WHERE Interfaces.NodeID=Nodes.NodeID and Interfaces.Status<>'1')

    I then need you to open a support case with the results. 

  • Also: don't have time to figure out how to find the ticket (Portal is broken, won't display existing tickets, I've been told it's my problem even though it happens with all browsers including IE 7) and attach the results.  Clues would be appreciated.

  • Karl,

     

    I just grabbed your case.

     

    Jamie

  • Can you tell me what the resolution to this issue was?  We are experiencing the same issue in a client environment.

    Thanks,

  • Chrystal,

     

    Support had me run a script which cleaned it up.  Since I've seen it pop up again, I surmise this is a bug.  Not sure if it was cleared up in the latest release.

     

    -ktb