The NHM Status Page

Transcript

The status bar is normally the first thing you see when you go into the Network Health Monitor. If you see a color other than green at the very top of the browser, there is a potential issue. The status color in the network section will also have the same color as the top color, which can be seen on every page of the Network Health Monitor. This network section can be expanded or contracted, and the color represents the worst-case status of the configured networks.

In this case, it's the wireless network. This line text shows that there are four disconnected, always-on devices, and that's the reason this network is showing red. If we expand the wireless network by clicking on it, highlighted in red are four disconnected, always-on devices, and the top parent is disconnected, again, because the isolated network isn't accessible. If we look at the simulator network, we see all green metrics and graphs which show the last two hours of total ping, receive, or transmit incidents for critical devices.

These are the Network Health Monitor incidents. If more than 20% of the critical devices in the network exceed their high normal limits, a red horizontal line shows the 20% mark, and hover text will tell you the exact time of any incident. In a normal situation, you will see a green in the upper area, and all the networks will also be green. This tells you you do not have a network issue. And if you are having production issues, you should look at causes other than the network.

An easy way to get more information is to get an instant PDF status report. A separate video covers the PDF report. Let's expand the system and memory section. There's information about the Java Virtual Machine free memory and the operating system free memory for the remote IntraVUE, as well as the Network Health Monitor host. There's also how much free disk space in each, and also something very hard to tell in IntraVUE itself.

It shows you the scanner switch cycle. This is the amount of time it takes the scanner to go through all the managed switch SNMP requests and responses to perform an analysis of where devices are and to resolve any conflicts. And if there's no conflicts, the scanner will move the device at the end of the scanner switch cycle, and it is the only time a move will be made. And a five-minute response time is fine.

There would be a warning if it took more than 10 minutes, and it would be bad if it was greater than 15 minutes. In the IntraVUE host information section, it gives you some version information, what the NICs subnet masks are, and what the host is. In this case, it's Windows. And it also tells us that the ARP clearing daemon is running and suggests disabling it if you don't have any PLC-5s or really old devices that can't withstand more than three ARPs in a 10-millisecond period.

You should disable it by setting the auto IP ARP clear service daemon to disabled or manual. And finally, there's a scanner setting section, which lists each network and what the top parent is. There's also a drop-down, and in the drop-down, it will list all the scan ranges of this network. It also gives you the opportunity to set an IP address other than the IntraVUE top parent, especially in the case of IntraVUE Edges.

You could put the router's IP address here, and then the maps shown by the Network Health Monitor will be from the perspective of the router, not the perspective of wherever the IntraVUE edge or Windows host exists in the network. That is the end of this video covering the status page.