We have a NetPath monitor that is overall green, however, there is a route between two points on it that is showing red, but it gives no reason as to why it's red. This isn't the first time we've had an issue with NetPath where something is in a Warning or Critical state without telling us why. No Response Time or Packet Loss thresholds have been surpassed and we can not find any reason why this link should be red.
In my opinion (and not just in NetPath, but product-wide), a Warning/Critical/Down status should never be shown without passing on why to the user. Surely there is a programmatic reason that the link is showing red, so why not pass that on to us?
Because this entire path is green, this shouldn't matter, however, there is an issue with the vendor's endpoint that this NetPath monitors and we were digging around the NetPath trying to find out if we could find a cause and this link was noticed.
Also, it shows the Transit Likelihood across this link as 150%... How can Transit Likelihood across a link ever be more than 100%? It makes no sense.
Does anyone know why this link could be red or how a transit likelihood could be over 100%? I put a ticket in, but I'm not too optimistic since I put a similar ticket in last year for something like this, but we'll see...
