Last Modified: Mar 17, 2021
See more info
Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 11.6.4, 11.6.5, 126.96.36.199, 188.8.131.52, 184.108.40.206
Opened: Sep 12, 2014
Non default route domain can be deleted without any error, even if there an ike-peer or ipsec-policy or traffic-selector referencing the route domain.
Traffic may stall if this is occurs in the middle of data transfer. Also note that any updates to the IPsec IKEv2 configuration may not be allowed after the deletion of the route domain
1. Create a route domain and associate (wan and lan) vlan interfaces to the route domain. 2. Create the self ip's for the wan and lan interfaces. 3. Configure the ipsec-policy, traffic-selector and ikev2-peer in the route domain. 4. Pass traffic and establish the tunnel. 5. Delete the self ip and the route domain. 6. Notice that route domain can be deleted and MCP does not complains that ike-peer or ipsec-policy or traffic-selector still references this route domain.
MCP will throw an error if the user tries to delete a route domain that is referenced by any ike-peer or ipsec-policy or traffic selector.