Unsolved

24 Posts

2052

August 17th, 2020 09:00

Force10 S4820T Config issues

2 Force10 S4820T config problems

What I'm trying to do is:

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

 

TIA.. Jim

Moderator

 • 

9.6K Posts

 • 

116 Points

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.

24 Posts

August 17th, 2020 15:00

OS: 9.14

PS: I don't mind wiping out the configs since I haven't gotten it working properly yet

Moderator

 • 

9.6K Posts

 • 

116 Points

August 17th, 2020 16:00

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?

24 Posts

August 18th, 2020 13:00

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!

working now!

Moderator

 • 

9.6K Posts

 • 

116 Points

August 18th, 2020 13:00

Glad you got it working. Let us know if there is anything else we can help you with. 

Moderator

 • 

9.6K Posts

 • 

116 Points

August 27th, 2020 12:00

Hi Jim, Nothing special, it should work when you set up the port channel.

24 Posts

August 27th, 2020 12:00

Still not put into production yet, trying to stay on top of day2day stuff that never seems to give me a break lol

the next bit i have to do is setting up LACP for:

a) LACP (0/23,1/23) uplink to a PC5324 (19/20), do i need to do anything on the 5324?

b) LACP 0/0,0/1,1/0,1/1 for the 1st server (Teamed NICs)

Still trying to read up on it

Moderator

 • 

9.6K Posts

 • 

116 Points

September 1st, 2020 15:00

Which instructions did you use? I don’t see a need to specify active https://dell.to/2EVfZ0q

24 Posts

September 1st, 2020 15:00

So this is what I came up with after a bit of reading:

Force10(config)#interface port-channel 1
Force10(config)#no shutdown
Force10(conf-if-po-1)#description "lines to adc01"
Force10(conf-if-po-1)#channel-member 0/0
Force10(conf-if-po-1)#channel-member 0/1
Force10(conf-if-po-1)#channel-member 1/0
Force10(conf-if-po-1)#channel-member 1/1
...
Force10(conf)#interface Gigabitethernet 0/0
Force10(conf-if-gi-0/0)#no shutdown
Force10(conf-if-gi-0/0)#port-channel-protocol LACP
Force10(conf-if-gi-0/0)#port-channel 1 mode active
...
Force10(conf)#interface Gigabitethernet 0/1
Force10(conf-if-gi-0/1)#no shutdown
Force10(conf-if-gi-0/1)#port-channel-protocol LACP
Force10(conf-if-gi-0/1)#port-channel 1 mode active
...
Force10(conf)#interface Gigabitethernet 1/0
Force10(conf-if-gi-1/0)#no shutdown
Force10(conf-if-gi-1/0)#port-channel-protocol LACP
Force10(conf-if-gi-1/0)#port-channel 1 mode active
...
Force10(conf)#interface Gigabitethernet 1/1
Force10(conf-if-gi-1/1)#no shutdown
Force10(conf-if-gi-1/1)#port-channel-protocol LACP
Force10(conf-if-gi-1/1)#port-channel 1 mode active

Not sure about this active/passive, i went with all active but I could be wrong and it could be 1 active and 1 passive per switch.

Anyways did I read correctly?

Moderator

 • 

9.6K Posts

 • 

116 Points

September 2nd, 2020 10:00

Thanks, yeah use those instructions.

24 Posts

September 2nd, 2020 13:00

Plugged in spare nic (teamed as lacp on server), all links dead. Something is missing in config:

default interface te 1/0-1
default interface te 2/0-1
interface range te 1/0-1, te 2/0-1
no portmode hybrid
no switchport

edit: no shutdown


port-channel-protocol lacp
port-channel 1 mode active
description "link to server"

Show lacp 1:

Force10-1#show lacp 1
Port-channel 1 admin up, oper down, mode lacp
LACP Fast Switch-Over Disabled
Actor System ID: Priority 32768, Address 90b1.1cf4.33db
Partner System ID: Priority 0, Address 0000.0000.0000
Actor Admin Key 1, Oper Key 1, Partner Oper Key 0, VLT Peer Oper Key 1
LACP LAG 1 is an individual link

LACP LAG 1 is a normal LAG

A - Active LACP, B - Passive LACP, C - Short Timeout, D - Long Timeout
E - Aggregatable Link, F - Individual Link, G - IN_SYNC, H - OUT_OF_SYNC
I - Collection enabled, J - Collection disabled, K - Distribution enabled
L - Distribution disabled, M - Partner Defaulted, N - Partner Non-defaulted,
O - Receiver is in expired state, P - Receiver is not in expired state

Port Te 1/0 is disabled, LACP is disabled and mode is lacp
Port State: Not in Bundle
Actor Admin: State ACEHJLMP Key 1 Priority 32768
Oper: State ACEHJLMP Key 1 Priority 32768
Partner is not present

Port Te 1/1 is disabled, LACP is disabled and mode is lacp
Port State: Not in Bundle
Actor Admin: State ACEHJLMP Key 1 Priority 32768
Oper: State ACEHJLMP Key 1 Priority 32768
Partner is not present


Port Te 1/1 is disabled, LACP is disabled and mode is lacp
Port State: Not in Bundle
Actor Admin: State ACEHJLMP Key 1 Priority 32768
Oper: State ACEHJLMP Key 1 Priority 32768
Partner is not present

Port Te 2/0 is disabled, LACP is disabled and mode is lacp
Port State: Not in Bundle
Actor Admin: State ACEHJLMP Key 1 Priority 32768
Oper: State ACEHJLMP Key 1 Priority 32768
Partner is not present

Port Te 2/1 is disabled, LACP is disabled and mode is lacp
Port State: Not in Bundle
Actor Admin: State ACEHJLMP Key 1 Priority 32768
Oper: State ACEHJLMP Key 1 Priority 32768
Partner is not present

24 Posts

September 2nd, 2020 14:00

nevermind, I figured out I need the no shutdown on the interface range te 1/0-1, te 2/0-1

 

24 Posts

September 3rd, 2020 10:00

Okay so far so good (bear with me)

VLAN 1 (LAN) untagged (Port Channels 1-23 (te 1/1-23 te 2/1-23)) seems to be working other than haven't tested uplink on po 23

Now on to VLAN 2 ISCSI which is for connections to ps4210 controller so for the uplink I have:

default interface te 1/46-47
default interface te 2/46-47
interface range te 1/46-47, te2/46-47
no portmode hybrid
no switchport
no shutdown
iscsi enable
port-channel-protocol lacp
port-channel 47 mode active
description "uplink to ps4210 controllers"

 

and for each server I have (of course bumping up the te's and po number accordingly):

default interface te 1/24-25
default interface te 2/24-25
interface range te 1/24-25, te 2/24-25
no portmode hybrid
no switchport
no shutdown
iscsi enable
port-channel-protocol lacp
port-channel 25 mode active
description "iscsi for server1"

Do these look correct to you, not sure if I even need the iscsi enable and if I need to define jumbo frames

TIA.

Jim..

 

 

24 Posts

September 4th, 2020 11:00

Not winning

Uplink Stacked S4220T to PC5324

1) I have a PC5324 switch that has:
a) All workstations connected by fibre (switches) ports 21-24
b) Internet/Routers connections ports 1-8
c) All other single point connection devices
d) port 18 connected to N3024 (stack) where the current servers are
3) LAG Membership 1 19/20 connected to S4820T stack port-channel 23
f) all default vlan untagged
g) ports 19/20 setup for LACP (LAG Membership)

2) S4820T Stack:
a) Port-Channels 1 thru 23 (te 1/0-23 te 2/0-23)
b) Vlan 1 members PO's 1-23 untagged
c) Vlan 2 memebrs PO's 25-47 (not in use yet, planned for iscsi, also untagged)
d) PO 23 (te 1/23 & te 2/23) are connected to PC5324 19/20
e) Temp Server connect to po 5

So all link lites showing, but temp server can not ping to anything else, and no other pc can ping temp server

for the life of me I don't see what I'm missing 

0 events found

No Events found!

Top