a) Stack them for auto failover (their cross connected A52->B60 and B52->A60) b) vlan 1 ports 0-23 on each for lan (untagged) c) vlan 2 ports 24-47 on each for iscsi (untagged) d) Ports A23 & B23 to be setup for LAG and connect to a pair of N3000 (LAN) switches (until all servers moved to the Force10's 0-23) e) Ports A47 & B47 to be setup for LAG and connect to a pair of N3000 (iSCSI) switches (until all data lines moved to the Force10's 24-47)
So I thought the failover would be fairly straight fwd but...
a) the lan connection on switch B port 23 & iscsi port 47 not linked (no lights) neither on the N3000's end (Switch A is fine) b) pulled the power from switch A and I'm dead in the water, my laptop is plugged in to switch B with no link
Show VLAN: all showing active for both Show Redundancy: Unit 1 = Mgmt, Unit 2 = Standby
Only the Pwr & B52/60 have any lights, the rest stay off and dead
What OS version are you running on the switches? It sounds like spanning-tree is treating it as a loop and putting the ports that don’t work in blocking mode.
If you reconnect to switch A does it work again? The roles sound correct for the stack, but it should just failover and work. Can you connect with serial and see what switch B shows after switch A is failed?
Ok, console port connected to standby, pulled pwr from master, standy sees failed heartbeat and takes control, still no live ports with laptop connected to standby, pwr up master and it takes control back, so looks like failover is working, just no ports on standby, all the ports are config'd exactly the same as master
as in: oh
now i feel like , range 2/0 - 47 were at 'shutdown' doh!
DELL-Josh Cr
Community Manager
•
9763 Posts
•
44886 Points
957
0
Posted August 17th, 2020 14:00
Hi Jim,
What OS version are you running on the switches? It sounds like spanning-tree is treating it as a loop and putting the ports that don’t work in blocking mode.