Cisco Bug: CSCvs55977 - Not able to attach bgp configuration due to "maximum prefix" error
Jan 10, 2020
- Cisco XE SD-WAN Routers
Known Affected Releases
Symptom: Not able to attach feature template due to "maximum prefix command" Conditions: While attaching a feature template we are getting the following error. [16-Dec-2019 19:42:50 UTC] Configuring device with feature template: BR-Template [16-Dec-2019 19:42:55 UTC] Device is online [16-Dec-2019 19:42:55 UTC] Updating device configuration in vManage [16-Dec-2019 19:42:58 UTC] Pushing configuration to device [16-Dec-2019 19:44:08 UTC] Failed to process device request. Error response : rpc-reply error: <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="13"> <rpc-error> <error-type>application</error-type> <error-tag>invalid-value</error-tag> <error-severity>error</error-severity> <error-message unknown:lang="en">inconsistent value: Device refused one or more commands</error-message> <error-info> <severity xmlns=" http://cisco.com/yang/cisco-ia">error_cli</severity>; <detail xmlns=" http://cisco.com/yang/cisco-ia">; <bad-cli> <bad-command> neighbor 126.96.36.199 maximum-prefix 100 100</bad-command> <error-location>45</error-location> <parser-response> % BGP: Peer 188.8.131.52 is being deactivated. Try it later</parser-response> </bad-cli> ------------------ show version ------------------ Cisco IOS XE Software, Version 16.12.01e Cisco ISR4461/K9 (3RU). We have tried to remove this value, however the vManage automatically adds this command after configuring a neighbor statement with password, more details in enclosure attachments router bgp 1000 bgp router-id 184.108.40.206 bgp log-neighbor-changes neighbor 220.127.116.11 maximum-prefix 100 100 address-family ipv4 unicast neighbor 18.104.22.168 remote-as 65521 neighbor 22.214.171.124 activate neighbor 126.96.36.199 password wan2.0 We have tried to reboot the device, rebuild the template and this wont fix the issue.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases