Masterclock GMR1000 - Configuration and Connectivity Problems



MasterclockGMRUserManualv2–2016.12
65
POSSIBLEREASONS/SOLUTIONS:
1. IncorrectnetworkconfigurationmaycausetheGMRtoreceiveafallbackIPaddressorperformsoftrestarts.
VerifythattheIPaddressiscorrect.Ifyoumanuallyenter(orDHCPassigns)anIPaddressthatalreadyexists
onthenetwork,thiswillcreateaconflict.TheGMRwillresetits
address(fallback)toonewithinthelink‐local
addressspace.DeterminethecauseofthefallbackIPaddressandresolvetheissue.
2. ViewtheerrorstatusfieldatthebottomoftheGMRStatuswindowformessages.
3. WhentheEthernetinterfaceisinitializedthenetworkdevicewillverify
thattheIPaddress(eitherstaticor
assignedbyDHCP)isnotbeingusedbyanotherdeviceonthenetwork.IfaconflictisfoundtheNTDclockwill
defaulttoa169.254.xxx.xxxaddress.TheIPaddressthatcausedtheerrorissavedandreturnedasanerrorto
WinDiscovery.This
errorstatusisavailabletotheuserviatheStatuswindowonWinDiscovery.
4. IfstaticIPaddressingisbeingusedtheoriginalconflictingstaticIPaddresscanberestoredbydoingasoft
restartofthedeviceusingeitherWinDiscovery,SSHorTelnetpriortochanginganyotherconfiguration
parameters.
5. Note:DeviceswhichhavebeenassignedafallbackIPaddressof169.254.xxx.xxxwillbedisplayedinthemain
WinDiscoverywindowwithREDtext,indicatingaproblemwiththeconfiguration.
IMPORTANTNOTE:iftheconfigurationofthenetworkdeviceischangedwhilea169.254.xxx.xxxisbeinguse,then
thecurrent
169.254.xxx.xxxaddresswillbecomethepermanentstaticaddressandtheoriginalconflictingstatic
addressislost.Atthispoint,itisnecessarytomanuallychangethestaticIPaddresstoaonethatwillnotconflict,
oryoumayhavetodoa“SetToDefaultConfiguration”torestorethe
systemtofactorydefaultsettings.

PROBLEM:
 GMRappearsto‘reset’periodically.
POSSIBLEREASONS/SOLUTIONS:
1. Checkthenetworkconnectionandsetup.IfDHCPisenabledandaDHCPserverisnotactiveonthenetwork
thewillrebootonceperhourwhileattemptingtoresolveDHCPconfiguration.Tocorrecttheproblem,switch
tomanualnetworkingconfiguration(setaStaticIPaddress)ordeterminewhythe
localDHCPserverisnot
operating.
2. IftheGMRhasnotbeenconfiguredwithatleastonevalidDNSserver(orthatDNSserverisdown)hesitations
similartothosedescribedin#1willoccur.AtleastonevalidDNSserverisrequiredforoperation.

PROBLEM:
 GMRUnabletocommunicateviaTelnet.
POSSIBLEREASONS/SOLUTIONS:
1. VerifythatyouhavethecorrectIPaddressfortheunitandtheIPaddressdidnotchange.IfusingDHCPto
providetheIPaddress,thisaddressmaychangeperiodically,youmustknowtheIPaddressoftheunittouse
theTELNETinterface.
2. VerifythattheGMR
doesnothavetheTelnetinterfacedisabled.
Note:Forsecuritypurposes,theTelnetinterfaceisdisabled.Tore‐enabletheTelnetfeature,oneoftheother
configurationmethodsmustbeused,ortheunitmustberesettofactorydefaultconfiguration.Pressingthereset
buttonwillnotenableTelnet.