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

# sk105441 - "vsx_util reconfigure" command fails to resume with "Error: Interface 'Interface_Name' exists in the management database, but not on the gateway"

| Property | Value |
|----------|-------|
| Solution ID | sk105441 |
| Date Created | 2015-03-27 |
| Last Modified | 2021-06-01 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Symptoms

- "*vsx_util reconfigure*" command fails to resume:

```

Previous reconfigure operation was not completed.
Resume the operation? (y|n) [y] y
... ... ... ...
Connectivity test for <VSX_Object_Name> succeeded.
Displaying last 5 notes from Management Server:
Fetching configuration information from <VSX_Object_Name> ... 
Configuration information from <VSX_Object_Name> fetched successfully.
Verifying configuration information for <VSX_Object_Name> ... 
**** Error: Interface '<Interface_Name>' exists in the management database, but not on the gateway.
**** If this interface is not in use, please remove it from the VSX '<VSX_Object_Name>' Physical Interfaces tab.
Aborting reconfiguration ...
```

## Solution

This problem was fixed. The fix is included in:

* [Check Point R81](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk166715)

Check Point recommends to always upgrade to the most recent version   
([upgrade Security Gateway](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=overview&product=435) / [upgrade Security Management Server](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=overview&product=184) / [upgrade Multi-Domain Security Management](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=overview&product=166)).

<br />

If you choose not to upgrade,follow these steps:

1.

   ### On the involved VSX Gateway / VSX Cluster member

   1. Connect to command line on the involved VSX Gateway / VSX Cluster member.   

   2. Log in to Expert mode.   

   3. Check whether the problematic interface (reported by "vsx_util") exists in the VSX configuration:  

      **For kernel 2.6:**

      **[Expert@HostName:0]# vrf list ifaces all | grep -v grep | grep <Interface_Name>**

      If the problematic interface appears in the output, then proceed to the next Step 2.

      *Example*:
      >
      > ```
      > [Expert@HostName:0]# vrf list ifaces all | grep -v grep | grep eth3
      > 1 : eth3-01
      > ```

   **For kernel 3.10:**   

   **`[Expert@HostName:0]# netns list ifaces all | grep -v grep | grep <Interface_Name>`**
2.

   ### On Security Management Server / Multi-Domain Security Management Server

   1. Connect to command line on Security Management Server / Multi-Domain Security Management Server.   

   2. On Multi-Domain Security Management Server, switch to the context of *Main* Domain Management Server that manages this VSX Gateway / VSX Cluster:

      **[Expert@HostName]# mdsenv <Domain_Name>**` `  

   3. Set the FWM daemon to skip the verification:

      **[Expert@HostName]# fw debug fwm on TDERROR_ALL_VSXM_DBG_SKIP_RECONF_VERIFY=INFO**` `  

   4. Start the VSX reconfiguration again:

      **[Expert@HostName]# vsx_util reconfigure**` `  

   5. Once the VSX reconfiguration is complete (successfully), set the FWM daemon back to normal operation mode:

      **[Expert@HostName]# fw debug fwm off TDERROR_ALL_ALL=0**

---

# 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