Install Instructions
Table Of Contents
- About This Manual
- Important Notice
- Introduction
- Document structure
- Document marks
- Key Features
- Hardware Platform
- Power supply
- Lightning protection unit
- Synchronization unit
- // 0) { /* For each inline-commented element clear data-ref and class */ for (var i=0; i < commentedElements.length; i++) { commentedElements[i].dataset.ref= ""; commentedElements[i].className = ""; } } /* Else do nothing */ } }); //]> AUX-ODU-SYNC Mounting
- AUX-ODU-SYNC Cable gland Assembling
- AUX-ODU-SYNC Connection to ODU
- Packing List
- Planning considerations
- Link Pre-configuration in the lab
- Installation
- Operation & Administration
- Troubleshooting
- Glossary
Infinet Wireless: Technical Documentation – InfiMAN Evolution
53 https://wiki.infinetwireless.com/display/DR/General+Purpose+Command+Set#GeneralPurposeCommandSet-system
54 https://wiki.infinetwireless.com/display/DR/General+Purpose+Command+Set#GeneralPurposeCommandSet-mem
55 https://wiki.infinetwireless.com/display/DR/General+Purpose+Command+Set#GeneralPurposeCommandSet-system
56 https://wiki.infinetwireless.com/display/DR/General+Purpose+Command+Set#GeneralPurposeCommandSet-system
57 https://wiki.infinetwireless.com/display/DR/General+Purpose+Command+Set#GeneralPurposeCommandSet-config
Troubleshooting – 153
•
•
•
•
•
•
•
•
105 Figure - Statistics graphs
8.4.4 Device status
Pay attention to the CPU and memory usage indicators in the"Device status(see page 64)" section. Excessive
processes running on a device can overflow the volatile memory and overload the CPU (over 95% usage), leading to
a deterioration in the wireless link's quality.The CPU load can be displayed using the"system cpu
53
"commandand
information about the device's memory state can be shown using the"mem
54
"command.
106 Figure - CPU and memory usage
8.4.5 Last reboot reason
Disruptions in the wireless link may be caused by the reboot of the device. In the "Maintenance(see page 129)" section
or in the"system uptime
55
" command outputpay attention to the last device reboot reason. The following values
are possible:
"Software fault".
"Unexpected restart".
"Manual restart".
"Manual delayed restart".
"Firmware upgrade".
"SNMP managed restart".
"Test firmware loaded".
"Power-on reset".
8.4.6 System log
Proceed to the System Log tool in the "Device status" section or by using the"system log
56
"command. Using the
log entries, check if the link degradation was caused by a configuration change ("system reconfiguration"
message).Restore the previous version of the configuration if necessary.Detailed information about saving and
uploading the configuration is available in the"General Purpose Command Set
57
" article.
107 Figure - System log