Hi Alex -
I would suggest running through some of our community training:
No access is generally a credential issue.
Skipped (unsupported device) means that ADDM appliance has No access to the target system, the credential has not even tried. Can you ping from your ADDM appliance to your target system?
Ok. I'll try to ping skipped ones. By the way, I'm trying to install Windows Proxy and reading getting started PDF.
It says Windows proxies are downloaded as install files on page 16 but which install file? Is this ADDM install files?
because ADDM install is for Linux so where's this "install files from the applicance and installed onto the local Windows host"? I don't see Windows Proxy install file in EPD.
I don't see Windows Proxy install file in EPD.
The proxies need to be downloaded from the appliance. From discovery its under tools.
I spoke too soon... I found it and installed it. I'll try to use credential (AD) and report back to you.
Oh, by the way, after install, it tried to connect to discovery but the URL seems different.
And I wasn't able to login with system login account. Is that use different login and do you have URL (after close I can't remember the page)
You will need to login to your ADDM appliance and get its ip information (run ifconfig command as root).
Okay, I got the proxy server installed and trying to use Active Directory credential. I used my domain account to set up until service acct gets set up for the testing. So ADDM use system for login and active directory proxy server use alex. But when I ran scan, I still don't have any success
not sure what changed but before proxt set up;
no access 60
no response 70
after proxy set up;
no access 71
no response 70
Is the set up or configuration not done correctly? I followed getting started with BMC atrium discovery.
We need to break this down into steps otherwise we are just guessing at what you have configured.
Starting with Linux.
You need to have a credential set up on the host credentials page (see here).
Once that it is place, try selecting Test from the Actions options on the right of the credential and providing an IP address for one of the Linux machines. This will take you to the Credential Test page. Presumably it will fail, in which case click through the Failure link to see what the system attempt to do. This should give you some indication of what is failing.
Setting up a windows proxy is slightly more complicated. Presuming you have ADDM 8.3.x, you will need to create a Windows Proxy Pool and define the slave within the pool (see here). If you are using an Active Directory (AD) Proxy there is no need to add a Windows credential - it will use the account the same account as the running Proxy. On the other hand if you are using a Credential Proxy you will need to add credential with the windows method. Again try testing this and see what happens.
If we could see what you are getting from the tests then we may be able to help you more.
I just installed ADDM 8.3.2 and installed Windows Proxy and slave pool was added long with proxy server install.
Upon install, I ran credential test with an ip address and it failed. saying ssh, rlogin, and telent failed and stopped. I'm using AD proxy.
we have mostly windows and some unix, vmware.
If checking for Windows access you will either need to select test from the Windows proxy Test action or selecting "Test IP Access..." on the Credentials Tests tab otherwise the system will not try to use an AD proxy to access the machine.