# Networking

| S.No. | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
| --- | --- | --- | --- | --- | --- |
| 1 | Cloud Network Mode Configuration | Cloud can operate in **Unmanaged** or **Managed (ArubaCX-Int)** network modes. This choice is made during cloud creation under **Advanced Options**. | Verify the correct network mode selected during cloud creation. | Morpheus UI log | Use Unmanaged for external network control; use Managed for Morpheus-managed ArubaCX switches. |
| 2 | Unmanaged Network - Default Setup | In Unmanaged mode, Morpheus creates a minimal configuration: a default Resource Pool and a default unmanaged network. The default network is **untagged** and uses **DHCP**. | Ensure the DHCP server exists and the network is configured for an untagged VLAN. | Morpheus UI log | This allows instances to boot with connectivity without extra network configuration. |
| 3 | Unmanaged Network - Additional VLANs | Users can create additional VLANs/networks as required. | Check VLAN configuration and availability in provisioning options. | Morpheus UI log | Additional networks can be consumed by bare-metal instances. |
| 4 | Managed Network - ArubaCX Integration | Managed mode uses ArubaCX switches and requires the ArubaCX plugin. | Confirm the ArubaCX plugin is loaded in Morpheus. | Morpheus UI log | Managed networks allow Morpheus to configure VLANs on switches automatically. |
| 5 | Adding HPE ArubaCX Plugin | The plugin must be loaded to enable managed network features. Follow the procedure Adding HPE BMaaS Integration to load the plugin JAR. | Verify plugin status in Morpheus. | Morpheus UI log | Required before creating network integrations. |
| 6 | Creating ArubaCX Network Integration | Integration defines switch credentials and switch pairs (typically 2 per rack). | Verify switch IPs, username, and password are correct. | Morpheus UI log | One integration is needed per rack (switch pair). |
| 7 | Creating Managed Networks | Networks represent VLANs and include attributes like subnet, gateway, DNS, and IP allocation method. | Ensure VLAN ID, trunks, and subnet are correct. | Morpheus UI log | Primary VLAN is untagged, VLAN trunks are tagged. |
| 8 | Private Network Option | Private networks do not configure a primary VLAN on the uplink, making them inaccessible outside the cloud. | Confirm if the network should be private or public. | Morpheus UI log | Used for internal workload networks only. |
| 9 | Network Consumption During Provisioning | Networks are attached to physical or bonded interfaces. Primary VLAN is untagged, trunk VLANs are tagged. | Check interface type (physical or bond) and correct VLAN assignment. | Morpheus UI log | Supports Static Bond, LACP Bond, and Switch Independent Bond. |
| 10 | Bond Interface Configuration | Bond interfaces require two physical ports to form an aggregated link. | Ensure both physical ports are available and correctly mapped. | Morpheus UI log | Bonding provides bandwidth aggregation and redundancy. |
| 11 | Virtual Network Interfaces | Virtual networks allow tagged VLANs to be configured as IP interfaces on the server OS. | Verify if tagged networks require an IP interface. | Morpheus UI log | If not needed, do not configure the virtual interface. |
