Site Launch Frequently Asked Questions
Hey there, community. We are maintaining this FAQ as new issues come in that might be experienced by the community at large. This will be continually updated as we fix the discovered issues. Login Issues I can't log in with my existing DevCentral credentials, how do I get logged in? Your existing credentials from the old site will not work. You need to create a new account with a valid email address. I am already a member of DevCentral. Why do I need to create a new account? For years the community has requested consolidated credentials across F5 web properties. DevCentral is the first site taking a step toward that reality, which requires a change in the credential setup. My password manager no longer works because the username and password are handled on separate pages, what can I do? Try any of these password manager tips provided. YMMV. Dashlane 1Password Keepass - auto-type keystroke sequence (#hattip to MVP Patrik Jonnson):{USERNAME}{ENTER}{DELAY 3000}{PASSWORD}{ENTER} Lastpass Profile Issues How do I get all my old content contributions back? Click on your profile and click edit, then scroll down toward the bottom of the page. You can merge in your old content by providing your old username and password and clicking merge account. I have merged my old account. Where are my favorites? The favorites were not ported over. You'll need to rebuild this. Content Issues I am searching on Google for DevCentral content and every link is returning a 404 page. What's wrong? It will take Google some time to index the new site and update its content. This should resolve itself in a week or so. Where is all the /wiki content? The wiki did not journey onward with DevCentral. The API documentation from the wiki is now located athttps://clouddocs.f5.com/api/. Other namespaces in the wiki were not retained, but select content from those areas will be released as articles in the near future. Comment below if there is anything in particular you need and we will prioritize it. You candownload an offline copy of the wikifor personal access. Some links embedded in DevCentral content and most of my bookmarks are resulting in a 404 page. What's wrong? We have some limitations with redirectswe’re working through. We prioritized the links most often visited. Other links are unlikely to work. Please search by title on DevCentral and you should find what you're looking for and can update your bookmarks. We will also be working on embedded links over time. Site Issues Why is nothing redirecting? I hear you make a killer product that does this sort of thing?!? It's not true that nothing is redirecting, we just have some limitations with redirectsand have prioritized the most popular destinations. If you end up on the 404 page, search for your content in the DevCentral search bar and you should find what you're looking for. We are aware of the power of BIG-IP iRules. We've written just a few here and there over the years. Our hosted solution makes using iRules not possible at this time. If you have the Tampermonkeybrowser extension, Michael Jenkins (former MVP) whipped up a couple scripts that will only redirect , or will rewrite on the page at document load and then redirect on click,all the API links that were formerlyin the DevCentral wiki to their new home on Clouddocs. Why is the title font so blurry? There is a rendering condition on the font that needs to be addressed for some browser in some situations. For example, Safari and Firefox show this issue on my external monitor, but it looks fine on my retina screen, whereas with Chrome, it looks fine on both screens. Your mileage may vary.
Frequently Asked Questions - F5 Access 2018
FAQ - F5 Access 2018 (Introduction): What are F5 Networks’ plans for F5 Access and F5 Access 2018 long-term? F5 is committed to providing the latest in SSL VPN technology to its users. Long-term, F5 Networks will focus on providing F5 Access 2018 users with the newest features and bug-fixes necessary for secure remote access. F5 Access will continue to be fully supported until it is transitioned to “Legacy F5 Access” in Fall 2018. What are the differences between the F5 Access and F5 Access 2018 applications? F5 Access and F5 Access 2018 are both SSL VPN applications that are published by F5 Networks on the App Store to provide secure access to enterprise applications. F5 Access 2018 uses Apple’s Network Extension framework to deliver SSL VPN functionality, whereas F5 Access utilizes an older Apple-provisioned plug-in framework. F5 Access will be deprecated over time, but continues to be deployed in many enterprise environments. Which application should my organization use? F5 Access supports Apple iOS v10 and later; it remains the recommended version for organizations that want to leverage the full feature set offered today. F5 Access 2018 will support Apple iOS v11.0 and later. F5 Access 2018 and F5 Access Differences: Configuration Deployment VPN Type Manual Configured MDM Configured Device-wide VPN No Client Certificate import in F5 Access 2018 User has to permit adding the first configuration VPNSubType change: F5 Access: com.f5.F5-Edge-Client.vpnplugin F5 Access 2018: com.f5.access.ios Managed user configuration mode is not supported in F5 Access 2018 Per-App VPN N/A VPNSubType change: F5 Access: com.f5.F5-Edge-Client.vpnplugin F5 Access 2018: com.f5.access.ios Extra key ProviderType must be set to "packet-tunnel" in F5 Access 2018 Key PerAppVpn is no longer required in VendorConfig dictionary in F5 Access 2018 iii. F5 Access 2018 and F5 Access Differences: VPN Establishment VPN Type Manual On-Demand Device-wide VPN F5 Access 2018: Notifications must be enabled for any user prompts or weblogon interactions User is able to save password during connection establishment in native mode if 'save password' is set to 'disk' on BIG-IP F5 Access 2018: Notifications must be enabled for anyuser prompts or weblogon interactions. With mechanism of notifications following is supported in F5 Access 2018: Web Logon mode; Authentication prompt in native mode; Device authentication Per-App VPN N/A Per-App VPN cannot be established if user interaction is required. For F5 Access 2018, configure the F5 Access policy so that user interaction is not required to establish the VPN connection. F5 Access 2018 and F5 Access Differences: BIG-IP Configuration Configuring BIG-IP for Per-App VPN Virtual server changes: Application Tunnels (Java & Per-App VPN) option is no longer needed to be enabled Access policy changes: Since per-app VPN is L3 tunnel in F5 Access 2018 following resources must be assigned to access policy: Network Access resource Webtop Enforce Logon Mode Support Admin can enforce logon mode on server side in the connectivity profile. User cannot change Web Logon option value if it's enforced by BIG-IP. ATS-related changes in F5 Access 2018 Plain text HTTP connections are no longer allowed, and HTTPS with the strongest TLS configuration (TLS 1.2 and PFS cipher suites) is required. Self-signed certificates are not supported (unless CA certificate is set to Trusted on device) Client Cert Authentication Client Certificate Authentication Is Not Supported in Web Logon mode. If you want to use client certificate, it can only be installed via configuration profile (.mobileconfig file) or by your MDM service. What are the support terms for F5 Access and F5 Access 2018? F5 Networks will continue to support both F5 Access and F5 Access 2018 applications simultaneously, but will announce the updated legacy support terms for the F5 Access iOS application in Fall 2018. Can both F5 Access and F5 Access 2018 applications coexist on iOS devices? Yes, both applications can coexist on iOS devices, although it is neither recommended nor supported by F5 Networks. Do I need to change my MDM configurations when transitioning from F5 Access to F5 Access 2018? F5 Access and F5 Access 2018 have different App IDs, so when deploying F5 Access 2018 any existing MDM policies that include the F5 Access application should be re-purposed for the F5 Access 2018 application. All cached F5 Access application data should be removed before deploying and using the F5 Access 2018 application. This includes: saved configurations and certificates. Certificates that were previously deployed for F5 Access can be re-distributed for F5 Access 2018. Are there any usability changes in the F5 Access 2018 application? There are some minor usability changes in the F5 Access 2018 application. These are described in more detail below: Initially Launching F5 Access 2018 Upon the initial launch of the F5 Access 2018 the user is prompted with the following message: “F5 Access 2018” Would Like to Send You Notifications may include alerts, sounds, and icon badges. These can be configured in Settings. It is imperative that the user allow this particular prompt because if he/she doesn’t accept the application will not be able to display prompts necessary to allow native authentication and web logon for multi-factor authentication. Granting initial access to the F5 Access 2018 creates a more seamless user experience. Due to changes in Network Extension, only when user interface interaction is required is the user prompted with modal windows; otherwise the F5 Access 2018 runs quietly in the background. Adding VPN Configurations Adding a VPN configuration results in an additional prompt for permission to create the configuration after the user selects the Save button. Please note: prompt is shown only for 1 st configuration. For 2 nd configuration and all further configurations prompt won’t be shown. If the device is secured with a password, pin, or TouchID authentication methods, the user will be prompted to authenticate. If the user selects “Don’t Allow” in the Add Configuration modal window, the configuration fails to save. Are there specific hardware limitations for using F5 Access or F5 Access 2018? No, F5 Access and F5 Access 2018 can be used from any iOS device including all versions historically available for the following models: iPhones, iPad, and iPod touch. How should I setup a VPN-profile for F5 Access 2018 in Mobile Device Management solution? Device-wide VPN profile: Add VPN profile Select Connection type: “Custom” Set Identifier to “com.f5.access.ios” Complete the rest of configuration as needed. Per-app VPN profile: Add VPN profile Select Connection type: “Custom” Set Identifier to “com.f5.access.ios” Select Provider Type: “Packet Tunnel” Complete the rest of configuration as needed.BIG-IP Cloud Edition FAQ
BIG-IP Cloud Edition is designed to enable easy to use and fast self-serve deployments of application services in private and public clouds. BIG-IP Cloud Edition is a solution composed of BIG-IP Per-App VEs and BIG-IQ CM 6.0. It's designed to deliver the same consistent industry leading intelligent traffic management (F5 Local Traffic Manager – LTM) and advanced web application firewall (Advanced WAF) services. For more information on BIG-IP Cloud Edition Components please read K3341282 on AskF5. In this FAQ you'll find a growing list of frequently asked questions about the BIG-IP Cloud Edition. Please provide feedback in this discussion thread. BIG-IP Cloud Edition Questions What is BIG-IP Cloud Edition? BIG-IP Cloud Edition is a solution composed of the BIG-IP Per-App Virtual Editions for app service auto-scaling plus BIG-IQ 6.0 per-app management and analytics capabilities. What are the minimum versions needed for BIG-IP Cloud Edition? The minimum versions required to support the full Cloud Edition solution is BIG-IP version 13.1.0.5 or later and BIG-IQ version 6.0. What are the supported cloud evironments for BIG-IP Cloud Edition? At release VMware and AWS environments will be supported. Support for Azure and other cloud providers is planned. Can BIG-IP Cloud Edition be deployed into private or public cloud? Yes, BIG-IP Cloud Edition can be deployed in the same clouds as BIG-IP VE, and managed as any BIG-IP normally would, but we are delivering lifecycle management functionality, e.g. spin-up/spin-down, autoscaling, and rolling upgrades using BIG-IQ for VMware vSphere and AWS cloud environments. Can I upgrade existing BIG-IQ 5.x to 6.0? Initially no, upgrades to 6.0 for existing BIG-IQ customers will be supported in 6.0.1 released later this year, along with support for BIG-IP 12.1.x versions. The intial release of BIG-IQ 6.0 will be limited to new installations of BIG-IQ. Is the BIG-IP AVR module required for BIG-IQ analytics? Are BIG-IQ Data Collection Devices (DCDs) required for analytics? Yes, AVR will be required to be provisioned on the BIG-IP’s utilized in the Cloud Edition use cases. Many of the advanced analytics use cases require AVR to collect more detailed HTTP layer, and performance stats to trigger autoscale. When setting up the Device Templates the admin will need to enable AVR. The AVR overhead on BIG-IP is lighter as all the processing/aggregation is done on BIG-IQ instead of BIG-IP. Data Collection Devices (DCDs) are required to receive the advanced analytics from BIG-IP and are available with a free license. What is an App Template? BIG-IQ 6.0 Application Templates are a way of standardizing application and security services deployment and policies required by an application in a service catalog as defined by the BIG-IP admin or domain expert. BIG-IQ 6.0 will include pre-defined templates for the common web application configurations. An App owner given the appropriate role-based access can then select a template that matches their desired deployment, fill out the required fields and then automatically deploy the application service for his/her application in the UI or can use published and documented APIs. What is a Device Template? BIG-IQ Device Templates are used to on-board BIG-IP Virtual Editions by enabling device instantiation, licensing, provisioning, and networking and are used along with application templates to support autoscaling. This allows complete automation of the environment, with no human involvement required to scale out VE services. Where can I give general feedback on the BIG-IP Cloud Edition? Please provide feedback through the DevCentral Q&A discussion for BIG-IP Cloud Edition. BIG-IP Per App VE Questions What is BIG-IP Per App VE? BIG-IP Per-App VE is a virtual edition designed and priced for dedicated per-app services, with licensed features for 1 VIP, 3 Virtual Servers, and support of LTM and Advanced WAF, and 2 throughput options, 25Mbps and 200Mbps. What is the ‘1 virtual server, 3 virtual servers' limit? Per-App VE is designed to support one application therefore it was licensed to support a single virtual IP address. However, within the 1 virtual IP address, administrators can also use 3 virtual server parameter different port numbers for the virtual IP. Within the allowed 3 virtual servers, one wild card virtual server is allowed primarily to support outbound traffic from backend servers. BIG-IP Per App VE BIG-IP VE (Standard # of Applications Supported 1 Virtual IP & 3 Virtual Servers Skys the Limit BIG-IP Services Available LTM Advanced WAF All Application Services Throughput Per Instance 25Mbps, 200Mbps 25Mbps, 200Mbps, 1GB, 3GB, 5GB, 10GB, High Peformance Licensing Models Subscription, Enterprise License Agreement, Perpetual Subscription, Enterprise License Agreement, Perpetual, Pay-As-You-Go Is there a BIG-IP version requirement for Per-App VE? Yes. Per App VE is available in BIG-IP version 13.1.0.2 but for full Cloud Edition functionality we require version 13.1.0.5 or later. I hear there are smaller images for VE, are these only for the Per-App VE? No, the smaller images are be available in the BIG-IP v13.1.0.2 and later releases and are not restricted to Per-App VE. F5 is reducing the disk size for all virtual editions. Are there different images for the Per App VE and the standard BIG-IP VE? No. The images are the same between the per-app VE and the standard VE. Software licensing determines Per App VE or standard BIG-IP VE functionality. What is the relevance of single slot images and Per-App VE? Slot = Boot Partition. Per-App VE increases the scale of deployments and cost savings on footprint becomes even more relevant. Per-App VE will be typically targeted for 'wipe/deploy' instead of in-place upgrades of BIG-IP. The 1 slot images provide further storage savings by removing the 2nd slot which has been used for version upgrades. 1 slot images are avilable for Per App VE and standard BIG-IP virtual editions. With the new Single Slot VE images, how do we perform upgrades? There is no capability to upgrade software to a new version or even a HF or point release as we now call them. Instead they need to be deployed in an environment that support wipe/deploy type workflows. Wipe/deploy basically means that a new instance with the new version of software is provisioned, and it will replace the older version VE either through automation, or some sort of auto-scale type workflow where traffic is directed from the older instance to the newer one. Can I upgrade from Per-App VE to a standard VE by adding/changing the license? Nope. You can license manage Per App VE along side standard virtual editions through BIG-IQ but they are not interchangeable.
