Wired Intelligent Edge

 View Only
Expand all | Collapse all

HPE 5406zl (J9642A), DT-LACP & pxe (split-LACP szenario)

This thread has been viewed 0 times
  • 1.  HPE 5406zl (J9642A), DT-LACP & pxe (split-LACP szenario)

    Posted Jan 17, 2019 06:47 AM

    Hello all,

    i've got a problem with a 5406zl "Cluster" and hope that one of you can give me the final hint to solve my Problem. Unforteunatly i did not find anything in the www :/

    We've got two 5406zl (K.16.02.0025). On both Switches is a Switch-Interconnect established to each other and all is working fine except in a Split-LACP szenario (e.g. PXE-Boot).

    Trk25-Trk32 is a Database Cluster where the first Server is a DHCP/TFTP-Server and the last seven are "PXE-Clients". The seven DB-Nodes are only bootet via PXE - they don't have a own OS on Disk.

    If both Ports are activated, the PXE-Client isn't able to bootstrap the OS. In the DHCP-Logs i can see a DHCP-Discover and the offer from the Server - thats it - not more. If i disable one, of both interfaces, than the PXE-Boot is successful. So i assume that dt-lacp isn't actually able to put both interfaces in a type of fallback-mode.

    Is this a limitation of DT-Trunking or did i forget something to configure?

     

    Config switch-1 (switch-2 is equivalent)

    module 1 type j9534a
    module 2 type j9534a
    console baud-rate 9600
    trunk A1 trk1 dt-lacp
    trunk A2 trk2 dt-lacp
    trunk A3 trk3 dt-lacp
    trunk A4 trk4 dt-lacp
    trunk A5 trk5 dt-lacp
    trunk A6 trk6 dt-lacp
    trunk A7 trk7 dt-lacp
    trunk A8 trk8 dt-lacp
    trunk A9 trk9 dt-lacp
    trunk A10 trk10 dt-lacp
    trunk A11 trk11 dt-lacp
    trunk A12 trk12 dt-lacp
    trunk A13 trk13 dt-lacp
    trunk A14 trk14 dt-lacp
    trunk A15 trk15 dt-lacp
    trunk A16 trk16 dt-lacp
    trunk A24 trk24 dt-lacp
    trunk B1 trk25 dt-lacp
    trunk B2 trk26 dt-lacp
    trunk B3 trk27 dt-lacp
    trunk B4 trk28 dt-lacp
    trunk B5 trk29 dt-lacp
    trunk B6 trk30 dt-lacp
    trunk B7 trk31 dt-lacp
    trunk B8 trk32 dt-lacp
    trunk A21-A22,B21-B22 trk144 lacp
    logging <snipp>
    timesync sntp
    sntp unicast
    sntp server priority 1 <snipp>
    sntp server priority 2 <snipp>
    no telnet-server
    time timezone 60
    no web-management
    ip default-gateway <snipp>
    ip dns domain-name "<snipp>"
    ip dns server-address priority 1 <snipp>
    switch-interconnect trk144
    interface A1
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A2
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A3
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A4
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A5
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A6
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A7
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A8
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A9
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A10
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A11
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A12
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A13
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A14
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A15
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A16
    name "<snipp>"
    no power-over-ethernet
    exit
    interface A17-A19,A23 (summarized to keep it short)
    disable
    no power-over-ethernet
    exit
    interface A20
    name "<name-other-switch>-a22 (DT-Keepalive)"
    no power-over-ethernet
    exit
    interface A21
    name "<name-other-switch>-a21 (trk144 - S-IC)"
    no power-over-ethernet
    exit
    interface A22
    name "<name-other-switch>-a22 (trk144 - S-IC)"
    no power-over-ethernet
    exit
    interface A24
    name "<snipp> (trk24 - uplink)"
    no power-over-ethernet
    exit
    interface B1
    name "<snipp>"
    no power-over-ethernet
    exit
    interface B2
    name "<snipp>"
    no power-over-ethernet
    exit
    interface B3
    name "<snipp>"
    no power-over-ethernet
    exit
    interface B4
    name "<snipp>"
    no power-over-ethernet
    exit
    interface B5
    name "<snipp>"
    no power-over-ethernet
    exit
    interface B6
    name "<snipp>"
    no power-over-ethernet
    exit
    interface B7
    name "<snipp>"
    no power-over-ethernet
    exit
    interface B8
    name "<snipp>"
    no power-over-ethernet
    exit
    interface B9-B20,B23-B24 (summarized to keep it short)
    disable
    no power-over-ethernet
    exit
    interface B21
    name "<name-other-switch>-b21 (trk144 - S-IC)"
    no power-over-ethernet
    exit
    interface B22
    name "<name-other-switch>-b22 (trk144 - S-IC)"
    no power-over-ethernet
    exit
    interface Trk1-Trk16,Trk24-Trk32 (summarized to keep it short)
    unknown-vlans disable
    exit
    snmp-server contact "<snipp>"
    snmpv3 enable
    snmpv3 only
    snmpv3 restricted-access
    snmpv3 group operatorauth user "<snipp>" sec-model ver3
    snmpv3 user "<snipp>"
    vlan 1
    name "DEFAULT_VLAN"
    no untagged A20,Trk1-Trk16
    untagged A17-A19,A23,B9-B20,B23-B24,Trk25-Trk32,Trk144
    tagged Trk24
    ip address <snipp>
    exit
    vlan 5
    name "<snipp>"
    untagged Trk15-Trk16
    tagged Trk3,Trk24,Trk144
    no ip address
    exit
    vlan 105
    name "<snipp>"
    untagged Trk1-Trk14
    tagged Trk24,Trk144
    no ip address
    exit
    vlan 106
    name "<snipp>"
    tagged Trk15-Trk16,Trk24,Trk144
    no ip address
    exit
    vlan 3802
    name "<snipp>"
    tagged Trk25-Trk32,Trk144
    no ip address
    exit
    vlan 4094
    name "DT-Keepalive"
    untagged A20
    ip address <snipp>
    exit
    spanning-tree Trk1 priority 4 bpdu-filter
    spanning-tree Trk2 priority 4 bpdu-filter
    spanning-tree Trk3 priority 4 bpdu-filter
    spanning-tree Trk4 priority 4 bpdu-filter
    spanning-tree Trk5 priority 4 bpdu-filter
    spanning-tree Trk6 priority 4 bpdu-filter
    spanning-tree Trk7 priority 4 bpdu-filter
    spanning-tree Trk8 priority 4 bpdu-filter
    spanning-tree Trk9 priority 4 bpdu-filter
    spanning-tree Trk10 priority 4 bpdu-filter
    spanning-tree Trk11 priority 4 bpdu-filter
    spanning-tree Trk12 priority 4 bpdu-filter
    spanning-tree Trk13 priority 4 bpdu-filter
    spanning-tree Trk14 priority 4 bpdu-filter
    spanning-tree Trk15 priority 4 bpdu-filter
    spanning-tree Trk16 priority 4 bpdu-filter
    spanning-tree Trk24 priority 4 bpdu-filter
    spanning-tree Trk25 priority 4 bpdu-filter
    spanning-tree Trk26 priority 4 bpdu-filter
    spanning-tree Trk27 priority 4 bpdu-filter
    spanning-tree Trk28 priority 4 bpdu-filter
    spanning-tree Trk29 priority 4 bpdu-filter
    spanning-tree Trk30 priority 4 bpdu-filter
    spanning-tree Trk31 priority 4 bpdu-filter
    spanning-tree Trk32 priority 4 bpdu-filter
    spanning-tree Trk144 priority 4
    no spanning-tree bpdu-throttle
    no tftp server
    distributed-trunking peer-keepalive vlan 4094
    distributed-trunking peer-keepalive destination <snipp>
    no autorun
    no dhcp config-file-update
    no dhcp image-file-update
    password <snipp>
    password <snipp>

     

    Thanks :)

    Best Regards Matthias



  • 2.  RE: HPE 5406zl (J9642A), DT-LACP & pxe (split-LACP szenario)

    Posted Jan 22, 2019 07:32 AM

    Hi all,

    is this szenario really that uncommon that no one has a little hint?

     

    Greetings Matthias