Re: [swinog] EtherChannel - Long Time between LINK-3-UPDOWN and LINEPROTO-5-UPDOWN
Hi everyone, I've compiled all your input, here is the output: The cables are all cat5e, which should be OK. But to be sure I've managed to find a cat6 cable, but as expected, it did not change anything. So the cables are not the problem. Then I added speed 1000 and duplex full to the two port configuration, but: no change. Next step: Try mode on - Does not work because on is PAGP which is not compatible with LACP. Go on: Try switchport nonegotiate - No change in behaviour. When the servers are booting (BIOS, not yet OS) then there is no bonding/etherchannel available. Both ports are independent. That should be no problem for the mode active/passive and it works as expected, the server can do DHCP/PXE during boot. But it takes a long time until the server gets an IP from DHCP because it takes so long to get the protocol up. Is your server supporting LACP? During BIOS boot: no While running OS: yes How are is the bonding configured on the interfaces? During BIOS boot: not configured While running OS: configured with linux bonding (that works fine) Maybe this will stay a mysterium =) I wish everyone good luck in finding the easter-eggs. (Maybe this behavior is a cisco-easter-egg and solved after easter, who knows =) 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
Re: [swinog] EtherChannel - Long Time between LINK-3-UPDOWN and LINEPROTO-5-UPDOWN
Tobias: Why is pxe enabled? Is this device having its IOS image downloaded from a tftp server every time it boots up? That would account for the latency... Vinnie Connected by MOTOBLUR™ -Original message- From: Tobias Brunner tobias.brun...@nine.ch To: swinog@lists.swinog.ch Sent: Thu, Apr 5, 2012 16:21:26 GMT+02:00 Subject: Re: [swinog] EtherChannel - Long Time between LINK-3-UPDOWN and LINEPROTO-5-UPDOWN Hi everyone, I've compiled all your input, here is the output: The cables are all cat5e, which should be OK. But to be sure I've managed to find a cat6 cable, but as expected, it did not change anything. So the cables are not the problem. Then I added speed 1000 and duplex full to the two port configuration, but: no change. Next step: Try mode on - Does not work because on is PAGP which is not compatible with LACP. Go on: Try switchport nonegotiate - No change in behaviour. When the servers are booting (BIOS, not yet OS) then there is no bonding/etherchannel available. Both ports are independent. That should be no problem for the mode active/passive and it works as expected, the server can do DHCP/PXE during boot. But it takes a long time until the server gets an IP from DHCP because it takes so long to get the protocol up. Is your server supporting LACP? During BIOS boot: no While running OS: yes How are is the bonding configured on the interfaces? During BIOS boot: not configured While running OS: configured with linux bonding (that works fine) Maybe this will stay a mysterium =) I wish everyone good luck in finding the easter-eggs. (Maybe this behavior is a cisco-easter-egg and solved after easter, who knows =) 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
Re: [swinog] EtherChannel - Long Time between LINK-3-UPDOWN and LINEPROTO-5-UPDOWN
Hi, Tobias: Why is pxe enabled? Is this device having its IOS image downloaded from a tftp server every time it boots up? That would account for the latency... PXE is enabled on the server, not on the switch =) 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
Re: [swinog] EtherChannel - Long Time between LINK-3-UPDOWN and LINEPROTO-5-UPDOWN
Hi Tobias It may be a stupid question, but have you tried opening a SR with Cisco TAC ? :) Cheers! On 5 Apr 2012, at 17:41, Tobias Brunner wrote: Hi, Tobias: Why is pxe enabled? Is this device having its IOS image downloaded from a tftp server every time it boots up? That would account for the latency... PXE is enabled on the server, not on the switch =) 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 Mathias Seiler MiroNet GmbH, Strassburgerallee 86, CH-4055 Basel T +41 61 201 30 90, F +41 61 201 30 99 mathias.sei...@mironet.ch www.mironet.ch www.mirocloud.com ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] EtherChannel - Long Time between LINK-3-UPDOWN and LINEPROTO-5-UPDOWN
Hi Tobias Here are perhaps some hints... -channel-group NUMBER mode on: Is a static channel with NO channel protocol on it. If you speak LACP on the other side the channel won't come up because the neighbors don't agree to a channel. You need a channel-group NUMBER mode active on the switch side so it speaks LACP. Set it to this mode and run a debug on the switch so you can see more: debug lacp ? See: (http://www.cisco.com/en/US/docs/switches/lan/catalyst3560/software/release/15.0_1_se/command/reference/cli1.html#wp11890010) You can also fix the channel only to speak LACP with channel-protocol lacp in combination with channel-group NUMBER active. See: (http://www.cisco.com/en/US/docs/switches/lan/catalyst3560/software/release/15.0_1_se/command/reference/cli1.html#wp11890203) -switchport nonegotiate: disables DTP (dynamic trunking protocol) which is used to negotiate a trunk between to dtp speaking switches. If you set the port to switchport mode trunk on the switch side then you make a trunk on this port. See: (http://www.cisco.com/en/US/docs/switches/lan/catalyst3560/software/release/15.0_1_se/command/reference/cli3.html#wp1948171) . So in my point of view you don't need the switchport nonegotiate command. -speed 1000: if you fix the speed to 1Gbit then its always full duplex. There is no 1Gbit with halfduplex as far as I know. So the duplex full is also useless on this port. Generally speaking: If you fix the duplex mode and speed one side please watch out that you also fix it on the other side. So I would frist watch out that the channel comes up. For trunking and vlans on the trunks you can troubleshoot later. Cheers Luki Am 05.04.2012 16:21, schrieb Tobias Brunner: Hi everyone, I've compiled all your input, here is the output: The cables are all cat5e, which should be OK. But to be sure I've managed to find a cat6 cable, but as expected, it did not change anything. So the cables are not the problem. Then I added speed 1000 and duplex full to the two port configuration, but: no change. Next step: Try mode on - Does not work because on is PAGP which is not compatible with LACP. Go on: Try switchport nonegotiate - No change in behaviour. When the servers are booting (BIOS, not yet OS) then there is no bonding/etherchannel available. Both ports are independent. That should be no problem for the mode active/passive and it works as expected, the server can do DHCP/PXE during boot. But it takes a long time until the server gets an IP from DHCP because it takes so long to get the protocol up. Is your server supporting LACP? During BIOS boot: no While running OS: yes How are is the bonding configured on the interfaces? During BIOS boot: not configured While running OS: configured with linux bonding (that works fine) Maybe this will stay a mysterium =) I wish everyone good luck in finding the easter-eggs. (Maybe this behavior is a cisco-easter-egg and solved after easter, who knows =) Cheers, Tobias ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
