# Unable to remove a single BGP neighbor \[cisco.nxos\]

**URL:** <https://forum.ansible.com/t/unable-to-remove-a-single-bgp-neighbor-cisco-nxos/44820>\
**Category:** Get Help\
**Tags:** network\
**Created:** [November 10, 2025, 8:48am UTC](https://forum.ansible.com/t/unable-to-remove-a-single-bgp-neighbor-cisco-nxos/44820 "2025-11-10T08:48:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![erman44](https://avatars.discourse-cdn.com/v4/letter/e/779978/32.png) [@erman44](https://forum.ansible.com/u/erman44)\
**Post date:** [November 10, 2025, 8:48am UTC](https://forum.ansible.com/t/unable-to-remove-a-single-bgp-neighbor-cisco-nxos/44820/1 "2025-11-10T08:48:33Z")

</div>

Hi! I’ve recently detailed my problem with cisco.nxos.nxos\_bgp\_global module and removing a neighbor from a VRF that’s under a specific BGP.

Long story short, it fails with an error:

```auto
VRF mmsc_radius has address-family configurations. Please use the nxos_bgp_af module to remove those first.

```

You can read the technical details here: [Unable to remove a single BGP neighbor · Issue #1017 · ansible-collections/cisco.nxos](https://github.com/ansible-collections/cisco.nxos/issues/1017)

I would love to help as much as I can. (Even though my contribution history is empty on this account, I do contribute to OS projects.) However, I’d like your input since looking at the error, code and documentation, it looks like it might be intentional? Could you help me out here and point me in the correct direction and maybe the steps I can take to help you solve this issue?

Thanks for all the great work on this module. We really appreciate it.

---

<div class="post-metadata">

**Author:** ![erman44](https://avatars.discourse-cdn.com/v4/letter/e/779978/32.png) [@erman44](https://forum.ansible.com/u/erman44)\
**Post date:** [November 13, 2025, 8:05am UTC](https://forum.ansible.com/t/unable-to-remove-a-single-bgp-neighbor-cisco-nxos/44820/2 "2025-11-13T08:05:22Z")

</div>

I perhaps do not understand the need for the self-fails that the nxos\_bgp\_global module raises. Is that a safety measure so that user doesn’t remove something by accident? Because by removing them, I got the desired outcome. 🙂 Here are the mentioned `self._module.fail_json()` :

[cisco.nxos/plugins/module\_utils/network/nxos/config/bgp\_global/bgp\_global.py at main · ansible-collections/cisco.nxos](https://github.com/ansible-collections/cisco.nxos/blob/main/plugins/module_utils/network/nxos/config/bgp_global/bgp_global.py#L247)

[cisco.nxos/plugins/module\_utils/network/nxos/config/bgp\_global/bgp\_global.py at main · ansible-collections/cisco.nxos](https://github.com/ansible-collections/cisco.nxos/blob/main/plugins/module_utils/network/nxos/config/bgp_global/bgp_global.py#L291)

---

<div class="post-metadata">

**Author:** ![markstos](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/markstos/32/9706_2.png) [@markstos](https://forum.ansible.com/u/markstos)\
**Post date:** [November 13, 2025, 4:04pm UTC](https://forum.ansible.com/t/unable-to-remove-a-single-bgp-neighbor-cisco-nxos/44820/3 "2025-11-13T16:04:46Z")

</div>

@nilashishc His question related to a PR you submitted:

> <https://github.com/ansible-collections/cisco.nxos/pull/225>
>
> \##### SUMMARY
> \- Targets https://github.com/ansible-network/resource\_module\_mode…ls/pull/106
> \- Fixes #106 
> 
> \##### ISSUE TYPE
> \- New Module Pull Request
> 
> \##### COMPONENT NAME
> nxos\_bgp\_global.py

We are trying to figure out if there might be a bug or if the current behavior here is intended.