Problems installing CA Unicenter Connection

Question

Hi,   I have problems installing the CA Unicenter Connection,   The servers isn't discovery in the 2d Map.   The Dell CA Monitor service is not created.   I install Connection_for_CA_3.0 and Connection_for_CA_3.1   I have Unicenter 3.1 installed in Windows 2003 SP1 Standard Edition, SQL Server 2000, IT Assistant Version 7.0.0. Please help me.   Carlos Labarca

dit001 · Answer

I have exactly the same issue but I haven't found a solution.

I think it's because the Dell connection for Unicenter requires version 1.9 or of Server administrator but this version is not supported on windows 2003 SP1. Version 2.1 is the first version supported on windows 2003 SP1.

I've contacted CA and they say it's Dell's issue. I only have hardware support with Dell so I can't contact their support team for this issue.

You may get it working without SP1 but then you're risking the security of your system. I've left it as is without hardware monitoring and hope Dell release an update for Windows 2003 SP1.

Let me know if you got any further with this issue

tester25 · Answer

Clabarca,   Do you have OpenManage Server Administrator running on the Dell servers that you are trying to discover?  If so, what version? Message Edited by tester25 on 02-03-2006 01:14 PM

dit001 · Answer

The versions I have installed myself are openmanage 4.4.0, which I believe consists of Server Administrator 2.1 (1st version supported on Windows 2003 SP1)   I think the problem is that Dell connection for unicenter only supports version 1.9 of Server Administrator.

dit001 · Answer

I have SNMP installed and configured on the managed servers. The managed servers are on the same network segment as the management station so there is no Firewall blocking SNMP traps. The NSM management server discovers the agents using the same SNMP community string as is configured on the managed servers.   I have Windows 2000 agents and SQL agents installed on the managed servers. These agents are working perfectly but I cannot get hardware info for these servers from within NSM.

tester25 · Answer

Do you have SNMP installed on the managed servers and do you have them set to accept SNMP packets from the management station?  And are the SNMP read/write communities setup properly?

tester25 · Answer

Okay. Can you install a MIB Browser on the Management Station and load the OMSA(OpenManage Server Administrator) SNMP MIB in it to do some queries against the managed nodes?

As far as I know, there is no reason why OMSA 2.1(4.4) wouldn't work with OpenManage Connection for Unicenter. The SNMP OIDs have not changed in the OMSA SNMP Extension Agent/MIB between OpenManage 1.9 and 2.1. SNMP is the method that OpenManage Connection for Unicenter uses to get hardware info from OMSA.

dit001 · Answer

I downloaded a free MIB browser from the Net and installed it on the management server. I have Server Administrator installed on the management server itself so tried that first. The MIB browser is asking for OID's and I have the walk option. The default IP address is localhost. I'm not sure what to enter in the OID field. Is there any way to find this info on the server? I guess there's a seperate OID for each hardware object. I looked in server Administrator but couldn't find this info.   This OID stuff is new to me so could you let me know which steps I need to follow? Thanks

tester25 · Answer

Here is a range of OMSA SNMP MIB OIDs that you can walk:

1.3.6.1.4.1.674.10892.1.300.10.1.1 to 1.3.6.1.4.1.674.10892.1.300.10.1.45

1.3.6.1.4.1.674.10892.1.300.10.1.9 should tell you the PowerEdge model number.

These OIDs can be found in the OMSA SNMP MIB that can be found under c:\program files\Dell\SysMgt\omsa\config in Windows or /opt/dell/srvadmin/omsa/mibs in Linux.

If you don't get any data returned from doing a walk on the OIDs that I listed above, then something is most likely wrong with the setup of the OMSA SNMP Extension Agent on your managed nodes. One possible and common cause of this is that OMSA may have been installed prior to installing SNMP on those managed systems.

tester25 · Answer

How many machines do you have discovered in Unicenter? Unicenter can take quite a while to update information about a server. If you can do this then this would be best, delete one of the Dell Servers in Unicenter and then rediscover it. You may have already tried this though. Just checking...

dit001 · Answer

I tried using the OID below and it didn't work with the company standard community string on the managed node. After changing it to public I could get the server information to appear using the MIB browser. It now looks as though Dell OMSA may require the SNMP community string to be public.   I then performed a discovery in Unicenter with the managed server community string set to public. The Dell hardware status still isn't appearing in Unicenter Explorer or the 2D map.

dit001 · Answer

Hi.

I think it's working now as it should. Thanks a lot for your help.

I set the snmp community string to public and re-installed Server administrator on a managed server. I then deleted the server from worldview and re-discovered the server. This put two objects in worldview - Dell Server Administrator and Dell Remote Access which I can now launch from within Unicenter. I guess this is the correct result. I now need to look at the event management side and set up automatic emails for hardware errors.

tester25 · Answer

Good deal.  I hope it works for you now.  Just post another message here if you need more help.  I actually learned some new stuff by trying to help you.

clabarca · Answer

Hi, I solved the problem.    The error was the community name in the Pollset Browser Thanks for your help Regards

Systems Management General

Was this post helpful?