All Posts

kmcd03 · ‎08-15-2023

I would like to start using NSX-T distributed firewall (dFW) in my VCF 4.5 domains, but won't be using logical routing at this time. VCF has prepared the nodes, e.g. created transport zone, the upli...

I would like to start using NSX-T distributed firewall (dFW) in my VCF 4.5 domains, but won't be using logical routing at this time. VCF has prepared the nodes, e.g. created transport zone, the uplink and transport node profiles, configured NSX on the nodes, etc. If I want to start using dFW, but don't care about overlay, do I simply create a segment with a VLAN in NSX Manager and associate it with the transport zone created by VCF? Then binding VMs vNIC to the VDS portgroup so dFW policies and rules are applied. Or should I create a new VLAN transport zone and associate with hosts in the domain? And then create the segment and bind VM vNICs. Thanks!

CyberNils · ‎08-15-2023

Change vmk0 back to 1500 bytes MTU. That is the recommended setting.

santunezlenovo · ‎08-14-2023

Hello Guys I am implementing VCF and when deploying VRLCM it gives me errors, the Management vlan is configured with MTU 9000, and the vmk0 from 1500 is changed to 9000. When I run from an esxi host...

Hello Guys I am implementing VCF and when deploying VRLCM it gives me errors, the Management vlan is configured with MTU 9000, and the vmk0 from 1500 is changed to 9000. When I run from an esxi host vmkping -s 9000 10.0.246.254 which is the gateway from X-Region does not respond, but if I do vmkping -s 1500 if you get a response, and the switch ports, it is at mtu 9000 the error is the following: Message: vRealize Suite Lifecycle Manager deployment failed. Correction message: Check if the Jumbo frames between SDDC Manager network and the vRealize Suite Lifecycle Manager network are enabled and if the required ports listed at https://ports.esp.vmware.com are open. Reference Token: QT04T5 Reason: vRSLCM deployer failed: Local command /iso_store/ovftool/ovftool --skipManifestCheck --powerOn --diskMode=thin --acceptAllEulas --allowExtraConfig --ipProtocol=IPv4 --ipAllocationPolicy=fixedPolicy --targetSSLThumbprint=4E:7C:61 :9C:78:F7:0D:FB:6C:00:47:7E:68:8E:01:35:83:6D:77:B0 --datastore=sfo-m01-cl01-ds-vsan01 --network =X-Region --prop:vami.DNS.VMware_vRealize_Suite_Life_Cycle_Manager_Appliance=10.0.10.11,10.0.10.13 --prop:vami.netmask0.VMware_vRealize_Suite_Life_Cycle_Manager_Appliance=255.255.255.0 --prop:vami.gate way.VMware_vRealize_Suite_Life_Cycle_Manager_Appliance=10.0.246.254 --name =vcf-vrlcm --prop:vami.hostname=vcf-vrlcm.pe280.bally.local --prop:vami.ip0.VMware_vRealize_Suite_Life_Cycle_Manager_Appliance=10.0.246.2 --X:waitForIp --prop:va-fips-enabled=False --prop:varoot-password=******** /nfs/vmware/vcf/nfs-mount/bundle/3132b806-f891-11ed-b67e-0242ac120002/bundle-79587/vrslcm_install/VMware-vLCM-Appliance -8.10.0.6-21331275_OVF10.ova vi://administrator@vsphere.local:************@vcenter-benavides.pe280.bally.local/VCF-BENAVIDES/host/VCF-VSAN-BENAVIDES /Resources/sfo-m01-cl01-rp-sddc-mgmt executed successfully with exit value true LocalProcess INFO: 2023-08-15 00:34:14 - Opening OVA source: /nfs/vmware/vcf/nfs-mount/bundle /3132b806-f891-11ed-b67e-0242ac120002/bundle-79587/vrslcm_install/VMware-vLCM-Appliance-8.10.0.6-21331275_OVF10.ova LocalProcess INFO: 2023-08-15 00:34:14 - The manifest does not validate LocalProcess INFO: 2023-08-15 00:34:14 - Opening VI target: vi://administrator%40vsphere.local@vcenter-benavides.pe280.bally.local:443/VCF-BENAVIDES/host/VCF-VSAN-BENAVIDES /Resources/sfo-m01-cl01-rp-sddc-mgmt LocalProcess INFO: 2023-08-15 00:35:10 - Error: LocalProcess INFO: 2023-08-15 00:35:10 - - An error occurred during host configuration: Failed to attach VIF: RPC call to NSX management plane timeout. LocalProcess INFO: 2023-08-15 00:35:10 - Warning: LocalProcess INFO: 2023-08-15 00:35:10 - - The manifest is present but user flag causing to skip it LocalProcess INFO: 2023-08-15 00:35:10 - Completed with errors

rholgateVCI · ‎08-10-2023

Question can a customer mix and match BOYL windows with SPLA on VMware running on azure? Answer

viquarhcimca · ‎08-09-2023

the path you want to achive is not support yet.

viquarhcimca · ‎08-09-2023

Are you able to login to the VRSLCM using the SVC account ?

santunezlenovo · ‎08-08-2023

Hello DHCP is being delivered by a Dell switch. interface vlan2500 description edge-vtep no shutdown mtu 9216 ip vrf forwarding acity ip address 192.168.35.253/24 ! vrrp-group 250 virtual-a...

Hello DHCP is being delivered by a Dell switch. interface vlan2500 description edge-vtep no shutdown mtu 9216 ip vrf forwarding acity ip address 192.168.35.253/24 ! vrrp-group 250 virtual-address 192.168.35.254 ! ip dhcp server no disable ! pool edge-vtep lease inifinite network 192.168.35.0/24 default-router 192.168.35.254 range 192.168.35.101 192.168.35.200 ! I understand that the recommendation is that there be a dhcp server in the network and that only the switch do a dhcp relay? I have rebooted the nodes, but they still do not accept IP. Thanks SAN

CyberNils · ‎08-08-2023

I think the error messages are pretty clear. You need to edit your json file to make it match your environment. Post the file here for help or call VMware Support and they will help you.

fredzhang · ‎08-07-2023

Dear Experts, When use the curl commands to access the VRLCM API, no response is output, do you have any suggestions? Thanks

fredzhang · ‎08-07-2023

Dear Experts, I am upgrade the SDDC Manager from 4.1.0, but the upgrade precheck for the VRLCM failed, the error messages is: vRealize Suite Lifecycle Manager connection check field. Would you ...

Dear Experts, I am upgrade the SDDC Manager from 4.1.0, but the upgrade precheck for the VRLCM failed, the error messages is: vRealize Suite Lifecycle Manager connection check field. Would you have some suggestions?

Gizzie · ‎08-07-2023

Upgrading this version is not possible I presume. Please see documentation note https://docs.vmware.com/en/VMware-NSX/4.0/upgrade/GUID-FAFED150-0652-4B7D-9B5E-5F655C22FE48.html Note: Upgrade fro...

Upgrading this version is not possible I presume. Please see documentation note https://docs.vmware.com/en/VMware-NSX/4.0/upgrade/GUID-FAFED150-0652-4B7D-9B5E-5F655C22FE48.html Note: Upgrade from NSX 3.2.2 to 4.0.1 or 4.0.1.1 is not supported. The reason is that the General Availability (GA) of NSX 3.2.2 happened after the GA of NSX versions 4.0.1 and 4.0.1.1. Some capabilities and important fixes in NSX 3.2.2 might not be available in versions 4.0.1 or 4.0.1.1 due to the chronological order in which these versions were released. https://docs.vmware.com/en/VMware-NSX/4.1/upgrade/GUID-FAFED150-0652-4B7D-9B5E-5F655C22FE48.html Note: The following upgrade paths are not supported: Upgrade from NSX 3.2.2 to 4.0.1 or 4.0.1.1. Upgrade from NSX 3.2.3 to 4.1.0.0 or 4.1.0.1 The reason is that the General Availability (GA) of the targeted upgrade version happened before the GA of your current version of NSX. Some capabilities and important fixes might not be available in the targeted versions due to the chronological order in which the versions were released.

Melvin3 · ‎08-07-2023

Hello everyone Having issues with nsx-t datacenter My NSX-T datacenter is version 3.2.3.1.0.22104592 and i want to upgrade 4.0.1U1 or 4.1.0 for my vcenter upgrade to 8.0. I have tried so...

Hello everyone Having issues with nsx-t datacenter My NSX-T datacenter is version 3.2.3.1.0.22104592 and i want to upgrade 4.0.1U1 or 4.1.0 for my vcenter upgrade to 8.0. I have tried some upgrade bundle but no one work The problem is i thinks no upgrade path exist for this upgrade, can you confirm and/or help ? regards,

CyberNils · ‎08-07-2023

Try rebooting one ESXi host and see if that helps. Try putting a laptop in the same VLAN and see if that can get a DHCP config.

Brisk · ‎08-06-2023

Did you define a DHCP relay in your Segments? This is needed to forward the DHCP requests to those switches. Alternatively, you could run DHCP inside of your NSX environment itself.

santunezlenovo · ‎08-06-2023

Hello Guys In a VCF cluster that is stretched, the Dell switch that delivered DHCP to the nodes had a 7-day lease policy. Subsequently, the nodes are not receiving DHCP, the switches were changed t...

Hello Guys In a VCF cluster that is stretched, the Dell switch that delivered DHCP to the nodes had a 7-day lease policy. Subsequently, the nodes are not receiving DHCP, the switches were changed to infinite lease, but the problem persists the following has been run on each node but is not receiving DHCP esxcli network ip interface set -e false -i vmk10 ; esxcli network ip interface set -e true -i vmk10 esxcli network ip interface set -e false -i vmk11 ; esxcli network ip interface set -e true -i vmk11 A support case was opened, but we don't have an answer yet, and I need to know if someone knows how to solve this problem. We have rebooted the nodes, switch, etc, but the problem persists. I would appreciate if someone could give me an idea what could be happening. VCF version is 5.0, and ESXi 8.0 Thanks for your comments Regards Sebastian

santunezlenovo · ‎08-06-2023

Thanks

cathalp_vmw · ‎08-04-2023

The VCF design requires the edges in the edge cluster to be on AZ1 nodes using affinity rules, no edges are deployed onto AZ2 nodes, additional configuration is required to configure BGP peers with t...

The VCF design requires the edges in the edge cluster to be on AZ1 nodes using affinity rules, no edges are deployed onto AZ2 nodes, additional configuration is required to configure BGP peers with the TORs in AZ2. This requires the uplink VLANs to be stretched between sites, this will ensure no asymmetric routing issues. To achieve this route maps are configured with AS Path Prepend and Local preference to steer traffic through AZ1 during normal operating conditions, if AZ1 fails the edges will restart on AZ2. Details of the design can be found here... https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-design/GUID-0FA19534-983E-46DE-B299-5176587FDCE4.html For the VI WLD alternative designs are possible depending on the requirement but may involve a manual edge deployment seen as SDDC manager workflow is based on the design detailed in the link provided.

santunez2275 · ‎08-03-2023

Hello Guys In a VCF configuration with Stretched cluster, how many Edge Clusters are required as a minimum? In datacenter A, the ASN of the ToR Switch is ASN 65101 and in datacenter B, The ASN is 6...

Hello Guys In a VCF configuration with Stretched cluster, how many Edge Clusters are required as a minimum? In datacenter A, the ASN of the ToR Switch is ASN 65101 and in datacenter B, The ASN is 65102 When I create the Edge Clusters with the configuration of Datacenter A with ASN 65101 they are created without problems with 2 edges that are required at least. When I configure 4 Edge nodes, where I configure 2 edge for ASN 65101 they have no problems, but the 2 Edge for ASN 65102 that corresponds to the ASN of datacenter B, gives the error attached in the image So I don't know if it is correct to create 4 Edge cluster, or with 2 it is correct. It is necessary to create the two edges of datacenter B, if not necessary, what happens if Datacenter A goes down, as the edge node works, to exit through the ASN of Datacenter 2. I appreciate your help, because I am doing a laboratory and it is not clear to me how it works in Stretched Cluster. Thank you Regards

cathalp_vmw · ‎08-03-2023

No a minimum of 3+3 is required as stated in the VCF on VxRail Architecture guide here on page 73... https://www.delltechnologies.com/asset/en-us/products/converged-infrastructure/technical-support/...

No a minimum of 3+3 is required as stated in the VCF on VxRail Architecture guide here on page 73... https://www.delltechnologies.com/asset/en-us/products/converged-infrastructure/technical-support/vmware-cloud-foundation-4-x-on-vxrail-architecture-guide.pdf.external

jburen · ‎08-03-2023

One more question: can you start with three nodes, stretch the cluster to six nodes and then remove two nodes from the cluster?

All

All Posts

using NSX-T distributed firewall in VCF 4.5 environment

Re: Error Deployment VRLCM

Error Deployment VRLCM

Can BOYL be used under SPLA licencing?

Re: NSX-T Datacenter 3.2.3.1 upgrade

Re: VCF upgrade from 4.1.0 precheck failed vRealize Suite Lifecycle Manager connection check field.

Re: DHCP NSX-Overlay

Re: Is it even possible to expand workload domain cluster that is working under SDDC?

Access the VRLCM API use the CURL commands

VCF upgrade from 4.1.0 precheck failed vRealize Suite Lifecycle Manager connection check field.

Re: NSX-T Datacenter 3.2.3.1 upgrade

NSX-T Datacenter 3.2.3.1 upgrade

Re: DHCP NSX-Overlay

Re: DHCP NSX-Overlay

DHCP NSX-Overlay

Re: Edge Cluster on Stretched Cluster

Re: Edge Cluster on Stretched Cluster

Edge Cluster on Stretched Cluster

Re: Number of hosts for an extra VxRail cluster in a VI Workload Domain

Re: Number of hosts for an extra VxRail cluster in a VI Workload Domain