Cowboy Denny Posted February 8 Share Posted February 8 This is designed to introduce you to the core features of the F5 rSeries platform. It begins with a high-level view of the system components and defines key concepts such as F5OS and tenants. Next, it presents the management domains available and how the naming and numbering convention is used to identify the rSeries platform. Getting Started with rSeries This course is designed to introduce you to the core features of the F5 rSeries platform. The course begins with a high-level view of the system components… Lesson Objectives The F5® rSeries platforms are powerful systems that are designed specifically for application delivery performance, application security, and scalability. The rSeries delivers unprecedented levels of performance, and it leverages API-first deployment next generation platform software. At the end of this course, you will be able to: Identify the major components of the rSeries platform Describe the role of F5OS and tenants Interpret the rSeries naming and numbering convention Describe the Dashboard Identify the two Software Management Domains Introducing the r10000 The r10000 system provides the flexibility and feature-rich capabilities of F5 products on a powerful and highly extensible hardware platform. The front of the r10000 series platform includes the following as displayed in the graphic: The LCD touchscreen includes a Health menu which enables you to run LCD tests. The LED indicators of the various LEDs on the platform indicate the status of the system or component. The F5 logo ball LED indicates whether the system is powered on and if the locator function is enabled. The F5 ball will blink if the locator function is enabled. The r10000 series contains the following management ports as displayed in the graphic: Management port USB 3.0 port Serial console port Serial failover port (future use) r10000 supports the following interface ports as displayed in the graphic: 25GbE SFP28 ports (16) 100GbE QSFP28 ports (4) The back of the r10000 Series platform includes a removable fan tray, two power supply units (PSUs), and a chassis ground terminal. The r10000 Series platforms are available with either an AC, a standard DC, or a high-voltage DC (HVDC) configuration. Fan tray (removable) Power input panel 1 (AC power receptacle) Power input panel 2 (AC power receptacle) Chassis ground terminal F5 platforms support up to two AC, DC, or high-voltage DC (HVDC) hot-swappable power supply units (PSUs). Do not mix power supply unit models of different wattage. Use only PSUs of the same wattage and part number. The chassis has a removable fan try that is designed to maintain airflow throughout the chassis. The fans in the fan tray run constantly while the unit is powered on. Over time, the fans may wear out, requiring you to replace the fan tray. Introducing the r5000 The r5000 Series platform is a powerful system designed specifically for application delivery performance and scalability. The front of the r5000 series platform includes the following as displayed in the graphic: The LCD touchscreen includes a Health menu which enables you to run LCD tests. The LED indicators of the various LEDs on the platform indicate the status of the system or component. The F5 logo ball LED indicates whether the system is powered on and if the locator function is enabled. The F5 ball will blink if the locator function is enabled. The r5000 series contains the following management ports as displayed in the graphic: Management port USB 3.0 port Serial console port Serial failover port (future use) The r5000 series platform supports the following interface ports as displayed in the graphic: 100GbE QSFP28 ports (2) 25GbE SFP28 ports (8) The 5000 Series platform contains either AC power supply or DC power supply. The AC power supply units (PSUs) are displayed here. Do not mix power supply unit models of different wattage. Use only PSUs of the same wattage and part number. The 5000 Series platform contains either AC power supply or DC power supply. The DC power supply units (PSUs) are displayed here. rSeries Naming and Numbering Convention Example: r10900 Generation r = Vanquish/Pantera OR i = Shuttle Series Price Point Low = 4xxxx, 2xxxx Mid = 5xxxx High = 7xxxx, 10xxx PAYG (Pay As You Grow) 6 = Low 8 = High 9 = High+ Mid-Gen (new CPU) 0 Reserved 0 From left to right, the rSeries naming convention uses the first letter to identify the generation. The "r" represents the rSeries. The first number, "10" in this example, represents the series price point, whether it's low, medium, or high. The next number, "9" in our example, represents "Pay as You Grow," giving you the ability to upgrade from one tier to another through license keys. The next number, "0" in this case, represents mid-Generation. This would be used, for example, if a new CPU is introduced. The last digit, "0" is reserved. Interface Examples Configuring the rSeries appliance can be accomplished using API calls, the command line interface (CLI), or the graphical user interface (GUI). The following are examples of creating a BIG-IP tenant using an API call, the CLI, and the GUI. Create BIG-IP Tenant via API Create a BIG-IP tenant via an API call. Create BIG-IP Tenant via CLI Create a BIG-IP tenant via the CLI. Create BIG-IP Tenant via GUI Create a BIG-IP tenant via the GUI. Key Concepts: F5OS-A and Tenants F5OS-A F5OS-A is a host environment responsible for configuring, provisioning, and deploying BIG-IP tenants, as well as managing and monitoring the appliance hardware. The software provides all of the basic administration capabilities needed to manage the system software version, download BIG-IP tenant software, and manage tenants, manage the license, manage users, and configure VLANs and trunks for the tenants. It is a Kubernetes based platform layer for F5 systems that enables higher automation and multi tenancy. F5OS is delivered in two versions, F5OS-C for chassis (VELOS) and F5OS-A for appliance-based hardware (rSeries). Tenants A tenant is a guest system running software on the appliance (for example, a Classic BIG-IP system). You can run several tenants in the same appliance, by assigning them resources from the appliance. The maximum number of tenants that can be created in an appliance depends on the model and resources available on that model. The administrator can install BIG-IP Virtual Edition (VE) onto tenants. The rSeries uses Kubevirt to launch BIG-IP VE. The administrator downloads the tenant software image files from the F5 downloads site. (Note: requires login credentials.) A tenant will consist of one or more CPUs, memory, and storage. You manage the tenants using the API, CLI, or GUI. Tenants inherit certain capabilities, such as the license and VLANs, from the appliance. rSeries Software Management Domains There are two different Management Domains in the rSeries — the platform layer and the tenant layer. Each has its own management IP address, set of users, and its own software. Each Management Domain can be accessed via API, CLI, or GUI. F5OS-A is a host environment responsible for configuring, provisioning, and deploying BIG-IP tenants, as well as managing and monitoring the appliance hardware. The tenants are managed by the Tenant Administrators. Dashboard The dashboard displays a graphical view of the platform interfaces (ports) and high-level information about network ports, vCPUs, active alarms, and tenants. System Summary The System Summary displays information about system storage, hostname, IP address, product name, software versions, available vCPUs, and deployed vCPUs. Network The Network displays the current state for all system interfaces (ports) and port mappings. CPU The CPU displays information about CPU thread counts. Active Alarms Active Alarms determine where an event occurred, the severity, the description, and the time it occurred. The system updates the alarms every few seconds. It shows the source of the alert, its severity, a brief description of what occurred, and when it happened. The lower section includes an overview of tenants deployed on the system. About Licensing The license you receive from F5 determines what features and software modules the BIG-IP tenant will support. Before you can configure and use the rSeries system, you must activate a valid license. The license service coordinates the license installation on the system and configures the same license to the tenants. The license activation process is initiated with the base registration key. Review In this lesson, you learned how to: Identify the major components of the rSeries platform Describe the role of F5OS and tenants Interpret the rSeries naming and numbering convention Describe the Dashboard Identify the two rSeries Software Management Domains rSeries Datasheet f5-application-delivery-controller-system-rseries-data-sheet.pdf Link to comment Share on other sites More sharing options...
Recommended Posts