Видео

Hi Please WhatsApp us on +917083939150 and we would be happy to assist you with your queries.

Hi If you are asking about Traditional vSphere Networking, if 2 VMs connected to same vSwitch and part of same L2 network. In this case, traffic will not leave the ESXi host and it will not reach the physical firewall located at L3. Packet forwarding will happen within vSwitch itself.

Hi This is our NSX-T Zero to Hero Deep-Dive Program. Tentative duration will be 8-10 weekends. For more details, please dm us on +91 7083939150

Hi This is our NSX-T Zero to Hero Deep-Dive Program. Tentative duration will be 8-10 weekends. For more details, please dm us on +91 7083939150

@@govmlab fee pls?

34999/- INR is the Fees of vSphere 8.x Deep-Dive Program.

@@govmlab the fee is included for nsx-t ? or it is only for vSphere 8.x ?

Hi This is our deep-dive program designed for L3 & Senior level job roles. No worries. We will introduce VMware NSX ICM program soon. This program will be at lesser price because it will prepare professional for L1/L2 administrator job roles. Wait for few months when we launch this program.

@@govmlab if you make it for 20k i think many people will join this course

Hi There are Use cases and Advantages of deploying dedicated T0 router for each T1 tenant. Few of them are listed as below: 1. Enhanced Security Isolation: Traffic Segmentation: By having a dedicated T0 router, each tenant's traffic is isolated, reducing the risk of cross-tenant traffic snooping or interference. 2. Dedicated Policies: Separate T0 routers allow for tailored security policies, firewall rules, and NAT configurations specific to each tenant, enhancing security. 3. Resource Management: Dedicated T0 routers enable better allocation of resources such as bandwidth, CPU, and memory for each tenant, ensuring consistent performance. 4. Scalability: This setup can scale more effectively with tenant growth, as resources are independently managed for each tenant. There are other benefits as well such as operational flexibility, compliance and regulatory requirements and performance optimization. Just to conclude, Implementing dedicated T0 routers for each T1 tenant can significantly enhance the overall security, performance, and manageability of a multitenant network environment, making it a preferred approach in scenarios demanding high isolation and customization. We hope you find this answer useful. Keep Sharing and Enjoy Learning with GoVMlab!!

Sorry, We didn't understand your query. If you want to join our RUclips Membership program then click on link below ruclips.net/user/govmlabjoin

Sure...JYI, these videos are just a glimpse of our Zero to Hero Deep-Dive Programs. If you are interested in such in-depth learning then feel free to connect with us on WhatsApp no. +917083939150. We would be happy to assist you. Keep Sharing and Enjoy Learning VMware with GoVMlab.

Hi Sorry but we can't help you much on this. Membership is capability offered by RUclips to content creators. We don't have any control over payment gateway methods. As a content creator, we only have access to publish our lectures. For payment related assistance, we would suggest you check out with RUclips Support team. Sorry for not being able to help you on this issue. Keep Sharing and Enjoy Learning VMware with GoVMlab.

Thank You!!

Hi Glad to know that you find our lectures informative and useful. Keep Sharing and Enjoy Learning VMware with GoVMlab.

Hi Thanks for your appreciation. Yes, we do have Zero to Hero Deep-Dive program on vSphere8. Feel free to connect with us over WhatsApp no. +917083939150 for VMware program related queries.

Hi Srinivas We totally agree with you. This video is just a glimpse of Virtual Networking. We have dedicated vSphere Networking Deep-Dive Program where we spent almost 15-16 hrs explaining vSphere Networking and Its Architecture and Datapath. This video is just a glimpse of vSphere Networking. If you are interested in such deep-dive learning then feel free to reach out to us.

Hi Vishal Thanks for your feedback & we appreciate it but can't help much on this.... If you find our videos confusing then we would advise you to check out some other platform which might help you to understand VMware technology better than us. Regarding charges also, If you are interested in our member-only content then it will always be chargeable. We do have free content as well which you can refer if you want to. Thanks once again!!

@c0mrad3 Each VM should be connected to a Portgroup irrespective of whether VMs resides on same ESXi or different ESXi Host. We didn't understand your comment about uplink per host vSwitch. If traffic has to leave ESXi host then it always requires uplink. Without Uplink connectivity, How Traffic leaves the source ESXi host and enters into Destination ESXi host. We hope it clarify your doubts.

@@govmlab sorry for the confusion. In short how can VMs from different hosts talk to each other using vSS? Tried to add PGs in different hosts, configured VMs to use it, added uplink but they can’t still ping each other. Hope this make sense. Thank you!

Hi We are not sure if we have understood your query correctly about custom local ID. If you are referring to Adding local users to vCenter Server and assigning permissions. You need to add those Local users to vCenter Inventory and then you can create custom roles/super admin roles and map it those users. That's the standard procedure to define Role Based Access Control in VMware vSphere. Please refer this docs from VMware. docs.vmware.com/en/VMware-vSphere/8.0/vsphere-vcenter-configuration/GUID-CAB3C0D8-978E-47AE-82D8-0D95C4005B41.html docs.vmware.com/en/VMware-vSphere/8.0/vsphere-security/GUID-18071E9A-EED1-4968-8D51-E0B4F526FDA3.html#GUID-18071E9A-EED1-4968-8D51-E0B4F526FDA3

Hi vSphere Networking only provides Layer2 switching capabilities only. If you have 2 VMs connected to 2 different port group configured with 2 different VLAN ( two IP subnets). In that case, communication will not work because vSphere Networking doesn't provide routing capabilities. NSX provides such routing capabilities in Hypervisor itself. Where 2 VMs connected to different network can communicate with each other without leaving ESXi host. That's called Logical Routing in NSX. Just to conclude, vSphere Networking only provide Layer2 Switching capabilities. We hope it clarifies your doubts. Feel free to reach out to us if you have any further query. Keep Supporting and Enjoy Learning VMware with GOVMLAB!!

Hi vSphere Networking only provides Layer2 Switching capabilities. It means that if 2 VMs are connected to 2 different Port groups configured with 2 VLAN ( 2 IP Subnets), You would require physical router to be placed in external network to enable communication between these VMs. vSphere Standard/Distributed Switch doesn't allow communication between VMs configured with 2 different VLANs or IP Subnets. In NSX, it is supported because ESXi Hypervisor has routing capabilities, and it can allow communication between 2 VMs configured with 2 IP subnets. This NSX capability is called Logical Routing. ESXi provides logical routing in Hypervisor itself. Just to conclude, vSphere Networking only provides Layer2 Switching capabilities. For L3 networking, you might have to use NSX implementation. We hope it clarifies your doubt. Keep Sharing and Enjoy Learning VMware with GOVMLAB!!

@@govmlab Thanks Sir!

@Rohit That's correct. We don't require tagging to be configured at pSwitch level. we always configure pSwitch ports in trunk mode. When we configure VLAN tagging at both vSwitch and pSwitch level then packet will drop.

@@govmlab Yes, I agree but some dedicate network like vSan, we don't need to configure trunk mode..for this we configure access mode vLAN

Thanks for liking it!! Keep Sharing and Enjoy Learning VMware with GOVMLAB!!

Hi Please click on below mentioned link to join our Membership Program. ruclips.net/channel/UCwYRe6puHkV-ySqUuLOiEBgjoin

Thanks Vishal for your kind appreciation!! Such positive feedback from our learners inspires us to create more valuable content for our youtube community. Keep supporting us and enjoy learning VMware with GOVMLAB!!

@@govmlab thanks for creating wonderful content on this channel..🎉🏆🙏🤩

Hi @Ramsuthar I think you didn't understand the concept of Snapshot and How it works. Snapshot is the chaining process. If you delete the Snapshot C, it's delta changes has to be written in it's parent disk.... We would suggest you to please read some VMware white paper about Snapshot architecture and implementation. If you are interested in deep-dive learning at the architecture level then feel free to reach out to our team as well on WhatsApp +91 7083939150 where we nurture professionals and help them to clarify their conceptual understanding w.r.t vmware architecture.

Thanks Vishal for appreciating our hard work and efforts creating these lectures. Keep Sharing and Enjoy Learning VMware with GOVMLAB!!

@YumnaMugheez Thanks for appreciating our hard work and efforts creating these lectures!! Keep Sharing and Enjoy Learning VMware with GOVMLAB!!

Thanks @nick Keep Sharing and Enjoy Learning VMware with GOVMLAB!!

@mine sorry, we couldn't understand your question completely. In virtual environment, your physical switch port should be configured in Trunk mode to allow multiple VLAN traffic to pass through that switch port where vmnicX is connected. For Management Network connectivity, VMK0 adapter is used. You should trace VMK0 mac address in physical switch. We hope it answer your query.

@user-ex3vm Thanks for your kind feedback. We are glad to know that you find our lectures useful. Keep Sharing and Enjoy Learning VMware with GOVMLAB.

@shubham Sorry but your question is not clear to us. Just to answer your query, cascading of virtual switches is not supported in VMware. You can't connect multiple individual switches to single common switch. Feel free to reach out to us if you want to understand vSphere Networking more in depth.

Thanks for your kind feedback. We really appreciate it. We will make sure to reduce our pace in upcoming videos.

@siumt Thanks for your kind feedback. We really appreciate it. Keep Sharing and Enjoy Learning VMware with GOVMLAB!!

@kendrift Thanks for your kind feedback. We really appreciate it. Keep Sharing and Enjoy Learning VMware with GOVMLAB!!

@gunjan Unfortunately, Creating DNS server is not the scope of this lecture. These are very generic topics of server administration. You can refer any video about configuring AD domain controller as DNS server. It's pretty straightforward. Configuring DNS server and creating A records has nothing to do with VMware specific learning. In our channel, we focus more on the VMware specific learning. We hope it clarifies your doubts. Keep Sharing and Enjoy Learning VMware with GOVMLAB!!

@mohammad if you want to see Members-only content published on our youtube channel. You will have to join our RUclips Membership Program. you will be able to access all the members only content only after joining our membership program. click on link below to join that program: ruclips.net/user/govmlabjoin

@danishmaan Sorry but we don't have any plan for GCVE tutorial in coming weeks. Unfortunately, we don't see much interest among learners about GCVE so we are focusing more on creating tutorial on basic product such as vSphere , NSX etc..

Thanks!! Keep Sharing and Enjoy Learning VMware with GOVMLAB.

Thank you for your kind feedback!! Keep sharing and Enjoy learning VMware with GOVMLAB!!

@uday Please refer below playlist for NSX-T lectures. ruclips.net/video/NDUWvN4rl7Y/видео.html

@danish Thanks for your kind suggestion. We will create it soon.

Unfortunately, these videos can't be sorted in specific sequence. We have created these videos in random sequence. Indexing of these videos would be quite difficult for us. Thanks for your kind feedback and suggestions.

Unfortunately, these videos can't be sorted in specific sequence. We have created these videos in random sequence. Indexing of these videos would be quite difficult for us. Thanks for your kind feedback and suggestions.