Skip to main content


Showing posts from April, 2020

PowerCLI | Who wants this engine?

Hi Guys, In my last post, I shared a few PowerCLI commands to take a snapshot but today I changed the look and feel. I tried to create an engine\application kind of thing where you just need to press 1, 2 and 3 and all your work related to your snapshot will be done. No need to login GUI and tasks will be done in a faster way. It helped me a lot and I hope it will be helpful for you as well. Tell me if anyone wants this engine now. Thank you, vCloudNotes

vCenter | Snapshot Operations

Hi Folks, Today someone asked about the snapshot. Like if I need to take snapshot from PowerShell then how to? if I quiesce the snapshot in PowerShell then how-to etc. etc. so, I thought to summarize as many as I can snapshot operations in a single page and share with all. Here you go.. Connect-VIserver VC-IP #To take a snapshot for a single VM without quiescing and memory $VM = read-host "Enter the VM Name " New-Snapshot -VM $VM -Name vcnotes_snap -Description "This is test snap" #with quiesced on New-Snapshot -VM $VM -Name vcnotes_snap -Description "This is test snap" -Quiesce #With memory state New-Snapshot -VM $VM -Name vcnotes_snap -Description "This is test snap" -Memory #with Memory and quiesce both New-Snapshot -VM $VM -Name vcnotes_snap -Description "This is test snap" -Memory -Quiesce #take snapshot for mulitple VMs and with quiesced off and no memory state foreach ($AVM in (Get-content -path C:\Temp\vmlist.txt)){New

Free Training and Certifications

Hi All, Free training and certification currently available for April and May. Make Use of it. 1. Microsoft - Azure certification 2. AWS - All AWS technology 3. IBM - All IBM technology 4. Oracle University - Cloud Infrastructure and Autonomous Database 5. Fortinet - NSE1 and NSE2 6. Palo Alto - Networks 7. Cisco - Cyber Security 8. Qualysguard - Vulnerabilty management 9. Nessus - Vulnerabilty management 10. SAN's - cyber security 11. Homeland security - ICS Security 12. Coursera - Cloud courses 13. Pluralsight - All Training 14. Sololearn - All Training  Keep Learning! Keep growing Thank you, vClou

NSX-T | Micro-Segmentation

Hello Guys, Hope you are doing well wherever you are and I pray for everyone's life. Stay Home & Stay Safe! So, as I promised, I am writing about micro-segmentation means DFW (Distributed FireWall) in NSX-T. This post is for those guys who knows how to configure it in NSX-V. In case, you want to understand DFW in detail then click here . First of all, let's understand the Connectivity Strategy in NSX-T. 1. Blacklist (with or without logging) - This is the default option which creates an allow all rule in DFW. It also does mean that micro-segmentation is off. 2. Whitelist (with or without logging) - It creates deny all rule in DFW. To allow any traffic, we have to create allow rules. It block DHCP traffic as well if not allowed via allow rule 3. None - This option will disable both Blacklisting and Whitelisting of firewall rules. This option is useful when you have already applied rules from older version of NSX-T In comparison of NSX-V, above terms were not i

Intro to K8s

I thought to put some definition or short description of Kubernetes terms for my reference. Detailed information you can obviously find on Hope you will find it good too. Before I explain Kubernetes, I think it is much useful to understand that what is Container. I know that web is already full with such definitions so I will try to explain in much shorter and easiest way. So Let's start with Container . Below image is self-explanatory. Some people refer it as VM but difference is pretty clear in below image. Hope it is clear to you that why it is more useful to use containers. It is faster, remove dependency of guest OS and it doesn't bother if target device is private datacenter, a public cloud or developer's personal laptop. In container, we can simply deploy our application without the need of any hosting OS. So now, when we know a bit about container, let's think about what is Kubernetes . So, to explain

NSX-T | Basic Routing Setup

Hi Folks, As most of the techie guys knows, who are dealing with cloud technologies and specially dealing with VMware cloud applications that NSX-v will sunset soon. To replace it VMware has already released NSX-T which provides wider support of cloud technologies, easier implementation and independent design approach. NSX-v was built only for vSphere environment whereas NSX-T can work with any cloud vendor, for example MS Azure, AWS and even with Openstack. Now a days, integrating k8s with NSX-T is in trend. I will try to create a post on that as well but in today's post let's see how you can setup basic east-west and north-south routing in NSX-T. It will clear many doubts that you might have like what is T0, T1 router? What is SR and DR? and many more. So, While explaining and demonstrating it, I will be using below topology. So, let's see how I did it. Steps are same as in NSX-v, just look and feel is different. Just remember that Logical switch in NSX

vROPS | Cluster Health-Check Script

Hi Guys, In vROPS, when we deploy\create multi-node cluster then sometime due to large collection of metrics and alerts vROPS database get full and start creating many issues like metric graphs doesn't populate correctly, metrics collection start getting skip the timeline, vROPS UI get slow etc. In order to maintain the health of vROPS cluster, you can use below script which gives very clear and exact information on its metric and alert collections, its current size and state of all active nodes in cluster, space in each directory of master node and many more things. I got this script from VMware while working on such an issue so thought to share with all. After all, sharing is caring. Isn't it? Below is the script. echo -e "\e[1;31mHOSTNAME:\e[0m" > $HOSTNAME-status.txt | hostname >> $HOSTNAME-status.txt;getent hosts | nslookup >> $HOSTNAME-status.txt; uname -a >> $HOSTNAME-status.txt; echo -e "\e[1;31mDNS CONFIGURATION:\e[0m&qu

NSX | PacketWalk

Hi Guys, Today I thought to put this kind of packetwalk from my VM in vxlan upto the physical firewall. I checked on internet but couldn't find such exhaustive informatin. I hope it will be help for many of you. Please leave your comment as a feedback and let me know how you found it. In case of any doubt or you see anything which I should include in below snippet, feel free to say via your comment. Thank you, Team vCloudnotes

Network Migration | VLAN to VXLAN

Hi Guys, Today I thought to write something about how you can migrate your underlay workload (VLAN) to overlay technology (VXLAN) in NSX. So, when I say network migration, it will include migration at two levels. A. L3 migration B. VM vNIC migration A. L3 migration means:- Your current setup has VLAN and your VM's default gateway is physical switch\router\firewall whatever you have configured in your environment as shown in below image                                                                    picture - 1.1 We basically needs to migrate this default gateway from your physical switch\router\firewall to DLR\UDLR in your NSX environment. See below image                                                                                 picture - 1.2 B. VM vNIC migration means:- Just changing the mapped portgroup from VLAN to VXLAN from VM properties of a VM. Below is the referenced image.