SA 2.0.1 - Error Status SA_106 SupportAssist-ComponentInstallation not availible - Enterprise Forum - SupportAssist - Dell Community

SA 2.0.1 - Error Status SA_106 SupportAssist-ComponentInstallation not availible

SupportAssist

SupportAssist
Remote monitoring and automated, proactive support

SA 2.0.1 - Error Status SA_106 SupportAssist-ComponentInstallation not availible

  • Hi All,

    i'm using the OME with the Dell Support Assist.

    OME 2.0.1

    Support Assist 2.0.1.55945

     

    In the past everything was ok. (until 26.01.2015 - last DSET's of SA)

    OME is working fine.

    All connectivity tests from SA are passed.

    Today i also created a new user like described in that post and updated from 2.0.0.x to 2.0.1

    http://en.community.dell.com/dell-groups/dell_integrated_support/f/4551/t/19606321

    I let the Support Assist Collect the Information today.

    In the Log's from SA i can see that the DSET is missing on all Servers.

    (BTW I saw that SA keep also all old DSET’s even if the Server is no existing anymore -> possible to reconfigure that he delete them?)

     

    Most Servers are discovered via WMI. That servers all have still an Error in SA. Here one part from the Logs during the discovery period:

    PeriodicCollectionLogFileAppender INFO  Dell.Services.PHome.Jobs.PeriodicCollection.BasePeriodicCollectionJob: Selected tool type DSET for svc tag XXXXXXXX
    2015-06-24 16:00:03,224: T0xPHOMEScheduler_Worker-10 ScheduledDiagnosticsJob INFO  Message=[Adding XXXXXXXX to DiagnosticThreadPoolManager]
    2015-06-24 16:00:03,224: T0xPHOMEScheduler_Worker-10 DiagnosticThreadPoolManager INFO  Message=[DSET NOT installed: Adding XXXXXXXX to the periodic collection queue]
    2015-06-24 16:00:03,349: T0xPHOMEScheduler_Worker-10 ScheduledDiagnosticsJob INFO  Message=[Added XXXXXXXX to DiagnosticThreadPoolManager]
    2015-06-24 16:00:03,349: T0xPHOMEScheduler_Worker-10 PeriodicCollectionLogFileAppender INFO  Dell.Services.PHome.Jobs.PeriodicCollection.BasePeriodicCollectionJob:Done scheduling periodical collection for XXXXXXXX | WINDOWS
    2015-06-24 16:00:03,349: T0xPHOMEScheduler_Worker-10 Dell.Services.PHome.Jobs.PeriodicCollection.BasePeriodicCollectionJob INFO  Message=[Done scheduling periodical collection for XXXXXXXX | WINDOWS]

     Or is the DSET Tool now needet on all servers?

    The other machines are discovered via WSMan (1VRTX/1CMC1000/DMZ Servers/Equallogics)

    For those machines now he say in SA: "Components will be installed" since one hour without any changes. Also in the logfile I can’t see anything like installing xyz…

     

    This is in the logs now and is repeating and repeating…   (we have only one R510)

    2015-06-24 16:45:17,660: T0xPHOMEScheduler_Worker-8 OMEQueryJob INFO Message=[Querying OME for alerts...]

    2015-06-24 16:45:17,676: T0xPHOMEScheduler_Worker-8 OMEQueryJob DEBUG Message=[OME REST service connected.]

    2015-06-24 16:45:17,676: T0xPHOMEScheduler_Worker-8 OMEQueryJob DEBUG Message=[Getting alerts...]

    2015-06-24 16:45:17,676: T0xPHOMEScheduler_Worker-8 OMEQueryJob DEBUG Message=[Using LastAlertID: -2147438908]

    2015-06-24 16:45:17,707: T0xPHOMEScheduler_Worker-8 OMEQueryJob DEBUG Message=[No alerts received.]

    2015-06-24 16:45:17,707: T0xPHOMEScheduler_Worker-8 OMEQueryJob INFO Message=[Done querying OME for alerts...]

    2015-06-24 16:49:10,116: T0xPHOMEScheduler_Worker-9 CaseQueryJob INFO Message=[Updating cases from the Server]

    2015-06-24 16:49:10,147: T0xPHOMEScheduler_Worker-9 CaseQueryJob INFO Message=[Total 189 asset tags for potential case query]

    2015-06-24 16:49:10,147: T0xPHOMEScheduler_Worker-9 CaseQueryJob INFO Message=[Need to query 0 assets.]

    2015-06-24 16:49:10,147: T0xPHOMEScheduler_Worker-9 CaseQueryJob INFO Message=[Case info stored to the cache]

    2015-06-24 16:50:08,522: T0xPHOMEScheduler_Worker-11 GetInventoryJob INFO Message=[Getting inventory Job from OME Job invoked start]

    2015-06-24 16:50:09,037: T0xPHOMEScheduler_Worker-11 GetInventoryJob INFO Message=[OME returned 259 assets]

    2015-06-24 16:50:09,100: T0xPHOMEScheduler_Worker-11 GetInventoryJob ERROR Message=[Unsupported iDRAC version per regular expression: PowerEdge R510]

    2015-06-24 16:50:09,380: T0xPHOMEScheduler_Worker-11 GetInventoryJob DEBUG Message=[Removing All CMC devices where Service Tag is Null or Empty]

    2015-06-24 16:50:09,380: T0xPHOMEScheduler_Worker-11 GetInventoryJob INFO Message=[Filtered down to 258 Dell Integrated Support supportable assets.]

    2015-06-24 16:50:09,739: T0xPHOMEScheduler_Worker-11 GetInventoryJob INFO Message=[Getting inventory Job from OME Job invoked End]

     

    Also if one of the WSMan devices have a Problem the SupportAssist create a Call. For the WMI machines not.

    I hope you can help me, or show me where is my mistake :)

    Best Regards

    Sergej

  • Sergej –

    Hard to tell what happened with limited information. Could you provide the RegistrationID from help > about and I can dig into the logs.

    The log clip shows DSET is not install, not sure if you removed it or the upgrade removed it to install the latest version and/or your system may have of had an issue downloading the latest version from the FTP location. DSET doesn’t need to be installed on all servers, just the box SupportAssist and OME is installed on.

    Install the latest version of DSET from the following link which should correct the periodic collection issue.

    http://www.dell.com/support/contents/us/en/19/article/Product-Support/Self-support-Knowledgebase/enterprise-resource-center/Enterprise-Tools/dell-system-e-support-tool

    If problem continues the best option may be to open a ticket with tech support so troubleshooting and sharing data would be easier and private

    DELL-Joe B
    Social Media and Community Professional
    #iwork4Dell

  • Hi,

    thank you for the wink with the DSET. Installed it this morning, and now he is collecting all the information.


    I will come back to you, when the job is done, and i know if everything was successful :)

    BR

    Sergej

  • Hi,

    so now the task has finished.

    I have 107 successful uploads.

    For the devices which are discovered via WSMan there is still the Status "Components will be installed" without any changes.

    The others machines have 3 different states.

    1:  2 Machines -> configured device.

    2:  55 Machines -> ? unknown

    3:  11 Machines -> Error ->  The SupportAssist can't run the collecting components, because the connection type is not supported (Error 1000_3)

    All Servers are online and are successful discovered in OME. All Servers have also the same Image and are reachable.


    In OME we have 204 devices (Servers/and 15 Equallogics). 3 warning/1 unknown.

    If i count the devices in support Assist i have 107+2+55+11= 175.

    I configure the collecting Job for today evening and on Monday we will see if the state is still the same.

    What i saw now in the Log, for one of the devices with the error:

    2015-06-26 15:02:17,545: T0x33 DsetDeviceValidationJob DEBUG Message=[Device validation of SERVERNAME.DOMAIN started ]
    2015-06-26 15:02:17,857: T0x33 DsetDeviceValidationJob DEBUG Message=[Checking whether x.x.x.x local host ip addresses]
    2015-06-26 15:02:17,872: T0x33 DsetDeviceValidationJob DEBUG Message=[DSET Argument passed for device validation of SERVERNAME.DOMAIN is -s x.x.x.x --validate 1 -u DOMAIN\USER]
    2015-06-26 15:03:33,517: T0x33 DsetDeviceValidationJob DEBUG Message=[Device validation error code of SERVERNAME.DOMAIN is 6]

    Tnx and BR

    Sergej

  • Could you provide the registration number from Help > About

    55 machines unknown, are these all the same type (WINDOWS, IDRACS?)

    When setting up collections are you selecting all Device types and Credential types in the System Logs tab?   (Windows, IDRAC).

    If you get 2 or more validation failures it will stop validating the rest and that may be why you get 55 unknowns. I would check the credentials or the device that failed to validate, make sure its reachable.

    DELL-Joe B
    Social Media and Community Professional
    #iwork4Dell

  • Since you have EQL arrays, also verify you have Lasso diagnostics tool install under

    Programs > Dell > Lasso

    If not please install Lasso

    http://www.dell.com/support/contents/us/en/19/article/Product-Support/Self-support-Knowledgebase/enterprise-resource-center/Enterprise-Tools/lasso

    DELL-Joe B
    Social Media and Community Professional
    #iwork4Dell

  • Hi,

    just installed Lasso. I have also to configure it, or it is enough only to install it on the OME Server?

    You mean the Client ID from the SA?  Client-ID m2usfnmote42rpjioc8uiouizw84cpgp

    i have 5 discovery ranges.

    1/2: Server ->only WMI and same credentials.  

    3: EQL's ->  only WSMan

    4: BladeCenter / VRTX -> Blades have a Redhat without OMSA etc (HPC Cluster) / VRTX have Windows Servers (Servers discovered in range 1)  ->only WSMan

    5:  DMZ -> only WSMan

    The weird thing is, that the machines with an error, are from the different discovery ranges.

    Also the OS, BIOS, OMSA and the IDrac(Version) have no relations, like all 2012R2 failed, or all OMSA 8.1.0.1 failed.

    On OME the credentials work fine.

    The Server from DMZ have only WSMan an Account. The DMZ have no Domain and i also don't specifies an account for that. So i think he have no rights on that machines to install the needed components?

    BR and a good Start in the new week.

    Sergej

    EDIT: i just receive an error form the SA that the update failed. No idea which update, buy i think the new SA.  Now the Status is downloading Update.

  • Hallo Dell.


    All Equallogics have an error. Internal Error. SA_101. I installed the new Lasso last week.

    Could you please answer my questions?

    And where is the Difference between "Inventory Uploadet" and "configured device"

    Br

    Sergej

  • thats all?