i have a cluster of two gs330 on ha and i have two aruba 2930 in stack mode for ha.
side hp i have 4 ports in trunk mode, side sophos instead of lag i have 3 ports in bridge mode.
what can I do to make them communicate without upsetting the network configuration?
first: you can't put two different physical devices into the same trunk on the hp/aruba side. That blows up.
second: you want link aggregation, not bridging.
You have to start with two unused and yet unconfigured interfaces on the Sophos SG side. Go to "Interfaces/Link Aggregation" and setup Link Aggregation Group #1.
This produces a new hardware interface "lag0", which you can subsequently select when adding a new interface of type "Ethernet".
On the switch side you have to setup two trunks with two ports each. One trunk goes to the first SG-UTM, the second goes to the other SG-UTM.
AFAIK, the Sophos supports LACP and uses the 802.3ad standards for link aggregation.
So you could try to use LACP on the Aruba side, set the switch to active, the Sophos will the be the passive side.
Please report back, if that worked for you, enjoy!
Mit freundlichem Gruß, Regards from Germany,
New Vision GmbH, GermanySophos Silver-Partner
If a post solves your question please use the 'Verify Answer' button.
first of all thanks for the reply,so i'll put ports 1/1 1/2 2/1 and 2/2 of the stacked switchs on lacp dynamic active mode?then i'll create a lag sophos side and migrate actual network configuration on new hardware?
yes, you built two trunks on the aruba-switch. For example trunk1 = 1/1 and 1/2, then trunk2=2/1 and 2/2.
Then you move to that lag0 on the Sophos side on each hardware device of your HA-pair.
question: can I insert the lag in the bridge?
you could do this, but what is your use case?
actually i have this.
if I could insert the lag in the bridge I could migrate from the old core switch to the new stack whithout problem
you first create the interface "lag0" like I described before, then insert this interface of type "Ethernet" into the bridge.
So first you create that lag0:
Then you leave out step 2,3 and 4 from my first poring above and instead of creating a new interface, you put it in the existing bridge.