Hi! Port Trunking (Link Aggregation) requires that all involved links (port trunk member interfaces) must be:
- point-to-point connections between a switch and another switch (there are exceptions: connections can be "not co-terminus" only when you're dealing with a virtual switch made of two ore more physical switches like with: DT-Trunking, VSF, VSX, IRF or Backplane Stacked Switches deployments), router, server, or workstation configured for port trunking.
- Not interrupted by intervening, non-trunking devices in between.
- referenced to physical ports - on both ends - that are working using the same mode (speed and duplex) and same flow control settings.
Given this if the E0/E1 of the Aruba 510 Access Point are set with that in mind you can aggregate E0 and E1 together by using LACP as your preferred link aggregation control protocol.
IMHO forget the case of aggregating the Aruba 510 E0 interface - working at a negotiated Smart Rate speed of 2.5 Gbps - with the Aruba 510 E1 interface working instead at normal Gigabit Ethernet of 1 Gbps. This would violate one of the essential requirements listed above (speed mismatch between Port Trunk member ports).