Support Center > Search Results > SecureKnowledge Details
The vip_index.conf file contains the wrong interface when new CMA is added
Symptoms
  • On MDS with 2 Leading interfaces, when adding a new CMA, the CMA will be assigned to the incorrect Leading interface

  • The $FWDIR/conf/vip_index.conf file contains the wrong interface.

    Example

    The machine interfaces are:

    eth0 10.30.50.7
    eth1 172.30.63.132 Mask:255.255.255.0
    eth2 172.30.112.4 Mask:255.255.255.0


    When adding a new CMA with IP address 172.30.112.100
    the calculated interface will be eth1, while eth2 should be chosen

Solution
Note: To view this solution you need to Sign In .