262 Posts

June 9th, 2008 18:00

Hi,David

It is necessary to use the Isolation function at 2NIC composition.
Because it falls into the split brain.

In the split brain, mirror status becomes BROKEN and must do a re-mirror


Yoshinobu

June 10th, 2008 08:00

so under the isolation script I should enter the corp IP address'? So that they can not ping/see each other? The cross over cable's are using no routeable address's such as 10.x.x.x or 172.x.x.x or 192.x.x.x. What ever range is not being used at there site?
Is the isolation script the only step that I am missing? Do I need to modify the script? I am going to do some testing here shortly and see what I destroy ?

Is there any other advantages having 3 nics in each server beside network redundancy? Will the 2 nic solution work as designed without breaking the mirror set?

Thanks for the reply..

262 Posts

June 10th, 2008 18:00

Hi,David

You must not appoint the IP of the cluster server.

Appoint an IP address of the third network machinery.

Set switch or router IP.


Please try by default the script.

1) Pull the LAN cable of the Corp network of the active side.

2) The OS of the active side does reboot.

3) The failover to the standby side.


Is there any other advantages having 3 nics in each server beside network redundancy?


Heart beat communicates only in the domain line.

In 3NIC composition, they are the following compositions.

NIC1 --- Public LAN1 = Domain Line1
NIC2 --- Public LAN2 = Domain Line2
NIC3 --- Mirror Line = Verification Line


It takes charge of the heart beat communication with Domain Line2 even if the cable of Domain Line1 comes off.

Therefore, the heart beat communication is redundancy.

As a result, the split brain can be evaded.


In 2NIC composition, they are the following compositions.

NIC1 --- Public LAN1 = Domain Line1
NIC2 --- Mirror Line = Verification Line

When the cable of Domain Line1 comes off, heart beat cannot be communicated.

Therefore, it becomes a split brain.

The Isolation function is used as an evasion plan.


Will the 2 nic solution work as designed without breaking the mirror set?


The mirror doesn't break if the Isolation function is used.


Yoshinobu Ito

June 11th, 2008 14:00

thanks for your help/comments and explainations... I am going to finish up a build in my test lab and destroy some stuff...

Is it just me or does EMC seem to have a hard time answering these questions.. I placed a call and seems like sales always wants to talk to me.. THEN they never call me back..


sorry for venting... BUT You've answered more of my questions than support line has..

Thanks...
David

262 Posts

June 12th, 2008 02:00

Hi,David

Please test once by 2NIC composition.

Moreover, please reply if there is a doubt.


Yoshinobu

June 17th, 2008 11:00

still manage to break the mirror set with only 2 nics.. just seems like there is a limitation with that....

I have Isolation script configured, and when I remove the Network cable from server1 that is running the resource group (application via service, and the data store). The server reboots (isolation) but the second server never picks up, the console, all icons' go to yellow status.. but never come on line?

David

262 Posts

June 17th, 2008 19:00

Hi,

The following message might appear when the failover is not correctly done.

MESSAGE: ID00001149 Agent on NodeA has failed. Ping Node results: Mirror Line IP=ALIVE


The following message appears when the failover is correctly done.

MESSAGE: ID00001150 Node NodeA has failed. Ping Node results: Mirror Line IP=DEAD, Public Network IP=DEAD


In the case of "Mirror Line IP=ALIVE", why was not the failover performed?

Answer

PING is executed with Mirror Line.
And, it finally judges by the response.

ALIVE --- nothing is done.
It is judged that the Agent service has been downed.

DEAD --- failover is executed.
It is judged that the server has been completely downed.

The startup of your test server might be early.
If the startup of the server is early, PING replies.

RESOLUTION
Please describe timeout=30 in Boot.ini, and delay the startup of the server.

EXAMPLE

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard" /noexecute=optout /fastdetect
timeout=30

Yoshinobu
No Events found!

Top