Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RouteFailover not happening. #10

Open
ebym opened this issue Oct 21, 2021 · 1 comment
Open

RouteFailover not happening. #10

ebym opened this issue Oct 21, 2021 · 1 comment

Comments

@ebym
Copy link

ebym commented Oct 21, 2021 •
edited
Loading

Template

LambdaAA-RouteFailover/6.0/FGT_LambdaAA-RouteFailover_ExistingVPC_BYOL.template.json
Lambda function - python.3.8
FGT v6.2.3 build8404

Successful deployment with modified "fgtami" values in template file, API keys also proper.

When FGT1 is stopped from EC2, FGT1-private route table goes to "blackhole", instead of automatically updating to FGT2-private-eni as per the template.

On FGT -> Automation -> Create Automation Stitch -> Name: "health-check" -> Trigger FortiOS Event Log -> Event: Link Monitor Status -> Action AWS Lambda -> 1st Action Name: "healthcheck-action" -> API Gateway, API Key, ID, Region, etc... are correct.
@MunzerRashed
Copy link

Hi
the routing information will never replicated... as well with IPs of interfaces

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ebym @MunzerRashed