Unsolved
This post is more than 5 years old
2 Posts
0
1769
ID00004904 Failed to assign Managed IP error when reassigning node
We keep getting the follow error when we try to switch the Virtual IP address to a different node.
How do we correct this issue? What are we doing wrong? We are running Autostart 5.4.0
Log Name: AutoStart
Source: AutoStart
Date: 10/13/2011 9:15:18 PM
Event ID: 4904
Task Category: 2
Level: Error
Keywords: Classic
User: N/A
Computer: ACS9002
Description:
Error FT By: FT/Agent on Node: acs9001
ID00004904 Failed to assign Managed IP: 192.168.1.10 to 10.1.1.1 on acs9001: Interface specified not in the same subnet
When we start the process, this is what happens:
Info FT By: FT/Agent on Node: acs9002
ID00001234 Released Managed IP 192.168.1.10
Info RULE By: FT/Rule Interpreter on Node: acs9002
ID00004738 Resource Group S5_XXXXXX is in the Offline state.
Info FT By: FT/Agent on Node: acs9001
ID00001201 Assign request received for Managed IP 192.168.1.10. Target Node: acs9001
Error FT By: FT/Agent on Node: acs9001
ID00004904 Failed to assign Managed IP: 192.168.1.10 to 10.1.1.1 on acs9001: Interface specified not in the same subnet
Info FT By: FT/Agent on Node: acs9001
ID00001201 Assign request received for Managed IP 192.168.1.10. Target Node: acs9001
Error FT By: FT/Agent on Node: acs9001
ID00004904 Failed to assign Managed IP: 192.168.1.10 to 10.1.1.1 on acs9001: Interface specified not in the same subnet
Info FT By: FT/Agent on Node: acs9001
ID00001201 Assign request received for Managed IP 192.168.1.10. Target Node: acs9002
ERROR: ID00005282: IP bind failed with error 10049
ERROR: ID00005282: IP bind failed with error 10049
ERROR: ID00005282: IP bind failed with error 10049
ERROR: ID00005282: IP bind failed with error 10049
Info FT By: FT/Agent on Node: acs9002
ID00005238 GARP was sent for the IP address 192.168.1.10 successfully
Info FT By: FT/Agent on Node: acs9002
ID00001219 Assigned Managed IP 192.168.1.10 to NIC 192.168.1.12 on node acs9002
yito1
262 Posts
0
October 15th, 2011 05:00
Hi
You check the configuration of the virtual IP.
Please look at the Settings tab of the IP.
Did you set Subnet Mask Option?
Please clear the Subnet Mask.
Or, please enter the correct value.
ecervant
63 Posts
0
October 17th, 2011 11:00
The Managed IP settings tab contains a section to configure "Target Interfaces". The Target Interfaces are the Network interfaces that the Managed IP address will be bound too when it is assigned to a node. If the target interfaces are not specified, then an interface will be automatically chosen that matches the subnet mask of the Managed IP address. If an incorrect Network interface is selected (does not match Managed IP Subnet Mask) in the Target Interfaces configuration then the Managed IP address will fail to bind to the Network interface.
From the error message the Managed IP 192.168.1.10 is being assgined to Network interface 10.1.1.1, which is on a different subnet.
epsilon61
2 Posts
0
October 17th, 2011 12:00
Right now the system is stuck on acs9002. Should I change the interface to acs9001:Access control Base IP: 192.168.1.11, insead of acs9001:HEARTBASE Base IP: 10.1.1.1?
ecervant
63 Posts
0
October 17th, 2011 13:00
According to the screenshots the Target interafces should be "acs9001:Access Control" and "acs9002:ACCESS CONTROL". That is assuming the IP addresses (192.168.1.111 and 192.168.1.12) are on the same subnet as managed IP 192.168.1.10.