Technical white paper

HPE Alletra dHCI switch

configuration guide
HPE Aruba 832x and HPE Aruba 6300 switches
Technical white paper

Contents
Executive summary .............................................................................................................................................................................................................................................................................................................. 3
Server, array, and switch cabling example ...................................................................................................................................................................................................................................................... 3
Network requirements for configuring an Ethernet switch ............................................................................................................................................................................................................. 4
MTU ............................................................................................................................................................................................................................................................................................................................................. 4
Flow control .......................................................................................................................................................................................................................................................................................................................... 4
Jumbo frames ..................................................................................................................................................................................................................................................................................................................... 4
VLAN .......................................................................................................................................................................................................................................................................................................................................... 5
VM network VLANs....................................................................................................................................................................................................................................................................................................... 5
Dead network VLAN .................................................................................................................................................................................................................................................................................................... 5
LLDP ........................................................................................................................................................................................................................................................................................................................................... 5
Spanning tree ...................................................................................................................................................................................................................................................................................................................... 5
Network configuration example for use with Peer Persistence ................................................................................................................................................................................................... 5
HPE Aruba 8320 or 8325 configuration example to prepare for network automation ...................................................................................................................................... 6
Task 1: Set up the initial configuration on the HPE Aruba 832x switches ................................................................................................................................................................ 7
Task 2: Set up the VSX configuration for the HPE Aruba switches .................................................................................................................................................................................. 8
Task 3: Configure a management network VLAN on ports for HPE Aruba 832x switches ....................................................................................................................10
Task 4: Connect the HPE Aruba switches to the customer network ............................................................................................................................................................................10
HPE Aruba 8320 or 8325 configuration example using manual steps...........................................................................................................................................................................11
Task 1: Set up the initial configuration on the HPE Aruba 832x switches .............................................................................................................................................................11
Task 2: Set up the VSX configuration on HPE Aruba 832x switches ..........................................................................................................................................................................12
Task 4: Create the required VLANs ............................................................................................................................................................................................................................................................12
Task 5: Add individual port descriptions for troubleshooting .............................................................................................................................................................................................13
Task 6: Assign the VLANs and configure jumbo frames and flow control for HPE Aruba 832x switches ................................................................................ 15
Task 7: Configure spanning tree ....................................................................................................................................................................................................................................................................17
Task 8: Connect the HPE Aruba switches to the customer network ............................................................................................................................................................................17
Task 9: Secure the remaining interfaces for HPE Aruba 832x switches...................................................................................................................................................................18
HPE Aruba 6300 configuration example .....................................................................................................................................................................................................................................................18
Task 1: Set up the initial configuration on HPE Aruba 6300 switches.......................................................................................................................................................................19
Task 2: Set up the VSF configuration for HPE Aruba 6300 switches .........................................................................................................................................................................19
Task 3: Configure NTP for HPE Aruba 6300 switches ............................................................................................................................................................................................................. 20
Task 4: Create the VLANs needed for HPE Aruba 6300 switches ................................................................................................................................................................................20
Task 5: Add individual port descriptions for troubleshooting HPE Aruba 6300 switches.......................................................................................................................21
Task 6: Assign the VLANs and configure jumbo frames and flow control for HPE Aruba 6300 switches ............................................................................... 22
Task 7: Configure spanning tree for HPE Aruba 6300 switches .....................................................................................................................................................................................25
Task 8: Secure the remaining interfaces for HPE Aruba 6300 switches ..................................................................................................................................................................25
Appendix A: Configuration worksheets ..........................................................................................................................................................................................................................................................26
Technical white paper Page 3

Executive summary
The HPE Alletra dHCI solution from Hewlett Packard Enterprise is a disaggregated hyperconverged infrastructure (HCI) platform that
delivers the flexibility of converged infrastructure and the simplicity of HCI. This scalable solution is designed, tested, and documented to
address the business requirements, workloads, and applications of HPE customers. The solution incorporates a wide range of products into a
portfolio of repeatable, scalable, and composable technologies that are supported by Hewlett Packard Enterprise.

This deployment guide details a sample configuration of the HPE Aruba 832x and 6300 network switches for use with HPE Alletra dHCI.

Although this guide describes general deployment considerations and best practices in detail, it is not meant to be exhaustive and does not
cover every possible supported configuration. This guide supplements the HPE Alletra dHCI New Servers Deployment Guide and the HPE
Alletra dHCI Existing Servers Deployment Guide, which are located on the HPE InfoSight portal.

Server, array, and switch cabling example

Use the methodology shown in the following figure to cable an HPE ProLiant DL server, HPE Alletra Storage 5000 or 6000 array, and
network switches.

Additional configuration examples are in the HPE Alletra dHCI solution network considerations guide. Note that if you are leveraging the
network automation feature, only the two-switch topology depicted here is currently supported.

Figure 1. Cabling example: HPE ProLiant server with four 10 Gbps ports

Figure 2. Sample switch port configuration on an HPE Aruba 8325 switch

Technical white paper Page 4

Table 1. Sample switch port configuration on an HPE Aruba 8325 switch

Interface Function

1/1/1 Server 1 management

1/1/2 Server 1 iSCSI
1/1/3 Server 2 management
1/1/4 Server 2 iSCSI
1/1/5 Server 1 iLO (Server 2 iLO on switch 2)
1/1/7 Storage Controller A management
1/1/8 Storage Controller B management
1/1/15 Storage Controller A iSCSI
1/1/16 Storage Controller B iSCSI
1/1/46-48 Virtual switching extension (VSX)

Network requirements for configuring an Ethernet switch

Although different Ethernet switches can have different requirements, in general you must set up the following features:
• Maximum transmission unit (MTU)
• Flow control
• Jumbo frames
• VLAN
• Link Layer Discovery Protocol (LLDP)

MTU
Many switches define MTU differently from the way the initiator or target defines it. Switches often define MTU as the frame size. End hosts
almost universally define MTU as the packet size. The configured frame size on the switch might need to be larger than the packet size or
the MTU value defined on the host and the array. For example, a value of 9000 on the host might require a value of 9014 or larger on the
switch. This difference might vary by manufacturer.

Setting the switch MTU value to a number that is higher than the MTU value on the host or initiator does not cause problems. The switch
MTU setting causes problems only when the MTU value on the intermediate device (the switch) is set to a number that is lower than the
MTU value on one or both end devices.

Flow control
Flow control provides a mechanism for temporarily pausing the transmission of data on Ethernet networks if a sending node transmits data
faster than the receiving node can accept it. Whenever possible, you should enable flow control on all host, switch, and array ports to ensure
graceful communication between network nodes. HPE Alletra Storage network interface cards (NICs) support flow control by default.

Jumbo frames
Ethernet frames that transport data are typically 1500 bytes in size. Anything over 1514 bytes (or 1518 with VLAN tagging) in the
Ethernet frame is typically referred to as a jumbo frame. Jumbo frames are generally better suited to handle the flow of iSCSI SAN traffic.
They typically consist of 9000-byte frames.
Enabling jumbo frames can help to improve storage throughput and reduce latency.

Hewlett Packard Enterprise recommends using jumbo frames for the iSCSI data network with new server deployments of dHCI.
Technical white paper Page 5

VLAN
The HPE Alletra dHCI solution requires at least three VLANs:
• A management VLAN — The management VLAN must be the native VLAN in the trunk port (untagged).
• Two iSCSI VLANs — Configure one per switch. The requirement is to use two different VLANs for iSCSI traffic:
– One VLAN should map to one 10 Gbps port of the server.
– The other should map to the second 10 Gbps port.
If the server has four 10 Gbps ports, you should dedicate two ports to the use of iSCSI traffic only. These two ports should be configured in
access mode (no VLAN tag). Each port should map to one VLAN only. Configure the iSCSI VLANs in access mode only (no VLAN tag).

For existing server deployments only: If the server has two 10 Gbps ports, you must trunk the iSCSI VLANs onto your existing ports and
tag the VLANs accordingly. For new server deployments, four ports are required.

Hewlett Packard Enterprise recommends a dedicated VLAN for iLO based on the deployment option you use. Optionally, the iLO network
can use the same VLAN as the management VLAN.

Table 2 lists the requirements.

Table 2. Required dHCI VLANs and port mode

VLAN description VLAN ID Port mode Notes

Management/vMotion mgmt_vlan Trunk Management/vMotion VLAN must be the native VLAN.

iSCSI 1 IP address range iscsi1_vlan Access Tagged VLAN
iSCSI 2 IP address range iscsi2_vlan Access Tagged VLAN
VM network vm_network Trunk VM Network can be trunked on the management interface.
iLO network ilo_vlan Access Optional VLAN. Only required if Split Management is selected
during deployment; that is a separate management network for iLO

VM network VLANs
The HPE Alletra dHCI solution does not configure the VM network during setup. The default VM network port group is present on vSwitch0
at deployment, but any additional configuration must be performed manually after the initial deployment. The VM network VLAN should be
labeled trunk, and each port group should be tagged with the corresponding VLAN ID.

Dead network VLAN

A dead network VLAN is a VLAN to which unused ports are assigned. Having a dead network VLAN provides a safeguard so that if the
cable is attached to an unused port, whether accidentally or intentionally, that port will not provide access to any traffic on the network.

The network automation feature configures a dead network VLAN as part of its workflow. If the network automation feature is not used, the
HPE Alletra dHCI solution itself does not require the use of a dead network VLAN. However, Hewlett Packard Enterprise recommends that
you include one, and having one is considered best practice by most switch vendors.

LLDP
LLDP must be enabled on each switch. The HPE Alletra dHCI solution uses LLDP both during and after deployment to verify the
environment.

Spanning tree
Each interface used for iSCSI traffic must be configured as spanning tree edge ports. Hewlett Packard Enterprise recommends that you use
spanning tree mode rpvst if it is supported by the switches.

Network configuration example for use with Peer Persistence

Before you deploy dHCI, you must complete the network configuration between the sites. Peer Persistence with dHCI requires that you
configure the management VLAN and both iSCSI VLANs so that they are available between the two solutions.
Technical white paper Page 6

The networking configuration should resemble the one shown in Figure 3.

Figure 3. Peer Persistence configuration example

HPE Aruba 8320 or 8325 configuration example to prepare for network automation
When deploying dHCI as a new server install and using HPE Aruba 832x or 6300 switches, you can use the dHCI network automation
feature to complete the switch setup. This feature uses the dHCI wizard to gather information from the array about the connected
HPE Aruba 832x or 6300 switches and then prompts you for information to complete the setup. This example demonstrates preparing
HPE Aruba 832x switches to use the network automation feature.

Important
If you do not set up the initial cabling correctly, you will not be able to use the dHCI network automation feature. The dHCI wizard checks to
see that you have a management port and data port connected to one switch and a second management port and data port connected to
another switch.

To use the network automation feature, you must first:

• Make sure that the switches are running the HPE firmware version specified in the Validated Configuration Matrix. A base HPE Storage
dHCI deployment must use a minimum of two network switches of the same model that are running the same version of firmware.
• Create a new cluster. This feature does not work with existing clusters.
• Provide a password for the dHCI switch administrator, which has the username switch_admin.
• Complete the following manual steps on the array before you start the dHCI setup. The dHCI wizard uses this information when you select
the dHCI network automation feature.
a. Set up the initial configuration on HPE Aruba 832x switches 1 and 2.
b. Set up the VSX configuration.
c. Configure a management network VLAN on all remaining ports under access. (Do not configure tag or trunk ports.)
d. Connect the HPE Aruba 832x switches to the customer network.

Important
The steps in the following tasks are examples. The steps you perform depend on the switches you use and your system configuration. You
should follow the best practices and documentation provided by your switch vendor.
You must be in configuration terminal mode when you enter the commands in the following tasks.
Technical white paper Page 7

Task 1: Set up the initial configuration on the HPE Aruba 832x switches
To use the dHCI network automation feature, you must perform the initial configuration of the HPE Aruba 8320 or HPE Aruba 8325 switch
pair before you start the dHCI setup.

Procedure
1. Prepare for the configuration of the HPE Aruba 832x switches.
a. If you are using a serial cable to connect to the console, specify 115,200 or 9600 baud as the speed.
b. Connect the two switches by using QSFP+ or SFP+, depending on the switch model.
c. Specify three ports on each switch: two for VSX and one for the VSX keepalive mechanism.
2. Configure switch 1:
a. Log in as admin.
b. On a new switch set to the factory defaults, the password will be blank. Press Enter. You will then be prompted to create a new
password.
c. Run the following commands:
config
interface mgmt
no shutdown
ip static <net_switch1_mgmt_ip>/<mgmt_net_netmask>
default-gateway <mgmt_net_gw>
exit
write memory

3. Configure switch 2:
a. Log in as admin.
b. On a new switch set to the factory defaults, the password will be blank. Press Enter. You will then be prompted to create a new
password.
c. If you are using serial cable to connect switch 2 to the console, specify 115,200 or 9600 baud as the speed.
d. Run the following commands:
config
interface mgmt
no shutdown
ip static <net_switch2_mgmt_ip>/<mgmt_net_netmask>
default-gateway <mgmt_net_gw>
exit
write memory

4. Enable an interface group.

a. Run the following commands on both switches, adjusting the ports as needed:
config
system interface-group 1 speed 10g
system interface-group 2 speed 10g
system interface-group 3 speed 10g
system interface-group 4 speed 10g
exit
write memory
Technical white paper Page 8

Note
Your interface group might differ from what is shown in the example. For more information, see the user's guide for the HPE Aruba switch.

5. Set the management address to IPv4 on both switches.

a. Run the following commands on both switches, adjusting the ports as needed:
config
lldp management-ipv4-address <switch_ip_address>
exit
write memory
Task 2: Set up the VSX configuration for the HPE Aruba switches
When you use the automation feature, dHCI checks for information about the VSX configuration. You must have it configured on the
HPE Aruba 832x switch pair that you are using.

Procedure
1. Configure the link aggregation group (LAG) that will be used for VSX.
a. Run the following commands on both switches, adjusting the ports as needed:
config
interface lag 99
no shutdown
no routing
lacp mode active
vlan trunk native 1 tag
vlan trunk allowed all
interface 1/1/47
no shutdown
lag 99
interface 1/1/48
no shutdown
lag 99
exit
write memory

2. Configure an interface to be used for the VSX keepalive connection.

a. Run the following commands on switch 1:
interface 1/1/46
no shutdown
ip address <net_switch1_vsx_ip>/<vsx_net_netmask>
exit
write memory

b. Run the following commands on switch 2:

interface 1/1/46
no shutdown
ip address <net_switch2_vsx_ip>/<vsx_net_netmask>
exit
write memory
Technical white paper Page 9

3. Configure the VSX role and enable the keepalive interface.

a. Run the following commands on switch 1:
config
vsx
role primary
inter-switch-link lag 99
keepalive peer <net_switch2_vsx_ip> source <net_switch1_vsx_ip>
exit
write memory

b. Run the following commands on switch 2:

config
vsx
role secondary
inter-switch-link lag 99
keepalive peer <net_switch1_vsx_ip> source <net_switch2_vsx_ip>
exit
write memory

4. Verify that VSX is enabled and configured.

a. Run the show vsx status command to request a status report.
show vsx status
VSX Operational State
---------------------
ISL channel : In-Sync
ISL mgmt channel : operational
Config Sync Status : In-Sync
NAE : peer_reachable
HTTPS Server : peer_reachable

Attribute Local Peer

------------ -------- --------
ISL link lag99 lag99
ISL version 2 2
System MAC 02:00:00:00:04:00 02:00:00:00:04:00
Platform 8325 8325
Software Version GL.10.10.1000 GL.10.10.1000
Device Role secondary primary
Technical white paper Page 10

Task 3: Configure a management network VLAN on ports for HPE Aruba 832x switches
The HPE Alletra dHCI solution requires that you configure a management network VLAN on all the remaining ports on the HPE Aruba 832x
switch pair that you are using.

Procedure
1. Create the required management network VLAN on switch 1. The vsx-sync command then syncs the VLANs to switch 2.
config
vlan <mgmt_net_vlan>
description MGMT-VLAN
vsx-sync
exit
write memory

2. Configure all remaining ports (except VSX ports) in access mode with the VLAN ID set to the management network VLAN. Adjust the
ports as needed. Run these commands on both switch 1 and switch 2:
config
interface 1/1/1-1/1/45,1/1/49-1/1/56
vlan access 3530
exit
write memory

Task 4: Connect the HPE Aruba switches to the customer network

To reach the customer environment, which includes DNS, NTP, and the VMware vCenter® plug-in, dHCI requires that you connect the HPE
Aruba 832x switch pair with the customer network.

Procedure
1. Create multi-chassis link aggregation group (MC-LAG) interface. Adjust the lag ID as required. Run the following commands on each
switch:
config
interface lag 1 multi-chassis
vsx-sync vlans
description MC-LAG
no shutdown
no routing
vlan trunk native <mgmt_net_vlan>
vlan trunk allowed all (or trunk only the VLANs you want)
lacp mode active
exit
write memory

2. Add physical interfaces into the multichassis interface. Run the following commands on each switch:
config
interface 1/1/<MC_LAG_PORT_ID>
no routing
no shutdown
lag 1
exit
write memory
Technical white paper Page 11

HPE Aruba 8320 or 8325 configuration example using manual steps

If you do not want to use the dHCI network automation feature, you can manually set up the HPE Aruba 8320 or 8325 switches. The tasks
in this section guide you through the steps to perform a manual configuration.

Important
The steps in these tasks are examples. The steps you perform depend on the switches you use and your system configuration. You should
follow the best practices and documentation provided by your switch vendor.
You must be in configuration terminal mode when you enter the commands in the following tasks.

Before you configure the switches, make sure that they are running a supported version of the HPE firmware. Refer to the Validated
Configuration Matrix on HPE InfoSight for information about system requirements.

A base dHCI deployment requires a minimum of two network switches. The switches must be the same model. The task examples in this
section use HPE Aruba 832x switches.

Important
After you set up the configuration file, copy or capture output from a show run command to a text file from each switch for future
reference.

To manually configure the HPE Aruba 832x switches for dHCI, perform the following tasks:
1. Set up the initial configuration on HPE Aruba 832x switches 1 and 2.
2. Set up the VSX configuration.
3. Configure NTP.
4. Create the VLANs needed.
5. Add individual port descriptions for troubleshooting.
6. Assign the VLANs and configure jumbo frames and flow control.
7. Configure spanning tree.
8. Connect the HPE Aruba 832x switches to the customer network.
9. Secure the remaining interfaces.

Task 1: Set up the initial configuration on the HPE Aruba 832x switches
The first task in manually setting up HPE Aruba 832x switches is to create the initial configuration of the HPE Aruba 832x switch pair.

Procedure
1. Set up HPE Aruba 832x switch 1.
a. If you are using serial cable to connect to the console, specify 115,200 or 9600 baud as the speed.
b. Connect the two switches by using QSFP+ or SFP+, depending on the switch model.
c. Specify three ports at minimum: two for VSX and one for the VSX keepalive mechanism.
2. Configure switch 1.
a. Log in as admin.
b. On a new switch set to factory defaults, the password will be blank. Press Enter. You will then be prompted to create a new password.
c. Run the following commands:
config
interface mgmt
no shutdown
Technical white paper Page 12

ip static <net_switch1_mgmt_ip>/<mgmt_net_netmask> default-gateway <mgmt_net_gw>

exit
write memory
3. Configure switch 2.
a. Log in as admin.
b. On a new switch set to factory defaults, the password will be blank. Press Enter. You will then be prompted to create a new password.
c. If you are using serial cable to connect switch 2 to the console, specify 115,200 or 9600 baud as the speed.
d. Run the following commands:
config
interface mgmt
no shutdown
ip static <net_switch2_mgmt_ip>/<mgmt_net_netmask> default-gateway <mgmt_net_gw>
exit
write memory
4. Enable an interface group.
a. Run the following commands on both switches, adjusting the ports as needed:
config
system interface-group 1 speed 10g
system interface-group 2 speed 10g
system interface-group 3 speed 10g
system interface-group 4 speed 10g
exit
write memory

Note
Your interface group might differ from what is shown in the example. For more information, see the user's guide for the HPE Aruba switch.

Task 2: Set up the VSX configuration on HPE Aruba 832x switches

As part of the manual setup of the HPE Aruba 832x switches, you must configure the VSX configuration.
Procedure
1. Configure the local time and date. Enable NTP.
2. Run the following commands on both switches, adjusting the ports as needed:
config
ntp server <mgmt_net_ntp1>
ntp enable
write memory

Task 4: Create the required VLANs

You must configure all the required VLANs and VLAN interfaces for the HPE Aruba 832x switch pair that you are using.
Procedure
Run the following commands on switch 1. When you create VLANs on switch 1, the vsx-sync command then syncs them to switch 2.

config
vlan <mgmt_net_vlan>
description MGMT-VLAN
Technical white paper Page 13

vsx-sync
exit
vlan <iscsi_san_a_vlan> description iSCSI-SAN-A-VLAN
vsx-sync
exit
vlan <iscsi_san_b_vlan> description iSCSI-SAN-B-VLAN
vsx-sync
exit
vlan <vm_production_net_1_vlan> description VM-Production-VLAN1
vsx-sync
exit
vlan <ilo_vlan> description ILO-VLAN
vsx-sync
exit
vlan <dead_net_vlan>
description Dead-Network for unused ports
vsx-sync
exit
write memory

Task 5: Add individual port descriptions for troubleshooting

You should add individual port descriptions to the HPE Aruba 832x switches. These descriptions can assist you when you perform
troubleshooting activities and verification.
Procedure
1. Add descriptions to both switches.
a. Run the following commands on switch 1:
config
interface 1/1/15
description <alletra_system_name>-CA-tg1a
exit
interface 1/1/16
description <alletra_system_name>-CB-tg1a
exit
interface 1/1/46
description VSX Keep Alive DO NOT MODIFY
exit
interface 1/1/47
description VSX DO NOT MODIFY
exit
interface 1/1/48
description VSX DO NOT MODIFY
exit
interface 1/1/1
description <mgmt_server_1_hostname>-Port1
exit
interface 1/1/2
Technical white paper Page 14

description <mgmt_server_1_hostname>-iSCSI-Port1
exit
interface 1/1/3
description <mgmt_server_2_hostname>-Port1
exit
interface 1/1/4
description <mgmt_server_2_hostname>-iSCSI-Port1
exit
interface 1/1/7
description <alletra_system_name>-MGMT-CA-Port1
exit
interface 1/1/8
description <alletra_system_name>-MGMT-CB-Port1
exit
interface 1/1/5
description <mgmt_server_1_hostname>-ILO
exit
write memory

b. Run the following commands on switch 2:

config
interface 1/1/15
description <alletra_system_name>-CA-tg1b
exit
interface 1/1/16
description <alletra_system_name>-CB-tg1b
exit
interface 1/1/46
description VSX Keep Alive DO NOT MODIFY
exit
interface 1/1/47
description VSX DO NOT MODIFY
exit
interface 1/1/48
description VSX DO NOT MODIFY
exit
interface 1/1/1
description <mgmt_server_1_hostname>-Port2
exit
interface 1/1/2
description <mgmt_server_1_hostname>-iSCSI-Port2
exit
interface 1/1/3
description <mgmt_server_2_hostname>-Port2
exit
interface 1/1/4
Technical white paper Page 15

description <mgmt_server_2_hostname>-iSCSI-Port2
exit
interface 1/1/7
description <alletra_system_name>-MGMT-CA-Port2
exit
interface 1/1/8
description <alletra_system_name>-MGMT-CB-Port2
exit
interface 1/1/5
description <mgmt_server_2_hostname>-ILO
exit
write memory

Task 6: Assign the VLANs and configure jumbo frames and flow control for HPE Aruba 832x switches
Assign individual VLANs to different ports and configure jumbo frames and flow control for both HPE Aruba 832x switches.

Procedure
1. Configure the management and VM network VLANs for each HPE ProLiant server in the environment. Run the following commands on
both switches, adjusting the ports as needed:
config
interface 1/1/1
no routing
vlan trunk native <mgmt_net_vlan>
vlan trunk allowed <vm_production_net_1_vlan>
exit
interface 1/1/3
no routing
vlan trunk native <mgmt_net_vlan>
vlan trunk allowed <vm_production_net_1_vlan>
exit
write memory
2. Configure management VLANs for the HPE Storage management interface for each management port on the array. Run the following
commands on both switches, adjusting the ports as needed:
config
interface 1/1/7
no routing
vlan access <mgmt_net_vlan>
exit
interface 1/1/8
no routing
vlan access <mgmt_net_vlan>
exit
write memory
Technical white paper Page 16

3. Configure management or iLO VLANs for the HPE ProLiant server iLO interface for each iLO port in your environment. Run the following
commands on both switches, adjusting the ports as needed:
config
interface 1/1/5
no routing
vlan access <mgmt_net_vlan> or <ilo_vlan>
exit
write memory

4. Configure iSCSI VLANs, flow control, and jumbo frames for each HPE ProLiant server in the environment.
a. Run the following commands on switch 1:
config
interface 1/1/2
no routing
vlan access <iscsi_san_a_vlan>
flow-control rx
mtu 9198
interface 1/1/4
no routing
vlan access <iscsi_san_a_vlan>
flow-control rx
mtu 9198
exit
write memory

b. Run the following commands on switch 2:

config
interface 1/1/2
no routing
vlan access <iscsi_san_b_vlan>
flow-control rx
mtu 9198
interface 1/1/4
no routing
vlan access <iscsi_san_a_vlan>
flow-control rx
mtu 9198
exit
write memory
Technical white paper Page 17

5. Configure iSCSI VLANs, flow control, and jumbo frames for each port on the array. Run the following commands on both switches,
adjusting the ports as needed:
config
interface 1/1/15
no routing
vlan access <iscsi_san_a_vlan>
flow-control rx
mtu 9198
interface 1/1/16
no routing
vlan access <iscsi_san_b_vlan>
flow-control rx
mtu 9198
exit
write memory

Task 7: Configure spanning tree

When you set up the pair of HPE Aruba 832x switches, it is important to set the interfaces to edge ports in spanning tree. When spanning
tree is enabled on the switch as part of the configuration, these ports directly transition to the forwarding state in the spanning tree
topology.

Procedure
Configure spanning tree for each HPE ProLiant server and HPE Storage interface that is used for iSCSI. Run the following commands on
both switches, adjusting the ports as needed:
config
spanning-tree mode rpvst
interface 1/1/2
spanning-tree port-type admin-edge
interface 1/1/4
spanning-tree port-type admin-edge
interface 1/1/15
spanning-tree port-type admin-edge
interface 1/1/16
spanning-tree port-type admin-edge
exit
write memory

Task 8: Connect the HPE Aruba switches to the customer network

To reach the customer environment, which includes DNS, NTP, and the vCenter plug-in, dHCI requires that you connect the HPE Aruba
832x switch pair to the customer network.
Procedure
1. Create the MC-LAG interface. Adjust the lag ID as required. Run the following commands on each switch:
config
interface lag 1 multi-chassis
vsx-sync vlans
description MC-LAG
Technical white paper Page 18

no shutdown
no routing
vlan trunk native <mgmt_net_vlan>
vlan trunk allowed all (or trunk only the VLANs you want)
lacp mode active
exit
write memory
2. Add physical interfaces to the multichassis interface. Run the following commands on each switch:
config
interface 1/1/<MC_LAG_PORT_ID>
no routing
no shutdown
lag 1
exit
write memory
Task 9: Secure the remaining interfaces for HPE Aruba 832x switches
To complete the HPE Aruba 832x switch setup, you must secure the remaining interfaces.

Procedure
Secure the rest of the switch by shutting down the unused ports and putting them into the dead_net_vlan. Run the following commands on
both switches, adjusting the ports as needed:
config
interface 1/1/6,1/1/9-1/1/14,1/1/17-1/1/45
no routing
vlan access <dead_net_vlan>
exit
write memory

HPE Aruba 6300 configuration example

The following tasks step you through the process of configuring HPE Aruba 6300 switches for use in a dHCI environment.

Important
The steps in these tasks are examples. The steps you perform depend on the switches you use and your system configuration. You should
follow the best practices and documentation provided by your switch vendor.
You must be in configuration terminal mode when you enter the commands in the following tasks.

Before you configure the switches, make sure that they are running a supported version of the HPE firmware. Refer to the Validated
Configuration Matrix on HPE InfoSight for information about system requirements.
A base dHCI deployment requires a minimum of two network switches. The switches must be the same model. The task examples in this
section use HPE Aruba 6300 switches.

Important
After you set up the configuration file, copy or capture a show run output to a text file from each switch for future reference.
Technical white paper Page 19

HPE Aruba 6300 switch configuration consists of the following tasks:

1. Set up the initial configuration on HPE Aruba 6300 switches 1 and 2.
2. Set up the virtual switching framework (VSF) configuration.
3. Configure NTP.
4. Create the required VLAN.
5. Add individual port descriptions for troubleshooting.
6. Assign the VLANs and configure jumbo frames and flow control.
7. Configure spanning tree.
8. Secure the remaining interfaces.
Task 1: Set up the initial configuration on HPE Aruba 6300 switches
The HPE Aruba 6300 switches come with a default factory configuration. You must configure them for your environment. The steps that
follow provide the initial configuration.
Procedure
1. Configure HPE Aruba 6300 switch 1.
a. If you are using serial cable to connect to the console, specify 115,200 or 9600 baud as the speed.
b. Connect the two switches by using QSFP+ or SFP+, depending on the switch model.
c. Specify two ports for VSF.
d. Log in as admin on switch 1. Run the following commands:
config
interface mgmt
no shutdown
ip static <net_switch1_mgmt_ip>/<mgmt_net_netmask>
default-gateway <mgmt_net_gw>
exit
write memory
2. Configure HPE Aruba 6300 switch 2.
a. If you are using serial cable to connect to the console, specify 115,200 or 9600 baud as the speed.
b. Log in as admin on switch 2. Run the following commands:
config
interface mgmt
no shutdown
ip static <net_switch2_mgmt_ip>/<mgmt_net_netmask>
default-gateway <mgmt_net_gw>
exit
write memory

Task 2: Set up the VSF configuration for HPE Aruba 6300 switches
You must configure the ports that will be used with VSF as part of the setup process for the HPE Aruba 6300 switches.

Procedure
1. Run the following commands on switch 1:
config
vsf member 1
link 1 1/1/25
link 2 1/1/26
Technical white paper Page 20

2. Run the following commands on switch 2 to configure it and enable it to join the stack. After the renumber command, the switch
reboots. This action causes the second switch (member 2) to join the stack with the first switch (member 1) as the master. You must
have the VSF link cables connected, or the operation will fail.
config
vsf member 2
link 1 1/1/25
link 2 1/1/26
exit
vsf renumber-to 2
This will save the VSF configuration and reboot the switch. Do you want to continue (y/n) ? y
3. Verify that the second switch (member 2) is now linked, with the first switch (member 1) as the master. Run the show vsf command
on switch 1 (member 1).
Show vsf
MAC Address : 38:21:c7:5d:d0:c0
Secondary :
Topology : Ring
Status : No Split
Split Detection Method : None
Mbr Mac Address Type Status
ID
--- ---------------- --------- ------------
1 38:21:c7:5d:d0:c0 JL668A Master
2 38:21:c7:6a:10:c0 JL668A Member
4. Configure VSF split detection. Run the following command on switch 1. After the two switches are linked, you only perform configuration
tasks on switch 1.
vsf split-detect mgmt

Task 3: Configure NTP for HPE Aruba 6300 switches

You must configure the local time and date and enable NTP.
Procedure
Configure the local time and date and enable NTP.

Run the following commands on both switches, adjusting the ports as needed:
config
ntp server <mgmt_net_ntp1>
ntp enable
write memory

Task 4: Create the VLANs needed for HPE Aruba 6300 switches
You must configure all the required VLANs and VLAN interfaces for the HPE Aruba 6300 switch pair that you are using.
Procedure
Run the following commands on switch 1:
vlan <mgmt_net_vlan>
description MGMT-VLAN
exit
vlan <iscsi_san_a_vlan>
Technical white paper Page 21

description iSCSI-SAN-A-VLAN
exit
vlan <iscsi_san_b_vlan>
description iSCSI-SAN-B-VLAN
exit
vlan <vm_production_net_1_vlan>
description VM-Production-VLAN1
exit
vlan <dead_net_vlan>
description Dead-Network for unused ports
exit
write memory

Task 5: Add individual port descriptions for troubleshooting HPE Aruba 6300 switches
You should add individual port descriptions to the HPE Aruba 6300 switches. These descriptions can assist you when you perform
troubleshooting and verification activities.
Procedure
Add descriptions to both switches.
config
interface 1/1/15
description <alletra_system_name>-CA-tg1a
exit
interface 2/1/15
description <alletra_system_name>-CB-tg1a
exit
interface 1/1/16
description <alletra_system_name>-CA-tg1b
exit
interface 2/1/16
description <alletra_system_name>-CB-tg1b
exit
interface 1/1/25
description VSF DO NOT MODIFY
exit
interface 1/1/26
description VSF DO NOT MODIFY
exit
interface 2/1/25
description VSF DO NOT MODIFY
exit
interface 2/1/26
description VSF DO NOT MODIFY
exit
interface 1/1/1
description <mgmt_server_1_hostname>-Port1
exit
Technical white paper Page 22

interface 1/1/2
description <mgmt_server_1_hostname>-iSCSI-Port1
exit
interface 2/1/1
description <mgmt_server_1_hostname>-Port2
exit
interface 2/1/2
description <mgmt_server_1_hostname>-iSCSI-Port2
exit
interface 1/1/3
description <mgmt_server_2_hostname>-Port1
exit
interface 1/1/4
description <mgmt_server_2_hostname>-iSCSI-Port1
exit
interface 2/1/3
description <mgmt_server_2_hostname>-Port2
exit
interface 2/1/4
description <mgmt_server_2_hostname>-iSCSI-Port2
exit
interface 1/1/5
description <mgmt_server_1_hostname>-ILO
exit
interface 2/1/5
description <mgmt_server_2_hostname>-ILO
exit
interface 1/1/7
description <alletra_system_name>-MGMT-CTRLA-Port1
exit
interface 2/1/7
description <alletra_system_name>-MGMT-CTRLB-Port1
exit
interface 1/1/8
description <alletra_system_name>-MGMT-CTRLA-Port2
exit
interface 2/1/8
description <alletra_system_name>-MGMT-CTRLB-Port2
exit
write memory

Task 6: Assign the VLANs and configure jumbo frames and flow control for HPE Aruba 6300 switches
You must assign individual VLANs to different ports and configure jumbo frames and flow control for both HPE Aruba 6300 switches.
Technical white paper Page 23

Procedure
Configure the management and VM network VLANs for each HPE ProLiant server in the environment.
1. Run the following commands on switch 1, adjusting the ports as needed:
config
interface 1/1/1
no routing
vlan trunk native <mgmt_net_vlan>
vlan trunk allowed <vm_production_net_1_vlan>
exit
interface 1/1/3
no routing
vlan trunk native <mgmt_net_vlan>
vlan trunk allowed <vm_production_net_1_vlan>
write memory
interface 2/1/1
no routing
vlan trunk native <mgmt_net_vlan>
vlan trunk allowed <vm_production_net_1_vlan>
exit
interface 2/1/3
no routing
vlan trunk native <mgmt_net_vlan>
vlan trunk allowed <vm_production_net_1_vlan>
exit
write memory
2. Configure management VLANs for the HPE Storage management interface for each management port on the array. Run the following
commands on switch 1, adjusting the ports as needed:
config
interface 1/1/7
no routing
vlan access <mgmt_net_vlan>
exit
interface 2/1/7
no routing
vlan access <mgmt_net_vlan>
exit
interface 1/1/8
no routing
vlan access <mgmt_net_vlan>
exit
interface 2/1/8
no routing
vlan access <mgmt_net_vlan>
exit
write memory
Technical white paper Page 24

3. Configure management or iLO VLANs for the HPE ProLiant server iLO interface for each iLO port in the environment. Run the following
commands on switch 1, adjusting the ports as needed:
config
interface 1/1/5
no routing
vlan access <mgmt_net_vlan> or <ilo_vlan>
interface 2/1/5
no routing
vlan access <mgmt_net_vlan> or <ilo_vlan>
exit
write memory
4. Configure iSCSI VLANs, flow control, and jumbo frames for each HPE ProLiant server in the environment. Run the following commands
on switch 1, adjusting the ports as needed:
config
interface 1/1/2
no routing
vlan access <iscsi_san_a_vlan>
flow-control rxtx mtu 9198
exit
interface 2/1/2
no routing
vlan access <iscsi_san_a_vlan>
flow-control rxtx mtu 9198
interface 2/1/4
no routing
vlan access <iscsi_san_b_vlan>
flow-control rxtx mtu 9198
interface 2/1/4
no routing
vlan access <iscsi_san_b_vlan>
flow-control rxtx mtu 9198
write memory
5. Configure iSCSI VLANs, flow control, and jumbo frames for each port on the array. Run the following commands on switch 1, adjusting
the ports as needed:
config
interface 1/1/15
no routing
vlan access <iscsi_san_a_vlan>
flow-control rxtx mtu 9198
exit
interface 2/1/15
no routing
vlan access <iscsi_san_a_vlan>
flow-control rxtx mtu 9198
config interface 1/1/16
no routing
Technical white paper Page 25

vlan access <iscsi_san_b_vlan>

flow-control rxtx mtu 9198
exit
interface 2/1/16
no routing
vlan access <iscsi_san_b_vlan>
flow-control rxtx mtu 9198
write memory

Task 7: Configure spanning tree for HPE Aruba 6300 switches

When you set up the pair of HPE Aruba 6300 switches, it is important to set the interfaces to edge ports in spanning tree. When spanning
tree is enabled on the switch as part of the configuration, these ports directly transition to the forwarding state in the spanning tree
topology.
Procedure
Configure spanning tree on each HPE ProLiant and HPE Storage interface that is used for iSCSI. Run the following commands on switch 1:
config
spanning-tree mode rpvst
interface 1/1/2
spanning-tree port-type admin-edge
interface 2/1/2
spanning-tree port-type admin-edge
interface 1/1/4
spanning-tree port-type admin-edge
interface 2/1/4
spanning-tree port-type admin-edge
interface 1/1/15
spanning-tree port-type admin-edge
interface 2/1/15
spanning-tree port-type admin-edge
interface 1/1/16
spanning-tree port-type admin-edge
interface 2/1/16
spanning-tree port-type admin-edge
write memory

Task 8: Secure the remaining interfaces for HPE Aruba 6300 switches
To complete the HPE Aruba 6300 switch setup, you must secure the remaining interfaces.
Procedure
Secure the rest of the switch by shutting down the unused ports and putting them into the dead_net_vlan. Run the following commands on
switch 1, adjusting the ports as needed:
config
interface 1/1/9-1/1/14
no routing
vlan access <dead_net_vlan>
write memory
Technical white paper Page 26

Appendix A: Configuration worksheets

The configuration worksheets list the values needed to complete the procedures in this guide.

Enter the correct and validated values on these sheets before you deploy dHCI. You can expand the sample configuration worksheets as
needed to suit your situation.

Certain products have naming or password character restrictions. Before you fill in this sheet, refer to the documentation for each
component to understand whether there are restrictions associated with it.

Table 3. Global networking configuration worksheet

Global networking description Variable Value

Management network VLAN <mgmt_net_vlan>

Management network netmask <mgmt_net_netmask>

Management network gateway <mgmt_net_gw>

Management network DNS
<mgmt_net_dns1>
server
Management network domain
<mgmt._net_domain_name>
server
Management network NTP
<mgmt_net_ntp1>
server
VM production network VLAN <vm_production_net_1_vlan>

Dead VLAN <dead_net_vlan>

iSCSI A VLAN <iscsia_vlan>

iSCSI B VLAN <iscsib_vlan>

iSCSI A network <iscsia_network>

iSCSI B network <iscsib_network>

iSCSI A netmask <iscsia_netmask>

iSCSI B netmask <iscsib_netmask>

Table 4. HPE Aruba switches configuration worksheet

HPE Aruba switches description Variable Value
Network switch 1 management IP
<net_switch1_mgmt_ip>
address
Network switch 2 management IP
<net_switch2_mgmt_ip>
address
Network switch 1 VSX IP address <net_switch1_vsx_ip>

Network switch 2 VSX IP address <net_switch2_vsx_ip>

VSX network netmask <vsx_net_netmask>

Switch admin password <net_switch_admin_password>

Technical white paper

Additional links
HPE Alletra dHCI solution network considerations guide
https://www.hpe.com/psnow/doc/a00114771enw

HPE Alletra dHCI Deployment Guide for New Installations on Array OS 6.1.x and Later
https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_HPE_Alletra_dHCI_Deployment_Guide_for_New_Installations_on_Array_OS
6_1_x_and_Later_6_1_x.pdf

HPE Alletra dHCI Deployment Guide for Existing Installations on Array OS 6.1.x and Later
https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_HPE_Alletra_dHCI_Deployment_Guide_for_Existing_Installations_on_Array
_OS_6_1_x_and_Later_6_1_x.pdf

AOS-CX 10.10 Command-Line Interface Guide 8320, 8325 Switch Series

https://www.arubanetworks.com/techdocs/AOS-CX/10.10/PDF/cli_832x.pdf

AOS-CX 10.10 Command-Line Interface Guide 6300, 6400 Switch Series

https://www.arubanetworks.com/techdocs/AOS-CX/10.10/PDF/cli_6300-6400.pdf

Learn more at
hpe.com/us/en/hpe-greenlake-
private-cloud-business-
edition.html
© Copyright 2023 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without
notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

VMware vCenter is a registered trademark or trademark of VMware, Inc. and its subsidiaries in the United States and other
jurisdictions. All third-party marks are property of their respective owners.

a00136807ENW