{"id":2027,"date":"2023-06-26T22:23:54","date_gmt":"2023-06-26T20:23:54","guid":{"rendered":"https:\/\/labovilleurbanne.fr\/blog\/?p=2027"},"modified":"2023-06-26T22:35:17","modified_gmt":"2023-06-26T20:35:17","slug":"analyse-switch-ubiquiti-us-8-150w","status":"publish","type":"post","link":"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/","title":{"rendered":"Analyse switch ubiquiti us-8-150w"},"content":{"rendered":"\n

J’ai r\u00e9cup\u00e9r\u00e9 un switch Ubiquiti US-8-150W. Malheureusement, il ne fonctionne plus.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Nous avons test\u00e9 la r\u00e9initialisation d’usine sans que les ports Ethernet ne soient affect\u00e9s.<\/p>\n\n\n\n\n\n\n\n

Nous avons ouvert le bo\u00eetier et avons d\u00e9couvert un port s\u00e9rie.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Nous avons connect\u00e9 le port s\u00e9rie du Raspberry Pi aux broches GPIO14\/GPIO15 (lecture\/transmission). Nous avons configur\u00e9 le port \u00e0 une vitesse de 115200 bauds, une parit\u00e9 de 1, 8 bits de donn\u00e9es et aucun contr\u00f4le de flux.<\/p>\n\n\n\n

Le port GPIO14 du Raspberry Pi est \u00e9galement connu sous le nom de DART (Direct Asynchronous Receiver\/Transmitter), ou UART (Universal Asynchronous Receiver\/Transmitter). Il est utilis\u00e9 pour la communication s\u00e9rie asynchrone avec d’autres p\u00e9riph\u00e9riques, tels que des capteurs, des modules radio ou d’autres microcontr\u00f4leurs.<\/p>\n\n\n\n

Le port GPIO14\/DART dispose de deux lignes : une ligne de lecture (RX) pour recevoir les donn\u00e9es entrantes et une ligne de transmission (TX) pour envoyer les donn\u00e9es sortantes. Il utilise un protocole de communication asynchrone, ce qui signifie qu’il n’y a pas de signal d’horloge synchronis\u00e9 entre l’\u00e9metteur et le r\u00e9cepteur.<\/p>\n\n\n\n

La configuration typique du port GPIO14\/DART comprend une vitesse de transmission, exprim\u00e9e en bauds (bits par seconde), une parit\u00e9 (optionnelle pour v\u00e9rifier l’int\u00e9grit\u00e9 des donn\u00e9es) et le nombre de bits de donn\u00e9es (g\u00e9n\u00e9ralement 8 bits). Le contr\u00f4le de flux (flow control) peut \u00eatre d\u00e9fini sur \u00ab\u00a0none\u00a0\u00bb (aucun contr\u00f4le de flux) pour une communication simple entre le Raspberry Pi et le p\u00e9riph\u00e9rique connect\u00e9.<\/p>\n\n\n\n

En r\u00e9sum\u00e9, le port GPIO14\/DART du Raspberry Pi est utilis\u00e9 pour \u00e9tablir une communication s\u00e9rie asynchrone avec d’autres dispositifs, en utilisant des param\u00e8tres tels que la vitesse, la parit\u00e9, le nombre de bits de donn\u00e9es et le contr\u00f4le de flux appropri\u00e9s.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Pour d\u00e9sactiver le Bluetooth, vous pouvez ex\u00e9cuter la commande suivante dans le terminal du Raspberry Pi:<\/p>\n\n\n\n

sudo systemctl disable bluetooth<\/code><\/p>\n\n\n\n

Cela emp\u00eachera le Bluetooth de d\u00e9marrer automatiquement au prochain red\u00e9marrage.<\/p>\n\n\n\n

En ce qui concerne l’activation du port DART (GPIO14), vous devrez modifier le fichier de configuration du Raspberry Pi. Suivez les \u00e9tapes ci-dessous :<\/p>\n\n\n\n

    \n
  1. Ouvrez le fichier de configuration en utilisant la commande suivante :<\/li>\n<\/ol>\n\n\n\n

    sudo nano \/boot\/config.txt<\/code><\/p>\n\n\n\n

      \n
    1. Recherchez la ligne qui commence par # Enable UART et enlevez le \u00ab\u00a0#\u00a0\u00bb pour la d\u00e9commenter.<\/li>\n\n\n\n
    2. Pour activer le port DART (GPIO14), ajoutez la ligne suivante apr\u00e8s avoir d\u00e9comment\u00e9 la ligne pr\u00e9c\u00e9dente :<\/li>\n<\/ol>\n\n\n\n

      enable_uart=1<\/code><\/p>\n\n\n\n

        \n
      1. Enregistrez les modifications en utilisant la combinaison de touches Ctrl+X, puis en appuyant sur Y pour confirmer, et enfin sur Entr\u00e9e pour sauvegarder le fichier.<\/li>\n\n\n\n
      2. Red\u00e9marrez le Raspberry Pi pour que les modifications prennent effet :<\/li>\n<\/ol>\n\n\n\n

        sudo reboot<\/code><\/p>\n\n\n\n

        Apr\u00e8s avoir suivi ces \u00e9tapes, le port DART (GPIO14) sera activ\u00e9 et pr\u00eat \u00e0 \u00eatre utilis\u00e9 pour la communication s\u00e9rie asynchrone. Veuillez noter que la d\u00e9sactivation du Bluetooth et l’activation du port DART peuvent varier l\u00e9g\u00e8rement en fonction de la version du Raspberry Pi et de l’OS utilis\u00e9s.<\/p>\n\n\n\n

        <\/p>\n\n\n\n

        Installation PICOCOM.<\/p>\n\n\n\n

        installer Picocom sur Raspberry Pi, vous pouvez suivre les \u00e9tapes ci-dessous :<\/p>\n\n\n\n

          \n
        1. Ouvrez le terminal sur votre Raspberry Pi.<\/li>\n\n\n\n
        2. Assurez-vous que votre Raspberry Pi est connect\u00e9 \u00e0 Internet.<\/li>\n\n\n\n
        3. Ex\u00e9cutez la commande suivante pour mettre \u00e0 jour les paquets disponibles :<\/li>\n<\/ol>\n\n\n\n

          sudo apt update<\/code><\/p>\n\n\n\n

            \n
          1. Une fois la mise \u00e0 jour termin\u00e9e, vous pouvez installer Picocom en utilisant la commande suivante :<\/li>\n<\/ol>\n\n\n\n

            apt install picocom<\/code><\/p>\n\n\n\n

              \n
            1. Confirmez l’installation en appuyant sur la touche Y lorsque vous \u00eates invit\u00e9.<\/li>\n\n\n\n
            2. Attendez que l’installation soit termin\u00e9e. Une fois celle-ci termin\u00e9e, Picocom sera install\u00e9 sur votre Raspberry Pi.<\/li>\n<\/ol>\n\n\n\n

              Picocom est maintenant pr\u00eat \u00e0 \u00eatre utilis\u00e9 pour \u00e9tablir une connexion s\u00e9rie avec un p\u00e9riph\u00e9rique via le port DART (GPIO14) que vous avez activ\u00e9 pr\u00e9c\u00e9demment. Vous pouvez ex\u00e9cuter la commande picocom suivie des param\u00e8tres appropri\u00e9s pour acc\u00e9der au p\u00e9riph\u00e9rique s\u00e9rie.<\/p>\n\n\n\n

              Assurez-vous de disposer des privil\u00e8ges suffisants (par exemple, utilisez sudo picocom si n\u00e9cessaire) et de sp\u00e9cifier les bons param\u00e8tres de communication (vitesse, parit\u00e9, etc.) pour \u00e9tablir une connexion correcte avec votre p\u00e9riph\u00e9rique s\u00e9rie.<\/p>\n\n\n\n

              Nous avons ensuite ouvert une connection sur les port picocom -b 115200 \/dev\/ttyS0 vers le switch.<\/p>\n\n\n\n

              Voci la soorie \u00e9cran ou vois un plantage et un reboot.<\/p>\n\n\n\n

              **************\n port 0 is not active!!\n**************\nIn:    serial\nOut:   serial\nErr:   serial\nUnlocking L2 Cache ...Done\narm_clk=400MHz, axi_clk=200MHz, apb_clk=50MHz, arm_periph_clk=200MHz\nDisabling outer cache\nNet:   Board Net Initialization Failed\nNo ethernet found.\nHit any key to stop autoboot:  0 \nubnt_bootsel_init: bootsel magic=a34de82b, bootsel = 1 \nUBNT application initialized \nBoot partition selected = 1 \nLoading Kernel Image @ 1000000, size = 15728640 \nVerifying 'kernel1' parition:OK\n## Booting kernel from Legacy Image at 01000000 ...\n   Image Name:   Ubiquiti 6.2.14.13855\n   Image Type:   ARM Linux Kernel Image (uncompressed)\n   Data Size:    15429120 Bytes = 14.7 MiB\n   Load Address: 00018000\n   Entry Point:  00018000\n   Verifying Checksum ... OK\n   Loading Kernel Image ... OK\nOK\nboot_prep_linux commandline: console=ttyS0,115200 mem=128M@0x0 mem=128M@0x68000000 mtdparts=spi1.0:768k(u-boot),64k(u-boot-env),64k(shmoo),15360k(kernel0),15424k(kernel1),1024k(cfg),64k(EEPROM) ubntbootid=1\n\nStarting kernel ...\n\nDisabling outer cache\n[    0.000000] Booting Linux on physical CPU 0\n[    0.000000] Linux version 3.6.5 (builder@link-owrt1505-builder) (gcc version 4.7.2 (OpenWrt GCC 4.7.2 unknown) ) #2 SMP Fri Apr 8 14:51:44 UTC 2022\n[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c53c7d\n[    0.000000] CPU: PIPT \/ VIPT nonaliasing data cache, VIPT aliasing instruction cache\n[    0.000000] Machine: Broadcom iProc\n[    0.000000] Memory policy: ECC disabled, Data cache writealloc\n[    0.000000] BUG: mapping for 0x18000000 at 0xf0000000 out of vmalloc space\n[    0.000000] BUG: mapping for 0x19000000 at 0xf1000000 out of vmalloc space\n[    0.000000] PERCPU: Embedded 7 pages\/cpu @c1d07000 s6272 r8192 d14208 u32768\n[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 61952\n[    0.000000] Kernel command line: console=ttyS0,115200 mem=128M@0x0 mem=128M@0x68000000 mtdparts=spi1.0:768k(u-boot),64k(u-boot-env),64k(shmoo),15360k(kernel0),15424k(kernel1),1024k(cfg),64k(EEPROM) ubntbootid=1 ubootver=usw-v1.1.4.115-g14af1ee6\n[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)\n[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)\n[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)\n[    0.000000] Memory: 128MB 128MB = 256MB total\n[    0.000000] Memory: 244640k\/244640k available, 17504k reserved, 131072K highmem\n[    0.000000] Virtual kernel memory layout:\n[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)\n[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)\n[    0.000000]     vmalloc : 0xc8800000 - 0xf0000000   ( 632 MB)\n[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)\n[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)\n[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)\n[    0.000000]       .text : 0xc0018000 - 0xc03528b0   (3307 kB)\n[    0.000000]       .init : 0xc0353000 - 0xc0ea5880   (11595 kB)\n[    0.000000]       .data : 0xc0ea6000 - 0xc0ecee00   ( 164 kB)\n[    0.000000]        .bss : 0xc0ecee24 - 0xc0efd454   ( 186 kB)\n[    0.000000] SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1\n[    0.000000] Hierarchical RCU implementation.\n[    0.000000] \tRCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.\n[    0.000000] NR_IRQS:292\n[    0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms\n[    0.010000] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)\n[    0.050000] pid_max: default: 4096 minimum: 301\n[    0.050000] Mount-cache hash table entries: 512\n[    0.050000] CPU: Testing write buffer coherency: ok\n[    0.050000] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000\n[    0.050000] Setting up static identity map for 0x286c38 - 0x286c90\n[    0.050000] L310 cache controller enabled\n[    0.050000] l2x0: 8 ways, CACHE_ID 0x410000c9, AUX_CTRL 0x0a120000, Cache size: 131072 B\n[    0.050000] Brought up 1 CPUs\n[    0.050000] SMP: Total of 1 processors activated (795.44 BogoMIPS).\n[    0.050000] devtmpfs: initialized\n[    0.060000] NET: Registered protocol family 16\n[    0.060000] DMA: preallocated 256 KiB pool for atomic coherent allocations\n[    0.060000] GENPLL[5] mdiv=40 rate=2000000000\n[    0.060000] Sel=1 Ovr=1 Div=48\n[    0.060000] UART clock rate 50000000\n[    0.080000] bio: create slab <bio-0> at 0\n[    0.080000] Bluetooth: Core ver 2.16\n[    0.080000] NET: Registered protocol family 31\n[    0.080000] Bluetooth: HCI device and connection manager initialized\n[    0.080000] Bluetooth: HCI socket layer initialized\n[    0.080000] Bluetooth: L2CAP socket layer initialized\n[    0.080000] Bluetooth: SCO socket layer initialized\n[    0.080000] Switching to clocksource iproc_gtimer\n[    0.090000] NET: Registered protocol family 2\n[    0.090000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)\n[    0.090000] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)\n[    0.090000] TCP: Hash tables configured (established 4096 bind 4096)\n[    0.090000] TCP: reno registered\n[    0.090000] UDP hash table entries: 128 (order: 0, 4096 bytes)\n[    0.090000] UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)\n[    0.090000] NET: Registered protocol family 1\n[   14.850000] pm_init: Initializing Power Management ....\n[   14.850000] iproc gpiochip add GPIOA\n[   14.850000] GPIOA:ioaddr f0000060 \n[   14.850000] GPIOA:intr_ioaddr f0000000 dmu_ioaddr   (null)\n[   15.100000] PCIE0: LINKSTA reg 0xbe val 0x1001\n[   15.100000] reg[0xac]=0x10, reg[0xae]=0x42, reg[0xb0]=0x8000, reg[0xb4]=0x2c10, reg[0xb6]=0x10, reg[0xb8]=0x5c12, reg[0xba]=0x65, reg[0xbe]=0x1001, reg[0xc6]=0x40, reg[0xca]=0x1, reg[0xd0]=0x1f, reg[0xd2]=0x8, reg[0xdc]=0x1, PCIE0 link=0\n[   15.350000] PCIe port 1 in End-Point mode - ignored\n[   15.350000] Registering iproc_pmu_device\n[   15.350000] bounce pool size: 64 pages\n[   15.370000] squashfs: version 4.0 (2009\/01\/31) Phillip Lougher\n[   15.370000] jffs2: version 2.2. (NAND) \u00a9 2001-2006 Red Hat, Inc.\n[   15.370000] msgmni has been set to 221\n[   15.370000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)\n[   15.370000] io scheduler noop registered\n[   15.370000] io scheduler deadline registered (default)\n[   15.370000] io scheduler cfq registered\n[   15.380000] Serial: 8250\/16550 driver, 2 ports, IRQ sharing enabled\n[   15.380000] serial8250.0: ttyS0 at MMIO 0x18000400 (irq = 123) is a 16550A\n[   15.860000] console [ttyS0] enabled\n[   15.860000] serial8250.0: ttyS1 at MMIO 0x18000300 (irq = 123) is a 16550A\n[   15.890000] brd: module loaded\n[   15.900000] loop: module loaded\n[   15.910000] nbd: registered device at major 43\n[   15.930000] tun: Universal TUN\/TAP device driver, 1.6\n[   15.940000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>\n[   15.950000] Bluetooth: HCI UART driver ver 2.2\n[   15.950000] Bluetooth: HCI H4 protocol initialized\n[   15.950000] Bluetooth: HCI BCSP protocol initialized\n[   15.960000] TCP: cubic registered\n[   15.970000] NET: Registered protocol family 10\n[   15.970000] sit: IPv6 over IPv4 tunneling driver\n[   15.980000] NET: Registered protocol family 17\n[   15.990000] Bluetooth: RFCOMM TTY layer initialized\n[   15.990000] Bluetooth: RFCOMM socket layer initialized\n[   16.000000] Bluetooth: RFCOMM ver 1.11\n[   16.000000] Bluetooth: BNEP (Ethernet Emulation) ver 1.3\n[   16.010000] Bluetooth: BNEP filters: protocol multicast\n[   16.010000] Bluetooth: HIDP (Human Interface Emulation) ver 1.2\n[   16.020000] 8021q: 802.1Q VLAN Support v1.8\n[   16.020000] GENPLL[5] mdiv=40 rate=2000000000\n[   16.030000] qspi_iproc qspi_iproc.1: 1-lane output, 3-byte address\n[   16.030000] m25p80 spi1.0: found mx25l25635e, expected m25p80\n[   16.040000] m25p80 spi1.0: mx25l25635e (32768 Kbytes)\n[   16.040000] 7 cmdlinepart partitions found on MTD device spi1.0\n[   16.050000] Creating 7 MTD partitions on \"spi1.0\":\n[   16.050000] 0x000000000000-0x0000000c0000 : \"u-boot\"\n[   16.060000] 0x0000000c0000-0x0000000d0000 : \"u-boot-env\"\n[   16.070000] 0x0000000d0000-0x0000000e0000 : \"shmoo\"\n[   16.080000] 0x0000000e0000-0x000000fe0000 : \"kernel0\"\n[   16.090000] 0x000000fe0000-0x000001ef0000 : \"kernel1\"\n[   16.090000] 0x000001ef0000-0x000001ff0000 : \"cfg\"\n[   16.100000] 0x000001ff0000-0x000002000000 : \"EEPROM\"\n[   16.130000] Freeing init memory: 11592K\n[   16.210000] ubnt_common: module license 'Proprietary' taints kernel.\n[   16.220000] Disabling lock debugging due to kernel taint\n[   16.300000] Data abort at addr=0xc8a10224, fsr=0x1406 ignored.\n[   16.300000] Data abort at addr=0xc8a10224, fsr=0x1406 ignored.\n[   16.320000] gpiodev: reset_timeout=3\n...running \/sbin\/init\ninit started: BusyBox v1.23.2 (2022-04-08 14:46:27 UTC)\ncan't run '\/etc\/rc.d\/rc.platform': No such file or directory\n\nPlease press Enter to activate this console. \n\nUS-8-150W login: ubnt\nPassword: \n\n\nBusyBox v1.23.2 (2022-04-08 14:46:27 UTC) built-in shell (ash)\n\n\n  ___ ___      .__________.__\n |   |   |____ |__\\_  ____\/__|\n |   |   \/    \\|  ||  __) |  |   (c) 2010-2022\n |   |  |   |  \\  ||  \\   |  |   Ubiquiti Inc.\n |______|___|  \/__||__\/   |__|\n            |_\/                  https:\/\/www.ui.com\n\n      Welcome to UniFi US-8-150W!\n\n********************************* NOTICE **********************************\n* By logging in to, accessing, or using any Ubiquiti product, you are     *\n* signifying that you have read our Terms of Service (ToS) and End User   *\n* License Agreement (EULA), understand their terms, and agree to be       *\n* fully bound to them. The use of SSH (Secure Shell) can potentially      *\n* harm Ubiquiti devices and result in lost access to them and their data. *\n* By proceeding, you acknowledge that the use of SSH to modify device(s)  *\n* outside of their normal operational scope, or in any manner             *\n* inconsistent with the ToS or EULA, will permanently and irrevocably     *\n* void any applicable warranty.                                           *\n***************************************************************************\n\nUS-8-150W-US.6.2.14# cd crashd  \ncrashd\n-sh: cd: can't cd to crashd\nUS-8-150W-US.6.2.14# ls\ncfg        crashlogs\nUS-8-150W-US.6.2.14# cd crumount: can't remount rootfs read-only\nThe system is going down NOW!\nSent SIGTERM to all processes\nSent SIGKILL to[   73.640000] Disabling non-boot CPUs ...\n[   73.640000] Restarting system.\n\n\nU-Boot usw-v1.1.4.115-g14af1ee6 (Feb 14 2017 - 18:50:54)\n\nDEV ID= 0000db56\nSKU ID = 0x8343\nDDR type: DDR3\nMEMC 0 DDR speed = 667MHz\nValidate Shmoo parameters stored in flash ..... OK\nPress Ctrl-C to run Shmoo ..... skipped\nRestoring Shmoo parameters from flash ..... done\nRunning simple memory test ..... OK\nDDR Tune Completed\nDRAM:  256 MiB\nWARNING: Caches not enabled\n\n soc_pcie_hw_init : port->reg_base = 0x18012000 , its value = 0x1 \nPCIe port 0 in RC mode\n\n pos is 172\n==>PCIE: LINKSTA reg 0xbe val 0x1001\n\n**************\n port 0 is not active!!\n**************\nIn:    serial\nOut:   serial\nErr:   serial\nUnlocking L2 Cache ...Done\narm_clk=400MHz, axi_clk=200MHz, apb_clk=50MHz, arm_periph_clk=200MHz\nDisabling outer cache\nNet:   Board Net Initialization Failed\nNo ethernet found.\n<\/code><\/pre>\n\n\n\n
              Pour l’instant, nous n’avons pas identifi\u00e9 la source du probl\u00e8me. Nous avons cependant pu envoyer les journaux (logs) au support d’Ubiquiti. L’histoire n’est pas encore termin\u00e9e.<\/p>","protected":false},"excerpt":{"rendered":"
              J’ai r\u00e9cup\u00e9r\u00e9 un switch Ubiquiti US-8-150W. Malheureusement, il ne fonctionne plus. Nous avons test\u00e9 la r\u00e9initialisation d’usine sans que les ports Ethernet ne soient affect\u00e9s.<\/p>","protected":false},"author":14,"featured_media":2029,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[82,67,1],"tags":[74,98],"yoast_head":"\nAnalyse switch ubiquiti us-8-150w - LABORATOIRE OUVERT VILLEURBANNAIS<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Analyse switch ubiquiti us-8-150w - LABORATOIRE OUVERT VILLEURBANNAIS\" \/>\n<meta property=\"og:description\" content=\"J’ai r\u00e9cup\u00e9r\u00e9 un switch Ubiquiti US-8-150W. Malheureusement, il ne fonctionne plus. Nous avons test\u00e9 la r\u00e9initialisation d’usine sans que les ports Ethernet ne soient affect\u00e9s.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/\" \/>\n<meta property=\"og:site_name\" content=\"LABORATOIRE OUVERT VILLEURBANNAIS\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/labolov\" \/>\n<meta property=\"article:published_time\" content=\"2023-06-26T20:23:54+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-06-26T20:35:17+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/labovilleurbanne.fr\/blog\/wp-content\/uploads\/2023\/06\/IMG_7284-scaled.jpeg\" \/>\n\t<meta property=\"og:image:width\" content=\"1920\" \/>\n\t<meta property=\"og:image:height\" content=\"2560\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Nicolas Rineau\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Nicolas Rineau\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":[\"Article\",\"BlogPosting\"],\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/\"},\"author\":{\"name\":\"Nicolas Rineau\",\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/#\/schema\/person\/c31b3bf795c7195791f43df93c06a250\"},\"headline\":\"Analyse switch ubiquiti us-8-150w\",\"datePublished\":\"2023-06-26T20:23:54+00:00\",\"dateModified\":\"2023-06-26T20:35:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/\"},\"wordCount\":758,\"publisher\":{\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/#organization\"},\"keywords\":[\"informatique\",\"raspberry pi\"],\"articleSection\":[\"projet en cours\",\"tuto\",\"uncategorized\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/\",\"url\":\"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/\",\"name\":\"Analyse switch ubiquiti us-8-150w - LABORATOIRE OUVERT VILLEURBANNAIS\",\"isPartOf\":{\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/#website\"},\"datePublished\":\"2023-06-26T20:23:54+00:00\",\"dateModified\":\"2023-06-26T20:35:17+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/labovilleurbanne.fr\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Analyse switch ubiquiti us-8-150w\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/#website\",\"url\":\"https:\/\/labovilleurbanne.fr\/blog\/\",\"name\":\"LABORATOIRE OUVERT VILLEURBANNAIS\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/labovilleurbanne.fr\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/#organization\",\"name\":\"LABORATOIRE OUVERT VILLEURBANNAIS\",\"url\":\"https:\/\/labovilleurbanne.fr\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/labovilleurbanne.fr\/blog\/wp-content\/uploads\/2023\/09\/cropped-logo.png\",\"contentUrl\":\"https:\/\/labovilleurbanne.fr\/blog\/wp-content\/uploads\/2023\/09\/cropped-logo.png\",\"width\":240,\"height\":240,\"caption\":\"LABORATOIRE OUVERT VILLEURBANNAIS\"},\"image\":{\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/labolov\",\"https:\/\/framateam.org\/labolov\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/#\/schema\/person\/c31b3bf795c7195791f43df93c06a250\",\"name\":\"Nicolas Rineau\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/labovilleurbanne.fr\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/aee6f7f17027c91c34936c5e329febbb?s=96&d=monsterid&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/aee6f7f17027c91c34936c5e329febbb?s=96&d=monsterid&r=g\",\"caption\":\"Nicolas Rineau\"},\"url\":\"https:\/\/labovilleurbanne.fr\/blog\/author\/nicolas_rineau\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Analyse switch ubiquiti us-8-150w - LABORATOIRE OUVERT VILLEURBANNAIS","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/","og_locale":"fr_FR","og_type":"article","og_title":"Analyse switch ubiquiti us-8-150w - LABORATOIRE OUVERT VILLEURBANNAIS","og_description":"J’ai r\u00e9cup\u00e9r\u00e9 un switch Ubiquiti US-8-150W. Malheureusement, il ne fonctionne plus. Nous avons test\u00e9 la r\u00e9initialisation d’usine sans que les ports Ethernet ne soient affect\u00e9s.","og_url":"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/","og_site_name":"LABORATOIRE OUVERT VILLEURBANNAIS","article_publisher":"https:\/\/www.facebook.com\/labolov","article_published_time":"2023-06-26T20:23:54+00:00","article_modified_time":"2023-06-26T20:35:17+00:00","og_image":[{"width":1920,"height":2560,"url":"https:\/\/labovilleurbanne.fr\/blog\/wp-content\/uploads\/2023\/06\/IMG_7284-scaled.jpeg","type":"image\/jpeg"}],"author":"Nicolas Rineau","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"Nicolas Rineau","Dur\u00e9e de lecture estim\u00e9e":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Article","BlogPosting"],"@id":"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/#article","isPartOf":{"@id":"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/"},"author":{"name":"Nicolas Rineau","@id":"https:\/\/labovilleurbanne.fr\/blog\/#\/schema\/person\/c31b3bf795c7195791f43df93c06a250"},"headline":"Analyse switch ubiquiti us-8-150w","datePublished":"2023-06-26T20:23:54+00:00","dateModified":"2023-06-26T20:35:17+00:00","mainEntityOfPage":{"@id":"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/"},"wordCount":758,"publisher":{"@id":"https:\/\/labovilleurbanne.fr\/blog\/#organization"},"keywords":["informatique","raspberry pi"],"articleSection":["projet en cours","tuto","uncategorized"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/","url":"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/","name":"Analyse switch ubiquiti us-8-150w - LABORATOIRE OUVERT VILLEURBANNAIS","isPartOf":{"@id":"https:\/\/labovilleurbanne.fr\/blog\/#website"},"datePublished":"2023-06-26T20:23:54+00:00","dateModified":"2023-06-26T20:35:17+00:00","breadcrumb":{"@id":"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/labovilleurbanne.fr\/blog\/2023\/06\/26\/analyse-switch-ubiquiti-us-8-150w\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/labovilleurbanne.fr\/blog\/"},{"@type":"ListItem","position":2,"name":"Analyse switch ubiquiti us-8-150w"}]},{"@type":"WebSite","@id":"https:\/\/labovilleurbanne.fr\/blog\/#website","url":"https:\/\/labovilleurbanne.fr\/blog\/","name":"LABORATOIRE OUVERT VILLEURBANNAIS","description":"","publisher":{"@id":"https:\/\/labovilleurbanne.fr\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/labovilleurbanne.fr\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/labovilleurbanne.fr\/blog\/#organization","name":"LABORATOIRE OUVERT VILLEURBANNAIS","url":"https:\/\/labovilleurbanne.fr\/blog\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/labovilleurbanne.fr\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/labovilleurbanne.fr\/blog\/wp-content\/uploads\/2023\/09\/cropped-logo.png","contentUrl":"https:\/\/labovilleurbanne.fr\/blog\/wp-content\/uploads\/2023\/09\/cropped-logo.png","width":240,"height":240,"caption":"LABORATOIRE OUVERT VILLEURBANNAIS"},"image":{"@id":"https:\/\/labovilleurbanne.fr\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/labolov","https:\/\/framateam.org\/labolov"]},{"@type":"Person","@id":"https:\/\/labovilleurbanne.fr\/blog\/#\/schema\/person\/c31b3bf795c7195791f43df93c06a250","name":"Nicolas Rineau","image":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/labovilleurbanne.fr\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/aee6f7f17027c91c34936c5e329febbb?s=96&d=monsterid&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/aee6f7f17027c91c34936c5e329febbb?s=96&d=monsterid&r=g","caption":"Nicolas Rineau"},"url":"https:\/\/labovilleurbanne.fr\/blog\/author\/nicolas_rineau\/"}]}},"_links":{"self":[{"href":"https:\/\/labovilleurbanne.fr\/blog\/wp-json\/wp\/v2\/posts\/2027"}],"collection":[{"href":"https:\/\/labovilleurbanne.fr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/labovilleurbanne.fr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/labovilleurbanne.fr\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/labovilleurbanne.fr\/blog\/wp-json\/wp\/v2\/comments?post=2027"}],"version-history":[{"count":3,"href":"https:\/\/labovilleurbanne.fr\/blog\/wp-json\/wp\/v2\/posts\/2027\/revisions"}],"predecessor-version":[{"id":2035,"href":"https:\/\/labovilleurbanne.fr\/blog\/wp-json\/wp\/v2\/posts\/2027\/revisions\/2035"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/labovilleurbanne.fr\/blog\/wp-json\/wp\/v2\/media\/2029"}],"wp:attachment":[{"href":"https:\/\/labovilleurbanne.fr\/blog\/wp-json\/wp\/v2\/media?parent=2027"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/labovilleurbanne.fr\/blog\/wp-json\/wp\/v2\/categories?post=2027"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/labovilleurbanne.fr\/blog\/wp-json\/wp\/v2\/tags?post=2027"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}