HP 6120XG 交换机 LACP 被阻止 - 错误情况

网络工程 思科 网络 生成树 生命值 IEEE-802.1ax
2022-02-25 09:40:11

伙计们,

我正在处理与 LACP 相关的非常奇怪的问题,不确定是 6120XG 开关的错误还是其他问题。所以让我在这里解释我的问题。

网络图:

在此处输入图像描述

我在 Cisco vPC 设计中有两台 Cisco Nexus 9396PX TOR 交换机,用于连接到 HP 刀片式交换机 6120XG 的多机箱。

这是过去 1 年的生产,没有任何问题。但最近注意到我的所有 LACP 链接都关闭了,即使所有交换机都打开了。在调试期间,我发现 Cisco 交换机没有收到任何 LACP 数据包来启动这个捆绑包。(这表明 HP 6120XG 交换机有问题) 似乎 HP 交换机已冻结,或者我什至可以通过 ssh 打开来切换并运行所有命令。

HP 6120XG 固件版本:Z.14.58

Cisco Nexus 9396PX 事件期间的日志,这是我在 Cisco 和 HP 交换机上找到的日志。

2022 Mar 31 05:28:39 swt-phx-k006-leaf-2-2 %ETH_PORT_CHANNEL-5-FOP_CHANGED: port-channel412: first operational port changed from Ethernet1/3 to Ethernet1/4
2022 Mar 31 05:28:39 swt-phx-k006-leaf-2-2 %ETH_PORT_CHANNEL-5-PORT_DOWN: port-channel412: Ethernet1/3 is down
2022 Mar 31 05:28:39 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_BANDWIDTH_CHANGE: Interface port-channel412,bandwidth changed to 10000000 Kbit
2022 Mar 31 05:28:39 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_DOWN_INITIALIZING: Interface Ethernet1/3 is down (Initializing)
2022 Mar 31 05:28:40 swt-phx-k006-leaf-2-2 %ETH_PORT_CHANNEL-5-FOP_CHANGED: port-channel412: first operational port changed from Ethernet1/4 to none
2022 Mar 31 05:28:40 swt-phx-k006-leaf-2-2 %ETH_PORT_CHANNEL-5-PORT_DOWN: port-channel412: Ethernet1/4 is down
2022 Mar 31 05:28:40 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel412 is down (No operational members)
2022 Mar 31 05:28:40 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_BANDWIDTH_CHANGE: Interface port-channel412,bandwidth changed to 100000 Kbit
2022 Mar 31 05:28:40 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_DOWN_INITIALIZING: Interface Ethernet1/4 is down (Initializing)
2022 Mar 31 05:28:40 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel412 is down (No operational members)
2022 Mar 31 05:28:49 swt-phx-k006-leaf-2-2 %ETH_PORT_CHANNEL-5-PORT_SUSPENDED: Ethernet1/3: Ethernet1/3 is suspended
2022 Mar 31 05:28:50 swt-phx-k006-leaf-2-2 %ETH_PORT_CHANNEL-5-PORT_SUSPENDED: Ethernet1/4: Ethernet1/4 is suspended
2022 Mar 31 06:05:19 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface Ethernet1/3 is down (Link failure)
2022 Mar 31 06:05:19 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface Ethernet1/4 is down (Link failure)
2022 Mar 31 06:05:19 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel412 is down (No operational members)
2022 Mar 31 06:08:26 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel412 is down (No operational members) (message repeated 2
 times)
2022 Mar 31 06:08:26 swt-phx-k006-leaf-2-2 %ETHPORT-5-SPEED: Interface Ethernet1/3, operational speed changed to 10 Gbps
2022 Mar 31 06:08:26 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/3, operational duplex mode changed to Full
2022 Mar 31 06:08:26 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/3, operational Receive Flow Control state changed to off
2022 Mar 31 06:08:26 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/3, operational Transmit Flow Control state changed to off
2022 Mar 31 06:08:26 swt-phx-k006-leaf-2-2 %ETHPORT-5-SPEED: Interface port-channel412, operational speed changed to 10 Gbps
2022 Mar 31 06:08:26 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_DUPLEX: Interface port-channel412, operational duplex mode changed to Full
2022 Mar 31 06:08:26 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface port-channel412, operational Receive Flow Control state changed to off
2022 Mar 31 06:08:26 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface port-channel412, operational Transmit Flow Control state changed to off
2022 Mar 31 06:08:27 swt-phx-k006-leaf-2-2 %ETHPORT-5-SPEED: Interface Ethernet1/4, operational speed changed to 10 Gbps
2022 Mar 31 06:08:27 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/4, operational duplex mode changed to Full
2022 Mar 31 06:08:27 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/4, operational Receive Flow Control state changed to off
2022 Mar 31 06:08:27 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/4, operational Transmit Flow Control state changed to off
2022 Mar 31 06:08:31 swt-phx-k006-leaf-2-2 %ETH_PORT_CHANNEL-5-PORT_UP: port-channel412: Ethernet1/3 is up
2022 Mar 31 06:08:31 swt-phx-k006-leaf-2-2 %ETH_PORT_CHANNEL-5-FOP_CHANGED: port-channel412: first operational port changed from none to Ethernet1/3
2022 Mar 31 06:08:31 swt-phx-k006-leaf-2-2 %ETH_PORT_CHANNEL-5-PORT_UP: port-channel412: Ethernet1/4 is up
2022 Mar 31 06:08:31 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_BANDWIDTH_CHANGE: Interface port-channel412,bandwidth changed to 10000000 Kbit
2022 Mar 31 06:08:31 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_UP: Interface Ethernet1/3 is up in mode trunk
2022 Mar 31 06:08:31 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_UP: Interface port-channel412 is up in mode trunk
2022 Mar 31 06:08:31 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_BANDWIDTH_CHANGE: Interface port-channel412,bandwidth changed to 20000000 Kbit
2022 Mar 31 06:08:31 swt-phx-k006-leaf-2-2 %ETHPORT-5-IF_UP: Interface Ethernet1/4 is up in mode trunk

LACP 日志

21) FSM:<Ethernet1/3> Transition at 472440 usecs after Thu Mar 31 05:28:39 2022
    Previous state: [LACP_ST_PORT_MEMBER_COLLECTING_AND_DISTRIBUTING_ENABLED]
    Triggered event: [LACP_EV_RECEIVE_PARTNER_PDU_TIMED_OUT]
    Next state: [LACP_ST_PORT_IS_DOWN_OR_LACP_IS_DISABLED]

22) FSM:<Ethernet1/3> Transition at 485224 usecs after Thu Mar 31 05:28:39 2022
    Previous state: [LACP_ST_PORT_IS_DOWN_OR_LACP_IS_DISABLED]
    Triggered event: [LACP_EV_LACP_DOWN_OR_PORT_DOWN]
    Next state: [FSM_ST_NO_CHANGE]

23) FSM:<Ethernet1/3> Transition at 513668 usecs after Thu Mar 31 05:28:39 2022
    Previous state: [LACP_ST_PORT_IS_DOWN_OR_LACP_IS_DISABLED]
    Triggered event: [LACP_EV_PORT_HW_PATH_DISABLED]
    Next state: [FSM_ST_NO_CHANGE]

24) FSM:<Ethernet1/3> Transition at 553383 usecs after Thu Mar 31 05:28:39 2022
    Previous state: [LACP_ST_PORT_IS_DOWN_OR_LACP_IS_DISABLED]
    Triggered event: [LACP_EV_CLNUP_PHASE_II]
    Next state: [LACP_ST_PORT_IS_DOWN_OR_LACP_IS_DISABLED]

25) FSM:<Ethernet1/3> Transition at 572723 usecs after Thu Mar 31 05:28:39 2022
    Previous state: [LACP_ST_PORT_IS_DOWN_OR_LACP_IS_DISABLED]
    Triggered event: [LACP_EV_LACP_ENABLED_AND_PORT_UP]
    Next state: [LACP_ST_DETACHED_LAG_NOT_DETERMINED]

26) FSM:<Ethernet1/3> Transition at 573092 usecs after Thu Mar 31 05:28:40 2022
    Previous state: [LACP_ST_DETACHED_LAG_NOT_DETERMINED]
    Triggered event: [LACP_EV_PERIODIC_TRANSMIT_TIMER_EXPIRED]
    Next state: [FSM_ST_NO_CHANGE]

27) FSM:<Ethernet1/3> Transition at 574523 usecs after Thu Mar 31 05:28:41 2022
    Previous state: [LACP_ST_DETACHED_LAG_NOT_DETERMINED]
    Triggered event: [LACP_EV_PERIODIC_TRANSMIT_TIMER_EXPIRED]
    Next state: [FSM_ST_NO_CHANGE]

28) FSM:<Ethernet1/3> Transition at 575875 usecs after Thu Mar 31 05:28:42 2022
    Previous state: [LACP_ST_DETACHED_LAG_NOT_DETERMINED]
    Triggered event: [LACP_EV_PERIODIC_TRANSMIT_TIMER_EXPIRED]
    Next state: [FSM_ST_NO_CHANGE]

29) FSM:<Ethernet1/3> Transition at 577793 usecs after Thu Mar 31 05:28:43 2022
    Previous state: [LACP_ST_DETACHED_LAG_NOT_DETERMINED]
    Triggered event: [LACP_EV_PERIODIC_TRANSMIT_TIMER_EXPIRED]
    Next state: [FSM_ST_NO_CHANGE]

在 HP 6120XG 交换机上

Mar 31 05:37:25 172.30.9.34 00393 lacp:  Port 18 is blocked - error condition
Mar 31 05:37:25 172.30.9.34 00435 ports:  port 18 is Blocked by LACP
Mar 31 05:37:51 172.30.9.34 00393 lacp:  Port 19 is blocked - error condition
Mar 31 05:37:51 172.30.9.34 00435 ports:  port 19 is Blocked by LACP
Mar 31 05:38:03 172.30.9.34 00393 lacp:  Port 20 is blocked - error condition
Mar 31 05:38:03 172.30.9.34 00435 ports:  port 20 is Blocked by LACP
Mar 31 05:38:36 172.30.9.34 00393 lacp:  Port 21 is blocked - error condition
Mar 31 05:38:36 172.30.9.34 00435 ports:  port 21 is Blocked by LACP
Mar 31 05:38:36 172.30.9.34 00079 ports:  trunk Trk1 is now inactive
Mar 31 05:38:36 172.30.9.34 00002 vlan:  DEFAULT_VLAN virtual LAN disabled
Mar 31 05:41:36 172.30.9.34 00075 system:  Out of pkt buffers; miss count: 2
Mar 31 05:43:57 172.30.9.34 02631 SNTP:  Server not found at 132.163.96.1.
Mar 31 05:44:06 172.30.9.34 02631 SNTP:  Server not found at 132.163.97.1.
Mar 31 05:44:06 172.30.9.34 00414 SNTP:  Unable to reach configured SNTP servers
 

Cisco Nexus 交换机端口配置

interface port-channel412
  description ** Link to enc-k004-1-b **
  switchport mode trunk
  switchport trunk allowed vlan 60,62-70,100
  mtu 9216
  speed 10000
  vpc 412

HP 6120XG 配置

hostname "swt-enc-k004-1-b"
interface 23
   disable
   lacp Active
exit
interface 24
   disable
   lacp Active
exit
trunk 18-21 Trk1 LACP
vlan 1
   name "DEFAULT_VLAN"
   untagged 17,22-24,Trk1
   ip address dhcp-bootp
   no untagged 1-16
   exit
vlan 100
   name "ostack_1_public1"
   tagged 1-16,Trk1
   no ip address
   jumbo
   exit
vlan 63
   name "ostack_1_br-vxlan"
   tagged 1-16,Trk1
   no ip address
   jumbo
   exit
vlan 64
   name "ops"
   tagged 1-16,Trk1
   no ip address
   jumbo
   exit
vlan 65
   name "ostack_1_br-mgmt"
   tagged 1-16,Trk1
   no ip address
   jumbo
   exit
vlan 66
   name "ostack_1_ops"
   tagged 1-16,Trk1
   no ip address
   jumbo
   exit
vlan 67
   name "ostack_1_odmz"
   tagged 1-16,Trk1
   no ip address
   jumbo
   exit
vlan 68
   name "ostack_1_idmz"
   tagged 1-16,Trk1
   no ip address
   jumbo
   exit
vlan 69
   name "ostack_lab"
   tagged 1-16,Trk1
   no ip address
   jumbo
   exit
vlan 70
   name "pxe"
   untagged 1-16
   tagged Trk1
   no ip address
   jumbo
   exit
vlan 62
   name "ostack_1_br-lbaas"
   tagged 1-16,Trk1
   no ip address
   jumbo
   exit
vlan 60
   name "ostack_1_br-storage"
   tagged 1-16,Trk1
   no ip address
   jumbo
   exit

logging 172.30.8.7 oobm
logging facility syslog
timesync sntp
sntp unicast
sntp server priority 1 132.163.96.1 3 oobm
sntp server priority 2 132.163.97.1 3 oobm
snmp-server community "XXXXXX" operator
spanning-tree
spanning-tree 1 admin-edge-port
spanning-tree 1 bpdu-protection
spanning-tree 2 admin-edge-port
spanning-tree 2 bpdu-protection
spanning-tree 3 admin-edge-port
spanning-tree 3 bpdu-protection
spanning-tree 4 admin-edge-port
spanning-tree 4 bpdu-protection
spanning-tree 5 admin-edge-port
spanning-tree 5 bpdu-protection
spanning-tree 6 admin-edge-port
spanning-tree 6 bpdu-protection
spanning-tree 7 admin-edge-port
spanning-tree 7 bpdu-protection
spanning-tree 8 admin-edge-port
spanning-tree 8 bpdu-protection
spanning-tree 9 admin-edge-port
spanning-tree 9 bpdu-protection
spanning-tree 10 admin-edge-port
spanning-tree 10 bpdu-protection
spanning-tree 11 admin-edge-port
spanning-tree 11 bpdu-protection
spanning-tree 12 admin-edge-port
spanning-tree 12 bpdu-protection
spanning-tree 13 admin-edge-port
spanning-tree 13 bpdu-protection
spanning-tree 14 admin-edge-port
spanning-tree 14 bpdu-protection
spanning-tree 15 admin-edge-port
spanning-tree 15 bpdu-protection
spanning-tree 16 admin-edge-port
spanning-tree 16 bpdu-protection
spanning-tree Trk1 priority 4
oobm
   ip address 172.30.9.34 255.255.248.0
   ip default-gateway 172.30.8.1
   exit
password manager
password operator
 

如您在以下输出中所见,LACP 模式在 HP 6120XG 上处于活动状态。(我在 Cisco 上也很活跃)

swt-enc-k004-1-b# show lacp

                           LACP

   PORT   LACP      TRUNK     PORT      LACP      LACP
   NUMB   ENABLED   GROUP     STATUS    PARTNER   STATUS
   ----   -------   -------   -------   -------   -------
   18     Active    Trk1      Up        Yes       Success
   19     Active    Trk1      Up        Yes       Success
   20     Active    Trk1      Up        Yes       Success
   21     Active    Trk1      Up        Yes       Success
   23     Active    23        Down      No        Success
   24     Active    24        Down      No        Success

重新启动 HP 刀片 6120XG LACP 后又回来了,流量开始流动,这在过去也发生在其他机架上,但每次我们只是重新启动交换机,它就会回来。(我们没有 HPE 支持,我们可以要求找出 HP 6120XG 交换机的 BUG 或我的配置中的其他内容)

1个回答

LACP 是一种聚合协议每一侧都需要为 LACP 进行配置,并且至少一侧需要主动通告聚合组才能真正形成。

您不能在 HPE 端将 Cisco VPC 与 LACP 混合使用。

在 6120XG 上,尝试trunk 18-21 Trk1 LACP active. 在 Nexus 上,您需要全局激活 LACP ( feature lacp) 并channel-group 1 mode active在每个成员接口上使用。