NSX V2T migration fails with error "Config translation failed [Reason: [TOPOLOGY] Can not proceed with migration: BGP neighbors with same ipAddress cannot have different attributes holdDownTimer,keepAliveTimer,removePrivateAS. Update and retry.]"
search cancel

NSX V2T migration fails with error "Config translation failed [Reason: [TOPOLOGY] Can not proceed with migration: BGP neighbors with same ipAddress cannot have different attributes holdDownTimer,keepAliveTimer,removePrivateAS. Update and retry.]"

book

Article ID: 407092

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • In the Migrate configuration phase, task fails with following error:

    • Config translation failed [Reason: [TOPOLOGY] Can not proceed with migration: BGP neighbors with same ipAddress <bgp_neighbor_ip_address> cannot have different attributes holdDownTimer,keepAliveTimer,removePrivateAS. Update and retry.]

Environment

VMware NSX for vSphere

VMware NSX

Cause

This error is thrown because same BGP neighbor in different Edges have different values/configuration for attributes Hold Down Time, Keep Alive Time and Remove Private AS.

Resolution

For a successful Configuration migration, ensure the above listed attributes for BGP neighbor have same value/configurations in all the Edges.

Following steps can be performed to make the values/configuration uniform:

  1. Log in to the vSphere Client.

  2. Click Networking & Security > NSX Edges.

  3. Double-click an NSX Edge.

  4. Click Manage > Routing > BGP.

  5. In the Neighbors table, select the BGP neighbor and click Edit.

  6. Ensure the Hold Down Time, Keep Alive Time and Remove Private AS for this neighbor is same across all Edges.