ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

2 dl380 server with MSA2000 (WINDOWS 2008) ERRORS

 
omar abdullah
Frequent Advisor

2 dl380 server with MSA2000 (WINDOWS 2008) ERRORS


Hi MyDear

The following errors for Felix company Cluster

Failover Cluster Validation Report in Felix AirLines
Hp proliant servers DL380 G5 P/D: 433524-421
S/N: CZC8370MQC
CZC8370MQK
MICROSOFT WINDOWS ENTERPRISE SERVER 2008



Node: node1.felixairways.net
Node: node2.felixairways.net
Started 12/30/2008 1:24:25 PM
Completed 12/30/2008 1:24:25 PM


Network
Name Result Description
Validate Cluster Network Configuration Success
Validate IP Configuration Failed
Validate Network Communication Success
Validate Windows Firewall Configuration Success




Overall Result
Testing has completed for the tests you selected. One or more tests indicate that the configuration is not suitable for clustering. For details, click "View Report." A cluster solution is supported by Microsoft only if it passes all tests in the wizard.


--------------------------------------------------------------------------------


Validate Cluster Network Configuration
Validate the cluster networks that would be created for these servers.
Validating the cluster networks that would be created for these servers.


Network: Cluster Network 1
DHCP Enabled: False
Network Role: Internal
Prefix Prefix Length
10.0.0.0 8

Item Value
Network Interface node1.felixairways.net - HB
DHCP Enabled False
IP Address 10.16.2.6
Prefix Length 8

Item Value
Network Interface node2.felixairways.net - HB
DHCP Enabled False
IP Address 10.16.2.7
Prefix Length 8



Network: Cluster Network 2
DHCP Enabled: False
Network Role: Enabled
Prefix Prefix Length
172.16.0.0 16

Item Value
Network Interface node1.felixairways.net - lan
DHCP Enabled False
IP Address 172.16.2.6
Prefix Length 16

Item Value
Network Interface node2.felixairways.net - LAN
DHCP Enabled False
IP Address 172.16.2.7
Prefix Length 16
IP Address 172.60.1.222
Prefix Length 16


Verifying that each cluster network interface within a cluster network is configured with the same IP subnets.
Examining network Cluster Network 1.
Network interface node1.felixairways.net - HB has addresses on all the subnet prefixes of network Cluster Network 1.
Network interface node2.felixairways.net - HB has addresses on all the subnet prefixes of network Cluster Network 1.
Examining network Cluster Network 2.
Network interface node2.felixairways.net - LAN has addresses on all the subnet prefixes of network Cluster Network 2.
Network interface node1.felixairways.net - lan has addresses on all the subnet prefixes of network Cluster Network 2.
Verifying that, for each cluster network, all adapters are consistently configured with either DHCP or static IP addresses.
Checking DHCP consistency for network: Cluster Network 1. Network DHCP status is disabled.
DHCP status (disabled) for network interface node1.felixairways.net - HB matches network Cluster Network 1.
DHCP status (disabled) for network interface node2.felixairways.net - HB matches network Cluster Network 1.
Checking DHCP consistency for network: Cluster Network 2. Network DHCP status is disabled.
DHCP status (disabled) for network interface node2.felixairways.net - LAN matches network Cluster Network 2.
DHCP status (disabled) for network interface node1.felixairways.net - lan matches network Cluster Network 2.

Back to Summary
Back to Top

--------------------------------------------------------------------------------


Validate IP Configuration
Validate that IP addresses are unique and subnets configured correctly.
Validating that IP addresses are unique and subnets configured correctly.


node1.felixairways.net
Item Name
Adapter Name Local Area Connection* 12
Adapter Description Microsoft Failover Cluster Virtual Adapter
Physical Address 02-21-5A-D0-A4-98
Status Operational
IP Address fe80::39ce:8799:b000:2279%13
Prefix Length 64
IP Address 169.254.1.205
Prefix Length 16

Item Name
Adapter Name HB
Adapter Description HP NC373i Multifunction Gigabit Server Adapter #2
Physical Address 00-21-5A-D0-A4-9A
Status Operational
IP Address 10.16.2.6
Prefix Length 8

Item Name
Adapter Name lan
Adapter Description HP NC373i Multifunction Gigabit Server Adapter
Physical Address 00-21-5A-D0-A4-98
Status Operational
IP Address 172.16.2.6
Prefix Length 16
IP Address 172.16.2.5
Prefix Length 16
IP Address 172.16.2.8
Prefix Length 16

Item Name
Adapter Name Loopback Pseudo-Interface 1
Adapter Description Software Loopback Interface 1
Physical Address 00-00-00-00-00-00-00-00
Status Operational
IP Address ::1
Prefix Length 128
IP Address 127.0.0.1
Prefix Length 8

Item Name
Adapter Name Local Area Connection* 8
Adapter Description isatap.{37F04D7B-FDA3-4283-93B7-3258E41A5E76}
Physical Address 00-00-00-00-00-00-00-E0
Status Not Operational
IP Address fe80::5efe:10.16.2.6%16
Prefix Length 128

Item Name
Adapter Name Local Area Connection* 9
Adapter Description isatap.{4EB4250A-E73C-4455-B3AD-DD1B8F45EBA2}
Physical Address 00-00-00-00-00-00-00-E0
Status Not Operational
IP Address fe80::5efe:172.16.2.6%15
Prefix Length 128

Item Name
Adapter Name Local Area Connection* 11
Adapter Description Teredo Tunneling Pseudo-Interface
Physical Address 02-00-54-55-4E-01-00-00
Status Not Operational
IP Address fe80::100:7f:fffe%12
Prefix Length 64

Item Name
Adapter Name Local Area Connection* 13
Adapter Description isatap.{D14B64E1-B76B-4E74-8967-A46D5D19FA11}
Physical Address 00-00-00-00-00-00-00-E0
Status Not Operational
IP Address fe80::5efe:169.254.1.205%14
Prefix Length 128




node2.felixairways.net
Item Name
Adapter Name Local Area Connection* 11
Adapter Description Microsoft Failover Cluster Virtual Adapter
Physical Address 02-21-5A-D0-B0-E0
Status Operational
IP Address fe80::59d5:f050:2e8c:fe15%13
Prefix Length 64
IP Address 169.254.2.108
Prefix Length 16

Item Name
Adapter Name HB
Adapter Description HP NC373i Multifunction Gigabit Server Adapter #2
Physical Address 00-21-5A-D0-B0-E2
Status Operational
IP Address 10.16.2.7
Prefix Length 8

Item Name
Adapter Name LAN
Adapter Description HP NC373i Multifunction Gigabit Server Adapter
Physical Address 00-21-5A-D0-B0-E0
Status Operational
IP Address 172.16.2.7
Prefix Length 16
IP Address 172.60.1.222
Prefix Length 16

Item Name
Adapter Name Loopback Pseudo-Interface 1
Adapter Description Software Loopback Interface 1
Physical Address 00-00-00-00-00-00-00-00
Status Operational
IP Address ::1
Prefix Length 128
IP Address 127.0.0.1
Prefix Length 8

Item Name
Adapter Name Local Area Connection* 8
Adapter Description isatap.{523C1653-210E-494B-B476-B54B4DB8C619}
Physical Address 00-00-00-00-00-00-00-E0
Status Not Operational
IP Address fe80::5efe:172.16.2.7%15
Prefix Length 128
IP Address fe80::200:5efe:172.60.1.222%15
Prefix Length 128

Item Name
Adapter Name Local Area Connection* 9
Adapter Description isatap.{FDA351F4-54F2-4B03-81F5-6197C7681AB3}
Physical Address 00-00-00-00-00-00-00-E0
Status Not Operational
IP Address fe80::5efe:10.16.2.7%16
Prefix Length 128

Item Name
Adapter Name Local Area Connection* 13
Adapter Description isatap.{C11F4C42-EC97-46E8-A73E-5D26ECB9512F}
Physical Address 00-00-00-00-00-00-00-E0
Status Not Operational
IP Address fe80::5efe:169.254.2.108%14
Prefix Length 128

Item Name
Adapter Name Local Area Connection* 12
Adapter Description Teredo Tunneling Pseudo-Interface
Physical Address 02-00-54-55-4E-01-00-00
Status Not Operational
IP Address fe80::100:7f:fffe%12
Prefix Length 64

Item Name
Adapter Name Local Area Connection* 14
Adapter Description 6TO4 Adapter
Physical Address 00-00-00-00-00-00-00-E0
Status Operational
IP Address 2002:ac3c:1de::ac3c:1de
Prefix Length 128



Verifying that a node does not have multiple adapters connected to the same subnet.
Verifying that each node has at least one adapter with a defined default gateway.
Verifying that there are no node adapters with the same EUI-48 physical address.
Verifying that there are no duplicate IP addresses between any pair of nodes.
Found duplicate IP address fe80::100:7f:fffe%12 on node node1.felixairways.net adapter Local Area Connection* 11 and node node2.felixairways.net adapter Local Area Connection* 12.
Checking that nodes are consistently configured with IPv4 and/or IPv6 addresses.

Back to Summary
Back to Top

--------------------------------------------------------------------------------


Validate Network Communication
Validate that servers can communicate, with acceptable latency, on all networks.
Validating that servers can communicate, with acceptable latency, on all networks.
Pinging network interface node2.felixairways.net - HB IP Address 10.16.2.7 from network interface node1.felixairways.net - HB IP Address 10.16.2.6 with maximum delay 500.
Succeeded in pinging network interface node2.felixairways.net IP Address 10.16.2.7 from network interface node1.felixairways.net IP Address 10.16.2.6 with maximum delay 500.
Pinging network interface node1.felixairways.net - HB IP Address 10.16.2.6 from network interface node2.felixairways.net - HB IP Address 10.16.2.7 with maximum delay 500.
Succeeded in pinging network interface node1.felixairways.net IP Address 10.16.2.6 from network interface node2.felixairways.net IP Address 10.16.2.7 with maximum delay 500.
Pinging network interface node1.felixairways.net - lan IP Address 172.16.2.6 from network interface node2.felixairways.net - LAN IP Address 172.16.2.7 with maximum delay 500.
Succeeded in pinging network interface node1.felixairways.net IP Address 172.16.2.6 from network interface node2.felixairways.net IP Address 172.16.2.7 with maximum delay 500.
Pinging network interface node2.felixairways.net - LAN IP Address 172.16.2.7 from network interface node1.felixairways.net - lan IP Address 172.16.2.6 with maximum delay 500.
Succeeded in pinging network interface node2.felixairways.net IP Address 172.16.2.7 from network interface node1.felixairways.net IP Address 172.16.2.6 with maximum delay 500.
Skipping ping from network interface node1.felixairways.net - HB IP Address 10.16.2.6 to network interface node2.felixairways.net - LAN IP Address 172.16.2.7 because the ICMP packet will be routed over a network path that is already being attempted. This generally occurs when the source node has a different network interface on the same cluster network as destination interface node2.felixairways.net - LAN.
Skipping ping from network interface node2.felixairways.net - HB IP Address 10.16.2.7 to network interface node1.felixairways.net - lan IP Address 172.16.2.6 because the ICMP packet will be routed over a network path that is already being attempted. This generally occurs when the source node has a different network interface on the same cluster network as destination interface node1.felixairways.net - lan.
Skipping ping from network interface node2.felixairways.net - LAN IP Address 172.16.2.7 to network interface node1.felixairways.net - HB IP Address 10.16.2.6 because the ICMP packet will be routed over a network path that is already being attempted. This generally occurs when the source node has a different network interface on the same cluster network as destination interface node1.felixairways.net - HB.
Skipping ping from network interface node1.felixairways.net - lan IP Address 172.16.2.6 to network interface node2.felixairways.net - HB IP Address 10.16.2.7 because the ICMP packet will be routed over a network path that is already being attempted. This generally occurs when the source node has a different network interface on the same cluster network as destination interface node2.felixairways.net - HB.
Analyzing connectivity results ...

Back to Summary
Back to Top

--------------------------------------------------------------------------------


Validate Windows Firewall Configuration
Validate that the Windows Firewall is properly configured to allow failover cluster network communication.
Validating that Windows Firewall is properly configured to allow failover cluster network communication.
The Windows Firewall on node node1.felixairways.net is configured to allow network communication between cluster nodes.
The Windows Firewall on node node1.felixairways.net is configured to allow network communication from cluster management clients.
The Windows Firewall on node node2.felixairways.net is configured to allow network communication between cluster nodes.
The Windows Firewall on node node2.felixairways.net is configured to allow network communication from cluster management clients.

Back to Summary
Back to Top

please any one help me to solve this problem

Best Regards
ENG: A. Omar