cisco.catalystcenter.floors_floor_id_planned_access_point_positions_bulk module -- Resource module for Floors Floor Id Planned Access Point Positions Bulk
Note
This module is part of the cisco.catalystcenter collection (version 2.11.0).
To install it, use: ansible-galaxy collection install cisco.catalystcenter.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: cisco.catalystcenter.floors_floor_id_planned_access_point_positions_bulk.
New in cisco.catalystcenter 2.0.0
Synopsis
Manage operation create of the resource Floors Floor Id Planned Access Point Positions Bulk.
Add Planned Access Points Positions on the map.
Note
This module has a corresponding action plugin.
Requirements
The below requirements are needed on the host that executes this module.
catalystcentersdk >= 3.2.3.0.0
python >= 3.12
Parameters
Parameter |
Comments |
|---|---|
Flag for Cisco Catalyst Center SDK to enable debugging. Choices: |
|
The Cisco Catalyst Center hostname. |
|
The Cisco Catalyst Center password to authenticate. |
|
The Cisco Catalyst Center port. Default: :ansible-option-default:`443` |
|
The Cisco Catalyst Center username to authenticate. Default: :ansible-option-default:`"admin"` |
|
Flag to enable or disable SSL certificate verification. Choices: |
|
Informs the SDK which version of Cisco Catalyst Center to use. Default: :ansible-option-default:`"3.1.6.0"` |
|
FloorId path parameter. Floor Id. |
|
Floors Floor Id Planned Access Point Positions Bulk's payload. |
|
Planned Access Point Id. |
|
Planned Access Point MAC address. |
|
Planned Access Point Name. |
|
Floors Floor Id Planned Access Point Positions Bulk's position. |
|
Access Point X coordinate in feet. |
|
Access Point Y coordinate in feet. |
|
Access Point Z coordinate in feet. |
|
Floors Floor Id Planned Access Point Positions Bulk's radios. |
|
Floors Floor Id Planned Access Point Positions Bulk's antenna. |
|
Angle of the antenna, measured relative to the x axis, clockwise. The azimuth range is from 0 through 360. |
|
Elevation of the antenna. The elevation range is from -180 through 180. For antennas designed to be horizontally mounted, 0° indicates mounted to ceiling pointed straight down to the floor, where 180° indicates mounted on floor (or mounted under a desk) pointed up to the ceiling. Positive elevation angles means AP is tilted in the direction of the configured azimuth, where negative elevation angles means tilted opposite the direction of the configured azimuth. For antennas designed to be vertically mounted (on wall, pole, etc.), 0° means the main lobe is pointed straight out from the wall, where -90° indicates mounted to wall and pointed straight down to the floor, and 90° indicates pointed up to the ceiling. Use `/dna/intent/api/v1/maps/supported-access-points` to find supported antennas for a particular Access Point type. Use `/dna/intent/api/v1/maps/antenna/{antennaName}` to lookup specific details about an antennas default mounting orientation. |
|
Antenna type for this Access Point. Use `/dna/intent/api/v1/maps/supported-access-points` to find supported Antennas for a particular Access Point type. |
|
Radio frequency in GHz. Please note that once set, this field cannot be changed. |
|
Channel to be used by the Access Point. In the context of a Planned Access Point, the channel have no bearing on what the real Access Point will actually be, they are just used for Maps visualization feature set. |
|
Radio Id. |
|
Transmit power for the channel in Decibel milliwatts (dBm). In the context of a Planned Access Point, the txPower have no bearing on what the real Access Point will actually be, they are just used for Maps visualization feature set. |
|
Planned Access Point type. Use `dna/intent/api/v1/maps/supported-access-points` to find the supported types. |
|
Flag for Cisco Catalyst Center SDK to enable the validation of request bodies against a JSON schema. Choices: |
Notes
Note
SDK Method used are site_design.SiteDesign.add_planned_access_points_positions,
Paths used are post /dna/intent/api/v2/floors/{floorId}/plannedAccessPointPositions/bulk,
Does not support
check_modeThe plugin runs on the control node and does not use any ansible connection plugins,
but instead uses the embedded connection manager from Cisco CATALYST SDK
Requires Python >= 3.10, matching the controller Python versions supported by the collection's minimum ansible-core version (see the collection README for the current ansible-core / Python compatibility range)
See Also
See also
- Cisco Catalyst Center documentation for Site Design AddPlannedAccessPointsPositions
Complete reference of the AddPlannedAccessPointsPositions API.
Examples
---
- name: Create
cisco.catalystcenter.floors_floor_id_planned_access_point_positions_bulk:
catalystcenter_host: "{{catalystcenter_host}}"
catalystcenter_username: "{{catalystcenter_username}}"
catalystcenter_password: "{{catalystcenter_password}}"
catalystcenter_verify: "{{catalystcenter_verify}}"
catalystcenter_port: "{{catalystcenter_port}}"
catalystcenter_version: "{{catalystcenter_version}}"
catalystcenter_debug: "{{catalystcenter_debug}}"
floorId: string
payload:
- id: string
macAddress: string
name: string
position:
x: 0
y: 0
z: 0
radios:
- antenna:
azimuth: 0
elevation: 0
name: string
bands:
- 0
channel: 0
id: string
txPower: 0
type: string
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
A dictionary or list with the response returned by the Cisco Catalyst Center Python SDK Returned: always Sample: :ansible-rv-sample-value:`{"response": {"taskId": "string", "url": "string"}, "version": "string"}` |