# Adding ArubaCX Integration

## About this task

NOTE

Making full use of the HPE Morpheus Enterprise ArubaCX integration requires credentials for Aruba CX switch pair with API access granted and read/write access to switch configuration. See ArubaCX 8325 documentation for more information on user rights administration in that product.

## Procedure

1. Navigate to Administration > Integrations
2. Select + New Integration > Other > ArubaCX 

   ![../../_images/arubacx_new_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00008058en_us/GUID-D9808197-A648-4D9C-864F-4A60FC8C7A35-high.png)
3. Enter the following: 

   NAME
   :   Name of the integration in HPE Morpheus Enterprise

   ENABLED
   :   Deselect to disable the integration

   USERNAME
   :   User username for all switches

   PASSWORD
   :   User password for all switches

   IPV4 ADDRESS
   :   Primary switch IP address for switch pair 1

   IPV4 ADDRESS
   :   Secondary switch IP address for switch pair 1

   IPV4 ADDRESS
   :   Primary switch IP address for switch pair 2

   IPV4 ADDRESS
   :   Secondary switch IP address for switch pair 2

   IPV4 ADDRESS
   :   Primary switch IP address for switch pair 3

   IPV4 ADDRESS
   :   Secondary switch IP address for switch pair 3

   IPV4 ADDRESS
   :   Primary switch IP address for switch pair 4

   IPV4 ADDRESS
   :   Secondary switch IP address for switch pair 4

   UPLINK LAG INTERFACE
   :   Name of the uplink LAG interface (default is 'lag1')
4. Select SAVE CHANGES

## Results

Upon save the ArubaCX Network integration will be created. See example screenshots created with and without leaf-spine enabled:

![../../_images/arubacx_settings.png](https://support.hpe.com/hpesc/public/api/document/sd00008058en_us/GUID-5D534A49-DDA0-4E90-856C-F6244B48C327-high.png)![](https://support.hpe.com/hpesc/public/api/document/sd00008058en_us/GUID-74EB5EDA-F973-4471-B1D1-74DBF6F4AAA4-high.png)

NOTE

All fields can be edited after saving.

Sample Reference Architecture for EVPN Configuration

1. Minimum four leaf switches, two spine switches, and one core switch
2. At least two servers in separate racks
3. Configure switches to encapsulate L2 traffic via VXLAN overlay across racks
4. VMs on servers in different racks communicate through the EVPN switch configuration
5. Route traffic between racks through spine switches
