Applies To:Show Versions
- 1.1.1, 1.1.0
Getting started with VELOS
- Proposed new passwords for VELOS admin and root accounts
- Proposed management IP addresses for system controllers, partition, and tenant (if not using DHCP)
- IP address of DHCP server running in network (if using DHCP)
- IP address of NTP server
- IP address of DNS server
- BIG-IP base registration key
About chassis installation
- Rack the chassis using the rack mount kit provided.
- 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.
- Connect the power supply and power apply power to the chassis.
About the internal chassis network
- VELOS management IP addresses for the system controllers, chassis partitions, and tenants
- Any external service configured on the VELOS system, such as a DNS server, NTP server, and so on
- Source IP addresses of any device used to communicate with the VELOS system (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 platform. Up to eight blades can be installed into the slots on the chassis.
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, the partition CLI, and a webUI.
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.
chassis terminal service
Built into the system controller software, the chassis terminal service provides a means to access the console for the system controllers and all blades.