Autoscaling in AWS version 3 (Gateway load balancer integration) - Firewalls never register in Panorama

[TonyCleveleys]

Hi all,

This is a really helpful group and I hope you can help with this challenge.

1. We deployed the ASG using Template 3.0 - all successful.

2. Firewalls bootstrapped successfully.

3. The lambda had a problem enabling the VM-Series element for cloudwatch (stated error 13 in use but) managed to make the change manually

4. Everything else error free

We are coming out of the firewall VPC and hitting the Panorama box in another VPC on it's external address. This never seems to complete the registration process and panorama status is disconnected.

Things I've tried:

1. Checked the ports

2. Validated the bootstrap auth code (works fine and bootstrap is clear)

3. Lowered the MTU on interface 1/1 to 1400

4. Manually registered a firewall in Panorama with the serial number and generated a manual auth code.

5. Used that auth code on one of the firewalls to connect to Panorama. The auth code is accepted but still states disconnected on the firewall and in Panorama.

It's really tough to get any detailed diagnosis for the error. Did I miss something?

We are running version 10.1.0 on the firewalls and in Panorama.

Would really appreciate a steer if anyone has faced this issue.

[TonyCleveleys · Accepted solution]

I fixed this. Just incase it's useful for anyone else the guide is unclear and it's important to name your template with a different name than the template name in the init-cfg.txt. The lambda creates a template stack and it's important this name is unique. Once I changed the name the firewalls registered.