VMware Cloud Community
srl101
Contributor
Contributor

Creation of VXLAN Network Pool fails in vCloud Director 5.6 with NSX with error - VSM response error (100): null

I am using NSX with vcloud 5.6 and VXLAN network pool creation fails with "[ 9d227524-e462-4ecf-94b3-8ed4cdf8ef38 ] VSM response error (100): null"

Error trace:

2015-08-19 16:28:11,032 | ERROR| backend-activity-pool-14  | TaskActivity               | [Activity Execution] Unable to execute task 'TaskModel [id=32d9be60-175f-403b-a69c-d7725d1ddf11, orgName=System, cellInstanceId=41, targetId=f5debfec-e67a-4f2a-a026-20910bd7e514, jobId=6a7e36e6-35ff-4ef6-8348-c11697ff016c, operation=NETWORK_REPAIR_NETWORK_POOL, taskName=NETWORK_REPAIR_NETWORK_POOL, retriable=false, status=running, version=2' - Handle: urn:uuid:6a7e36e6-35ff-4ef6-8348-c11697ff016c, Current Phase: TaskActivity$ExecutePhase, ActivityExecutionState Parameter Names: [NDC, TASK_JOB_ID, activityPhaseStackList] | requestId=e69c2f57-a012-42a3-a490-9a91b276556c vcd=46ef3bf5-7c9e-473a-973b-707f69b2d943,task=6a7e36e6-35ff-4ef6-8348-c11697ff016c activity=urn:uuid:6a7e36e6-35ff-4ef6-8348-c11697ff016c

com.vmware.vcloud.fabric.nsm.error.VsmException: VSM response error (100): null

    at com.vmware.vcloud.fabric.nsm.error.NetworkSecurityErrorHandler.processException(NetworkSecurityErrorHandler.java:95)

    at com.vmware.vcloud.fabric.nsm.error.NetworkSecurityErrorHandler.handleError(NetworkSecurityErrorHandler.java:70)

    at org.springframework.web.client.RestTemplate.handleResponseError(RestTemplate.java:494)

    at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:451)

    at com.vmware.vcloud.fabric.net.utils.impl.LoggingRestTemplate.doExecute(LoggingRestTemplate.java:64)

    at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:409)

    at org.springframework.web.client.RestTemplate.getForObject(RestTemplate.java:207)

0 Kudos
1 Reply
IamTHEvilONE
Immortal
Immortal

you'll probably need a support request to get assistance from the vCloud and NSX team to resolve this.

anytime i have seen the VSM response error (100), there is some brief work on the internal parts that is best fixed with guidance from support.

0 Kudos