
LBI-38962
38
Problem
Corrective Actions
Telnet or FTP are not accepted
1. Verify that host has the correct IP Address of the EDG CAP
External Address.
2. Verify that the Host and EDG can reach each other by using
"ping" or equivalent.
3. Verify both the EDG's and host's network connections.
4. Verify that both the EDG and host are operational.
5. Verify that the Max Telnet or FTP sessions is greater than 0
on the EDG.
Login not accepted.
1. Verify spelling and case of login name and password.
2. Verify that login name is still valid in /etc/passwd.
Radio fails to receive an Individual
Data Call
1. Verify that radio is on, in range, and logged into the site.
2. Verify that radio is programmed correctly.
3. Check mic. Some radios display 'nd' or 'no data' when mic is
connected or when it is off the hook, preventing data calls.
4. Verify that the LID is registered in the System Manager.
5. Verify that the EDG successfully started up.
6. Verify that the DIM Link hasn't failed.
7. Check for other errors in EDG activity log or site reports
and correct problem.
Radio fails to receive a Group Data
Call
1. Verify that the data group has been programmed into the
radio (using the RDI interface).
2. Verify that the group is either forced at the site or that at
least one radio has logged in with the same voice group.
3. Check mic. Some radios display 'nd' or 'no data' when mic is
connected or when it is off the hook, preventing data calls.
4. Verify that the radio supports Group Data Calls.
5. See Individual Call Problems.
Radio receives data call, but
message doesn't reach RDT.
1. Check the cabling on the radio, RDI and RDT.
2. Verify that RDT is on and executing the correct application
software.
3. Cycle power on the radio and RDT.
4. EDACS Network Driver is installed on RDT, but radio LID
or GID is not defined as a network layer RDT in
SYSTEM.TXT.
2. TSI_ANTI_BIASING command in SYSTEM.TXT is set to
TRUE, but RDI is not set up to use BREN.
Excessive Error Rate
1. Verify that the radio is in range and isn't being interfered
with.
2. Verify that the SYSTEM.TXT Msg_Timeout value is long
enough.
3. Verify that the SYSTEM.TXT Max_Msgs value is set high
enough.
4. Verify that the SYSTEM.TXT Outbound_Msg_Delay value
is large enough.
5. Verify that the TSI Board isn't running out of memory.