知
某局点S10506X与S6850做动态聚合有端口协议down
- 0关注
- 0收藏 2600浏览
组网及说明
问题描述
S10506X与S6850交换机互连100G端口做了动态链路聚合，其中两端各有两个端口物理状态up但是协议状态down
过程分析
1、查看两端交换机端口状态，协议状态down的原因是因为动态链路聚合。
S10506X
HundredGigE1/0/0/14
Current state: UP
Line protocol state: DOWN(LAGG)
HundredGigE1/0/0/15
Current state: UP
Line protocol state: DOWN(LAGG)
6850
HundredGigE1/2/5
Current state: UP
Line protocol state: DOWN(LAGG)
HundredGigE1/2/7
Current state: UP
Line protocol state: DOWN(LAGG)
2、查看链路聚合详细信息，物理状态up但是协议状态down的几个端口在链路聚合中是未选中状态。
S10506X
Aggregate Interface: Bridge-Aggregation103
Creation Mode: Manual
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLANs: None
System ID: 0x8000, 40fe-956f-da00
Local:
Port Status Priority Index Oper-Key Flag
HGE1/0/0/13 S 32768 49 4 {ACDEF}
HGE1/0/0/14 U 32768 53 4 {ACDE}
HGE1/0/0/15 U 32768 59 4 {ACDE}
HGE1/0/0/16 S 32768 67 4 {ACDEF}
HGE2/0/0/13(R) S 32768 4 4 {ACDEF}
HGE2/0/0/14 S 32768 14 4 {ACDEF}
HGE2/0/0/15 S 32768 22 4 {ACDEF}
HGE2/0/0/16 S 32768 37 4 {ACDEF}
6850
Aggregate Interface: Bridge-Aggregation100
Creation Mode: Manual
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLANs: None
System ID: 0x8000, 642f-c759-9196
Local:
Port Status Priority Index Oper-Key Flag
HGE1/2/5 S 32768 11 11 {ACDEF}
HGE1/2/6 U 32768 21 11 {ACD}
HGE1/2/7 U 32768 22 11 {ACD}
HGE1/2/8 S 32768 23 11 {ACDEF}
HGE2/2/5 S 32768 34 11 {ACDEF}
HGE2/2/6 S 32768 44 11 {ACDEF}
HGE2/2/7 S 32768 45 11 {ACDEF}
HGE2/2/8 S 32768 46 11 {ACDEF}
3、查看相应配置，并无问题
S10506X
interface Bridge-Aggregation103
port link-type trunk
port trunk permit vlan all
link-aggregation mode dynamic
#
interface HundredGigE1/0/0/13
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 103
#
interface HundredGigE1/0/0/14
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 103
#
interface HundredGigE1/0/0/15
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 103
#
interface HundredGigE1/0/0/16
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 103
#
interface HundredGigE2/0/0/13
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 103
#
interface HundredGigE2/0/0/14
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 103
#
interface HundredGigE2/0/0/15
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 103
#
interface HundredGigE2/0/0/16
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 103
6850
interface Bridge-Aggregation100
port link-type trunk
port trunk permit vlan all
link-aggregation mode dynamic
#
interface HundredGigE1/2/5
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 100
#
interface HundredGigE1/2/5
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 100
#
interface HundredGigE1/2/7
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 100
#
interface HundredGigE1/2/8
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 100
#
interface HundredGigE2/2/5
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 100
#
interface HundredGigE2/2/6
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 100
#
interface HundredGigE2/2/7
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 100
#
interface HundredGigE2/2/9
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 100
4、收集debugging link-aggregation lacp packet all和debugging link-aggregation lacp fsm all发现两端lacp报文都有正常发送。但是从port-index发现了问题所在，是现场线缆插错导致LACP报文交互出了问题。
S10506X
*Jan 28 02:46:49:647 2022 GQY-9#-1F-Core LAGG/7/Packet: -MDC=1-Chassis=1-Slot=0; PACKET.HundredGigE1/0/0/15.send.
size=110, subtype=1, version=1
Actor: type=1, len=20, sys-pri=0x8000, sys-mac=40fe-956f-da00, key=0x4, pri=0x8000, port-index=0x3b, state=0x1d
Partner: type=2, len=20, sys-pri=0x8000, sys-mac=642f-c759-9196, key=0xb, pri=0x8000, port-index=0x16, state=0x5
Collector: type=3, len=16, col-max-delay=0x0
Terminator: type=0, len=0
*Jan 28 02:46:49:647 2022 GQY-9#-1F-Core LAGG/7/Packet: -MDC=1-Chassis=1-Slot=0; PACKET.HundredGigE1/0/0/15.send.
size=110, subtype=1, version=1
Actor: type=1, len=20, sys-pri=0x8000, sys-mac=40fe-956f-da00, key=0x4, pri=0x8000, port-index=0x3b, state=0x1d
Partner: type=2, len=20, sys-pri=0x8000, sys-mac=642f-c759-9196, key=0xb, pri=0x8000, port-index=0x16, state=0x5
Collector: type=3, len=16, col-max-delay=0x0
Terminator: type=0, len=0
*Jan 28 02:46:49:653 2022 GQY-9#-1F-Core LAGG/7/Packet: -MDC=1-Chassis=1-Slot=0; PACKET.HundredGigE1/0/0/15.receive.
size=110, subtype=1, version=1
Actor: type=1, len=20, sys-pri=0x8000, sys-mac=642f-c759-9196, key=0xb, pri=0x8000, port-index=0x16, state=0xd
Partner: type=2, len=20, sys-pri=0x8000, sys-mac=40fe-956f-da00, key=0x4, pri=0x8000, port-index=0x35, state=0x15
Collector: type=3, len=16, col-max-delay=0x0
Terminator: type=0, len=0
*Jan 3 17:05:29:900 2001 GQY-9#-3F-Corv LAGG/7/Packet: PACKET.HundredGigE1/2/7.receive.
size=110, subtype=1, version=1
Actor: type=1, len=20, sys-pri=0x8000, sys-mac=40fe-956f-da00, key=0x4, pri=0x8000, port-index=0x35, state=0x1d
Partner: type=2, len=20, sys-pri=0x8000, sys-mac=642f-c759-9196, key=0xb, pri=0x8000, port-index=0x15, state=0x5
Collector: type=3, len=16, col-max-delay=0x0
Terminator: type=0, len=0
*Jan 3 17:05:29:900 2001 GQY-9#-3F-Corv LAGG/7/Packet: PACKET.HundredGigE1/2/7.send.
size=110, subtype=1, version=1
Actor: type=1, len=20, sys-pri=0x8000, sys-mac=642f-c759-9196, key=0xb, pri=0x8000, port-index=0x16, state=0xd
Partner: type=2, len=20, sys-pri=0x8000, sys-mac=40fe-956f-da00, key=0x4, pri=0x8000, port-index=0x35, state=0x15
Collector: type=3, len=16, col-max-delay=0x0
Terminator: type=0, len=0
解决方法
交叉互联线缆，恢复正常链路
0
个评论
该案例暂时没有网友评论
编辑评论
✖
案例意见反馈
➤
✖
亲~登录后才可以操作哦!
确定
✖
✖
你的邮箱还未认证，请认证邮箱或绑定手机后进行当前操作
✖