swinog

swinog@lists.swinog.ch

1 participants
2934 discussions

Private VLAN with none-private-vlan speaking switch in between
by Lukas Eisenberger 17 Apr '12

17 Apr '12

Hi Does somebody know if its possible to connect two private-vlan speaking switches (Cisco 3560/3750) with a none-private-vlan speaking switch in between? Does that work so that I can still use the community/isolated vlans on both private-vlan speaking switches? ( http://www.cisco.com/en/US/docs/switches/lan/catalyst3560/software/release/… ) [3650] <------> HP Switch <------> [3650] Cheers Luki

2 1

webland
by Fabian Abplanalp 15 Apr '12

15 Apr '12

Sawadeekap Is there any webland.ch Admin on this List? Thx. Fabiana

1 0

www.nic.ch
by Matthias Hertzog 14 Apr '12

14 Apr '12

Good morning Anyone able to reach www.nic.ch ? Have a nice day, Matthias _________________________________________ mhs @ internet AG Zürcherstrasse 204, CH - 9014 St. Gallen Phone +41 71 274 93 93, Fax +41 71 274 93 94 http://www.mhs.ch _________________________________________

4 5

Ideal fanless box for a small IP-PBX @ricardo
by Stanislav Sinyagin 06 Apr '12

06 Apr '12

might be useful for someone: ricardo.ch -> article no. 672073182 Here I made voice tests with a similar CPU: http://txlab.wordpress.com/2012/03/12/freeswitch-performance-test-on-amd-ge… The item at Ricardo has a built-in hard drive, which is convenient for CDR and voice recordings. The only limitation, the seller does not want to send it by post. cheers, stan

1 0

EtherChannel - Long Time between LINK-3-UPDOWN and LINEPROTO-5-UPDOWN
by Tobias Brunner 05 Apr '12

05 Apr '12

Hi there, Maybe there are some Cisco specialists reading this List =) On a WS-C3750X it tooks about 1 minute after connecting a port to change the status from LINK-3-UPDOWN "up" to LINEPROTO-5-UPDOWN "up" Mar 27 16:25:37 192.168.1.144 788: *Mar 8 00:30:48.032: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up Mar 27 16:26:38 192.168.1.144 790: *Mar 8 00:31:49.227: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up Mar 27 16:25:54 192.168.1.144 789: *Mar 8 00:31:05.086: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/1, changed state to up Mar 27 16:26:56 192.168.1.144 791: *Mar 8 00:32:06.583: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/1, changed state to up The ports are configured like that: interface GigabitEthernet1/0/1 switchport access vlan 27 switchport mode access spanning-tree portfast spanning-tree bpdufilter enable channel-group 1 mode active ! interface GigabitEthernet2/0/1 switchport access vlan 27 switchport mode access spanning-tree portfast spanning-tree bpdufilter enable channel-group 1 mode active ! interface Port-channel1 switchport access vlan 27 switchport mode access end The server which is connected has nothing special configured... It should boot via DHCP/PXE (of course without Bonding) and then the installed Linux with Bonding configured. Does anyone have an idea why this takes so long? Thanks! 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

8 12

SwiNOG #24, Registration is open
by Steven Glogger 04 Apr '12

04 Apr '12

Dear SwiNOGers, The registration for SwiNOG #24 is officially open since about 3 weeks! Looks like almost no one is reading our CFP :) Speakers: do NOT register yet, you will get an email with a voucher code. If you register you will have to pay but you will get a voucher for the next event. Registration: https://register.swinog.ch/ Have a nice day! -steven

1 0

Re: [swinog] EtherChannel - Long Time between LINK-3-UPDOWN and LINEPROTO-5-UPDOWN
by vwatson＠dancendrumarts.com 04 Apr '12

04 Apr '12

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.brunner@nine.ch] Sent: Wednesday, April 4, 2012 03:11 AM To: swinog(a)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(a)lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

1 0

Cisco WLAN Controller
by Silvan Gebhardt 03 Apr '12

03 Apr '12

Hi Swinog, I am currently looking for a WLAN controller for cisco for at least the 15 AP model. We are needing that urgently - haven't managed to get one so far - for our even that runs over easter. if someone is not aware of it - www.easterhegg.ch. This is an Hacker event. If someone could help us out please contact me offlist, it would be greatly appreciated! Best Silvan

2 1

Fwd: Re: Re: Youtube Problem
by Jeroen Massar 02 Apr '12

02 Apr '12

It is vacation time! As a general reminder: It is always sad to see that people do not understand that their vacation tools should ignore mails that have a "Precedence: list" header set... for the folks who use these autoresponders, please make sure that it handles mailinglists properly: ignores it. Greets, Jeroen -------- Original Message -------- Subject: Re: Re: [swinog] Youtube Problem Date: 2 Apr 2012 11:53:18 +0200 From: bruce.*****(a)*******.ch To: jeroen(a)unfix.org Sehr geehrte Damen und Herren, Ich bin zurzeit ausser Haus und voraussichtlich am 2. April 2012 wieder im Büro erreichbar. Falls es mir möglich ist, werde ich Ihre E-Mail vorher beantworten. Ihre E-Mail wird nicht weitergeleitet. In dringenden Fällen wenden Sie sich bitte an Francis *****, francis.********(a)homing.ch oder an das ********* Team: *********** Vielen Dank und freundliche Grüsse Bruce ******** ...more contact details scrapped...

1 0

Youtube Problem
by Rolf Tschumi 02 Apr '12

02 Apr '12

is a problem in the net? videos of youtube go very slowly to which come, and it gives again and again interruptions? is you which well-known? rolf

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog