Deploying the Dell Force10 MXL into a Cisco Nexus Network Environment37Te 1/31 128.216 128 200000 DIS 4000 32768 001e.c9f1.0153 128.216Te 1/32 128.217 128 200000 DIS 4000 32768 001e.c9f1.0153 128.217Te 1/43 128.228 128 2000 FWD 4000 28672 547f.ee6c.21c1 128.131Te 1/45 128.230 128 2000 DIS 4000 32768 001e.c9f1.0153 128.230Interface BpduName Role PortID Prio Cost Sts Cost Link-type Edge Filter Boundary---------- ------ -------- ---- ------- ----------- ------- --------- ---- ------ --------Po 1 Dis 128.2 128 200000 DIS 4000 P2P No No NoTe 1/1 Dis 128.186 128 2000 DIS 4000 P2P No No NoTe 1/2 Dis 128.187 128 200000 DIS 4000 P2P No No NoTe 1/3 Dis 128.188 128 2000 DIS 4000 P2P No No No...Te 1/30 Dis 128.215 128 200000 DIS 4000 P2P No No NoTe 1/31 Dis 128.216 128 200000 DIS 4000 P2P No No NoTe 1/32 Dis 128.217 128 200000 DIS 4000 P2P No No NoTe 1/43 Root 128.228 128 2000 FWD 4000 P2P No No NoTe 1/45 Dis 128.230 128 2000 DIS 4000 P2P No No NoMXL2#Nexus MSTP and MXL MSTP – Remainder of Test ObservationsAfter the Local Port Failover and Failback scenarios were observed, the following 4 scenarios werealso observed.1) Failover: Uplink Failure Simulation (Uplink Fast). In this test a shutdown was issued on N5K1’sinterface 1/5. This caused MXL2 to place its interface 1/45 into a status of Discarding and itsinterface 1/43 in to the Role of Root. This scenario was observed with only a single ping beinglost during the failover, indicating that the re-convergence took about 1 second2) Failback: Uplink Failure Simulation (Uplink Fast). In this test a no shutdown was issued onN5K1’s interface 1/5. This caused STP on MXL2 to place its interface 1/43 into a Role ofAlternate and its interface 1/45 in to the Role of Root since it has the lowest path cost to the