Dynamic LACP???

[madmac]

I have a server with a dual NIC that I would like to connect to 2 different 5412zl switches for resiliency purposes. Should I be using dynamic LACP or should I be looking at some other form of link aggreagtion?

It is an intel dual port NIC using the ProSet drivers. Ideally I would want one link actice with the other link becoming active should the primary switch fail. Initially I was looking at dynamic LACP, but Im not sure this works accross different switches?

If someone can give me some pointers Im happy to go away and read up..

Thanks

[jguse]

Hello,

If you want to connect a server to two switches with LACP, you'll want to use distributed trunking for static LACP.

It's not quite as simple as setting up an ordinary LACP trunk, so you'll want to see the Configuration Guide for details:
http://cdn.procurve.com/training/Manuals/3500-5400-6200-6600-8200-MCG-Mar10-12-PortTrunk.pdf

Hope that helps. Feel free to let me know if you have any questions.

[madmac]

Looks like just the ticket though I need to have a think about trunked links as DTIP looks like it needs me to remove any trunked links and set them up again.

Thanks for the heads up, I will have a read, try a config or three and come back here with any questions

[madmac]

Nt working for me.

I have a dual port Intel NIC set up for SFT (switch fault tolerance)

NIC port 1 connects to switch A port 1

NIC port 2 connects to switch B port 1

ISC ports are set to port 20 on both switches

Im testing by pinging the VRRP interface (xx.1) for the vlan and disconnecting the NIC cables one at a time

If I disconnect the cable from port 1 on switch A, I don't lose a ping as everything fails over.

When I reconnect the cable into switch A port 1, I lose all ping responses UNTIL I remove the connection from port 1 switch B, as soon as I do ping comes back up.

So it fails over, but when the link comes back up I lose connectivity until I remove the second link and then wait until ping responds and then i can reconnect the second link.

Sho lacp distributed gives me

Local Port Status:

       LACP    Trunk   Port            LACP    Admin  Oper
  Port Enabled Group   Status  Partner Status  Key    Key
  ---- ------- ------- ------- ------- ------- ------ ------
  1    Active  Trk2    Up      No      Success 0      291

Remote Port Status:

          LACP      Trunk     Port                LACP      Oper
   Port   Enabled   Group     Status    Partner   Status    Key
   ----   -------   -------   -------   -------   -------   ------
   1      Active    Trk2      Up        No        Success   9

Are my issues down to the fact that I have no LACP partner status

Configs below

 Switch A

; J8692A Configuration Editor; Created on release #K.15.10.0009
; Ver #03:03.1f.ef:f0
hostname "SS-TEST-SSLTA"
module 1 type j86xxa
trunk 1 trk2 dt-lacp
logging 163.119.81.81
logging 163.119.88.132
logging facility local6
timesync sntp
sntp unicast
sntp server priority 1 163.119.87.121
no telnet-server
ip ssh filetransfer
ip router-id 163.119.92.13
ip routing
switch-interconnect 20
interface 1
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 2
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 3
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 4
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 5
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 6
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 7
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 8
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 9
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 10
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 11
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 12
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 13
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 14
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 15
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 16
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 17
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 18
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 19
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 20
   name "unassigned"
   speed-duplex 100-full
   exit
interface Trk2
   unknown-vlans disable
   exit
interface loopback 0
   ip address 163.119.92.13
   ip ospf 163.119.92.13 area backbone
   exit
snmp-server community "public" operator unrestricted
snmp-server community "nwsupport" operator unrestricted
snmp-server host 163.119.80.63 community "public"
snmp-server contact "Infrastructure_Team" location "LT_Equipment_Room"
router ospf
   area backbone
   redistribute connected
   enable
   exit
router vrrp
   enable
   exit
vlan 1
   name "DEFAULT_VLAN"
   no untagged 2-19,21-22,Trk2
   untagged 23-24
   tagged 20
   no ip address
   exit
vlan 2
   name "prod-lt"
   untagged 2-22,Trk2
   tagged 23-24
   ip address 163.119.2.1 255.255.255.0
   vrrp vrid 2
      owner
      virtual-ip-address 163.119.2.1 255.255.255.0
      priority 255
      preempt-delay-time 55
      enable
      exit
   exit
vlan 2053
   name "P2P - SSLTA - CSLTA"
   tagged 20,23
   ip address 163.119.93.178 255.255.255.252
   ip ospf 163.119.93.178 area backbone
   exit
vlan 2054
   name "P2P - SSLTA - CST0A"
   tagged 20,24
   ip address 163.119.93.182 255.255.255.252
   ip ospf 163.119.93.182 area backbone
   exit
spanning-tree Trk2 priority 4
no tftp client
no tftp server
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager
password operator

Switch B

; J8692A Configuration Editor; Created on release #K.15.10.0009
; Ver #03:03.1f.ef:f0
hostname "SSLTB"
module 1 type j86xxa
console inactivity-timer 10
trunk 1 trk2 dt-lacp
logging 163.119.81.81
logging 163.119.88.132
logging facility local6
timesync sntp
sntp unicast
sntp server priority 1 163.119.87.121
no telnet-server
ip ssh filetransfer
ip router-id 163.119.92.14
ip routing
switch-interconnect 20
interface 1
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 2
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 3
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 4
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 5
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 6
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 7
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 8
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 9
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 10
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 11
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 12
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 13
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 14
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 15
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 16
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 17
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 18
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 19
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 20
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 21
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface 22
   name "unassigned"
   no power-over-ethernet
   speed-duplex 100-full
   exit
interface loopback 0
   ip address 163.119.92.14
   ip ospf 163.119.92.14 area backbone
   exit
snmp-server community "public" operator unrestricted
snmp-server community "nwsupport" operator unrestricted
snmp-server host 163.119.80.63 community "public"
snmp-server contact "Infrastructure_Team" location "LT_Equipment_Room"
router ospf
   area backbone
   redistribute connected
   enable
   exit
router vrrp
   enable
   exit
vlan 1
   name "DEFAULT_VLAN"
   no untagged 2-19,21-22,Trk2
   untagged 23-24
   tagged 20
   no ip address
   exit
vlan 2
   name "prod-lt"
   untagged 2-22,Trk2
   tagged 23-24
   ip address 163.119.2.2 255.255.255.0
   vrrp vrid 2
      backup
      virtual-ip-address 163.119.2.1 255.255.255.0
      enable
      exit
   exit
vlan 2065
   name "P2P - SSLTB - CSLTA (CTEST-A)"
   tagged 20,23
   ip address 163.119.93.226 255.255.255.252
   ip ospf 163.119.93.226 area backbone
   exit
vlan 2068
   name "P2P - SSLTB - CST0A (CTEST-B)"
   tagged 20,24
   ip address 163.119.93.238 255.255.255.252
   ip ospf 163.119.93.238 area backbone
   exit
spanning-tree Trk2 priority 4
no tftp client
no tftp server
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager

[jguse]

Hello again,

You need to set up a peer keep-alive vlan and link for this between the switches for this as well.

Additionally, why are you using SFT on the NICs? With distributed LACP, the distributed end (switches) runs DT-LACP and the other end (your server) needs to use static LACP.

Another helpful document for distributed trunking:

http://h20195.www2.hp.com/v2/GetDocument.aspx?docname=4AA3-4841ENW&doctype=white%20paper&doclang=EN_US&searchquery=&cc=uk&lc=en

[madmac]

Hi, Thanks for this, now Im back I will try your suggestions.

I was using SFT on the NIC as switch failure was exactly the scenario I was trying to get resiliency for with the dual homes connections.

I will look again at the options.