DAS TYCO Troubleshooting
DAS TYCO Troubleshooting
DAS TYCO Troubleshooting
Overview
Unison SNMP monitoring is supported by the use of an external device called a Network Interface Unit or NIU.
The NIU is industrial PC running a custom software application that converts the proprietary Unison serial protocol
into SNMP.
The NIU also acts as a data concentrator allowing from 1-12 Unison MHs to share one NIU.
The Unison DAS product has a broad range of alarms that covers almost every facet of the DAS from RAUs and
antennas to the MH.
The system supports a three level alarm hierarchy of, Errors (Faults), Warnings and Status.
Trap Types
The NIU can generate 10 different traps. Some are related to the NIU itself and the remaining are related to
Unison or the FlexWave Focus (MetroReach) product that is attached to the NIU.
• niuContactSenseTrap
• niuImAliveTrap
• niuNewTimeTagLog
• niuSerialLinkBlocked
• niuSerialLinkBlockCleared
• niuSerialLinkDown
• niuSerialLinkUp
• niuStatusChange
• niuSystemTrap
• niuTestTrap
niuContactSenseTrap
The niuContactSenseTrap supports the 21 dry contacts the NIU can monitor. The contacts can be
Open,Closed or Disabled.
niuImAliveTrap
The niuImAliveTrap is the NIU heartbeat. It is usually used to indicate the NIU is operational and is
communicating.
niuNewTimeTagTrap
The niuNewTimeTagTrap is used to indicate a Unison MH or FlexWave Focus link has generated a Time
Tagged Log entry in relation to a change of state. This trap is not normally used.
niuSerialLinkBlocked
The NIU generates this trap when a serial port is blocked due to a serial pass-through. When the serial pass-
though is active on a port the NIU cannot monitor the port for changes in state.
niuSerialLinkBlockCleared
The NIU generates this trap when the serial pass-through is dropped on a serial port. This indicates the NIU
can resume monitoring of the port.
niuSystemTrap
This trap contains any system information such as finishing a System Test. Not used at this time.
niuTestTrap
The NIU generates this trap in response to the setting of the niuSecondsToSendTestTrap OID. It is
primarily used to test whether the NIU is configured properly and that connectivity is working between the
NIU and the NMS.
niuStatusChange
The NIU generates this trap when it detects a status change in any connected Unison or FlexWave Focus
devices.
Alarm Types
The niuStatusChange trap supports the following Unison alarms.
Error (Fault)
An Error is a service affecting alarm. RF coverage is impacted at one or more antennas. Errors are usually the result
of disconnects, loss of AC power, internal H/W failure. The faceplate LEDs turn red when an Error is detected in the
system. Warning and Status alarms have no visible indicators.
Warning
A Warning maybe service affecting. RF service is impacted, but, not to the point where RF is lost. Possible warnings
are; high fiber optical loss, fan failure, DL overdrive, etc.
Status
Status alarms are considered informational. System Test required is a typical Status alarm.
SNMP Monitoring
The primary SNMP trap that covers the above three alarm levels is defined in the NIU MIB as the
niuStatusChangeTrap. Below is the configuration the niuStatusChangeTrap.
Name: niuStatusChange
Type: NOTIFICATION-TYPE
OID: 1.3.6.1.4.1.12882.1.100.0.1
Full path:
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).lgc(12882).lgcNetworkInterfaceUnit(
1).niuEvents(100).niuTraps(0).niuStatusChange(1)
Module: LGC-NIU-MIB
Parent: niuTraps
Next sibling: niuSerialLinkDown
Status: current
Objects: 1: niuTrapId
• okay(79)
• error(70)
• userLockout(76)
• errorLockout(88)
• warning(87)
• notManuTested(77)
• infoAvailable(85)
• notConnected(78)
• disconnected(68)
• contactOpen(58)
• contactClosed(93)
Several of the states are related to factory testing and should never appear in the field and can be ignored. These
states are:
• frozen(90)
• notManuTested(77)
The remaining states can be grouped into Error, Warning, Status and Ok. The following states are considered Errors:
• error(70)
• userLockout(76)
• errorLockout(88)
• userLockout(76)
• disconnected(68)
The following states are considered Ok and are used to clear any previous alarm state a device was in:
• notConnected(78)
• okay(79)
The following states are considered special in that they relate to external devices to the Unison DAS and are usually
considered a warning.
• contactOpen(58)
• contactClosed(93)
Errors
Main Hub
Message # Description
{MF01} Software error occurred and recovered; If this happens repeatedly, replace the MH
{MF02} Software error occurred and recovered; If this happens repeatedly, replace the MH
{MF03} Software error occurred and recovered; If this happens repeatedly, replace the MH
{MF04} Software reset occurred and recovered; If this happens repeatedly, replace the MH
{MF05} Software error occurred and recovered; If this happens repeatedly, replace the MH
{MF06} MH power cycle; If AC mains not cycled, replace the MH
{MF07} Invalid fault code; Send logs to LGC for review
{MF09} Temperature is high; Replace the MH if fan failure. Check fan for rotation, air flow blockage, and dust. Check
room environmental controls
{MF10} System Error Lockout; Check MH faults, system is out-of-service due to MH internal fault
{MF11} Commanded Out-of-Service; Command In-service to restore operation
{MF13} Hardware failure (Power Supply); Replace the MH
{MF14} Hardware failure (DL Laser); Replace the MH
{MF15} Failed to perform system test (PLL unlock); Unable to perform system end-to-end test. Replace the MH when
possible
{MF16} Fan failure; Check fan for rotation, air flow blockage, and dust. Replace the MH on temperature warning
{MF17} Hardware failure (SPI); Cycle power once. If fault persists, replace the MH
{MF18 }Hardware failure (DL PLL Unlock); Cycle power once. If fault persists, replace the MH
{MF19} Hardware failure (DL PLL Unlock); Cycle power once. If fault persists, replace the MH
{MF20} Hardware failure (DL Pilot PLL Unlock); Cycle power once. If fault persists, replace the MH
{MF21} Hardware failure (UL PLL Unlock); Cycle power once. If fault persists, replace the MH
{MF22} Hardware failure (UL PLL Unlock); Cycle power once. If fault persists, replace the MH
{MF23} Hardware failure (UL PLL Unlock); Cycle power once. If fault persists, replace the MH
{MF24} Frequency band not programmed; Use AdminManager to program the frequency band
{MF25} Hardware failure (DL pilot too low); Cycle power once. If fault persists, replace the MH
{MF26} Hardware failure (DL pilot too high); Cycle power once. If fault persists, replace the MH
{MF27} Failed to perform system test (Test tone too high); Unable to perform system end-to-end test. Replace the MH
when possible
{MF28} Failed to perform system test (Test tone too low); Unable to perform system end-to-end test. Replace the MH when
possible
{MF29} Hardware failure (DL Path); Replace the MH
{MF30} Hardware failure (UL Path); Re-run system test. Swap first two EHs and re-run system test. If fault persists, replace
the MH when possible
Expansion Hub
Message # Description
{EF01} Software error occurred and recovered; If this happens repeatedly, replace the EH
Main Hub
Message # Description
<MW01> DL signal from RF source is excessive; Reduce DL signal from RF source (base station or bi-directional amplifier)
<MW02> Temperature is high; Replace the MH if fan failure. Check fan for rotation, air flow blockage, and dust. Check
room environmental controls
[MS03] Downlink laser is failing; Replace the MH when possible
[MS04] Fan failure; Check fan for rotation, air flow blockage, and dust. Replace the MH on high temperature warning
[MS05] Commanded Out-of-Service; Command In-service to restore operation
[MS06] Factory special test mode; Cycle power to clear test mode
[MS07] System Lockout; Check MH for faults
[MS08] Unable to perform system test on power up; Check EHs and RAUs for faults. Re-run system test
[MS09] EH 1/RAUs report warning condition; Check EH 1 and RAUs for warnings
[MS10] EH 2/RAUs report warning condition; Check EH 2 and RAUs for warnings
[MS11] EH 3/RAUs report warning condition; Check EH 3 and RAUs for warnings
[MS12] EH 4/RAUs report warning condition; Check EH 4 and RAUs for warnings
[MS13] Port 1 UL fiber interface has high optical loss; Clean fiber cable connectors and ports
[MS14] Port 2 UL fiber interface has high optical loss; Clean fiber cable connectors and ports
[MS15] Port 3 UL fiber interface has high optical loss; Clean fiber cable connectors and ports
[MS16] Port 4 UL fiber interface has high optical loss; Clean fiber cable connectors and ports
[MS17] Failed to perform system test (PLL unlock); Unable to perform system end-to-end test, replace the MH when
possible
[MS18] Failed to perform system test (Test tone too high); Unable to perform system end-to-end test, replace the MH when
possible
[MS19] Failed to perform system test (Test tone too low); Unable to perform system end-to-end test, replace the MH when
possible
<MW20> Hardware failure (DL Path); Replace the MH when possible
Expansion Hub
Message # Description
[ES01] The DL fiber interface has high optical loss; Clean fiber connectors and ports, and check DL cable for excessive
optical loss
[ES02] The DL RF path loss is above the recommended limit; Clean fiber connectors and ports, and check DL cable for
excessive optical loss
[ES03] UL laser is failing; Replace the EH when possible
[ES04] System test required; Run system test
[ES05] Temperature is high; Check fan for rotation, air flow blockage, dust. Check room environmental controls
[ES06] Fan 1 failure; Check fan for rotation, air flow blockage, and dust. Replace the EH on temperature fault
[ES07] Fan 2 failure; Check fan for rotation, air flow blockage, and dust. Replace the EH on temperature fault
[ES08] Fan 3 failure; Check fan for rotation, air flow blockage, and dust. Replace the EH on temperature fault
[ES09] Port 1 UL RF path loss is above the recommended limit; Check CAT-5/6 cable, especially on new install. Check
CAT-5 Extender, if present. Use CAT-5 Extender to improve coverage
[ES10] Port 2 UL RF path loss is above the recommended limit; Check CAT-5/6 cable, especially on new install. Check
CAT-5 Extender, if present. Use CAT-5 Extender to improve coverage
[ES11] Port 3 UL RF path loss is above the recommended limit; Check CAT-5/6 cable, especially on new install. Check
CAT-5 Extender, if present. Use CAT-5 Extender to improve coverage