none
WS-Management Error during Discovering AIX Agent

    Question

  • Hi Team,

    we are in the process of monitoring the AIX Agent thro SCOm R2 and we are getting the below error during the installation.

    It has discoverd the Agent, faild to install the agent on AIX Server.

    WS-Management could not connect to the specified destination: (abc.domain.com:1270).

    Regards

    Nachi

    • Moved by Hengzhe Li Wednesday, October 26, 2011 9:00 PM move to new forum (From:Cross Platform Solutions for System Center)
    Wednesday, September 22, 2010 11:55 AM

Answers

All replies

  • Interesting, we are having the same issue with few of our servers running Solaris 10.

    Have you installed the CU2 ?

     

    Mathieu.

    Wednesday, September 22, 2010 3:03 PM
  • Sorry I think we have missed this thread. Do you still have the issue?

    There are a number of troubleshooting techniques around agents installation detailed in this article (and following ones) http://blogs.msdn.com/b/scxplat/archive/2010/06/10/troubleshooting-cross-platform-discovery-and-agent-installation-part-1.aspx that might help you

    • Marked as answer by Robert_Hearn Friday, December 03, 2010 6:10 PM
    Friday, October 22, 2010 3:39 PM
    Moderator
  • Hi Nachiappan M and Mathieu.

    We had the same issue with AIX 6.3.

    Searching we've found a workaround:

    http://operatingquadrant.com/2012/01/12/opsmgr-unixlinux-heartbeat-failures-after-applying-kb2585542/

    When this KB is applied, it causes the WS-Management connections to UNIX/Linux agents to fail.

    We have followed the registry editing approach but we are not happy to disable a security fix.

    You'll find a lot of information about WS-Management connections issues if you search for this KB (KB2585542).

    I haven't find, however, a definitive solution for this.

    Wednesday, September 25, 2013 1:50 PM
  • Latest update fixes this issue for SCOM 2007 R2 without having to edit the registry to disable the security fix.

    http://support.microsoft.com/kb/2783850

    Have you applied it?

    Regards,

    -Steve

    Wednesday, September 25, 2013 2:58 PM
    Moderator
  • Steve,

    We are using SCOM 2012 SP1.

    Is there a fix for this version as well?

    Thks,

    Eduardo Aguiar

    Wednesday, September 25, 2013 4:27 PM
  • Eduardo,

    It was fixed for 2012 SP1 and should not be a problem in that version without any patches.

    -Steve

    Wednesday, September 25, 2013 4:42 PM
    Moderator
  • Hi Steve.

    Unfortunately we are having this issue with SCOM 2012 SP1 and the workaround has worked. As I sad I haven't found any information about a definitive solutuon.

    Here you'll find some other people with a similar issue (it's Linux, not AIX) with SCOM 2012:

    1) http://blog.scomfaq.ch/2012/03/27/scom-2012-linux-monitoring-lab-part-3-5-agent-deployment/

    2) http://blog.coretech.dk/msk/scom-2012-linux-discovery-unexpected-discoveryresult-errordata-type-please-file-bug-report-errordata/

    Thanks for your help.

    Eduardo Aguiar

    Wednesday, September 25, 2013 7:16 PM
  • Eduardo,

    Couple things here, both the links you list are for OM 2012 which had the issue and the workaround provided resolved the issue but the latest CUs for OM 2012 fixes the issue as well and does not require the removal of the KB patch or the registry edit. For OM 2012 SP1 this was fixed and worked with the KB patch applied and no registry edits out of the box.

    Having said this, I went ahead and built out a new Windows server 2008 R2 with the latest patches available (KB2585542 included and no modifications to the registry) and installed the RTM version of OM 2012 SP1. I had no issues discovering and managing AIX 5.3, 6.1 or Linux once I installed the management packs.

    For your issue we believe it may have something to do with the ciphers the AIX server is trying to negotiate by default. Did you have other systems discovered and managed prior to applying the registry edit? Can you provide your SCOM environment so I can compare it to what I'm testing with? Do you have the exact error that was generated when it failed to discovery/manage the AIX 6.3 system?

    Thanks,

    -Steve


    Thursday, September 26, 2013 6:11 PM
    Moderator
  • Steve, first of all, thanks for your time.

    I've removed the registry entry (i.e. I reactivated the KB) and removed the AIX machine from SCOM.

    When I readded it to the SCOM, the discovery and the agent installation ocurred with no issues.

    Then I added a new AIX machine to the SCOM and the discovery and the agent installation ocurred with no issues as well.

    I can't say why this didn't work at the beginning, but it's working now.

    I'll report any news here if I have other issues about this.

    Att,

    Eduardo Aguiar

    Tuesday, October 01, 2013 2:58 PM