Tobias: Now that you have shown this show interface command output and i see all the connections are flapping up and down for so long i am even more so convinced that this is a layer 1 problem and i am sure it has something to do with the cables. replace all the ethernet cables with NEW minmum CAT 6 cables and I would bet that the problem disappears straightaway. Let me know. Cheers!
Vincent Watson Senior System Technologist EMEA Quantum Storage GmbH +4179 294 3229 -----Original Message----- From: Tobias Brunner [mailto:tobias.brun...@nine.ch] Sent: Wednesday, April 4, 2012 03:11 AM To: swinog@lists.swinog.ch Subject: Re: [swinog] EtherChannel - Long Time between LINK-3-UPDOWN and LINEPROTO-5-UPDOWN Hi all, Thanks for the input so far. I've merged all the input of you (and the trunk/vlan configuration I need to use) and this is how the configuration looks right now: interface GigabitEthernet1/0/1 switchport trunk encapsulation dot1q switchport trunk native vlan 27 switchport trunk allowed vlan 27,453 switchport mode trunk no cdp enable spanning-tree portfast trunk spanning-tree bpdufilter enable channel-group 1 mode active ! interface GigabitEthernet2/0/1 switchport trunk encapsulation dot1q switchport trunk native vlan 27 switchport trunk allowed vlan 27,453 switchport mode trunk no cdp enable spanning-tree portfast trunk spanning-tree bpdufilter enable channel-group 1 mode active ! interface Port-channel1 switchport trunk encapsulation dot1q switchport trunk native vlan 27 switchport trunk allowed vlan 27,453 switchport mode trunk spanning-tree portfast trunk spanning-tree bpdufilter enable end It's not possible to just configure the "channel-group" on the GiX interfaces and all the rest on Po1 (as suggested by Steven), I had to add at least the "switchport" settings (otherwise the switch complains about not compatible ports). The addition of the spanning-tree settings to Po1 did not change the behaviour either. Also the used cables should be OK. And now, when I power on the server, this is the output of the switch-log (The server boots from Network, then from local disk with Debian and bonding configured: Apr 4 09:00:06 192.168.1.144 152: *Mar 15 17:05:41.781: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to up Apr 4 09:00:06 192.168.1.144 153: *Mar 15 17:05:41.781: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up Apr 4 09:00:15 192.168.1.144 154: *Mar 15 17:05:51.202: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to down Apr 4 09:00:16 192.168.1.144 155: *Mar 15 17:05:52.250: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down Apr 4 09:00:17 192.168.1.144 156: *Mar 15 17:05:53.525: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to up Apr 4 09:00:18 192.168.1.144 157: *Mar 15 17:05:54.607: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up Apr 4 09:00:30 192.168.1.144 158: *Mar 15 17:06:05.907: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to down Apr 4 09:00:30 192.168.1.144 159: *Mar 15 17:06:05.924: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down Apr 4 09:00:32 192.168.1.144 160: *Mar 15 17:06:08.465: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to up Apr 4 09:00:32 192.168.1.144 161: *Mar 15 17:06:08.482: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up Apr 4 09:00:47 192.168.1.144 162: *Mar 15 17:06:22.701: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to down Apr 4 09:00:47 192.168.1.144 163: *Mar 15 17:06:22.718: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down Apr 4 09:00:49 192.168.1.144 164: *Mar 15 17:06:25.050: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to up Apr 4 09:00:49 192.168.1.144 165: *Mar 15 17:06:25.285: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up Apr 4 09:00:54 192.168.1.144 166: *Mar 15 17:06:29.957: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down Apr 4 09:00:54 192.168.1.144 167: *Mar 15 17:06:30.116: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to down Apr 4 09:00:56 192.168.1.144 168: *Mar 15 17:06:32.515: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to up Apr 4 09:00:56 192.168.1.144 169: *Mar 15 17:06:32.641: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up Apr 4 09:01:35 192.168.1.144 170: *Mar 15 17:07:10.768: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down Apr 4 09:01:37 192.168.1.144 171: *Mar 15 17:07:13.125: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up Apr 4 09:01:59 192.168.1.144 172: *Mar 15 17:07:35.430: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/1, changed state to up Apr 4 09:02:39 192.168.1.144 173: *Mar 15 17:08:15.142: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up Apr 4 09:02:56 192.168.1.144 174: *Mar 15 17:08:32.246: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to down Apr 4 09:02:56 192.168.1.144 175: *Mar 15 17:08:33.253: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down Apr 4 09:03:00 192.168.1.144 176: *Mar 15 17:08:35.753: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up Apr 4 09:03:15 192.168.1.144 177: *Mar 15 17:08:51.649: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/1, changed state to down Apr 4 09:03:16 192.168.1.144 178: *Mar 15 17:08:52.446: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down Apr 4 09:03:16 192.168.1.144 179: *Mar 15 17:08:52.672: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to down Apr 4 09:03:19 192.168.1.144 180: *Mar 15 17:08:54.979: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up Apr 4 09:03:37 192.168.1.144 181: *Mar 15 17:09:13.308: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to up Apr 4 09:04:22 192.168.1.144 182: *Mar 15 17:09:57.835: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up Apr 4 09:04:23 192.168.1.144 183: *Mar 15 17:09:58.825: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up Apr 4 09:04:24 192.168.1.144 184: *Mar 15 17:09:59.722: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/1, changed state to up Apr 4 09:04:24 192.168.1.144 185: *Mar 15 17:09:59.832: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up As you can see, the ports go up and down many times (very strange, but maybe this is "by-design"). And it takes always 1 minute between LINK-3-UPDOWN and LINEPROTO-5-UPDOWN. The thing that makes me thinking of that this should be explainable: Why does it take always 1 minute? Is there something that can be configured which causes this delay? What does the switch expect? What does it wait for? It's nice to get good input in this mailing list! Thanks for that! =) Cheers, Tobias -- Nine Internet Solutions AG, Albisriederstr. 243a, CH-8047 Zuerich Support +41 44 637 40 40 | Tel +41 44 637 40 00 | Direct +41 44 637 40 13 Skype nine.ch_support _______________________________________________ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
_______________________________________________ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
