After patching the node, the node is not joining the cluster.

Dear All,
We are having a two node suncluster with below release
Sun Cluster 3.2u1 for Solaris 10 sparc
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
And nodes are
Node Name Status
scrbdomdefrm005 Online
scrbdomderue005 Offline
We are patching the nodes with 2q 2009 quarter patches, first we patched the node scrbdomderue005. we have followed the below step to patch the server.
1) Our root d0 has d1(c0t0d0s0) and d2(c1t0d0s0)
2) we have detached the d2 from d0; metaclear d2
3) mount the c1t0d0s0 /mnt
4) use the patchadd -R /mnt to patch the server. While patching we got only one error the patch 126106-27 need to be install in noncluster mode.
5) switch the RG's from node scrbdomderue005 to scrbdomdfrm005.
6) shutdown the scrbdomderue005, boot the scrbdomderue005 with c1t0d0s0 in noncluster-single user mode, and installed the patch 126106-27 and it was successful.
7) shutdown the scrbdomderue005, boot the scrbdomderue005 with c1t0d0s0 in clustermode, and we are getting the following error.
Booting as part of a cluster
NOTICE: CMM: Node scrbdomdefrm005 (nodeid = 1) with votecount = 1 added.
NOTICE: CMM: Node scrbdomderue005 (nodeid = 2) with votecount = 1 added.
WARNING: CMM: Open failed for quorum device /dev/did/rdsk/d5s2 with error 1.
NOTICE: clcomm: Adapter nxge7 constructed
NOTICE: clcomm: Adapter nxge3 constructed
NOTICE: CMM: Node scrbdomderue005: attempting to join cluster.
NOTICE: nxge3: xcvr addr:0x0a - link is up 1000 Mbps full duplex
NOTICE: nxge7: xcvr addr:0x0a - link is up 1000 Mbps full duplex
WARNING: CMM: Open failed for quorum device /dev/did/rdsk/d5s2 with error 1.
NOTICE: CMM: Cluster doesn't have operational quorum yet; waiting for quorum.
NOTICE: clcomm: Path scrbdomderue005:nxge7 - scrbdomdefrm005:nxge7 errors during initiation
NOTICE: clcomm: Path scrbdomderue005:nxge3 - scrbdomdefrm005:nxge3 errors during initiation
WARNING: Path scrbdomderue005:nxge7 - scrbdomdefrm005:nxge7 initiation encountered errors, errno = 62. Remote node may be down or unreachable through this path.
WARNING: Path scrbdomderue005:nxge3 - scrbdomdefrm005:nxge3 initiation encountered errors, errno = 62. Remote node may be down or unreachable through this path.
exit from console.
We are able to boot the node scrbdomderue005 in noncluster-mode and it was successful., please check the below details.
scrbdomderue005:/# uname -a
SunOS scrbdomderue005 5.10 Generic_138888-07 sun4u sparc SUNW,SPARC-Enterprise
scrbdomderue005:/#
Before pathcing the server scrbdomderue005 the kernel version was.
SunOS scrbdomderue005 5.10 Generic_137111-07 sun4u sparc SUNW,SPARC-Enterprise
If i boot the scrbdomderue005 with d1(c0t0d0s0), the server is properly joining the cluster without issue.
could any one please guide me, what could be the problem... how to resolve the issue.

Hi
I could be because you have installed patch 138888. It has problems with nxge interfaces used as interconnect.
Rgds
Carsten

Similar Messages

Node can not join cluster after RAC HA Testing

Dear forum,
We are performing RAC failover tests according to document "RAC System Test Plan Outline 11gR2, Version 2.0". In testcase #14 - Interconnect network failure (11.2.0.2 an higher), we have disabled private interconnect network of node node1 (OCR Master).
Then - as expected - node node2 was evicted. Now, after enabling private interconnect network on node node1, i want to start CRS again on node2. However, node does not join cluster with messages:
2012-03-15 14:12:35.138: [ CSSD][1113114944]clssgmWaitOnEventValue: after CmInfo State val 3, eval 1 waited 0
2012-03-15 14:12:35.371: [ CSSD][1109961024]clssnmvDHBValidateNCopy: node 1, node1, has a disk HB, but no network HB, DHB has rcfg 226493542, wrtcnt, 2301201, LATS 5535614, lastSeqNo 2301198, uniqueness 1331804892, timestamp 1331817153/13040714
2012-03-15 14:12:35.479: [ CSSD][1100884288]clssnmvDHBValidateNCopy: node 1, node1, has a disk HB, but no network HB, DHB has rcfg 226493542, wrtcnt, 2301202, LATS 5535724, lastSeqNo 2301199, uniqueness 1331804892, timestamp 1331817154/13041024
2012-03-15 14:12:35.675: [ CSSD][1080801600]clssnmvDHBValidateNCopy: node 1, node1, has a disk HB, but no network HB, DHB has rcfg 226493542, wrtcnt, 2301203, LATS 5535924, lastSeqNo 2301200, uniqueness 1331804892, timestamp 1331817154/13041364
Rebooting node2 did not help. Node1 which was online all the time (although private interconnect interface was unplugged for a few minutes and then plugged back in). I suppose that if we reboot node2, the problem will disappear. But there should be solution, which keeps availability requirements.
Setup:
2 Nodes (OEL5U7, UEK)
2 Storages
Network bonding via Linux bonding
GI 11.2.0.3.1
RDBMS 11.1.0.7.10
Any ideas?
Regards,
Martin

I have found a solution myself:
[root@node1 trace]# echo -eth3 > /sys/class/net/bond1/bonding/slaves
[root@node1 trace]# echo -eth1 > /sys/class/net/bond1/bonding/slaves
[root@node1 trace]# echo +eth1 > /sys/class/net/bond1/bonding/slaves
[root@node1 trace]# echo +eth3 > /sys/class/net/bond1/bonding/slaves
Now node2 is automatically joining the cluster.
Regards,
martin

Local disks are in FAIL status after installing the cluster

The /var/adm/messages log isn't giving me much info to go on. This has happened twice now. After installing the cluster, my local disks are in a FAIL status and the cluster is not giving me much information why.
It's a two-node cluster w/ x2100 M2s.
Any ideas?
-Hedo

when I run cldevice status -v, it reports that the two local disks are in FAIL status on each node.
That's all that's going on right now. Everything else seems to be perfect, other then those disks in FAIL status.
== from /var/adm/messages ==
Jan 15 10:17:38 frito Cluster.scdpmd: [ID 977412 daemon.notice] The state of the path to device: /dev/did/rdsk/d12s0 has changed to FAILED
Jan 15 10:17:38 frito Cluster.scdpmd: [ID 977412 daemon.notice] The state of the path to device: /dev/did/rdsk/d11s0 has changed to FAILED
-hedo.

JCo missing after patching the system

Hi
We have gone for pataching the Portal and ESS. We see that after patching there is only Selfservicgenerics and HumanResources Jco appearing. All other JCo,s are missing from the system. Is this normal behavior ??
How do we get other JCo appear asthey were already configured before.

Hi Purav,
I think yuu need me create manually as per your required JCO for ESS/MSS applciation.
Try to check in the SLD if all earlier JCO's available
Thanks
Arun

Node does not join cluster upon reboot

Hi Guys,
I have two servers [Sun Fire X4170] clustered together using Solaris cluster 3.3 for Oracle Database. They are connected to a shared storage which is Dell Equallogic [iSCSI]. Lately, I have ran into a weird kind of a problem where as both nodes come up fine and join the cluster upon reboot; however, when I reboot one of nodes then any of them does not join cluster and shows following errors:
This is happening on both the nodes [if I reboot only one node at a time]. But if I reboot both the nodes at the same time then they successfully join the cluster and everything runs fine.
Below is the output from one node which I rebooted and it did not join the cluster and puked out following errors. The other node is running fine will all the services.
In order to get out of this situation, I have to reboot both the nodes together.
# dmesg output #
Apr 23 17:37:03 srvhqon11 ixgbe: [ID 611667 kern.info] NOTICE: ixgbe2: link down
Apr 23 17:37:12 srvhqon11 iscsi: [ID 933263 kern.notice] NOTICE: iscsi connection(5) unable to connect to target SENDTARGETS_DISCOVERY
Apr 23 17:37:12 srvhqon11 iscsi: [ID 114404 kern.notice] NOTICE: iscsi discovery failure - SendTargets (010.010.017.104)
Apr 23 17:37:13 srvhqon11 iscsi: [ID 240218 kern.notice] NOTICE: iscsi session(9) iqn.2001-05.com.equallogic:0-8a0906-96cf73708-ef30000005e50a1b-sblprdbk online
Apr 23 17:37:13 srvhqon11 scsi: [ID 583861 kern.info] sd11 at scsi_vhci0: unit-address g6090a0887073cf961b0ae505000030ef: g6090a0887073cf961b0ae505000030ef
Apr 23 17:37:13 srvhqon11 genunix: [ID 936769 kern.info] sd11 is /scsi_vhci/disk@g6090a0887073cf961b0ae505000030ef
Apr 23 17:37:13 srvhqon11 scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Apr 23 17:37:13 srvhqon11 /scsi_vhci/disk@g6090a0887073cf961b0ae505000030ef (sd11): Command failed to complete (3) on path iscsi0/[email protected]:0-8a0906-96cf73708-ef30000005e50a1b-sblprdbk0001,0
Apr 23 17:46:54 srvhqon11 svc.startd[11]: [ID 122153 daemon.warning] svc:/network/iscsi/initiator:default: Method or service exit timed out. Killing contract 41.
Apr 23 17:46:54 srvhqon11 svc.startd[11]: [ID 636263 daemon.warning] svc:/network/iscsi/initiator:default: Method "/lib/svc/method/iscsid start" failed due to signal KILL.
Apr 23 17:46:54 srvhqon11 svc.startd[11]: [ID 748625 daemon.error] network/iscsi/initiator:default failed repeatedly: transitioned to maintenance (see 'svcs -xv' for details)
Apr 24 14:50:16 srvhqon11 svc.startd[11]: [ID 694882 daemon.notice] instance svc:/system/console-login:default exited with status 1
root@srvhqon11 # svcs -xv
svc:/system/cluster/loaddid:default (Oracle Solaris Cluster loaddid)
State: offline since Tue Apr 23 17:46:54 2013
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: /var/svc/log/system-cluster-loaddid:default.log
Impact: 49 dependent services are not running:
svc:/system/cluster/bootcluster:default
svc:/system/cluster/cl_execd:default
svc:/system/cluster/zc_cmd_log_replay:default
svc:/system/cluster/sc_zc_member:default
svc:/system/cluster/sc_rtreg_server:default
svc:/system/cluster/sc_ifconfig_server:default
svc:/system/cluster/initdid:default
svc:/system/cluster/globaldevices:default
svc:/system/cluster/gdevsync:default
svc:/milestone/multi-user:default
svc:/system/boot-config:default
svc:/system/cluster/cl-svc-enable:default
svc:/milestone/multi-user-server:default
svc:/application/autoreg:default
svc:/system/basicreg:default
svc:/system/zones:default
svc:/system/cluster/sc_zones:default
svc:/system/cluster/scprivipd:default
svc:/system/cluster/cl-svc-cluster-milestone:default
svc:/system/cluster/sc_svtag:default
svc:/system/cluster/sckeysync:default
svc:/system/cluster/rpc-fed:default
svc:/system/cluster/rgm-starter:default
svc:/application/management/common-agent-container-1:default
svc:/system/cluster/scsymon-srv:default
svc:/system/cluster/sc_syncsa_server:default
svc:/system/cluster/scslmclean:default
svc:/system/cluster/cznetd:default
svc:/system/cluster/scdpm:default
svc:/system/cluster/rpc-pmf:default
svc:/system/cluster/pnm:default
svc:/system/cluster/sc_pnm_proxy_server:default
svc:/system/cluster/cl-event:default
svc:/system/cluster/cl-eventlog:default
svc:/system/cluster/cl-ccra:default
svc:/system/cluster/ql_upgrade:default
svc:/system/cluster/mountgfs:default
svc:/system/cluster/clusterdata:default
svc:/system/cluster/ql_rgm:default
svc:/system/cluster/scqdm:default
svc:/application/stosreg:default
svc:/application/sthwreg:default
svc:/application/graphical-login/cde-login:default
svc:/application/cde-printinfo:default
svc:/system/cluster/scvxinstall:default
svc:/system/cluster/sc_failfast:default
svc:/system/cluster/clexecd:default
svc:/system/cluster/sc_pmmd:default
svc:/system/cluster/clevent_listenerd:default
svc:/application/print/server:default (LP print server)
State: disabled since Tue Apr 23 17:36:44 2013
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: man -M /usr/share/man -s 1M lpsched
Impact: 2 dependent services are not running:
svc:/application/print/rfc1179:default
svc:/application/print/ipp-listener:default
svc:/network/iscsi/initiator:default (?)
State: maintenance since Tue Apr 23 17:46:54 2013
Reason: Restarting too quickly.
See: http://sun.com/msg/SMF-8000-L5
See: /var/svc/log/network-iscsi-initiator:default.log
Impact: This service is not running.
######## Cluster Status from working node ############
root@srvhqon10 # cluster status
=== Cluster Nodes ===
--- Node Status ---
Node Name Status
srvhqon10 Online
srvhqon11 Offline
=== Cluster Transport Paths ===
Endpoint1 Endpoint2 Status
srvhqon10:igb3 srvhqon11:igb3 faulted
srvhqon10:igb2 srvhqon11:igb2 faulted
=== Cluster Quorum ===
--- Quorum Votes Summary from (latest node reconfiguration) ---
Needed Present Possible
2 2 3
--- Quorum Votes by Node (current status) ---
Node Name Present Possible Status
srvhqon10 1 1 Online
srvhqon11 0 1 Offline
--- Quorum Votes by Device (current status) ---
Device Name Present Possible Status
d2 1 1 Online
=== Cluster Device Groups ===
--- Device Group Status ---
Device Group Name Primary Secondary Status
--- Spare, Inactive, and In Transition Nodes ---
Device Group Name Spare Nodes Inactive Nodes In Transistion Nodes
--- Multi-owner Device Group Status ---
Device Group Name Node Name Status
=== Cluster Resource Groups ===
Group Name Node Name Suspended State
ora-rg srvhqon10 No Online
srvhqon11 No Offline
nfs-rg srvhqon10 No Online
srvhqon11 No Offline
backup-rg srvhqon10 No Online
srvhqon11 No Offline
=== Cluster Resources ===
Resource Name Node Name State Status Message
ora-listener srvhqon10 Online Online
srvhqon11 Offline Offline
ora-server srvhqon10 Online Online
srvhqon11 Offline Offline
ora-stor srvhqon10 Online Online
srvhqon11 Offline Offline
ora-lh srvhqon10 Online Online - LogicalHostname online.
srvhqon11 Offline Offline
nfs-rs srvhqon10 Online Online - Service is online.
srvhqon11 Offline Offline
nfs-stor-rs srvhqon10 Online Online
srvhqon11 Offline Offline
nfs-lh-rs srvhqon10 Online Online - LogicalHostname online.
srvhqon11 Offline Offline
backup-stor srvhqon10 Online Online
srvhqon11 Offline Offline
cluster: (C383355) No response from daemon on node "srvhqon11".
=== Cluster DID Devices ===
Device Instance Node Status
/dev/did/rdsk/d1 srvhqon10 Ok
/dev/did/rdsk/d2 srvhqon10 Ok
srvhqon11 Unknown
/dev/did/rdsk/d3 srvhqon10 Ok
srvhqon11 Unknown
/dev/did/rdsk/d4 srvhqon10 Ok
/dev/did/rdsk/d5 srvhqon10 Fail
srvhqon11 Unknown
/dev/did/rdsk/d6 srvhqon11 Unknown
/dev/did/rdsk/d7 srvhqon11 Unknown
/dev/did/rdsk/d8 srvhqon10 Ok
srvhqon11 Unknown
/dev/did/rdsk/d9 srvhqon10 Ok
srvhqon11 Unknown
=== Zone Clusters ===
--- Zone Cluster Status ---
Name Node Name Zone HostName Status Zone Status
Regards.

check if your global devices are mounted properly
#cat /etc/mnttab | grep -i global
check if proper entries are there on both systems
#cat /etc/vfstab | grep -i global
give output for quoram devices .
#scstat -q
or
#clquorum list -v
also check why your scsi initiator service is going offline unexpectedly
#vi /var/svc/log/network-iscsi-initiator:default.log

After patching primary database, can I do not patch phsical standby db?

If I patch the primary from 10.2.4.0 to 10.2.0.5 in RAC db,
Do I must patch phsical standby to the same version or can afford to leave it alone (still 10.2.0.4)?
Thank you.

You must apply the same patchs to the standby site.
Because in case of a failover, when the standby become primary, you do not want to find a bug resolved in the patch already applied to the failed database.
That is why the docs for patching this scenario always describe the steps to patch both sites, production and standby.
For example, Note ID 187242. "Applying Patch Sets / Interim Patches with Physical Standby Database in Place".
Regards.

After bring the Cluster and ASM is up, I'm not able to start the rdbms ins.

I am not able to bring the database up.
Cluster and ASM is up and running.
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/oracle/app/oracle/product/11.1.0/db_1/dbs/initTMISC11G.ora'

That is wre the confusion is: I coud nt find it under O_H/dbs,
However the log file indicates that it is using spfile which is located at :
spfile = +DATA_TIER/dintw10g/parameterfile/spfile_dintw10g.ora
Now it checks only the /dbs directory only i guess.
Could you please how can i bring it up now.
Just for the information: ASM instance is up.

Can i patch oracle database on RAC and not patch the RAC software

Hi there
Kindly advise on implications of doing the following
1 i have oracle cluster version 10.2.0.1.0 running 2 nodes
2 i have database version 10.2.0.1.0
i have 4 different databases
I want to patch only one database
question !!
Can i patch the database to 10.2.0.4 on both nodes with out patching the cluster software ?
I' m doing this in order to fix a bug that is messing the live Db
Is That possible
Please answer
Thanks
Francis

Can i patch the database to 10.2.0.4 on both nodes with out patching the cluster software ? Can you? yes
Should you? NO

Cluster is not coming up after changing the network

Hi All,
I changes the network using srvctl modify command. Accidently i modify it to Private interconnect.
After restarting the cluster,The crsd is not coming up. I can see this in crsdlog which mean it is trying to listen on private IP.
(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.0.204)(PORT=0))
I am not able to modify it now using srvctl commnad as i am getting the below error.
Failed to check if resource ora.net1.network is registered
Please somebody help me to modify metwork back to its original value.
Env Details
DB- 11.2.0.3
OS : RHEL-5
Thanks and Regards,

Hi,
you may want to try if you can startup the cluster stack in exclusive mode (crsctl start crs exclusive).
This might bring up the clusterstack, so you can modify with srvctl again.
If this fails, it could also be that the network and the internal information got out of sync.
Can you give a
# oifcfg getif
# oifcfg iflist
# crsctl stat res ora.net1.network -p
# gpnptool c14n -p=$ORACLE_HOME/gpnp/profiles/peer/profile.xml -fmt
Regards
Sebastian

Reports not Generated after moving SCCM 2012 SP1 DB on SQL 2012 SP1 cluster

Hi all,
i have moved my SCCM 2012 SP1 DB on SQL 2012 SP1 Failover Cluster,this cluster is a two node cluster.the DB was moved fine and the DB configuration in SCCM Site maintenance was also done successfully.After the migration process,SCCM was working fine created
few collections & packages, then checked the DB on cluster & they were updated successfully.
but when i tried to install report server on my SCCM machine,again there was no instance displayed after entering the cluster name.
I searched this & come across this post :-
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/4479e73e-8a19-4c7e-9418-b36770656b9b/
which says to install report server on the cluster node machine which is currently running the Reporting Service.I tried to install the report server & the instance was detected this time.it was installed successfully.
But when i tried to generate reports I got this error :-
Permissions are fine as i have added SCCMadmin & sccm machine in the local admin of both the nodes.
Please Help.
Thanks,
Pranay.

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
If you look at your second screenshot the Remote errors is not enabled. Use this blog to enable them.
http://www.enhansoft.com/blog/enabling-remote-errors-in-sql
If changing the data source on the report fixed it for a single report. It means that your shared Datasource is having problems. Reset the username and password within CM12 console and this should fix it for every report.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

After patching Portal 7.31 SP9 - SP13, CM BW reports fail

Our links to the BI credit reports (like Early Warning Risk) stopped working after patching the NW Portal 7.31 from SP9 to SP13. No other changes were made, and the reports worked prior to the patching.
The child window for the report opens, but then comes back with error:
com.sap.portal.appintegrator.sap.BWReport::BWReport/AskForReport
And then it asks for a BEx Web Application Query String.
I would put this in the portal/netweaver forum, but this error seems strictly related to the CM delivered content (we are on the most current 1.41 BP). We've validated that that the SSO tickets from portal to back end ERP and BI are working properly. Has anyone had this kind of issue after a patch (while staying on same portal release)? We didn't make any changes/patches to the back end ERP and BI systems either.

Yes we have experienced the same thing. We upgraded from 30 to 353 and now we are getting the BW logon prompt. It is very frustrating. I have been searching these message boards for help.
Brien

System Slow after patching.

Hi All,
Ecc6,Oracle10.2, Unix, System is slow after patching the application server. Will there be any problem in the patch or itu2019s because the server has been restarted. If the second one is the case how long it will take to come to the optimal performance?
Best Regards,
A.K

Run SGEN>Genereate all objects of selected software components> Select the Components for which u have applied the patches--> Select theserver and start the job directly.
Thanks,
Pundari
Edited by: pundari kakshayya on Mar 11, 2009 10:44 PM

Why virtual interfaces added to ManagementOS not visible to Cluster service?

Hello All,
I"m starting this new thread since the one before is answered by our friend Udo. My problem in short is following. Diagram will be enough to explain what I'm trying to achieve. I've setup this lab to learn Hyper-V clustering with 2 nodes. It is Hyper-V
server 2012. Both nodes have 3x physical NIcs, 1 in each node is dedicated to managing the Node. Rest of the two are used to create a NIC team. Atop of that NIC team, a virtual switch is created with -AllowManagementOS
$False. Next I created and added following virtual interfaces to host partition, and plugged them into virtual switch created atop of teamed interface. These virtual interfaces should serve the purpose of various networks available.
For SAN i'm running a Linux VM which has iSCSI target server and clustering service has no problem with that. All tests pass ok.
The problem is......when those virtual interfaces added to hosts; do not appear as available networks
to cluster service; instead it only shows the management NIC as the available network to leverage.
This is making it difficult to understand how to setup a cluster of 2x Hyper-V Server nodes. Can someone help please?
Regards,
Shahzad.

Shahzad,
I've read this thread a couple of times and I don't think I'm clear on the exact question you're asking.
When the clustering service goes out to look for "Networks", what it does is scan the IP addresses on each node. Every time it finds an IP in a unique subnet, that subnet is listed as a network. It can't see virtual switches and doesn't care about
virtual vs. teamed vs. physical adapters or anything like that. It's just looking at IP addresses. This is why I'm confused when you say, "it won't show virtual interfaces available as networks". "Networks" in this context are IP subnets.
I'm not aware of any context where a singular interface would be treated like a network.
If you've got virtual adapters attached to the management operating system
and have assigned IPs to them, the cluster should have discovered those networks. If you have multiple adapters on the same node using IPs in the same subnet, that network will only appear once and the cluster service will only use
one adapter from that subnet on that node. The one it picked will be visible on the "Network Connections" tab at the bottom of Failover Cluster Manager when you're on the Networks section.
Eric Siron Altaro Hyper-V Blog
I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
"Every relationship you have is in worse shape than you think."
Hello Eric and friends,
Eric, much appreciated about your interest about the issue and yes I agree with you when you said... "When the clustering service goes out to look for "Networks",
what it does is scan the IP addresses on each node. Every time it finds an IP in a unique subnet, that subnet is listed as a network. It can't see virtual switches and doesn't care about virtual vs. teamed vs. physical adapters or anything like that. It's
just looking at IP addresses. This is why I'm confused when you say, "it won't show virtual interfaces available as networks". "Networks" in this context are IP subnets. I'm not aware of any context where a singular interface would be treated
like a network."
By networks I meant to say subnets. Let me explain what I've configured so far:
Node 1 & Node 2 installed with 3x NICs. All 3 NICs/node plugged into same switch.
Node1: 131.107.0.50/24
Node2: 131.107l.0.150/24
A Core Domain controller VM running on Node 1: 131.107.0.200/24
A JUMPBOX (WS 2012 R2 Std.) VM running on Node 1: 131.107.0.100/24
A Linux SAN VM running on Node 2: 10.1.1.100/8
I planed to configured following networks:
(1) Cluster traffic: 10.0.0.50/24 (IP given to virtual interface for Cluster traffic in Node1)
Cluster traffic: 10.0.0.150/24 (IP given to virtual interface for Cluster traffic in Node2)
(2) SAN traffic: 10.1.1.50/8 (IP given to virtual interfce for SAN traffic in Node1)
SAN traffic: 10.1.1.150/8 (IP given to virtual interfce for SAN traffic in Node2)
Note: Cluster service has no problem accessing the SAN VM (10.1.1.100) over this network, it validates SAN settings and comes back OK. This is an indication that virtual interface is
working fine.
(3) Migration traffic: 172.168.0.50/8 (IP given to virtual interfce for
Migration traffic in Node1)
Migration traffic: 172.168.0.150/8 (IP given to virtual interfce for
Migration traffic in Node2)
All these networks (virtual interfaces) are made available through two virtual switches which are configured EXACTLY identical on both Node1/Node2.
Now after finishing the cluster validation steps (which comes all OK), when create cluster wizard starts, it only shows one network; i.e. network of physical Layer 2 switch i.e. 131.107.0.0/24.
I wonder why it won't show IPs of other networks (10.0.0.0/8, 10.1.1.0/8 and 172.168.0.0/8)
Regards,
Shahzad

Managed Server is not Joining Cluster

Dear All,
          I have 3 (A,B,C) machines(each machine for each server) configured as 1 cluster (MainApp Cluster),
          due to unknown problem then 2 (B,C) machines is not recieving any EJB request from client, request only served by 1 machine (A).
          Then i try to restart these 2 (B,C) machines, B server was succesfully restarted and recieving request also from client, but when i restarted C server, A & B server stop serving request and all requests are handled only by C server, and if i stop the C server then A & B server start to recieve requests again.
          The MainApp Cluster monitoring menu looked someting like this when i started C server:
          Name Server Known Server
          A 3 A B
          B 3 A B
          C 1 C
          At first, after creation the cluster configuration served well.
          Do you guys ever have the same issues??? Is this a cluster configuation problem? Any comment is highly regarded.
          When i try with multicast test, i got out of order when i restartted the test in one of the server.
          Thanks
          [RESOLVED]
          Edited by bagusprabawa at 10/26/2007 1:30 AM
          Edited by bagusprabawa at 10/26/2007 2:54 AM

It looks like the multicast connection between C and remain machines (A and B) is not proper. Please try multicast test from C and other machines and send the output.
          Regards,
          Rejeev Divakaran,
          http://rejeev.blogspot.com

Public Interface not responding after second node is started in the cluster

Hi
Has anyone ever experienced the public interface not responding between nodes in the cluster (ping, ssh, scp) after the second nodeapps is started in the cluster?
This is a new install so all I have installed so far is the base release of CRS 10.2.0. This is on Solaris10. The vipca failed during the installation, however I was able to proceed and manually add the nodeapps using srvctl add nodeaps -n -o -A.
It seems after the second node is started I loose all connectivity to the public interfaces and to my default gateway.
Also I'm getting the following messages sometimes after I try and stop the nodeapps and start them back up.
CRS-1006: No more members to consider
CRS-0215: Could not start resource 'ora.node1.vip'.
Any suggestions on where I should start troubleshooting?
Thanks

Do you have default GW?
It can connects with GW, can't it?
Check metalink
CRS-0215: Could not start resource 'ora..vip' [ID 356535.1]
CRS-1006: No more members to consider when starting service [ID 465364.1]
Good Luck

After patching the node, the node is not joining the cluster.

Similar Messages

Maybe you are looking for