# Networks Configuration

Once the network integration is created, networks can be created using the specific network integration that was created. Networks essentially define the VLAN that they represent along with other attributes such as the subnet’s IPv4 prefix, IP address allocation method, gateway address, DNS, etc. The screenshot below shows those details.

The VLAN Trunks specifies the trunk VLANs to be added when this network is consumed by an instance. The VLAN ID field represents the primary VLAN for this network. This VLAN is configured as the untagged VLAN when this network is consumed by an instance.

The Network Service corresponds to the network integration that was created. This specifies that the network is to be created in the infrastructure (switches) specified in the network integration selected.

The Private checkbox specifies that the network is a private network. By default, all networks are public. If private is selected, the primary VLAN in this network is not configured on the uplink connection. This would render them unreachable from outside of the cloud infrastructure. This is typically used for workload networks that are used to communicate between only the workload servers and other infrastructure within the private cloud.

The configuration of a network will result in the primary VLAN in that network being provisioned on the network switches. The server ports are configured when those networks are consumed during the provisioning of a compute instance.

**Subtopics**  

- **[Creating Network Using the ArubaCX Integration](https://support.hpe.com/hpesc/public/api/document/sd00008375en_us/render?page=GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.html)**
- **[Network Usage](https://support.hpe.com/hpesc/public/api/document/sd00008375en_us/render?page=GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.html)**
