Please enter search query.
Search <product_name> all support & community content...
Article: 100043882
Last Published: 2019-03-12
Ratings: 0 0
Product(s): eDiscovery Platform
Problem
A myriad of unexplained errors can occur when using multiple Nics within the eDiscovery Platform (eDP) appliance. Issues can be seen in 'Native mode' Review or exports where the items cannot be found to any eDP Collection task to connects to a server source.
Error Message
Cause
When multiple Nics are present in a Windows server, Microsoft is designed to provide the path from source to destination using the lowest cost metric. eDP requests an IP address from the Windows operating software without providing the destination, so a path cost metric is not calculated by Windows. Windows will simply provide the first Nic card IP address with the lowest metric cost to the requesting Java programming code.
Collection Tasks are multi-threaded and several operations are occurring simultaneously. If multiple requests are made to the Windows operating system for an IP address (reminder, no path is provided), as long as the Nics have the same cost metric, Windows may provide the second, third or forth Nic IP address from the list of available IP addresses with the same cost. Thus, the secondary Nics must have extra costs applied to their metric.
Collection Tasks are multi-threaded and several operations are occurring simultaneously. If multiple requests are made to the Windows operating system for an IP address (reminder, no path is provided), as long as the Nics have the same cost metric, Windows may provide the second, third or forth Nic IP address from the list of available IP addresses with the same cost. Thus, the secondary Nics must have extra costs applied to their metric.
When the eDP server contains multiple Nics with the same metric cost, there is a possibility the wrong IP address will be returned, resulting in a myriad of possible errored scenarios.
Scenario:
The primary interface is Ethernet1 with the IP address 10.10.10.245
The secondary storage is on interface Ethernet2 with the IP address 192.168.10.110
See Figure 1 for the Route Print information. Notice the primary Ethernet1 interface Metric cost is higher at 266 (10.10.10.245) than the secondary Ethernet2 interface at a Metric cost of 261 (192.168.10.110).
This condition will cause the eDP program to select the lower cost Ethernet2 for external communications and cause unpredictable behavior.
NOTE: In the event the Metric costs are the same across the multiple network interface cards, the eDP program will be randomly assigned any Nic interface to communicate to external endpoints, thus resulting in unpredictable results.
The primary interface is Ethernet1 with the IP address 10.10.10.245
The secondary storage is on interface Ethernet2 with the IP address 192.168.10.110
See Figure 1 for the Route Print information. Notice the primary Ethernet1 interface Metric cost is higher at 266 (10.10.10.245) than the secondary Ethernet2 interface at a Metric cost of 261 (192.168.10.110).
This condition will cause the eDP program to select the lower cost Ethernet2 for external communications and cause unpredictable behavior.
NOTE: In the event the Metric costs are the same across the multiple network interface cards, the eDP program will be randomly assigned any Nic interface to communicate to external endpoints, thus resulting in unpredictable results.
Figure 1
Solution
Set the primary Nic as the preferred route for external communications for the eDP software by adding additional costs to the secondary Nics.
Open the Network Connections window
Figure 2
Open the properties of the Nic card that requires the higher Metric cost ( In this scenario Ethernet2 ).
Highlight 'Internet Protocol Version 4 (TCP/IPv4)' and select Properties.
Select the 'Advanced...' settings button.
Uncheck 'Automatic metric' and add a numeric value in the 'Interface metric:' box (in the example 20 is entered).
Select 'OK', 'OK', 'Yes', 'Close'
Figure 3
Execute Route Print from the command line and this time the primary Ethernet1 10.10.10.245 will have the lower Metric cost (266) while the secondary Ethernet2 will have the higher Metric cost (276). This condition will allow the eDP code to always be assigned the primary Ethernet1 Nic for external server communications.
Figure 4
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.