HPE Aruba Networking & ProVision-based
1830850 Members
2234 Online
110017 Solutions
New Discussion

Distributed Trunking - 6600 Series

 
Steve Battman
Occasional Contributor

Distributed Trunking - 6600 Series

I have 2 6600 switches setup.

 

The 2 switches have a ISC link between them and a peer-keepalive link between them.

 

I have 2 servers (with 2 NICS teamed). 1 NIC connected to one of the switches, 1 NIC connected to the other switch.

 

The links from the server to the switches are dt-lacp links.

 

When both the ISC link and the Peer link are connected, both switches can ping both servers.

 

When the ISC link goes down, the DT primary can ping both servers but the DT secondary switch disables it's DT trunk, which I believe is normal operation.

 

When both the ISC and the peer link goes down (simulating a switch failure) the primary DT Switch can still ping the servers but the secondary DT switch cannot.

 

According to the documentation , when 1 of the switches loses its ISC and Peer link , it does not know what the other switch is doing so they should both be able to ping the servers , but in my case the secondary cannot.

 

If I were to have a failure of the secondary DT switch then the servers could be contacted by any host connected to the primary DT switch, but if the primary DT switch were to go down, the Secondary DT switch cannot contact the servers so any clients connected to the Secondary switch would lose connectivity to the servers (even though the servers are directly connected into the DT secondary switch).

 

I hope this makes sense, and was wondering where I am going wrong in this scenario.

 

Any help would be appreicated

10 REPLIES 10
Oleg Sukharev
Valued Contributor

Re: Distributed Trunking - 6600 Series

Hi Steve,

 

Please try to disable not only ISL and keepalive links, but also links to server on Primary switch. Or just reboot it to simulate its outage.

 

HTH

Oleg

Steve Battman
Occasional Contributor

Re: Distributed Trunking - 6600 Series

Thanks for the post.

 

When I switch the DT Secondary switch off , the primary can route as expected.

 

When I switch the DT Primary off then the secondary cannot ping anything.

cenk sasmaztin
Honored Contributor

Re: Distributed Trunking - 6600 Series

hi Steve

very importand issue

 

please send me sh run print both switch

cenk

Steve Battman
Occasional Contributor

Re: Distributed Trunking - 6600 Series

Thanks

 

Here are the configs

 

 

cenk sasmaztin
Honored Contributor

Re: Distributed Trunking - 6600 Series

hi Steve

 

fristly

 

IP routing and distributed trunking are mutually exclusive. Routing restrictions with distributed trunking are switch-wide and do not apply to the DT ports only.

 

disable ip routing on switch

and copy and paste my config

 

please try

 

if you can see same eror please send me

 

config)# show lacp distributed 

 

command print.

cenk

Steve Battman
Occasional Contributor

Re: Distributed Trunking - 6600 Series

Thanks for your swift reply., I will try if first thing in the morning and let you know.

thx again

 

 

cenk sasmaztin
Honored Contributor

Re: Distributed Trunking - 6600 Series

can you try
cenk

ISoliman
Super Advisor

Re: Distributed Trunking - 6600 Series

IP Routinh and DT restriction has been removed, now you can use both and it will work fine :)

tschaps
Valued Contributor

Re: Distributed Trunking - 6600 Series


@ISoliman wrote:

IP Routinh and DT restriction has been removed, now you can use both and it will work fine :)

May I ask where this is documented (that the restriction has been removed)? I am having a similar issue to the OP with a similar setup (5406zl). The consultants that set this up left IP routing enabled on both DT switches, but we're having a fair amount of connectivity issues.

 

Running K.15.06.0008

 

Thanks

ISoliman
Super Advisor

Re: Distributed Trunking - 6600 Series

You can find all the info in the below link:

 

http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA3-4841ENW.pdf

 

Make sure it is configured correctly, and if you have issues then I would recomment contacting the support to see if these issues are config related to software bugs.