Table Of Contents
ANM Web Services API
Mapping Table
OperationManager Web Service APIs
login
logout
listDeviceids
listVirtualContexts
listVirtualServers
listServerFarms
listRservers
listServerfarmRservers
listAnswers
listDnsRules
activateVirtualServer
suspendVirtualServer
addRserverToServerfarm
removeRserverFromServerfarm
activateServerfarmRserver
suspendServerfarmRserver
changeServerfarmRserverWeight
activateAnswer
suspendAnswer
activateDnsRule
suspendDnsRule
getVMMappingInfo
ApplicationTemplateManager Web Service APIs
listTemplateDefinitions
getTemplateDefinitionMetadata
createTemplateInstance
listTemplateInstances
deleteTemplateInstance
listCheckpoints
createCheckpoint
deleteCheckpoint
rollbackCheckpoint
freeFormShow
ANM Web Services API
This chapter describes the ANM Web Services APIs, which allows you to manage the Cisco Application Control Engine (ACE) module, Cisco Application Control Engine (ACE) appliance, Cisco Content Services Switch (CSS) and Cisco Content Switching Module (CSM), Cisco Content Switching Module with SSL (CSM-S), and Cisco Global Site Selector (GSS) using ANM. ANM Web Services provide APIs to support configuration functionalities. All APIs are implemented as synchronous calls and each call is a transaction.
This chapter contains the mapping table and describes the following ANM APIs:
•
Mapping Table
•
OperationManager Web Service APIs
•
ApplicationTemplateManager Web Service APIs
Mapping Table
Table 2-1 displays the mapping of each API with the specified role and the domain, where
•
F = Full access
•
N = No access
OperationManager Web Service APIs
This section describes the APIs associated with the OperationManager Web Service, which are as follows:
•
login
•
logout
•
listDeviceids
•
listVirtualContexts
•
listVirtualServers
•
listServerFarms
•
listRservers
•
listServerfarmRservers
•
listAnswers
•
listDnsRules
•
activateVirtualServer
•
suspendVirtualServer
•
addRserverToServerfarm
•
removeRserverFromServerfarm
•
activateServerfarmRserver
•
suspendServerfarmRserver
•
changeServerfarmRserverWeight
•
activateAnswer
•
suspendAnswer
•
activateDnsRule
•
suspendDnsRule
•
getVMMappingInfo
login
This request logs in an application user to ANM. The login API validates the credentials and returns a session token. The session times out after being idle for 30 minutes even if the logout is not called.By default, ANM allows 10 concurrent API logins, but you can modify this number (see the "Modifying the Number of Concurrent Sessions Allowed" section).
Input Parameters
Parameter
|
Description
|
Username
|
Username of the application user.
|
Password
|
Password of the application user.
|
Output Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
Exceptions
Type
|
Exception String
|
String
|
Maximum session limit configured_limit reached for WS.
Note The default is 10 (see the "Modifying the Number of Concurrent Sessions Allowed" section).
|
String
|
Invalid username or password. Please try again.
|
String
|
Session ID is in use. Please try again later.
|
String
|
Username cannot be null.
|
String
|
Password cannot be null.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the login action. The input parameters for this particular action are username and password.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<password xmlns="">admin</password>
Example Response
The following example shows the XML response:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
xmlns:ns2="http://anm.cisco.com">
<sid>5546099606143734326</sid>
</S:Envelope>
logout
This request logs out an application user from the ANM. The session times out after being idle for 30 minutes even if the logout is not called. In case of a session timeout, the following exception string is generated: Invalid Session Id.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid Session ID.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the logout action. Session token is the input parameter for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>-6055365969690519291</sid>
Example Response
The following example shows the XML response that contains no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:logoutResponse xmlns:ns2="http://anm.cisco.com"/>
listDeviceids
This request lists all device IDs for a device type from the ANM inventory. If none of the devices is imported in ANM, it returns an empty list.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceType
|
List of device types including the device name and status. For example, CSS, CSM, CAT6K, GSS, VIRTUAL_CONTEXT, ACE4710, and ACE_BLADE.
|
Output Parameters
Parameter
|
Description
|
DeviceIDs
|
List of device IDs including the device name, device type, IP address, slot, and chassis IP address attributes.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid Session ID.
|
String
|
Unsupported Device Type: device_type.
|
String
|
Device Type should not be null.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the listDeviceids action. SessionToken and DeviceType are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>-81548021995146358</sid>
<deviceType xmlns="">VIRTUAL_CONTEXT</deviceType>
Example Response
The following example shows the XML response that contains DeviceID as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listDeviceIdsResponse
xmlns:ns2="http://anm.cisco.com">
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
</ns2:listDeviceIdsResponse>
listVirtualContexts
This request lists all the virtual contexts for an Application Control Engine (ACE) module or ACE appliance from the ANM inventory.
This API is supported only on ACE modules and appliances (device type: ACE_BLADE and ACE4710).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
ACE module: Device ID includes the device type, slot, and chassis IP address attributes.
ACE appliance: Device ID includes the device type, IP address, and name attributes.
|
Output Parameters
Parameter
|
Description
|
DeviceIDs
|
List of virtual context device IDs including the device type, IP address, slot, and chassis IP address attributes.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid Session ID.
|
String
|
Given ACE module is not yet imported in ANM.
|
String
|
Given ACE Appliance does not exist in ANM.
|
String
|
None of the devices are imported.
|
String
|
Unsupported Device Type: device_type.
|
String
|
Given ACE module does not exist in the chassis: Chassis_IPaddress.
|
String
|
Device Type should be not null.
|
String
|
"chassisIPAddr" and "ipAddr" are not added in deviceID. Either should be provided.
|
String
|
Both "chassisIPAddr" and "ipAddr" are added in deviceID. Only one of them can be added.
|
String
|
DeviceID should not be not null.
|
String
|
DeviceType is set as ACE_BLADE, but the mandatory field "slot" is set as null or empty.
|
String
|
DeviceType is set as ACE4710, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
Invalid IP Address: IPaddress.
|
String
|
DeviceType is set as ACE_BLADE, but the mandatory field "slot" is set as null or empty.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the listVirtualContexts action. SessionToken and DeviceID are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>-81548021995146358</sid>
<deviceType>ACE_BLADE</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
Example Response
The following example shows the XML response that contains the list of virtual context DeviceIDs as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listVirtualContextsResponse
xmlns:ns2="http://anm.cisco.com">
<deviceType>VIRTUAL_CONTEXT</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
</ns2:listVirtualContextsResponse>
listVirtualServers
This request lists all the virtual servers configured on the specified device. The device can be a CSS, CSM, or a virtual context (VIRTUAL_CONTEXT) on an ACE module or ACE appliance.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
Virtual context DeviceID, which contains the virtual server name, device type, IP address, chassis slot, and chassis IP address attributes.
|
allVSs
|
(Optional) Input parameter that instructs ANM to return a list of all virtual servers that match ANM's virtual server definition and those that do not match this definition but that ANM can recognize as virtual servers using SNMP polling. By default, ANM returns only the virtual servers that match ANM's virtual server definition.
|
Output Parameters
Parameter
|
Description
|
vservers
|
List of all virtual servers including the virtual server name, policy-map name, and IP address attributes.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid Session ID.
|
String
|
Maximum session limit configured_limit reached for WS.
Note The default is 10 (see the "Modifying the Number of Concurrent Sessions Allowed" section).
|
String
|
Given ACE module is not yet imported in ANM.
|
String
|
Given ACE Appliance does not exist in ANM.
|
String
|
None of the devices are imported.
|
String
|
Unsupported Device Type: device_type.
|
String
|
Given ACE module does not exist in the chassis: Chassis_IPaddress.
|
String
|
Device Type should be not null.
|
String
|
"chassisIPAddr" and "ipAddr" are not added in deviceID. Either should be provided.
|
String
|
Both "chassisIPAddr" and "ipAddr" are added in deviceID. Only one of them can be added.
|
String
|
DeviceID should not be not null.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "slot" is set as null or empty.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "name" is set as null or empty.
|
String
|
Invalid IP Address: IPaddress.
|
String
|
Given virtual context name "[VC name]" does not exist in the ACE Devices.
|
String
|
DeviceType is set as CSS, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
DeviceType is set as VIRTUAL_CONTEXT, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
Device Type is set as CSM, but the mandatory field "chassisIPAddr" is set as null or empty.
|
String
|
Device Type is set as CSM, but the mandatory field "slot" is set as null or empty.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the listVirtualServers action. SessionToken, DeviceID, and allVSs are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>7299761084673772498</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
<allVS xmlns="">false</allVS>
Example Response
The following example shows the XML response that contains the list of virtual servers as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listVirtualServersResponse
xmlns:ns2="http://anm.cisco.com">
<listVirtualServers xmlns="">
<virtualserverName>14_simple_vs</virtualserverName>
<policyMapName>int2</policyMapName>
<ipAddress>15.5.3.2</ipAddress>
<serverfarms>14_simple_sf</serverfarms>
<adminState>DOWN</adminState>
<operState>DOWN</operState>
<lastPolledTime>Fri May 27 16:52:31 IST 2011</lastPolledTime>
<virtualserverName>ds_simple_vs</virtualserverName>
<policyMapName>int161</policyMapName>
<ipAddress>13.3.3.3</ipAddress>
<serverfarms>ds_simple_sf</serverfarms>
<adminState>DOWN</adminState>
<operState>DOWN</operState>
<lastPolledTime>Fri May 27 16:52:31 IST 2011</lastPolledTime>
<virtualserverName>test</virtualserverName>
<policyMapName>global</policyMapName>
<ipAddress>4.5.6.7</ipAddress>
<serverfarms>gh</serverfarms>
<adminState>UP</adminState>
<operState>DOWN</operState>
<lastPolledTime>Fri May 27 16:52:31 IST 2011</lastPolledTime>
</ns2:listVirtualServersResponse>
listServerFarms
This request lists all server farms on a virtual context from the ANM inventory. This API is supported only on ACE devices (device type: VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
Virtual context device ID including the device name, device type, IP address, slot, and chassis IP address attributes.
|
Output Parameters
Parameter
|
Description
|
Serverfarms
|
List of server farm objects including the name and type (host or redirect) attributes.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid Session ID.
|
String
|
Maximum session limit [configured_limit] reached for WS.
The default is 10 (see the "Modifying the Number of Concurrent Sessions Allowed" section).
|
String
|
Given ACE module is not yet imported in ANM.
|
String
|
Given ACE Appliance does not exist in ANM.
|
String
|
None of the devices are imported.
|
String
|
Unsupported Device Type: device_type.
|
String
|
Given ACE module does not exist in the chassis: Chassis_IPaddress
|
String
|
Device Type should be not null.
|
String
|
"chassisIPAddr" and "ipAddr" are not added in deviceID. Either should be provided.
|
String
|
Both "chassisIPAddr" and "ipAddr" are added in deviceID. Only one of them can be added.
|
String
|
DeviceID should not be not null.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "slot" is set as null or empty.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "name" is set as null or empty.
|
String
|
Invalid IP Address: IPaddress.
|
String
|
Given virtual context name VC_name does not exist in the ACE Devices.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the listServerFarms action. SessionToken and DeviceID are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>8368662778638735743</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
Example Response
The following example shows the XML response that contains the list of Serverfarm objects as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listServerFarmsResponse
xmlns:ns2="http://anm.cisco.com">
<serverFarmType>host</serverFarmType>
<serverFarmType>host</serverFarmType>
</ns2:listServerFarmsResponse>
listRservers
This request lists all the real servers on a virtual context from the ANM inventory. This API is supported only on ACE devices (device type: VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
Virtual context device ID including the device name, device type, IP address, slot, and chassis IP address attributes.
|
Output Parameters
Parameter
|
Description
|
Rservers
|
List of real server objects including the name, IP address, admin state, and weight attributes.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid Session ID.
|
String
|
Maximum session limit configured_limit reached for WS.
The default is 10 (see the "Modifying the Number of Concurrent Sessions Allowed" section).
|
String
|
Given ACE module is not yet imported in ANM.
|
String
|
Given ACE appliance does not exist in ANM.
|
String
|
None of the devices are imported.
|
String
|
Unsupported Device Type: device_type.
|
String
|
Given ACE module does not exist in the chassis: Chassis_IPaddress.
|
String
|
Device Type should be not null.
|
String
|
"chassisIPAddr" and "ipAddr" are not added in deviceID. Either should be provided.
|
String
|
Both "chassisIPAddr" and "ipAddr" are added in deviceID. Only one of them can be added.
|
String
|
DeviceID should not be not null.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "slot" is set as null or empty.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "name" is set as null or empty.
|
String
|
Invalid IP Address: IPaddress.
|
String
|
Given virtual context name VC_name does not exist in the ACE devices.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the listRservers action. SessionToken and DeviceID are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>8368662778638735743</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
Example Response
The following example shows the XML response that contains the list of real server objects as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listRserversResponse
xmlns:ns2="http://anm.cisco.com">
</ns2:listRserversResponse>
listServerfarmRservers
This request lists all the real servers present in the given server farm from the ANM inventory. If the server farm name is provided as empty or null in the input parameters, it lists all the real server objects in the given virtual context. This API is supported on CSS, CSM, and ACE devices (device type: CSS, CSM, and VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
Device ID of the virtual context including the device name, device type, IP address, slot and chassis IP address attributes.
|
Serverfarmname
|
Name of an existing server farm. It can be empty, null, or a specific server farm configured in the device.
|
Output Parameters
Parameter
|
Description
|
SfRservers
|
List of server farm real server objects including server farm name, server farm real server name, IP address, admin state, weight, and port value attributes.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Maximum session limit configured_limit reached for WS.
The default is 10 (see the "Modifying the Number of Concurrent Sessions Allowed" section).
|
String
|
Given ACE module is not yet imported in ANM.
|
String
|
Given ACE appliance does not exist in ANM.
|
String
|
None of the devices are imported.
|
String
|
Unsupported Device Type: device_type.
|
String
|
Given ACE module does not exist in the chassis: Chassis_IPaddress.
|
String
|
Device Type should be not null.
|
String
|
"chassisIPAddr" and "ipAddr" are not added in deviceID. Either should be provided.
|
String
|
Both "chassisIPAddr" and "ipAddr" are added in deviceID. Only one of them can be added.
|
String
|
DeviceID should not be not null.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "slot" is set as null or empty.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "name" is set as null or empty.
|
String
|
Invalid IP Address: IPaddress.
|
String
|
Given virtual context name VC_name does not exist in the ACE Devices.
|
String
|
DeviceType is set as CSS, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
DeviceType is set as VIRTUAL_CONTEXT, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
Device Type is set as CSM, but the mandatory field "chassisIPAddr" is set as null or empty.
|
String
|
Device Type is set as CSM, but the mandatory field "slot" is set as null or empty.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the listServerfarmRservers action. SessionToken, DeviceID, and Serverfarmname are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>-2221649013806878130</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
<serverfarmname xmlns="">SF1</serverfarmname>
</listServerfarmRservers>
Example Response
The following example shows the XML response that contains SfRserver as the output parameter:
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listServerfarmRserversResponse
xmlns:ns2="http://anm.cisco.com">
<serverfarmName>SF1</serverfarmName>
<realserverName>04122009sanitytesting</realserverName>
<adminState>IS</adminState>
<operationState>UP</operationState>
<lastPolledTime>Wed Jun 08 20:53:18 IST 2011</lastPolledTime>
<serverfarmName>1</serverfarmName>
<realserverName>anm-vm-118</realserverName>
<adminState>IS</adminState>
<serverfarmName>SF1</serverfarmName>
<realserverName>test</realserverName>
<adminState>OOS</adminState>
<operationState>UP</operationState>
<ipAddr>10.2.1.11</ipAddr>
<lastPolledTime>Wed Jun 08 20:53:18 IST 2011</lastPolledTime>
</ns2:listServerfarmRserversResponse>
listAnswers
This request lists all the VIP answers configured on the specified given GSS.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
GSS device ID, which contains the GSS name, device type, and IP address attributes.
|
Output Parameters
Parameter
|
Description
|
answers
|
List of answer objects, including the answer name, IP address, configuration state, and type attributes. The type attribute is always "vip."
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session token.
|
String
|
GSS does not exist.
|
String
|
Session timeout.
|
String
|
Cannot reach the GSS.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the listAnswers action. SessionToken and DeviceID are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>7299761084673772498</sid>
<deviceType>GSS</deviceType>
<ipAddr>172.23.244.135</ipAddr>
Example Response
The following example shows the XML response that contains answers as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
xmlns:ns2="http://anm.cisco.com">
<ipAddr>10.10.9.99</ipAddr>
<answerName>vip2131</answerName>
<configState>ACTIVATE</configState>
<anserGroups>vipgrp1066</anserGroups>
<location>null</location>
<operState>ACTIVE</operState>
<pGssmTime>17:50:19</pGssmTime>
</ns2:listAnswersResponse>
listDnsRules
This request lists all the DNS rules configured on the specified given GSS.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
GSS device ID, which contains the GSS name, device type, and IP address attributes.
|
Output Parameters
Parameter
|
Description
|
dnsRules
|
List of DNS rule objects, including the DNS rule name, source IP address, owner, and configuration state attributes.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session token.
|
String
|
GSS does not exist.
|
String
|
Session timeout.
|
String
|
Cannot reach the GSS.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the listDnsRules action. SessionToken and DeviceID are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>6600024266770332702</sid>
<deviceType>GSS</deviceType>
<ipAddr>10.77.241.40</ipAddr>
Example Response
The following example shows the XML response that contains dnsRules as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listDnsRulesResponse
xmlns:ns2="http://anm.cisco.com">
<dnsRuleName>dns1</dnsRuleName>
<sourceAddress>Anywhere</sourceAddress>
<dnsConfigState>Active</dnsConfigState>
<answerGroups>null</answerGroups>
</ns2:listDnsRulesResponse>
activateVirtualServer
This request activates an existing virtual server, putting it into service. This API is supported on CSS, CSM, and virtual contexts (VIRTUAL_CONTEXT) on ACE modules and appliances.
Note
For CSS and CSM devices, after changing the state, SNMP polling is triggered. The API does not return until the polling is complete.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
Virtual server device ID, including the device name, device type, IP address, slot, and chassis IP address attributes.
|
vServer
|
Virtual server object, including the virtual server name, policy-map name, and IP address attributes.
|
Reason
|
Reason for the activation.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session token.
|
String
|
Virtual context does not exist.
|
String
|
Session timeout.
|
String
|
Cannot reach the virtual context.
|
String
|
Virtual server does not exist.
|
String
|
Config errors from the ACE, CSS, or CSM.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the activateVirtualServer action. SessionToken, DeviceID, and virtualServer (vip1) are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>2713248117084982682</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
<virtualserverName>12_simple_vs</virtualserverName>
<policyMapName>NAT_Policy</policyMapName>
<reason xmlns="">testing</reason>
Example Response
The following example shows the XML response that contains no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:activateVirtualServerResponse xmlns:ns2="http://anm.cisco.com"/>
suspendVirtualServer
This request suspends an existing virtual server, putting it out of service. This API is supported on CSS, CSM, and virtual contexts (VIRTUAL_CONTEXT) on ACE modules and appliances.
Note
For CSS and CSM devices, after changing the state, SNMP polling is triggered. The API does not return until the polling is complete.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
Virtual server device ID, including the device name, device type, IP address, slot, and chassis IP address attributes.
|
vServer
|
Virtual server object, including the virtual server name, policy-map name, and IP address attributes.
|
Reason
|
Reason for the activation.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session token.
|
String
|
Virtual context does not exist.
|
String
|
Session timeout.
|
String
|
Cannot reach the virtual context.
|
String
|
Virtual server does not exist.
|
String
|
Config errors from the ACE, CSS, or CSM.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the suspendVirtualServer action. SessionToken, DeviceID, and virtualServer (vip1) are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>2713248117084982688</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
<virtualserverName>12_simple_vs</virtualserverName>
<policyMapName>NAT_Policy</policyMapName>
<reason xmlns="">test</reason>
Example Response
The following example shows the XML response that contains no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:suspendVirtualServerResponse xmlns:ns2="http://anm.cisco.com"/>
addRserverToServerfarm
This request adds a real server to an existing server farm. If it does not find the real server, it creates a real server and adds it to the server farm. This API is supported on ACE devices (device type: `VIRTUAL_CONTEXT').
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
Device ID of the virtual context including the device name, device type, IP address, slot and chassis IP address attributes.
|
Rserver
|
Real server object including name, IP address, admin state, and weight attributes.
|
Port
|
Port of the server farm real server.
|
Serverfarm
|
Name of an existing server farm.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid Session ID.
|
String
|
Given ACE module is not yet imported in ANM.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "slot" is set as null or empty.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "name" is set as null or empty.
|
String
|
Invalid IP Address: IPaddress.
|
String
|
Given virtual context name VC_name does not exist in the ACE Devices.
|
String
|
Given ACE Appliance does not exist in ANM.
|
String
|
None of the devices are imported.
|
String
|
Unsupported Device Type: device_type.
|
String
|
Given ACE module does not exist in the chassis: Chassis_IPaddress.
|
String
|
Device Type should be not null.
|
String
|
"chassisIPAddr" and "ipAddr" are not added in device ID. Either should be provided.
|
String
|
Both "chassisIPAddr" and "ipAddr'" are added in device ID. Only one of them can be added.
|
String
|
DeviceID should not be not null.
|
String
|
DeviceType is set as VIRTUAL_CONTEXT, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
Given Server Farm "ServerFarmname" is not available in the given Virtual Context.
|
String
|
Server Farm name should not be null or empty.
|
String
|
Maximum session limit configured_limit reached for WS.
The default is 10 (see the "Modifying the Number of Concurrent Sessions Allowed" section).
|
String
|
Given Name: ServerFarm_name exceeds the maximum length of 64 characters.
|
String
|
Invalid Port: port_number. Port number should be numeric.
|
String
|
Invalid port value: port_number. Port value is outside the range <0-65535>.
|
String
|
Invalid weight value: weight_value. Weight value should be numeric.
|
String
|
Invalid weight value: weight_value. Weight value is outside the range <0-100>.
|
String
|
Invalid Name: ServerFarm_name. Name should match the format [^a-zA-Z0-9._-].
|
String
|
Invalid Name: RealServer_name. Name should match the format [^a-zA-Z0-9._-].
|
String
|
Invalid Name: ServerFarm_name. Name should not hold any reserved keywords.
|
String
|
Invalid Name: RealServer_name. Name should not hold any reserved keywords.
|
String
|
IP address must be provided for the Real Server.
|
String
|
Given Real Server type "Real Server Type" is not associated with Server Farm type "Server Farm type."
|
String
|
Real Server "Real Server Name/ Port value" already exist in the Server Farm ServerFarm_name.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the addRserverToServerfarm action. SessionToken, DeviceID, Rserver, Port, and Serverfarm are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>5731694438459731003</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
xmlns="">SF1</serverfarmname>
<ipAddr>2.3.6.53</ipAddr>
</addRserverToServerfarm>
Example Response
The following example shows the XML response that has no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:addRserverToServerfarmResponse xmlns:ns2="http://anm.cisco.com"/>
removeRserverFromServerfarm
This request removes an existing server farm real server from a server farm. It removes the real server, if there is no server farm real server reference to the real server. This API is supported on ACE devices (device type: VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
Virtual context device ID including the device name, device type, IP address, slot, and chassis IP address attributes.
|
SfRserver
|
Server farm real server object including the server farm name, real server name, IP address, admin state, weight, and port attributes.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid Session ID.
|
String
|
Maximum session limit configured_limit reached for WS.
The default is 10 (see the "Modifying the Number of Concurrent Sessions Allowed" section).
|
String
|
Given ACE module is not yet imported in ANM.
|
String
|
Given ACE Appliance does not exist in ANM.
|
String
|
None of the devices are imported.
|
String
|
Unsupported Device Type: device_type.
|
String
|
Given ACE module does not exist in the chassis: Chassis_IPaddress.
|
String
|
Device Type should be not null.
|
String
|
"chassisIPAddr" and "ipAddr" are not added in deviceID. Either should be provided.
|
String
|
Both "chassisIPAddr" and "ipAddr" are added in deviceID. Only one of them can be added.
|
String
|
DeviceID should not be not null.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "slot" is set as null or empty.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "name" is set as null or empty.
|
String
|
Invalid IP Address: IPaddress.
|
String
|
Given virtual context name VC_name does not exist in the ACE Devices.
|
String
|
DeviceType is set as VIRTUAL_CONTEXT, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
Given Server Farm ServerFarm_name is not available in the given Virtual Context.
|
String
|
Server Farm name should not be null or empty.
|
String
|
Given Name : ServerFarm_name exceeds the maximum length of 64 characters.
|
String
|
Invalid Port: port_number. Port number should be numeric.
|
String
|
Invalid port value: port_number. Port value is outside the range <0-65535>.
|
String
|
Invalid weight value: weight_value. Weight value should be numeric.
|
String
|
Invalid weight value: weight_value. Weight value is outside the range <0-100>.
|
String
|
Invalid Name: ServerFarm_name. Name should match the format [^a-zA-Z0-9._-].
|
String
|
Invalid Name: RealServer_name. Name should match the format [^a-zA-Z0-9._-].
|
String
|
Invalid Name: ServerFarm_name. Name should not hold any reserved keywords.
|
String
|
Invalid Name: RealServer_name. Name should not hold any reserved keywords.
|
String
|
Given Server Farm ServerFarm_name is not available in the given Virtual Context.
|
String
|
Given Real Server RealServer_name/ port_number does not exist in the Server Farm ServerFarm_name.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the removeRserverFromServerfarm action. SessionToken, DeviceID, and SfRserver are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<removeRserverFromServerfarm
xmlns="http://anm.cisco.com">
<sid>-81548021995146358</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
<serverfarmName>SF1</serverfarmName>
<realserverName>sampletest</realserverName>
<adminState>IS</adminState>
<ipAddr>2.3.6.53</ipAddr>
</removeRserverFromServerfarm>
Example Response
The following example shows the XML response that has no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:removeRserverFromServerfarmResponse xmlns:ns2="http://anm.cisco.com"/>
activateServerfarmRserver
This request activates an existing server farm real server in service. This API is supported on CSS, CSM, and ACE devices (device type: CSS, CSM and VIRTUAL_CONTEXT).
Note
For CSS and CSM devices, after changing the state, SNMP polling is triggered. The API does not return until the polling is complete.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
Virtual context device ID including the device name, device type, IP address, slot, and chassis IP address attributes.
|
SfRserver
|
Server farm real server object including the server farm name, real server name, IP address, admin state, weight and port attributes
|
Reason
|
Reason for the activation.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid Session ID.
|
String
|
Server Farm name cannot be null.
|
String
|
Maximum session limit [configured_limit] reached for WS.
The default is 10 (see the "Modifying the Number of Concurrent Sessions Allowed" section).
|
String
|
Given Server farm Real Server name cannot be null.
|
String
|
Given Real Server state cannot be null.
|
String
|
Given Real server weight cannot be null.
|
String
|
Server Farm Real server port value should not be null.
|
String
|
Given ACE module is not yet imported in ANM.
|
String
|
Given ACE Appliance does not exist in ANM.
|
String
|
Given Cat6k does not exist in ANM.
|
String
|
Given ACE module does not exist in the chassis: Chassis_IPaddress.
|
String
|
Given CSM does not exist in the chassis: Chassis_IPaddress.
|
String
|
Given CSS does not exist in ANM.
|
String
|
None of the devices are imported.
|
String
|
Unsupported Device Type: device_type.
|
String
|
Device Type should be null.
|
String
|
"chassisIPAddr" and "ipAddr" are not added in deviceID. Either should be provided.
|
String
|
Both "chassisIPAddr" and "ipAddr" are added in deviceID. Only one of them can be added.
|
String
|
DeviceID should not be null.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "slot" is set as null or empty.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "name" is set as null or empty.
|
String
|
Invalid IP Address: "IP address."
|
String
|
DeviceType is set as CSS, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
DeviceType is set as VIRTUAL_CONTEXT, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
Device Type is set as CSM, but the mandatory field "chassisIPAddr" is set as null or empty.
|
String
|
Device Type is set as CSM, but the mandatory field "slot" is set as null or empty.
|
String
|
Given Server Farm ServerFarm_name is not available in the given Virtual Context.
|
String
|
Given Name: ServerFarm_name exceeds the maximum length of 64 characters.
|
String
|
Given Name:ServerFarm_name exceeds the maximum length of 15 characters.
|
String
|
Given Name: ServerFarm_name exceeds the maximum length of 31 characters.
|
String
|
Invalid Port: port_number. Port number should be numeric.
|
String
|
Invalid port value: port_number. Port value is outside the range <0-65535>.
|
String
|
Given Real Server RealServer_name/port_number does not exist in the Server Farm ServerFarm_name.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the activateServerfarmRserver action. SessionToken, DeviceID, SfRserver, and Reason are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<activateServerfarmRserver
xmlns="http://anm.cisco.com">
<sid>-5217915770163489503</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
<serverfarmName>SF1</serverfarmName>
<realserverName>test</realserverName>
<adminState>OOS</adminState>
<ipAddr>10.2.1.11</ipAddr>
<reason xmlns="">sample Webservices testing</reason>
</activateServerfarmRserver>
Example Response
The following example shows the XML response that has no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:activateServerfarmRserverResponse xmlns:ns2="http://anm.cisco.com"/>
suspendServerfarmRserver
This request suspends the existing server farm real server. This API is supported on CSS, CSM, and ACE devices (device type: CSS, CSM and VIRTUAL_CONTEXT).
Note
For CSS and CSM devices, after changing the state, SNMP polling is triggered. The API does not return until the polling is complete.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
Virtual context device ID including the device name, device type, IP address, slot, and chassis IP address attributes.
|
SfRserver
|
Server farm real server object including the server farm name, real server name, IP address, admin state, weight and port attributes
|
State
|
List of options supported are Graceful, Suspend, Suspend_Clear_Connections.
|
Reason
|
Reason for suspension.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid Session ID.
|
String
|
Server Farm name cannot be null.
|
String
|
Given Server farm Real Server name cannot be null.
|
String
|
Maximum session limit configured_limit reached for WS.
The default is 10 (see the "Modifying the Number of Concurrent Sessions Allowed" section).
|
String
|
Given Real Server state cannot be null.
|
String
|
Given Real server weight cannot be null.
|
String
|
Server Farm Real server port value should not be null.
|
String
|
Given ACE module is not yet imported in ANM.
|
String
|
Given ACE Appliance does not exist in ANM.
|
String
|
Given Cat6k does not exist in ANM.
|
String
|
Given ACE module does not exist in the chassis: Chassis_IPaddress.
|
String
|
Given CSM does not exist in the chassis: Chassis_IPaddress.
|
String
|
Given CSS does not exist in ANM.
|
String
|
None of the devices are imported.
|
String
|
Unsupported Device Type: device_type.
|
String
|
Device Type should be null.
|
String
|
"chassisIPAddr" and "ipAddr" are not added in deviceID. Either should be provided.
|
String
|
Both "chassisIPAddr" and "ipAddr" are added in deviceID. Only one of them can be added.
|
String
|
DeviceID should not be null.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "slot" is set as null or empty.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "name" is set as null or empty.
|
String
|
Invalid IP Address: IPaddress.
|
String
|
DeviceType is set as CSS, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
DeviceType is set as VIRTUAL_CONTEXT, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
Device Type is set as CSM, but the mandatory field "chassisIPAddr" is set as null or empty.
|
String
|
Device Type is set as CSM, but the mandatory field "slot" is set as null or empty.
|
String
|
Given Server Farm ServerFarm_name is not available in the given Virtual Context.
|
String
|
Given Name: ServerFarm_name exceeds the maximum length of 64 characters.
|
String
|
Given Name: ServerFarm_name exceeds the maximum length of 15 characters.
|
String
|
Given Name: ServerFarm_name exceeds the maximum length of 31 characters.
|
String
|
Invalid Port: port_number. Port number should be numeric.
|
String
|
Invalid port value: port_number. Port value is outside the range <0-65535>.
|
String
|
Given Real Server RealServer_name/port_number does not exist in the Server Farm ServerFarm_name.
|
String
|
Invalid suspend state: suspend_state.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the suspendServerfarmRserver action. SessionToken, DeviceID, SfRserver, Reason, and State are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<suspendServerfarmRserver
xmlns="http://anm.cisco.com">
<sid>2658073681808034239</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
<serverfarmName>SF1</serverfarmName>
<realserverName>test</realserverName>
<adminState>IS</adminState>
<ipAddr>10.2.1.11</ipAddr>
xmlns="">Suspend</suspendState>
</suspendServerfarmRserver>
Example Response
The following example shows the XML response that has no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:suspendServerfarmRserverResponse xmlns:ns2="http://anm.cisco.com"/>
changeServerfarmRserverWeight
This request changes the weight of an existing server farm real server. This API is supported on CSS, CSM, and ACE devices (device type: CSS, CSM, and VIRTUAL_CONTEXT).
Note
For CSS & CSM devices, after changing the weight, SNMP polling is triggered. The API does not return until the polling is complete.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
Virtual context device ID including the device name, device type, IP address, slot, and chassis IP address attributes.
|
SfRserver
|
Server farm real server object including the server farm name, real server name, IP address, admin state, weight and port attributes.
|
Reason
|
Reason for the operation.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid Session ID.
|
String
|
Server Farm name cannot be null.
|
String
|
Maximum session limit configured_limit reached for WS.
The default is 10 (see the "Modifying the Number of Concurrent Sessions Allowed" section).
|
String
|
Given Server farm Real Server name cannot be null.
|
String
|
Given Real Server state cannot be null.
|
String
|
Given Real server weight cannot be null.
|
String
|
Server Farm Real server port value should not be null.
|
String
|
Given ACE module is not yet imported in ANM.
|
String
|
Given ACE Appliance does not exist in ANM.
|
String
|
Given Cat6k does not exist in ANM.
|
String
|
Given ACE module does not exist in the chassis: Chassis_IPaddress.
|
String
|
Given CSM does not exist in the chassis: Chassis_IPaddress.
|
String
|
Given CSS does not exist in ANM.
|
String
|
None of the devices are imported.
|
String
|
Unsupported Device Type: device_type.
|
String
|
Device Type should be null.
|
String
|
"chassisIPAddr" and "ipAddr" are not added in deviceID. Either should be provided.
|
String
|
Both "chassisIPAddr" and "ipAddr" are added in deviceID. Only one of them can be added.
|
String
|
DeviceID should not be null.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "slot" is set as null or empty.
|
String
|
DeviceType is set as VIRTUALCONTEXT, but the mandatory field "name" is set as null or empty.
|
String
|
Invalid IP Address: "Ip address."
|
String
|
DeviceType is set as CSS, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
DeviceType is set as VIRTUAL_CONTEXT, but the mandatory field "ipAddr" is set as null or empty.
|
String
|
Device Type is set as CSM, but the mandatory field "chassisIPAddr" is set as null or empty.
|
String
|
Device Type is set as CSM, but the mandatory field "slot" is set as null or empty.
|
String
|
Given Server Farm ServerFarm_name is not available in the given Virtual Context.
|
String
|
Given Name: ServerFarm_name exceeds the maximum length of 64 characters.
|
String
|
Given Name: ServerFarm_name exceeds the maximum length of 15 characters
|
String
|
Given Name : ServerFarm_name exceeds the maximum length of 31 characters.
|
String
|
Invalid Port: port_number. Port number should be numeric.
|
String
|
Invalid port value: port_number. Port value is outside the range <0-65535>.
|
String
|
Given Real Server RealServer_name/port_number does not exist in the Server Farm ServerFarm_name.
|
String
|
Invalid Port: port_number. Port number should be numeric.
|
String
|
Invalid port value: port_number. Port value is outside the range <0-65535>.
|
String
|
Given Real Server RealServer_name/port_number does not exist in the Server Farm ServerFarm_name.
|
String
|
Invalid weight value: weight_value. Weight value is outside the range <1-100> [ace module, ace appliance].
|
String
|
Invalid weight value: weight_value. Weight value is outside the range <0-100> [csm].
|
String
|
Invalid weight value: weight_value. Weight value is outside the range <0-10> [css].
|
Example Request
The following example shows an XML-formatted SOAP request to perform the changeServerfarmRserverWeight action. SessionToken, DeviceID, SfRserver, and Reason are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<changeServerfarmRserverWeight
xmlns="http://anm.cisco.com">
<sid>-5217915770163489503</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
<serverfarmName>SF1</serverfarmName>
<realserverName>test</realserverName>
<adminState>OOS</adminState>
<ipAddr>10.2.1.11</ipAddr>
</changeServerfarmRserverWeight>
Example Response
The following example shows the XML response that has no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:changeServerfarmRserverWeightResponse xmlns:ns2="http://anm.cisco.com"/>
activateAnswer
This request activates an existing answer on the specified GSS, putting the answer into service.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
GSS device ID, including the device name, device type, and IP address attributes.
|
answer
|
Answer object, including the answer name, IP address, and type attributes. The type is always "vip."
|
Reason
|
Reason for the activation.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session token.
|
String
|
Session timeout.
|
String
|
Cannot reach the GSS.
|
String
|
GSS does not exist.
|
String
|
Config errors from the GSS.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the activateAnswer action. SessionToken, DeviceID, and answer are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>991427603955168471</sid>
<name>172.23.244.135</name>
<deviceType>GSS</deviceType>
<ipAddr>172.23.244.135</ipAddr>
<answerName>vip1</answerName>
<reason xmlns="">test</reason>
Example Response
The following example shows the XML response that has no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:activateAnswerResponse xmlns:ns2="http://anm.cisco.com"/>
suspendAnswer
This request suspends an existing answer on the specified GSS, putting the answer out of service.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
GSS device ID, including the device name, device type, and IP address attributes.
|
answer
|
Answer object, including the answer name, IP address, and type attributes. The type is always "vip."
|
Reason
|
Reason for the activation.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session token.
|
String
|
Session timeout.
|
String
|
Cannot reach the GSS.
|
String
|
GSS does not exist.
|
String
|
Config errors from the GSS.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the suspendAnswer action. SessionToken, DeviceID, and answer are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>991427603955168481</sid>
<name>172.23.244.135</name>
<deviceType>GSS</deviceType>
<ipAddr>172.23.244.135</ipAddr>
<answerName>vip1</answerName>
<reason xmlns="">test</reason>
Example Response
The following example shows the XML response that has no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:suspendAnswerResponse xmlns:ns2="http://anm.cisco.com"/>
activateDnsRule
This request activates an existing DNS rule on the specified GSS, putting the DNS rule into service.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
GSS device ID, including the device name, device type, and IP address attributes.
|
dnsRule
|
DNS rule object, including the DNS rule name, source IP address, owner, and configuration state attributes.
|
Reason
|
Reason for the activation.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session token.
|
String
|
Session timeout.
|
String
|
Cannot reach the GSS.
|
String
|
GSS does not exist.
|
String
|
Config errors from the GSS.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the activateDnsRule action. SessionToken, DeviceID, and dnsRule are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>6195441786283682375</sid>
<name>172.23.244.135</name>
<deviceType>GSS</deviceType>
<ipAddr>172.23.244.135</ipAddr>
<dnsRuleName>dns1</dnsRuleName>
<sourceAddress>Anywhere</sourceAddress>
<reason xmlns="">test</reason>
Example Response
The following example shows the XML response that has no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:activateDnsRuleResponse xmlns:ns2="http://anm.cisco.com"/>
suspendDnsRule
This request suspend an existing DNS rule on the specified GSS, putting the DNS rule out of service.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
DeviceID
|
GSS device ID, including the device name, device type, and IP address attributes.
|
dnsRule
|
DNS rule object, including the DNS rule name, source IP address, owner, and configuration state attributes.
|
Reason
|
Reason for the activation.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session token.
|
String
|
Session timeout.
|
String
|
Cannot reach the GSS.
|
String
|
GSS does not exist.
|
String
|
Config errors from the GSS.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the suspendDnsRule action. SessionToken, DeviceID, and dnsRule are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>6195441786283682370</sid>
<name>172.23.244.135</name>
<deviceType>GSS</deviceType>
<ipAddr>172.23.244.135</ipAddr>
<dnsRuleName>dns1</dnsRuleName>
<sourceAddress>Anywhere</sourceAddress>
<reason xmlns="">test</reason>
Example Response
The following example shows the XML response that has no output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:suspendDnsRuleResponse xmlns:ns2="http://anm.cisco.com"/>
getVMMappingInfo
This request returns all the server farm real server mapping information for a given VM. This API is supported on CSS, CSM, and ACE devices (device type: CSS, CSM, and VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
VMName
|
Unique name of the VM. The format is "/<Vcenter Name given in ANM>/<full path for vmname as in the Vcenter>/<VM name>".
|
Output Parameters
Parameter
|
Description
|
VMMappingInfos
|
Object attributes including the device ID, server farm name, server farm real server name, IP address, and port attributes.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Maximum session limit configured_limit reached for WS.
The default is 10 (see the "Modifying the Number of Concurrent Sessions Allowed" section).
|
String
|
None of the vCenter is imported in ANM.
|
String
|
Given VM VM_name does not exist.
|
String
|
Unable to get DeviceId for device_id.
|
String
|
Vmname should not be null.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the getVMMappingInfo action. SessionToken and VMName are the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
xmlns="http://anm.cisco.com">
<sid>3920090311151112722</sid>
<vmname xmlns="">/Vcenter/ANM_DC/vm/Discovered virtual machine/anm-vm-115</vmname>
Example Response
The following example shows the XML response that contains the list of VMMappingInfo objects as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:getVMMappingInfoResponse
xmlns:ns2="http://anm.cisco.com">
<VMMappingInfos xmlns="">
<deviceType>CSS</deviceType>
<ipAddr>172.23.244.250</ipAddr>
<sfrsname>myReal8</sfrsname>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
<sfrsname>webservicesample</sfrsname>
<deviceType>CSM</deviceType>
<chassisIPAddr>172.23.244.130</chassisIPAddr>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.241.46</ipAddr>
<sfname>tst_sf_dup</sfname>
<sfrsname>testing_dup</sfrsname>
</ns2:getVMMappingInfoResponse>
ApplicationTemplateManager Web Service APIs
This section describes the APIs associated with the ApplicationTemplateManager Web Service, which are as follows:
•
listTemplateDefinitions
•
getTemplateDefinitionMetadata
•
createTemplateInstance
•
listTemplateInstances
•
deleteTemplateInstance
•
listCheckpoints
•
createCheckpoint
•
deleteCheckpoint
•
rollbackCheckpoint
•
freeFormShow
listTemplateDefinitions
This API lists all the available ANM templates, including both ANM-defined templates (or system templates) and user-defined templates. Template definitions include the template name, description, application, application version, and so forth.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
Output Parameters
Parameter
|
Description
|
templateDefinitionArray
|
List of template definitions.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Session timeout.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the listTemplateDefinitions action. SessionToken is the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listTemplateDefinitions xmlns:ns2="http://anm.cisco.com">
<sid>-4754037077725100881</sid>
</ns2:listTemplateDefinitions>
Example Response
The following example shows the XML response that contains the list of templateDefinitions objects as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listTemplateDefinitionsResponse xmlns:ns2="http://anm.cisco.com">
<description>FTP LB</description>
<application>FTP</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
<name>Java Application Server</name>
<description>HTTP server, Java Servlet and JSP technologies, ie Apache
Tomcat</description>
<application>Java Application Server</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
<description>Basic L4 LB for HTTP</description>
<application>Basic HTTP</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
<description>Simple L3 all ports no mapping</description>
<application>Layer 3 LB</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
<name>Secure Webserver</name>
<description>Generic Secure Webserver with redirect</description>
<application>Secure Webserver</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
<name>Microsoft Exchange 2010</name>
<description>MS Exchange Template</description>
<application>Microsoft Exchange 2010</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
<name>DWS with Nexus 7000 OTV</name>
<description>Dynamic Workload Scaling with Nexus 7000 OTV for Basic LB
with HTTP or Secure Webserver</description>
<application>DWS with Nexus 7000 OTV</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
<description>Remote Desktop Protocol</description>
<application>RDP</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
<name>Microsoft SharePoint 2010</name>
<description>Microsoft SharePoint Template</description>
<application>Microsoft SharePoint 2010</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
<description>Simple L4 LB</description>
<application>Layer 4 LB</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
<description>DNS LB</description>
<application>DNS</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
</ns2:listTemplateDefinitionsResponse>
getTemplateDefinitionMetadata
This API takes an available ANM template definition and returns an array of template input objects, which contain the template name, default value, userData, hasChild, and the childElements details. The names are the variable names defined in the template definition file.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
TemplateDefinition
|
Template definition, which includes the template name, description, application, application version, and so forth. To retrieve a list of available template definitions, use the listTemplateDefinitions API.
|
Output Parameters
Parameter
|
Description
|
templateInputArray
|
Array of TemplateInput objects.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Session timeout.
|
String
|
Invalid template definition.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the getTemplateDefinitionMetadata action. SessionToken is the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:getTemplateDefinitionMetadata xmlns:ns2="http://anm.cisco.com">
<sid>-986099040932183901</sid>
<name>Microsoft SharePoint 2010</name>
<description>Microsoft SharePoint Template</description>
<application>Microsoft SharePoint 2010</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
</ns2:getTemplateDefinitionMetadata>
Example Response
The following example shows the XML response that contains the list of TemplateDefinitionMetadata objects as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:getTemplateDefinitionMetadataResponse xmlns:ns2="http://anm.cisco.com">
<templateDefinitionMetadata>
<displayString>Application Configuration</displayString>
<tagName>VARIABLE</tagName>
<displayString>Application Config Name:</displayString>
<tagName>VARIABLE</tagName>
<type>ipaddresswithprefix</type>
<displayString>VIP Address:</displayString>
<displayString>SharePoint Application Servers:</displayString>
<tagName>VARIABLE</tagName>
<tagName>VARIABLE</tagName>
<displayString>SSL Offload Port:</displayString>
<defaultValue>80</defaultValue>
<tagName>VARIABLE</tagName>
<displayString>Key Type:</displayString>
<defaultValue>PKCS12</defaultValue>
<tagName>VARIABLE</tagName>
<displayString>SSL Key URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.pkcs12</defaultValue>
<tagName>VARIABLE</tagName>
<displayString>SSL Key URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.pkcs12</defaultValue>
<tagName>VARIABLE</tagName>
<displayString>Key Server Username:</displayString>
<tagName>VARIABLE</tagName>
<displayString>Key Server Password:</displayString>
<tagName>VARIABLE</tagName>
<displayString>SSL Key URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.key</defaultValue>
<tagName>VARIABLE</tagName>
<name>der_key_url.name</name>
<displayString>SSL Key URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.key</defaultValue>
<tagName>VARIABLE</tagName>
<displayString>SSL Cert URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.der</defaultValue>
<tagName>VARIABLE</tagName>
<name>der_cer_url.name</name>
<displayString>SSL Cert URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.der</defaultValue>
<tagName>VARIABLE</tagName>
<name>der_username</name>
<displayString>Key Server Username:</displayString>
<tagName>VARIABLE</tagName>
<name>der_password</name>
<displayString>Key Server Password:</displayString>
<tagName>VARIABLE</tagName>
<displayString>SSL Key:</displayString>
<tagName>VARIABLE</tagName>
<displayString>SSL Key:</displayString>
<tagName>VARIABLE</tagName>
<name>key.contents</name>
<displayString>SSL Key:</displayString>
<tagName>VARIABLE</tagName>
<displayString>SSL Certificate:</displayString>
<tagName>VARIABLE</tagName>
<displayString>SSL Certificate:</displayString>
<tagName>VARIABLE</tagName>
<name>cert.contents</name>
<displayString>SSL Certificate:</displayString>
<tagName>VARIABLE</tagName>
<displayString>Cert/Key Passphrase:</displayString>
<tagName>VARIABLE</tagName>
<displayString>Enable Compression:</displayString>
<defaultValue>true</defaultValue>
<displayString>Network Configuration</displayString>
<tagName>VARIABLE</tagName>
<displayString>Load Balancer
(Device:VirtualContext):</displayString>
<tagName>VARIABLE</tagName>
<displayString>Client VLANs:</displayString>
<tagName>VARIABLE</tagName>
<displayString>Enable Source NAT:</displayString>
</templateDefinitionMetadata>
</ns2:getTemplateDefinitionMetadataResponse>
createTemplateInstance
This API takes a TemplateDefinition and TemplateInputArray object, generates a configuration based on the TemplateDefinition, and then deploys the configuration to the device. The TemplateInput object contains the template name and an array of name and value pairs. The names are the variable names defined in the template definition file and the values are all empty.
This API is supported on ACE devices (device type: VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
sessionToken
|
Session key of the application user.
|
deviceID
|
Device name, deviceType, and IP address attributes. For the ACE module only, the device ID includes the host chassis slot and chassis IP address attributes.
|
templateDefinition
|
Template definition, which includes the template name, description, application, application version, and so forth. To retrieve a list of available template definitions, use the listTemplateDefinitions API.
|
templateInputArray
|
Array of TemplateInput objects, which includes the template name, default value, userData, hasChild, and the childElements details. The names are the variable names defined in the template definition file and the values are the values set to the variable names.
|
Output Parameters
Parameter
|
Description
|
instanceId
|
Unique integer value of the created template.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Session timeout.
|
String
|
Invalid template definition.
|
String
|
Invalid template input.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the createTemplateInstance action. SessionToken is the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:createTemplateInstance xmlns:ns2="http://anm.cisco.com">
<sid>-8257363202654966035</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<chassisIPAddr>10.77.247.2</chassisIPAddr>
<name>Microsoft SharePoint 2010</name>
<description>Microsoft SharePoint Template</description>
<application>Microsoft SharePoint 2010</application>
<appVersion>1.1</appVersion>
<createTime>2012-02-08 15:06:51</createTime>
<createUser>Management Task</createUser>
<updateTime>2012-02-08 15:06:51</updateTime>
<updateUser>Management Task</updateUser>
<displayString>Application Configuration</displayString>
<tagName>VARIABLE</tagName>
<displayString>Application Config Name:</displayString>
<userData>sp_vs_01</userData>
<tagName>VARIABLE</tagName>
<type>ipaddresswithprefix</type>
<displayString>VIP Address:</displayString>
<userData>210.2.3.2</userData>
<displayString>SharePoint Application Servers:</displayString>
<tagName>VARIABLE</tagName>
<userDatas>210.2.3.4</userDatas>
<userDatas>210.2.3.5</userDatas>
<userDatas>210.2.3.6</userDatas>
<userDatas>210.2.3.7</userDatas>
<tagName>VARIABLE</tagName>
<displayString>SSL Offload Port:</displayString>
<defaultValue>80</defaultValue>
<tagName>VARIABLE</tagName>
<displayString>Key Type:</displayString>
<defaultValue>PKCS12</defaultValue>
<userData>PKCS12</userData>
<tagName>VARIABLE</tagName>
<displayString>SSL Key URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.pkcs12</defaultValue>
<userData>sftp://10.77.240.100/p12_rsa768.p12</userData>
<tagName>VARIABLE</tagName>
<displayString>SSL Key URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.pkcs12</defaultValue>
<userData>p12_rsa768.p12</userData>
<tagName>VARIABLE</tagName>
<displayString>Key Server Username:</displayString>
<userData>root</userData>
<tagName>VARIABLE</tagName>
<displayString>Key Server Password:</displayString>
<userData>roZes123</userData>
<tagName>VARIABLE</tagName>
<displayString>SSL Key URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.key</defaultValue>
<tagName>VARIABLE</tagName>
<name>der_key_url.name</name>
<displayString>SSL Key URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.key</defaultValue>
<tagName>VARIABLE</tagName>
<displayString>SSL Cert URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.der</defaultValue>
<tagName>VARIABLE</tagName>
<name>der_cer_url.name</name>
<displayString>SSL Cert URL:</displayString>
<defaultValue>sftp://1.2.3.4/dir/myfile.der</defaultValue>
<tagName>VARIABLE</tagName>
<name>der_username</name>
<displayString>Key Server Username:</displayString>
<tagName>VARIABLE</tagName>
<name>der_password</name>
<displayString>Key Server Password:</displayString>
<tagName>VARIABLE</tagName>
<displayString>SSL Key:</displayString>
<tagName>VARIABLE</tagName>
<displayString>SSL Key:</displayString>
<tagName>VARIABLE</tagName>
<name>key.contents</name>
<displayString>SSL Key:</displayString>
<tagName>VARIABLE</tagName>
<displayString>SSL Certificate:</displayString>
<tagName>VARIABLE</tagName>
<displayString>SSL Certificate:</displayString>
<tagName>VARIABLE</tagName>
<name>cert.contents</name>
<displayString>SSL Certificate:</displayString>
<tagName>VARIABLE</tagName>
<displayString>Cert/Key Passphrase:</displayString>
<tagName>VARIABLE</tagName>
<displayString>Enable Compression:</displayString>
<defaultValue>true</defaultValue>
<userData>true</userData>
<displayString>Network Configuration</displayString>
<tagName>VARIABLE</tagName>
<displayString>Load Balancer
(Device:VirtualContext):</displayString>
<tagName>VARIABLE</tagName>
<displayString>Client VLANs:</displayString>
<userData>ALL_VLAN</userData>
<tagName>VARIABLE</tagName>
<displayString>Enable Source NAT:</displayString>
<userData>false</userData>
</ns2:createTemplateInstance>
Example Response
The following example shows the XML response that contains the instanceId object as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:createTemplateInstanceResponse xmlns:ns2="http://anm.cisco.com">
<instanceId>5</instanceId>
</ns2:createTemplateInstanceResponse>
listTemplateInstances
This API lists all template instances, which includes the template name, description, application, application version, and so forth.
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
Output Parameters
Parameter
|
Description
|
templateInstanceArray
|
List of template instances.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Session timeout.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the listTemplateInstances action. SessionToken is the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listTemplateInstances xmlns:ns2="http://anm.cisco.com">
<sid>4918324415074336347</sid>
</ns2:listTemplateInstances>
Example Response
The following example shows the XML response that contains the list of templateInstances objects as the output parameter:
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listTemplateInstancesResponse xmlns:ns2="http://anm.cisco.com">
<instanceId>1</instanceId>
<templateName>FTP1</templateName>
<applicationType>FTP</applicationType>
<status>Complete</status>
<deviceId>10.77.247.20:new</deviceId>
<lastUpdatedTime>2012-02-09 00:25:58</lastUpdatedTime>
</ns2:listTemplateInstancesResponse>
deleteTemplateInstance
This API takes an instance ID and deviceID and deletes the configuration based on the instance ID.
This API is supported on ACE devices (device type: VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
deviceID
|
Virtual context name, devicetype, and IP address attributes. For the ACE module only, the device ID includes the host chassis slot and chassis IP address attributes.
|
instanceId
|
Template instance ID. To retrieve a list of available template instances, use the listTemplateInstances API.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Session timeout.
|
String
|
Invalid device ID.
|
String
|
Invalid template input.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the deleteTemplateInstance action. SessionToken is the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:deleteTemplateInstance xmlns:ns2="http://anm.cisco.com">
<sid>4918324415074336347</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>10.77.247.20</ipAddr>
<instanceId>1</instanceId>
</ns2:deleteTemplateInstance>
Example Response
The following example shows the XML response:
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:deleteTemplateInstanceResponse xmlns:ns2="http://anm.cisco.com">
</ns2:deleteTemplateInstanceResponse>
listCheckpoints
This API lists all the checkpoints in ANM inventory for a specified device.
This API is supported on ACE devices (device type: VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
deviceID
|
Virtual context name, devicetype, and IP address attributes. For the ACE module only, the device ID includes the host chassis slot and chassis IP address attributes.
|
Output Parameters
Parameter
|
Description
|
Checkpoints
|
List of checkpoints.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Session timeout.
|
String
|
Invalid device type.
|
String
|
Invalid device ID.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the listCheckpoints action. SessionToken is the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<listCheckpoints xmlns="http://anm.cisco.com">
<sid>-8567831601320378522</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>172.16.244.214</ipAddr>
Example Response
The following example shows the XML response that contains the list of Checkpoints objects as the output parameter:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:listCheckpointsResponse xmlns:ns2="http://anm.cisco.com">
<date>Sun May 1 15:10:04 2011</date>
<date>Sun May 1 15:10:04 2011</date>
<name>app-tmpl-1314729175709</name>
<date>Mon Sep 5 10:54:45 2011</date>
<name>beforeupgrade</name>
<date>Sun May 1 15:10:04 2011</date>
</ns2:listCheckpointsResponse>
createCheckpoint
This API creates a checkpoint on a specified device.
This API is supported on ACE devices (device type: VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
deviceID
|
Virtual context name, devicetype, and IP address attributes. For the ACE module only, the device ID includes the host chassis slot and chassis IP address attributes.
|
checkpointName
|
Name of the checkpoint to create.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Session timeout.
|
String
|
Invalid device type.
|
String
|
Invalid device ID.
|
String
|
Checkpoint already exists: checkpoint_name.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the createCheckpoint action. SessionToken is the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<createCheckpoint xmlns="http://anm.cisco.com">
<sid>-5488932206595059144</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>172.23.244.214</ipAddr>
<checkpointName xmlns="">test-checkpoint</checkpointName>
Example Response
The following example shows the XML response:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:createCheckpointResponse xmlns:ns2="http://anm.cisco.com"/>
deleteCheckpoint
This API deletes a checkpoint from a specified device.
This API is supported on ACE devices (device type: VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
deviceID
|
Virtual context name, devicetype, and IP address attributes. For the ACE module only, the device ID includes the host chassis slot and chassis IP address attributes.
|
checkpointName
|
Name of the checkpoint to delete. To retrieve a list of available checkpoints, use the listCheckpoints API.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Session timeout.
|
String
|
Invalid device type.
|
String
|
Invalid device ID.
|
String
|
Invalid checkpoint name.
|
String
|
Checkpoint doesn't exist: checkpoint_name
|
Example Request
The following example shows an XML-formatted SOAP request to perform the deleteCheckpoint action. SessionToken is the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<deleteCheckpoint xmlns="http://anm.cisco.com">
<sid>-5019678635804080238</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>172.16.244.214</ipAddr>
<checkpointName xmlns="">test-checkpoint</checkpointName>
Example Response
The following example shows the XML response:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:deleteCheckpointResponse xmlns:ns2="http://anm.cisco.com"/>
rollbackCheckpoint
This API rolls back a device's running configuration to a specified checkpoint.
This API is supported on ACE devices (device type: VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
deviceID
|
Virtual context name, devicetype, and IP address attributes. For the ACE module only, the device ID includes the host chassis slot and chassis IP address attributes.
|
checkpointName
|
Checkpoint to which you want to roll back.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Session timeout.
|
String
|
Invalid device type.
|
String
|
Invalid device ID.
|
String
|
Invalid checkpoint name.
|
String
|
Checkpoint doesn't exist: checkpoint_name
|
Example Request
The following example shows an XML-formatted SOAP request to perform the rollbackCheckpoint action. SessionToken is the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<rollbackCheckpoint xmlns="http://anm.cisco.com">
<sid>4270884926038298576</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>172.16.244.214</ipAddr>
<checkpointName xmlns="">test-checkpoint</checkpointName>
Example Response
The following example shows the XML response:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:rollbackCheckpointResponse xmlns:ns2="http://anm.cisco.com"/>
freeFormShow
This API returns the output of a specified show command sent to a specified device. The API includes the xml-show command, which specifies that the show command output is either regular CLI display output or it is in XML format.
This API is supported on ACE devices (device type: VIRTUAL_CONTEXT).
Input Parameters
Parameter
|
Description
|
SessionToken
|
Session key of the application user.
|
deviceID
|
Virtual context name, devicetype, and IP address attributes. For the ACE module only, the device ID includes the host chassis slot and chassis IP address attributes.
|
command
|
Name of the show command. Specify the command without using the word show. For example, to specify the show version command output, just use the word version.
|
isXMLized
|
Command output format:
• On (true)—XML format.
• Off (false)—CLI display format.
|
Output Parameters
Parameter
|
Description
|
None
|
None.
|
Exceptions
Type
|
Exception String
|
String
|
Invalid session ID.
|
String
|
Session timeout.
|
String
|
Invalid device type.
|
String
|
Invalid device ID.
|
String
|
Internal error: command parse error.
|
Example Request
The following example shows an XML-formatted SOAP request to perform the freeFormShow action. SessionToken is the input parameters for this particular action.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<freeFormShow xmlns="http://anm.cisco.com">
<sid>-869899350867169519</sid>
<deviceType>VIRTUAL_CONTEXT</deviceType>
<ipAddr>172.16.244.214</ipAddr>
<command xmlns="">access-list ALL</command>
<isXMLized xmlns="">false</isXMLized>
Example Response
The following example shows the XML response:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:freeFormShowResponse xmlns:ns2="http://anm.cisco.com">
<output xmlns="">access-list:ALL, elements: 3, status: ACTIVE
access-list ALL line 8 extended permit ip any any (hitcount=333800)
access-list ALL line 18 extended permit ip any host 172.16.244.230 (hitcount=0)
access-list ALL line 28 extended permit ip any host 10.10.10.1 (hitcount=0)</output>
</ns2:freeFormShowResponse>