...
cd /usr/ccsp/EasyMesh
onewifi_em_cli bpi |
Observation in EM-Contrller device side:
- All configured VAPs should be UP and Running
- VAPs should be broadcasting EasyMesh default SSIDs(eg, private_ssid, mesh_backhaul)
- Logs files are generated under /tmp folder
Extender 1 + STAR Topology
1.Please ensure below processes are running in Ext1
| Code Block |
|---|
| language | bash |
|---|
| title | process_status |
|---|
| collapse | true |
|---|
|
root@Filogic-GW:~# systemctl status onewifi
* onewifi.service - Cosa service
Loaded: loaded (8;;file://Filogic-GW/lib/systemd/system/onewifi.service/lib/systemd/system/onewifi.service8;;; enabled; vendor preset: e)
Active: active (running) since Thu 2022-04-28 17:43:15 UTC; 3min 29s ago
TriggeredBy: * filogicwifiinitialized.path
Process: 1781 ExecStartPre=/bin/sh /usr/ccsp/wifi/onewifi_pre_start.sh (code=exited, status=0/SUCCESS)
Process: 2085 ExecStart=/usr/bin/OneWifi -subsys $Subsys (code=exited, status=0/SUCCESS)
Main PID: 2086 (OneWifi)
Tasks: 14 (limit: 4713)
Memory: 38.2M
CGroup: /system.slice/onewifi.service
`- 2086 /usr/bin/OneWifi -subsys eRT.
2022 Apr 28 17:42:48 Filogic-GW systemd[1]: Starting Cosa service...
2022 Apr 28 17:42:53 Filogic-GW UTOPIA[2086]: system.syscfg Shared memory file not found
2022 Apr 28 17:42:53 Filogic-GW UTOPIA[2086]: 2022-04-28 17:42:53., ../../../../git/source/syscfg/lib/syscfg_lib.c:466, Error initializing sy
2022 Apr 28 17:43:15 Filogic-GW systemd[1]: Started Cosa service.
2022 Apr 28 17:44:01 Filogic-GW [OneWifi][2086]: WiFi radio radio1 is set to UP
root@Filogic-GW:~# systemctl status ieee1905_em_agent
* ieee1905_em_agent.service - ieee1905 EasyMesh Remote Agent service
Loaded: loaded (8;;file://Filogic-GW/lib/systemd/system/ieee1905_em_agent.service/lib/systemd/system/ieee1905_em_agent.service8;;; enabl)
Active: active (running) since Thu 2022-04-28 17:43:35 UTC; 3min 16s ago
Process: 3284 ExecStartPre=/bin/sh -c /usr/ccsp/EasyMesh/setup_ext_pre.sh (code=exited, status=0/SUCCESS)
Process: 3303 ExecStartPre=/bin/sh -c if [ ! -e "/sys/class/net/eth1_virt_peer/address" ]; then `/usr/ccsp/EasyMesh/setup_veth_for_em.sh )
Process: 3304 ExecStartPre=/bin/sh -c sleep 5 (code=exited, status=0/SUCCESS)
Process: 3439 ExecStart=/bin/sh -c /usr/bin/ieee1905 -f ieee1905::al_sap=trace,ieee1905::cmdu_handler=trace,ieee1905::cmdu_proxy=trace,ie)
Main PID: 3440 (ieee1905)
Tasks: 7 (limit: 4713)
Memory: 10.5M
CGroup: /system.slice/ieee1905_em_agent.service
`- 3440 /usr/bin/ieee1905 -f ieee1905::al_sap=trace,ieee1905::cmdu_handler=trace,ieee1905::cmdu_proxy=trace,ieee1905::cmdu_obserr
2022 Apr 28 17:43:30 Filogic-GW systemd[1]: Starting ieee1905 EasyMesh Remote Agent service...
2022 Apr 28 17:43:35 Filogic-GW systemd[1]: Started ieee1905 EasyMesh Remote Agent service.
root@Filogic-GW:~# systemctl status em_agent
* em_agent.service - EasyMesh Agent service
Loaded: loaded (8;;file://Filogic-GW/lib/systemd/system/em_agent.service/lib/systemd/system/em_agent.service8;;; enabled; vendor preset:)
Active: active (running) since Thu 2022-04-28 17:44:00 UTC; 2min 57s ago
Process: 3283 ExecStartPre=/bin/sh -c sleep 30 (code=exited, status=0/SUCCESS)
Process: 3621 ExecStartPre=/bin/sh -c /usr/ccsp/EasyMesh/setup_ext_pre.sh (code=exited, status=0/SUCCESS)
Process: 3640 ExecStart=/bin/sh -c /usr/bin/onewifi_em_agent >> /tmp/em_agent.log & (code=exited, status=0/SUCCESS)
Main PID: 3641 (onewifi_em_agen)
Tasks: 9 (limit: 4713)
Memory: 10.8M
CGroup: /system.slice/em_agent.service
`- 3641 /usr/bin/onewifi_em_agent |
2.Ensure mesh backhaul connectivity is established over 5G through wifi1.1 interface.
3.Verify mesh backhaul connection in EM-Contrller side as well.
iw dev wifi1.1.sta<i> info
iw dev wifi1.1.sta<i> station dump |
4. Wait for few minutes( for Agent to propagate SSID information from Controller to OneWifi in Extender1) and then check
- Check all configured VAPs should be up and running with "iw dev" command
- VAPs should be broadcasting default EasyMesh SSIDS (ie private_ssid, mesh_backhaul)
- logs files are generated under /tmp folder
5. Test the connectivity to EM-Controller through backhaul
Sample logs
EM-Controller and EM-Agent success logs
...
