Skip to main content

8.x Network profiles

There are different types of network profile available - Existing, Public, Private, Routed and Outbound in vRealize Automation which uses default IP Address Management(IPAM). Apart from these network profiles we can assign a static IP to a blueprint as well.

Creation of a blueprint with static IP
 
1. Specify a Static IP Address for Your Virtual Machine

This static IP address must be an unused address in the defined range of static IP address on the network profile.

Verify that your YAML code appears similar to the screenshot 


2. Configure Your vSphere Network



Note: When you TEST the deployment it reserves a static IP to run the test. You may need to wait for 30 minutes for the IP to return to available pool.

Network profile Types

1. Existing Network profile

These are the networks which are discovered from vSphere and associated NSX-T datacenter cloud accounts. No need of creating on-demand networks. You can define network CIDR, default gateway and DNS server for the networks. Networks can be set as default for Zone and enable support for external access.

Use the existing discovered networks to deploy blueprints



2. Public Network profile

This network allows external access. When the existing network that are flagged as public it will match the network component in a blueprint that have a network type: public property.


3. Private Network profile

This isolates provisioned VMs from the external access. A private network can be created in one of the following ways
  • Create on-demand network(Do not specify an external n/w, Tier-0 router or Edge cluster)
  • Create on-demand security group(Define discovered/deployed existing network by NSX-T DC
Note: vSphere networks are not supported



4. Routed Network profile

These are on-demand network profiles created during provisioning. It must use a routed gateway to access external networks.Network component in the blueprint must be selected as networktype:routed

Deploying one VM with Routed network profile creates
  • One logical switch
  • One DHCP server
  • One Tier-1 router
  • connects a Tier-1 router to Tier-0 router
  • Advertise NSX routes

Note: Cloud agnostic network does not support routed network profiles

5. Outbound Network profile

These are on-demand networks created during provisioning. An outbound network profile defines internal and external networks that use a translation table for mutual communication.

Deploying one VM with Outbound network profile creates
  • One logical switch
  • One DHCP server
  • One Tier-1 router
  • Connects a Tier-1 router to Tier-0 router
  • Creates one-to-many SNAT rule

Labels:

Comments

Post a Comment

Popular posts from this blog

Deleting stale kubernetes clusters in vCD

Unlike the previous version the CSE 4.x is a stateless appliance and its data is stored in VMware Cloud Director Database.  The cluster creation and deletion compared with CSE 3.x version has improved. Besides, there are some scenarios where the cluster deletion is failing even when the "Force Delete" option is chosen. We can use vCD API explorer to delete it, the following are the API queries you can execute  Under definedEntity POST /1.0.0/entities/{id}/resolve DELETE /1.0.0/entities/{id}
Post a Comment
Read more

Manage RabbitMQ using VCP LCM

I have been working in vCD for quite some time, and most of the implementation engineers or consultants faced issues during the deployment or upgrade of RabbitMQ for the vCD message queuing service. From vCD 10.2.2, we can use the built-in MQTT client instead of RabbitMQ however, for VCD multisite configuration or some 3rd party applications need RabbitMQ, such as Veeam or VMware HCX. Using the VCP LCM, we can create a new RabbitMQ environment or manage an existing environment. The reason for this blog is that none of the VMware documentation has the information that registering an existing RMQ instance is only going to work if the RMQ instance was previously deployed by the VCP LCM (or at least, if it is a similar setup based on a Bitnami RMQ VM). Other RMQ instances (e.g., running in CentOS) are not supported and cannot be imported into the VCP LCM 1.5. I hope this information will be useful for someone who is performing green field deployment or upgrading an existing setup. ...
Post a Comment
Read more