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.

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

Can CFE support moving IP prefixes in AWS? #82

Open
mikeoleary opened this issue Jul 23, 2021 · 1 comment
Open

Can CFE support moving IP prefixes in AWS? #82

mikeoleary opened this issue Jul 23, 2021 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@mikeoleary
Copy link

Do you already have an issue opened with F5 support?

No.

Description

AWS recently announced the ability to configure an ENI with a range of IP address, as opposed to /32 address. There's a few limitations in the details, including that IPv4 prefixes must be /28 and IPv6 must be /80.

I have tested with CFE v1.9, where I had an A/S pair and the Active device was configured with IPv4 address, multiple IPv6 addresses, and an IPv4 range of /28. Upon failover, CFE worked as expected (IPv4 and IPv6 addresses failed over), but the IPv4 range did not fail over.

Could we see support for moving of IP prefixes in AWS in future? I have not had this as a requirement from a customer yet (I think the announcement of the feature was yesterday) but I expect that customers will find these prefixes a popular option.

Environment information

For bugs, enter the following information:

  • Cloud Failover Extension Version: 1.9
  • BIG-IP version: 16.1
  • Cloud provider: AWS

Severity Level

3

@shyawnkarim
Copy link

Thanks for bringing this to our attention. We are now tracking it internally with ID AUTOSDK-560.

@shyawnkarim shyawnkarim added the enhancement New feature or request label Aug 2, 2021
@shyawnkarim shyawnkarim added this to the backlog milestone Aug 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants