In order for automatic relocation to occur when a node is no longer online, the isolation detection addresses must also be configured in the environment. The isolation detection addresses may be entered globally by going to the isolation tab under the domain name. To configure the isolation detection IP addresses at the node level you would expand nodes and select the "Failure Detection and Mirroring" tab for each node. The isolation IP addresses must be on the same subnet as the node and should be available at all times. For redundancy at least two Isolation IP addresses should be specified, but only one is required.
The second thing I would suggest is also making the 192 an AutoStart domain line. Typically the main domain line should be over the public interface and the secondary domain line may be over the crossover cable. By just having the domain line over a crossover cable, it may cause problems when the partner node goes down due to Windows media sensing on the surviving node. Windows media sensing can cause the base IP address of the surviving node to be lost and therefore causing AutoStart agent failures.
ecervant
63 Posts
0
December 27th, 2007 08:00
In order for automatic relocation to occur when a node is no longer online, the isolation detection addresses must also be configured in the environment. The isolation detection addresses may be entered globally by going to the isolation tab under the domain name. To configure the isolation detection IP addresses at the node level you would expand nodes and select the "Failure Detection and Mirroring" tab for each node. The isolation IP addresses must be on the same subnet as the node and should be available at all times. For redundancy at least two Isolation IP addresses should be specified, but only one is required.
The second thing I would suggest is also making the 192 an AutoStart domain line. Typically the main domain line should be over the public interface and the secondary domain line may be over the crossover cable. By just having the domain line over a crossover cable, it may cause problems when the partner node goes down due to Windows media sensing on the surviving node. Windows media sensing can cause the base IP address of the surviving node to be lost and therefore causing AutoStart agent failures.
Emilio Cervantes
EMC Technical Support