"Having a cluster node act as a router is not supported by Sun Cluster"

Hello,
can someone please explain me the rationale behind the above statement?
I need to enable ip_forwarding in the kernel and would like to understand what "not supported"
means exactly (i.e. what the involved risks are).
I have a 2 node Solaris 9 / SC 3.1 cluster runnning with ip_forwarding = 1 since more than 2 years
wirhout a problem, at least that I am aware of :-)
Thanks in advance,
Rick

Correct, I only use failover addresses (Logical Hostnames), glad to know it is safe to have routing in this case!!
I think you should mention that in the docs, and maybe in scinstall (which, right now, just touches /etc/notrouter
and says "please DO NOT enable routing" :-))
Thanks for the explanation, I really appreciated it.
Best,
Rick

Similar Messages

Anyone else having issues with third party changers saying "this accessory not supported". I get it every time I plug my phone. It only started after the iOS 7 updates

Anyone else having issues with third party changers saying "this accessory not supported". I get it every time I plug my phone. It only started after the iOS 7 update?

That's because part of iOS7 had code in it to look for and recognize unsigned cables.
In other words, Apple knew that people used non-signed ones and didn't care....until last month when they decided to care. People with iOS6 and lower should experience no issues (unless Apple patches those iOS versions) but folks with iOS7 will need to deal with it.

Timesten database driver is not supported in Weblogic cluster mode??

Does anybody encounter this situation??
I have 2 managed server in a Weblogic cluster domain and there is DataSource for them.
In each managed server, I setup Timesten client correctly to connect to Timesten Oracle DB cache server.
But when we start each of managed server, I will get exception:
####<Nov 22, 2010 6:03:24 PM CST> <Critical> <WebLogicServer> <Machine1> <Main Thread> <<WLS Kernel>> <1290420204498> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError:
java.lang.AssertionError: Unsupported database driver
at weblogic.cluster.singleton.QueryHelperImpl.getTimeFunction(QueryHelperImpl.java:88)
at weblogic.cluster.singleton.QueryHelper.getLeaseOwnerQuery(QueryHelper.java:110)
at weblogic.cluster.singleton.DatabaseLeasingBasis.pingDB(DatabaseLeasingBasis.java:411)
at weblogic.cluster.singleton.DatabaseLeasingBasis.getJDBCConnection(DatabaseLeasingBasis.java:465)
at weblogic.cluster.singleton.DatabaseLeasingBasis.getJDBCConnection(DatabaseLeasingBasis.java:507)
at weblogic.cluster.singleton.DatabaseLeasingBasis.findOwner(DatabaseLeasingBasis.java:305)
at weblogic.cluster.singleton.LeaseManager.findOwner(LeaseManager.java:218)
at weblogic.cluster.singleton.MigratableServerService.findSingletonMaster(MigratableServerService.java:201)
at weblogic.cluster.singleton.ReplicatedSingletonServicesStateManager.syncStateFromActiveStateManager(ReplicatedSingletonServicesStateManager.java:618)
at weblogic.cluster.singleton.ReplicatedSingletonServicesStateManager.<init>(ReplicatedSingletonServicesStateManager.java:168)
at weblogic.cluster.singleton.SingletonMonitor.<init>(SingletonMonitor.java:97)
at weblogic.cluster.singleton.SingletonMaster.<init>(SingletonMaster.java:44)
at weblogic.cluster.singleton.MigratableServerService.initialize(MigratableServerService.java:142)
at weblogic.cluster.singleton.MigratableServerService.start(MigratableServerService.java:436)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
But if I create a standalone domain, still use the same datasource(still this timesten server), weblogic server can start successfully.
BR,
Peng
Edited by: user8028210 on Nov 25, 2010 1:18 AM
Edited by: user8028210 on Nov 25, 2010 1:19 AM

Does anybody encounter this situation??
I have 2 managed server in a Weblogic cluster domain and there is DataSource for them.
In each managed server, I setup Timesten client correctly to connect to Timesten Oracle DB cache server.
But when we start each of managed server, I will get exception:
####<Nov 22, 2010 6:03:24 PM CST> <Critical> <WebLogicServer> <Machine1> <Main Thread> <<WLS Kernel>> <1290420204498> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError:
java.lang.AssertionError: Unsupported database driver
at weblogic.cluster.singleton.QueryHelperImpl.getTimeFunction(QueryHelperImpl.java:88)
at weblogic.cluster.singleton.QueryHelper.getLeaseOwnerQuery(QueryHelper.java:110)
at weblogic.cluster.singleton.DatabaseLeasingBasis.pingDB(DatabaseLeasingBasis.java:411)
at weblogic.cluster.singleton.DatabaseLeasingBasis.getJDBCConnection(DatabaseLeasingBasis.java:465)
at weblogic.cluster.singleton.DatabaseLeasingBasis.getJDBCConnection(DatabaseLeasingBasis.java:507)
at weblogic.cluster.singleton.DatabaseLeasingBasis.findOwner(DatabaseLeasingBasis.java:305)
at weblogic.cluster.singleton.LeaseManager.findOwner(LeaseManager.java:218)
at weblogic.cluster.singleton.MigratableServerService.findSingletonMaster(MigratableServerService.java:201)
at weblogic.cluster.singleton.ReplicatedSingletonServicesStateManager.syncStateFromActiveStateManager(ReplicatedSingletonServicesStateManager.java:618)
at weblogic.cluster.singleton.ReplicatedSingletonServicesStateManager.<init>(ReplicatedSingletonServicesStateManager.java:168)
at weblogic.cluster.singleton.SingletonMonitor.<init>(SingletonMonitor.java:97)
at weblogic.cluster.singleton.SingletonMaster.<init>(SingletonMaster.java:44)
at weblogic.cluster.singleton.MigratableServerService.initialize(MigratableServerService.java:142)
at weblogic.cluster.singleton.MigratableServerService.start(MigratableServerService.java:436)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
But if I create a standalone domain, still use the same datasource(still this timesten server), weblogic server can start successfully.
BR,
Peng
Edited by: user8028210 on Nov 25, 2010 1:18 AM
Edited by: user8028210 on Nov 25, 2010 1:19 AM

Timesten database driver is not supported in Weblogic Cluster mode domain??

Does anybody encounter this situation??
I have 2 managed server in a Weblogic cluster domain and there is DataSource for them.
In each managed server, I setup Timesten client correctly to connect to Timesten Oracle DB cache server.
But when we start each of managed server, I will get exception:
####<Nov 22, 2010 6:03:24 PM CST> <Critical> <WebLogicServer> <Machine1> <Main Thread> <<WLS Kernel>> <1290420204498> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError:
java.lang.AssertionError: Unsupported database driver
at weblogic.cluster.singleton.QueryHelperImpl.getTimeFunction(QueryHelperImpl.java:88)
at weblogic.cluster.singleton.QueryHelper.getLeaseOwnerQuery(QueryHelper.java:110)
at weblogic.cluster.singleton.DatabaseLeasingBasis.pingDB(DatabaseLeasingBasis.java:411)
at weblogic.cluster.singleton.DatabaseLeasingBasis.getJDBCConnection(DatabaseLeasingBasis.java:465)
at weblogic.cluster.singleton.DatabaseLeasingBasis.getJDBCConnection(DatabaseLeasingBasis.java:507)
at weblogic.cluster.singleton.DatabaseLeasingBasis.findOwner(DatabaseLeasingBasis.java:305)
at weblogic.cluster.singleton.LeaseManager.findOwner(LeaseManager.java:218)
at weblogic.cluster.singleton.MigratableServerService.findSingletonMaster(MigratableServerService.java:201)
at weblogic.cluster.singleton.ReplicatedSingletonServicesStateManager.syncStateFromActiveStateManager(ReplicatedSingletonServicesStateManager.java:618)
at weblogic.cluster.singleton.ReplicatedSingletonServicesStateManager.<init>(ReplicatedSingletonServicesStateManager.java:168)
at weblogic.cluster.singleton.SingletonMonitor.<init>(SingletonMonitor.java:97)
at weblogic.cluster.singleton.SingletonMaster.<init>(SingletonMaster.java:44)
at weblogic.cluster.singleton.MigratableServerService.initialize(MigratableServerService.java:142)
at weblogic.cluster.singleton.MigratableServerService.start(MigratableServerService.java:436)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
But if I create a standalone domain, still use the same datasource(still this timesten server), weblogic server can start successfully.
BR,
Peng

Hi,
I have use WebLogic Server Console, tree: Services -> JDBC -> Connection Pools. Then I have choose 'Configure a new JDBC Connection Pool...':
1.) as 'Database Type:' I have select MySQL (version using com.mysql.jdbc.Driver) -> click 'Continue' button;
2.) 'Database Name:' = OSS; 'Host Name' = localhost; 'Port' = 3306; 'Database User Name:' = root; -> click 'Continue' button;
3.) 'Driver Classname:' = com.mysql.jdbc.Driver; 'URL:' = jdbc:mysql://localhost:3306/OSS; 'Database User Name:' = root; 'Properties:' = user=root -> click to 'Test Driver Configuration' button.
After click on test driver button I get message: JDBC driver is not on the CLASSPATH.
But when I check System variables (in Control Panel -> System) I have set up following:
CLASSPATH=.;C:\DB2\java\db2java.zip;C:\DB2\java\db2jcc.jar;C:\DB2\java\sqlj.zip;C:\DB2\java\db2jcc_license_cu.jar;C:\DB2\bin;C:\DB2\java\common.jar;C:\DBS\JDBC\db2\db2.jar;C:\DB2\BIN;c:\mysql.jar
The last value is 'c:\mysql.jar' and that's the mysql jdbc driver located on c:\.
I don't understand why weblogic cannot find it.
Any idea?
Thanks in advance for help,
with best regards,
Julian Legeny

Question about cluster node majority voting

We've been having problems with a DB instance crashing regularly. This weekend when it crashed, it seems to have taken the node it was on with it, or this was a separate incident...
Right now I have 3 nodes in the cluster. 2 nodes are running 3 instances (2 on 1). The 3rd node is in a state where the OS is mostly unusable and the Cluster service will not start.
Event Log:
"The failover cluster database could not be unloaded. If restarting the cluster service does not fix the problem, please restart the machine."
Cluster Log from that machine:
00003768.000067a0::2014/01/06-03:28:05.393 INFO -----------------------------+ LOG BEGIN +-----------------------------
00003768.000067a0::2014/01/06-03:28:05.393 INFO [CS] Starting clussvc as a service
00003768.000067a0::2014/01/06-03:28:05.394 INFO [CS] cluster service logging level is 2
00003768.00004c30::2014/01/06-03:28:05.521 DBG   [NETFTAPI] received NsiInitialNotification
00003768.00004c30::2014/01/06-03:28:05.523 DBG   [NETFTAPI] received NsiInitialNotification
00003768.000031f4::2014/01/06-03:28:05.588 DBG   [NETFTAPI] received NsiAddInstance for 169.254.3.47
00003768.00004eb4::2014/01/06-03:28:05.590 ERR   [DM] Error while restoring (refreshing) the hive: STATUS_INVALID_PARAMETER(c000000d
00003768.00004eb4::2014/01/06-03:28:05.592 ERR   [DM] mscs::DmAgent::Start: STATUS_INVALID_PARAMETER(c000000d' because of 'Load(NOTHROW(), securityAttributes, discardError )'
00003768.00004eb4::2014/01/06-03:28:05.592 ERR   [DM] Node 3: failed to unload cluster hive, error 87.
00003768.00004eb4::2014/01/06-03:28:05.592 ERR   Hive unload failed (status = 87)
00003768.00004eb4::2014/01/06-03:28:05.592 ERR   FatalError is Calling Exit Process.
This is a 3 node cluster set to node majority, I don't have an available drive letter for a witness disk. Since the cluster service won't start, I'm not certain how the cluster is still running, but am thankful that it is.
A reboot might fix everything, but I'm very worried that if I reboot the server, and the cluster service still fails to start... it may prevent the entire cluster from starting and we won't be able to run the instances on the other 2 nodes.
Does the 3rd server still act as an odd-number server, even if the cluster service won't start? If I reboot and the cluster service still fails to start, will the cluster itself be able to be in an UP state and run the DB instances on the other nodes?
I already need to open a MS Support incident on the DB instance crashing, so I'd rather not have to open a 2nd one just to answer this hopefully simple question.
Thanks in advance!
Mark

I'll answer it here, since it matters fundamentally to SQL High Availability.
There are a couple of entities you are conflating here, leading to much confusion. There is a difference between the Cluster and the cluster service.
The cluster service will run on a node once the Failover Cluster Feature is installed on that node. The cluster service will run, even if a cluster is not created. It may generate errors and not participate in a Cluster if it cannot talk to the
other nodes, but it will not shut down.
The Cluster itself requires a quorum, that is a majority of votes, in order to operate. With three nodes, you should choose Node Majority quorum model, which sounds like what you have. Any two votes will count, so the third node being offline
does not matter. You can safely restart the cluster service on the failed nod, and even restart the node. Note that with the third node down, you have no redundancy. (Windows 2012 and 2012 R2 have dynamic quorum, which adjusts the quorum
count based on the last "settled" quorum vote, but that doesn't apply here).
I am concerned with your statement that you are out of drive letters. With three instances, you should have plenty of drive letters left. I suggest investigating Mount Points. You only need one drive letter per instance when using Mount
Points.
Geoff N. Hiten Principal Consultant Microsoft SQL Server MVP

After reboot cluster node went into maintanance mode (CONTROL-D)

Hi there!
I have configured 2 node cluster on 2 x SUN Enterprise 220R and StoreEdge D1000.
Each time when rebooted any of the cluster nodes i get the following error during boot up:
The / file system (/dev/rdsk/c0t1d0s0) is being checked.
/dev/rdsk/c0t1d0s0: UNREF DIR I=35540 OWNER=root MODE=40755
/dev/rdsk/c0t1d0s0: SIZE=512 MTIME=Jun 5 15:02 2006 (CLEARED)
/dev/rdsk/c0t1d0s0: UNREF FILE I=1192311 OWNER=root MODE=100600
/dev/rdsk/c0t1d0s0: SIZE=96 MTIME=Jun 5 13:23 2006 (RECONNECTED)
/dev/rdsk/c0t1d0s0: LINK COUNT FILE I=1192311 OWNER=root MODE=100600
/dev/rdsk/c0t1d0s0: SIZE=96 MTIME=Jun 5 13:23 2006 COUNT 0 SHOULD BE 1
/dev/rdsk/c0t1d0s0: LINK COUNT INCREASING
/dev/rdsk/c0t1d0s0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
In maintanance mode i do:
# fsck -y -F ufs /dev/rdsk/c0t1d0s0
and it managed to correct the problem ... but problem occured again after each reboot on each cluster node!
I have installed Sun CLuster 3.1 on Solaris 9 SPARC
How can i get rid of it?
Any ideas?
Brgds,
Sergej

Hi i get this:
112941-09 SunOS 5.9: sysidnet Utility Patch
116755-01 SunOS 5.9: usr/snadm/lib/libadmutil.so.2 Patch
113434-30 SunOS 5.9: /usr/snadm/lib Library and Differential Flash Patch
112951-13 SunOS 5.9: patchadd and patchrm Patch
114711-03 SunOS 5.9: usr/sadm/lib/diskmgr/VDiskMgr.jar Patch
118064-04 SunOS 5.9: Admin Install Project Manager Client Patch
113742-01 SunOS 5.9: smcpreconfig.sh Patch
113813-02 SunOS 5.9: Gnome Integration Patch
114501-01 SunOS 5.9: drmproviders.jar Patch
112943-09 SunOS 5.9: Volume Management Patch
113799-01 SunOS 5.9: solregis Patch
115697-02 SunOS 5.9: mtmalloc lib Patch
113029-06 SunOS 5.9: libaio.so.1 librt.so.1 and abi_libaio.so.1 Patch
113981-04 SunOS 5.9: devfsadm Patch
116478-01 SunOS 5.9: usr platform links Patch
112960-37 SunOS 5.9: patch libsldap ldap_cachemgr libldap
113332-07 SunOS 5.9: libc_psr.so.1 Patch
116500-01 SunOS 5.9: SVM auto-take disksets Patch
114349-04 SunOS 5.9: sbin/dhcpagent Patch
120441-03 SunOS 5.9: libsec patch
114344-19 SunOS 5.9: kernel/drv/arp Patch
114373-01 SunOS 5.9: UMEM - abi_libumem.so.1 patch
118558-27 SunOS 5.9: Kernel Patch
115675-01 SunOS 5.9: /usr/lib/liblgrp.so Patch
112958-04 SunOS 5.9: patch pci.so
113451-11 SunOS 5.9: IKE Patch
112920-02 SunOS 5.9: libipp Patch
114372-01 SunOS 5.9: UMEM - llib-lumem patch
116229-01 SunOS 5.9: libgen Patch
116178-01 SunOS 5.9: libcrypt Patch
117453-01 SunOS 5.9: libwrap Patch
114131-03 SunOS 5.9: multi-terabyte disk support - libadm.so.1 patch
118465-02 SunOS 5.9: rcm_daemon Patch
113490-04 SunOS 5.9: Audio Device Driver Patch
114926-02 SunOS 5.9: kernel/drv/audiocs Patch
113318-25 SunOS 5.9: patch /kernel/fs/nfs and /kernel/fs/sparcv9/nfs
113070-01 SunOS 5.9: ftp patch
114734-01 SunOS 5.9: /usr/ccs/bin/lorder Patch
114227-01 SunOS 5.9: yacc Patch
116546-07 SunOS 5.9: CDRW DVD-RW DVD+RW Patch
119494-01 SunOS 5.9: mkisofs patch
113471-09 SunOS 5.9: truss Patch
114718-05 SunOS 5.9: usr/kernel/fs/pcfs Patch
115545-01 SunOS 5.9: nss_files patch
115544-02 SunOS 5.9: nss_compat patch
118463-01 SunOS 5.9: du Patch
116016-03 SunOS 5.9: /usr/sbin/logadm patch
115542-02 SunOS 5.9: nss_user patch
116014-06 SunOS 5.9: /usr/sbin/usermod patch
116012-02 SunOS 5.9: ps utility patch
117433-02 SunOS 5.9: FSS FX RT Patch
117431-01 SunOS 5.9: nss_nis Patch
115537-01 SunOS 5.9: /kernel/strmod/ptem patch
115336-03 SunOS 5.9: /usr/bin/tar, /usr/sbin/static/tar Patch
117426-03 SunOS 5.9: ctsmc and sc_nct driver patch
121319-01 SunOS 5.9: devfsadmd_mod.so Patch
121316-01 SunOS 5.9: /kernel/sys/doorfs Patch
121314-01 SunOS 5.9: tl driver patch
116554-01 SunOS 5.9: semsys Patch
112968-01 SunOS 5.9: patch /usr/bin/renice
116552-01 SunOS 5.9: su Patch
120445-01 SunOS 5.9: Toshiba platform token links (TSBW,Ultra-3i)
112964-15 SunOS 5.9: /usr/bin/ksh Patch
112839-08 SunOS 5.9: patch libthread.so.1
115687-02 SunOS 5.9:/var/sadm/install/admin/default Patch
115685-01 SunOS 5.9: sbin/netstrategy Patch
115488-01 SunOS 5.9: patch /kernel/misc/busra
115681-01 SunOS 5.9: usr/lib/fm/libdiagcode.so.1 Patch
113032-03 SunOS 5.9: /usr/sbin/init Patch
113031-03 SunOS 5.9: /usr/bin/edit Patch
114259-02 SunOS 5.9: usr/sbin/psrinfo Patch
115878-01 SunOS 5.9: /usr/bin/logger Patch
116543-04 SunOS 5.9: vmstat Patch
113580-01 SunOS 5.9: mount Patch
115671-01 SunOS 5.9: mntinfo Patch
113977-01 SunOS 5.9: awk/sed pkgscripts Patch
122716-01 SunOS 5.9: kernel/fs/lofs patch
113973-01 SunOS 5.9: adb Patch
122713-01 SunOS 5.9: expr patch
117168-02 SunOS 5.9: mpstat Patch
116498-02 SunOS 5.9: bufmod Patch
113576-01 SunOS 5.9: /usr/bin/dd Patch
116495-03 SunOS 5.9: specfs Patch
117160-01 SunOS 5.9: /kernel/misc/krtld patch
118586-01 SunOS 5.9: cp/mv/ln Patch
120025-01 SunOS 5.9: ipsecconf Patch
116527-02 SunOS 5.9: timod Patch
117155-08 SunOS 5.9: pcipsy Patch
114235-01 SunOS 5.9: libsendfile.so.1 Patch
117152-01 SunOS 5.9: magic Patch
116486-03 SunOS 5.9: tsalarm Driver Patch
121998-01 SunOS 5.9: two-key mode fix for 3DES Patch
116484-01 SunOS 5.9: consconfig Patch
116482-02 SunOS 5.9: modload Utils Patch
117746-04 SunOS 5.9: patch platform/sun4u/kernel/drv/sparcv9/pic16f819
121992-01 SunOS 5.9: fgrep Patch
120768-01 SunOS 5.9: grpck patch
119438-01 SunOS 5.9: usr/bin/login Patch
114389-03 SunOS 5.9: devinfo Patch
116510-01 SunOS 5.9: wscons Patch
114224-05 SunOS 5.9: csh Patch
116670-04 SunOS 5.9: gld Patch
114383-03 SunOS 5.9: Enchilada/Stiletto - pca9556 driver
116506-02 SunOS 5.9: traceroute patch
112919-01 SunOS 5.9: netstat Patch
112918-01 SunOS 5.9: route Patch
112917-01 SunOS 5.9: ifrt Patch
117132-01 SunOS 5.9: cachefsstat Patch
114370-04 SunOS 5.9: libumem.so.1 patch
114010-02 SunOS 5.9: m4 Patch
117129-01 SunOS 5.9: adb Patch
117483-01 SunOS 5.9: ntwdt Patch
114369-01 SunOS 5.9: prtvtoc patch
117125-02 SunOS 5.9: procfs Patch
117480-01 SunOS 5.9: pkgadd Patch
112905-02 SunOS 5.9: ippctl Patch
117123-06 SunOS 5.9: wanboot Patch
115030-03 SunOS 5.9: Multiterabyte UFS - patch mount
114004-01 SunOS 5.9: sed Patch
113335-03 SunOS 5.9: devinfo Patch
113495-05 SunOS 5.9: cfgadm Library Patch
113494-01 SunOS 5.9: iostat Patch
113493-03 SunOS 5.9: libproc.so.1 Patch
113330-01 SunOS 5.9: rpcbind Patch
115028-02 SunOS 5.9: patch /usr/lib/fs/ufs/df
115024-01 SunOS 5.9: file system identification utilities
117471-02 SunOS 5.9: fifofs Patch
118897-01 SunOS 5.9: stc Patch
115022-03 SunOS 5.9: quota utilities
115020-01 SunOS 5.9: patch /usr/lib/adb/ml_odunit
113720-01 SunOS 5.9: rootnex Patch
114352-03 SunOS 5.9: /etc/inet/inetd.conf Patch
123056-01 SunOS 5.9: ldterm patch
116243-01 SunOS 5.9: umountall Patch
113323-01 SunOS 5.9: patch /usr/sbin/passmgmt
116049-01 SunOS 5.9: fdfs Patch
116241-01 SunOS 5.9: keysock Patch
113480-02 SunOS 5.9: usr/lib/security/pam_unix.so.1 Patch
115018-01 SunOS 5.9: patch /usr/lib/adb/dqblk
113277-44 SunOS 5.9: sd and ssd Patch
117457-01 SunOS 5.9: elfexec Patch
113110-01 SunOS 5.9: touch Patch
113077-17 SunOS 5.9: /platform/sun4u/kernal/drv/su Patch
115006-01 SunOS 5.9: kernel/strmod/kb patch
113072-07 SunOS 5.9: patch /usr/sbin/format
113071-01 SunOS 5.9: patch /usr/sbin/acctadm
116782-01 SunOS 5.9: tun Patch
114331-01 SunOS 5.9: power Patch
112835-01 SunOS 5.9: patch /usr/sbin/clinfo
114927-01 SunOS 5.9: usr/sbin/allocate Patch
119937-02 SunOS 5.9: inetboot patch
113467-01 SunOS 5.9: seg_drv & seg_mapdev Patch
114923-01 SunOS 5.9: /usr/kernel/drv/logindmux Patch
117443-01 SunOS 5.9: libkvm Patch
114329-01 SunOS 5.9: /usr/bin/pax Patch
119929-01 SunOS 5.9: /usr/bin/xargs patch
113459-04 SunOS 5.9: udp patch
113446-03 SunOS 5.9: dman Patch
116009-05 SunOS 5.9: sgcn & sgsbbc patch
116557-04 SunOS 5.9: sbd Patch
120241-01 SunOS 5.9: bge: Link & Speed LEDs flash constantly on V20z
113984-01 SunOS 5.9: iosram Patch
113220-01 SunOS 5.9: patch /platform/sun4u/kernel/drv/sparcv9/upa64s
113975-01 SunOS 5.9: ssm Patch
117165-01 SunOS 5.9: pmubus Patch
116530-01 SunOS 5.9: bge.conf Patch
116529-01 SunOS 5.9: smbus Patch
116488-03 SunOS 5.9: Lights Out Management (lom) patch
117131-01 SunOS 5.9: adm1031 Patch
117124-12 SunOS 5.9: platmod, drmach, dr, ngdr, & gptwocfg Patch
114003-01 SunOS 5.9: bbc driver Patch
118539-02 SunOS 5.9: schpc Patch
112837-10 SunOS 5.9: patch /usr/lib/inet/in.dhcpd
114975-01 SunOS 5.9: usr/lib/inet/dhcp/svcadm/dhcpcommon.jar Patch
117450-01 SunOS 5.9: ds_SUNWnisplus Patch
113076-02 SunOS 5.9: dhcpmgr.jar Patch
113572-01 SunOS 5.9: docbook-to-man.ts Patch
118472-01 SunOS 5.9: pargs Patch
122709-01 SunOS 5.9: /usr/bin/dc patch
113075-01 SunOS 5.9: pmap patch
113472-01 SunOS 5.9: madv & mpss lib Patch
115986-02 SunOS 5.9: ptree Patch
115693-01 SunOS 5.9: /usr/bin/last Patch
115259-03 SunOS 5.9: patch usr/lib/acct/acctcms
114564-09 SunOS 5.9: /usr/sbin/in.ftpd Patch
117441-01 SunOS 5.9: FSSdispadmin Patch
113046-01 SunOS 5.9: fcp Patch
118191-01 gtar patch
114818-06 GNOME 2.0.0: libpng Patch
117177-02 SunOS 5.9: lib/gss module Patch
116340-05 SunOS 5.9: gzip and Freeware info files patch
114339-01 SunOS 5.9: wrsm header files Patch
122673-01 SunOS 5.9: sockio.h header patch
116474-03 SunOS 5.9: libsmedia Patch
117138-01 SunOS 5.9: seg_spt.h
112838-11 SunOS 5.9: pcicfg Patch
117127-02 SunOS 5.9: header Patch
112929-01 SunOS 5.9: RIPv2 Header Patch
112927-01 SunOS 5.9: IPQos Header Patch
115992-01 SunOS 5.9: /usr/include/limits.h Patch
112924-01 SunOS 5.9: kdestroy kinit klist kpasswd Patch
116231-03 SunOS 5.9: llc2 Patch
116776-01 SunOS 5.9: mipagent patch
117420-02 SunOS 5.9: mdb Patch
117179-01 SunOS 5.9: nfs_dlboot Patch
121194-01 SunOS 5.9: usr/lib/nfs/statd Patch
116502-03 SunOS 5.9: mountd Patch
113331-01 SunOS 5.9: usr/lib/nfs/rquotad Patch
113281-01 SunOS 5.9: patch /usr/lib/netsvc/yp/ypbind
114736-01 SunOS 5.9: usr/sbin/nisrestore Patch
115695-01 SunOS 5.9: /usr/lib/netsvc/yp/yppush Patch
113321-06 SunOS 5.9: patch sf and socal
113049-01 SunOS 5.9: luxadm & liba5k.so.2 Patch
116663-01 SunOS 5.9: ntpdate Patch
117143-01 SunOS 5.9: xntpd Patch
113028-01 SunOS 5.9: patch /kernel/ipp/flowacct
113320-06 SunOS 5.9: patch se driver
114731-08 SunOS 5.9: kernel/drv/glm Patch
115667-03 SunOS 5.9: Chalupa platform support Patch
117428-01 SunOS 5.9: picl Patch
113327-03 SunOS 5.9: pppd Patch
114374-01 SunOS 5.9: Perl patch
115173-01 SunOS 5.9: /usr/bin/sparcv7/gcore /usr/bin/sparcv9/gcore Patch
114716-02 SunOS 5.9: usr/bin/rcp Patch
112915-04 SunOS 5.9: snoop Patch
116778-01 SunOS 5.9: in.ripngd patch
112916-01 SunOS 5.9: rtquery Patch
112928-03 SunOS 5.9: in.ndpd Patch
119447-01 SunOS 5.9: ses Patch
115354-01 SunOS 5.9: slpd Patch
116493-01 SunOS 5.9: ProtocolTO.java Patch
116780-02 SunOS 5.9: scmi2c Patch
112972-17 SunOS 5.9: patch /usr/lib/libssagent.so.1 /usr/lib/libssasnmp.so.1 mibiisa
116480-01 SunOS 5.9: IEEE 1394 Patch
122485-01 SunOS 5.9: 1394 mass storage driver patch
113716-02 SunOS 5.9: sar & sadc Patch
115651-02 SunOS 5.9: usr/lib/acct/runacct Patch
116490-01 SunOS 5.9: acctdusg Patch
117473-01 SunOS 5.9: fwtmp Patch
116180-01 SunOS 5.9: geniconvtbl Patch
114006-01 SunOS 5.9: tftp Patch
115646-01 SunOS 5.9: libtnfprobe shared library Patch
113334-03 SunOS 5.9: udfs Patch
115350-01 SunOS 5.9: ident_udfs.so.1 Patch
122484-01 SunOS 5.9: preen_md.so.1 patch
117134-01 SunOS 5.9: svm flasharchive patch
116472-02 SunOS 5.9: rmformat Patch
112966-05 SunOS 5.9: patch /usr/sbin/vold
114229-01 SunOS 5.9: action_filemgr.so.1 Patch
114335-02 SunOS 5.9: usr/sbin/rmmount Patch
120443-01 SunOS 5.9: sed core dumps on long lines
121588-01 SunOS 5.9: /usr/xpg4/bin/awk Patch
113470-02 SunOS 5.9: winlock Patch
119211-07 NSS_NSPR_JSS 3.11: NSPR 4.6.1 / NSS 3.11 / JSS 4.2
118666-05 J2SE 5.0: update 6 patch
118667-05 J2SE 5.0: update 6 patch, 64bit
114612-01 SunOS 5.9: ANSI-1251 encodings file errors
114276-02 SunOS 5.9: Extended Arabic support in UTF-8
117400-01 SunOS 5.9: ISO8859-6 and ISO8859-8 iconv symlinks
113584-16 SunOS 5.9: yesstr, nostr nl_langinfo() strings incorrect in S9
117256-01 SunOS 5.9: Remove old OW Xresources.ow files
112625-01 SunOS 5.9: Dcam1394 patch
114600-05 SunOS 5.9: vlan driver patch
117119-05 SunOS 5.9: Sun Gigabit Ethernet 3.0 driver patch
117593-04 SunOS 5.9: Manual Page updates for Solaris 9
112622-19 SunOS 5.9: M64 Graphics Patch
115953-06 Sun Cluster 3.1: Sun Cluster sccheck patch
117949-23 Sun Cluster 3.1: Core Patch for Solaris 9
115081-06 Sun Cluster 3.1: HA-Sun One Web Server Patch
118627-08 Sun Cluster 3.1: Manageability and Serviceability Agent
117985-03 SunOS 5.9: XIL 1.4.2 Loadable Pipeline Libraries
113896-06 SunOS 5.9: en_US.UTF-8 locale patch
114967-02 SunOS 5.9: FDL patch
114677-11 SunOS 5.9: International Components for Unicode Patch
112805-01 CDE 1.5: Help volume patch
113841-01 CDE 1.5: answerbook patch
113839-01 CDE 1.5: sdtwsinfo patch
115713-01 CDE 1.5: dtfile patch
112806-01 CDE 1.5: sdtaudiocontrol patch
112804-02 CDE 1.5: sdtname patch
113244-09 CDE 1.5: dtwm patch
114312-02 CDE1.5: GNOME/CDE Menu for Solaris 9
112809-02 CDE:1.5 Media Player (sdtjmplay) patch
113868-02 CDE 1.5: PDASync patch
119976-01 CDE 1.5: dtterm patch
112771-30 Motif 1.2.7 and 2.1.1: Runtime library patch for Solaris 9
114282-01 CDE 1.5: libDtWidget patch
113789-01 CDE 1.5: dtexec patch
117728-01 CDE1.5: dthello patch
113863-01 CDE 1.5: dtconfig patch
112812-01 CDE 1.5: dtlp patch
113861-04 CDE 1.5: dtksh patch
115972-03 CDE 1.5: dtterm libDtTerm patch
114654-02 CDE 1.5: SmartCard patch
117632-01 CDE1.5: sun_at patch for Solaris 9
113374-02 X11 6.6.1: xpr patch
118759-01 X11 6.6.1: Font Administration Tools patch
117577-03 X11 6.6.1: TrueType fonts patch
116084-01 X11 6.6.1: font patch
113098-04 X11 6.6.1: X RENDER extension patch
112787-01 X11 6.6.1: twm patch
117601-01 X11 6.6.1: libowconfig.so.0 patch
117663-02 X11 6.6.1: xwd patch
113764-04 X11 6.6.1: keyboard patch
113541-02 X11 6.6.1: XKB patch
114561-01 X11 6.6.1: X splash screen patch
113513-02 X11 6.6.1: platform support for new hardware
116121-01 X11 6.4.1: platform support for new hardware
114602-04 X11 6.6.1: libmpg_psr patch
Is there a bundle to install or i have to install each patch separatly_?

Question about cluster node NodeWeight property

Hi,
I have a three nodes (A/B/C) windows 2008 r2 sp1 cluster testCluster, and installed KB2494036 for three nodes,suppose Node A is a active node.
I configured node C's NodeWeight property to 0, and node A and node B keep default (NodeWeight=1). I also added a shared disk Q for cluster quorum.
So i want to know if node C and Node B are down , is the windows cluster testCluster down as lost of quorum or keep up?
At the first i thought testCluster should keep up , because the cluster has 2 votes (node A and quorum), node B is down, node C doesn't join voting. But after testing, testCluster was down as lost of quorum.
So anybody konw the reason,thanks.

Hello mark.gao,
Let me see if I understand correctly your steps, so I can think that if you create your cluster with three nodes at the beginning your quorum model should be "Node Majority", then you have three votes one per each node.
Then was removed the vote for Node "C" and added a disk to be witness for cluster quorum, at this point we have two out of three votes from the original configuration on "Node Majority"
Question:
At some point you changed the quorum model to be "Node and Disk Majority"???
Maybe this is the issue, you are stuck on "Node Majority" and when "B" and "C" nodes are down we have only one vote from node "A" therefore there is no quorum to keep the service online.
On 2012 we have the awesome option to configure a Dynamic Quorum:
Dynamic quorum management
In Windows Server 2012, as an advanced quorum configuration option, you can choose to enable dynamic quorum management by cluster. When this option is enabled, the cluster dynamically manages
the vote assignment to nodes, based on the state of each node. Votes are automatically removed from nodes that leave active cluster membership, and a vote is automatically assigned when a node rejoins the cluster. By default, dynamic quorum management is enabled.
Note
With dynamic quorum management, the cluster quorum majority is determined by the set of nodes that are active members of the cluster at any time. This is an important distinction from the cluster quorum in Windows Server 2008 R2, where the quorum
majority is fixed, based on the initial cluster configuration.
With dynamic quorum management, it is also possible for a cluster to run on the last surviving cluster node. By dynamically adjusting the quorum majority requirement, the cluster can sustain
sequential node shutdowns to a single node.
The cluster-assigned dynamic vote of a node can be verified with the DynamicWeight common property of the cluster node by using the Get-ClusterNodeWindows
PowerShell cmdlet. A value of 0 indicates that the node does not have a quorum vote. A value of 1 indicates that the node has a quorum vote.
The vote assignment for all cluster nodes can be verified by using the Validate Cluster Quorum validation test.
Additional considerations
Dynamic quorum management does not allow the cluster to sustain a simultaneous failure of a majority of voting members. To continue running, the cluster must always have a quorum majority at the time of a node shutdown or failure.
If you have explicitly removed the vote of a node, the cluster cannot dynamically add or remove that vote.
Configure and Manage the Quorum in a Windows Server 2012 Failover Cluster
https://technet.microsoft.com/en-us/library/jj612870.aspx#BKMK_dynamic
Hope this info help you to reach your goal. :D
5ALU2 !

2 node Sun Cluster 3.2, resource groups not failing over.

Hello,
I am currently running two v490s connected to a 6540 Sun Storagetek array. After attempting to install the latest OS patches the cluster seems nearly destroyed. I backed out the patches and right now only one node can process the resource groups properly. The other node will appear to take over the Veritas disk groups but will not mount them automatically. I have been working on this for over a month and have learned alot and fixed alot of other issues that came up, but the cluster is just not working properly. Here is some output.
bash-3.00# clresourcegroup switch -n coins01 DataWatch-rg
clresourcegroup: (C776397) Request failed because node coins01 is not a potential primary for resource group DataWatch-rg. Ensure that when a zone is intended, it is explicitly specified by using the node:zonename format.
bash-3.00# clresourcegroup switch -z zcoins01 -n coins01 DataWatch-rg
clresourcegroup: (C298182) Cannot use node coins01:zcoins01 because it is not currently in the cluster membership.
clresourcegroup: (C916474) Request failed because none of the specified nodes are usable.
bash-3.00# clresource status
=== Cluster Resources ===
Resource Name Node Name State Status Message
ftp-rs coins01:zftp01 Offline Offline
coins02:zftp01 Offline Offline - LogicalHostname offline.
xprcoins coins01:zcoins01 Offline Offline
coins02:zcoins01 Offline Offline - LogicalHostname offline.
xprcoins-rs coins01:zcoins01 Offline Offline
coins02:zcoins01 Offline Offline - LogicalHostname offline.
DataWatch-hasp-rs coins01:zcoins01 Offline Offline
coins02:zcoins01 Offline Offline
BDSarchive-res coins01:zcoins01 Offline Offline
coins02:zcoins01 Offline Offline
I am really at a loss here. Any help appreciated.
Thanks

My advice is to open a service call, provided you have a service contract with Oracle. There is much more information required to understand that specific configuration and to analyse the various log files. This is beyond what can be done in this forum.
From your description I can guess that you want to failover a resource group between non-global zones. And it looks like the zone coins01:zcoins01 is reported to not be in cluster membership.
Obviously node coins01 needs to be a cluster member. If it is reported as online and has joined the cluster, then you need to verify if the zone zcoins01 is really properly up and running.
Specifically you need to verify that it reached the multi-user milestone and all cluster related SMF services are running correctly (ie. verify "svcs -x" in the non-global zone).
You mention Veritas diskgroups. Note that VxVM diskgroups are handled in the global cluster level (ie. in the global zone). The VxVM diskgroup is not imported for a non-global zone. However, with SUNW.HAStoragePlus you can ensure that file systems on top of VxVM diskgroups can be mounted into a non-global zone. But again, more information would be required to see how you configued things and why they don't work as you expect it.
Regards
Thorsten

SAN boot disk in a cluster node?

As far as I remember, SC requires local boot disk.
Is it possible to use the SAN boot disk? Can this configuration work being just not supported by SUN or there is some technical limitation ?
I am thinking of low price configuration with two diskless X2100s + HBAs and SAN storage. Possible?
thanks
-- leon

As far as I remember, SC requires local boot disk.
Is it possible to use the SAN boot disk? Can this
configuration work being just not supported by SUN or
there is some technical limitation ?The rule for boot disks gos like this:
Any local storage device, supported by the base platform as a boot device, can be used as a boot device for the server in the cluster as well. A shared storage device cannot be used as a boot device for a server in a cluster. It is recommended to mirror the root disk. Multipathed boot is supported with Sun Cluster when the drivers associated with SAN 4.3 (or later) are used in conjunction with an appropriate storage device (i.e. the local disks on a SF v880 or a SAN connected fiber storage device).
So your boot disk can be in a SAN as long the base platform supports it as a boot disk and it is not configured as a shared lun in the SAN (i.e. visible to other nodes than the one that uses it as boot disk).
I am thinking of low price configuration with two
diskless X2100s + HBAs and SAN storage. Possible?You need to check the support matrix of the storage device you plan to use, if it is supported as a boot device for the X2100 + HBA. If the answer is yes, you just must make sure that this lun is only visible to that X2100.
Greets
Thorsten

BizTalk Enterprise Passive Cluster Node Licensing Question

Can anyone confirm if you need to license a passive BizTalk Enterprise cluster node if all BizTalk components are not running? If so is there an official reference I can refer to? The PUR has a section on Running Instances that states components must be
in memory to require a license, but no BizTalk components would be in memory if all services are stopped. All references I have read about passive nodes state they must be licensed though.
Nikolai Blackie Adaptiv Integration

The reason I am asking this question is there is a site with a small cluster with all hosts and SSO under cluster management, on the effectively passive node there are no actually running instance of any BizTalk components. Not strictly HA, but certainly
quicker than DR. Personally I would have just used VM failover but that design decision was made a long time ago.
http://msdn.microsoft.com/en-us/library/aa578057.aspx
This is a relatively grey area in terms of licensing the configuration and depending on how you interpret PUR non licensable passive nodes appear to valid under the documented terms.
It would just be great if there was something somewhere that said outright all BizTalk servers in a cluster must have an assigned server license, or cluster nodes with no running components are not licensable =)
Nikolai Blackie Adaptiv Integration

Cluster Node Bootup Sequence

I confuse a situation for long time...
Assume a 2 nodes cluster. When both nodes of cluster down, we attempt to bring up the cluster again. we found one node must keep waiting for another node alive. It stops and showing message: "NOTICE: CMM: Node clusternode-1: attempting to join cluster."
And then we found a rule that: The Last node be shutdown, then firstly be startup.
So the example for the shutdown and startup sequence should be:
1) shutdown node1 -> 2) shutdown node2 -> 3) startup node2 -> 4) startup node1
There is a problem. If node2 is unable to startup again, the node1 seems also can't startup alone for provide service in HA manner.
There is a similar (but not same) situation for VCS. VCS has a command to bringup the single node in this situation "/sbin/gabconfig -c -x"
So we have serveral questions about this situation:
1) Is that a normal situation, that we must face when all nodes was down?
2) Is this caused by misconfiguration of cluster?
3) Is this relate to different version of Sun Cluster (3.1/3.2) ?
4) Is there any command like VCS can awake a single node cluster?

This is the way that Solaris Cluster is supposed to work. It is called amnesia protection. What it does is protect you against the following type of problem:
1. Node 1, Node 2 running with services S1, S2,S3
2. Shutdown node 1
3. Remove/delete S1 - node 1 does not know about this as it is down
4. Shutdown node 2
5. Bring up node 1
Node 1 will have a stale configuration and try to bring up S1, not knowing that it has been deleted.
SC automatically protects against this by the mechanism you've found. There are ways round it and they have been described in other posts in this forum. They should not be used lightly since they override this protection.
Regards,
Tim
---

Does sun Cluster 3.0/3.1 HA Oracle agent support to use Oracle spfile?

When defining the resource, the 'parameter_file' properties is usually sets to the Oracle pfile. Is it possible to use Oracle spfile?
It is said if leaving 'parameter_file' NULL, it will be default to Oracle default. Suppose leaving it NULL and with Oracle spfile created in default location, will it use the spfile?

You did not specify which Sun Cluster version and Oracle version you are running.
Within SC 3.1 my understanding is that beginning with Oracle 9i it is possible to use the spfile.
If you leave the "parameter_file" property empty (NULL) then the default behaviour for 9i should work:
search under $ORACLE_HOME/dbs in the order:
1. spfile$(ORACLE_SID}.ora
2. spfile.ora
3. init${ORACLE_SID}.ora
Greets
Thorsten

Content Server on Sun Cluster

Hello.
Does anybody know, is Contenr Server can work on Sun Cluster?
I did not find any information in notes or PAM. Technically, Sun Cluster support both Apache and MaxDB.

HI,
It is supported on sun cluster. You can use Apache 2.052 and MaxDB 7.6
Anirudh,

Sun Cluster.. Why?

What are the advantages of installing RAC 10.2.0.3 on a Sun Cluster.? Are there any benefits?

Oracle 10g onward, there is no such burning requirement for Sun Cluster (or any third party cluster) as far as you are using all Oracle technologies for your Oracle RAC database. You should Oracle RAC with ASM for shared storage and that would not require any third party cluster. Bear inmind that
You may need to install Sun Cluster in the following scenarios:
1) If there is applicaiton running with in the cluster along with Oracle RAC database that you want to configure for HA and Sun Cluster provide the cluster resourced (easy to use) to manage and monitor the application. THIS can be achieved with Oracle Clusterware but you will have to write your own cluster resource for that.
2) If you want to install cluster file system such as QFS then you will need to install the Sun Cluster. If this cluster is only running the Oracle RAC database then you can rely on Oracle technologies such as ASM, raw devices without installing Sun Cluster.
3) Any certification conflicts.
Any correction is welcome..
-Harish Kumar Kalra

What can I do if I want to use a route that is not supported by my device

I am using a refrence trigger Vi. and I want the source of the trigger to be Ai\ start trigger but this route is not supported by my S series DAQ device.
since I want the source of triggering to be one of the analog input signals that I'm acquiring by my device, I have to use a refrence trigger Vi.
otherwise the source and destination of my triggering would be the samewhich will give me an error.
Is there any other way I can do my triggering by my device or I need to change my device?
Attachments:
vi pic.jpg ‏3547 KB

sorry. I did not attach the vi because i think you may not be able to run it. and also it has some errors in it. here's my Vi.
Attachments:
OFDR 10.28.2014.vi ‏51 KB

"Having a cluster node act as a router is not supported by Sun Cluster"

Similar Messages

Maybe you are looking for