4 Replies Latest reply: Feb 14, 2012 3:11 PM by Saurabh Saxena RSS

Unable to discover OS stats while using ADDM 7.5

Saurabh Saxena

Hey Guys,

 

Currently we are stuck with kind of strange issue. We are running Atrium Discovery 7.5.01 ( I know its almost EOL and going to be out of support in Oct 2012).

 

We will upgrade but just wanted to make sure we get it working first. When I create new discovery task, all it finds is IP and any remote services that are running (like tomcat webserver etc).

 

It appears its failing on WMI authentication to fetch host Details like OS, Manufacturer etc.

 

When I run mtool against that host, using same credentials as in discovery task, it fetches the data just fine.

 

I also did not get any kind of error in Details section after task completes.

 

I am wondering if there is any king of troubleshooting I am missing or any place I should be looking into.

 

Thanks,Saurabh.

  • 1. Re: Unable to discover OS stats while using ADDM 7.5
    Nikola Vukovljak

    I'm afraid I don't have an aswer to your question,, hopefully others in the community will. I would like to point out however that getting Atrium Discovery 7.5.01 working will not give you a head start when you decide to upgrade to Atrium Discovery 8.x. The two are very different products and skills in one do not translate to the other.

  • 2. Unable to discover OS stats while using ADDM 7.5
    Saurabh Saxena

    You're right Nikola and we are aware of all the things that are new/different in 8.x versions. Its just that we have this 7.5 setup and running and I was wondering if I could make it work. Weird its failing (probably) at WMI without giving any error.

  • 3. Unable to discover OS stats while using ADDM 7.5
    Alok Kumar

    Hi Saurabh,

     

    It will be helpful if you can mention what configuration you have done for Discovery Type while configuring Discovery task. You should have a look at the logs of discovery to see what message does it give. Inventory logs and Discovery logs should give you messages on the details of discovery task.

     

    Regards,

     

    Alok

  • 4. Unable to discover OS stats while using ADDM 7.5
    Saurabh Saxena

    So the issue came out to be that we enabled NMAP port scanning in discovery task config while our FW wasn't allowing this. We only requested WMI ports to be allowed over firewall while with NMAP scanning turned on, discovery opens a number of random ports to check service ports before connecting. Probably to not waste effort in unavailable ports.

     

    Once I disabled NMAP scanning, it directly connected to WMI ports available on server and was able to scan everything.

     

    We also enabled trace logs for agent and manager to find out where it was failing/doing nothing.