Active-passive xenserver bond availibility after stacked switch failure

There are no bonding modes in Windows teaming. There's only active/active (mode-4 in Linux terms, requires a switch that supports it) and active/passive (or failover) mode.

Also, if you're mixing b-coms and intels in the same machine, you cannot use both Intel ProSet and BACS to manage the teams. You have to use only one of them, and each team must have at least one NIC corresponding to the team management brand used.

That means that if you have b-coms and intels, and you want to use BACS for teaming, you need to create teams, each with at least one b-com (since it corresponds to BACS natively). You can't, under BACS, create teams with intels only.

I'm not terribly familiar with Juniper switches, but you shouldn't have to configure LACP on them; that is the point of LACP. If this isn't the case, something is wrong with your switch configuration.

LACP only specifies a protocol for dynamically aggregating ports. It does not specify a port scheduling policy (where traffic is sent and received). This policy is set separately. I don't remember the process in Linux, but I know Linux supports specifying at couple different policies, probably similar to balance-alb.

The balance-alb has specific disadvantages. Mainly that it semi-intelligently selects an outgoing port for new connections, and they're stuck to that one port for the life of the connection (it's actually done by MAC, not port, if a port fails the MAC gets assigned to another port, thus allowing the connection to continue).

This doesn't exactly "aggregate" the ports however, as connections will not be able to utilize more than one port. So if you've got 2 1GbE ports, a single connection is still limited to 1GbE. LACP resolves this usually, though it depends on your scheduling policy and the number of active ports supported at each end.