Applies To:Show Versions
- 1.6.1, 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
- 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 tenantsK15930: 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
PlatformChassis installation overview
- 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.
Internal chassisplatform network overview
- Management IP addresses for the system and tenants
- 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)
VELOS terminology and taxonomy
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 VELOS system. The CX410 chassis has eight available blade slots, and the CX1610 chassis has 32 available blade slots. 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.