Users Manual

Chapter 9: Troubleshooting 177
PoP not online from E2E/cnMaetro GUI
This usually means that the PoP node is not able to talk to the E2E controller. Ensure that the PoP node has
the E2E IPv6 configured properly. Also ensure that there is a route between the E2E controller and the PoP
node, if they are not in the same VLAN. Try to ping the E2E from the PoP node (login to ssh).
Link not coming up
1. Ensure that the two ends of the radios can see each other (clear line of sight in between). If the link
is using V3000, ensure that they are properly aligned.
2. Ensure that MAC address of the radios are configured correctly in the E2E Controller.
3. Ensure that GPS sync is not enabled if indoor and ensure that GPS sync is enabled if outdoor.
4. Ensure that both ends of the link has the same software version.
5. Ensure to configure country code on the E2E GUI.
6. Ensure that the two ends of the link use opposite polarity and Golay codes that matches each other.
7. Ensure that the remote ends can reach the E2E Controller – IPv6 configuration (if beamforming is
successful but the remote end cannot reach back to the E2E, the E2E/cnMaestro GUI displays link
status as up but the remote radio is offline).
8. If you already have experience setting up a link and you are trying to setup a daisy chain, ensure
that there is not any interference caused by the existing link. For example, make sure that the two
neighboring link use different Golay code.
Link does not come up after some configuration change
There is a possibility that the remote unit could be in a state that it uses different channel/Golay
code/polarity from the near-end unit. Try to factory default the remote radio if possible.
On the E2E Controller/cnMaestro, it shows that the link is up, but the remote radio is NOT online - This
means that link is established but the remote end radio cannot reply back to the E2E controller. Check the
E2E configuration to make sure that the IPv6 default gateway is configured correctly to allow a route
between the E2E controller and the remote radio.
Link not having expected throughput performance
l Check the radio GUI to ensure that the link is running as the expected MCS mode when user data is
passing through.
l Check to ensure that the Ethernet ports of the radios and the testing devices are negotiated to
expected data rate (10Gbps).
l Ensure that your testing devices are capable of handling the throughput – run data throughput test
by bypassing the radio link.
l Do not use radio internal iperf tool to test throughput.