# Removing FRRouting Configuration Is Not Idempotent

DevFeed: [Removing FRRouting Configuration Is Not Idempotent](<https://devfeed.tech/articles/removing-frrouting-configuration-is-not-idempotent-10947.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2024/02/frr-bgp-prefix-origination/>)

Published: 2024-02-07T07:22:00Z

Content type: opinion

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Ansible](<https://devfeed.tech/topics/ansible.md>)

Tags: [ansible](<https://devfeed.tech/tags/ansible.md>), [automation](<https://devfeed.tech/tags/automation.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [linux](<https://devfeed.tech/tags/linux.md>)

## AI overview

The article explains that removing BGP network statements, IP addresses, and BGP processes in FRRouting is not idempotent. It recommends generating complete configuration files and using FRRouting reload functionality when automating configuration changes.

## Source excerpt

One of the few beauties of most "industry standard CLI" implementations1 is that they're idempotent: nothing changes (apart from ACLs) if you configure the same stuff a dozen times. Most of these implementations allow you to deconfigure the same stuff multiple times; FRRouting is one of the unfortunate exceptions. I'm not saying what FRRouting does is wrong. It's just different and a bit unexpected once you get into the mindset of "Wow, it looks almost like Cisco IOS." What Am I Talking About? Imagine you have a bunch of IP prefixes you want to advertise with BGP. You could use network statements within the router bgp configuration to get that done: Read more ...