The two switches are not physically connected to each other inside the chassis, so just think of them as two separate switches, each connected to two NIC ports on the compute blade. If you want fault tolerance between the two switches, use Switch Fault Tolerance (SFT) to team NIC1 or NIC2, with NIC3 or NIC4.
For more information about SFT, see Network Connectivity — How do I use Teaming with Advanced Networking Services (ANS)?
Thank you for your answer. So, it seems that the best way is making a teaming between one NIC of one switch and another NIC of the other switch and cross connect both switches. Isn't it?
What about aggregating ports? Is it possible to LAG more than one port for cross-connect purposes?
Yes you're correct.
When you say aggregating ports, do you mean the connection between the switches? Yes you can configure LAG for the uplink switch ports.
Yes,what we want is to aggretate more than one port (uplink) between both switches. Please, follow next images. Suppose that one switch has NIC 1 and 2 and the other switch has NIC 3 and 4. Firewall is defined as master/slave, so it can change from one to another at any time. The idea is making a linux bonding (or vmware teaming) between NICs and maximize the 10 uplinks port of each switch:
On this image, what I try to show is a teaming between NIC 1 and 3 (VLAN 1) and NIC 2 and 4 (VLAN 2). The issue on this topology is we should use one port for each switch and for each VLAN for cross-connect them. For this reason, perhaps it could be better choice next image:
Here, we have a teaming of four NICs and a LAG of two (or more) ports between both switches. Is it possible to aggregate these two uplink ports with VLAN tagging?