extlb healthcheck maps to loopback.1 to hit nat rule #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you @yyzh1. This saved me after hours long of troubleshooting the unhealthy external load balancer. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
extlb healthcheck maps to loopback.1 to hit nat rule
Motivation and Context
The current configuration on the PANW vm series does not map the extlb healthcheck correctly.
Due to the existence of loopback.1, the extlb heathcheck coming into ethernet1/1 will then be targeting loopback.1, which fails to match the NAT for healthcheck probes.
With the current configuration, from GCP load balancer, both active and passive backends behind external load balancer will show health check as failed.
How Has This Been Tested?
Have followed the steps in README.md to apply the new configuration. Both internal and external load balancer will behave correctlty with active vm series showing healthy and forwarding traffic.
Screenshots (if appropriate)
Types of changes
Checklist