update_device_wtp_profile_radio
Update a single radio's channel and/or channel width on a FortiAP profile while preserving existing radio settings by reading the profile first and writing back unchanged fields.
Instructions
Update a single radio's channel and/or channel width on a FortiAP profile.
This is a read-modify-write, like assign_vap_to_wtp_profile: the profile is read first and every other field already on the target radio (band, power, vap-all, vaps, mode, ...) is carried through unchanged, minus a couple of read-only bookkeeping keys the API injects on GET but rejects on write (see _WTP_RADIO_READONLY_KEYS). FortiManager replaces a nested radio object rather than merging into it, so writing back only channel/channel-bonding would reset the rest to defaults on the next install_device_settings.
Args: device: Managed device name profile: FortiAP (WTP) profile name radio: Radio to update, 1-3 channel: Channel(s) to pin the radio to. For radio 1/2 (2.4/5GHz) this is a single-element list, e.g. [36], to pin one channel. For radio 3 (6GHz) at a bonding width above 20MHz, FortiOS represents the wide channel as the full list of its member 20MHz sub-channels rather than a single label -- pass either the single conventional wide-channel label (e.g. [15] for 160MHz channel 15) and it is expanded to the correct member list automatically, or the explicit member list itself (e.g. [1, 5, 9, 13, 17, 21, 25, 29]). channel_bonding: Channel width/bonding, one of WTP_PROFILE_CHANNEL_BONDING_MODES ("20MHz", "40MHz", "80MHz", "160MHz") vdom: VDOM the profile lives in (default "root")
Returns: Update result
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| vdom | No | root | |
| radio | Yes | ||
| device | Yes | ||
| channel | No | ||
| profile | Yes | ||
| channel_bonding | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||