First of all please explain us why you created Port Trunks (Trk<id>) referencing just one physical port for each one?
Port Trunk = Link(s) Aggregation = to bond/aggregate/team two or more physical ports (up to 8 generally) to form a logical port (the various Trk<id> - trk1, trk2, trk3, etc - you listed) which can be used to uplink/downlink to a peer Switch or a Host (with teamed ports). You specified lacp...so your idea is to have (at least) two ports aggregated with LACP as link aggregation control protocol...so why each Port Trunk has just one port?
Here I suspect a confusion with Cisco's Trunk meaning...where Trunk = port that is able to carry multiple tagged VLANs.
If so...please re-think your actual design.
On HPE/HP/Aruba (as on Cisco) also a Port Trunk can carry multiple tagged VLANs...simply with interface ethernet trk1 tagged vlan <vlanid>...or, once into the <vlanid> context, with the simple command tagged <vlanid>.
First fix this part then we can start speaking about the above layer (IP Addressing, Routing, VLAN's SVI...).
Edit: trk<id> doesn't need to match between peer switches (Trk1 can connect to Trk100 and vice-versa...it shouldn't necessarily be Trk1 to Trk1 or TrkN to TrkN...it can be - it's really usual - TrkX to TrkY...what it is really important are that both Port Trunks have the same settings and uses the same type of ports and ports' speed)
