"red" Devices in cause of interfaces without a link

Started by Tom, February 27, 2008, 06:10:40 PM

Previous topic - Next topic

Tom

Hi,

I'm new to NetXMS and in the test phase for company.

I have the following problem:
My discover works great, I think everything is discovered as it should. But I have many networks that appear "red" in the map overview, because there are a lot of access-switches in that network with down interfaces.

How is it possible to turn off the status propagation of these interfaces (e.g. cisco catalyst 2950, Port 1-24 not relevant, Port 25 is Uplink)?
In my opinion the only state change of the network should be when the switch itself is not responding to the poll.

Can anybody help me?

Thanks in advance,

Tom

Victor Kirhenshtein

Hello!

You can put interfaces you are not interesting in into "unmanaged" state - then they will be excluded from polling or status calculation. To do so, select interface object in object browser, right-click on it and select "Unmanage". Alternatively, if you need to unmanage multiple interfaces at a time, select switch object in object browser, open "Subordinates" tab, select all interfaces you wish to unmanage, right-click and select "Unmanage".

Best regards,
Victor

Tom

Thank you for the quick reply.

surely its possible to set the interface to status "unmanaged". If this is the only way I will do so.

I was surprised because all the other management tools we tested, for example Network Node Manager, do not set the access-node to red if the interfaces went down. I'm wondering now how this is done, because the links in the core are displayed correctly when they go down.

I have to think about this :)

Victor Kirhenshtein

#3
I didn't play much with new NNM 8i, but NNM 6.x and 7.x uses a slightly different approach - status of a node is depending on number of interfaces being down - for example if less than half of interfaces is down node status will be Minor, and if more than half is down - Major. If talking anout HP management products, we use approach similar to OpenView Operations - by default parent object's status equal to most critical child status, but you can change this by changing status propagation and/or calculation properties for either parent or child object.
For example, setting status calculation mode for switch node object to "multiple thresholds" and setting thresholds to Warning 0.1, Minor 0.2, Major 0.5, Critical 0.9 will give you kind of NNM-like status calcualtion for switch node.

Best regards,
Victor