Cisco Cisco Prime Unified Operations Manager 9.0 White Paper
Operations Manager Deployment Best Practices
All contents are Copyright © 1992–2006 Cisco Systems, Inc. All rights reserved.
Page 86 of 112
Use the tasklist command now available in Windows 2003. Performing the command
tasklist /v /fo CSV > somefile.csv
produces information about processes,
memory, etc. This information can be loaded into an Excel spreadsheet.
7.7.1 Boot Up
It takes several minutes for the Operations Manager server to fully restart after a server
reboot. The complete boot-up sequence can be traced by going to Programs >
Administrative Tools > Event Viewer and then double-clicking on the System folder.
reboot. The complete boot-up sequence can be traced by going to Programs >
Administrative Tools > Event Viewer and then double-clicking on the System folder.
In the right pane, in the Event column, look for events with the ID 6009 followed by (in
time sequence) a 6005. This sequence tells you that the system was restarted. These two
events log the fact that the Windows event log was started up, followed by the Windows
Release version, and so on.
From this point on in the event log, you can trace the time sequence of when the various
system services (such as DCOM, IpSec, TCPIP, telephony, CiscoWorks daemons,
Tomcat, Apache, VisiBroker, DbEngines, and so on) were started.
If the Operations Manager system does not seem to be working properly, it could be due
to an improper shutdown, perhaps caused by an expected loss of power. Properly shut
down and reboot the server before calling the Cisco TAC. A reboot clears up most of
these problems.
time sequence) a 6005. This sequence tells you that the system was restarted. These two
events log the fact that the Windows event log was started up, followed by the Windows
Release version, and so on.
From this point on in the event log, you can trace the time sequence of when the various
system services (such as DCOM, IpSec, TCPIP, telephony, CiscoWorks daemons,
Tomcat, Apache, VisiBroker, DbEngines, and so on) were started.
If the Operations Manager system does not seem to be working properly, it could be due
to an improper shutdown, perhaps caused by an expected loss of power. Properly shut
down and reboot the server before calling the Cisco TAC. A reboot clears up most of
these problems.
7.7.2 Device Management Operations
The following script can be used from the Operations Manager Windows command
prompt to completely delete the Operations Manager database and clean all devices out
of the system.
prompt to completely delete the Operations Manager database and clean all devices out
of the system.
cd C:\Program Files\CSCOpx\objects\vhm\utilities
perl "C:\Program Files\CSCOpx\objects\vhm\utilities\dbclean.pl"
YES
cisco
y
y
y
y
y
net start crmdmgtd