So beginning with 2.3.3.4 the Add ip pool to virtual network has started to fail. We have been using this call in a script for a while now, but it now dislikes our names for the actual vlans. The structure that worked with 2.2.x.x was:
{
"siteNameHierarchy": "Global/Sites/Testsite",
"virtualNetworkName": "vrf1",
"isLayer2Only": false,
"ipPoolName": "vrf1-pool1",
"vlanId": "1023",
"vlanName": "vrf1_pool1",
"autoGenerateVlanName": false,
"scalableGroupName": "some_sgroup",
"isL2FloodingEnabled": false,
"isThisCriticalPool": false,
"isWirelessPool": false,
"isIpDirectedBroadcast": false,
"isCommonPool": false,
}
When this payload is sent in 2.3.3.4 we get:
{
"status": "failed",
"description": "'namespace'",
"taskId": null,
"taskStatusUrl": "/dna/intent/api/v1/task/null",
"executionStatusUrl": "/dna/intent/api/v1/dnacaap/management/execution-status/56e16f0c-57e4-4909-a461-772cd488292f",
"executionId": "56e16f0c-57e4-4909-a461-772cd488292f",
"response": {
"failureReason": "Unknown Error: An unexpected condition was encountered. Please try after the system is restored."
}
}
However, if i change "vlanName": "vrf1_pool1" to "vlanName": "vrf1_pool11" or some other small change, it works as expected. It seems like the "namespace" error indicates that this vlanName has been used previously (as it has), and cant be used again. The problem here is that we have 100 sites already using the same vlanname, and we use that name in our Auth-policies in ISE to not make 100 different policies to assign vlan/ip-pools. Anyone seen the same in 2.3.3.4?
