Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

New Failover-Cluster over Windows 2012 Server - Error adding node:

$
0
0


hi, i have a bladecenter System H with one HS22V and one HS23E, with 4 nics, each server  have d 2 teams of 2 nics .

I can ping every nic  by name or IP from both servers and i can also ping the cluster name.

When i try to add the node to the cluster it gives me the following message:

The server 'NODE2.master.pt' could not be added to the cluster.
An error occurred while adding node 'NODE2.master.pt' to cluster 'ClusterFailover'.

This operation returned because the timeout period expired

error in event log of the NODE2:

Critical EventID: 1572

Node 'NODE2' failed to join the cluster because it could not send and receive failure detection network messages with other cluster nodes. Please run the Validate a Configuration wizard to ensure network settings. Also verify the Windows Firewall 'Failover Clusters' rules.

This error in the event log comes after some ntfs errors:

Warning EventID 140:

The system failed to flush data to the transaction log. Corruption may occur in VolumeId: ??, DeviceName: .
({Device Busy}
The device is currently busy.)

and

Error EventID 55:

A corruption was discovered in the file system structure on volume \\?\Volume{6dfcb8ed-78a6-447d-a82d-f065fea6fae7}.

The exact nature of the corruption is unknown.  The file system structures need to be scanned and fixed offline.

On validation i receive no warnings on the storage side, everything passes.

Only receive warnings on the Network side ( because of the vnic's with same MAC ) and in the processor, diferent Xeons.

Also receive a warning on the Quorum side:

    The recommended quorum configuration for the current number of nodes is Node Majority.

    The quorum partition is formated in ReFS and the others are in NTFS.

    Also receive this warning:

      The service startup type for the Cluster service on node Minerva.manchete.pt is not set to the default and recommended value of AUTO_START (0x2). If this server is not currently a member of a cluster, then this warning can be ignored. This setting may have been changed by another application or by an administrator during the troubleshooting of a problem. The setting affects whether the driver is automatically started and the point at which the service starts in the system boot process. To change the setting back to the recommended value, in Server Manager, in the Tools menu, click Services. In the list of services, double-click Cluster Service. On the General tab, change the selection for "Startup type" to Automatic.

      But since it its a new node i think this can be dischard.

      Thanks for the attention,

      AM



Viewing all articles
Browse latest Browse all 5654

Trending Articles