LAN Routing
cancel
Showing results for 
Search instead for 
Did you mean: 

Iussue: LAGG_INACTIVE_PARTNER

ABramante
Occasional Visitor

Iussue: LAGG_INACTIVE_PARTNER

Hi,

I have a problem. After to configuration link-aggregation. I see on the output this log:

%Jun 28 10:10:17:306 2017 SW2-SRV ARP/5/ARP_DUPLICATE_IPADDR_DETECT: Detected an IP address conflict. The device with MAC address 0015-5d05-68fb connected to Bridge-Aggregation2 in VLAN 1 and the device with MAC address 0015-5d05-67ff connected to Bridge-Aggregation1 in VLAN 1 are using the same IP address 172.20.5.112.
%Jun 28 16:36:51:744 2017 SW2-SRV ARP/5/ARP_DUPLICATE_IPADDR_DETECT: Detected an IP address conflict. The device with MAC address 7446-a083-780c connected to GigabitEthernet1/0/48 in VLAN 1 and the device with MAC address 0060-351c-fb2c connected to GigabitEthernet1/0/48 in VLAN 1 are using the same IP address 172.20.5.84.
%Jun 28 17:35:05:653 2017 SW2-SRV MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/48 was notified of a topology change.
%Jun 28 17:35:07:654 2017 SW2-SRV MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/48 was notified of a topology change.
%Jun 28 21:12:55:565 2017 SW2-SRV LAGG/5/LAGG_INACTIVE_PARTNER: Member port GigabitEthernet1/0/21 of aggregation group BAGG2 becomes INACTIVE because the port's partner is improper for being attached.
%Jun 29 08:38:40:262 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/39 link status is DOWN.
%Jun 29 08:38:40:262 2017 SW2-SRV LAGG/5/LAGG_INACTIVE_PHYSTATE: Member port GigabitEthernet1/0/39 of aggregation group BAGG4 becomes INACTIVE because the port's physical state (down) is improper for being attached.
%Jun 29 08:38:40:441 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/40 link status is DOWN.
%Jun 29 08:38:40:442 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/21 link status is DOWN.
%Jun 29 08:38:40:442 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/22 link status is DOWN.
%Jun 29 08:38:41:210 2017 SW2-SRV LAGG/5/LAGG_INACTIVE_PHYSTATE: Member port GigabitEthernet1/0/40 of aggregation group BAGG4 becomes INACTIVE because the port's physical state (down) is improper for being attached.
%Jun 29 08:38:41:468 2017 SW2-SRV IFNET/3/LINK_UPDOWN: Bridge-Aggregation4 link status is DOWN.
%Jun 29 08:38:41:468 2017 SW2-SRV IFNET/3/LINK_UPDOWN: Bridge-Aggregation2 link status is DOWN.
%Jun 29 08:38:48:385 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/22 link status is UP.
%Jun 29 08:38:48:385 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/39 link status is UP.
%Jun 29 08:38:48:414 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/40 link status is UP.
%Jun 29 08:38:51:960 2017 SW2-SRV LAGG/5/LAGG_ACTIVE: Member port GigabitEthernet1/0/39 of aggregation group BAGG4 becomes ACTIVE.
%Jun 29 08:38:51:981 2017 SW2-SRV IFNET/3/LINK_UPDOWN: Bridge-Aggregation4 link status is UP.
%Jun 29 08:38:51:981 2017 SW2-SRV LAGG/5/LAGG_ACTIVE: Member port GigabitEthernet1/0/22 of aggregation group BAGG2 becomes ACTIVE.
%Jun 29 08:38:52:087 2017 SW2-SRV IFNET/3/LINK_UPDOWN: Bridge-Aggregation2 link status is UP.
%Jun 29 08:39:21:929 2017 SW2-SRV MSTP/6/MSTP_FORWARDING: Instance 0's port Bridge-Aggregation2 has been set to forwarding state.
%Jun 29 08:39:21:929 2017 SW2-SRV MSTP/6/MSTP_DETECTED_TC: Instance 0's port Bridge-Aggregation2 detected a topology change.
%Jun 29 08:39:21:930 2017 SW2-SRV MSTP/6/MSTP_FORWARDING: Instance 0's port Bridge-Aggregation4 has been set to forwarding state.
%Jun 29 08:39:21:930 2017 SW2-SRV MSTP/6/MSTP_DETECTED_TC: Instance 0's port Bridge-Aggregation4 detected a topology change.
%Jun 29 08:42:57:418 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/39 link status is DOWN.
%Jun 29 08:42:57:419 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/22 link status is DOWN.
%Jun 29 08:42:57:419 2017 SW2-SRV LAGG/5/LAGG_INACTIVE_PHYSTATE: Member port GigabitEthernet1/0/39 of aggregation group BAGG4 becomes INACTIVE because the port's physical state (down) is improper for being attached.
%Jun 29 08:42:57:420 2017 SW2-SRV LAGG/5/LAGG_ACTIVE: Member port GigabitEthernet1/0/40 of aggregation group BAGG4 becomes ACTIVE.
%Jun 29 08:42:57:420 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/40 link status is DOWN.
%Jun 29 08:42:57:491 2017 SW2-SRV LAGG/5/LAGG_INACTIVE_PHYSTATE: Member port GigabitEthernet1/0/22 of aggregation group BAGG2 becomes INACTIVE because the port's physical state (down) is improper for being attached.
%Jun 29 08:42:57:564 2017 SW2-SRV IFNET/3/LINK_UPDOWN: Bridge-Aggregation2 link status is DOWN.
%Jun 29 08:42:59:965 2017 SW2-SRV LAGG/5/LAGG_ACTIVE: Member port GigabitEthernet1/0/40 of aggregation group BAGG4 becomes ACTIVE.
%Jun 29 08:43:00:010 2017 SW2-SRV IFNET/3/LINK_UPDOWN: Bridge-Aggregation4 link status is UP.
%Jun 29 08:43:00:071 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/22 link status is UP.
%Jun 29 08:43:00:241 2017 SW2-SRV IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/39 link status is UP.
%Jun 29 08:43:00:241 2017 SW2-SRV LAGG/5/LAGG_ACTIVE: Member port GigabitEthernet1/0/39 of aggregation group BAGG4 becomes ACTIVE.
%Jun 29 08:43:00:242 2017 SW2-SRV LAGG/5/LAGG_INACTIVE_PARTNER: Member port GigabitEthernet1/0/40 of aggregation group BAGG4 becomes INACTIVE because the port's partner is improper for being attached.
%Jun 29 08:43:03:162 2017 SW2-SRV LAGG/5/LAGG_ACTIVE: Member port GigabitEthernet1/0/21 of aggregation group BAGG2 becomes ACTIVE.
%Jun 29 08:43:03:174 2017 SW2-SRV IFNET/3/LINK_UPDOWN: Bridge-Aggregation2 link status is UP.
%Jun 29 08:43:09:766 2017 SW2-SRV LAGG/5/LAGG_INACTIVE_PARTNER: Member port GigabitEthernet1/0/21 of aggregation group BAGG2 becomes INACTIVE because the port's partner is improper for being attached.
%Jun 29 08:43:09:812 2017 SW2-SRV LAGG/5/LAGG_INACTIVE_PARTNER: Member port GigabitEthernet1/0/39 of aggregation group BAGG4 becomes INACTIVE because the port's partner is improper for being attached.
%Jun 29 08:43:11:818 2017 SW2-SRV LAGG/5/LAGG_ACTIVE: Member port GigabitEthernet1/0/22 of aggregation group BAGG2 becomes ACTIVE.
%Jun 29 08:43:11:868 2017 SW2-SRV LAGG/5/LAGG_ACTIVE: Member port GigabitEthernet1/0/40 of aggregation group BAGG4 becomes ACTIVE.

LAGG_INACTIVE_PARTNER: Member port GigabitEthernet of aggregation group BAGG becomes INACTIVE because the port's partner is improper for being attached.

Someone can help me to understand the problem?

Thanks

 

1 REPLY
it_ejvnior
Frequent Advisor

Re: Iussue: LAGG_INACTIVE_PARTNER

You need to ensure that the ports will become a part of the etherchannel has the same configurations on both sides.

Probably the switches are running STP as the default configuration and if you set the ports as an "edge port" then the switch will protect those ports against BPDU and the etherchannel will not work.

Ensure that you don't have an IP address conflict on the network, the Spanning Tree Protocol isn't misconfigured and you don't have "edge port enable" over the trunk ports. Use LACP to perform and create the etherchannel, so the protocol will handle this aggreagtion and you will avoid a switch loop.

I hope it can help you.

Regards.