Re: OT: Dell EMC switches
Hello guys, Thanks for replies. To add some more info for the case. We have DWDM network with star topology. Switches will be connected to center point with 100G uplink (currently 10G or 2x10G) via DWDM lambda. Customers are connected to 10G ports. We carry Internet traffic and IPTV multicast to regional ISPs over VLANs. What is important for me is switch to be capable to carry traffic on wire speed without packet loss. Latency is not big issue here. I will also have a look at Arista switches. Thanks a lot for the help, Ivo On 10.4.2021 г. 00:10 ч., Tom Smyth wrote: +1 re arista switches... On Friday, 9 April 2021, Diana Eichert wrote: I second Arista switches, in my day job we use a lot of Arista switches. Though one of the "issues" we see is Arista drops older tech regularly. I believe their last presentation to us was 25G/100G/400G switches. On Thu, Apr 8, 2021 at 1:18 PM Mischa wrote: Hi Ivo, I don’t have any experience with the Dell switches but what about the Arista DCS-7050QX-32 or DCS-7050QX-32S? 32x40G QSFP+ for the 7050QX-32 32x40G QSFP+ of which one QSFP+ can act as a dual personality to 4xSFP+ for the 7050QX-32S. (mind the S) There are converters for the QSFP+ to turn them into a SFP+ port if you need more 10G but want to have a way to migrate to 40G. You can do this with the Mellanox 655902-001 QSA adapter. Which is pretty much what we have in production. :) Are you planning to buy new or eBay? There are some pretty good deals on eBay. Mischa
Lenovo Thinkpad X1 Extreme Gen 3 patch
Hi everyone,
the following diff against -current has the PCI device IDs for the AX201
wireless LAN and the Thunderbolt 3 bridge on the Lenovo Thinkpad X1
Extreme Gen 3. I have this running without noticeable problems, and the
QuZ firmware seems to work well with the iwx driver, although I guess it
could be updated at some point.
Maybe somebody would like to take a look at this diff?
Happy to provide pcidump and/or dmesg of this machine if anyone is
interested.
Remaining problems: PCH cAVS is detected but azalia driver does not
attach, so no sound. Power management (fans on all the time, gets warm,
battery life 2h whereas it is 10h on Linux kernel 5.11).
Does anyone else have this laptop as well?
best,
- ivo
Index: if_iwx.c
===
RCS file: /cvs/src/sys/dev/pci/if_iwx.c,v
retrieving revision 1.50
diff -u -p -r1.50 if_iwx.c
--- if_iwx.c17 Mar 2021 15:59:27 - 1.50
+++ if_iwx.c13 Apr 2021 10:56:13 -
@@ -7711,6 +7711,8 @@ static const struct pci_matchid iwx_devi
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_22500_2 },
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_22500_3 },
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_22500_4,},
+ { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_22500_5,},
};
static const struct pci_matchid iwx_subsystem_id_ax201[] = {
@@ -7751,6 +7753,7 @@ iwx_match(struct device *parent, iwx_mat
case PCI_PRODUCT_INTEL_WL_22500_2: /* AX201 */
case PCI_PRODUCT_INTEL_WL_22500_3: /* AX201 */
case PCI_PRODUCT_INTEL_WL_22500_4: /* AX201 */
+ case PCI_PRODUCT_INTEL_WL_22500_5: /* AX201 */
for (i = 0; i < nitems(iwx_subsystem_id_ax201); i++) {
if (svid == iwx_subsystem_id_ax201[i].pm_vid &&
spid == iwx_subsystem_id_ax201[i].pm_pid)
@@ -7938,6 +7941,7 @@ iwx_attach(struct device *parent, struct
break;
case PCI_PRODUCT_INTEL_WL_22500_2:
case PCI_PRODUCT_INTEL_WL_22500_3:
+ case PCI_PRODUCT_INTEL_WL_22500_5:
if (sc->sc_hw_rev != IWX_CSR_HW_REV_TYPE_QUZ) {
printf("%s: unsupported AX201 adapter\n", DEVNAME(sc));
return;
Index: pcidevs.h
===
RCS file: /cvs/src/sys/dev/pci/pcidevs.h,v
retrieving revision 1.1957
diff -u -p -r1.1957 pcidevs.h
--- pcidevs.h 9 Apr 2021 20:59:03 - 1.1957
+++ pcidevs.h 13 Apr 2021 10:56:14 -
@@ -3970,6 +3970,9 @@
#define PCI_PRODUCT_INTEL_JHL6340 0x15d9 /* JHL6340 Thunderbolt
3 */
#define PCI_PRODUCT_INTEL_JHL6340_PCIE 0x15da /* JHL6340 Thunderbolt
3 */
#define PCI_PRODUCT_INTEL_JHL6340_XHCI 0x15db /* JHL6340 Thunderbolt
3 */
+#definePCI_PRODUCT_INTEL_JHL7540_PCIE 0x15ea /* JHL7540
Thunderbolt 3 */
+#definePCI_PRODUCT_INTEL_JHL7540_XHCI 0x15eb /* JHL7540
Thunderbolt 3 */
+#definePCI_PRODUCT_INTEL_JHL7540_USB 0x15ec /* JHL7540
Thunderbolt 3 USB */
#define PCI_PRODUCT_INTEL_I219_LM8 0x15df /* I219-LM */
#define PCI_PRODUCT_INTEL_I219_V8 0x15e0 /* I219-V */
#define PCI_PRODUCT_INTEL_I219_LM9 0x15e1 /* I219-LM */
@@ -5006,6 +5009,7 @@
#define PCI_PRODUCT_INTEL_495SERIES_LP_XDCI 0x34ee /* 495 Series
xDCI */
#define PCI_PRODUCT_INTEL_495SERIES_LP_SRAM 0x34ef /* 495 Series
Shared SRAM */
#define PCI_PRODUCT_INTEL_WL_22500_40x34f0 /* Wi-Fi 6 AX201 */
+#definePCI_PRODUCT_INTEL_WL_22500_50x06f0 /* Wi-Fi 6
AX201 */
#define PCI_PRODUCT_INTEL_495SERIES_LP_SDXC 0x34f8 /* 495 Series
SDXC */
#define PCI_PRODUCT_INTEL_495SERIES_LP_GSPI_3 0x34fb /* 495 Series
GSPI */
#define PCI_PRODUCT_INTEL_495SERIES_LP_ISH 0x34fc /* 495 Series
ISH */
Index: pcidevs_data.h
===
RCS file: /cvs/src/sys/dev/pci/pcidevs_data.h,v
retrieving revision 1.1952
diff -u -p -r1.1952 pcidevs_data.h
--- pcidevs_data.h 9 Apr 2021 20:59:03 - 1.1952
+++ pcidevs_data.h 13 Apr 2021 10:56:15 -
@@ -13292,6 +13292,18 @@ static const struct pci_known_product pc
"JHL6340 Thunderbolt 3",
},
{
+ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_JHL7540_PCIE,
+ "JHL7540 Thunderbolt 3",
+ },
+ {
+ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_JHL7540_XHCI,
+ "JHL7540 Thunderbolt 3",
+ },
+ {
+ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_JHL7540_USB,
+ "JHL7540 Thunderbolt 3 USB Controller",
+ },
+ {
PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_I219_LM8,
"I219-LM",
},
@@ -17433,6 +17445,10 @@ static const struct pci_known_product pc
},
{
PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_22500_4,
+
Lenovo Thinkpad X1 Extreme Gen 3 patch
Hi everyone,
the following diff against -current has the PCI device IDs for the AX201
wireless LAN and the Thunderbolt 3 bridge on the Lenovo Thinkpad X1
Extreme Gen 3. I have this running without noticeable problems, and the
QuZ firmware seems to work well with the iwx driver, although I guess it
could be updated at some point.
Maybe somebody would like to take a look at this diff?
Happy to provide pcidump and/or dmesg of this machine if anyone is
interested.
Remaining problems: PCH cAVS is detected but azalia driver does not
attach, so no sound. Power management (fans on all the time, gets warm,
battery life 2h whereas it is 10h on Linux kernel 5.11).
Does anyonw else have this laptop as well?
best,
- ivo
Index: if_iwx.c
===
RCS file: /cvs/src/sys/dev/pci/if_iwx.c,v
retrieving revision 1.50
diff -u -p -r1.50 if_iwx.c
--- if_iwx.c17 Mar 2021 15:59:27 - 1.50
+++ if_iwx.c13 Apr 2021 10:56:13 -
@@ -7711,6 +7711,8 @@ static const struct pci_matchid iwx_devi
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_22500_2 },
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_22500_3 },
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_22500_4,},
+ { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_22500_5,},
};
static const struct pci_matchid iwx_subsystem_id_ax201[] = {
@@ -7751,6 +7753,7 @@ iwx_match(struct device *parent, iwx_mat
case PCI_PRODUCT_INTEL_WL_22500_2: /* AX201 */
case PCI_PRODUCT_INTEL_WL_22500_3: /* AX201 */
case PCI_PRODUCT_INTEL_WL_22500_4: /* AX201 */
+ case PCI_PRODUCT_INTEL_WL_22500_5: /* AX201 */
for (i = 0; i < nitems(iwx_subsystem_id_ax201); i++) {
if (svid == iwx_subsystem_id_ax201[i].pm_vid &&
spid == iwx_subsystem_id_ax201[i].pm_pid)
@@ -7938,6 +7941,7 @@ iwx_attach(struct device *parent, struct
break;
case PCI_PRODUCT_INTEL_WL_22500_2:
case PCI_PRODUCT_INTEL_WL_22500_3:
+ case PCI_PRODUCT_INTEL_WL_22500_5:
if (sc->sc_hw_rev != IWX_CSR_HW_REV_TYPE_QUZ) {
printf("%s: unsupported AX201 adapter\n", DEVNAME(sc));
return;
Index: pcidevs.h
===
RCS file: /cvs/src/sys/dev/pci/pcidevs.h,v
retrieving revision 1.1957
diff -u -p -r1.1957 pcidevs.h
--- pcidevs.h 9 Apr 2021 20:59:03 - 1.1957
+++ pcidevs.h 13 Apr 2021 10:56:14 -
@@ -3970,6 +3970,9 @@
#definePCI_PRODUCT_INTEL_JHL6340 0x15d9 /* JHL6340
Thunderbolt 3 */
#definePCI_PRODUCT_INTEL_JHL6340_PCIE 0x15da /* JHL6340
Thunderbolt 3 */
#definePCI_PRODUCT_INTEL_JHL6340_XHCI 0x15db /* JHL6340
Thunderbolt 3 */
+#definePCI_PRODUCT_INTEL_JHL7540_PCIE 0x15ea /* JHL7540
Thunderbolt 3 */
+#definePCI_PRODUCT_INTEL_JHL7540_XHCI 0x15eb /* JHL7540
Thunderbolt 3 */
+#definePCI_PRODUCT_INTEL_JHL7540_USB 0x15ec /* JHL7540
Thunderbolt 3 USB */
#definePCI_PRODUCT_INTEL_I219_LM8 0x15df /* I219-LM */
#definePCI_PRODUCT_INTEL_I219_V8 0x15e0 /* I219-V */
#definePCI_PRODUCT_INTEL_I219_LM9 0x15e1 /* I219-LM */
@@ -5006,6 +5009,7 @@
#definePCI_PRODUCT_INTEL_495SERIES_LP_XDCI 0x34ee /* 495
Series xDCI */
#definePCI_PRODUCT_INTEL_495SERIES_LP_SRAM 0x34ef /* 495
Series Shared SRAM */
#definePCI_PRODUCT_INTEL_WL_22500_40x34f0 /* Wi-Fi 6
AX201 */
+#definePCI_PRODUCT_INTEL_WL_22500_50x06f0 /* Wi-Fi 6
AX201 */
#definePCI_PRODUCT_INTEL_495SERIES_LP_SDXC 0x34f8 /* 495
Series SDXC */
#definePCI_PRODUCT_INTEL_495SERIES_LP_GSPI_3 0x34fb /* 495
Series GSPI */
#definePCI_PRODUCT_INTEL_495SERIES_LP_ISH 0x34fc /* 495
Series ISH */
Index: pcidevs_data.h
===
RCS file: /cvs/src/sys/dev/pci/pcidevs_data.h,v
retrieving revision 1.1952
diff -u -p -r1.1952 pcidevs_data.h
--- pcidevs_data.h 9 Apr 2021 20:59:03 - 1.1952
+++ pcidevs_data.h 13 Apr 2021 10:56:15 -
@@ -13292,6 +13292,18 @@ static const struct pci_known_product pc
"JHL6340 Thunderbolt 3",
},
{
+ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_JHL7540_PCIE,
+ "JHL7540 Thunderbolt 3",
+ },
+ {
+ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_JHL7540_XHCI,
+ "JHL7540 Thunderbolt 3",
+ },
+ {
+ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_JHL7540_USB,
+ "JHL7540 Thunderbolt 3 USB Controller",
+ },
+ {
PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_I219_LM8,
"I219-LM",
},
@@ -17433,6 +17445,10 @@ static const struct
Re: Technical Documentation - CARP
Hi Jannick the man pages are also a good up to date source of information... sometimes a paper from a few years ago states something like X/Y is not supported... but as an OpenBSD developer once quiped "yes we do add features from time to time" :) so the papers can give really good context and insights... but refer to the manuals also to validate any improved syntax and or features Hope this helps Tom Smyth On Tue, 13 Apr 2021 at 09:34, jannick Weiss wrote: > > Hello,my name is Jannick Weiss and i am currently in the process of taking > my education as a datatechnician. As part of my education i have to do a > presentation on a self-elected subject and i have chosen to talk about CARP. > > It is my understanding that it is you (OpenBSD) that have developed CARP. > I am having trouble finding information about CARP, such as the different > states the protocol goes through or how the election of the master node > works specifically. > If you can provide any documentation on CARP it would be greatly > appreciated. > > In advance, thank you for any help you may provide. > > Best regards > > Jannick Weiss -- Kindest regards, Tom Smyth.
Re: Technical Documentation - CARP
On 2021-04-13, Janne Johansson wrote: > Den tis 13 apr. 2021 kl 10:29 skrev jannick Weiss : >> Hello,my name is Jannick Weiss and i am currently in the process of taking >> my education as a datatechnician. As part of my education i have to do a >> presentation on a self-elected subject and i have chosen to talk about CARP. >> >> It is my understanding that it is you (OpenBSD) that have developed CARP. >> I am having trouble finding information about CARP, such as the different >> states the protocol goes through or how the election of the master node >> works specifically. >> If you can provide any documentation on CARP it would be greatly >> appreciated. > > https://www.openbsd.org/events.html lists a few talks some 15 years > ago which focused on PF and Carp, those might help. https://github.com/jedisct1/UCarp has some useful information. There's no formal documentation for the protocol afaik. > Googling "openbsd carp design" turned this PDF up, > https://core.ac.uk/download/pdf/17210042.pdf from 2006 which perhaps > dives a bit deeper. It's a bit wrong though, I noticed it says "encrypted" - it's authenticated but not encrypted. Doesn't go much into the protocol details either.
Re: Technical Documentation - CARP
Den tis 13 apr. 2021 kl 10:29 skrev jannick Weiss : > Hello,my name is Jannick Weiss and i am currently in the process of taking > my education as a datatechnician. As part of my education i have to do a > presentation on a self-elected subject and i have chosen to talk about CARP. > > It is my understanding that it is you (OpenBSD) that have developed CARP. > I am having trouble finding information about CARP, such as the different > states the protocol goes through or how the election of the master node > works specifically. > If you can provide any documentation on CARP it would be greatly > appreciated. https://www.openbsd.org/events.html lists a few talks some 15 years ago which focused on PF and Carp, those might help. Googling "openbsd carp design" turned this PDF up, https://core.ac.uk/download/pdf/17210042.pdf from 2006 which perhaps dives a bit deeper. -- May the most significant bit of your life be positive.
Technical Documentation - CARP
Hello,my name is Jannick Weiss and i am currently in the process of taking my education as a datatechnician. As part of my education i have to do a presentation on a self-elected subject and i have chosen to talk about CARP. It is my understanding that it is you (OpenBSD) that have developed CARP. I am having trouble finding information about CARP, such as the different states the protocol goes through or how the election of the master node works specifically. If you can provide any documentation on CARP it would be greatly appreciated. In advance, thank you for any help you may provide. Best regards Jannick Weiss
