If the RN is connected but not performing at expected levels, there are several common issues that may apply.
If the RN is not connected to the optimal BN, it may have a weaker link, which will deliver a lower than expected throughput. To verify, follow these steps:
-
Log into TCS.
-
Click Devices on the navigation pane.
-
Make sure via the toggle switch that the table is showing RNs (not BNs).
-
Find the row that corresponds to the RN in question.
-
Verify the RN is connected to its intended BN by checking the Sector column, this will show the hostname of the BN to which the RN is connected.
The service level agreement (SLA) of the RN directly affects its throughput. To verify, follow these steps:
-
Log into TCS.
-
Click Devices on the navigation pane.
-
Make sure via the toggle switch that the table is showing RNs (not BNs).
-
Find the row that corresponds to the RN in question.
-
Click the serial number of the RN to open the RN’s individual device page.
-
Check the SLA Profile on the Information card. The SLA may be modified by clicking the Edit icon.
For more information on setting the SLA for the RN, refer to the Setting the RN SLA section.
If the RN is connected but customer (residential) equipment is not connecting (router, Wi-Fi access point, etc.), the device connected directly to the Ethernet port of the RN’s PoE injector may not support gigabit Ethernet. The Ethernet port of the RN is full-duplex gigabit-only and does not support negotiating to a slower link speed (100BaseTX, etc.). To verify, follow these steps:
-
Log into TCS.
-
Click Devices on the navigation pane.
-
Make sure via the toggle switch that the table is showing RNs (not BNs).
-
Find the row that corresponds to the RN in question.
-
Click the serial number of the RN to open the individual device page.
-
Check the Errors row in the Interface Statistics card.
An RN can reboot for a number of reasons. To verify, follow these steps:
Comments
Article is closed for comments.