Latest Posts



Translate

Total Pageviews

Thursday, 14 May 2015

Network Profiles in vRealize Automation 6.x

Network profiles define IP addresses and subnets that are used in deployments:
•Can use standard switches, distributed switches, or logical switches
•Uses IP pools for static IP assignments

vRealize Automation supports the following types of network profiles:
•External
•Routed
•Network address translation (NAT)
•Private

External Network Profile
External network profiles are for connecting an application to a precreated network:
•For example, an existing VXLAN or VLAN-backed network that you want to connect component virtual machines to, potentially for multiple applications. This topology is a multitier, single flat network topology.

Routed Network Profile

Using routed network profiles, virtual machines can use a dynamically created network with routed access to the enterprise network:
•The subnets that the machines connect to are reachable to the outside.
•Uses an NSX Edge gateway for external access.
vRealize Automation Routed Gateways
Blueprints with routed network profile must use a routed gateway to talk to external networks.

Routed gateway is defined at the Reservation level for routed and external profiles:
•Only one gateway per external network profile
•Determines whether distributed logical router or NSX Edge gateway is used by a routed network Profile

NAT Network Profile
NAT network profiles allow virtual machines to use a dynamically created network with NAT to access external networks:
•Used when applications have overlapping IP subnets.
•One-to-many and one-to-one NAT supported.
•vRealize Automation programs destination NAT and source NAT rules for access.


Private Network Profile
Using the private network profile, virtual machines can use a dynamically created isolated network when external connectivity is not required