Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 112
  • Last Modified:

Cisco L2/L3 Switch Unable to Communicate with L3 LACP

Hello Experts,

I posted a similar question yesterday, however I don't think I really got the answer I was hoping for. Therefore, I would like to post the question again.

The question is can someone let me know why I can't ping across the L3 port-channels. 172.16.1.1 and 172.16.1.2.

The interfaces are up and the channels are looking good:

There is also an adjacency across eigrp.

dlsw-5#
dlsw-5#show ip int brie
Interface              IP-Address      OK? Method Status                Protocol
Ethernet0/0            unassigned      YES manual up                    up      
Ethernet0/1            unassigned      YES manual up                    up      
Ethernet0/2            unassigned      YES unset  administratively down down    
Ethernet0/3            unassigned      YES unset  administratively down down    
Ethernet1/0            unassigned      YES unset  administratively down down    
Ethernet1/1            unassigned      YES unset  administratively down down    
Ethernet1/2            unassigned      YES unset  administratively down down    
Ethernet1/3            unassigned      YES unset  administratively down down    
Port-channel1          172.16.1.2      YES manual up                    up      
Vlan1                  unassigned      YES unset  administratively down down    
dlsw-5#



Group  Port-channel  Protocol    Ports
------+-------------+-----------+-----------------------------------------------
1      Po1(RU)         LACP      Et0/0(P)    Et0/1(P)    

dlsw-5#

EIGRP-IPv4 Neighbors for AS(100)
H   Address                 Interface              Hold Uptime   SRTT   RTO  Q  Seq
                                                   (sec)         (ms)       Cnt Num
0   172.16.1.1              Po1                      11 00:00:08    1  4500  1  0
dlsw-5#

Having said all of that I am getting the following error:

dlsw-5#
*Aug 26 09:04:54.371: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.1.1 (Port-channel1) is down: retry limit exceeded
dlsw-5#
*Aug 26 09:04:57.335: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.1.1 (Port-channel1) is up: new adjacency
dlsw-5#
*Aug 26 09:06:16.925: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.1.1 (Port-channel1) is down: retry limit exceeded
*Aug 26 09:06:17.610: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.1.1 (Port-channel1) is up: new adjacency
dlsw-5#

I have attached the configs

Any help will be greatly appreciated.

Cheers

Carlton
15-48-31--DLSW-4-64.187.124.3-.txt
15-48-37--DLSW-5-64.187.124.3-.txt
0
Member_2_7966113
Asked:
Member_2_7966113
  • 3
  • 2
1 Solution
 
Member_2_7966113Author Commented:
I am now getting the following error message

Aug 26 09:18:12.035: EIGRP: Handle deallocation failure [0]
*Aug 26 09:18:12.035: EIGRP: Neighbor 172.16.1.1 went down on Port-channel1
0
 
Member_2_7966113Author Commented:
I'm using i86bi-linux-l2-adventerprisek9-15.2d
0
 
eeRootCommented:
Since you are using the "no switchport" command, you may need to add the "ip information-reply" command as well.

See -> http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipapp/command/iap-cr-book/iap-i1.html#wp1706748839
0
 
Member_2_7966113Author Commented:
eeRoot

Thanks for the link. That solved the problem. Cheers
0
 
eeRootCommented:
the author indicted that the command "ip information-reply" resolved the issue
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now