Decision Factors to choose in between NVDS & CVDS during NSX-T deployments




Decision Factors to choose in between NVDS & CVDS

           - Prashant Pandey, VCAP-NV


During NSX-T deployment, while preparing Transport nodes we have an option to choose between NVDS(virtual switch dedicated to NSX tasks) & VDS (existing virtual switch used to manage vCenter environment)

There are few design decisions which I have tried to consolidate and capture for easy reference.



Decision Factors to choose N-VDS or Converge VDS.

N-VDS

Converge VDS

Supports older version of vSphere, prior to 7.0

Requires vSphere 7.0 or more.

Requires free pNics for uplinks

No free pNics are required, can use original VDS uplinks only.

Can only be managed in NSX and not in vCenter.

Can be centralized managed in vCenter.

Available with older version of NSX-T, prior to 3.0

Available with NSX-T 3.0 onwards

If use-case is to prepare KVM or Bare-metal for NSX,
NVDS is the only option

Available for vSphere hypervisor, 7.0 onwards


PS: Improvement points and suggestions are always welcome. J


Thank You!

Prashant Pandey


Comments

  1. Shank Mohan3 August 2022 at 14:08

    Hey mate, don't forget that NVDS will be deprecated / is deprecated with the latest release.

    ReplyDelete
    Replies
    1. Prashant Pandey12 August 2022 at 07:59

      Hey Shank, thankyou!

      Yes with 4.0 onwards, it is noted.

      Delete

Post a Comment

Popular posts from this blog

NSX-v to NSX-T workload migration with Network Coexistence via L2Bridge

Image
NSX-v to NSX-T workload migration with Network Co-existence - L2Bridging - Prashant Pandey , VCAP-NV   Use case -L2bridge is one of major use-case of workload migration from NSX-v to NSX-T along with network co-existence. Summary - There are mainly 3 use-cases for the workload migration from NSX-v to NSX-T . 1. Subnet based Migration - Shut one subnet at NSX-v  and add & advertise the same from NSX-T Pros - Easy to migrate, no addition VLAN requirement at physical network. Cons – No flexibility at Application level migration, it has be entire subnet in one go, might not be feasible in most of the production environment.   2. Network Co-existence with VMware HCX tool – Supports Network stretch with L2E feature. Pros – Network Co-existence can be achieved with ease. Cons – Separate license requires, includes extra cost.   3. Network Co-existence with L2Bridging - Supports Network stretch with layer 2 bridging feature. Pros – Netwo...
Read more

Independent Bridging : NSX-v to NSX-T In-Parallel Migration use case.

Image
                    Independent Bridging : NSX-v to NSX-T In-Parallel Migration use case. –  Prashant Pandey, VCAP-NV-2021 Agenda NSX-v to NSX-T workload migration using NSX Independent bridging option. •          Different Available Migration Approaches – High level •          Independent Bridging approach – In detail •          Customer use-case discussion – Why independent Bridging ? •          L2Bridging Readiness •          Validation & Testing Why Migrate to NSX-T ? NSX for vSphere (NSX-V) has already been out of general support since Jan/2022 & will be out of technical guidance from Jan/2023 onwards. Top of mind question for customers who have adopted NSX-V is - how do I upgrade my NSX-V based data center to...
Read more