Aviat Networks ECLIPSE EDGE, Руководство пользователя

Страница: 178 / 274

16 Aviat Networks
Chapter 5. Eclipse Edge Commissioning and Troubleshooting
• A laptop PC loaded with Portal, an Ethernet connection cable, and an IP address
list for the radios in the Eclipse network.
• If login security has been enabled, you will need the 'engineer' password for the
local and remote sites to be accessed.
• Any special test equipment that may be needed, such as a BER tester.
• Toolkit.
• Key(s) for access to the site.
NOTE:
For more information, refer to Aviat Networks Best Practices Guide,
Chapter 9, Troubleshooting.
Edge Troubleshooting Basics
This section provides general guidance on Eclipse Edge troubleshooting:
• Check front-panel LED indications . These provide summary alarm indications,
which can help narrow down the location and type of failure. Refer to
Edge IDUspe
LEDs on page 19
.
• Check System Summary screen . When logging into Eclipse with Portal, the
opening screen is System Summary. Use the information provided to check the alarm
location, its severity, and problem type:
• Mouse-over problem icons for a description of the problem type.
• Double clicking a module takes you to the relevant Portal Alarms screen. Refer to
Portal Alarms for Edge on page 21
. Use these alarms with the information
provided on probable cause and recommended actions, to help determine the real
cause of a failure and the action to take.
• Check the basics first .
• For example, if multiple alarms are present, and these include power supply
voltage or hardware alarms, always check their cause before looking at resultant
down-stream path failure or path warning alarms.
• Similarly, if a path-related failure is indicated (no hardware or software alarms),
investigate the path. Go to the Portal History screen (15 minute view), and the
Events screen to check supporting data, such as low RSL and incidence of
intermittent pre-failure BER alarms, which if present are evidence of a
path-related failure. Refer to
Troubleshooting Edge Path Problems on
page 17
for more information.
• Check if symptoms match the alarm . Alarms reflect the alarm state, but in
exceptional circumstances an alarm may be raised because of a failure to
communicate correctly with the alarm source, or a failure in alarm management
processing. Always check to see if symptoms match the alarm, using LED indications
and Portal Diagnostics.
• Check if recent work may be a cause . Recent work at the site may be a cause or
contributing factor. Check for a configuration change, software upgrade, power
recycling (reboot), or other site work: