Why are "Self-Monitoring: Server is disconnected from Operations Management Server on <TSPS host name>" events seen? |
This can happen if the TSPS has been stopped or if the TSIM disconnects from the TSPS. To tell which, go to the TSPS and run: tssh server status If the TSPS is running, open the TrueSight.log of the TSPS to see whether the TSPS was started after the time that the event was seen. When the TSPS is started you'll see "Namaste". If the TSPS was not restarted, then the TSIM has lost connection to the TSPS around the time of the event. The event itself is generated on the TSIM machine. If this event has been seen more than once, it would also be good to check the frequency of those events. Once we know that, monitor the network during an equivalent time span. For the check, test connectivity from the TSIM to TSPS on ports 1900, 8080, and 8043 by looping (e.g. telnet tspshostname 1900). It might also be good to check resource utilization on the TSPS box over time. Get a baseline from 'top' while the problem isn't happening vs. the 'top' output during the event generation time. (If the TSPS is on Windows, use Task Manager.) -- Is CPU higher, if so on what process? -- Is real Memory usage higher than usual for one of the TSPS processes (perhaps nearing a MaxHeap limit)? Is there a firewall or load balancer between the TSPS and the TSIM? Are they both on the same subnet? What FixPack is in place? If you're unsure, run 'tssh properties list' on the TSPS. For the TSIM, run 'pw viewhistory'. |