Specifically Trunking on the Backup VLAN (27)
The Backup Media Server has 3 NICs connected to the backup vlan. In this example, these are on ports F7,F8,F9 and assigned to a LACP trunk named Trk4.
The Backup Storage (in this case a DR4000) has four NICs connected to the backup vlan. These are on ports are f4,f10,f11,f12 and assigned to a LACP trunk named Trk6
To affect trunk configuration, you need to be at a CLI.
The GUI does not support all of the commands that we need.
SSH to the switch and log in.
Note that this access is equivalent to already being in enable mode (EN) on a Cisco device.
MDF# sho trunk To view the trunks on the device
MDF# sho lacp View the status of lacp interfaces
mdf# sho vlan (vlan ID) Our backup vlan is 27
mdf# sho vlan 27
Changes need to be made from a config prompt
MDF# config t
MDF(config)# To get out of config mode and back to the root prompt press Ctrl+Z or exit.
This is the same as Cisco IOS but doesn’t tell you that in the interface.
Create a trunk The example uses the interfaces that the DR4000 is connected to the interfaces are f4,f10,f11,f12 the vlan is 27 untagged. Cisco calls that the native vlan.
An interface can only be assigned to one untagged (native) vlan at a time
Create an LACP trunk
MDF(config)# trunk f4,f10,f11,f12 Trk6 lacp
From a config prompt we just told the switch to create a trunk, containing these interfaces named Trk6 of type LACP. The trunk interface needs to be added to our backup vlan. This is a little different than Cisco IOS. HP does not treat trunks as interfaces the same way that Cisco does. In IOS we config the interface Trk6 to affect it. Here we edit the VLAN to add the interfaces.
We should check the vlan members, the status of the trunk and the lacp status to validate what we just did.
To remove the trunk we remove trunking from each interface.
When there are no mambers, the trunk ID is removed.
MDF(config)no trunk f4,f10,f11,f12
There are occasions where LACP is still trying to negotiate and the interfaces will not be able to be taken out of the trunk. If that happens you can disable(shutdown) the individual interfaces, take them out of the trunk and enable (no shutdown) them again.
MDF(config)# int f4
These interfaces could then be added to the vlan individually, or lacp enabled individually if needed.
Remember, if you remove all of the interfaces from a trunk it goes away. When you recreate it you will need to assign its untagged vlan again.