Unsolved
This post is more than 5 years old
38 Posts
0
353
June 14th, 2007 14:00
NIC is not appear
Hi,
Environment
- 2 server AIX 5.3
- AutoStart 5.2
- Every server has 2 NIC
Actually AutoStart is doing the failover when the application and server crash, then autostart work fine, but only with one NIC.
The problem was that the NIC´s displayed the status "no response", these NIC´s were working as "heartbeat".
I did many things to try to resolve the problem, these actions were:
- To change the network cable (crossover for one to one and one to one for crossover)
- To execute the ping command
- To reboot the machines at the same time
- To reset the NIC
- To increase the values in the fields at "failure detection" tab
- To create the file if.include with name of NIC. Restart the servers too
- To change the in the "failure detection" tab the heartbeat´s NIC´s like a "Verification". The NIC´s had "domain" value.
But with this last action the NIC dissapper if the GUI, only the NIC Group appear. In the node resource aren´t the heartbeat IP address. I have done the reboot the machines but the addresses aren´t appear
First, what is command to create this IP address in the node resource? or what is the procedure?
Second, what do you think the problem is in the case the NIC test is failed (no response)?
Thank you, regards
Edgar
Environment
- 2 server AIX 5.3
- AutoStart 5.2
- Every server has 2 NIC
Actually AutoStart is doing the failover when the application and server crash, then autostart work fine, but only with one NIC.
The problem was that the NIC´s displayed the status "no response", these NIC´s were working as "heartbeat".
I did many things to try to resolve the problem, these actions were:
- To change the network cable (crossover for one to one and one to one for crossover)
- To execute the ping command
- To reboot the machines at the same time
- To reset the NIC
- To increase the values in the fields at "failure detection" tab
- To create the file if.include with name of NIC. Restart the servers too
- To change the in the "failure detection" tab the heartbeat´s NIC´s like a "Verification". The NIC´s had "domain" value.
But with this last action the NIC dissapper if the GUI, only the NIC Group appear. In the node resource aren´t the heartbeat IP address. I have done the reboot the machines but the addresses aren´t appear
First, what is command to create this IP address in the node resource? or what is the procedure?
Second, what do you think the problem is in the case the NIC test is failed (no response)?
Thank you, regards
Edgar
0 events found
No Events found!
IKP1
198 Posts
0
June 18th, 2007 02:00
How is the hardware configured?
Are the two nics on each server using separate switches or the same switch?
Can you from node 1 ping each of the addresses for node 2 and likewise ping both nics on node1 from node2?
If you traceroute each interface card from both nodes, what are the routes between the two nic pairs?
Also, check the FTHOSTS file, make sure that EAS is populating this file correctly - this is an automated procedure at agent start UNLESS you have set the relevant flags not to do so. Does this file contain ALL 4 interface addresses?
You stated that the second line was for "heartbeat" - do you mean a domain line or a verification line as the usage of these two settings is different. Normal cluster traffic including the heartbeats uses domain lines and you are recommended to have a minimum of two domain lines per node in the cluster. Whereas verification lines are ONLY used when the cluster is unable to communicate across the domain lines and then the interface is ONLY used to verify the other node(s) are alive, NOT to pass domain data / heartbeats between nodes.
If you only have two nics per node, then you should configure them all as domain lines and ensure that the network routing is correct to ensure that nodes are able to communicate with each other using both nics. If you want a private network between the two second nics on the nodes then look at using a private subnet on the two interfaces and either a switch or a hub and NOT cross over cables.
Hope this helps
IKP
Message was edited by:
IKP