From ArubaOS 3.4.x and later, AP-124/AP-125 can be configured as mesh nodes.
Prior to ArubaOS 3.4, if the AP12x APs are provisioned as mesh nodes, they can (not necessarily though) generate errors log like the event shown here. The AP-12x may keep rebooting at 3 minute intervals.
Jul 21 18:48:51 <meshd 399803> <ERRS> |AP 00:1a:1e:c0:fa:email@example.com meshd| An internal system error has occurred at file meshd_cfg.c function meshd_binary_wif_sysctl line 1119 error Error opening </proc/sys/dev/wifi0/mesh_cmn_struct> : No such file or directory.
Jul 21 18:49:01 <nanny 303073> <ERRS> |AP 00:1a:1e:c0:fa:firstname.lastname@example.org nanny| Process /aruba/bin/meshd [pid 234] died: got signal SIGSEGV
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.