Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update O128S2 port_config.ini (#21561)
What is the motivation for this PR? Patch Applier: * [{"op": "remove", "path": "/BGP_PEER_RANGE/BGPSLBPassiveV6"}]\n Patch Applier: * [{"op": "add", "path": "/BGP_PEER_RANGE/BGPVac", "value": {"ip_range": ["192.168.0.0/21"], "name": "BGPVac", "src_address": "10.1.0.32"}}]\n Patch Applier: * [{"op": "remove", "path": "/BGP_PEER_RANGE/BGPSLBPassive"}]\n Patch Applier: * [{"op": "add", "path": "/BGP_PEER_RANGE/BGPSLBPassive", "value": {"ip_range": ["10.255.0.0/25"], "name": "BGPSLBPassive", "src_address": "10.1.0.32"}}] The problem comes from that the running config already has 192.168.0.0 in BGPSLBPassive when add ip_range 192.168.0.0 to BGPVac. Then it cause the ip_range duplicate issue. Though the BGPSLBPassive's ip range change also in the patch, it comes after BGPVac which cause issue during the rollback. The fix is to clean up the config before rollback. How did you do it? Remove BGP_PEER_RANGE config before rollback. How did you verify/test it? E2E
- Loading branch information