Re: OEM12c Target Host Config after delete
- From: Ryan January <rjjanuary@xxxxxxxxxxxxxxxx>
- To: Ray Stell <stellr@xxxxxx>
- Date: Mon, 21 Jan 2013 16:24:40 -0600
Unfortunately I haven't been so lucky. After spending an inordinate
amount of time trying to clean everything up I decided to bite the
bullet and reinstall. I would admit that the un/reinstall process
worked much smoother than anticipated however I'm still faced with a
similar, but slightly different, issue. Now both the host *and* agent
are missing. :)
The agent appears to start up and run as expected, however it never
shows up within the OMS console. Both install and gcagent logs are
clean and bi-directional communication has been verified. I've seen a
little movement on the SR today, however no forward progress. I keep
getting told to click on the (non existent) agent link within OEM and
force a resync.
Is there any way we can flush the previous agent info from the database
allowing the agent to perform the registration process? What sequence of
events creates the agent/host/targets within OEM? Documentation states
that the host and agent are created when the first upload happens on a
new agent. My expectation is that there is some cruft hanging around
inside the repository from the old agent causing this process to not fire.
On 01/18/2013 04:08 PM, Ray Stell wrote:
> On Jan 18, 2013, at 4:44 PM, Ryan January wrote:
>
>> I'm working on a migration from OEM11 to OEM12 and running into an issue
>> with regards to host targets after removal from OEM12.
>> As a test I performed a silent install of the agent to a test server,
>> however neglected to specify the port I wanted to use.
>
> I did that, also, and did the SR thing for a long time. In the end I
> uninstalled the agent software and reinstalled the agent. It was most
> definitely the easiest path because finding out how to clean up went nowhere.
> The point of the SR, and also the MOS forum quer, on my part, was to see if
> there was a way to clean up the mess. I never did get there. I did have an
> interesting exchange here:
>
> https://communities.oracle.com/portal/server.pt?open=514&objID=224&mode=2&threadid=480580&aggregatorResults=T502648T496841T491988T480580T461590T461526T458037T451248T446352T25991&sourceCommunityId=248&sourcePortletId=268&doPagination=true&pagedAggregatorPageNo=1&returnUrl=https%3A%2F%2Fcommunities.oracle.com%2Fportal%2Fserver.pt%3Fopen%3Dspace%26name%3DCommunityPage%26id%3D25%26cached%3Dtrue%26in_hi_userid%3D46539%26control%3DSetCommunity%26PageID%3D0%26CommunityID%3D248%26&Portlet=All%20Community%20Discussions&PrevPage=Communities-CommunityHome
>
> The take home is to verify all the ports before you install. My SR on the
> topic brought me this list of checks to verify you are ready to install,
> seems overboard, but...
>
> Agent OMS Communication, on OMS host:
> --------------------------------------------
> + <OMS_HOME>/bin/emctl status oms -details
>
> + Verify the basic Network connectivity for Agent & OMS Servers: (Send me the
> output of the below commands)
>
> From the Agent server:
>> $ ping <IP adddress of the OMS machine>
>> $ ping <hostname.domain of the OMS machine>
>> $ ping <hostname of the OMS machine>
> From the OMS server:
>> $ ping <IP adddress of the Agent machine>
>> $ ping <hostname.domain of the Agent machine>
>> $ ping <hostname of the Agent machine>
> + Verify the Hostname resolution for Agent & OMS Servers: (Send me the output
> of the below commands)
>
> From the Agent server:
>> $ nslookup <IP adddress of the OMS machine>
>> $ nslookup <hostname.domain of the OMS machine>
>> $ nslookup <hostname of the OMS machine>
> From the OMS server:
>> $ nslookup <IP adddress of the Agent machine>
>> $ nslookup <hostname.domain of the Agent machine>
>> $ nslookup <hostname of the Agent machine>
> + Verify that the ports are not blocked: (Send me the output of the below
> commands)
>
> Use telnet from the Agent machine:
>
>> $ telnet omsmachine.domain 4889
>> $ telnet omsmachine.domain 1159
> From the OMS machine:
>
>> $ telnet agentmachine.domain 3872
> + From Agent machine
> wget http://<OMS_Hostname>:<EM_HTTP_UPLOAD_PORT>/empbs/genwallet
> wget http://<OMS_Hostname>:<EM_HTTPS_UPLOAD_PORT>/empbs/genwallet
>
> NOTE: You will get EM_HTTP_UPLOAD_PORT and EM_HTTPS_UPLOAD_PORT from the
> output of 'emctl status oms -details' command above.
>
>
---------------------------------------------------------------------------------------
This email is intended solely for the use of the addressee and may
contain information that is confidential, proprietary, or both.
If you receive this email in error please immediately notify the
sender and delete the email.
---------------------------------------------------------------------------------------
--
//www.freelists.org/webpage/oracle-l
Other related posts:
