|IP Recovery Kit impact on routing table|| LifeKeeper-protected IP addresses are implemented on Linux as logical interfaces. When a logical interface is configured on Linux, a route to the subnet associated with the logical interface is automatically added to the routing table, even if a route to that subnet already exists (for example, through the physical interface). This additional route to the subnet could possibly result in multiple routing-table entries to the same subnet.
If an application is inspecting and attempting to verify the address from which incoming connections are made, the multiple routing-table entries could cause problems for such applications on other systems (non-LifeKeeper installed) to which the LifeKeeper system may be connecting. The multiple routing table entries can make it appear that the connection was made from the IP address associated with the logical interface rather than the physical interface.
|IP subnet mask||For IP configurations under LifeKeeper protection, if the LifeKeeper-protected IP address is intended to be on the same subnet as the IP address of the physical interface on which it is aliased, the subnet mask of the two addresses must be the same. Incorrect settings of the subnet mask may result in connection delays and failures between the LifeKeeper GUI client and server.|
|EEpro100 driver initialization|| The Intel e100 driver should be installed to resolve initialization problems with the eepro100 driver on systems with Intel Ethernet Interfaces. With the eepro100 driver, the following errors may occur when the interface is started at boot time and repeat continuously until the interface is shut down.
eth0: card reports no Rx buffers
eth0: card reports no resources
Thanks for your feedback.
Post your comment on this topic.