sunvmware1's Posts

The NSX Distributed Firewall has added malware detection and prevention support for Linux guest endpoints (VMs). Linux has become the most common operating system across multi-cloud environments. In... See more...
The NSX Distributed Firewall has added malware detection and prevention support for Linux guest endpoints (VMs). Linux has become the most common operating system across multi-cloud environments. In addition, we expanded the support for malware analysis for known and unknown files. Along with hash-based detection for new files, we added support for local and cloud analysis for unknown files of up to 64MB. Prior to NSX 4.0.1.1, the NSX Gateway supported Active/Standby High Availability mode where traffic is forwarded through a single active NSX Gateway.  This deployment mode required additional design and architecture considerations such as limits induced by the Active/Standby mode on bandwidth and CPU utilization. Additionally, 4.0.1.1 brings added support for malware detection to the NSX Gateway Firewall running directly on bare metal, allowing for consistent protection regardless of whether customers choose a virtual or physical form factor NSX 4.0.1.1 introduces 16 additional NSX Edge metrics that further enhance monitoring and troubleshooting.  This includes flow cache metrics, queue occupancy for fast path interfaces, and NIC throughput on ingress and egress on the NSX Edge fast path interfaces. more details refer - https://blogs.vmware.com/networkvirtualization/2022/11/nsx-4-0-innovations.html/  
How to Mapping NSX for vSphere sites to NSX-T Federation Locations? can some help steps to create.
Hi, Try to check the logs, ssh to the NSX manager and check the manager log using : show manager log command Is this is the first controller in the system? refer- https://roie9876.wordpress.com/2... See more...
Hi, Try to check the logs, ssh to the NSX manager and check the manager log using : show manager log command Is this is the first controller in the system? refer- https://roie9876.wordpress.com/2014/08/30/deploying-nsx-v-controller-disappear-from-vsphere-client/   If the Answer is helpful, please click "Mark as Correct Answer", this can be beneficial to other community members.
Hi, A Non-Maskable Interrupt (NMI) is a hardware interrupt that cannot be ignored by the processor. These types of interrupts are usually reserved for very important tasks and to report hardware err... See more...
Hi, A Non-Maskable Interrupt (NMI) is a hardware interrupt that cannot be ignored by the processor. These types of interrupts are usually reserved for very important tasks and to report hardware errors to the processor. Depending on the make and model of the system, you may be able to deliberately send an NMI to the CPUs. By sending an NMI to the processor, it is forced to switch CPU context to the registered non-maskable interrupt handler. The interrupt cannot be ignored (masked). The operating system can handle the NMI based on prior configuration. refer article & detail steps - https://kb.vmware.com/s/article/1014767  
Hi, We have officially tested 16 overlays out of a single interface. In regards to multiple overlays out of 1 physical interface, indeed as long as its a route capable interface , VMware SD-WAN can... See more...
Hi, We have officially tested 16 overlays out of a single interface. In regards to multiple overlays out of 1 physical interface, indeed as long as its a route capable interface , VMware SD-WAN can run multiple overlays.    If the Answer is helpful, please click "Mark as Correct Answer", this can be beneficial to other community members.  
Hi, The limitation is 5000 per Tier-0 and 16,000 for system-wide rules.  
Hi, If a DHCP service is configured on your NSX-v Edge Services Gateway, pre-configure a Gateway DHCP service on the NSX-T overlay segment. For migrating DHCP leases, Edge cutover migration mode sup... See more...
Hi, If a DHCP service is configured on your NSX-v Edge Services Gateway, pre-configure a Gateway DHCP service on the NSX-T overlay segment. For migrating DHCP leases, Edge cutover migration mode supports only Gateway DHCP service. Local DHCP server or Local DHCP relay is not supported. refer- https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/nsxt_31_migrate.pdf   If the Answer is helpful, please click "Mark as Correct Answer", this can be beneficial to other community members.
Hi, No. Beginning with NSX-T Data Center 3.1, the NSX license editions that you have assigned to your NSX-T Data Center deployment determine which features you can access in the Policy mode of the ... See more...
Hi, No. Beginning with NSX-T Data Center 3.1, the NSX license editions that you have assigned to your NSX-T Data Center deployment determine which features you can access in the Policy mode of the NSX Manager user interface. If you have multiple editions of licenses, NSX Manager uses the highest license edition that is applicable. When the licenses are valid, the order of priority for the license editions is as follows. NSX Data Center Enterprise Plus, NSX Enterprise Plus per Processor (Limited Export), NSX Data Center Evaluation NSX Data Center Advanced, NSX for vSphere - Enterprise, NSX for vSphere - Advanced, NSX Data Center Advanced per Processor (for Limited Export) NSX Data Center Remote Office Branch Office (ROBO) NSX Data Center Professional NSX Data Center Standard and NSX for vSphere - Standard NSX for vShield Endpoint Add-on license is checked for add-on features, such as NSX Data Center Distributed Threat Prevention. https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-8274054D-FA4C-4E1B-860A-4A5BD04620BF.html   If the Answer is helpful, please click "Mark as Correct Answer", this can be beneficial to other community members.
Hi, To resolve this issue, enable switch notification by setting the Notify Switches option to Yes in the Load Balancing and Failover Policy. refer- https://kb.vmware.com/s/article/1007464
Hi @blu3nood, You can gradually migrate specific parts of the NSX-v logical configuration, or if needed, create some configurations manually in the destination NSX-T environment. When your organizat... See more...
Hi @blu3nood, You can gradually migrate specific parts of the NSX-v logical configuration, or if needed, create some configurations manually in the destination NSX-T environment. When your organization is ready to switch to the new NSX-T environment, you can use Layer 2 bridging to extend networks logically between both environments and move the workloads to NSX-T. For instance, you might want to bridge one network at a time, and gradually move the workloads from NSX-v to NSX-T. After all the workloads are moved to the new NSX-T environment, you can remove the bridge, and finally decommission your old hardware. Refer: https://nsx.techzone.vmware.com/resource/nsx-v-nsx-t-3x-migration-coordinator#_Toc57645169 https://mynetworker.blog/2020/06/27/nsx-v-to-nsx-t-migration-using-layer-2-bridging/        
Hi, Refer to the common troubleshooting steps. SSL VPN-Plus: Communication Issues KB article https://kb.vmware.com/s/article/2126671
When completing an upgrade precheck in SDDC-Manager the NSX-T password validity check fails:   Impact - HIgh: Password has expired and upgrade will fail due to this.  You will see the following i... See more...
When completing an upgrade precheck in SDDC-Manager the NSX-T password validity check fails:   Impact - HIgh: Password has expired and upgrade will fail due to this.  You will see the following in the /var/log/vmware/vcf/lcm/lcm-debug.log:   2021-06-17T19:10:20.089+0000 DEBUG [vcf_lcm,0000000000000000,0000,precheckId=af8ce3f0-615b-4387-919c-f123e797d4a5,resourceType=NSX_T,resourceId=nsx.corp.local] [c.v.e.s.l.p.c.u.VmwPrimitiveUtils,pool-3-thread-48] Password validation status for API credential type of resource: nsx.corp.local is VALID 2021-06-17T19:10:20.090+0000 DEBUG [vcf_lcm,0000000000000000,0000,precheckId=af8ce3f0-615b-4387-919c-f123e797d4a5,resourceType=NSX_T,resourceId=nsx.corp.local] [c.v.e.s.l.p.util.PrimitiveHelper,pool-3-thread-48] Password validation for API credential type of resource: nsx.corp.local is VALID 2021-06-17T19:10:20.090+0000 DEBUG [vcf_lcm,0000000000000000,0000,precheckId=af8ce3f0-615b-4387-919c-f123e797d4a5,resourceType=NSX_T,resourceId=nsx.corp.local] [c.v.e.s.l.p.c.u.VmwPrimitiveUtils,pool-3-thread-48] Password validationexpiry data for API credential type of resource: nsx.corp.local is SUCCEEDED 2021-06-17T19:10:20.090+0000 DEBUG [vcf_lcm,0000000000000000,0000,precheckId=af8ce3f0-615b-4387-919c-f123e797d4a5,resourceType=NSX_T,resourceId=nsx.corp.local] [c.v.e.s.l.p.c.u.VmwPrimitiveUtils,pool-3-thread-48] Password validationexpiry for API credential type of resource: nsx.corp.local is in -22 days 2021-06-17T19:10:20.090+0000 INFO  [vcf_lcm,0000000000000000,0000,precheckId=af8ce3f0-615b-4387-919c-f123e797d4a5,resourceType=NSX_T,resourceId=nsx.corp.local] [c.v.e.s.l.p.i.nsxt.NsxtPrimitiveImpl,pool-3-thread-48] Completed precheck task NSX_T_PASSWORD_VALIDITY_CHECK  on resource id nsx.corp.local  with status RED   Note: This precheck will also fail if the password expiry is cleared using the command "clear user admin password-expiration". It is a known issue, please refer the KB SDDC manager falsely shows the password for NSXT component as expired for more information.      Cause NSX-T does not support setting password expiry for root or admin to 99999 NSX-T password expiry can be set to a maximum period of 9999      Resolution Set password expiry for root and admin to 9999: 1. SSH to NSX-T VIP with admin credentials 2. Check password expiry for both root and admin accounts get user admin password-expiration 3. If the password has expired or is set to 99999 use the following command to set password expiry to 9999 set user admin password-expiration 9999 4. Retry upgrade precheck in SDDC-Manager
Hi, Before you place your ESXi host in maintenance mode, power off any NSX Edge VMs that may be residing on the host and ensure that the NSX Edge VMs continue to reside on the same host For ESXi ho... See more...
Hi, Before you place your ESXi host in maintenance mode, power off any NSX Edge VMs that may be residing on the host and ensure that the NSX Edge VMs continue to reside on the same host For ESXi host, for an in-place upgrade you do not need to power off the tenant VMs and placing a host into maintenance mode before the upgrade Limitations on In-Place Upgrade For NSX-T Data Center, in-place upgrade of a host is not supported in the following scenarios: More than one N-VDS switch is configured on the host. More than 100 vNICs are configured on the host N-VDS switch. ENS is configured on the host N-VDS switch. CPU use for the hostd, nsxa, or the config-agent service is high. vSAN(with LACP) is configured on the host N-VDS switch. Layer 7 firewall rules or Identity Firewall rules are enabled. VMkernel interface is configured on the overlay network. NSX-T Data Center Upgrade Guide VMware, Inc. 8 Service Insertion has been configured to redirect north-south traffic or east-west traffic. A VProbe-based packet capture is in progress. For ESXi hosts with version 7.0 and later, when upgrading from NSX-T 3.1 or later, in-place upgrade is not supported in the following scenarios: More than 1000 vNICs are configured on the host N-VDS or the VDS switch. CPU use for the hostd, nsxa, or the config-agent service is high. Layer 7 firewall rules or Identity Firewall rules are enabled. Service Insertion has been configured to redirect north-south traffic or east-west traffic. A VProbe-based packet capture is in progress. The nsx-cfgagent service is not running on the host. refer step-by-process document  
Hi, Migration to VMware NSX-T Data Center (NSX-T) is top of mind for customers who are on NSX for vSphere (NSX-V). Broadly speaking, there are two main methods to migrate from NSX for vSphere to NSX... See more...
Hi, Migration to VMware NSX-T Data Center (NSX-T) is top of mind for customers who are on NSX for vSphere (NSX-V). Broadly speaking, there are two main methods to migrate from NSX for vSphere to NSX-T Data Center: In Parallel Migration and In Place Migration. Example: Partial Migration Let us say that your organization wants to migrate only the NSX-v Distributed Firewall configuration to protect the flow of east-west traffic in the newly deployed NSX-T Data Center. To achieve this goal, use the following high-level migration workflow: Deploy the new NSX-T Data Center environment on a separate hardware. Compute clusters for NSX-v and NSX-T Data Center environments must be different because both cannot coexist on the same hosts. Management and Edge Clusters might be shared with both environments. Create the NSX-T network topology and configure the necessary network services. Configure an NSX-T Edge bridge to extend the Logical Switch in NSX-v to an overlay segment in NSX-T. Use the migration coordinator to migrate the Distributed Firewall configuration. Switch the default gateway to the NSX-T Data Center environment. Use NSX-T Edge bridge and vSphere vMotion to migrate workload VMs to the overlay segment in NSX-T. Migrate the Security Tags to the workload VMs in NSX-T. Important:When you use the lift and shift approach to migrate the DFW configuration from NSX-v to NSX-T, you must run the DFW-only migration mode of the migration coordinator only once. After the DFW configuration is migrated to NSX-T, you must not update the DFW configuration in your NSX-v environment and run the DFW-only migration mode again. Running the DFW-only migration mode multiple times is not recommended. Please refer to the below link. Migrating Distributed Firewall Configuration      
Hi, Please refer to the below link it is explained in step-by-step with screenshots, this article will help you. https://vxplanet.com/2021/06/20/nsx-t-federation-part-11-site-failures-and-network-r... See more...
Hi, Please refer to the below link it is explained in step-by-step with screenshots, this article will help you. https://vxplanet.com/2021/06/20/nsx-t-federation-part-11-site-failures-and-network-recovery/
Hi, But under those circumstances unable to delete a Segment or logical switch from the NSX-T database due to dependency. Common known dependencies are listed below: Ensuring deletion of Router Po... See more...
Hi, But under those circumstances unable to delete a Segment or logical switch from the NSX-T database due to dependency. Common known dependencies are listed below: Ensuring deletion of Router Port on Tier-0 or Tier-1 mapped to the Segment as downlink. Also, make sure that there are no workloads mapped to the Segment or Logical Switch No Bridging Profile attached to the Segment. refer below url it is explained. https://www.livefire.solutions/uncategorized/do-you-fail-to-delete-a-nsx-t-2-4-segment-or-logical-switch-via-simlified-ui-or-adanced-ui/   Please mark "Helpful" or "Correct Answer" if applies. Appreciate it.
Nice article
We are pleased to announce the introduction of VMware NSX Advanced Firewall for VMware Cloud on AWS, which takes the network security capabilities of VMware Cloud on AWS SDDC to a new level. Adding N... See more...
We are pleased to announce the introduction of VMware NSX Advanced Firewall for VMware Cloud on AWS, which takes the network security capabilities of VMware Cloud on AWS SDDC to a new level. Adding NSX Advanced Firewall features allows organizations to define security policies at Layer 7 while enabling deep packet inspection across all vNICS within the software-defined data center (SDDC).      NSX Advanced Firewall capabilities help you secure your applications against a never-expanding set of threats on the internet. Specifically, it includes a robust set of networking and security capabilities that enable customers to run production applications in the cloud.  This capability allows you to:  Detect attempts at exploiting vulnerabilities in your workloads.  Gain protection against vulnerabilities inside your SDDC with granular application-level security policies.  Reduce the attack surface of your workloads by allowing only the intended application traffic to run in your SDDC.  Seamlessly provide inspection for all traffic without a single inspection bottleneck.  Achieve your compliance goals.  Customers can purchase the NSX Advanced Firewall as an add-on in VMware Cloud on AWS. 
Hi, Make sure your following the same process in the below url. https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-0FC85023-C5A5-414B-867D-8EACAAFC080D.html
Modern apps need to run in multi-cluster, multi-cloud environments across a mix of traditional and microservices architectures. In this context, enterprise platform, infrastructure, and operations te... See more...
Modern apps need to run in multi-cluster, multi-cloud environments across a mix of traditional and microservices architectures. In this context, enterprise platform, infrastructure, and operations teams are presented with unique challenges in securely connecting and managing modern workloads, in delivering scalable services, or bridging between traditional VM workloads and containers, and supporting production operations for modern apps.   VMware recently introduced the “VMware Modern Apps Connectivity solution”, which brings together the advanced capabilities of Tanzu Service Mesh (TSM) and VMware NSX Advanced Load Balancer ALB (formerly Avi Networks) address today’s unique enterprise challenges.