In addition to the information requested by Mark, please also check the network connection speed, make sure it is 1 GB and not 100 MB . If it is 100 MB change it to 1 GB and try the installation again.
If it is 100 MB change it to 1 GB and try the installation again.
It is a violation of the 802.3 Ethernet specification to force a NIC to 1Gb. More importantly, if autonegotiation failed to bring the NIC up to 1Gb, there is likely some underlying reason and forcing the NIC to 1Gb would almost certainly lead to intermittent and frustrating problems later.
There may have been a transitory issue where the NIC and switch failed to negotiate to the full 1Gb speed. Restarting network services normally resolves this type of issue. Because AVEs are single node servers, this can be done safely at any time but be aware that on multi-node servers, restarting network services with the GSAN running is likely to cause issues.
If after restarting the network services the NIC is still not at 1Gb, the cable, the switch port or the NIC may be damaged or defective. Support will normally try a different port and cable first. If that doesn't resolve the issue, the NIC is probably the cause.
Yes. I did. The md5 check went fine. I have already installed on one VM, and now trying to configure a second one. Idea is to try out replication for a specific domain or client.
Mark_Bellows
240 Posts
1350
0
Posted April 10th, 2012 06:00
Pavel,
What environment did you install AVE in? VMware, Hyper-V?
Also, any screen shots show progression will help.
Mark Bellows