> Source: [sk108763](https://support.checkpoint.com/results/sk/sk108763)

# sk108763 - The vip_index.conf file contains the wrong interface when new CMA is added

| Property | Value |
|----------|-------|
| Solution ID | sk108763 |
| Date Created | 2015-11-19 |
| Last Modified | 2019-05-28 |
| Technical Level | Advanced |
| Products | Multi-Domain Security Management Server |
| Versions | R82.10, R81.20, R82, R82.20 |

## 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  

  <br />

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

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content