Commit ff21fc1
authored
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?
E2E1 parent 98bfebd commit ff21fc1
File tree
1 file changed
+3
-3
lines changed- device/arista/x86_64-arista_7060x6_64pe/Arista-7060X6-64PE-O128S2
1 file changed
+3
-3
lines changedLines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
110 | 110 | | |
111 | 111 | | |
112 | 112 | | |
113 | | - | |
| 113 | + | |
114 | 114 | | |
115 | 115 | | |
116 | 116 | | |
117 | 117 | | |
118 | 118 | | |
119 | | - | |
| 119 | + | |
120 | 120 | | |
121 | 121 | | |
122 | 122 | | |
123 | 123 | | |
124 | 124 | | |
125 | 125 | | |
126 | | - | |
| 126 | + | |
127 | 127 | | |
128 | 128 | | |
129 | 129 | | |
| |||
0 commit comments