Cluster Name Resolution and failover

We are running a cluster consisting of two managed servers and one
          admin server on Solaris using WebLogic 6.1 SP3. The application is
          composed of EJB's only. Each managed server has been assigned a DNS
          name (host names weblogic-cluster-ma & weblogic-cluster-mb). A
          cluster address (DNS name weblogic-cluster) has been setup to
          round-robin amongst the two IP's assocaited with the managed server
          that are participating in the server.
          If I do a nslookup on the same cluster name successively, I get two
          different IP addresses.
          The behavior that I am observing is as follows:
          1. When all instances participating in the cluster are running
          everything is fine. The clients are able to connect to the machine
          using the cluster name while doing the JNDI lookup.
          2. When one of the servers participating in the cluster is down, and
          the cluster name is used to access it (the round-robin DNS name),
          depending on which machine is down, all calls either get through or
          none of them get through.
          I do not want to use the following cluster aware syntax to access the
          cluster
          t3://weblogic-cluster-ma,weblogic-cluster-mb:7001
          Instead I would like to use the cluster name
          t3://weblogic-cluster:7001 and have transparent failover.
          It would appear to me that if I have DNS return me back all the IP's
          associated with the cluster then my problem would be solved.
          for example:
          nslookup weblogic-cluster.
          216.33.240.47, 216.33.240.12
          Is this possible? How have others solved this problem.
          Thanks for your reply!

Aaravali,
          What you describe should work. However, could you clarify statement
          #2, specifically, "all calls either get through or none of them get
          through." Do you mean that the client either works or it simply fails?
          Are you failing on creating the initial context?
          Regards,
          Simon
          Developer Relations Engineer
          BEA SupportAaravali Karavali wrote:
          > We are running a cluster consisting of two managed servers and one
          > admin server on Solaris using WebLogic 6.1 SP3. The application is
          > composed of EJB's only. Each managed server has been assigned a DNS
          > name (host names weblogic-cluster-ma & weblogic-cluster-mb). A
          > cluster address (DNS name weblogic-cluster) has been setup to
          > round-robin amongst the two IP's assocaited with the managed server
          > that are participating in the server.
          >
          > If I do a nslookup on the same cluster name successively, I get two
          > different IP addresses.
          >
          > The behavior that I am observing is as follows:
          >
          > 1. When all instances participating in the cluster are running
          > everything is fine. The clients are able to connect to the machine
          > using the cluster name while doing the JNDI lookup.
          > 2. When one of the servers participating in the cluster is down, and
          > the cluster name is used to access it (the round-robin DNS name),
          > depending on which machine is down, all calls either get through or
          > none of them get through.
          >
          > I do not want to use the following cluster aware syntax to access the
          > cluster
          >
          > t3://weblogic-cluster-ma,weblogic-cluster-mb:7001
          >
          > Instead I would like to use the cluster name
          > t3://weblogic-cluster:7001 and have transparent failover.
          >
          > It would appear to me that if I have DNS return me back all the IP's
          > associated with the cluster then my problem would be solved.
          >
          > for example:
          >
          > nslookup weblogic-cluster.
          >
          > 216.33.240.47, 216.33.240.12
          >
          > Is this possible? How have others solved this problem.
          >
          > Thanks for your reply!

Similar Messages

Find monitor instance name , device name , resolution and frequency of multiple monitors (VGA and HDMI)

hi,
In my system multiple monitors are connected (VGA and HDMI). In need to know the
monitor instance name , device name , resolution and frequency of each monitor.. any solution?
i used wm class 'WmiMonitorConnectionParams' to determine Video output technology connection type and InstanceName.
But i didn't get the device name , resolution and frequency of each monitor.??
There are other wmi class like :
WmiMonitorBrightnessEvent
WmiMonitorConnectionParams
WmiMonitorRawEEdidV1Block
WmiMonitorListedFrequencyRanges
WmiMonitorDigitalVideoInputParams
WmiMonitorAnalogVideoInputParams
WmiMonitorID
WmiMonitorBrightnessMethods
WmiMonitorBasicDisplayParams
WmiMonitorColorCharacteristics
WmiMonitorDescriptorMethods
WmiMonitorListedSupportedSourceM…
WmiMonitorBrightness
WmiMonitorColorXYZinCIE
WmiMonitorSupportedDisplayFeatures
WmiMonitorBasicDisplayParams
Win32_VideoController
Win32_VideoConfiguration
Win32_VideoSettings Win32_DisplayControllerConfiguration
Win32_DisplayConfiguration
But unable to determine monitor having its corresponding values? please help me to find a solution .
is there any other method to get multi monitor details?
thank you

Hi sumith,
I read some documents about WmiMonitorConnectionParams class, it should be able to get the video putput technology by the D3DKMDT_VIDEO_OUTPUT_TECHNOLOGY enumeration.
D3DKMDT_VIDEO_OUTPUT_TECHNOLOGY enumeration
So what happens when you are using WmiMonitorConnectionParams class? What prevent you? Anyway, please see a example of using WmiMonitorConnectionParams class, maybe you could get some hints on it.
http://stackoverflow.com/questions/10085900/querying-wmi-for-d3dkmdt-video-output-technology
Best regards,
Shu Hu
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Enabling Firewall breaks Bonjour name resolution (and other problems)

Hi there, I thought I had a simple setup but trying to enable VPN & Firewall has shown me there are some issues I need help with:
Setup: MacOS X Server 10.5.8 on MacPro
- Machine is Mobile Account Server for 5 other machines connected to network
- DHCP is obtained from Router in 10.1.10.x range. Server hardcodes its IP in that range (outside of DHCP addressable range)
- Services running are: AFP, Open Directory, SMB, Software Update
- All client workstations connect to server using "servername.local"
This has all been working fine. However over the weekend I tried enabling VPN as we have a public IP address we can use. VPN works fine except:
a) Plugging an additional ethernet cable into port 2, and configuring that port to have the external "public" IP information caused the "license in use issue" that has been reported here (http://discussions.apple.com/thread.jspa?messageID=9958588&tstart=0) so I had to use the solution of duplicating the existing ethernet config and entering the additional external IP to run both off the same port.
b) I can't get L2TP working, but I can get P2PP. Seems like other people are having similar issues (http://discussions.apple.com/click.jspa?searchID=-1&messageID=9704644)
But anyway, so I have P2PP VPN working and without a firewall previous functionality hasn't been impacted. Now of course, I'd be silly to leave this machine with the Firewall turned off as it is now a sitting duck out on the inter-tubes.
I thus enabled the Firewall service with these settings:
- Any service: Allow only traffic from "any" to these ports: (I enabled the ports for P2PP and L2TP)
- 10-net: Allow all traffic from "10-net"
This I assume would restrict access from the external interface, but let all internal subnet communication be unrestricted (like it was before I enabled the firewall). However this doesn't seem to be the case. I noticed that simple non-VPN connections to AFP service took a long time to happen using "afp://servername.local", several minutes before the authentication dialog appeared.
Furthermore if I brought up "Software Update" on a managed client set to pull from "servername.local:8088", the connection would fail.
If I disabled the firewall service, the slowdown and local Software Update would work fine.
But if I try setting: "Allow all traffic from 'any'" on the Firewall (which should be almost like turning it of) it doesn't have a positive effect and slowdown of name resolution and failure to connect to local software update still occurred.
Is there something in the Firewall being enabled that breaks Bonjour name resolution? Anyway to enable the Firewall and still keep Bonjour .local name resolution? Does this problem have anything to do with issue (a) we have to work-around?
Thanks for any recommendations,
Matt

Hi Flanjman,
Additional this article may give you more tips.
https://connect.microsoft.com/SQLServer/feedback/details/674454/name-resolution-not-yet-available
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Jms in cluster / load balancing and failover

          Did I get it right ???
          I have 1 admin server and 4 managed servers in a 2 clusters, a development cluster
          and a test cluster.
          I now want to have loadbalancing with my jms server and I want to be able to migrate
          my jms server in case of failer.
          for each cluster I have created
          connectionFactory targeted to the cluster
          Distributed destination with 2 queue members
          One JMSServer migratable targeted on managed server 1, with destination 1 from
          the ditributed destination
          One JMSServer migratable targeted on managed server 2, with destination 2 from
          the ditributed destination
          I expect this to make loadbalancing between the 2 servers in the cluster, and
          I can migrate the jms server if one of the server fails to the running server.
          One thing is now.....If one server fails and I migrate the jms server to the other
          server that is running, and I then restart the server that was down, what is then
          happening, do I then have 3 jms servers ???
          [config.xml]


          "Kris" <[email protected]> wrote in message news:[email protected]...
          >
          > "Kawaljit Singh Sunny" <[email protected]> wrote:
          > >
          > >"Kris" <[email protected]> wrote in message
          > >news:[email protected]...
          > >>
          > >> Did I get it right ???
          > >>
          > >> I have 1 admin server and 4 managed servers in a 2 clusters, a
          development
          > >cluster
          > >> and a test cluster.
          > >> I now want to have loadbalancing with my jms server and I want to be
          > >able
          > >to migrate
          > >> my jms server in case of failer.
          > >>
          > >> for each cluster I have created
          > >> connectionFactory targeted to the cluster
          > >> Distributed destination with 2 queue members
          > >> One JMSServer migratable targeted on managed server 1, with destination
          > >1
          > >from
          > >> the ditributed destination
          > >> One JMSServer migratable targeted on managed server 2, with destination
          > >2
          > >from
          > >> the ditributed destination
          > >
          > >If the server where your JMSConnections are loadBalanced to goes down,
          > >the
          > >producers and consumers using this JMSConnection are closed.
          > >You have to recreate these producers and consumers.
          > >If the server where your Destination resides goes dow, the consumers
          > >are
          > >closed.
          > >If the producers JMSConnection is not on this server, the producer stays
          > >up.
          > >
          > >>
          > >>
          > >> I expect this to make loadbalancing between the 2 servers in the
          cluster,
          > >and
          > >> I can migrate the jms server if one of the server fails to the running
          > >server.
          > >>
          > >> One thing is now.....If one server fails and I migrate the jms server
          > >to
          > >the other
          > >> server that is running, and I then restart the server that was down,
          > >what
          > >is then
          > >> happening, do I then have 3 jms servers ???
          > >
          > >No you still have 2 JMSServers. JMS Migration is manual.
          > >
          > >>
          >
          > you say : No you still have 2 JMSServers. JMS Migration is manual.
          >
          > But if I manual migrate the jmsserver that was down to the running wls
          server,
          > that already have one jms server running, this wls server must then have 2
          jms
          > servers. And I boot the wls server that hosted the jms server that was
          down, this
          > will now have a running jms server. isn't that 3 jms servers ?
          Once you migrate a JMSServer from a WeblogicServer1 to WeblogicServer2,
          and then you boot WeblogicServer1, this JMSServer which was migrated should
          NOT be on WeblogicServer1.
          (You have migrated the JMSServer from WeblogicServer1 to WeblogicServer2)
          >
          > But I was thinking about that I could spare the migration part. If I have
          2 wls
          > servers and a jms server on each of them, and a destributed destination
          with 2
          > queue members that are persistent in a database. If a wls og just a jms
          server
          > goes down, I just have to reboot the server and it will run again. This
          way I
          > dont have to think about migration, or what ?
          Yes that is true.
          Irrespective of whether you have migration or not,
          only thing you need to do take care is to reconnect to weblogic server, if
          the the server where your JMSConnection is loadBalanced to goes down.
          There is no failover of JMSConnections. Producers inside this JMSConnection
          will be closed. You will have to create a new JMSConnection and a new
          Producer and continue with your production of JMS Messages.
          -sunny

[boxir2-sp4] two separate CMS with same cluster name

How can I change the current cluster name. Currently have two separate CMS on two separate servers but with the same cluster name. They both show up on each others CMC -> Servers page. This was not our intention.
Please advise.
Thanks.

Login to CCM, stop CMS server, go to it's properties, go to Configuration tab, check "change cluster name box" and type new cluster name, click apply, OK, start CMS. Done
Make absolutly sure that each CMS is pointing to it's own CMS DB !!!

Failover Cluster Network Name Failed and Can't be Repaired

I have an issue that seem to be a different problem than any others have encountered.
I've scoured everything I can find and nothing has fixed my problem.
The problem starts with the common problem of the cluster network name failing on my 2 node server 2012 file server cluster. The computer object was still in AD and appeared to be fine so it was not the common problem of the object
getting deleted somehow. At the time, there was no other object with that name in the recycling bin, so I don't think it was mistakenly deleted and quickly recreated to cover any tracks, so to speak.
Following one guide, I tried to find the registry key that corresponded with the GUID of the object, but neither node in the cluster had it in its registry (which may be part of the problem).
Since it was in the failed state, I tried to do the repair on the object to no avail.
We run a "locked down" DC environment so all computer objects have to be pre-provisioned. They were all pre-provisioned successfully and successfully assigned during cluster creation. The cluster was running with no issues for a month
or so before this problem came up.
When I do a repair on the object while taking diagnostic logs the following 4609 error appears:
The action 'Repair' did not complete. - System.ApplicationException: An error occurred resetting the password for 'Cluster Name'. ---> System.ComponentModel.Win32Exception: Unknown error (0x80005000)
There appears to be a corresponding 4771 error with a failure code 0x18 that comes from the security log of the DC that states there was a Kerberos pre-authentication failure for the cluster network name object (Domain\Clustername$)
I believe this is what is causing the repair failure. All the information I found related to security error 4771 was either a bad credentials given for a user account or the fix was to reconnect the computer to the domain. I can't seem to find
a way to do this with the cluster network name. If there's a way please let me know.
I've tried a number of things, like resetting the object, disabling it, deleting and creating a new object with the same name, deleting that new object and recovering the original, etc...
Can anyone shed some light on what is going on and hopefully how to fix it other than rebuilding the cluster? I'm quite close to just tearing it down and building it back up but am hesitant because this cluster in currently in production...
Any help would be appreciated

Hi,
I don’t find out the similar issue with yours, base on my experience, the 4096 error
often caused by the CSV disk issue, and the 0x80005000 error some time caused by the repetitive computer object in OU. Please check the above related part or run the validate test then post the error information.
Although I do have a CSV, there doesn't seem to be any problems with it and it was running just fine for a month or so before the problem started. I double checked and there is no duplicate computer objects, maybe I don't understand what you mean by
repetitive, could you explain further?
The cluster validates successfully with a few warnings:
Validating cluster resource Name: DT-FileCluster.
This resource is marked with a state of 'Failed' instead of
'Online'. This failed state indicates that the resource had a problem either
coming online or had a failure while it was online. The event logs and cluster
logs may have information that is helpful in identifying the cause of the
failure.
- This is because the cluster name is in the failed state
Validating the service principal names for Name:
DT-FileCluster.
The network name Name: DT-FileCluster does not have a valid
value for the read-only property 'ObjectGUID'. To validate the service principal
name the read-only private property 'ObjectGuid' must have a valid value. To
correct this issue make sure that the network name has been brought online at
least once. If this does not correct this issue you will need to delete the
network name and re-create it.
- This is definitely related to the problem and the GUID probably got removed when we attempted a fix by resetting the object and trying the repair from the failover cluster manager.
The user running validate, does not have permissions to create
computer objects in the 'ad.unlv.edu' domain.
- This is correct, we run a restricted domain. I have a delegated OU that I can pre-provision accounts in. The account was pro-provisioned successfully and was at one point setup and working just fine.
There are no other errors nor warnings.

Network Name Resource Availability - failover cluster error 1196 on Hyper-V 2012 R2 nodes

Hello,
We're getting this error in our even logs of our four node failover cluster, we tried deleting Host A record in DNS management, that did nothing.
Failover cluster event: 1196
"Cluster network name resource 'CAUCrgt8' failed registration of one or more associated DNS name(s) for the following reason: This operation returned because the timeout period expired.
Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server."
And this resource http://technet.microsoft.com/en-us/library/cc773529%28v=WS.10%29.aspx did not help in solving this.
Do you guys have any other suggestions we could try to resolve this error?

Hi Jonas,
Please offer us which platform server you are using, such as if you are using server 2012 please refer the following update first.
Recommended hotfixes and updates for Windows Server 2012-based Failover Clusters - http://support.microsoft.com/kb/2784261
If the update not work please ppply Full Control permissions for the Cluster Name Resources in the DNS console.
More detail information please refer the following article:
Windows Server 2008 Troubleshooting: Event ID 1196 — Microsoft-Windows-FailoverClustering - http://social.technet.microsoft.com/wiki/contents/articles/windows-server-2008-troubleshooting-event-id-1196-microsoft-windows-failoverclustering.aspx
DNS Registration with the Network Name Resource -
http://blogs.msdn.com/b/clustering/archive/2009/07/17/9836756.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SQL cluster name on a Windows Failover Cluster

Hello,
I am installing a SQL cluster (first timer) using Windows server and SQL (both 2008 R2)
Windows failover cluster is setup and functioning. I am now installing the SQL failover cluster part.
Question: What should be the "SQL server network name", should it be the same as my Windows cluster name or different name ?
Thanks for your help,
Luca

It should be different, this is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters.
SQL Server Network Name —
Specify a network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.
https://msdn.microsoft.com/en-us/library/ms179530.aspx?f=255&MSPPError=-2147217396
This will be the name used to identify your cluster on the network. This is the name that will be available on the
network for the clients to connect SQL instance.
http://www.mssqltips.com/sqlservertip/1709/install-sql-server-2008-on-a-windows-server-2008-cluster-part-3/

Set cluster name and IP address ONLINE

Hi
I had to shut down all cluster nodes. After turned on all cluster nodes I saw in Management cluster console:
Basic cluster resourses:
Name: CLuster1 State:Offline
Adress IP: xx.xx.xx.xx. State Offline
How to set these cluster resources (cluster name, ip adress) Online using Powershell?
Kind Regards Tomasz

Hi Yukio Seki,
If you want to know how to bring cluster resource online please refer the following KB:
Microsoft.FailoverClusters.PowerShell
https://technet.microsoft.com/en-us/library/ee461009.aspx
Failover Clusters Cmdlets in Windows PowerShell
https://technet.microsoft.com/en-us/library/hh847239.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How to find out the primary and failover DNS name

Hi;
This sounds very stupid, but could some one please tell me how to find out the name/dns name of the primary and failover server without using the CDS console.
any help is appreciated

Is this what you want?
$ /usr/lib/ldap/ldap_cachemgr -g
cachemgr configuration:
server debug level 0
server log file "/var/ldap/cachemgr.log"
number of calls to ldapcachemgr 12729
cachemgr cache data statistics:
Configuration refresh information:
Previous refresh time: 2005/08/07 23:54:59
Next refresh time: 2005/08/08 00:55:00
Server information:
Previous refresh time: 2005/08/14 15:15:00
Next refresh time: 2005/08/15 03:15:00
server: ldap1.example.com, status: UP
server: ldap2.example.com, status: UP
server: ldap3.example.com, status: UP
Cache data information:
Maximum cache entries: 256
Number of cache entries: 0
Gary

PL/SQL, synonyms to packages and name resolution

I have some question about name resolution in PL/SQL. First, I need to describe situation, because it is quite complicated.
There are three schemas: A1, B1 and O. A1 and B1 are containing proprietary software and I cannot modify objects there (but I can modify configuration tables, so in this way I can call any package from anyhere). O schema is my own schema. A1 and B1 schemas are in one "module", there are also A2 and B2 schemas in second "module" and AN and BN in n-th "module".
In normal situation, A1 schema contains synonym to package B1.PKG (on B1 schema) and uses it to call B1.PKG with DEFINER rights. The same for every "module".
I need to extend some functionality of B.PKG by buliding some kind of "wrapper" on my own O schema. It is only one MY_PKG and should be used by every "module". In this place I need some kind of magic :)
I want to place package MY_PKG with AUTH_ID CURRENT_USER clause on my O schema and use A1..AN schema to call it. Package MY_PKG have to call package placed on one of B1..BN schemas, so I need to create synonym on O schema for package, for example, B1.PKG just to compile the MY_PKG package.
Now, I call MY_PKG package from A1 schema and I expect MY_PKG will use synonym to B1.PKG placed on A1 schema, instead of using synonym on my O schema. That's not happening. MY_PKG still uses synonym on O schema, so it ruins whole concept :)
Actually, I use some set of packages that already work properly in that way, but there is some difference. In my other packages I use SQL and synonyms to tables and views placed on _one_ A schema. I use those synonyms only for compiling. When packages are calling from A1..AN schemas, they use proper objects on proper A1..AN schema. In this case I try to do the same, but with package instead of tables and view. I find it difficult probably because SQL and PLSQL resolves names in other way.
Here is the question, is it possible to make such thing as decribed above? Of course, I can use execute immediate to run proper packages directly from O schema, but I don't want :)
Sorry for my bad english, I hope you understand whole concept.
DB version: 11.2.0.3

The documentation is pretty clear that invoker rights applies only to certain statements...
Using PL/SQL Subprograms
SELECT, INSERT, UPDATE, and DELETE data manipulation statements
The LOCKTABLE transaction control statement
OPEN and OPEN-FOR cursor control statements
EXECUTEIMMEDIATE and OPEN-FOR-USING dynamic SQL statements
SQL statements parsed using DBMS_SQL.PARSE()
So clearly static PL/SQL references will not be resolved in this way.
I can't actually remember (I have found AUTHID CURRENT_USER to be very rarely useful) but you may be able to get around this by executing dynamic PL/SQL blocks but given the potential downsides of dynamic SQL and PL/SQL you almost certainly don't want to.

Failover clusterign... How similar do the primary and failover instance need to be in a failover cluster?

How similar do the primary and failover instance need to be in a failover cluster?
Does the number of database have to match, naming, general config etc...
Mr Shaw

In failover clustering, you use shared storage so the number of databases is irrelevant since only one node can see/access the shared storage at any given point in time. Ideally, the server configuration should be the same on all of the nodes to minimize
potential issues that may impact downtime. However, you need to consider licensing/# of CPU-cores and implementation cost, especially if you are only using the other nodes as standby. As far as licensing is concerned, the standby has to have the same or fewer
number of CPU-cores as the primary node to be covered by licensing. Besides, you don't want your standby node to be more powerful than your primary node. This is why the option to have a hybrid deployment of having a physical server as the primary node and
virtual machine for standby nodes is now supported.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Failover Zones / Containers with Sun Cluster Geographic Edition and AVS

Hi everyone,
Is the following solution supported/certified by Oracle/Sun? I did find some docs saying it is but cannot find concrete technical information yet...
* Two sites with a 2-node cluster in each site
* 2x Failover containers/zones that are part of the two protection groups (1x group for SAP, other group for 3rd party application)
* Sun Cluster 3.2 and Geographic Edition 3.2 with Availability Suite for SYNC/ASYNC replication over TCP/IP between the two sites
The Zones and their application need to be able to failover between the two sites.
Thanks!
Wim Olivier

Fritz,
Obviously, my colleagues and I, in the Geo Cluster group build and test Geo clusters all the time :-)
We have certainly built and tested Oracle (non-RAC) configurations on AVS. One issue you do have, unfortunately, is that of zones plus AVS (see my Blueprint for more details http://wikis.sun.com/display/BluePrints/Using+Solaris+Cluster+and+Sun+Cluster+Geographic+Edition). Consequently, you can't built the configuration you described. The alternative is to sacrifice zones for now and wait for the fixes to RG affinities (no idea on the schedule for this feature) or find another way to do this - probably hand crafted.
If you follow the OHAC pages (http://www.opensolaris.org/os/community/ha-clusters/) and look at the endorsed projects you'll see that there is a Script Based Plug-in on the way (for OHACGE) that I'm writing. So, if you are interested in playing with OHACGE source or the SCXGE binaries, you might see that appear at some point. Of course, these aren't supported solutions though.
Regards,
Tim
---

Installing Cloud Control 12c agent on other blades thru RPM and response file sets wrong cluster name

Hi,
Hopefully someone can help me with this. We installed em Cloud Control 12c and its agents on miscellaneous machines.
We first proceeded with two target-nodes part of a Grid Infra cluster (let's call it proclu_1). OS is RH6.
Then, using the same method (1/ yum -y install /tmp/oracle-agt-12.1.0.3.0-1.0.x86_64.rpm and then
2/ /etc/init.d/oracle-agt RESPONSE_FILE=/usr/lib/oracle/agent/agent.properties) we installed the agent on 2 other
blades that are part of another cluster (proclu_2). The agent.properties file above just contained the usual key-value lines:
OMS_HOST=omsmachine.stuff.be
OMS_PORT=4889
AGENT_REGISTRATION_PASSWORD=ametemp
AGENT_USERNAME=oracle
AGENT_GROUP=oinstall
AGENT_PORT=3873
ORACLE_HOSTNAME=promachine.stuff.be
Now if I change dir to /usr/lib/oracle/agent and search for the name "proclu*" from there, I find the name of the
first install (on first cluster proclu_1):
[oracle@bladb0406 agent]$ pwd
/usr/lib/oracle
[oracle@bladb0406 oracle]$ find . -name "proclu_1*"
./agent/agent_inst/sysman/emd/state/has/proclu2/cluster/proclu
./agent/agent_inst/sysman/emd/state/configstate/cluster/proclu_1
./agent/agent_inst/sysman/emd/state/statemgmt/cluster/proclu_1
./agent/agent_inst/sysman/log/targets/cluster/proclu_1
My questions:
1/ on the first two nodes (blada0204 & blada0406) of our first cluster doing this 'find' returns the
same directory names with "proclu_1", this is what we expected: where did the oracle-agt script pick up
our cluster name ?
2/ why has it set the same -and wrong- "proclu_1" name on our two other nodes (bladb0204 & bladb0406) ??
(we would've expected "proclu_2"...)
Is there a way to correct this, or should I reinstall the agent (after configuring/modifying something somewhere
so that it picks up the correct cluster name...) ??
Thanks a lot.
Regards,
Seb

Unfortunately, this goes back to the RAC install procedures. Check the cluster name for each cluster. If they're all installed the same, then you'll need to manually discover/edit name when you promote so that your clusters are unique in EM.
To verify name set for clusterware installation:
<CRS_HOME>/bin/cemutlo -n

2012R2 hyper-v failover cluster Cluster name object has no DNS record created

I’m trying to setup a 2-node ws2012R2 cluster using ws2008R2 AD(with DNS) but got an issue with DNS entry creation on AD. I also tried ws2012 AD but it's the same problem.
The individual node DNS entries were created on AD automatically upon joining AD but I can’t get AD to create DNS entry for my cluster name object automatically. AD will have cluster name computer
created but no record for cluster name in DNS entries
Got the following event ID 1196 error with the info below.
Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:
DNS server failure.

Hi hjma29,
How about your issue now? I just want to confirm the current situations.
Please feel free to let us know if you need further assistance.
Regards.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Cluster Name Resolution and failover

Similar Messages

Maybe you are looking for