User's Manual

Table Of Contents
8 Web Page Reference
130
The following system alarms are defined:
Ethernet Link Status: Current status of the Ethernet link. If there are any problems with the
Ethernet interface, this alarm will be asserted. This alarm will most likely be seen if the unit
has no Ethernet cable plugged into its Ethernet socket. Note that a change of state may
generate an SNMP trap and/or SMTP email alert.
Telecoms Channel Status (see section 8.3.4.3 “Telecoms Interface” for a description of the
Tele
coms Interface): Indicates an alarm condition on a telecoms channel. Alarms include:
"No Signal (Local)": there is no telecoms signal present at the connection to the ODU at
the local end.
"No Signal (Remote)": indicates that an absence of telecoms data across the wireless
link.
"No Signal (Local and Remote)": both alarms occur at the same time.
"Remote Timing": there is insufficient wireless capacity available to carry telecoms data.
Under these conditions telecoms timing information is still sent to keep the telecoms
clocks synchronized.
"No Signal (Local) and Remote Timing", indicates both no local signal and remote timing.
In remote timing mode the ODU will transmit an Alarm Indication Signal (AIS), consisting of
all-ones, from the associated telecoms interface. A change of state may generate an SNMP
trap and/or SMTP email alert.
Telecoms Interface A Loopback (see section 8.3.4.3 for a description of the Telecoms
Interf
ace): The loopback status of telecoms channel A. This is intended for installation testing
and should be set to 'None' for normal operation. The wire connections to a unit can be tested
by applying a 'Copper' loopback to the local unit. The wireless connection to the remote unit
can be tested by applying a 'Wireless' loopback to the remote unit with no loopback on the
local unit. Note that a change of state may generate an SNMP trap and/or SMTP email alert.
The loopback can be disabled from the telecoms configuration sub menu (see Section
8.3.1.6).