| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Any AIX networking gurus (related to Grid Control)?
Well DNS is not AIX specific.
Yes, the alias config your DNS folks have setup looks good.
Basically the host has a hostname (it will also have an A and reverse entry in DNS ) The alias (a CNAME DNS entry) basically points to the A entry.
This setup does give you flexibility 1)should the host need to be moved to a new server 2) for vendor HA setups (HACMP, MCSG,etc...) 3) prevents applications from being tied to hostnames, etc...But you've already mentioned these...
I wonder, was the alias ever setup correctly since you say it was resolving to the wrong host?
From: oracle-l-bounce_at_freelists.org on behalf of Thomas Jeff
Sent: Fri 6/17/2005 6:33 PM
To: Oracle-L_at_freelists.org
Subject: Any AIX networking gurus (related to Grid Control)?
I'm in between a rock and a hard place. I'm trying to install Oracle Grid Control 10.1.0.3 against a 10.1.0.3 repository on AIX 5.2. After the install, the Console screen would show two targets -- the host and the agent -- but the status/metrics were always empty. After checking logs and noticing the targets.xml did not quite look right -- I contacted Oracle Support. In a nutshell, Support said that due to the DNS configuration, the Agent discovery code thought that the host was part of a cluster configuration, which the host is most definitely not.
The particulars: hostname: indysdb05t, old primary DNS name: indysdb05tg1, alias: indysdb05t. The DNS change recommended by Support was to simply reverse the primary and alias so that the primary name resolved to the hostname and the alias being the old primary DNS name.
For some reason, the Agent code was using some 'get host by name' call that picked up the indysdb05t, then when it resolved this and got indysdb05tg1, it seems to have confused it to the point it kicked in some cluster detection code which messed up the discovery process.
Anyway, after the DNS change, the Agent discovery/Console began working correctly, much to the displeasure of the SA staff, which had been insisting all along that the Oracle code was simply buggy.
The DNS configuration set up by the SA staff is to use the hostname as the alias, with all applications (batch FTP, tnsnames.ora, etc) using this alias. The primary DNS name is basically the NIC card. That way, if something changes (a new NIC card, network error, etc), all they have to do is change the primary DNS name to which the alias resolves, and the applications do not need to change their code. The SA staff says this is the way DNS configurations are normally done. Not being a DNS/networking maven, I cannot completely assess their argument.
So, I've got Oracle Support saying our DNS has issues, and the SA staff saying the Oracle Agent code is buggy. If you are an AIX shop, I'm curious as to how your DNS configuration is defined.
Thanks.
Email: jeff.thomas_at_thomson.net
Documentation available at:
http://gkmqp.tce.com/tis_dba <http://gkmqp.tce.com/tis_dba>
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Jun 17 2005 - 22:42:11 CDT
 |
 |