AAA/TACACS+ Servers Operations Service
Provides services manage AAA servers used by the appliance.
Resource | Description | API Version |
---|---|---|
DELETE Delete Server
DELETE op/aaa/tacacsPlusServer |
Delete existing TACACS+ server | |
GET List Servers
GET op/aaa/tacacsPlusServer |
Read all TACACS+ servers | |
POST Add Server
POST op/aaa/tacacsPlusServer |
Add new TACACS+ server | |
PUT Update Server
PUT op/aaa/tacacsPlusServer |
Update an existing TACACS+ server. The serverIp attribute must match the existing server to be modified, and cannot be changed. |
CLI Template Configuration
The CLI Template Configuration service allows a CLI configuration template to be applied to one or more target devices. It also provides a way to upload, delete, and get the CLI templates in the system.
Resource | Description | API Version |
---|---|---|
DELETE Delete Configuration Template Folder
DELETE op/cliTemplateConfiguration/folder |
Delete folder | |
GET List Configuration Template Folders
GET op/cliTemplateConfiguration/folder |
Get folders | |
POST Create Configuration Template Folder
POST op/cliTemplateConfiguration/folder |
Create new folder | |
PUT Modify Configuration Template Content
PUT op/cliTemplateConfiguration/template |
Update template. Does not support Converged Access Templates (IOS-XE templates and templates created from them). |
Configuration Archive Service
Provides services for configuration file, diff and versions operations.
Resource | Description | API Version |
---|---|---|
GET Configuration archive list
GET data/ConfigArchives |
Configuration archive for device | |
GET Configuration versions and files list
GET data/ConfigVersions |
Represents information about the version of the configuration files | |
GET Download the sanitized configuration file
GET op/configArchiveService/extractSanitizedFile |
Extract a sanitized configuration file (not applicable for config files with type VLAN and DATABASE) | |
GET Download the unsanitized configuration file
GET op/configArchiveService/extractUnsanitizedFile |
Extract an unsanitized configuration file (not applicable for config files with type VLAN and DATABASE) |
Group Management Service
The Group Management Service provides operations for getting group rules summary, deleting and updating groups, managing devices and rules assigned to groups.
Resource | Description | API Version |
---|---|---|
DELETE Delete device or port group
DELETE op/groups/group |
Delete a device or port group by it's ID or full path and name. Only Location and 'User Defined' Device groups and 'User Defined' port groups are supported. | |
GET Device Group Rules
GET op/groups/groupRules |
Get list of group rules. Only Location and Network Device groups are supported. | |
PUT Assign devices to a group
PUT op/groups/groupDevices |
Statically assign list of devices to a group (devices are listed by device IDs or IP addresses). Only Location and User Defined device groups are supported. | |
PUT Create or update device or port group
PUT op/groups/group |
Create or update a device or port group. Only 'Location' and 'User Defined' Device groups and 'User Defined' port groups are supported. You cannot modify the system defined groups except 'Location/All Locations/System Campus' for which you can change only description and geographical location. | |
PUT Remove devices from a group
PUT op/groups/removeDevices |
Remove list of devices from a group (devices are listed by device IDs or IPs). Only Location and 'User Defined' Device groups are supported. | |
PUT Replace set of group rules
PUT op/groups/groupRules |
Replace set of group rules with a new one. Only Location and Network Device groups are supported. |
Plug and Play
Provides operations related to Plug And Play
Resource | Description | API Version |
---|---|---|
POST Create Update PnP Status
POST op/pnp/status/{serialNumber} |
Trap Receivers
Provides for operations to retrieve, create, modify, and delete Trap Receivers.
Resource | Description | API Version |
---|---|---|
DELETE Delete Trap Receiver
DELETE op/trapReceiverService/receiver |
Deprecated
Notification Receivers API is deprecated because Notification Receivers were replaced by Notification Policies. This resource will not delete receivers which (1) are used by more than one policy or (2) have other receivers associated with the same policy. This resource may be removed in a future release. Deletes an existing northbound trap receiver destination and the associated notification policy.
The API supports only those trap receivers associated with one notification policy. If there is more than one policy mapped to the receiver, or the the policy is associated with any other receiver, then an explicit error will be thrown, and neither the receiver nor the policy will be deleted. |
|
GET List Trap Receivers
GET op/trapReceiverService/list |
Deprecated
Notification Receivers API is deprecated because Notification Receivers were replaced by Notification Policies. This resource will not list receivers which (1) are used by more than one policy or (2) have other receivers associated with the same policy. This resource may be removed in a future release. Retrieves certain existing northbound trap receiver destinations with the associated notification policy.
Notification Policies underwent significant changes in Prime Infrastructure 3.2, therefore the API works with the following restrictions:
|
|
POST Create Trap Receiver
POST op/trapReceiverService/receiver |
Deprecated
Notification Receivers API is deprecated because Notification Receivers were replaced by Notification Policies. This resource may be removed in a future release. Create a new northbound trap receiver destination with an associated notification policy.
Notification Policies underwent significant changes in Prime Infrastructure 3.2, therefore the API works with the following restrictions:
|
|
PUT Update Trap Receiver
PUT op/trapReceiverService/receiver |
Deprecated
Notification Receivers API is deprecated because Notification Receivers were replaced by Notification Policies. This resource will not update receivers which (1) are used by more than one policy or (2) have other receivers associated with the same policy. This resource may be removed in a future release. Updates an existing northbound trap receiver destination and the associated notification policy.
Notification Policies underwent significant changes in Prime Infrastructure 3.2, therefore the API works with the following restrictions:
|