Strict adherence to supported configurations is required to maintain eligibility for Avaya support. Any deviation from these guidelines should be treated as a controlled change.
Support guidelines
Only the VLAN configuration procedures outlined in this document are validated by Avaya.
Use of system tools such as nmcli is permitted only as outlined in this document. Any other tools, commands, or procedures not documented here are, by default, considered unsupported.
Changes to OOBM, bridge0, or existing bonded interfaces via Cockpit are not supported if those components were originally configured using the script.
Change control requirements
Submit a request to Avaya support before applying custom VLAN or bond configurations outside the documented models
Maintain configuration backups and change logs before applying VLAN changes
If unsupported configurations are applied and connectivity is lost, a full re-image of the host may be required
Note:
To confirm whether a specific VLAN topology is supported, customers are advised to contact Avaya technical support prior to implementation.
