Title: Alarm for ipsec_policy_based_tunnel_down
Event ID: vpn.ipsec_policy_based_tunnel_down
VMware NSX-T Data Center
VMware NSX
Edge Form factors:
Recommended Action:
Networking Tab --> VPN --> IPSec Sessions and check particular session Status.For API, to get the session status details and fail_reason, use following:
3.0.0 and higher
GET /policy/api/v1/infra/tier-0s/{tier-0-id}/ipsec-vpn-services/{service-id}/sessions/{session-id}/statistics
GET /policy/api/v1/infra/tier-1s/{tier-1-id}/ipsec-vpn-services/{service-id}/sessions/{session-id}/statistics
4.2 and higher
GET /policy/api/v1/orgs/{org-id}/projects/{project-id}/infra/tier-1s/{tier-1-id}/ipsec-vpn-services/{service-id}/sessions/{session-id}/statistics
9.1 and higher
GET /policy/api/v1/orgs/{org-id}/projects/{project-id}/transit-gateways/{transit-gateway-id}/ipsec-vpn-services/{service-id}/sessions/{session-id}/statistics
admin and run the command belowget ipsecvpn session summary
get ipsecvpn session sessionid <session-id> :- You get the session-id from the previous commandIPSECVPN session being down, refer to the documentation to know the "Possible Cause" and "Necessary Actions to Resolve the Alarm Message" Alarms When an IPsec VPN Session or Tunnel Is DownMaintenance window required for remediation? No
Alarms When an IPsec VPN Session or Tunnel Is Down
Refer below to check IPsec profile configuration in NSXT for any possible mismatch between local and remote tunnel endpoints.