Thank-you for the very thorough response, I have for clarity attached a diagram of my setup currenlty and yes the remote switch I would like to use for voice and the primary (closest to the router) for data.
Correct, port 9 is the interconnection between the switches and I have created the ports as tagged ports (in both VLAN's despite the fact I dont really need to).
You are right, the remote switch should really only be for VLAN 40 voice but I am just thinking in the instance perhaps that maybe another switch is added to the link that could require both voice/data (daisy chaining) or data only.
Thank-you for your point:
"you, eventually, can aggregate 9 with 10 to form trk1 by using LACP and then re-apply VLAN untagging/tagging directly - and only - on new logical trk1 port"
This is what I was asking for, information on LACP/Trunking as at least with Aruba this is a new topic for me - if you can offer a little guidance on the correct setup I can simply follow the guide (Aruba is very well supported so have no issues doing this).
To clarify also on the data switch (closes to the firewall) it is the uplink port 10 that is connected to our firewall/router. I have made the below changes to the configuration however so we have a clear voice/data split.
switch_1_data# show lldp info remote-device
LLDP Remote Devices Information
LocalPort | ChassisId PortId PortDescr SysName
--------- + ------------------------- ------ --------- ----------------------
7 | 48 2a e3 25 1b 28 48 ...
9 | 94 f1 28 68 33 d0 9 9 switch_2_voice
switch_2_voice# show lldp info remote-device
LLDP Remote Devices Information
LocalPort | ChassisId PortId PortDescr SysName
--------- + ------------------ ------------------ --------- ------------------
1 | 0.0.0.0 80 5e c0 52 be 7b WAN PORT SIP-T46S
1 | T46S805EC052BE7B WAN PORT T46S
9 | 1c 98 ec 46 14 90 9 9 switch_1_data