Bug ID 2227509: VELOS tenant reports chassis-type “VIPRION” instead of “velos” after migration from vCMP guest

Last Modified: Feb 23, 2026

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4

Opened: Feb 20, 2026

Severity: 4-Minor

Symptoms

On a tenant deployed on F5 VELOS, the command: tmsh list cm device shows: chassis-type VIPRION The tenant is running on VELOS hardware, but the cm device object reports the chassis-type as “VIPRION”. The chassis-type field is system-generated and not user-configurable.

Impact

Cosmetic / metadata inconsistency only. No observed impact to: HA functionality Device trust or config sync Licensing TMM / data-plane traffic processing

Conditions

-- A BIG-IP tenant deployed on F5 VELOS (F5OS-C). -- Tenant is running version 17.5.1 -- Default tenant deployment (no special configuration required). -- No user modification of the cm device object. The behavior is observed immediately after tenant provisioning and persists across reboots and config loads.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips