sun Cluster resource group cant failover


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications High Performance Computing sun Cluster resource group cant failover
# 1  
Old 07-08-2008
sun Cluster resource group cant failover

I have rcently setup a 4 node cluster running sun cluster 3.2

and I have installed 4 zones on each node. when installing the zones I had to install the zone on all nodes the on the last node do a zlogin -C <zonename>

this worked ok.

theni I tried to siwitch the zone to node a thei work fine when I try to switch to node b this also works fine but whenI try to switch to c or d this doe not work .
it seems like it get to a certain stage the it falls over when trying to load the zone-rs I have setup HAStorage plus to deal iwth mounting the file system and this works fine for a and b but it can load the zone-rs does any one have any cluse ?
# 2  
Old 07-08-2008
open up 2 sessions. perform the failover on one session. on the other, tail the cluster log file and show me what you're getting.
# 3  
Old 07-08-2008
Cluster failover issue

Can you confirm where the cluster logs are kept ? I assume you are not taling about /var/adm/messages
# 4  
Old 07-09-2008
log files - /var/cluster/logs, /var/adm/messages
sccheck logs - /var/cluster/sccheck/report.<date>
CCR files - /etc/cluster/ccr
Cluster Infra file - /etc/cluster/ccr/infrastructure
# 5  
Old 07-09-2008
Hi,

Thanks for geting back in contact. I have attached a copy of the messages file when trying to failover the prox2-rg resource group,
I will send additional info from the files you have requested:-

Jul 9 11:54:51 C2SRV2 Cluster.RGM.rgmd: [ID 224900 daemon.notice] launching method <hastorageplus_prenet_start> for resource <proxy2-HAS-rs>, resource group <proxy2-rg>, node <C2SRV2>, timeout <1800> seconds
Jul 9 11:54:51 C2SRV2 Cluster.RGM.rgmd: [ID 252072 daemon.notice] 50 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hastorageplus/hastorageplus_prenet_start>:tag=<proxy2-rg.proxy2-HAS-rs.10>: Calling security_clnt_connect(..., host=<C2SRV2>, sec_type {0:WEAK, 1:STRONG, 2SmilieES} =<1>, ...)
Jul 9 11:54:51 C2SRV2 Cluster.RGM.rgmd: [ID 285716 daemon.notice] 20 fe_rpc_command: cmd_type(enum):<2>:cmd=<null>:tag=<proxy2-rg.proxy2-HAS-rs.10>: Calling security_clnt_connect(..., host=<C2SRV2>, sec_type {0:WEAK, 1:STRONG, 2SmilieES} =<0>, ...)
Jul 9 11:54:51 C2SRV2 Cluster.RGM.rgmd: [ID 316625 daemon.notice] Timeout monitoring on method tag <proxy2-rg.proxy2-HAS-rs.10> has been suspended.
Jul 9 11:54:54 C2SRV2 Cluster.Framework: [ID 801593 daemon.notice] stdout: becoming primary for proxy2-dg
Jul 9 11:54:56 C2SRV2 scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Jul 9 11:54:56 C2SRV2 /scsi_vhci/ssd@g600a0b800029d28e000005ff48649a5c (ssd24): path /pci@780/SUNW,qlc@0/fp@0,0 (fp1) target address 200a00a0b829d290,b is now STANDBY because of an externally initiated failover
Jul 9 11:55:01 C2SRV2 scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Jul 9 11:55:01 C2SRV2 Initiating failover for device ssd (GUID 600a0b800029d28e000005ff48649a5c)
Jul 9 11:55:03 C2SRV2 scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Jul 9 11:55:03 C2SRV2 Failover operation completed successfully for device ssd (GUID 600a0b800029d28e000005ff48649a5c): failed over from <none> to primary
Jul 9 11:55:03 C2SRV2 scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Jul 9 11:55:03 C2SRV2 /scsi_vhci/ssd@g600a0b800029d2160000057148649e21 (ssd25): path /pci@780/SUNW,qlc@0/fp@0,0 (fp1) target address 200a00a0b829d290,c is now STANDBY because of an externally initiated failover
Jul 9 11:55:08 C2SRV2 scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Jul 9 11:55:08 C2SRV2 Initiating failover for device ssd (GUID 600a0b800029d2160000057148649e21)
Jul 9 11:55:09 C2SRV2 scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Jul 9 11:55:09 C2SRV2 Failover operation completed successfully for device ssd (GUID 600a0b800029d2160000057148649e21): failed over from <none> to secondary
Jul 9 11:55:10 C2SRV2 Cluster.RGM.rgmd: [ID 285716 daemon.notice] 20 fe_rpc_command: cmd_type(enum):<3>:cmd=<null>:tag=<proxy2-rg.proxy2-HAS-rs.10>: Calling security_clnt_connect(..., host=<C2SRV2>, sec_type {0:WEAK, 1:STRONG, 2SmilieES} =<0>, ...)
Jul 9 11:55:10 C2SRV2 Cluster.RGM.rgmd: [ID 316625 daemon.notice] Timeout monitoring on method tag <proxy2-rg.proxy2-HAS-rs.10> has been resumed.
Jul 9 11:55:12 C2SRV2 Cluster.RGM.rgmd: [ID 515159 daemon.notice] method <hastorageplus_prenet_start> completed successfully for resource <proxy2-HAS-rs>, resource group <proxy2-rg>, node <C2SRV2>, time used: 1% of timeout <1800 seconds>
Jul 9 11:55:12 C2SRV2 Cluster.RGM.rgmd: [ID 224900 daemon.notice] launching method <hastorageplus_monitor_start> for resource <proxy2-HAS-rs>, resource group <proxy2-rg>, node <C2SRV2>, timeout <90> seconds
Jul 9 11:55:12 C2SRV2 Cluster.RGM.rgmd: [ID 224900 daemon.notice] launching method <gds_svc_start> for resource <proxy2-zone-rs>, resource group <proxy2-rg>, node <C2SRV2>, timeout <300> seconds
Jul 9 11:55:12 C2SRV2 Cluster.RGM.rgmd: [ID 333393 daemon.notice] 49 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hastorageplus/hastorageplus_monitor_start>:tag=<proxy2-rg.proxy2-HAS-rs.7>: Calling security_clnt_connect(..., host=<C2SRV2>, sec_type {0:WEAK, 1:STRONG, 2SmilieES} =<1>, ...)
Jul 9 11:55:12 C2SRV2 Cluster.RGM.rgmd: [ID 252072 daemon.notice] 50 fe_rpc_command: cmd_type(enum):<1>:cmd=</opt/SUNWscgds/bin/gds_svc_start>:tag=<proxy2-rg.proxy2-zone-rs.0>: Calling security_clnt_connect(..., host=<C2SRV2>, sec_type {0:WEAK, 1:STRONG, 2SmilieES} =<1>, ...)
Jul 9 11:55:12 C2SRV2 Cluster.RGM.rgmd: [ID 515159 daemon.notice] method <hastorageplus_monitor_start> completed successfully for resource <proxy2-HAS-rs>, resource group <proxy2-rg>, node <C2SRV2>, time used: 0% of timeout <90 seconds>
Jul 9 11:55:13 C2SRV2 genunix: [ID 408114 kern.info] /pseudo/zconsnex@1/zcons@1 (zcons1) online


Jul 9 12:00:16 C2SRV2 Cluster.RGM.rgmd: [ID 764140 daemon.error] Method <gds_svc_start> on resource <proxy2-zone-rs>, resource group <proxy2-rg>, node <C2SRV2>: Timeout.
Jul 9 12:00:16 C2SRV2 Cluster.RGM.rgmd: [ID 224900 daemon.notice] launching method <hastorageplus_monitor_stop> for resource <proxy2-HAS-rs>, resource group <proxy2-rg>, node <C2SRV2>, timeout <90> seconds
Jul 9 12:00:16 C2SRV2 Cluster.RGM.rgmd: [ID 224900 daemon.notice] launching method <gds_svc_stop> for resource <proxy2-zone-rs>, resource group <proxy2-rg>, node <C2SRV2>, timeout <300> seconds
Jul 9 12:00:16 C2SRV2 Cluster.RGM.rgmd: [ID 333393 daemon.notice] 49 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hastorageplus/hastorageplus_monitor_stop>:tag=<proxy2-rg.proxy2-HAS-rs.8>: Calling security_clnt_connect(..., host=<C2SRV2>, sec_type {0:WEAK, 1:STRONG, 2SmilieES} =<1>, ...)
Jul 9 12:00:16 C2SRV2 Cluster.RGM.rgmd: [ID 252072 daemon.notice] 50 fe_rpc_command: cmd_type(enum):<1>:cmd=</opt/SUNWscgds/bin/gds_svc_stop>:tag=<proxy2-rg.proxy2-zone-rs.1>: Calling security_clnt_connect(..., host=<C2SRV2>, sec_type {0:WEAK, 1:STRONG, 2SmilieES} =<1>, ...)
Jul 9 12:00:16 C2SRV2 Cluster.RGM.rgmd: [ID 515159 daemon.notice] method <hastorageplus_monitor_stop> completed successfully for resource <proxy2-HAS-rs>, resource group <proxy2-rg>, node <C2SRV2>, time used: 0% of timeout <90 seconds>
# 6  
Old 07-09-2008
hi,

I have attached information from the /etc/cluster/ccr/infrastructure :

bash-3.00# cat infrastructure
ccr_gennum 37
ccr_checksum CA2D84527351512B9D561320FA5CB117
cluster.name scberl
cluster.state enabled
cluster.properties.cluster_id 0x48450FEC
cluster.properties.installmode disabled
cluster.properties.private_net_number 172.16.0.0
cluster.properties.private_netmask 255.255.248.0
cluster.properties.private_subnet_netmask 255.255.255.128
cluster.properties.private_user_net_number 172.16.4.0
cluster.properties.private_user_netmask 255.255.254.0
cluster.properties.private_maxnodes 64
cluster.properties.private_maxprivnets 10
cluster.properties.auth_joinlist_type sys
cluster.properties.auth_joinlist_hostslist C2SRV1,C2SRV2
cluster.properties.transport_heartbeat_timeout 10000
cluster.properties.transport_heartbeat_quantum 1000
cluster.properties.udp_session_timeout 480
cluster.properties.cmm_version 1
cluster.nodes.1.name C2SRV3
cluster.nodes.1.state enabled
cluster.nodes.1.properties.private_hostname clusternode1-priv
cluster.nodes.1.properties.quorum_vote 1
cluster.nodes.1.properties.quorum_resv_key 0x48450FEC00000001
cluster.nodes.1.adapters.1.name bge2
cluster.nodes.1.adapters.1.state enabled
cluster.nodes.1.adapters.1.properties.device_name bge
cluster.nodes.1.adapters.1.properties.device_instance 2
cluster.nodes.1.adapters.1.properties.transport_type dlpi
cluster.nodes.1.adapters.1.properties.lazy_free 1
cluster.nodes.1.adapters.1.properties.dlpi_heartbeat_timeout 10000
cluster.nodes.1.adapters.1.properties.dlpi_heartbeat_quantum 1000
cluster.nodes.1.adapters.1.properties.nw_bandwidth 80
cluster.nodes.1.adapters.1.properties.bandwidth 70
cluster.nodes.1.adapters.1.properties.ip_address 172.16.0.129
cluster.nodes.1.adapters.1.properties.netmask 255.255.255.128
cluster.nodes.1.adapters.1.ports.1.name 0
cluster.nodes.1.adapters.1.ports.1.state enabled
cluster.nodes.1.adapters.2.name bge21001
cluster.nodes.1.adapters.2.state enabled
cluster.nodes.1.adapters.2.properties.device_name bge
cluster.nodes.1.adapters.2.properties.device_instance 1
cluster.nodes.1.adapters.2.properties.transport_type dlpi
cluster.nodes.1.adapters.2.properties.lazy_free 1
cluster.nodes.1.adapters.2.properties.dlpi_heartbeat_timeout 10000
cluster.nodes.1.adapters.2.properties.dlpi_heartbeat_quantum 1000
cluster.nodes.1.adapters.2.properties.nw_bandwidth 80
cluster.nodes.1.adapters.2.properties.bandwidth 70
cluster.nodes.1.adapters.2.properties.vlan_id 21
cluster.nodes.1.adapters.2.properties.ip_address 172.16.1.1
cluster.nodes.1.adapters.2.properties.netmask 255.255.255.128
cluster.nodes.1.adapters.2.ports.1.name 0
cluster.nodes.1.adapters.2.ports.1.state enabled
cluster.nodes.1.cmm_version 1
cluster.nodes.2.name C2SRV4
cluster.nodes.2.state enabled
cluster.nodes.2.properties.quorum_vote 1
cluster.nodes.2.properties.quorum_resv_key 0x48450FEC00000002
cluster.nodes.2.properties.private_hostname clusternode2-priv
cluster.nodes.2.adapters.1.name bge2
cluster.nodes.2.adapters.1.properties.device_name bge
cluster.nodes.2.adapters.1.properties.device_instance 2
cluster.nodes.2.adapters.1.properties.transport_type dlpi
cluster.nodes.2.adapters.1.properties.lazy_free 1
cluster.nodes.2.adapters.1.properties.dlpi_heartbeat_timeout 10000
cluster.nodes.2.adapters.1.properties.dlpi_heartbeat_quantum 1000
cluster.nodes.2.adapters.1.properties.nw_bandwidth 80
cluster.nodes.2.adapters.1.properties.bandwidth 70
cluster.nodes.2.adapters.1.properties.ip_address 172.16.0.130
cluster.nodes.2.adapters.1.properties.netmask 255.255.255.128
cluster.nodes.2.adapters.1.state enabled
cluster.nodes.2.adapters.1.ports.1.name 0
cluster.nodes.2.adapters.1.ports.1.state enabled
cluster.nodes.2.adapters.2.name bge21001
cluster.nodes.2.adapters.2.properties.device_name bge
cluster.nodes.2.adapters.2.properties.device_instance 1
cluster.nodes.2.adapters.2.properties.vlan_id 21
cluster.nodes.2.adapters.2.properties.transport_type dlpi
cluster.nodes.2.adapters.2.properties.lazy_free 1
cluster.nodes.2.adapters.2.properties.dlpi_heartbeat_timeout 10000
cluster.nodes.2.adapters.2.properties.dlpi_heartbeat_quantum 1000
cluster.nodes.2.adapters.2.properties.nw_bandwidth 80
cluster.nodes.2.adapters.2.properties.bandwidth 70
cluster.nodes.2.adapters.2.properties.ip_address 172.16.1.2
cluster.nodes.2.adapters.2.properties.netmask 255.255.255.128
cluster.nodes.2.adapters.2.state enabled
cluster.nodes.2.adapters.2.ports.1.name 0
cluster.nodes.2.adapters.2.ports.1.state enabled
cluster.nodes.2.cmm_version 1
cluster.nodes.3.name C2SRV1
cluster.nodes.3.state enabled
cluster.nodes.3.properties.quorum_vote 1
cluster.nodes.3.properties.quorum_resv_key 0x48450FEC00000003
cluster.nodes.3.properties.private_hostname clusternode3-priv
cluster.nodes.3.adapters.1.name bge2
cluster.nodes.3.adapters.1.properties.device_name bge
cluster.nodes.3.adapters.1.properties.device_instance 2
cluster.nodes.3.adapters.1.properties.transport_type dlpi
cluster.nodes.3.adapters.1.properties.lazy_free 1
cluster.nodes.3.adapters.1.properties.dlpi_heartbeat_timeout 10000
cluster.nodes.3.adapters.1.properties.dlpi_heartbeat_quantum 1000
cluster.nodes.3.adapters.1.properties.nw_bandwidth 80
cluster.nodes.3.adapters.1.properties.bandwidth 70
cluster.nodes.3.adapters.1.properties.ip_address 172.16.0.131
cluster.nodes.3.adapters.1.properties.netmask 255.255.255.128
cluster.nodes.3.adapters.1.state enabled
cluster.nodes.3.adapters.1.ports.1.name 0
cluster.nodes.3.adapters.1.ports.1.state enabled
cluster.nodes.3.adapters.2.name bge21001
cluster.nodes.3.adapters.2.properties.device_name bge
cluster.nodes.3.adapters.2.properties.device_instance 1
cluster.nodes.3.adapters.2.properties.vlan_id 21
cluster.nodes.3.adapters.2.properties.transport_type dlpi
cluster.nodes.3.adapters.2.properties.lazy_free 1
cluster.nodes.3.adapters.2.properties.dlpi_heartbeat_timeout 10000
cluster.nodes.3.adapters.2.properties.dlpi_heartbeat_quantum 1000
cluster.nodes.3.adapters.2.properties.nw_bandwidth 80
cluster.nodes.3.adapters.2.properties.bandwidth 70
cluster.nodes.3.adapters.2.properties.ip_address 172.16.1.3
cluster.nodes.3.adapters.2.properties.netmask 255.255.255.128
cluster.nodes.3.adapters.2.state enabled
cluster.nodes.3.adapters.2.ports.1.name 0
cluster.nodes.3.adapters.2.ports.1.state enabled
cluster.nodes.4.name C2SRV2
cluster.nodes.4.state enabled
cluster.nodes.4.properties.quorum_vote 1
cluster.nodes.4.properties.quorum_resv_key 0x48450FEC00000004
cluster.nodes.4.properties.private_hostname clusternode4-priv
cluster.nodes.4.adapters.1.name bge2
cluster.nodes.4.adapters.1.properties.device_name bge
cluster.nodes.4.adapters.1.properties.device_instance 2
cluster.nodes.4.adapters.1.properties.transport_type dlpi
cluster.nodes.4.adapters.1.properties.lazy_free 1
cluster.nodes.4.adapters.1.properties.dlpi_heartbeat_timeout 10000
cluster.nodes.4.adapters.1.properties.dlpi_heartbeat_quantum 1000
cluster.nodes.4.adapters.1.properties.nw_bandwidth 80
cluster.nodes.4.adapters.1.properties.bandwidth 70
cluster.nodes.4.adapters.1.properties.ip_address 172.16.0.132
cluster.nodes.4.adapters.1.properties.netmask 255.255.255.128
cluster.nodes.4.adapters.1.state enabled
cluster.nodes.4.adapters.1.ports.1.name 0
cluster.nodes.4.adapters.1.ports.1.state enabled
cluster.nodes.4.adapters.2.name bge21001
cluster.nodes.4.adapters.2.properties.device_name bge
cluster.nodes.4.adapters.2.properties.device_instance 1
cluster.nodes.4.adapters.2.properties.vlan_id 21
cluster.nodes.4.adapters.2.properties.transport_type dlpi
cluster.nodes.4.adapters.2.properties.lazy_free 1
cluster.nodes.4.adapters.2.properties.dlpi_heartbeat_timeout 10000
cluster.nodes.4.adapters.2.properties.dlpi_heartbeat_quantum 1000
cluster.nodes.4.adapters.2.properties.nw_bandwidth 80
cluster.nodes.4.adapters.2.properties.bandwidth 70
cluster.nodes.4.adapters.2.properties.ip_address 172.16.1.4
cluster.nodes.4.adapters.2.properties.netmask 255.255.255.128
cluster.nodes.4.adapters.2.state enabled
cluster.nodes.4.adapters.2.ports.1.name 0
cluster.nodes.4.adapters.2.ports.1.state enabled
cluster.blackboxes.1.name switch1
cluster.blackboxes.1.state enabled
cluster.blackboxes.1.properties.type switch
cluster.blackboxes.1.ports.1.name 1
cluster.blackboxes.1.ports.1.state enabled
cluster.blackboxes.1.ports.2.name 2
cluster.blackboxes.1.ports.2.state enabled
cluster.blackboxes.1.ports.3.name 3
cluster.blackboxes.1.ports.3.state enabled
cluster.blackboxes.1.ports.4.name 4
cluster.blackboxes.1.ports.4.state enabled
cluster.blackboxes.2.name switch2
cluster.blackboxes.2.state enabled
cluster.blackboxes.2.properties.type switch
cluster.blackboxes.2.ports.1.name 1
cluster.blackboxes.2.ports.1.state enabled
cluster.blackboxes.2.ports.2.name 2
cluster.blackboxes.2.ports.2.state enabled
cluster.blackboxes.2.ports.3.name 3
cluster.blackboxes.2.ports.3.state enabled
cluster.blackboxes.2.ports.4.name 4
cluster.blackboxes.2.ports.4.state enabled
cluster.cables.1.properties.end1 cluster.nodes.1.adapters.1.ports.1
cluster.cables.1.properties.end2 cluster.blackboxes.1.ports.1
cluster.cables.1.state enabled
cluster.cables.2.properties.end1 cluster.nodes.1.adapters.2.ports.1
cluster.cables.2.properties.end2 cluster.blackboxes.2.ports.1
cluster.cables.2.state enabled
cluster.cables.3.properties.end1 cluster.nodes.2.adapters.1.ports.1
cluster.cables.3.properties.end2 cluster.blackboxes.1.ports.2
cluster.cables.3.state enabled
cluster.cables.4.properties.end1 cluster.nodes.2.adapters.2.ports.1
cluster.cables.4.properties.end2 cluster.blackboxes.2.ports.2
cluster.cables.4.state enabled
cluster.cables.5.properties.end1 cluster.nodes.3.adapters.1.ports.1
cluster.cables.5.properties.end2 cluster.blackboxes.1.ports.3
cluster.cables.5.state enabled
cluster.cables.6.properties.end1 cluster.nodes.3.adapters.2.ports.1
cluster.cables.6.properties.end2 cluster.blackboxes.2.ports.3
cluster.cables.6.state enabled
cluster.cables.7.properties.end1 cluster.nodes.4.adapters.1.ports.1
cluster.cables.7.properties.end2 cluster.blackboxes.1.ports.4
cluster.cables.7.state enabled
cluster.cables.8.properties.end1 cluster.nodes.4.adapters.2.ports.1
cluster.cables.8.properties.end2 cluster.blackboxes.2.ports.4
cluster.cables.8.state enabled
cluster.quorum_devices.2.name d15
cluster.quorum_devices.2.state enabled
cluster.quorum_devices.2.properties.votecount 1
cluster.quorum_devices.2.properties.gdevname /dev/did/rdsk/d15s2
cluster.quorum_devices.2.properties.path_1 enabled
cluster.quorum_devices.2.properties.path_2 enabled
cluster.quorum_devices.2.properties.access_mode scsi2
cluster.quorum_devices.2.properties.type scsi2
# 7  
Old 07-09-2008
Sun cluster 3.2

hi,

I have also attached acopy of the /etc/cluster/ccr/rgm_rg_proxy2-rg
file:

bash-3.00# cat rgm_rg_proxy2-rg
ccr_gennum 6
ccr_checksum 53FF13F4E152CAB05ED6D524C74B089C
Unmanaged FALSE
Nodelist 1,2,3,4
Maximum_primaries 1
Desired_primaries 1
Failback FALSE
RG_System FALSE
Resource_list proxy2-HAS-rs,proxy2-zone-rs
RG_dependencies
Global_resources_used *
RG_mode Failover
Implicit_network_dependencies TRUE
Pathprefix
RG_description
Pingpong_interval 3600
RG_project_name
RG_SLM_type manual
RG_SLM_pset_type default
RG_SLM_CPU_SHARES 1
RG_SLM_PSET_MIN 0
RG_affinities
Auto_start_on_new_cluster TRUE
Suspend_automatic_recovery FALSE
Ok_To_Start
RS_proxy2-HAS-rs Type=SUNW.HAStoragePlus:6;Type_version=6;R_description=;On_off_switch=1,2,3,4;Monitored_switch=1,2,3 ,4;Resource_project_name=;Resource_dependencies=;Resource_dependencies_weak=;Resource_dependencies_r estart=;Resource_dependencies_offline_restart=;Extension;FilesystemMountPoints=/opt/zones/mail/proxy2.mail.internal,/opt/zones/mail/proxy2.mail.internal/mounts/var
RS_proxy2-zone-rs Type=SUNW.gds:6;Type_version=6;R_description=;On_off_switch=1,2,3,4;Monitored_switch=1,2,3,4;Resourc e_project_name=;Resource_dependencies=proxy2-HAS-rs;Resource_dependencies_weak=;Resource_dependencies_restart=;Resource_dependencies_offline_restart= ;Extension;Start_command=/opt/SUNWsczone/sczbt/bin/start_sczbt -R proxy2-zone-rs -G proxy2-rg -P /opt/ParameterFile;Stop_command=/opt/SUNWsczone/sczbt/bin/stop_sczbt -R proxy2-zone-rs -G proxy2-rg -P /opt/ParameterFile;Probe_command=/opt/SUNWsczone/sczbt/bin/probe_sczbt -R proxy2-zone-rs -G proxy2-rg -P /opt/ParameterFile;Network_aware=FALSE;Stop_signal=9
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Process to add mount point in Sun Cluster existing HAplus resource

Hi Well I would like to know step by step process of adding a mountpoint in HAPLUS resource in SUN cluster as I go the below command to add a mount point but not the step by step process of adding a mount point in existing HA Plus resource. clrs set -p FileSystemMountPoints+=<new_MP>... (3 Replies)
Discussion started by: amity
3 Replies

2. Red Hat

Linux Cluster failover issue

Hi Guys, I am not much aware of clusters but i have few questions can someone provide the overview as it would be very helpful for me. How can i perform cluster failover test to see all the services are failing back to other node ? If it is using veritas cluster then what kind of... (2 Replies)
Discussion started by: munna529
2 Replies

3. Solaris

Solaris Cluster Failover based on scan rate

Dear Experts, If there is a possible Solaris Cluster failover to second node based on scan rate? I need the documentation If solaris cluster can do this. Thank You in Advance Edy (3 Replies)
Discussion started by: edydsuranta
3 Replies

4. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

5. AIX

Adding a Volume Group to an HACMP Resource Group?

Hi, I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over) Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes... (6 Replies)
Discussion started by: aixromeo
6 Replies

6. Gentoo

How to failover the cluster ?

How to failover the cluster ? GNU/Linux By which command, My Linux version 2008 x86_64 x86_64 x86_64 GNU/Linux What are the prerequisites we need to take while failover ? if any Regards (3 Replies)
Discussion started by: sidharthmellam
3 Replies

7. AIX

Resource Group Monitoring

Hi, I have a requirement to monitor the HACMP Resource Groups. At present in my environment, if the Resource Groups fail over from preferred node to Secondary node we dont get notification. Can some one help me in creating a scrript. I have more than one RG online. (Max 4 Resource Groups in... (2 Replies)
Discussion started by: srnagu
2 Replies

8. Solaris

Sun Cluster 3.1 failover

Hi, We have two sun SPARC server in Clustered (Sun Cluster 3.1). For some reason, System 1 failed over to System 2. Where can I find the logs which could tell me the reason for this failover? Thanks (5 Replies)
Discussion started by: Mack1982
5 Replies

9. High Performance Computing

Veritas Cluster Server Management Console IP Failover

I have just completed a first RTFM of "Veritas Cluster Server Management Console Implementation Guide" 5.1, with a view to assessing it to possibly make our working lives easier. Unfortunately, at my organisation, getting a test installation would be worse than pulling teeth, so I can't just go... (2 Replies)
Discussion started by: Beast Of Bodmin
2 Replies

10. HP-UX

ServiceGuard cluster & volume group failover

I have a 2-node ServiceGuard cluster. One of the cluster packages has a volume group assigned to it. When I fail the package over to the other node, the volume group does not come up automatically on the other node. I have to manually do a "vgchange -a y vgname" on the node before the package... (5 Replies)
Discussion started by: Wotan31
5 Replies
Login or Register to Ask a Question

Featured Tech Videos