Model: MTS200 (1U)
Doc. Ref. no. : m08/om/201
Issue no. : 03
User’s Manual
Page 190 of 195
Page 190 of 195
1) IP address of GPS ethernet port and telnet device should be same network domain.
2) Please verify the Ethernet connection between GPS ethernet port and telnet device by
pinging the IP address of GPS ethernet port. If IP address of GPS ethernet port is not
reachable, telnet connection will fail.
3) Provide correct IP address of GPS Ethernet port while trying to establish telnet connection.
Refer manual Appendix E for procedure for telnet connection with GPS Ethernet port.
4) SSH service should be ON/START in MTS200 unit.
5) SSH service should be ON in PC from which telnet session is required with MTS200.
6) Enter correct password of MTS200 when prompted for password filed while starting SSH
session with MTS200. Refer section 13.2 for details.
7) SSH version 1 and 2 and their keys must be supported at PC side from where SSH session
with MTS200 is required.
8) User should accept the MTS200 keys if prompted for in PC console. If PC warns to remove
old keys with that particular IP address, user should remove old keys and then again give
SSH command to have access with MTS200.
17.19 Cannot start Webserver
1) IP address of GPS ethernet port and telnet device should be same network domain.
2) Please verify the Ethernet connection between GPS ethernet port and telnet device by
pinging the IP address of GPS ethernet port. If IP address of GPS ethernet port is not
reachable, telnet connection will fail.
3) Provide correct IP address of GPS Ethernet port while trying to establish telnet connection.
Refer manual Appendix E for procedure for telnet connection with GPS Ethernet port.
4) HTTP or HTTPS service should be ON/START in MTS200 unit.
5) Enter correct password of MTS200 when prompted for password filed while starting
webserver session with MTS200. Refer section 13.4 for details.
6) If HTTP service is ON in MTS200, then user cannot have HTTPS connection for webserver.
Also, If HTTPS service is ON in MTS200, then user cannot have HTTP connection for
webserver
7) User should accept the MTS200 Webserver certificate if prompted for in PC web based
browser for having HTTPS connection.
17.20 Alarms/Notification being not received on remote Syslog Server
1) In MTS200, syslog server IP address should be properly configured in Network settings.
2) At PC server side, syslog service should be ON and should accept packets from MTS200 on
UDP layer.
3) Syslog server should be in same network domain and connected in LAN in which MTS200 is
connected.
17.21 NTP Broadcast / Multicast messages not received at NTP client side
1) If NTP client is a Unix or Linux or Solaris or Red-Hat system, user need to configure ntp.conf
file in unix based system for receiving broadcast/multicast ntp messages and then restart the
ntp service in those systems.
2) If ntp client is configured for ntp authentication, then ntp authentication type should be same
as authentication type configured for broadcast in MTS200.
3) If NTP broadcast is configured with NONE Authentication type in MTS200 and ntp clients are
configured with broadcast authentication, then configure NTP broadcast in MTS200 with
same type of settings.
