Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

MapMaker - Network Links

When creating network links, I see how to point the link to one node so the status can be dependent on that node, but network links always depend on atleast two nodes. If either side of that link goes down, then the link itself is down. How can a represent this on the map?

-Charles

Find more posts tagged with

Accepted answers

All comments

qle

You can associate the network link to the corresponding interface on one of the nodes.

chaldz

But what happens if the interface I have the link watching isn't the one that goes down, then the link still shows it's up. Also, if the node itself goes down, then the interfaces show up as 'unknwon' and the link still shows its up.

-Charles

qle

I don't think there's a problem if the interface is "unknown" but the node is down. I think the idea is that we know the link is not at fault so obviously, we should be checking out the node whose icon should be flashing red at that point. What's the point of having both the network links AND the node icons flashing red?

I guess another suggestion would be to create two links, one for each interface on both nodes. Or maybe a compromise would be to have the link represent the remote interface. That is, the interface that is farthest downstream from your poller, if that makes sense. That way, even if the local (closest) interface goes down, your poller still won't be able to reach the remote interface.

tobyarnett

I am a little unclear about what your asking. It sounds like you need to add more links, but if I am mistaken the other situation you could do is to change the nodes to resemble pictures (routers, switches.. ect..) then use the small circle connector (as "unknown") in the middle of your two nodes. You can then link a connection from a node to the circle connector on each side. This way you will be able to monitor your node itself and each respective connecting interface.

X = node
-- = linke
o = connector

Node (e0) (e1) Node
X-----------------------o-------------------X

chaldz

What I was originally saying was that a link depends on two sides to be up and if either side (node) goes down, then technically the link is down as well. However, when you create a link, the status of the link is only determined by pointing it to one device, not both.

I understand there is another way of looking at this which is if a link is up and the node is down, it's not the links fault if you have the link pointed to the interface...so an interface can be down, but the node can be up or vice versa. Hope that makes sense...

I like you idea tobyarnet, create a connector in the middle so that you visually see that when a interface is down on either side, at least part of the link will reflect this.

I still would like to have the link show 'down' when it's connected to a interface and the node is down. Currently when a node is down, the interfaces are 'unknown'.

-Charles