Actions
Bug #11792
closedCannot disable IPsec P1 when related P2s are in VTI mode and enabled
Start date:
04/08/2021
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
21.05
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
Setup:
IPsec Phase 1 with one or more Phase 2 entries in VTI mode. No IPsec interfaces assigned.
Issue:
While both P1 and P2 are enabled, try disabling the P1. The following error is shown:
Cannot disable a Phase 1 with a child Phase 2 while the interface is assigned. Remove the interface assignment before disabling this P2.Expected:
- When clicking disable on P1, the P1 along with all its P2s should be disabled to match the behavior of non-vti P2s - as long as related IPsec interfaces are assigned.
- The error description should say:
Cannot disable a Phase 1 with a child Phase 2 while the interface is assigned. Remove the interface assignment before disabling this P1.
This is related to #10190
Related issues
Updated by Viktor Gurov over 3 years ago
Updated by Jim Pingle over 3 years ago
- Status changed from New to Pull Request Review
- Target version changed from CE-Next to 2.6.0
Updated by Viktor Gurov over 3 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
Applied in changeset 66c5f2959f391760eb8f1728131792161067a7d8.
Updated by Jim Pingle over 3 years ago
Marcos Mendoza wrote:
Tested latest snapshot. Worked well.
2.6.0 snapshot or 21.05 snapshot?
Updated by Jim Pingle over 3 years ago
- Target version changed from 2.6.0 to 2.5.2
Updated by Viktor Gurov over 3 years ago
- Related to Bug #12198: Disabling an IPsec phase 1 entry does not disable related phase 2 entries added
Actions