vRealize blueprint fails

[rupamc1983]

I have a VRA7 setup with NSX  6 integrated and i am trying to deploy a VM with Network configuration ( using blue print).

Problem is that few days back it was working but without doing any change i can see that the blueprint from the creation of  the VM with network config is failing.

Found two repaetaed issue .

1. The network range in the network profile for the routed network status keep on getting to destroyed and i need to regenerate the range again

2. the blue print deployment is failing with the below error

Error in (Workflow:Create logical switch / Scriptable task (item1)#4) VSM response error (100): 409 Conflict

From the orchestrator workflow for the Create logical switch below is the attached logs.

[2017-01-21 03:09:21.336] [E] Error in (Workflow:Create logical switch / Scriptable task (item1)#4) VSM response error (100): 409 Conflict

[2017-01-21 03:09:21.358] [E] Workflow execution stack:

***

item: 'Create logical switch/item1', state: 'failed', business state: 'null', exception: 'VSM response error (100): 409 Conflict (Workflow:Create logical switch / Scriptable task (item1)#4)'

workflow: 'Create logical switch' (594445ef-0ae9-4c46-b989-96be7caacc10)

|  'input': name=connection type=NSX:Connection value=dunes://service.dunes.ch/CustomSDKObject?id='21e35c69-4f8e-4b94-b22c-f50bc0bccb0f'&dunesName='NSX:Connection'

|  'input': name=scopeId type=string value=vdnscope-1

|  'input': name=logicalSwitchName type=string value=AutoWebTier-dbfa0546-70a5-4c17-992c-25cffcc0f739

|  'input': name=description type=string value=Managed by VMware vRealize Automation

|  'input': name=tenantId type=string value=

|  'output': name=logicalSwitch type=NSX:VirtualWire value=null

|  'no attributes'

*** End of execution stack.

any help is appreciated.

[bayupw]

From the error message, the workflow seems to fail to create a new logical switch.

How do you config your 1. NSX Segment ID pool and 2. Routed network profile?

Would like to make sure that you have sufficient segment IDs and routed network ranges.

Could you test to if creating a logical switch from vSphere Web Client successful?

1. NSX Segment ID configuration

2. Routed Network Profile configuration

[rupamc1983]

Hi

Thanks for the quick response

I have verified and  all my setting are intact.

This time i again tried to deploy the machine with services and getting the below error.

The following component requests failed: Auto_Web_Tier. [Error code: 42000 ] - [Error Msg: Infrastructure service provider error: Cannot allocate a network range for routed network profile. The list of unallocated network ranges for the parent network profile Auto_Web_Tier has been exhausted.]

below is the network range screenshot.

Not sure why everytime i recreate and wanted to deploy the machine it gives the above error.

The above error is something new from the previous one i posted.

Any help appreciated.

[bayupw · Accepted solution]

Everytime a blueprint is created, a network range will be used and network range cannot be re-used even if the IP is not all alocated in that subnet/range.

I would suggest you to create multiple network ranges as in my examples.

For example, you have 2 network ranges in your routed network profiles. A user submit a request from catalog/blueprint that uses a routed network profile, it will allocate IP address from the network range and let say use the 1st network range, then a logical switch will be created and connected to DLR using that network range.

If there is another user who submit a new request, it will use the 2nd network range even if the 1st network range still have some spare IP.

If the deployment gets deleted, then the IP can be used if it has been reclaimed.

vRealize Automation 6.2 Documentation Center - Static IP Address Assignment

"When a machine that has a static IP address is destroyed, its IP address is made available for use by other machines. The process to reclaim static IP addresses runs every 30 minutes, so unused addresses may not be available immediately after the machines using them are destroyed. If there are not available IP addresses in the network profile, machines cannot be provisioned with static IP assignment on the associated network path."

vRealize Automation 6.2 Documentation Center - Creating a Network Profile

"Fabric administrators specify the ranges of IP addresses that can be used in network profiles. Each IP address in the specified ranges allocated to a machine is reclaimed for reassignment when the machine is destroyed and the ReclaimDestroyedStaticIPAddresses workflow runs."

[MRoushdy]

Hi, but this is unreasonable, what if I wanted to use a /24 IP range?, does this mean that every deployment requires a separate range?

I've created two network ranges, and I'm testing on just two users, and their second requests fail