July 13, 2012
Yesterday I found a really old DELL server in out system – PE 4600 with Server Administrator v1.0.0 on it. This version is really old and does not have some feature we use, so the decision was to install v5.5. Well, the installation did not start, it always said that the older version existed and should have been uninstalled first.Stopping the services, restarting the server or even removing the OMSA keys from registry did not help
The solution is simpler than you could have expected:
- Go to the <Server Administrator installation folder\support\omclean directory
- Run OMClean.
- Close the window prompting to reboot at the end of the process. (I’m not sure if clicking OK forces a reboot, but I does not want to test it on the production server).
- Install OMSA v5.5 (or any other version), but do not restart at the end
- Start up DSM …. services and you can use new version of OMSA
August 22, 2011
VMware ESX v4.x includes an SNMP agent that is embedded in hostd service. This VMware SNMP agent supports VMware Management Information Base (MIB) files and extends SNMP functionality.
Before version 4, VMware ESX used Net-SNMP as SNMP agent. Now it has its own agent which can be used with or without Net-SNMP. Usually, Net-SNMP is required by monitoring software. In this case it can be set up to pass any incoming requests, related to VMware, to VMware SNMP agent to get access to VMware MIBs.
This article describes how to configure both agents. If you do not need to use VMware SNMP agent, configure Net‐SNMP as you would do on a typical Linux host. If you do not need to use Net-SNMP agent, configure VMware SNMP agent to use UDP port 161 instead of 171, shown in this document
Some information can be also found here: http://www.vmware.com/pdf/vsp_4_snmp_config.pdf
Read the rest of this entry »
July 28, 2011
This post includes description of the entire process as well as a working example. The post is big, but I hope it is worth to read.
1. What We Need to Do
There are three major parts of remote installation of any software: files to install, command line to run and how to run it remotely. There will be also one additional step for SNMP to run it properly: configuration. The installation parts are the same for Windows 2000 and Windows 2003. It is completely different and way easier for Windows 2008. The configuration part is the same for all of them
Read the rest of this entry »
July 12, 2011
If you have a problem with receiving the CA Spectrum email notifications for specific alarms, you can trace the logic of alarmNotifier.
1. Log into the SpectroSERVER
2. Open up Command Prompt window
3. Run alarmNotifier with the /? option to see all the parameters
Usage: AlarmNotifier [-r <resource file>] [-n <application>]
[-tl summary|details [-tn <trace file>] [-ts <size>]]
4. Run alarmNotifier with the tracing paramenters
alarmNotifier -r servers.alarmrc -tl details -tn MyTraceFile.txt
Note: You can use your customized resource file if you have any. If you omit the –r parameter, the default .alarmrc file will be used.
5. Wait until the required event happens or simulate it
6. Stop the alarmNotifier
7. Go to \SPECTRUM\Notifier folder and open up the MyTraceFile.txt file
Note: AlarmNotifier is checking the properties of each alarm against every filter in the policy associated with the selected resource file (servers.alarmrc in this example).
Note: There are no filter names in the trace file, but they can be identified by notification data.
Note: AlarmNotifier is checking tab by tab in a filter, using logical AND between tabs and logical OR within tabs
June 4, 2011
If you do not want your CA SpectroSERVER to re-sends all existing alerts after restart, you need to make a change in Alarm Notifier configuration file.
Go to the Notifier directory, open up the .alarmrc file and find the following line
just change the value to “false” and the problem solved! Almost. If you think you can use the comment sign (#), you are wrong. Notifier ignores it and re-sends alerts even if there is another statement
Seems like “true” wins anyway :o)