F5OS share APM VPN licence across tenant clusters
Hello, I have deployed a pair of r5900 series appliances. On these appliances, I have an Active/Standby tenant cluster of F5 BIG IP running with the APM module provisioned and an APM configuration dedicated to SSL VPN using the F5 Edge Client. The F5OS chassis are using 3 licences : r5900 Best bundle APM 1000 VPN Users (x2) This means that the production environment can handle up to 2000 concurrent users connected at the same time, on the APM-enabled BIG-IP tenants. My question is the following : Can I create 2 new tenants running BIG-IP with APM module and create a new APM configuration for VPN testing purposes ? How are the "APM 1000 VPN Users" licence shared across tenants running on the same r5900 chassis ? In the official F5OS documentation, I have noticed that every tenants inherits the licences provisionned on the F5OS chassis. But there is no explanation regarding the sharing of the VPN seats included in the APM VPN licences. Thank you.
AD/LDAP Auth on rSeries F5-OS
AD/LDAP auth on F5-OS seems unnecessarily complicated compared to how TMOS handles it. Does anyone have this working in their environment? If so, can you explain which attributes are created (F5-F5OS-UID, F5-F5OS-GID, uidNumber, gidNumber, etc.) and if they are applied directly to the AD user and/or AD group? The config guide mentions that F5-F5OS-GID is the only required attribute (F5-F5OS-UID defaults to 1001). It's not clear to me if this attribute must be added directly to the user account or if it can be created in an AD group that the user is a member of. Then there is aSolution Article that says LDAP requires the user have a uidNumber and gidNumber. The AD group must have a gidNumber that corresponds to the associated group ID of the F5 system role. They provide an example of a AD user and AD group showing uidNumber and gidNumber, but there is no reference to F5-F5OS-GID.
F5OS R4800 upgrade to 1.7.0
Hi All, I have installed a F5 R4800 platform in our test environment, now i want it to upgrade to 1.7.0. After the upload the new image via GUI, it stays in "Signature Verification Failed" status. I have installed a R5900 platform in production, over there i no issue to upgrade to version 1.7.0 Dont know if the platform is doing verification through internet or not. Does anyone knows by chance. Thanks in advance.
F5OS missing interfaces in tenant
Hello, I'm totally new to F5OS, I'm configuring a rSeries 2600 (1.5.1-12283) and deploying a tenant (BIG-IP 15.1.5.1 Build 0.0.14 Point Release 1). All seemed to work perfectly fine both in the host and the tenant deployments, but looking at the interfaces section on the tenant the list is totally empty! And in VLAN properties the "interface" section is missing. I assigned VLAN's to interfaces in the Network Settings at F5OS level - would it be by design that the interfaces are no longer showed in the tenant ? I tried to find info in the doc with no results... Any info/help would be more than welcome :-) Thanks & have a good day, GeraldAnsible modules for F5OS
Hello everyone, Any ansible modules available to configure F5OS hypervisor?, i am looking to automate the baseline configuration when we have a new F5OS based box, when i say baseline configuration it includes setting the hostnames, login banner, dns server, ntp, snmp, creating new tenants etc... are they any plans from F5 to release ansible modules for F5OS like what F5 team releases modules for BIG-IP??. if there are no plans what would be the general recommendation to go with either ansible shell module (or) ansible expect module to configure the F5OS box?? thank you, kumar
Upgrade 14.1.5.4 to newer version
I will migrate a physical BigIP running 14.1.5.4 to a new appliance running F5OS and tenant image. The current BigIP has a lot of configuration, features, iRules and so on and I plan to use Journeys. What would be a recommended image for the tenant from field experience? I see 14.x supports migration up to 16.x. Given the breadth of configuration currently in place I wonder if I should go to the latest 15 first and go from there for future updates when the production is confirmed stable on the new systems.
F5OS support for TACACS+ over CLI
We ran into issues deploying rSeries and VELOS platforms on the network at our company using a custom form of TACACS+. Our implementation allows for application-specific domains with unique ports and keys. We had issues with it until we added the attribute value pairs to the TACACS+ domain profiles: Admin (unlimited_config): F5-F5OS-UID=1001 F5-F5OS-GID=9000 Operator (unlimited_enable): F5-F5OS-UID=1001 F5-F5OS-GID=9001 This change resolved the access issues via GUIand we are able to access using our TACACS+ credentials, but it does NOT work via CLI for access using the same credentials. We already have a case out to F5 about this, but I was wondering if anyone else is experiencing the same implementation challenge on accessing CLI using TACACS+.
