Adding to Cluster Problem

I have two c350's on separate networks with two firewalls between them.
When trying to add the second 350 am getting a time out error. When checking the logs it tries to connect to the cluster as anonymous and is refused access.
any ideas?????

can you review the following KB article please and verify all the steps?
http://tinyurl.com/pjmpwh
once you're done, if there's still trouble, you can include outputs from your 'system_logs' during the failed join.

Similar Messages

An error occurred while adding the Cluster to the list

Hello,
I've installed the HFM 9.3.1 client on a Windows Server 2003 machine and now I'm attempting to configure it. I get all the way to the Server/Cluster Registration and when I try to add my one and only HFM application server to the list I'm present with this error.
"An error occurred while adding the Cluster to the list".
I don't see anything of use in the config tool log and as a result, I'm stuck. The odd thing is that not more than 10 minutes previously I added just finished installing the HFM client on another Windows Server 2003 machine and it installed / configured perfectly.
What am I missing?
Thanks!

You may have a DNS error of sorts. From a command line on the server which presents the error, ping the servername you are trying to reach. Do not use the cluster name, but instead use the server name or IP address. If you successfully reach it, use this in the registration utility. Once the server has been reached, it will return the cluster's name. If you cannot reach it using ping, focus on the underlying DNS problem.
--Chris

Ironport c160 cluster problems

Hi!
I have two Ironport C160 in cluster mode, tonight one of them has stopped working, and I can not access this on, but it responds to ping.
In the system log I found only the following line:
Mon Mar 12 15:30:39 2012 Warning: Error connecting to cluster machine xxxxx (Serial#: xxxxxx-xxxxxx) at IP xx.xxx.xxx.x - Operation timed out - Timeout connecting to remotehost cluster
Mon Mar 12 15:31:09 2012 Info: Attempting to connect via IPxxxxx toxxxxxxxx port 22 (Explicitly configured)
My version is:6.5.3-007
What I can log to find the cause of the problem?
How I can find out what the problem?
How can you solve?
Thank you very much

Well, "queuereset" is not a valid command, what you mean is "resetqueue", which I would strongly not recomment to use without having a very good reason.Because this command removes all messages from the workqueue, delivery queues, and quarantines. There are usually less destructive ways to fix a cluster problem.
BTW, version 5.5 has long been gone, so we won't need to reference any bugs from there any more.
Regards,
Andreas

SPF is not supported SCVMM cluster problems, when repairing ?

SPF is not supported SCVMM cluster problems, when repairing ?

See:
*http://forums.sdn.sap.com/thread.jspa?threadID=2056183&tstart=45#10718101

Adding another Cluster into existing CSS LB

Hi,
Im in the process of adding a new cluster into the existing LB. I understand the concept of configuring a new LB but adding a new network to it is a question.
I have preconfigured the LB with a new service called SPWeb 1-4 and an assign this to the content owner Central_Platform using VLAN 144 and 145.
I have one physical connection to the PIX and all port on the PIX is taken. Do I have to setup another physical connection for the new server SPWeb to the PIX?
Both owners Servcorp and Central_Platform are using separate public IP Subnets.
Also, please advise if I miss anything and if you have any suggestions.
Thansks
!************************* INTERFACE *************************
interface 1/1
bridge vlan 200
interface 2/1
phy 100Mbits-FD
description "To PIX"
bridge vlan 300
interface 2/2
phy 100Mbits-FD
description "To LB switches"
bridge vlan 301
interface 2/3
phy 100Mbits-FD
bridge vlan 303
description "Management"
interface 2/4
phy 100Mbits-FD
bridge vlan 144
description "SPWeb1/2"
interface 2/5
phy 100Mbits-FD
bridge vlan 145
description "SPWeb3/4"
!************************** CIRCUIT **************************
circuit VLAN1
ip address 192.168.10.1 255.255.255.0
circuit VLAN300
ip address (Network 1) 255.255.255.0
circuit VLAN301
ip address (Network 1) 255.255.255.0
circuit VLAN303
ip address (Network 1) 255.255.255.0
circuit VLAN144
ip address (Network 2) 255.255.255.0
circuit VLAN145
ip address (Network 2) 255.255.255.0
!************************** SERVICE **************************
service TS1
ip address 172.16.250.1
active
service TS2
ip address 172.16.250.2
active
service Spweb1
ip address 172.16.144.51
keepalive type HTTP
active
service Spweb2
ip address 172.16.144.52
keepalive type HTTP
active
service Spweb3
ip address 172.16.145.53
keepalive type HTTP
active
service Spweb4
ip address 172.16.145.54
keepalive type HTTP
active
!*************************** OWNER ***************************
owner Servcorp
content hottdesk.au
add service TS1
add service TS2
protocol tcp
port 3389
vip address (Network 1)
active
content hottdesk_FTP
add service TS1
add service TS2
port 20
protocol tcp
vip address (Network 1)
active
content hottdesk_FTP2
add service TS1
protocol tcp
port 21
application ftp-control
add service TS2
vip address (Network 1)
active
owner Central_Platform
content WebServers_1
add service Spweb1
add service Spweb2
protocol tcp
port 90
vip address (Network 2)
active
content WebServers_2
add service Spweb3
add service Spweb4
protocol tcp
port 81
vip address (Network 2)
active
content WebServers_3
add service Spweb3
add service Spweb4
protocol tcp
port 83
vip address (Network 2)
active
!*************************** GROUP ***************************
group TS-WebAccess
add service TS2
add service TS1
vip address (Network 1)
active

It would help if you could attach a picture of the network. I really can't understand why you have 2 VLANs on the same network ? Or am I missing the ide ?
Generally I would just do VLAN tag towards the PIX and have several networks that way. If speed isn't a issue I see no problems with that.

Two nodes Cluster problems

hello experts, I has the following problem:
I has a two nodes oracle RAC(version: 11.1.0.7 and OS: Enterprise Suse 10). Yesterday I had to delete one node of the cluster configuration and after I re-install it again I added it to the cluster configuration. Everything was ok but now there are two problems:
1- When I down the new instance using the srvctl utility the instance goes down normaly but when I try to start it one message appears notice me that the instance_number does not configured. I think it is very rare because when I start it using the sqlplus the instance goes up without problems.
Could you please give a suggestion about that problem?
2-Normally, before the delete and add the node, the cluster startup by itself when I restart the server but now it does not, so I have to execute crsctl start crs and this is not optimal.
Again, Do you have any suggestion?
Really there is not big problem because now I have a two nodes RAC again but I would like to solve this remain problems.
Thank in advance, I hope you can help me.

Hello thank you for your answer:
ASM show parameter instance_number 1
BD show parameter instance_number 1
I can found one difference(I think it is the only one) between the ora.bdm.bdm1.inst resource and the ora.bdm.bdm2.inst resource. That is, the ora.bdm.bdm2.inst has as required resource ora.bls2.ASM2.asm while ora.bdm.bdm1.inst does not has.
crs_stat -p
NAME=ora.bdm.bdm1.inst
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=300
DESCRIPTION=CRS application for Instance
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=900
STOP_TIMEOUT=300
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bdm.bdm2.inst
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=300
DESCRIPTION=CRS application for Instance
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=ora.bls2.ASM2.asm
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=900
STOP_TIMEOUT=300
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bdm.db
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=600
DESCRIPTION=CRS application for the Database
FAILOVER_DELAY=0
FAILURE_INTERVAL=60
FAILURE_THRESHOLD=1
HOSTING_MEMBERS=
OPTIONAL_RESOURCES=
PLACEMENT=balanced
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=0
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls1.ASM1.asm
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=300
DESCRIPTION=CRS application for ASM instance
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=900
STOP_TIMEOUT=180
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysasm
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=mount
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls1.LISTENER_BLS1.lsnr
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=600
DESCRIPTION=CRS application for listener on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=ora.bls1.vip
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls1.gsd
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=600
DESCRIPTION=CRS application for GSD on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls1.ons
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=60
DESCRIPTION=CRS application for ONS on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=3
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls1.vip
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=1
AUTO_START=1
CHECK_INTERVAL=15
DESCRIPTION=CRS application for VIP on a node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=favored
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=0
SCRIPT_TIMEOUT=60
START_TIMEOUT=0
STOP_TIMEOUT=0
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=bond0
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=255.255.255.128
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=90.40.100.115
NAME=ora.bls2.ASM2.asm
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=300
DESCRIPTION=CRS application for ASM instance
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=900
STOP_TIMEOUT=180
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysasm
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=mount
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls2.LISTENER_BLS2.lsnr
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=600
DESCRIPTION=CRS application for listener on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=ora.bls2.vip
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls2.gsd
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=600
DESCRIPTION=CRS application for GSD on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls2.ons
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=always
CHECK_INTERVAL=60
DESCRIPTION=CRS application for ONS on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=3
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls2.vip
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=1
AUTO_START=1
CHECK_INTERVAL=15
DESCRIPTION=CRS application for VIP on a node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=favored
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=0
SCRIPT_TIMEOUT=60
START_TIMEOUT=0
STOP_TIMEOUT=0
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=bond0
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=255.255.255.128
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=90.40.100.116
I hope you can help me.

Leopard - QMaster and Virtual Cluster problem

Hi guys,
Up until yesterday I had my MacPro Octo running under 10.4 where I did succesfully set up a Virtual Cluster using 4 instances for Compressor. It worked as a charm and my MacPro was doing it's job perfectly.
Today, I made a bootable backup of my 10.4 install and installed 10.5 using the erase and install options ( clean install ). I installed all my software again and tryed setting up my Virtual Cluster again, using the same settings I had under 10.4. Sadly I can't seem to get it working.
In the QMaster Preferences pane, I have the QuickCluster with Services option checked. For the compressor entry in the Services I have the Share Option checked and used 4 isntances for the selected service. The Quickcluster received a descent name and the option to include unmanaged services from other computers is checked.
I have the default options set in the Advanced tab, ( nothing checked except log service activity to log file and Show QMaster service status in the Menu Bar). I then started the Cluster using the Start Sharing button.
Now I open u Compressor and add a file to process ( QT encode to iPod ), but when I hit the Submit button, my Virtual Cluster doesn't show up in the Cluster Dropdown. If I now leave the Compressor GUI open for 5 minutes, it will eventually show up in the list, and I can pick it. Sadly, picking it from the list at this point and hitting the Submit button makes Compressor Hang.
I checked my logs, but the only thing concerning Compressor I could find is this :
4/12/07 20:12:35 Compressor[242] Could not find image named 'MPEG1-Output'.
4/12/07 20:12:35 Compressor[242] Could not find image named 'MPEG1-Output'.
4/12/07 20:12:35 Compressor[242] Could not find image named 'MPEG1-Output'.
4/12/07 20:12:41 Batch Monitor[190] * CDOClient::connect2: CException [NSException raised by 'NSPortTimeoutException', reason = '[NSPortCoder sendBeforeTime:sendReplyPort:] timed out (218488391.647220 218488361.647369) 1'], server [tcp://10.0.1.199:49167]
4/12/07 20:12:41 Batch Monitor[190] exception caught in -[ClusterStatus getNewStatusFromController:withOptions:withQueryList:]: NSException raised by 'NSPortTimeoutException', reason = '[NSPortCoder sendBeforeTime:sendReplyPort:] timed out (218488391.647220 218488361.647369) 1'
4/12/07 20:17:55 Batch Monitor[190] * CDOClient::connect2: CException [NSException raised by 'NSPortTimeoutException', reason = '[NSPortCoder sendBeforeTime:sendReplyPort:] timed out (218488705.075513 218488675.075652) 1'], server [tcp://10.0.1.199:49167]
I tried Stopping and then Restart Sharing and I noticed the follwoing entries in my log :
4/12/07 20:23:26 compressord[210] can't refresh cache from file "/Library/Application Support/Apple Qmaster/qmasterservices.plist"
4/12/07 20:23:26 compressord[211] can't refresh cache from file "/Library/Application Support/Apple Qmaster/qmasterservices.plist"
4/12/07 20:23:26 compressord[213] can't refresh cache from file "/Library/Application Support/Apple Qmaster/qmasterservices.plist"
4/12/07 20:23:26 qmasterca[269] can't refresh cache from file "/Library/Application Support/Apple Qmaster/qmasterservices.plist"
4/12/07 20:23:26 qmasterqd[199] can't refresh cache from file "/Library/Application Support/Apple Qmaster/qmasterservices.plist"
4/12/07 20:23:27 QmasterStatusMenu[178] * CDOClient::connect2: CException [NSException raised by 'NSPortTimeoutException', reason = '[NSPortCoder sendBeforeTime:sendReplyPort:] timed out (218489009.603992 218489007.604126) 1'], server [tcp://10.0.1.199:49407]
4/12/07 20:23:27 Batch Monitor[190] * CDOClient::connect2: CException [NSException raised by 'NSPortTimeoutException', reason = '[NSPortCoder sendBeforeTime:sendReplyPort:] timed out (218489037.738080 218489007.738169) 1'], server [tcp://10.0.1.199:49407]
4/12/07 20:23:27 Batch Monitor[190] exception caught in -[ClusterStatus getNewStatusFromController:withOptions:withQueryList:]: NSException raised by 'NSPortTimeoutException', reason = '[NSPortCoder sendBeforeTime:sendReplyPort:] timed out (218489037.738080 218489007.738169) 1'
Batch Monitor immediately detects the cluster being active again, but Compressor doesnt, leaving me only This Computer available in the Cluster drop down when submitting a batch.
In my Activity Monitor, I notice that CompressorTranscoder is not responing ( the 4 CompressorTranscoderX processes are fine ) and the ContentAgent proces isn't responding neither.
Does anyone have any clue on what I could check next or how I could fix my problems ?
Thanks a lot in advance,
Stefaan

Bah, this is crazy, today it doesn't work anymore. Yesterday my cluster was showing up in the Dropdown window, and I could submit a batch to it, and it got processed over my virtual cluster.
Today, after finishing the second part of my movie, I tried it again. I didn't change anything to my settings, my machine hasn't even rebooted (just recovered from sleep mode) and my cluster isn't showing up at all anymore. Even the Qmaster menu doesn't show it
Guess, I'll have to wait out until it appears again, or try a few things out

August Patch Cluster Problems

Has anyone had the following issue after installing the latest Patch Cluster?
After a reboot I get
couldn't set locale correctly
To correct this I have to edit /etc/default/init
and remove
LC_COLLATE=en_GB.ISO8859-1
LC_CTYPE=en_GB.ISO8859-1
LC_MESSAGES=C
LC_MONETARY=en_GB.ISO8859-1
LC_NUMERIC=en_GB.ISO8859-1
LC_TIME=en_GB.ISO8859-1
If I then create a flash archive and use this flash archive the jumpstart process then puts the locale info back and the problem appears again.
It's not critical as I don't need to be on the latest Patch Cluster but would wondered if I'm the only one having issues?

If you open the directory in CDE's file manager, right click on the zipped file and select unzip. The cluster will be unzipped to a directory structure called x86_recommended or something of the sort. Change to that directory to run the patch cluster install script. The patch script is looking for that directory structure.
Lee

NVGRE Gateway Cluster Problem

Hello
We have following setup:
Management Hyper-V hosts running WAP, SPF and SCVMM 2012 R2 components
Gateway Hyper-V host: single node gateway hyper-v host, configured as a single node cluster to be able to join extra hardware in the future
this Hyper-V host runs 2 Windows Server Gateway VMs,configured as a failover cluster.
The following script is used to deploy these windows server gateway VMs as a high available NVGRE gateway service:
http://www.hyper-v.nu/archives/mscholman/2015/01/hyper-v-nvgre-gateway-toolkit/
two tenant Hyper-V hosts running VMs which are using network virtualization
The setup is completed successfully and when creating a tenant in WAP and creating VM network for this tenant using NAT, the VMs of this tenant are accessible and can access Internet using the HA Gateway cluster.
The Gateway Hyper-V host and NVGRE Gateway VMs are running in a DMZ zone, in a DMZ Active Directory Domain.
Management and Tenant Hyper-V hosts, incl all Management VMs, are running in a dedicated internal Active Directory domain.
Problems start when we failover the Windows Server Gateway service to the other VM node of the NVGRE Gateway cluster. We see in the lookup records on the Gateway Hyper-V host that the MAC address of the gateway record for tenants is updated with the new
MAC address of the VM node running the gateway service.
But in SCVMM, apparently, this record is not updated. The tenant hosts still use the old MAC address of the other Gateway VM node.
When looking in the SCVMM database, we can also see that in the VMNetworkGateway table that the record representing the gateway of the tenant, still points to the MAC address of the PA network adapter of the other node of the NVGRE Gateway cluster, not to the
new node on which the gateway service is running after initiating a failover.
On the tenant hyper-v hosts, the lookup record for the gateway also points to the old node as well.
When manually changing the record in the VMNetworkGateway table to the new MAC address, and refreshing the tenant hosts in SCVMM, all starts working again and the tenant VMs can access the gateway again.
Anybody else facing this issue? Or is running a NVGRE Gateway cluster on a single Hyper-V node not supported?
To be complete, the deployed VMs running the gateway service are not configured as HA VMs.
Regards
Stijn

If i understand your post correctly you have a single Hyper-V Host running 2 GW VM's. I think the problem is that when you deploy a HA VM Gateway Cluster it wants to create a Cluster Resource (PA IP Address) on the Hyper-V host as well. So when you run 2
hyper-v hosts and 2 gw vm's and you move the active role to another host it will move the Provider Address to the other Hyper-V host as well. I believe this is by design. You should ask yourself also the question why running 2 vm's in a cluster on the same
node ;-)
I would recommend to use 2 node Hyper-V Host Cluster (This is needed for the HA PA Address, And not necessary for your GW VM's )
Then run the deployment toolkit again. Now when that's done again, take a close look on how the Active node on the Hyper-V host has the corresponding PA assiogned on that Hyper-V host. Then do a failover, refresh the cluster manager and take notice
of the PA address that has moved along to the other Hyper-V host that is the active one. It is diffuclt to explain, in a couple of sentences but i hope you have the opportunity to build the 2nd Hyper-V host aswell and create a cluste.
Side note: if you want to keep the excising VM Gateway cluster. remove all gateways from VM Networks and remove the Gateway service from VMM. Then provision the second Hyper-V Host, Configure Cluster, Live migrate 1 GW VM node to it. Reconfigure
Shared VHDX for quorum and csv and then add back the network service again. Don't try to leave it as a network service in VMM and move the VM to another node. It will not work when failover.
Best regards, Mark Scholman. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Adding ASAv cluster into APIC: Status remains as init

Hi,
I've been trying to integrate an ASAv cluster into the APIC, but couldn't seem to get it working. The status remains as "init". However, when I add a standalone ASAv into APIC, the integration seems to work fine. Could someone offer some insight into why this is happening?
I've attached an XML file describing the fault.
Basically, what I did was the following:
1) Set up my 2 ASAv VMs as active-standby with the following configuration:
- Mgmt IP of 10.88.88.201 for ASAv-Pri and 10.88.88.202 for ASAv-Sec
- Failover LAN IP of 192.168.0.1 for ASAv-Pri and 192.168.0.2 for ASAv-Sec
2) Under one of the tenants, I added the ASAv cluster under the L4-L7 Devices, with the necessary interfaces configured. I also configured the necessary interfaces under Parameters, although I'm not sure if I did it correct. I've attached the configuration in xml format for reference (you can remove the *.txt extension)
Was there something that I did wrongly, or missed out?
Thanks for reading!

It looks like your failover configuration is incomplete. You need to specify the failover_lan_interface under the LAN Failover Interface folder. The name used should match the interface_name (failover) you specified under the Failover Interface Configuration.
See the following screenshot for an example:
Regards,
Zach

Recently Added Playlist having problems?

Couple of weeks ago my music in the 'Recently Added' playlist listed each track in the order they were added to the library. Now all the tracks in the playlist are all over the place, despite the fact that it is a smart playlist. How can i solve this problem? Is there an alternative method instead of adding the date added column in the playlist? I would appreciate it if anyone could help me.
Thanks in advance.

Click at the top of the Date Added column, and the list will sort by Date Added.
The column where you see a triangle is the one it is currently sorted by.

Cluster Problems??

Hi All,
Need some help we have a SAP 4.6C install on a Microsoft cluster with a MSQL database one node in the
Cluster is corrupt and needs to be rebuilt my question to you all is can one node of the cluster be built
Or will both nodes have to be rebuilt.
If so where can I find the documentation to do this can it result in any other problems.
Thanks
John

Hello - The nature of MSCS is failover. Thus one node failure = one node recovery. MSCS documentation would suffice here.
Regards.

BorderManager Cluster problems

I have set up a 2 node NW 6.5 SP8 cluster to run BorderManager 3.9 SP2. I don't have a 'Split Brain Detector' (SBD) partition; the servers only monitor each other through the LAN heartbeat signal that is being sent by the master and replies by the slave. This has worked well from a high availability perspective but I keep running into a situation where both nodes will go 'active'.
Usually, I have Node 0 set as both the cluster master and the host of the NBM proxy resource. Node 1 is then in standby - ready to load the proxy service and assume the proxy IP address if node 0 dies. At some point (the time is variable in days 2 - 5 and doesn't seem to be related to network load) Node 0 will think that Node 1 has failed and will show that on the Cmon console. Shortly afterwards Node 1 will think that Node 0 has failed and bind the proxy IP and cluster master IP and load the proxy. At this time I have two servers; both with the same Cluster Master IP bound and the proxy IP bound and proxy.nlm loaded!
I can access Node 0 through rconj and it appears to be working fine. If I do a 'display secondary ipaddress' I can see it has both the proxy IP and Cluster Master IP bound to it. The same thing is the case for Node 1. I unload the proxy on Node 0 and reset the server. When it comes back up, it joins the cluster just fine and there doesn't appear to be any other problem.
Has anyone else seen this behavior? (Craig???)
thanks,
Dan

In article <[email protected]>, Dchuntdnc wrote:
> but I keep running into a situation where
> both nodes will go 'active'.
I've got one of those situations too, at a client.
>
> Usually, I have Node 0 set as both the cluster master and the host of
> the NBM proxy resource. Node 1 is then in standby - ready to load the
> proxy service and assume the proxy IP address if node 0 dies. At some
> point (the time is variable in days 2 - 5 and doesn't seem to be related
> to network load) Node 0 will think that Node 1 has failed and will show
> that on the Cmon console.
This sounds familiar, except for me it happens within hours.
> Shortly afterwards Node 1 will think that
> Node 0 has failed and bind the proxy IP and cluster master IP and load
> the proxy. At this time I have two servers; both with the same Cluster
> Master IP bound and the proxy IP bound and proxy.nlm loaded!
Yep. Gets annoying, to say the least!
>
> I can access Node 0 through rconj and it appears to be working fine.
> If I do a 'display secondary ipaddress' I can see it has both the proxy
> IP and Cluster Master IP bound to it. The same thing is the case for
> Node 1. I unload the proxy on Node 0 and reset the server. When it
> comes back up, it joins the cluster just fine and there doesn't appear
> to be any other problem.
Yep.
>
> Has anyone else seen this behavior? (Craig???)
I have definitely fought this issue, but only on one (of many) BM cluster.
Both nodes of the cluster are on old servers, and when the proxy is
active, it is exceptionally busy. (More than 2000 users, and plenty of LAN
bandwidth). I was on site at the client working on this (and a lot of
other projects) and I never was able to get to the bottom of it. The fact
that the server was so busy (24x7) made it hard to experiment on. My hope
at this point is to get decent newer hardware in there to replace the
7-year old nodes.
This happened when one server was BM 3.8 and the other BM 3.9, but it
continued to happen when I upgraded both to 3.9sp2. It also happened even
though I moved the heartbeat to dedicated nics with a crossover cable.
I'm thinking that something causes the LAN drivers to hiccup long enough
for the server to stop responding to heartbeat - but the proxy seems to
work continuously without showing a 30-second pause anywhere.
For the time being, I've left the oldest node not loading cluster
services. It's a manual failover at this time, but that's better than
nothing. (And the primary node is quite stable anyway, for months and
months at a time).
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Patchin portal cluster problem

I am trying to run, Portal patch 13 on a WAS cluster.
t
The problem I am getting is that the patch installation asks for a "username and password" for administrator
When I enter the details I get an error.
My question is that if it is in safe modde, how is the install checking these details. I cannot log into the visual admin when the cluster is in safe mode.
Anybode else have this problem.
Thanks

I think I just figured out how to use the sage mode. It basically just limits the cluster to 1 server and 1 dispatcher. Youre right, the same result can be achieved with the config tool
Thanks

Adding Secondary cluster

Dear All,
I am already having ISE in distributed deployment as
1)Primary Admin node
2)Primary Monitor node
3)PSN
Now i have 3 more ISE boxes & i need to build secondary cluster.
1) Secondary Admin node
2) Secondary Monitor node
3) PSN
To do this what all prerequisites .. any maintanance window required..?
Secondary cluster will be deployed at different location where firewall facing scenario. is there any ports need to be opened for synchronization..?
Thanks in advance

After you register the secondary node, the configuration of the secondary node is added to the database of the primary node and the application server on the secondary node is restarted. After the restart is complete, the secondary node will be running the personas and services that you have enabled on it.
http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/user_guide/ise_user_guide/ise_dis_deploy.html#pgfId-1053327
ISE 1.2 what ports need to be open between different personas?
http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/installation_guide/ise_ig/ise_app_c-ports.html
ISE 1.3 what ports need to be open between different personas?
http://www.cisco.com/c/en/us/td/docs/security/ise/1-3/installation_guide/b_ise_InstallationGuide13/b_ise_InstallationGuide12_appendix_01001.html
Hope this helps.
Regards,
Jatin

Adding to Cluster Problem

Similar Messages

Maybe you are looking for