Description of problem: When MRG Grid is run on a node with multiple network interfaces it will attempt to choose which interface it believes is the correct one for communications. If MRG Grid chooses the incorrect interface, the node could fail to communicate with other parts of MRG Grid correctly. It is possible to see which interface MRG Grid is choosing by adding D_HOSTNAME to the logging for the daemon(s) having problems. It is possible to force MRG Grid to use a specific network interface by setting the parameter NETWORK_INTERFACE to the IP address or network interface device that MRG Grid should use. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Reassigned to Tomas Capek who is looking after Release Notes for MRG 2.1
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When MRG Grid ran on a node with multiple network interfaces, it tried to estimate the correct interface for its communications with the remaining MRG Grid nodes. As a consequence, the node could have failed to communicate with other parts of MRG Grid correctly if the wrong interface had been chosen. As a workaround to this issue, MRG Grid can be forced to use a specific network interface by setting the NETWORK_INTERFACE parameter to the IP address of that interface. To determine which interface was used by MRG Grid when it fails to communicate with other parts of the grid, include the D_HOSTNAME variable in the logging configuration of the corresponding daemon.
Added to http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html-single/MRG_Release_Notes/index.html#Grid_2.1_Release