Push Feature error after change Localized Policy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2023 09:12 PM
After changing configuration in Localized Policy -> Data Prefix List I get error.
I change my acl, put new value - 192.168.10.5/32 (or other ip) and get error like that -
22-Jan-2023 13:54:18 MSK] Device: Data provider returned CONFD_ERRCODE_INCONSISTENT_VALUE (38): inconsistent value: Device refused one or more commands: 100 permit 192.168.10.5 0.0.0.0 ^ % Invalid input detected at '^' marker. Component Response: " % Duplicate entry exists at sequence 110"
I thought that vmanage just has to add new value, but it tries add already existing values again.
how can I fix it? without deleting and adding all policy?
My version is 20.9.1 and I have a cluster
- Labels:
-
SD-WAN vManage
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2023 01:40 AM
i have noticed the error , Is there the same configuration in seq 110? Or whether it's ok when permit host x.x.x.x
% Duplicate entry exists at sequence 110"
Rps-Cheers | If it solves your problem, please mark as answer. Thanks !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2023 02:54 AM - edited 01-29-2023 02:58 AM
This is an existing ACL, it happens when I add new string
110 permit 192.168.11.5 0.0.0.0
120 permit 192.168.12.5 0.0.0.0
130 permit 192.168.13.5 0.0.0.0
140 permit 192.168.14.5 0.0.0.0
After I try to add new string - 192.168.10.5/32 in my existing Data Prefix List I get the error
% Invalid input detected at '^' marker. Component Response: " % Duplicate entry exists at sequence 110"
% Duplicate entry exists at sequence 120"
% Duplicate entry exists at sequence 130"
% Duplicate entry exists at sequence 140"
vManage doesn't add new string sometime, and I have to delete local policy acl and add again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2023 05:32 AM
This may be a bug, it is recommended to open a Cisco TAC CASE to confirm.
Please let me know if there is an update. thanks
Rps-Cheers | If it solves your problem, please mark as answer. Thanks !
