Re: [ClusterLabs] Antw: Corosync ring marked as FAULTY

In our case it does not create problems since all nodes are located in few networks whichserved by single router. There are also no any errors detected on public ring 1 unlike private ring 0. I have a suspicion that this error could be related to private VLAN settings but unfortunately have

[ClusterLabs] Antw: Oracle Stopping

>>> Chad Cravens schrieb am 22.02.2017 um 02:44 in Nachricht

[ClusterLabs] Antw: Corosync ring marked as FAULTY

Is "ttl 1" a good idea for a public network? >>> Denis Gribkov schrieb am 21.02.2017 um 18:26 in Nachricht <4f5543c4-b80c-659d-ed5e-7a99e1482...@itsts.net>: > Hi Everyone. > > I have 16-nodes asynchronous cluster configured with Corosync redundant > ring feature. > > Each node

[ClusterLabs] Oracle Stopping

Hello fellow Cluster Geeks! I'm having an issue with the standard Oracle RA script that I can't understand why this is happening. I create a Resource using the standard ocf:heartbeat:oracle script included with a Pacemaker install. I do this through the web interface, so setting the standard

[ClusterLabs] Corosync ring marked as FAULTY

Hi Everyone. I have 16-nodes asynchronous cluster configured with Corosync redundant ring feature. Each node has 2 similarly connected/configured NIC's. One NIC connected to the public network, another one to our private VLAN. When I checked Corosync rings operability I found: #

Re: [ClusterLabs] Antw: Re: Disabled resource is hard logging

Hi, After applying last changes... it looks not appear de huge amount of errors related to vdicone01 vm. I apologice for my maybe simple question, but can you explain which is the difference between the following commands: pcs resource op remove vm-vdicone01 monitor role=Stopped pcs resource op