Entuity - Eye of the Storm - Fault Management
You are a service manager in the network operation center. You receive a phone call from the financial controller from one of your field offices, one week before quarter close, and he says that his system is unacceptably slow. This is typical - the user says that "the network is slow" at a remote site, but you're in the NOC. How can you troubleshoot this? It could be an application or server issue, even though the user thinks it's the network. Once again, the network is "guilty before being proven innocent."
Fortunately, you were already prepared for the call. The EYE Status Summary gives you a dashboard view of the overall health of your network.
(Click on image to enlarge)
You know it can't be the switch the server is plugged into, because you would have received an alarm from EYE, showing packet corruption on the port the server is plugged into, looking like this:
(Click on image to enlarge)
You didn't receive an alarm from the server or the application running on the server, so you know it can't be the server or the application causing the problem.
So you need to look at that controller's specific machine to chase down the problem. The Find Tool allows you to do this quickly.
(Click on image to enlarge)
Now let's look at this user's traffic and fault patterns.
(Click on image to enlarge)
You check the settings of his switch port, and you see that it is set for Full 100, which is the standard for your organization. However, this user has recently upgraded his network PCMCIA card driver, because of VPN incompatibilities, and that has reset the NIC to auto duplex, causing a negotiation mismatch. There's your problem. You call the local support tech to go to the local workstation and change the setting to Full 100.
