Re: LACP problem [SOLVED]

2017-10-08 Thread Charles Lecklider 
Just in case someone has the same problem and finds this thread, the
solution was to reboot the switch.

That was it - no other changes required.

Re: LACP problem

2017-09-20 Thread Charles Lecklider 
On 09/06/2017 04:07, Lyndon Nerenberg wrote:
> The first step is to have the switch display its idea of the LACP 
> configuration and status.  I haven't a clue how a TP-LINK does that, but on 
> our Junipers it's 'show lacp interfaces'.

So I finally found my serial cable


TL-SG3424#show lacp internal
Flags:  S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in active mode   P - Device is in passive mode
[...]
Channel group 6
  LACP port   AdminOperPort   Port
Port  Flags  StatePriorityKey  Key Number State
Gi1/0/9   SP Up   32768   0x6  0xf60   0x90x3c
Gi1/0/10  SP Down 32768   0x6  0   0xa0x44

TL-SG3424#show lacp neighbor

Flags:  S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in active mode   P - Device is in passive mode
[...]
Channel group 6
 LACP port  Admin  Oper   PortPort
Port  Flags  Priority   Dev ID  KeyKeyNumber  State
Gi1/0/9   SA 32768  0cc4.7ad9.ead0  0  0x405c 0x5 0x3d
Gi1/0/10  SP 0  ..  0  0  0   0


I'm not sure if any of that is informative in any way?

Re: LACP problem

2017-06-10 Thread Charles Lecklider 
On 10/06/2017 19:15, Lyndon Nerenberg wrote:
> Not really, other than running tcpdump on the two interfaces and
> examining the LACP protocol packets to try to discover why the
> negotiation is acting the way it is.

OK, that sounds like an even deeper rabbit-hole.

> Also, if you don't have the enable password, how did you configure
> LACP on the switch to begin with?

Fair question: via the web UI. That would imply it's not just a
front-end for the CLI, which implies another set of potential security
issues. Not an issue for this network, but certainly something to
consider in future.

Re: LACP problem

2017-06-10 Thread Charles Lecklider 
On 09/06/2017 04:07, Lyndon Nerenberg wrote:
> The first step is to have the switch display its idea of the LACP
> configuration and status.

That's turning into a bit of a mission

Seems TP-LINK don't set an enable password by default so I can't get
what I need via ssh until I've set that. To set it I need to connect to
the console port, which means finding the cable and a serial-to-USB adapter.
I have all the above (somewhere), it's just going to take some time.

Is there no other diagnostic information I can get from the OpenBSD side?

LACP problem

2017-06-08 Thread Charles Lecklider 
I'm trying to get LACP working over 2 ports (em0, em1). I've done this
successfully with FreeBSD and 4 ports on the same switch so I know it
can be done, I just can't get it working with OpenBSD. I'm hoping I've
just botched the config somewhere.

The switch is a TP-LINK TL-SG3424, latest firmware available, and LACP
is set to passive for the two ports (I've tried active, too).

hostname.em0:
mtu 9000 up

hostname,em1:
mtu 9000 up

hostname.trunk0:
trunkport em0 trunkport em1 trunkproto lacp
inet 10.1.2.1 255.255.255.0 NONE


>From my reading of the man pages that's all I need to do, and ifconfig
seems to agree:

em0: flags=8b43
mtu 9000
lladdr 0c:c4:7a:d9:ea:d0
index 5 priority 0 llprio 3
trunk: trunkdev trunk0
media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause)
status: active
em1: flags=8b43
mtu 9000
lladdr 0c:c4:7a:d9:ea:d0
index 6 priority 0 llprio 3
trunk: trunkdev trunk0
media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause)
status: active

trunk0: flags=8843 mtu 9000
lladdr 0c:c4:7a:d9:ea:d0
index 11 priority 0 llprio 3
trunk: trunkproto lacp
trunk id: [(8000,0c:c4:7a:d9:ea:d0,405C,,),
 (8000,30:b5:c2:07:81:4a,0CF3,,)]
trunkport em1
trunkport em0 active,collecting,distributing
groups: trunk
media: Ethernet autoselect
status: active
inet 10.1.2.1 netmask 0xff00 broadcast 10.1.2.255


The trunk is there, seems to be configured the right way, but the second
port doesn't come up. If I pull the cable on em0, em1 comes up, put the
cable back, em0 doesn't join the trunk.


Have I botched the config somewhere? Or is there some incompatibility
going on between OpenBSD and the switch? And if it's the latter, how do
I get some diagnostic information to work out what's going on?

Thanks!




OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr  1 13:45:56 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17134788608 (16341MB)
avail mem = 16610807808 (15841MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x7f4d8000 (53 entries)
bios0: vendor American Megatrends Inc. version "1.1a" date 08/27/2015
bios0: Supermicro A1SAi
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP FPDT FIDT SPMI MCFG WDAT UEFI APIC BDAT HPET
SSDT HEST BERT ERST EINJ
acpi0: wakeup devices PEX1(S0) PEX2(S0) PEX3(S0) PEX4(S0) EHC1(S0)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Atom(TM) CPU C2550 @ 2.40GHz, 2400.44 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: TSC frequency 2400438240 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 100MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Atom(TM) CPU C2550 @ 2.40GHz, 2400.01 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Atom(TM) CPU C2550 @ 2.40GHz, 2400.01 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu2: 1MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Atom(TM) CPU C2550 @ 2.40GHz, 2400.01 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu3: 1MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEX1)
acpiprt2 at acpi0: bus 2 (BR04)
acpiprt3 at acpi0: bus 3 (P