Skip to content

GB-302: the IPsec link did not come up on the new leaf; the old pair was put back

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-302 is printed by goatbuilder. The same text offline: goat explain GB-302 or goatbuilder explain GB-302.

What it means

After switching to the staged leaf, goat-peering-edge loaded the credentials, re-authenticated the IKE SA and waited up to peering_edge_rotation_confirm_seconds (the DPD timeout by default) for an established IKE SA with an installed CHILD SA. None came up, so it put the set-aside pair back from .previous-<id>/, loaded it and re-authenticated: the old leaf is live. It marks the rotation rolled back (.previous-<id>/rolled-back), so every later run of the same id, a resume or a retire, reports GB-302 again, moves nothing and never replaces our CA. For ipsec-ca with --no-overlap, a partner that no longer trusts our old CA cannot carry the link on the old pair either.

Why it happens

  • the partner does not trust the CA that issued the new leaf
  • the partner's edge expects another identity, or is not reachable
  • this rotation id was rolled back by an earlier run

What to do

One line per step or alternative:

read swanctl --list-sas and the charon log on both edges, then stage the new pair again and start a rotation with a new id

Read more

Exit code

goatbuilder exits with 2.