I recently found that on one of our busiest SCOM deployments, that certain Dell servers had not been discovered by the Dell Server Management Pack.
The primary requirement for the Management Pack to operate, is to have Dell Open Manage Server Administrator 6.2 or higher installed when using the most recent Dell Server Management Pack (Version 5.1).
For us, this was a recently installed Windows 2012 server which had a disk that was in a predictive failure state. As the server had not been discovered we missed this alert, luckily it was just a predictive failure not a failed disk / RAID array!
So to fix the issue plenty of troubleshooting was done! In our case the following helped address the issue!
I had noticed that the list of management packs the non discovered server had in
"C:\Program Files\System Center Operations Manager\Agent\Health Service State\Management Packs"
differed from a server that was discovered, so it was then obvious a discovery had failed to obtain the remainder of the required management packs.
Within authoring, i set the scope to the Dell management packs, and selected object discoveries.
Locate the following discovery -
Create an override for all objects of the class: Windows Computer
Changing the interval to something less that a day! Additionally set the Log Level to 1.
This will create a file called "Discover_DellServer.log" in the folder "c:\Windows\Temp"
When reading the contents of the log, a rather obvious error was on show!
"ERROR: UnManaged Server object created. Reason: Failure error while connecting to root-cimv2-Dell namespace."
After some searching through various posts, this post led me to the fix.
Even though it was based on an older version of omsa, the folder structure and file name is now native 64 bit. So within the path "C:\Program Files\Dell\SysMgt\omsa\config", is a file called "dccim64.mof".
Add "#pragma autorecover" in the first line of the file, and then run
mofcomp dccim64.mof from a command prompt to import the new data.
Restart the System Center Management Service on the server in question and let the discovery occur.
For me the log didn't have the issue as before. The additional management packs were then downloaded to the server. The server didn't appear in the "Dell Unmanaged Servers" group anymore, but did appear in the In-band server view of the console as expected!!
Gareth Grimshaw Azure Blog
All things Azure!!
Tuesday, 12 November 2013
Friday, 21 June 2013
HP Storage Management Pack 3.0.1 using P2000 SAN.
Today was the first time of using the HP Storage Management Pack 3.0.1
The plan was to get the Management Pack to monitor a HP P2000 SAN that was used for hosting a Hyper-V Cluster.
Having gone through the Management Pack guide and set all the pre-requisites, the HP Storage Management Pack User Configuration Tool resulted in the following when adding the storage device :-
The problem was that the SAN was installed with SMI-S set to encrypted, and there is no option in the configuration tool to specify to use encryption.
On the SAN configuration, the following was set
The plan was to get the Management Pack to monitor a HP P2000 SAN that was used for hosting a Hyper-V Cluster.
Having gone through the Management Pack guide and set all the pre-requisites, the HP Storage Management Pack User Configuration Tool resulted in the following when adding the storage device :-
No matter what username and password was entered, red exclamation marks were present, and when hovering over them, this message was shown
On the SAN configuration, the following was set
Under Storage Management Initiative Specification (SMI-S), change the option to Unencrypted. Alternatively using the CLI interface of the SAN run
set protocols smis disabled
then
set protocols usmis enabled
Once the remainder of the management pack guide was completed the magic appeared in the Operations Manager Console :-
Also the P2000 now has a diagram view showing comprehensive coverage of the individual components.
Links
Subscribe to:
Posts (Atom)