- play_arrow Configure Kubernetes and Contrail
- play_arrow Configure DPDK
- play_arrow Configure Services
- play_arrow Analytics
- Contrail Networking Analytics
- Contrail Networking Metric List
- Kubernetes Metric List
- Cluster Node Metric List
- Contrail Networking Alert List
- vRouter Session Analytics in Contrail Networking
- Centralized Logging
- Port-Based Mirroring
- Configurable Categories of Metrics Collection and Reporting (Tech Preview)
- Juniper CN2 Technology Previews (Tech Previews)
Health Check
SUMMARY In Cloud-Native Contrail Networking (CN2) Release 22.3, a new health check custom resource object is introduced that associates the virtual machine interface (VMI) to the pod creation and update workflow. The health check resource is a namespace-scoped resource.
Health Check Overview
The health check functionality is provided by the Contrail vRouter agent. You can associate a ping or HTTP health check to an interface. If the health check fails, based on the timers and intervals configured in the health check object, the interface is set as administratively down and associated routes are withdrawn. Health check traffic continues to be transmitted in an administratively down state to allow for an interface to recover.
Health Check Process
The Contrail vRouter agent is responsible for providing the health check service. The agent spawns a health check probe process to monitor the status of a service hosted on the same compute node, and the process updates the status to the vRouter agent.
The vRouter agent acts on the status provided by the script to withdraw or restore the exported interface routes. The agent is also responsible for providing a link-local metadata IP address for allowing the script to communicate with the destination IP address from the underlay network, using appropriate NAT translations. In a running system, this information is displayed in the vRouter agent introspect at:
http://<compute-node-ip>:8085/Snh_HealthCheckSandeshReq?uuid=