Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Workload domain creation fails with the error " Can't slice subnet. Invalid subnet VSAN_SLICE-1" (59353)

Last Updated: 10/27/2018Categories: How toTotal Views: 2381Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Creation of new workload domain fails with the error  "Can't slice subnet. Invalid subnet VSAN_SLICE-1" during audit step before the actual workflow starts.

You see messages similar to the following in the /home/vrack/vrm/logs/vrack-vrm-debug.log on the SDDC Manager Controller VM:

2018-09-21 14:34:17.544 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.workflow.IPAllocationPlan] plan executed. allotted: 1, required: 1
2018-09-21 14:34:17.544 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.iaas.tools.IaasWorkflowService] For vCenter with id 511d683c-b419-4748-8232-817c9cdd5b36-0-vcenter-mgmt using IP address 10.152.1.89
2018-09-21 14:34:17.672 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.iaas.tools.IaasIpamService] Found existing network NetworkEntity{id=fefd5eec-5c60-4d90-8863-513d8a25a596, createdBy=null, name='VSAN', networkType=VSAN, subnet='172.30.8.0', subnetMask='255.255.254.0', gateway='172.30.8.1', dns='10.152.1.7', secondaryDns='null', ntps='[10.152.2.20, 10.152.2.21]', vlanId=302, portGroupName='vRack-DPortGroup-VSAN', isDefault=true} of type VSAN
2018-09-21 14:34:17.672 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.ipam.IpamService] checking if exist for VSAN
2018-09-21 14:34:17.673 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.ipam.IpamService] VSAN is exist: true
2018-09-21 14:34:17.673 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.ipam.IpamService] Attending to get subnet information for VSAN
2018-09-21 14:34:17.677 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.ipam.IpamService] Found information about VSAN with parent @/ , start address 172.30.8.1 and end address 172.30.9.254
2018-09-21 14:34:17.677 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.ipam.IpamService] Got the subnet info for VSAN
2018-09-21 14:34:17.681 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.iaas.tools.IaasWorkflowService] Vsan parent - base: VSAN
2018-09-21 14:34:17.681 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.configuration.util.IpamHelper] Getting unique name for network VSAN_SLICE
2018-09-21 14:34:17.681 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.ipam.IpamService] checking if exist for VSAN_SLICE
2018-09-21 14:34:17.682 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.ipam.IpamService] VSAN_SLICE is exist: true
2018-09-21 14:34:17.682 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.ipam.IpamService] checking if exist for VSAN_SLICE-1
2018-09-21 14:34:17.683 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.ipam.IpamService] VSAN_SLICE-1 is exist: false
2018-09-21 14:34:17.683 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.configuration.util.IpamHelper] Unique name found is VSAN_SLICE-1
2018-09-21 14:34:17.683 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.iaas.tools.IaasWorkflowService] Getting a slice from parent range VSAN, child range name VSAN_SLICE-1
2018-09-21 14:34:17.683 [https-jsse-nio-8443-exec-10] DEBUG [com.vmware.vrack.vrm.core.ipam.IpamService] Attedning to slice subnet VSAN with slice logicalname VSAN_SLICE-1 and netmask 255.255.255.128 .
2018-09-21 14:34:17.701 [https-jsse-nio-8443-exec-7] DEBUG [com.vmware.vrack.vrm.prm.dbservice.service.PrmInventoryServiceImpl] Inside PrmInventoryServiceImpl.getRackInfo() with rackId: 3bc42539-1c33-45eb-bd40-c01cbc00632f
2018-09-21 14:34:17.728 [https-jsse-nio-8443-exec-10] ERROR [com.vmware.vrack.vrm.core.ipam.IpamService] Failed to slice subnet VSAN with slice logicalname VSAN_SLICE-1 and netmask 255.255.255.128

2018-09-21 14:34:17.729 [https-jsse-nio-8443-exec-10] ERROR [com.vmware.vrack.vrm.iaas.tools.IaasWorkflowService] Could not register VSAN slice network.
com.vmware.vrack.vrm.core.ipam.IpamException: com.vmware.ipam.exceptions.RangeNotFoundIpamException: Can't slice subnet. Invalid subnet VSAN_SLICE-1

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

SDDC Manager slices the default VSAN network with a subnet mask of /25 by default. This provides 128 IPs per slice which is allocated to each workload domain. The issue occurs when a subnet smaller than /22 is chosen for the VSAN network during bring-up and there are not enough IPs left for further slicing into a /25 subnet.

Resolution

Login to the SDDC Manager Controller VM.

Open the /home/vrack/VMware/vrack/vrm.properites file with a text editor.

Change the property ip.slice.mask to 255.255.255.192. This will shrink the slice size to /26, or 64 IP addresses.

Save and close the file.

Restart the vcfmanager service by issuing the following command:

systemctl restart vcfmanager

In the SDDC manager UI, restart the workload domain creation workflow.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
设置虚拟机的最大待处理磁盘请求数 (1268)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 2.x

Take Our Survey

Support Assistant