Applies To:Show Versions
VELOS System Overview
Introducing the VELOS system
Restricts user access to root and the bash shell at the system controller, chassis partition, and the tenant levels. When enabled, the root user cannot log in to the device by any means, including from the serial console. Disabled by default.
The primary hardware component that handles traffic management including disaggregation, packet classification, and traffic-steering for the VELOS platform. Up to eight blades can be installed into the slots on the chassis.
The main component of the unit that houses the blades, system controllers, and other components. The chassis can be divided into multiple chassis partitions.
A virtual system or subset of the chassis that handles the management and separation of disjoint sets of blades within the chassis. Partitions form chassis level management and traffic partitions. Each chassis partition is a separate managed device – unlike the BIG-IP system’s administrative partitions within a single managed device. The partition can be managed using REST APIs, partition CLI (confD-based), and a webUI.
chassis terminal service
Built into the system controller software the chassis terminal service provides a means to access each blades' serial console.
Platform operating system software that runs on the system controllers and the chassis platforms.
Link aggregation group. A way to group interfaces on the VELOS system so they function as a single interface. The LAG (like a trunk on Classic BIG-IP systems) distributes traffic across multiple links increasing the bandwidth by adding the bandwidth of multiple links together.
A guest system (similar to a vCMP guest) running software within a chassis partition (for example, a Classic BIG-IP system). Multiple tenants can be deployed in one chassis partition.
Components of the chassis that provide a unified point for external management and connectivity to the platform and applications running in the chassis. The chassis contains a redundant pair of system controllers that provides a high bandwidth interconnect between blades and high availability. The system controllers also provide REST APIs, a system controller CLI (confD-based), and a webUI.
Browser-based user interfaces for configuring the VELOS platform at the system controller (or chassis) level and at the chassis partition level.
VELOS system licensing overview
Features and functionality of an F5 product that a customer can enable by purchasing a license.
base registration key
The base registration key is a 27-character string that informs the license server about which F5 products are included in the license.
Add-on keys enable entitlements on a device, in addition to the entitlements associated with the device base registration key.
A digital fingerprint of an F5 product instance. The dossier uniquely identifies the device.
VELOS system administration overview
System controller administrator
Manages the whole chassis configuration with read-write access to all blades, terminal consoles, system controllers, system settings, and creates chassis partitions and users at the chassis level. Able to change the chassis root and admin passwords.
Has read access to the chassis configuration and the ability to change operator password.
Manages the chassis partition, creates users in the partition, has access to all tenant consoles in that partition. Able to change the partition root and admin passwords.
Has read access to the chassis partition configuration and the ability to change operator password.
Has access to the tenant only. Performs user management on the deployed tenant(s). No management of the VELOS system.
VELOS administration tasks overview
Before using this guide
- Make sure VELOS hardware is installed and the initial configuration of management IP addresses and gateway address is completed. Refer to thePlatform Guide: VELOS CX Seriesfor complete details and descriptions of the hardware.
- Make sure the VELOS system is made accessible. Configure network settings, DHCP, DNS, NTP. Initially, the system controller and chassis partition software will be installed. One default partition is set up for the entire chassis with all slots assigned to it. For information about software installation, refer toVELOS Systems: Software Installation and Upgrade.
Plan the configuration
- Depending on the number of blades installed and your business needs, determine how many chassis partitions to create.
- What is the network configuration at the system controller level including management interfaces?
- What is the network configuration for the chassis partitions including port groups, interfaces, and VLANs. Will you use link aggregation or spanning tree protocol?
- How many administrators and operators will need accounts on the system at the system controller level? On the partition level?
- How will system users be authenticated? RADIUS or LDAP?
- Within each partition, how many tenants do you plan to deploy?
- What will the tenants be used for? For example, which application delivery modules will you be configuring? Multiple modules?
- The configuration can be modified later if needs change.
Configure the system from the system controller
- Log in to the system controller.
- License the system, if it wasn't done already. SeeSystem Settings.
- Adjust network settings such as management interfaces if needed.
- Create chassis partitions dividing up the blades. SeePartition Management.
- Optionally create accounts for system controller administrators or operators. SeeUser Management.
Configure the system from the chassis partitions
- Log in to the chassis partition.
- Configure or adjust port groups, interfaces, VLANs, LAGs. SeeNetwork Settings.
- Optionally create accounts for chassis partition administrators and operators. SeeUser Management.
Deploy tenants in the partitions
- Log in to the chassis partition.
- Consider tenant resources needed with regard to the different tenant images of different sizes that are available. Understand the size of the partition and plan what hardware resources will be configured for this partition. SeeTenant Management.
- Deploy one or more tenants in the partition. SeeTenant Management.
- Log in to each tenant and configure the system as needed. For Classic BIG-IP tenants, seeBIG-IP System documentation.