Administering VELOS (VELOS) – Outline

Detailed Course Outline

Chapter 1: Introducing VELOS

Introducing Major Components

  • CX410 Chassis
  • BX110 Blade
  • Blade Numbering
  • SX410 System Controller
  • System Controller Diagram/Architecture

Introducing Other Components

  • Front Bezel
  • Power Supplies
  • Power Controllers
  • Fan Tray

Key Concepts: Partitions and Tenants

  • Defining Partitions
  • Multiple Single-Blade Partitions Example
  • Multi-Blade Partitions Example
  • Tenants

VELOS Software Management Domains

  • Management Domains
  • System Controller
  • Chassis Partition
  • Tenant
  • F5OS

VELOS Naming Convention

  • CX=VELOS Family Chassis
  • SX=System Controller
  • BX=Blade


  • License requires activation initiated with base registration key
  • Partitions and tenants inherit the license (just like VIPRION)

Lab: View System Controller Settings

  • Access the GUI and explore the Dashboard, System Inventory, Licensing, General
  • Access the CLI and explore the command: show running-config
Chapter 2: Comparing VELOS to VIPRION

How we got here and F5OS architecture

  • Compare cabling, blades, chassis partitions, VLANs & LAGs, tenants & vCMP guests, and bare metal configurations.
  • No lab
Chapter 3: Setting Up VELOS System Controllers

System Controllers

  • Discuss system controllers’ redundancy and high availability.

VELOS Setup Wizard

Chassis Partitions

  • Discuss chassis partitions and how to group blades together.

Lab: Create Chassis Partition

  • Each student creates a 1-blade partition –must do sequentially.

Lab: Create System User Accounts

  • Each student creates an operator to demonstrate read-only access.

Lab: Create System Controller Backup

  • Each student creates a system controller backup.
Chapter 4: Setting Up VELOS Chassis Partitions

Port Groups, VLANs, LAGs, and Interfaces

  • Discuss heterogeneous Port Group Modes, VLANs, LAGs, and interfaces.

Lab: Create Port Groups

  • Each student configures port group in their partition.

Lab: Add VLANs

  • Each student adds VLANs to their partition.

Lab: Create LAGs and View Interfaces

  • Each student creates a LAG and views the interfaces to determine if they are up and operational.

Tenant Image Considerations

  • Discuss Tenant Image types.

Demo: Download BIG-IP Tenant

Lab: Create a BIG-IP Tenant

  • Each student creates a BIG-IP tenant in their partition.

Lab: Modify a BIG-IP Tenant

  • Demonstrates how some fields can be changed “on the fly” while other fields require changing the state which stops tenant processing.

Lab: Create a Partner BIG-IP Tenant for High Availability (HA)

Optional Lab: Create a BIG-IP Tenant via CLI

Optional Lab: Create a BIG-IP Tenant via API

Lab: Partition Backup

  • Each student backs up their partition configuration.
Chapter 5: Managing Tenants

BIG-IP Tenants

  • Confirm student’s knowledge of BIG-IP systems can be applied to BIG-IP tenants.

Lab: Run Setup Utility on a BIG-IP Tenant

  • Each student runs the Setup Utility to activate the tenant.

Lab: Create Traffic Processing Objects

  • Each student creates a pool and virtual server and drives application traffic.

Lab: Create BIG-IP Tenant Backups and Restore

  • Each student creates a tenant backup and restores the backed-up file.
Chapter 6: Configure BIG-IP Tenant High Availability

High Availability (HA) Overview

Lab: Verify System Settings on Primary BIG-IP Tenant

Lab: Activate Partner BIG-IP Tenant

  • Each student runs the Setup Utility on partner system

Lab: Establish an Active Standby Pair of BIG-IP Tenants

  • Each student creates an active standby pair of BIG-IP tenants

Lab: Test Failover

Chapter 7: Basic VELOS Troubleshooting

Troubleshooting Tools and Techniques

  • Read and identify basic LED behavior
  • QKview Introduction
  • Configure and view logging
  • Generate tcpdump output
  • Run basic VELOS system commands

Lab: Generate a Chassis Partition Qkview and Upload to iHealth

  • Perform via the GUI
  • Optionally perform via the CLI

Lab: View VELOS Event Logging

Lab: Generate a tcpdump

  • Generate a system controller tcpdump output
  • Run tcpdump filtering through a single interface
  • Run tcpdump option and send output to a file

Lab: Perform VELOS System Commands