Merge pull request #78684 from sharaths-cs/sharaths

Added images to concept articles

Author: GitHubber17

articles/vmware-cloudsimple/cloudsimple-azure-network-connection.md

@@ -36,10 +36,14 @@ Azure network connection allows you to:
 
 Private Clouds can be connected to your Azure resources using ExpressRoute.  You can use this connection to access different resources running in your Azure subscription from your Private Cloud.  This connection allows you to extend you Private Cloud network to your Azure virtual network.
 
+![Azure ExpressRoute Connection to virtual network](media/cloudsimple-azure-network-connection.png)
+
 ## ExpressRoute connection to on-premises network
 
 You can connect your existing Azure ExpressRoute circuit to your CloudSimple region. ExpressRoute Global Reach feature is used to connect the two circuits with each other.  A connection is established between the on-premises and CloudSimple ExpressRoute circuits.  This connection allows you to extend your on-premises networks to Private Cloud network.
 
+![On-premises ExpressRoute Connection - Global Reach](media/cloudsimple-global-reach-connection.png)
+
 ## Next steps
 
 * [Obtain peering information for Azure virtual network to CloudSimple connection](https://docs.azure.cloudsimple.com/virtual-network-connection)

articles/vmware-cloudsimple/cloudsimple-vlans-subnets.md

@@ -13,6 +13,8 @@ manager: dikamath
 
 CloudSimple provides a network per region where your CloudSimple service is deployed.  The network is a single TCP Layer 3 address space with routing enabled by default.  All private clouds and subnets created in this region can communicate with each other without any additional configuration.  You can create distributed port groups on the vCenter using the VLANs.
 
+![CloudSimple Network Topology](media/cloudsimple-network-topology.png)
+
 ## VLANs
 
 VLANs (Layer 2 network) are created per private cloud.  The Layer 2 traffic stays within the boundary of a private cloud, allowing you to isolate the local traffic within the private cloud.  A VLAN created on the private cloud can be used to create distributed port groups only in that private cloud.  A VLAN created on a private cloud is automatically configured on all the switches connected to the hosts of a private cloud.
@@ -30,6 +32,10 @@ A Private Cloud is created as an isolated VMware stack (ESXi hosts, vCenter, vSA
 Minimum vSphere/vSAN subnets CIDR range prefix: **/24**
 Maximum vSphere/vSAN subnets CIDR range prefix: **/21**
 
+> [!CAUTION]
+> IP addresses in the vSphere/vSAN CIDR range are reserved for use by Private Cloud infrastructure. Don't use an IP address in this range on any virtual machine.
+
+
 ### vSphere/vSAN subnets CIDR range limits
 
 Selecting vSphere/vSAN subnets CIDR range size has an impact on the size of your Private Cloud.  Table below shows the maximum number of nodes you can have based on the size of vSphere/vSAN subnets CIDR.
@@ -71,4 +77,4 @@ Example:
 
 ## Next steps
 
-* [Create and manage VLANs and Subnets](https://docs.azure.cloudsimple.com/create-vlan-subnet/)
+* [Create and manage VLANs and Subnets](https://docs.azure.cloudsimple.com/create-vlan-subnet/)

articles/vmware-cloudsimple/cloudsimple-vpn-gateways.md

@@ -31,6 +31,8 @@ Use cases for site-to-site VPN include:
 * Convenient transfer of VM templates, ISOs, and other files from your on-premises resources to your private cloud vCenter.
 * Accessibility of workloads running on your private cloud from your on-premises network.
 
+![Site-to-Site VPN connection topology](media/cloudsimple-site-to-site-vpn-connection.png)
+
 ### Cryptographic parameters
 
 A site-to-site VPN connection uses the following default cryptographic parameters to establish a secure connection.  When you create a connection from on-premises VPN device, the parameters must match.