search

F5Networks / f5-aws-cloudformation

CloudFormation Templates for quickly deploying BIG-IP services in Amazon Web Services EC2
112 stars 118 forks source link

Template failing to build F5's in US-GOV-EAST region #138

Closed misterx280 closed 3 years ago

misterx280 commented 3 years ago

Description

Describe the problem you're having or the enhancement you'd like to request.

Deploying the 3 nic clustered cross AZ F5 template fails to build a configured F5 HA pair. The CFT runs with 0 errors abut when I log onto the F5s they are in a standalone state with no networking, resource provisioning, or HA configurations. The F5s are licensed and ready for initial setup.

Template

For bugs, enter the template with which you are experiencing issues below.

f5-existing-stack-across-az-cluster-payg-3nic-bigip.template

Severity Level

For bugs, enter the bug severity level. Do not set any labels.

Severity: 1. without this template I cannot continue the F5 build in my VPC.

Severity level definitions:

  1. Severity 1 (Critical) : Defect is causing systems to be offline and/or nonfunctional. immediate attention is required.
  2. Severity 2 (High) : Defect is causing major obstruction of system operations.
  3. Severity 3 (Medium) : Defect is causing intermittent errors in system operations.
  4. Severity 4 (Low) : Defect is causing infrequent interuptions in system operations.
  5. Severity 5 (Trival) : Defect is not causing any interuptions to system operations, but none-the-less is a bug.
JeffGiroux commented 3 years ago

Anything obvious stick out in the log files? Check /var/log/cloud directory for log errors.

misterx280 commented 3 years ago

Deploying new stack and checking right now.

Chris

On Tue, Oct 13, 2020 at 10:06 AM Jeff notifications@github.com wrote:

Anything obvious stick out in the log files? Check /var/log/cloud directory for log errors.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/F5Networks/f5-aws-cloudformation/issues/138#issuecomment-707762863, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN2ZYVJDMCJ2NXBTR5AJHXLSKRNGZANCNFSM4SO5JDFA .

misterx280 commented 3 years ago

There is no /var/log/cloud directory but there are two logs called cloud-init.log and the other is cloud-init-output.log.

hparr commented 3 years ago

The management interface and the Eth1 (external interface) both require access to the internet to complete deployment. This can be via Elastic IP or NAT Gateway services. The lack of a /var/log/cloud/ directory indicates that this requirement has not been met. As an instance boot straps an outgoing call is made from the management interface to download the libraries required to onboard the system (and activate a BYOL license). After these libraries are installed a TMM interface is used to contact S3 and other APIs to complete the configuration of the systems and cluster them.

misterx280 commented 3 years ago

roger, will check the IGW and NAT gateways.

hparr commented 3 years ago

Note that the SG/NACL needs to also allow ICMP as that is one of the network connectivity checks used by the onboarding process.

misterx280 commented 3 years ago

There was no NAT gateway on the management route. that solved my problem thank you.

hparr commented 3 years ago

That is good news - happy to help.

shyawnkarim commented 3 years ago

Closing. Please reopen if additional help is needed.