Comtech EF Data CME-5000 Manual - Manual (Page 88)

Digicast Micro Encapsulator (MENCAP) Revision A
Troubleshooting MN/MENCAPEDC.IOM
Ensure the MENCAP 50 and the PC are set with unique IP addresses that are in
the same subnet.
If the MENCAP 50 and the PC are not in the same subnet, then both the
MENCAP 50 and PC must have a valid “Default Gateway” defined so that non-
local traffic will be redirected to this device for routing the IP messages between
the two devices.
SYMPTOM: MENCAP 50 will not synchronize with a modem
The MENCAP 50 may be connected directly from an ASI Output port to an ASI
Input port on a modem. If the modem will not lock, the most likely cause is the
data rate on the MENCAP 50 or modem are not set correctly.
Another cause is the formatting of the MPEG packets – make sure that both are
set to either 188-byte mode (standard) or 204-byte mode.
Always ensure the cable type between the MENCAP 50 and the modem is RG59
75Ω cable.
SYMPTOM: MENCAP 50 reports dropped packets
The most likely cause of this problem is the incoming data on a route or all routes
exceeds the configured egress bandwidth.
To remedy the problem:
• Look at the route statistics for the MENCAP 50 and identify the routes
with dropped packets.
• Lower the rate of the incoming data or increase the maximum bandwidth
assigned to the route if QoS is set.
SYMPTOM: MENCAP 50 has a RED Alarm displayed
The most likely cause of the Alarm LED is the maximum bandwidth has been
exceeded. Please refer to the previous item to troubleshoot this problem.
D–2