Manual Chapter : Getting started with F5 VELOS
Applies To:Show Versions
- 1.5.0, 1.3.2, 1.3.1, 1.3.0, 1.2.2, 1.2.1, 1.2.0, 1.1.4, 1.1.3, 1.1.2, 1.1.1, 1.1.0
Getting started with F5 VELOS
VELOSplatforms are a modular (chassis and blade) form factor, designed to meet the needs of large enterprise networking environments that require the ability to scale and process a large volume of increasing application workloads.
This guide walks you through getting started with a new installation of a
VELOSplatform, including essential steps like configuring DHCP, network settings, chassis partitions, and tenants. After you complete these procedures, your system will be running a basic configuration that includes a chassis partition and a tenant.
F5OSarchitecture consists of two implementations: F5OS-C (chassis) for
VELOSand F5OS-A (appliance) for
VELOS, be sure to use F5OS-C images. For information about
F5OSsoftware, see K03278510: F5OS-A and F5OS-C software for F5 hardware platforms.
F5strongly recommends that you upgrade to the latest F5OS-C software version after you complete initial configuration. For more information, see
VELOS Systems: Installation and Upgradeon the techdocs.f5.com.
Before you begin, be sure that you have this information:
- Proposed new passwords forVELOSadmin and root accounts
- Proposed static management IP addresses for (if not using DHCP)
- system controllers
- chassis partitions
- Proposed cluster IP addresses for tenants (for more information about this and other best practices, see K15930: Overview of vCMP configuration considerations)
- IP address of DHCP server running in network (if using DHCP)
- IP address of NTP server
- IP address of DNS server
- Tenant base registration key
For additional information on installing and configuring
VELOSsystems, refer to the documentation at techdocs.f5.com.
Chassis installation overview
For detailed information about installing your platform, see the document titled
Setting Up the VELOS CX Series AC and DC Platformsthat is included with the chassis.
At a high level, to install the chassis into your data center, you perform these tasks:
- Rack the chassis using the rack mount kit provided.
- Connect the power cables to the power supply units (PSUs) and apply power to the chassis.
- Insert blades into the chassis, starting at slot 1.
- Ensure the front bezel with LCD is secured to the chassis.
- Connect the serial console cables, management interfaces, and networking cables.
VELOSsystem uses an internal
chassisnetwork for control plane and management plane communication. Traffic on this internal network is firewall-protected and is not exposed to a customer’s management network. The internal network uses a predefined range of IP addresses, using 100.64.0.0/12 addressing, by default.
IP addresses in the predefined range are reserved for internal networking and cannot be used for any of the following:
- Management IP addresses for the system controllers, chassis partitions, and tenants
- Any external service configured on theVELOSsystem, such as a DNS server and NTP server
- Source IP addresses of any device used to communicate with theVELOSsystem (such as a laptop, workstation, or other device that connects)
If your network uses addresses in the predefined range for any of the above, you will not be able to access the
VELOSsystem from the management interfaces (including the CLI, webUI, or RESTCONF APIs). This is only an issue if using 100.64.0.0/12 addresses for management IP addresses, external servers, or source IP addresses described here. This does not affect data plane/in-band interfaces.
To prevent this issue,
F5provides a procedure that enables you to select a different internal IP address range during initial provisioning of a system, as an alternative to using the default range. For more information on how to change the internal network IP address range, see
VELOS Systems: Administration and Configurationat techdocs.f5.com.
VELOS terminology and taxonomy
These are some of the terms and taxonomy that you will encounter when configuring the VELOS system.
The main component of the unit that houses the blades, system controllers, and other components. The chassis can be divided into multiple chassis partitions.
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, and a webUI.
The primary hardware component that handles traffic management including disaggregation, packet classification, and traffic-steering for the
VELOSsystem. Up to eight blades can be installed into the slots on the VELOS CX410. Runs chassis partition software, on which tenants are deployed.
A chassis partition is a grouping of blades that can be isolated from other blades within the same chassis. Each chassis partition is a separate managed system, unlike the tenant system’s administrative partitions within a single managed system. Chassis partitions are commonly use to allow for further isolation than just tenancy between different environments and can include one or more blades. You can manage a chassis partition using a REST API, CLI, and webUI.
A guest system (a virtualized BIG-IP instance similar to a vCMP guest) running software within a chassis partition. You can deploy multiple tenants in one chassis partition. BIG-IP is the F5 TMOS-based tenant, and BIG-IP Next is the next generation, modularized version of the BIG-IP tenant.
chassis terminal service
Built into the system controller software, the chassis terminal service provides a way to access the console for the system controllers and all blades.