ISE PSN node won't join cluster

Hi All,
Has anyone seen an issue where a PSN can't join the cluster ?
We join PSN Node
-Node is registered sucessfully (sync in progress)
- 1hr later - Replication to node failed.
- Replication Sync failed due to Secondary Database is down
I have a customer where admin node and PSN are seperated by firewall.
We allow in both directions
Admin <--> PSN
ICMP
HTTPS
1521
Firewall not showing drops.
DNS and NTP are ok.
Current topology is 1 PSN, 1 Admin node.
Works fine in our test lab, but not customers environmnet.
Cheers
Peter.

You will probably need more stuff opened between the PSN and the network but your rules between Admin and PSN. You might wanna add syslog udp 20514 as well.
Also, what type of FW are you using? If ASA what happens if you run packet tracer and/or packet capture? Is the flow allowed through and do you see the packets in the capture
Last but not the least, can you confirm that the DB service is running on the secondary node? From CLI run "show application status ise" If is not either restart the node or just issue "application start ise"
Thank you for rating!

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

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

11gR1 1 node won't join the cluster after reboot.

This is a high level description of a problem.
We usually run a two node cluster.
This week we had an issue where one node needed to be taken down. It became non responsive and upon reboot the other node no longer functioned correctly.
So one node was left running until the maintenance window.
Apparently when it's brought back up it has the MAC of the second node in the arp cache.
This leads to node1 not being able to join the cluster.
I've seen workarounds that involve refreshing the arp cache but is there anything else to this?

This is a high level description of a problem.
We usually run a two node cluster.
This week we had an issue where one node needed to be taken down. It became non responsive and upon reboot the other node no longer functioned correctly.
So one node was left running until the maintenance window.
Apparently when it's brought back up it has the MAC of the second node in the arp cache.
This leads to node1 not being able to join the cluster.
I've seen workarounds that involve refreshing the arp cache but is there anything else to this?

How to fix ? please advise: In Adobe LiveCycle ES2, JBOSS(4.2.1.GA) node unable to join cluster after restart.

Hi Team,
We are using Adobe LiveCycle ES2, JBOSS(4.2.1.GA) on windows OS.
We are facing issue after every time we restart JBOSS. JBOSS node after restart is coming up but unable to join the cluster.
We are getting below error in the jboss server.log:
2014-07-18 00:25:37,206 WARN [org.jgroups.protocols.pbcast.GMS] join(10.183.100.39:61469) sent to 10.183.100.39:64118 timed out, retrying
2014-07-18 00:25:44,206 WARN [org.jgroups.protocols.pbcast.GMS] join(10.183.100.39:61469) sent to 10.183.100.39:64118 timed out, retrying
2014-07-18 00:25:51,206 WARN [org.jgroups.protocols.pbcast.GMS] join(10.183.100.39:61469) sent to 10.183.100.39:64118 timed out, retrying
2014-07-18 00:25:58,207 WARN [org.jgroups.protocols.pbcast.GMS] join(10.183.100.39:61469) sent to 10.183.100.39:64118 timed out, retrying
2014-07-18 00:26:05,207 WARN [org.jgroups.protocols.pbcast.GMS] join(10.183.100.39:61469) sent to 10.183.100.39:64118 timed out, retrying
Could you please help to advise on this.
Thanks.

My apologies about the wall of text. After I made my original post, I thought maybe it would better to go back and put it in a pastebin instead. I was not able to edit that post once I sent it.
In regards to your question, the permissions on the
/Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist file is "read and write" for system, wheel and everyone.

Critical VLAN/"fail open" support when ISE PSN is unavailable

This thread regards ISE operation (and options) where a policy node becomes unavailable - so, in the case of either a single standalone ISE appliance (no HA), or more often a PSN becoming unavailable due to a WAN failure to a remote branch. The intended design for the deployment in question would involve using downloadable ACLs (dACLs) to provide differentiated access, specifically:
- A default ACL would be configured on 802.1x switchports would allow "limited" access (possibly Internet-only, but TBD).
- Successful 802.1x authentication would require 1) validation of a corporate certificate on the endpoint, and 2) successful AD login. This would provision a dACL providing full access.
ISE provides the option to configure Inaccessible Authentication Bypass to support RADIUS unavailability when 802.1x is configured on switch ports, but I'm needing to confirm how this works when using dACLs instead of VLANs for differentiated access. Specifically, if IAB is configured so that 802.1x ports (maybe all of them if all ports at the branch need to be functional) get placed into a "critical VLAN", will this override the default ACL on the port, which would no longer be applicable to the new VLAN anyway?
Simply put - we need to configure the deployment so that all endpoints fail open and have full access in the event of ISE/RADIUS becoming unavailable. (There'll be no local RADIUS and/or AD server in the event of WAN failure.) This will need to work although the 802.1x authentication/authorization will be using dACLs to determine access.
Thank you

I have a similar set up i.e. Pre-auth ACL applied on each port which is overwritten by a 'permit ip any any' DACL from the ISE server if a device successfully authenticates.
My understanding is that if the ISE PSN nodes become unavailable then if a Critical Vlan has been configured then devices will be placed into that vlan, however, the pre-auth ACL will still apply. Hence, if the pre-auth ACL only allows limited network connectivity, then in the event of all the ISE PSN nodes being unreachable then the device will only get the connectivity you allow via the pre-auth ACL.
This is obviously quite undesirable and so when I raised this with TAC they suggested that I add an EEM script to each switch so that if the ISE PSN nodes become unavailable then the EEM script will kick in and add a "1 permit ip any any' at the top of the pre-auth ACL.

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

New ISE PSN Does Not Do Anything

Hello,
In my Cisco ISE deployment, I have:
- 1 Primary Admin / Secondary Monitoring Server
- 1 Secondary Admin / Primary Monitoring Server
- 1 Policy Server (up and running without any issues)
- 1 Policy Server (the one that has a problem right now).
After having reimaged it from ACS 5.2 to ISE 1.1.4.218, I registered it as a Policy Service Node. This was done successfully.
The Administration -> Deployment interface on the primary admin node shows that the PSN sync is COMPLETE.
However, no authentication are done on this server and the Home page of the primary server shows a greyed icon with "no Data available".
Any idea ?
Many thanks,
David

Hi,
The full replication is running fine without error.
I saw that on my primary administration server, I have the status of all my deployment. And it shows the following:
- the first ISE server I added to the cluster has the "services" field to All
- the new ISE server I added to the cluster has the "services" field to "SESSION".
If I click on it, I can indeed see that the Profiler Service is not ticked, only the Session is ticked. However, when I registered my new server, I am 100% sure to have ticked the Profiler and the Session services, because I did it twice already.
However, I cannot tick it now because the option is grayed out.
May that be the issue ? How to enable that now ?
Many thanks,
David

What happens if the certificate expire on a ISE PSN

What happens if a PSN certificate expire? Does all other nodes in the cluster looses the communication channel to that PSN node?
What is the procedure to install a new certificate on a PSN node with the expired certificate?
Does the PSN node still handle client RADIUS requests that does not depend on the PSN cerfificate?
Tanks!

You definitely want to renew the certs before they expire. Otherwise the effects can be very devastating to your ISE environment depending on what the certificates are used for :) Below are a couple of links that you can use to obtain more info on both of your questions:
ISE version 1.2:
http://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/116977-technote-ise-cert-00.html
ISE Version 1.3:
http://www.cisco.com/c/en/us/td/docs/security/ise/1-3/admin_guide/b_ise_admin_guide_13/b_ise_admin_guide_sample_chapter_01000.html#concept_D7826198A3304303AD046DB981DA4FE6
Thank you for rating helpful posts!

ISE PSN rejecting RADIUS request

Hi,
We have a distributed ISE infrastructure version 1.3.
We begin noticing the following problem.
Randomly the PSN's started dropping radius requests.
Basically they didn't serviced any client.
It looked like this bug:
ISE PSN rejecting RADIUS request; deadlocks found @ catalina.out
CSCur43427
Symptom:
++ CU runs distributed deployment; 2PSN +MnT +PMN;
++ PSN "node status were up during the issue;
++ PSNs were rejecting RADIUS request; ICMP reachability to PSN were OK;
++ both wired and wireless are affected
++ removing accounting from both foreign/anchor did not fix the issue;
Conditions:
++ ISE 1.2.0.p10
++ happens every 2-3 weeks;
Workaround:
++ restart ISE services;
So we installed patch 2.
But now we got the same problem and there is no newer patch.
Did anyone encountered this also?
thanks,
laszlo

We've also encountered this with 1.3 and logged a TAC case but unfortunately they weren't able to determine the cause due to not enough detail. They suggested changing the log level for runtime-AAA and prrt-JNI to debug temporarily and when it happens again, before restarting the PSN, download the logs from it to supply to TAC.

ISE PSN rebooted and will not rejoin distributed deployment

Hi,
A PSN was powered down by accident and I'm trying to register it back to its PAN as part of a distributed deployment but I keep getting the error message "ISE not in Standalone mode".
I'm not sure how to set the PSN node back to Standalone mode when it's no longer part of the deployment.
Thanks for any help.
Barry

Hi,
Yes Deregister the PSN from the PAN after deregistration this node become Standalone node.

Cisco ISE PSN multicast

Hi
Need to get information regarding Cisco ISE PSN deployment,
How PSN will be synchronizing using a multicast IP address? lets take an scenario, where i have 4 PSN and connected to Cisco switch 3560. what configuration changes are required in Cisco switch?
Lets take another scenario that we have 2 nexus switches in 2 separate DC like SW-1 in DC-1 and SW-2 in DC-2. SW-1 and SW-2 are in VSS mode. 2 PSN connecting in SW-1 and 2 PSN connecting in SW-2. can we maintain a single node group?
with regards,
RK

Hi There,
I think the word replication has triggered a different angle to the question. i understand the theory of node group but in the requirement of multicast, they have just mentioned that it should be L2 adjacent (i.e) in same vlan and same switch.
if multicast traffic should pass through the switch then we need to perform some configuration in switch. By default multicast is enabled in Cisco switches, but no multicast router will be configured. if the application doesn't depend on external multicast router to pass this multicast traffic then default setting is enough. if the application is depends on external multicast router then this should be configured.
if you are seeing the first question, it queries about the configuration requirement in switches to enable multicast between the PSN's in single node group which are connected to same switch and same vlan.
second question queries, in case of Nexus switch in VSS mode, switch behaves as same switch and same vlan will be available. whether single node group in same vlan can be spread across two different nexes switch in VSS mode?
hope the queries are crystal clear. please let me know the answers.
thanks for the time and effort.
with regards,
RK

Can I create different Coherence nodes in the same cluster with defferent?

Can I create different Coherence nodes in the same cluster with defferent cache-config.xml file ?
Can a cache be distributed in these deffirent nodes?

Yes. You can create different Coherence nodes in the same cluster with defferent cache-config.xml files as long as you use the same tangosol-coherence.xml file and the same tangosol-coherence-override.xml file. But you cannot store the cache data in the different nodes (started with different cache-config file). In other word, a node only create caches in their own's modes which are started with the same cache-config.xml file.
See the following demo:
I start a cache server using the cache config file examples-cache-server.xml. Then I start a storage-disabled cache console (cache client) using the cache config file coherence-cache-config.xml. Both of them using the same tangosol-coherence.xml file and the same tangosol-coherence-override.xml file.
The cache server uses a cache service PartitionedPofCache. But the client side is using the Distributedcache service. The cluster address is same 224.3.5.2.
The cluster name is also samme. They know each other.
D:\coherence\lib>D:\examples\java\bin\run-cache-server.cmd
D:\coherence\lib>D:\examples\java\bin\run-cache-server.cmd
The system cannot find the file D:\coherence.
The system cannot find the file C:\Oracle\Middleware\jdk160_11.
2009-12-22 12:09:31.400/4.987 Oracle Coherence 3.5.2/463 <Info> (thread=main, member=n/a): Loaded operational configurat
ion from resource "jar:file:/D:/coherence/lib/coherence.jar!/tangosol-coherence.xml"
2009-12-22 12:09:31.450/5.037 Oracle Coherence 3.5.2/463 <Info> (thread=main, member=n/a): Loaded operational overrides
from resource "jar:file:/D:/coherence/lib/coherence.jar!/tangosol-coherence-override-dev.xml"
2009-12-22 12:09:31.470/5.057 Oracle Coherence 3.5.2/463 <D5> (thread=main, member=n/a): Optional configuration override
"/tangosol-coherence-override.xml" is not specified
2009-12-22 12:09:31.540/5.127 Oracle Coherence 3.5.2/463 <D5> (thread=main, member=n/a): Optional configuration override
"/custom-mbeans.xml" is not specified
Oracle Coherence Version 3.5.2/463
Grid Edition: Development mode
Copyright (c) 2000, 2009, Oracle and/or its affiliates. All rights reserved.
2009-12-22 12:09:33.864/7.451 Oracle Coherence GE 3.5.2/463 <Info> (thread=main, member=n/a): Loaded cache configuration
from "file:/D:/examples/java/resource/config/examples-cache-config.xml"
2009-12-22 12:09:39.983/13.570 Oracle Coherence GE 3.5.2/463 <D5> (thread=Cluster, member=n/a): Service Cluster joined t
he cluster with senior service member n/a
2009-12-22 12:09:43.187/16.774 Oracle Coherence GE 3.5.2/463 <Info> (thread=Cluster, member=n/a): Created a new cluster
"cluster:0xD3FB" with Member(Id=1, Timestamp=2009-12-22 12:09:38.06, Address=192.168.8.80:8088, MachineId=24656, Locatio
n=process:144, Role=CoherenceServer, Edition=Grid Edition, Mode=Development, CpuCount=1, SocketCount=1) UID=0xC0A8085000
000125B75D888C60501F98
2009-12-22 12:09:43.508/17.095 Oracle Coherence GE 3.5.2/463 <D5> (thread=Invocation:Management, member=1): Service Mana
gement joined the cluster with senior service member 1
2009-12-22 12:09:46.582/20.169 Oracle Coherence GE 3.5.2/463 <D5> (thread=DistributedCache:PartitionedPofCache, member=1
): Service PartitionedPofCache joined the cluster with senior service member 1
2009-12-22 12:09:46.672/20.259 Oracle Coherence GE 3.5.2/463 <Info> (thread=DistributedCache:PartitionedPofCache, member
=1): Loading POF configuration from resource "file:/D:/examples/java/resource/config/examples-pof-config.xml"
2009-12-22 12:09:46.702/20.289 Oracle Coherence GE 3.5.2/463 <Info> (thread=DistributedCache:PartitionedPofCache, member
=1): Loading POF configuration from resource "jar:file:/D:/coherence/lib/coherence.jar!/coherence-pof-config.xml"
2009-12-22 12:09:47.734/21.321 Oracle Coherence GE 3.5.2/463 <Info> (thread=main, member=1): Started DefaultCacheServer.
SafeCluster: Name=cluster:0xD3FB
Group{Address=224.3.5.2, Port=35463, TTL=4}
MasterMemberSet
ThisMember=Member(Id=1, Timestamp=2009-12-22 12:09:38.06, Address=192.168.8.80:8088, MachineId=24656, Location=process
:144, Role=CoherenceServer)
OldestMember=Member(Id=1, Timestamp=2009-12-22 12:09:38.06, Address=192.168.8.80:8088, MachineId=24656, Location=proce
ss:144, Role=CoherenceServer)
ActualMemberSet=MemberSet(Size=1, BitSetCount=2
    Member(Id=1, Timestamp=2009-12-22 12:09:38.06, Address=192.168.8.80:8088, MachineId=24656, Location=process:144, Rol
e=CoherenceServer)
RecycleMillis=120000
RecycleSet=MemberSet(Size=0, BitSetCount=0
Services
TcpRing{TcpSocketAccepter{State=STATE_OPEN, ServerSocket=192.168.8.80:8088}, Connections=[]}
ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_JOINED), Id=0, Version=3.5, OldestMemberId=1}
InvocationService{Name=Management, State=(SERVICE_STARTED), Id=1, Version=3.1, OldestMemberId=1}
DistributedCache{Name=PartitionedPofCache, State=(SERVICE_STARTED), LocalStorage=enabled, PartitionCount=257, BackupCo
unt=1, AssignedPartitions=257, BackupPartitions=0}
2009-12-22 12:12:29.737/183.324 Oracle Coherence GE 3.5.2/463 <D5> (thread=Cluster, member=1): Member(Id=2, Timestamp=20
09-12-22 12:12:29.541, Address=192.168.8.80:8089, MachineId=24656, Location=process:1188, Role=CoherenceConsole) joined
Cluster with senior member 1
2009-12-22 12:12:30.498/184.085 Oracle Coherence GE 3.5.2/463 <D5> (thread=Cluster, member=1): Member 2 joined Service M
anagement with senior member 1
2009-12-22 12:12:31.860/185.447 Oracle Coherence GE 3.5.2/463 <D5> (thread=Cluster, member=1): TcpRing: connecting to me
mber 2 using TcpSocket{State=STATE_OPEN, Socket=Socket[addr=/192.168.8.80,port=8089,localport=2463]}
2009-12-22 12:12:51.338/204.925 Oracle Coherence GE 3.5.2/463 <D5> (thread=Cluster, member=1): Member 2 joined Service D
istributedCache with senior member 2The following command starts a cache client.
D:\coherence\bin>coherence.cmd
D:\coherence\bin>coherence.cmd
** Starting storage disabled console **
java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) Server VM (build 11.0-b16, mixed mode)
2009-12-22 12:12:21.054/3.425 Oracle Coherence 3.5.2/463 <Info> (thread=main, member=n/a): Loaded operational configurat
ion from resource "jar:file:/D:/coherence/lib/coherence.jar!/tangosol-coherence.xml"
2009-12-22 12:12:21.355/3.726 Oracle Coherence 3.5.2/463 <Info> (thread=main, member=n/a): Loaded operational overrides
from resource "jar:file:/D:/coherence/lib/coherence.jar!/tangosol-coherence-override-dev.xml"
2009-12-22 12:12:21.365/3.736 Oracle Coherence 3.5.2/463 <D5> (thread=main, member=n/a): Optional configuration override
"/tangosol-coherence-override.xml" is not specified
2009-12-22 12:12:21.415/3.786 Oracle Coherence 3.5.2/463 <D5> (thread=main, member=n/a): Optional configuration override
"/custom-mbeans.xml" is not specified
Oracle Coherence Version 3.5.2/463
Grid Edition: Development mode
Copyright (c) 2000, 2009, Oracle and/or its affiliates. All rights reserved.
2009-12-22 12:12:29.316/11.687 Oracle Coherence GE 3.5.2/463 <D5> (thread=Cluster, member=n/a): Service Cluster joined t
he cluster with senior service member n/a
2009-12-22 12:12:29.356/11.727 Oracle Coherence GE 3.5.2/463 <Info> (thread=Cluster, member=n/a): Failed to satisfy the
variance: allowed=16, actual=20
2009-12-22 12:12:29.356/11.727 Oracle Coherence GE 3.5.2/463 <Info> (thread=Cluster, member=n/a): Increasing allowable v
ariance to 17
2009-12-22 12:12:29.807/12.178 Oracle Coherence GE 3.5.2/463 <Info> (thread=Cluster, member=n/a): This Member(Id=2, Time
stamp=2009-12-22 12:12:29.541, Address=192.168.8.80:8089, MachineId=24656, Location=process:1188, Role=CoherenceConsole,
Edition=Grid Edition, Mode=Development, CpuCount=1, SocketCount=1) joined cluster "cluster:0xD3FB" with senior Member(I
d=1, Timestamp=2009-12-22 12:09:38.06, Address=192.168.8.80:8088, MachineId=24656, Location=process:144, Role=CoherenceS
erver, Edition=Grid Edition, Mode=Development, CpuCount=1, SocketCount=1)
2009-12-22 12:12:29.977/12.348 Oracle Coherence GE 3.5.2/463 <D5> (thread=Cluster, member=n/a): Member 1 joined Service
Management with senior member 1
2009-12-22 12:12:29.977/12.348 Oracle Coherence GE 3.5.2/463 <D5> (thread=Cluster, member=n/a): Member 1 joined Service
PartitionedPofCache with senior member 1
2009-12-22 12:12:30.578/12.949 Oracle Coherence GE 3.5.2/463 <D5> (thread=Invocation:Management, member=2): Service Mana
gement joined the cluster with senior service member 1
SafeCluster: Name=cluster:0xD3FB
Group{Address=224.3.5.2, Port=35463, TTL=4}
MasterMemberSet
ThisMember=Member(Id=2, Timestamp=2009-12-22 12:12:29.541, Address=192.168.8.80:8089, MachineId=24656, Location=proces
s:1188, Role=CoherenceConsole)
OldestMember=Member(Id=1, Timestamp=2009-12-22 12:09:38.06, Address=192.168.8.80:8088, MachineId=24656, Location=proce
ss:144, Role=CoherenceServer)
ActualMemberSet=MemberSet(Size=2, BitSetCount=2
    Member(Id=1, Timestamp=2009-12-22 12:09:38.06, Address=192.168.8.80:8088, MachineId=24656, Location=process:144, Rol
e=CoherenceServer)
    Member(Id=2, Timestamp=2009-12-22 12:12:29.541, Address=192.168.8.80:8089, MachineId=24656, Location=process:1188, R
ole=CoherenceConsole)
RecycleMillis=120000
RecycleSet=MemberSet(Size=0, BitSetCount=0
Services
TcpRing{TcpSocketAccepter{State=STATE_OPEN, ServerSocket=192.168.8.80:8089}, Connections=[]}
ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_JOINED), Id=0, Version=3.5, OldestMemberId=1}
InvocationService{Name=Management, State=(SERVICE_STARTED), Id=1, Version=3.1, OldestMemberId=1}
Map (?):
2009-12-22 12:12:49.505/31.906 Oracle Coherence GE 3.5.2/463 <Info> (thread=main, member=2): Loaded cache configuration
from "jar:file:/D:/coherence/lib/coherence.jar!/coherence-cache-config.xml"
2009-12-22 12:12:51.358/33.729 Oracle Coherence GE 3.5.2/463 <D5> (thread=DistributedCache, member=2): Service Distribut
edCache joined the cluster with senior service member 2
<distributed-scheme>

<scheme-name>example-distributed</scheme-name>
<service-name>DistributedCache</service-name>
<backing-map-scheme>
    <local-scheme>
      <scheme-ref>example-binary-backing-map</scheme-ref>
    </local-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>But when I try to store data into cache from the client side, it report error message: it's staorage-disabled. It shows that this cache console cannot store the data in the existing cache server because then using different cache config files.
Map (ca3): cache ca2
<distributed-scheme>

<scheme-name>example-distributed</scheme-name>
<service-name>DistributedCache</service-name>
<backing-map-scheme>
    <local-scheme>
      <scheme-ref>example-binary-backing-map</scheme-ref>
    </local-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
Map (ca2): put 1 one
2009-12-22 14:00:04.999/6467.370 Oracle Coherence GE 3.5.2/463 <Error> (thread=main, member=2):
java.lang.RuntimeException: Storage is not configured
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.onMissing
Storage(DistributedCache.CDB:9)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.ensureReq
uestTarget(DistributedCache.CDB:34)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.put(Distr
ibutedCache.CDB:22)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.put(Distr
ibutedCache.CDB:1)
        at com.tangosol.util.ConverterCollections$ConverterMap.put(ConverterCollections.java:1541)
        at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ViewMap.put(Distrib
utedCache.CDB:1)
        at com.tangosol.coherence.component.util.SafeNamedCache.put(SafeNamedCache.CDB:1)
        at com.tangosol.coherence.component.application.console.Coherence.processCommand(Coherence.CDB:581)
        at com.tangosol.coherence.component.application.console.Coherence.run(Coherence.CDB:39)
        at com.tangosol.coherence.component.application.console.Coherence.main(Coherence.CDB:3)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.tangosol.net.CacheFactory.main(CacheFactory.java:1400)

Coherence.jar in EAR - ejbmodule error while joining cluster senior member

Hi
We are trying to package coherence in EAR to connect to JMS queue. The ejb MDB module when a message is received process the data and tries to connect to coherence cluster members - Looking at the following log - right coherence config file/override/pof are picked however while this new member join DistributedService - it fails.
The senior member has 13001 partition, backup count 1. Both MDB module , coherence cluster use the same cache-config file.
Can someone help me in this regard.
Thanks
sunder
2011-10-12 11:18:05.351/2523.753 Oracle Coherence GE 3.7.0.0 <Info> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Loaded cache configuration from "file:/data/blazecache/config/SDR-Cache-config.xml"
2011-10-12 11:18:05.980/2524.382 Oracle Coherence GE 3.7.0.0 <D4> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): TCMP bound to /10.160.57.138:8092 using SystemSocketProvider
2011-10-12 11:18:06.211/2524.613 Oracle Coherence GE 3.7.0.0 <Info> (thread=Cluster, member=n/a): Failed to satisfy the variance: allowed=16, actual=41
2011-10-12 11:18:06.211/2524.613 Oracle Coherence GE 3.7.0.0 <Info> (thread=Cluster, member=n/a): Increasing allowable variance to 19
2011-10-12 11:18:06.538/2524.940 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=6): Member(Id=4, Timestamp=2011-10-12 11:18:06.332, Address=10.160.57.138:8092, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:8703, Role=WeblogicServer) joined Cluster with senior member 1
2011-10-12 11:18:06.539/2524.941 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=8): Member(Id=4, Timestamp=2011-10-12 11:18:06.332, Address=10.160.57.138:8092, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:8703, Role=WeblogicServer) joined Cluster with senior member 1
2011-10-12 11:18:06.553/2524.955 Oracle Coherence GE 3.7.0.0 <Info> (thread=Cluster, member=n/a): This Member(Id=4, Timestamp=2011-10-12 11:18:06.332, Address=10.160.57.138:8092, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:8703, Role=WeblogicServer, Edition=Grid Edition, Mode=Development, CpuCount=1, SocketCount=1) joined cluster "sdrcluster_dev.dell.com" with senior Member(Id=1, Timestamp=2011-10-12 09:43:00.859, Address=10.160.57.138:14001, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:6992,member:BlazeCacheServerDEV01_1, Role=WeblogicWeblogicCacheServer, Edition=Grid Edition, Mode=Development, CpuCount=1, SocketCount=1)
2011-10-12 11:18:06.593/2524.995 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member(Id=2, Timestamp=2011-10-12 09:43:35.556, Address=10.160.57.138:14003, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:6989,member:BlazeCacheExtendServerDEV01_1, Role=WeblogicWeblogicCacheServer) joined Cluster with senior member 1
2011-10-12 11:18:06.595/2524.997 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member(Id=3, Timestamp=2011-10-12 09:43:35.983, Address=10.160.57.138:14005, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:7034,member:BlazeCacheServerDEV01_2, Role=WeblogicWeblogicCacheServer) joined Cluster with senior member 1
2011-10-12 11:18:06.595/2524.997 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member(Id=6, Timestamp=2011-10-12 10:36:33.614, Address=10.160.57.138:8088, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:8703, Role=WeblogicServer) joined Cluster with senior member 1
2011-10-12 11:18:06.595/2524.997 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member(Id=8, Timestamp=2011-10-12 10:42:51.491, Address=10.160.57.138:8090, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:8703, Role=WeblogicServer) joined Cluster with senior member 1
2011-10-12 11:18:06.652/2525.054 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 1 joined Service Cluster with senior member 1
2011-10-12 11:18:06.653/2525.055 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 1 joined Service Management with senior member 1
2011-10-12 11:18:06.653/2525.055 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistributedCache1 with senior member 1
2011-10-12 11:18:06.654/2525.056 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 2 joined Service Cluster with senior member 1
2011-10-12 11:18:06.654/2525.056 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 2 joined Service Management with senior member 1
2011-10-12 11:18:06.654/2525.056 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 2 joined Service DistributedCache1 with senior member 1
2011-10-12 11:18:06.654/2525.056 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 2 joined Service ExtendTcpProxyService with senior member 2
2011-10-12 11:18:06.654/2525.056 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 3 joined Service Cluster with senior member 1
2011-10-12 11:18:06.654/2525.056 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 3 joined Service Management with senior member 1
2011-10-12 11:18:06.654/2525.056 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 3 joined Service DistributedCache1 with senior member 1
2011-10-12 11:18:06.654/2525.056 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 6 joined Service Cluster with senior member 1
2011-10-12 11:18:06.654/2525.056 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 6 joined Service Management with senior member 1
2011-10-12 11:18:06.654/2525.056 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 8 joined Service Cluster with senior member 1
2011-10-12 11:18:06.654/2525.056 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=n/a): Member 8 joined Service Management with senior member 1
2011-10-12 11:18:06.661/2525.063 Oracle Coherence GE 3.7.0.0 <Info> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Started cluster Name=sdrcluster_dev.dell.com
WellKnownAddressList(Size=1,
WKA{Address=10.160.57.138, Port=14001}
MasterMemberSet
ThisMember=Member(Id=4, Timestamp=2011-10-12 11:18:06.332, Address=10.160.57.138:8092, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:8703, Role=WeblogicServer)
OldestMember=Member(Id=1, Timestamp=2011-10-12 09:43:00.859, Address=10.160.57.138:14001, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:6992,member:BlazeCacheServerDEV01_1, Role=WeblogicWeblogicCacheServer)
ActualMemberSet=MemberSet(Size=6, BitSetCount=2
Member(Id=1, Timestamp=2011-10-12 09:43:00.859, Address=10.160.57.138:14001, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:6992,member:BlazeCacheServerDEV01_1, Role=WeblogicWeblogicCacheServer)
Member(Id=2, Timestamp=2011-10-12 09:43:35.556, Address=10.160.57.138:14003, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:6989,member:BlazeCacheExtendServerDEV01_1, Role=WeblogicWeblogicCacheServer)
Member(Id=3, Timestamp=2011-10-12 09:43:35.983, Address=10.160.57.138:14005, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:7034,member:BlazeCacheServerDEV01_2, Role=WeblogicWeblogicCacheServer)
Member(Id=4, Timestamp=2011-10-12 11:18:06.332, Address=10.160.57.138:8092, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:8703, Role=WeblogicServer)
Member(Id=6, Timestamp=2011-10-12 10:36:33.614, Address=10.160.57.138:8088, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:8703, Role=WeblogicServer)
Member(Id=8, Timestamp=2011-10-12 10:42:51.491, Address=10.160.57.138:8090, MachineId=12174, Location=site:us.dell.com,machine:austeochr01,process:8703, Role=WeblogicServer)
RecycleMillis=1200000
RecycleSet=MemberSet(Size=0, BitSetCount=0
TcpRing{Connections=[3, 8]}
IpMonitor{AddressListSize=0}
2011-10-12 11:18:06.741/2525.143 Oracle Coherence GE 3.7.0.0 <D5> (thread=Invocation:Management, member=4): Service Management joined the cluster with senior service member 1
2011-10-12 11:18:06.750/2525.152 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=6): Member 4 joined Service Management with senior member 1
2011-10-12 11:18:06.751/2525.153 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=8): Member 4 joined Service Management with senior member 1
2011-10-12 11:18:07.299/2525.701 Oracle Coherence GE 3.7.0.0 <Info> (thread=DistributedCache:DistributedCache1, member=4): Loaded POF configuration from "file:/data/blazecache/config/SDR-coherence-pof-config.xml"
2011-10-12 11:18:07.306/2525.708 Oracle Coherence GE 3.7.0.0 <Info> (thread=DistributedCache:DistributedCache1, member=4): Loaded included POF configuration from "zip:/data/oracle/middleware/user_projects/domains/BlazeDEV/servers/BlazeJMS/tmp/_WL_user/BlazeMDBEAR/1pwed8/APP-INF/lib/coherence.jar!/coherence-pof-config.xml"
2011-10-12 11:18:07.382/2525.784 Oracle Coherence GE 3.7.0.0 <D5> (thread=DistributedCache:DistributedCache1, member=4): Service DistributedCache1 joined the cluster with senior service member 1
2011-10-12 11:18:07.454/2525.856 Oracle Coherence GE 3.7.0.0 <Warning> (thread=DistributedCache:DistributedCache1, member=4): This node is configured with a 'partition-count' value of 257, but the service senior is using a value of 13001; overriding the local configuration.
2011-10-12 11:18:07.455/2525.857 Oracle Coherence GE 3.7.0.0 <Warning> (thread=DistributedCache:DistributedCache1, member=4): This node is configured with a 'backup-count' value of 1, but the service senior is using a value of 0; overriding the local configuration.
2011-10-12 11:18:07.456/2525.858 Oracle Coherence GE 3.7.0.0 <Error> (thread=DistributedCache:DistributedCache1, member=4): Incompatible KeyAssociator implementation: this node is configured to use com.tangosol.net.partition.DefaultKeyAssociator, but the service senior is using com.dell.it.services.sdr.blazeload.partaffinity.BlazeCacheKeyAssociator; stopping the service.
2011-10-12 11:18:07.466/2525.868 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=6): Member 4 left service DistributedCache1 with senior member 1
2011-10-12 11:18:07.467/2525.869 Oracle Coherence GE 3.7.0.0 <D5> (thread=Cluster, member=8): Member 4 left service DistributedCache1 with senior member 1
2011-10-12 11:18:07.477/2525.879 Oracle Coherence GE 3.7.0.0 <D5> (thread=DistributedCache:DistributedCache1, member=4): Service DistributedCache1 left the cluster
2011-10-12 11:18:07.477/2525.879 Oracle Coherence GE 3.7.0.0 <Error> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=4): Error while starting service "DistributedCache1": java.lang.RuntimeException: Failed to start Service "DistributedCache1" (ServiceState=SERVICE_STOPPED)
2011-10-12 11:18:07.477/2525.879 Oracle Coherence GE 3.7.0.0 <Error> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=4): at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:38)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.util.SafeService.startService(SafeService.CDB:39)
at com.tangosol.coherence.component.util.safeService.SafeCacheService.startService(SafeCacheService.CDB:5)
at com.tangosol.coherence.component.util.SafeService.ensureRunningService(SafeService.CDB:27)
at com.tangosol.coherence.component.util.SafeService.start(SafeService.CDB:14)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:1102)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:934)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:916)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1293)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:294)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:204)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:181)
at com.dell.it.services.sdr.blazeinc.util.CustomerProductUpdate.recordExists(CustomerProductUpdate.java:267)
at com.dell.it.services.sdr.blazeinc.util.CustomerProductUpdate.insert(CustomerProductUpdate.java:222)
at com.dell.it.services.sdr.blazeinc.util.DataMapperUtility.mapToBean(DataMapperUtility.java:260)
at com.dell.it.services.sdr.blazeinc.util.DataMapperUtility.mapToBean(DataMapperUtility.java:119)
at com.dell.it.services.sdr.blazeinc.listener.BlazeMDB.onMessage(BlazeMDB.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

The KeyAssociator implementation is MDB classpath as well.
Here is the configuration override config
===========
<coherence>
<cluster-config>
     <member-identity>
<cluster-name system-property="tangosol.coherence.cluster">sdrcluster_dev.XX.com</cluster-name>
     </member-identity>
<unicast-listener>

<well-known-addresses>

<socket-address id="austeochr01.us.XX.com">
<address>austeochr01.us.XX.com</address>
<port>14001</port>
</socket-address>
</well-known-addresses>
</unicast-listener>
<shutdown-listener>
<enabled system-property="tangosol.coherence.shutdownhook">false</enabled>
</shutdown-listener>
<service-guardian>
     <timeout-milliseconds system-property="tangosol.coherence.guard.timeout">360000</timeout-milliseconds>
</service-guardian>
</cluster-config>
<configurable-cache-factory-config>
<class-name>com.tangosol.net.DefaultConfigurableCacheFactory</class-name>
<init-params>
<init-param>
<param-type>java.lang.String</param-type>
<param-value system-property="tangosol.coherence.cacheconfig">/data/blazecache/config/SDR-Cache-config.xml</param-value>
</init-param>
</init-params>
</configurable-cache-factory-config>
</coherence>
Here is the Cache config
=========
<?xml version="1.0" encoding="UTF-8"?>
<cache-config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns="http://xmlns.oracle.com/coherence/coherence-cache-config"
     xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-cache-config/coherence-cache-config.xsd">
     <caching-scheme-mapping>
          <cache-mapping>
               <cache-name>blaze-local-*</cache-name>
               <scheme-name>blaze-local</scheme-name>
          </cache-mapping>
          <cache-mapping>
               <cache-name>blaze-distributed-ASSET_HEADER_DATA</cache-name>
               <scheme-name>blaze-distributed-AssetHeaderData</scheme-name>
          </cache-mapping>
          <cache-mapping>
               <cache-name>blaze-distributed-ENTITLEMENT_SUMMARY_DATA</cache-name>
               <scheme-name>blaze-distributed-EntitlementSummaryData</scheme-name>
          </cache-mapping>
     </caching-scheme-mapping>
     <caching-schemes>
          <local-scheme>
               <scheme-name>blaze-local</scheme-name>
               <expiry-delay>0</expiry-delay>
          </local-scheme>
          <distributed-scheme>
               <scheme-name>blaze-distributed-AssetHeaderData</scheme-name>
               <service-name>DistributedCache1</service-name>
               <serializer>
                    <class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
                    <init-params>
                         <init-param>
                         <param-type>java.lang.String</param-type>
                         <param-value>/data/blazecache/config/SDR-coherence-pof-config.xml</param-value>
                         </init-param>
                    </init-params>
               </serializer>
               <thread-count>40</thread-count>
               <backup-count>0</backup-count>
               <backup-storage>
                    <flashjournal-scheme />
               </backup-storage>
               <key-associator>
                    <class-name>com.XX.it.services.sdr.blazeload.partaffinity.BlazeCacheKeyAssociator</class-name>
          </key-associator>
<partition-count>13001</partition-count>
<task-hung-threshold>360000</task-hung-threshold>
<task-timeout>360000</task-timeout>
<backing-map-scheme>
<partitioned>true</partitioned>
                    <read-write-backing-map-scheme>
                         <scheme-name>DBCacheLoaderScheme</scheme-name>
                         <internal-cache-scheme>
<local-scheme>
<expiry-delay>0</expiry-delay>
<high-units>3</high-units>
<unit-calculator>BINARY</unit-calculator>
<unit-factor>1073741824</unit-factor>
</local-scheme>
                         </internal-cache-scheme>
                         <read-only>true</read-only>
                    </read-write-backing-map-scheme>
               </backing-map-scheme>
               <autostart>true</autostart>
          </distributed-scheme>
          <distributed-scheme>
                         <scheme-name>blaze-distributed-EntitlementSummaryData</scheme-name>
                         <service-name>DistributedCache1</service-name>
               <serializer>
                    <class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
                    <init-params>
                         <init-param>
                         <param-type>java.lang.String</param-type>
                         <param-value>/data/blazecache/config/SDR-coherence-pof-config.xml</param-value>
                         </init-param>
                    </init-params>
               </serializer>
                         <key-associator>
               <class-name>com.XX.it.services.sdr.blazeload.partaffinity.BlazeCacheKeyAssociator</class-name>
                    </key-associator>
                         <thread-count>40</thread-count>
                         <backup-count>1</backup-count>
                         <backup-storage>
                              <flashjournal-scheme />
                         </backup-storage>
          <partition-count>13001</partition-count>
                         <task-hung-threshold>360000</task-hung-threshold>
                         <task-timeout>360000</task-timeout>
                         <backing-map-scheme>
<partitioned>true</partitioned>
                              <read-write-backing-map-scheme>
                                   <scheme-name>DBCacheLoaderScheme</scheme-name>
                                   <internal-cache-scheme>
<local-scheme>
<expiry-delay>0</expiry-delay>
<high-units>3</high-units>
<unit-calculator>BINARY</unit-calculator>
<unit-factor>1073741824</unit-factor>
</local-scheme>
                                   </internal-cache-scheme>
                                   <read-only>true</read-only>
                              </read-write-backing-map-scheme>
                         </backing-map-scheme>
                         <autostart>true</autostart>
          </distributed-scheme>
<proxy-scheme>
<service-name>ExtendTcpProxyService</service-name>
<thread-count>5</thread-count>
<acceptor-config>
<tcp-acceptor>
<local-address>
<address system-property="tangosol.coherence.session.proxy.localhost"></address>
<port system-property="tangosol.coherence.session.proxy.localport"></port>
</local-address>
</tcp-acceptor>
</acceptor-config>
<task-hung-threshold>360000</task-hung-threshold>
<task-timeout>360000</task-timeout>
<proxy-config>
<cache-service-proxy>
<enabled>true</enabled>
</cache-service-proxy>
<invocation-service-proxy>
<enabled>true</enabled>
</invocation-service-proxy>
</proxy-config>
<autostart system-property="tangosol.coherence.session.proxy"></autostart>
</proxy-scheme>
          <class-scheme>
               <scheme-name>default-backing-map</scheme-name>
               <class-name>com.tangosol.util.SafeHashMap</class-name>
          </class-scheme>
     </caching-schemes>
</cache-config>
Thanks
sunder

Maximum number of nodes in a Weblogic cluster on RedHat Linux?

Is there a limitation of the number of nodes in a weblogic cluster
          running under RedHat Linux?
          Can I start with 5 nodes and in a year scale up to 500 or 5000 nodes?
          Thanks!
          Ralf.


Ralf,
          > Is there a limitation of the number of nodes in a weblogic cluster
          > running under RedHat Linux?
          A realistic limit, of course.
          > Can I start with 5 nodes and in a year scale up to 500 or 5000 nodes?
          If your app is completely stateless, then it can scale to 40 maybe 80
          servers.
          The problem is that stateless apps typically manage state that sits behind
          them, and there's basically no database in the world that can handle the
          load that 40 servers can put on it. Depending on the app, you can easily
          saturate 4 database CPUs per 1 app server CPU, but usually the factor is
          closer to 1:1, and with agressive caching in the app tier even less.
          Things like stateful session bean replication and HTTP session replication
          in a cluster ... well, YMMV ... but I would hypothesize that it won't scale
          up anywhere close to 40 servers under load.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com/coherence.jsp
          Tangosol Coherence: Clustered Replicated Cache for Weblogic
          "Ralf Reddin" <[email protected]> wrote in message
          news:[email protected]..
          >

ISE PSN node won't join cluster

Similar Messages

Maybe you are looking for