NetworkGalaxy - by Prashant Sahu

 In this blog post we'll see step by step configuration of NSX-T 1. Add Compute Manager 2. Create Transport Zones as following      a. One Overlay Transport Zone for Host and Edge Transport Nodes      b. Two VLAN Transport Zones. One for Host Transport Nodes and another for Edge Transport Node. (having two separate VLAN transport zones is not necessary, a single VLAN Transport Zone can be used Host and Edge Transport zones) 3. Create Uplink profile for Host Transport Node      In our design, we are using LAG consisting of two uplink on Host Transport Nodes. LAG is already created on vCenter ESXi hosts. Transport VLAN is the VLAN used for Host TEP IP address pool. There is no need to specify the MTU size in Host Uplink Profile, as we are using converged VDS in our design and MTU settings need to configured in VDS (on vCenter).     MTU Settings on VDS 4. Create IP pool for Host Transport Nodes. In our case, we would be using DHCP. 5. Create Host Transport Node Profile     Type: VDS (

 There may be times when you  want to get a report that contains information of all VNETS along with their subnets and address prefixes. You might have question, how to export or backup Azure VNET or subnets information into CSV.  This script will export Azure Virtual Network information along with subnets and address prefixes of all Active subscriptions into a CSV.

So you have have created a PowerShell script to run a job quickly, but now you want to automate that PowerShell Script at a scheduled interval. For this you can use Azure Automation account where you can add you PowerShell script as a runbook and schedule that runbook at a desired time interval. In addition to the script that you have created, you also need to add some additional lines to make Automation account use a connection. Also note that if your script is performing some action (read or write) on any other subscription where the automation account is created, then you'll have to grant Automation Account's Runas account, the access of other subscriptions (You can refer the Microsoft article here. )

There could be many use cases where you may want to export Network Security Groups into CSV. You might have question, how to export or backup Azure Network Security Groups into CSV. Here is the PowerShell script that you can use to export Azure Network Security Groups into CSV using PowerShell script. This script will export Network Security Group along with rules of all Active subscriptions into a CSV.

 There could be many use cases where you may want to export Azure route tables into CSV. Here is the PowerShell script that you can use to export Azure Route Tables into CSV using PowerShell script. This script will export Azure Route Tables along with routes of all Active subscriptions into a CSV.

 In this post we'll be setting up a VIP with a backend pool of three nodes. We have details of backend node IP addresses, which are given by developer team, and VIP address is allocated/secured by us. In our last post, we looked at F5 BigIP Initial Setup and Configuration . First thing first, so lets create an A record in DNS for application FQDN pointing to Virtual Server IP address.

 In this blog post we'll setup and configure a standalone F5 Application Delivery Controller (commonly referred as load balancer). We'll be using a BigIP VM appliance for this lab. Before we begin, we should have following information handy. BIG-IP base registration key Internal/External self IP address, netmask, and default gateway IP address on the management route

 In this playbook, we we'll see how we can get display of multiple show commands in stdout_lines format. We can make use of loops (or with_items) for submitting multiple commands, but debug output with stdout_lines does not gives the formatted result as it would give for single command. So in case of multiple commands, we can debug the output of each command separately in stdout_lines format.

DNS terminology is complex and confusing, so much so that not just one, but two RFC's have been written just trying to clear up what each term means (RFC 8499 and RFC 7719). Below are the terms: 1. FQDN - FQDN stands for Fully Qualified Domain Name, which is the complete domain name for a host on the Internet. The FQDN has two parts: the hostname, and the domain name. e.g. in foo.example.com, foo is the hostname, and example.com is the domain name.

If you have already worked on Azure Cloud or AWS and now you are moving or expanding your cloud to Google, then you might want to see what the former cloud service providers' services translate to in Google Cloud. So here you can get the answer. Map Microsoft Azure services to Google Cloud Products https://cloud.google.com/docs/compare/azure#service_comparisons Map  AWS services to Google Cloud Products https://cloud.google.com/docs/compare/aws#service_comparisons