Operation and Maintenance Manual
MultiHaul™ Installation, Operation and Maintenance Manual
Page 88
You can ping it or connect to the BU and see that the TU is connected.
You should also check on the BU that the YU is connected (show remote-terminal-unit).
If TU is not connected, then obviously no service.
2. If no internet, check that the customer is physically connected to the TU (check the
active alarms to see that the port is up and connected).
3. Check the log file for disconnection events. This might also explain slow internet
connection (and often disconnections).
The BU log (and the TU log) records all disconnect events and active alarms.
Here is an example of disconnection in the log of the TU:
TU>show log
Apr 24 13:46:07 cad: link down eth eth-bu1
Apr 24 13:50:50 cad: link up eth eth-bu1
4. You can monitor the throughput (Tx and Rx, in Mbps) on the BU and TU to see if
there is an issue.
TU>show terminal-unit
terminal-unit self-mac : 00:24:a4:07:47:14
terminal-unit ssid : MultiHaul
terminal-unit password : MultiHaul
terminal-unit connection-mode : auto-connect
terminal-unit status : connected
terminal-unit frequency : channel-2
terminal-unit base-unit mac : 00:24:a4:07:48:74
terminal-unit tx-mcs : 7
terminal-unit signal-quality : 30
terminal-unit tx-throughput : 0
terminal-unit rx-throughput : 0
terminal-unit tx-rate-limiter : 100
5. You can monitor the Tx-MCS (modulation) and Signal quality. Typically, should be 8
and min 35, respectively.
6. If issues persist and require an in-depth investigation, you can schedule a
maintenance window and run iperf test from the TU to the BU to confirm performance.