Advertisment: Broadband via satellite
Advertisment: Planet Earth rotating animation

www.satsig.net

Satellite Internet Forum.

Welcome, Guest.        Forum rules.
      Home            Login            Register          
Pages: 1

Remote Problem

(Read 4343 times)
Ex Member
Ex Member


Apr 23rd, 2009 at 9:43am  
Hi,

Hub & this remote are able to ping each other. The remote is able to get on net but at the iMonitor there is an alarm for the remote showing "Stopped receiving echo reply from remote".

Try to reset the NMS, reload remote config file but no use. What should i do?

Pls kindly advice. Thank you.
Back to top
 
 
IP Logged
 
TDMAMike
Senior Member
★★★
Offline



Posts: 826
Reply #1 - Apr 23rd, 2009 at 12:02pm  
When you UDP push it (with reboot), can you visibly see the unit reboot in the Events and Conditions tab?  Does it bust the link layer (os reboot?)

How about when you use TCP to reset falcon? Does it respond and restart falcon?

Since you are investigating, I recommend you use iSite (from the hub) to pull/extract the opt from the remote.  Log into it over the link (eth0 or Sat0). Save it to your desktop.  Once on your desktop, take a look at the interface addresses for Eth0 and Sat0.  Ensure they match those that are populated in the Hub.  Look at every octet.  To esure accuracy. 

Let me know what you come up with.
Back to top
 

Regards, &&&&M
 
IP Logged
 
Ex Member
Ex Member


Reply #2 - Apr 23rd, 2009 at 3:52pm  
Hi,

Remote is able to reset thr' the UDP and the IP & Mgmt address are correct compared to the Hub side.

It seems that this problem is caused by another remote in another network. Cos' once i power off another remote, this problem disappear?

Do you know why?

Best Regards,
Back to top
 
 
IP Logged
 
TDMAMike
Senior Member
★★★
Offline



Posts: 826
Reply #3 - Apr 23rd, 2009 at 4:30pm  
Sounds to me like you have a possible IP conflict (dup).
Back to top
 

Regards, &&&&M
 
IP Logged
 
Ex Member
Ex Member


Reply #4 - Oct 6th, 2009 at 11:26am  
try to change your IP addresse , when your remote camback , re-inter the original ip add
Back to top
 
 
IP Logged
 
Scout
Senior Member
★★★
Offline



Posts: 86
Reply #5 - Oct 6th, 2009 at 1:27pm  
TDMAMike wrote on Apr 23rd, 2009 at 4:30pm:
Sounds to me like you have a possible IP conflict (dup).

Agree with Mike.  Try this:
When you have just this modem online and not the other one that causes the issue.  try a trace route form the NMS or the upstream router.  record the output.
Bring the other modem that causes the issue back online and do the trace route again.
see if there is a change in the behaviour.
Back to top
 
 
IP Logged
 
Pages: 1