Unsolved
This post is more than 5 years old
3 Posts
0
25764
Trunking an S4810 and an S2410 together
I have an S4810 (48 sfp+, 4 qsfp+) and an S2410 (24 cx4, 4 xfp). The S2410 is an existing switch and has run out of ports. I would like to add more equipment, and could do this by migrating all current equipment to the S4810 - but to change every server adapter from cx4 to sfp+ and purchase optics + schedule downtime for 24 servers seems unnecessary. To that effect I got the S4810 and would like to add it to the S2410 to form a single logical switch across the two (and move some high traffic servers onto the 40G ports).
I am not doing any complicated vlan stuff between the two, both are using default vlan (1) for all ports.
I have connected a single XFP port on the S2410 to a single SFP+ port on the S4810 with SR optics, and the link is showing as active on both sides.
I cannot, however, ping between hosts on both switches. Hosts on the same switch can ping each other without an issue, but between the switches they cannot ping.
On my gigE switches (powerconnect 2824 for example) I can simply plug a single cable between both switches and that effectively spans them. This doesn't seem to work for the S series switches and I am not sure why.
I have seen lots of reference to LAG w/LACP and am wondering if this is required to achieve what I want to do. I would also like to increase the bandwidth between the switches by using two 10G ports on each, so this looks to be the ideal solution, but I have never set this up on Dell/Force10 equipment. Any instruction on how to achieve this from both switches would be very appreciated, there are subtle differences in the FTOS commands between the two switches so any advice on how it can be achieved from both ends would really be great.
Any insight into why the two switches are not forwarding to each other at present would also be good to know, just for the sake of learning.
Thanks for reading.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 16th, 2015 14:00
How are the ports configured on each switch? For both the switch to switch connection, and switch to host? I agree that once the communication is working with just one connection, then move on to making the connection with a LAG. Feel free to post up the running config from each switch, we can help look them over.
tgsz
3 Posts
0
March 16th, 2015 16:00
On the S4810, Very barebone config, nothing is customized other than the no-shut, mtu and management interface.
Port TenGigabitEthernet 0/47 is the port connected to the s2410.
#show running-config
Current Configuration ...
! Version 9.5(0.1)
! Last configuration change at Tue Mar 17 13:17:13 2015 by admin
! Startup-config last updated at Mon Mar 16 10:59:55 2015 by default
!
boot system stack-unit 0 primary system: B:
boot system stack-unit 0 secondary system: B:
boot system stack-unit 0 default system: B:
!
redundancy auto-synchronize full
!
hardware watchdog
!
hostname internal40g
!
cam-acl l2acl 2 ipv4acl 8 ipv6acl 0 ipv4qos 2 l2qos 1 l2pt 0 ipmacacl 0 vman-qos 0 ecfmacl 0
!
cam-acl-vlan vlanopenflow 0 vlaniscsi 0 vlanaclopt 2
!
enable password level 15 7 b125455cf679b208ce222dfed3faaad891181403808a8d71
!
username admin password 7 0851a220d0997e9d privilege 15
!
stack-unit 0 provision S4810
!
interface TenGigabitEthernet 0/0
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/1
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/2
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/3
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/4
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/5
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/6
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/7
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/8
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/9
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/10
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/11
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/12
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/13
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/14
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/15
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/16
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/17
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/18
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/19
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/20
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/21
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/22
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/23
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/24
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/25
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/26
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/27
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/28
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/29
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/30
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/31
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/32
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/33
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/34
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/35
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/36
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/37
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/38
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/39
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/40
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/41
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/42
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/43
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/44
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/45
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/46
no ip address
mtu 12000
no shutdown
!
interface TenGigabitEthernet 0/47
no ip address
mtu 12000
no shutdown
!
interface fortyGigE 0/48
no ip address
mtu 12000
no shutdown
!
interface fortyGigE 0/52
no ip address
mtu 12000
no shutdown
!
interface fortyGigE 0/56
no ip address
mtu 12000
no shutdown
!
interface fortyGigE 0/60
no ip address
mtu 12000
no shutdown
!
interface ManagementEthernet 0/0
ip address 192.168.10.10/24
no shutdown
!
interface ManagementEthernet 1/0
no shutdown
!
interface ManagementEthernet 2/0
no shutdown
!
interface ManagementEthernet 3/0
no shutdown
!
interface ManagementEthernet 4/0
no shutdown
!
interface ManagementEthernet 5/0
no shutdown
!
interface ManagementEthernet 6/0
no shutdown
!
interface ManagementEthernet 7/0
no shutdown
!
interface ManagementEthernet 8/0
no shutdown
!
interface ManagementEthernet 9/0
no shutdown
!
interface ManagementEthernet 10/0
no shutdown
!
interface ManagementEthernet 11/0
no shutdown
!
interface Vlan 1
!
protocol lldp
!
line console 0
line vty 0
line vty 1
line vty 2
line vty 3
line vty 4
line vty 5
line vty 6
line vty 7
line vty 8
line vty 9
!
reload-type normal-reload
!
end
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 17th, 2015 08:00
I would think that the ports would by default be untagged for VLAN 1, but we may need to assign the port to untagged for VLAN 1.
Example: http://bit.ly/1lvrXrF
Force10#config
Force10(conf)#interface vlan 1
Force10(conf-if-vlan)#untagged gi 0/2
tgsz
3 Posts
0
March 17th, 2015 16:00
turns out it was an MTU mismatch, the S4810 (as configured in the quick start guide) had the MTU set to 12000, and the S2410 cannot accept frames of this size, and was set to 9000.
After many hours of "it should work" the MTU was changed to 9000 on the S4810 and packets flowed normally. Then LAG/lacp was set up in dynamic mode and it was fine.
There is a rather large discrepancy between the commands used on the S4810 and the S2410 - to the point where almost every command is different.
One final note, all ports on both switches (except for the ports being used for LAG) were placed into a non-default vlan, and then the LAG port-channels were added to this vlan as well as all the other non-lag ports and everything worked as expected.
Quite frustrating that this is not mentionned anywhere in the switch documentation (including the 1000-page S4810 CLI reference).
Hopefully this helps somebody else trying to achieve the same. Any setting above 9000 on ports of the S4810 to the S2410 would cause the S2410 to not see the link (the S4810 would see the link as up, but no packets could be sent or received).
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 18th, 2015 07:00
Good catch on that. Sorry that was so convoluted. I am glad you got it operational and am certain it will help others on the same path as you.
Cheers