Port-Channel

vishwancc · ‎04-19-2009

Hi All,

I am facing a very strange issue with my port-channel port.

The port is going down due to some reason and then coming back up.

There are no error on the port interface and i have already changed the port physically to different one.

This is the only port in the port channel which is having this issue.

And yes i have 5 ports in my port-channel bundle.

There is one more thing the vlan allowed on the ends are different ,but as i said out of 5 ports with same configuration only 1 is having this issue rest all the working fine.

interface FastEthernet4/4

switchport trunk encapsulation dot1q

switchport trunk allowed vlan x,x,x,x

switchport mode trunk

logging event link-status

speed 100

duplex full

channel-group 1 mode active

FastEthernet4/4 is up, line protocol is up (connected)

Hardware is Fast Ethernet Port, address is 0017.593a.8123 (bia 0017.593a.8123)

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 192/255, rxload 65/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, link type is auto, media type is 10/100BaseTX

input flow-control is unsupported output flow-control is unsupported

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:15, output never, output hang never

Last clearing of "show interface" counters 1d03h

Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 28097

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 25730000 bits/sec, 10540 packets/sec

5 minute output rate 75673000 bits/sec, 11408 packets/sec

719728814 packets input, 231640805874 bytes, 0 no buffer

Received 90645 broadcasts (6995 multicast)

0 runts, 0 giants, 0 throttles

1 input errors, 1 CRC, 0 frame, 0 overrun, 0 ignored

0 input packets with dribble condition detected

757223878 packets output, 590713356235 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

.Apr 17 15:47:15.710 GMT: %EC-5-UNBUNDLE: Interface Fa4/4 left the port-channel Po1

: .Apr 17 15:47:16.754 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/4, changed state to down

: .Apr 17 15:47:17.710 GMT: %LINK-3-UPDOWN: Interface FastEthernet4/4, changed state to down

: .Apr 17 15:47:20.846 GMT: %LINK-3-UPDOWN: Interface FastEthernet4/4, changed state to up

: .Apr 17 15:47:30.090 GMT: %EC-5-L3DONTBNDL2: Fa4/4 suspended: LACP currently not enabled on the remote port.

: .Apr 17 15:47:37.866 GMT: %LINK-3-UPDOWN: Interface FastEthernet4/4, changed state to down

: .Apr 17 15:47:41.846 GMT: %LINK-3-UPDOWN: Interface FastEthernet4/4, changed state to up

: .Apr 17 15:47:44.874 GMT: %EC-5-BUNDLE: Interface Fa4/4 joined port-channel Po1

: .Apr 17 15:47:45.914 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/4, changed state to up

: .Apr 17 15:51:37.101 GMT: %EC-5-UNBUNDLE: Interface Fa4/4 left the port-channel Po1

: .Apr 17 15:51:38.121 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/4, changed state to down

: .Apr 17 15:51:39.101 GMT: %LINK-3-UPDOWN: Interface FastEthernet4/4, changed state to down

: .Apr 17 15:51:41.840 GMT: %LINK-3-UPDOWN: Interface FastEthernet4/4, changed state to up

: .Apr 17 15:51:50.948 GMT: %EC-5-L3DONTBNDL2: Fa4/4 suspended: LACP currently not enabled on the remote port.

: .Apr 17 15:51:56.512 GMT: %LINK-3-UPDOWN: Interface FastEthernet4/4, changed state to down

: .Apr 17 15:52:00.840 GMT: %LINK-3-UPDOWN: Interface FastEthernet4/4, changed state to up

: .Apr 17 15:52:03.884 GMT: %EC-5-BUNDLE: Interface Fa4/4 joined port-channel Po1

: .Apr 17 15:52:04.900 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/4, changed state to up

Chao

Vishwa

mahmoodmkl · ‎04-19-2009

HI

channel-group 1 mode active

why u have placed the above line under the interface,is it applied to all interfaces or not..?

if u make the port channel as active then it will enable LACP rather Pagp.

The allowed range should be same on both ends ie on both the switches.

And i see that u trying to use LACP make sure that u have it configured on the other end.

Thanks

Mahmood

vishwancc · ‎04-20-2009

Hi Mahmood,

I want to run LACP only,as i have said i dont see any problem in the configuration since this port channel have 5 port out which only 1 is creating problem,if its the issue with configuration i would face this with all the ports.

Chao

Vishwa

Giuseppe Larosa · ‎04-20-2009

Hello Vishwa,

>> The port is going down due to some reason and then coming back up.

According to your log this port didn't hear LACP messages coming from the remote end:

.Apr 17 15:47:30.090 GMT: %EC-5-L3DONTBNDL2: Fa4/4 suspended: LACP currently not enabled on the remote port.

Verify if the other side is the right expected port.

Someone suggests for avoiding timing issues to use an interface range macro to enable all the ports at once when using LACP.

Hope to help

Giuseppe

vishwancc · ‎04-20-2009

Hi Giuspee,

If you see the port is first going down and then coming up and then the LCAP message,after that it joins the port channel again.

It dont seems to me the issue with LCAP.

these port channel are part of my oc3 link to ISP,incase this helps.

Chao

Vishwa