Happy Christmas to you all.
Satellite Internet home page

Satellite Internet Forum.

Welcome, Guest.
Welcome to this satellite broadband discussion forum. Wherever you are and whatever your problem we are here to help each other. Connecting to the internet via satellite is not always easy but is critically important to those in remote places or with poor terrestrial infrastructure. Both service providers and customers are encouraged to contribute. Register at the bottom of the forum home page if you wish to contribute or ask question. May 2018: GDPR: Updates to Privacy and Cookies policies: As you may know, a new EU data protection law called GDPR will apply from Friday 25th May 2018. As part of satsig's commitment to protecting the privacy of site visitors and forum members, I have therefore updated the Privacy and Cookie policies. There are now links leading to these policies: Disclaimer, Terms of Use and Privacy, Forum User Agreement, Forum Rules and Cookies at the bottom of the home page and all forum pages. Read the Forum rules.
      Satellite internet forum          
Pages: 1

Remote TCP Connection

(Read 1151 times)
Ex Member
Ex Member


Feb 11th, 2014 at 9:00am  
At my HUB we manage a large number of nodes and since changing sites have lost our "TCP Connection" to our remotes. Basically, we can monitor them juts fine in iMONITOR but when it comes to pushing changes through iBUILDER we can only do so through UDP pushes. So our iBUILDER page has numerous bubbles over our remotes identifying changes that need to be verified.
A basic summary of troubleshooting so far: IP's have been checked, routing in our upstream and tunnel switches have been checked, NMS and PP's have been "checked", we've performed TCP Dumps while testing SSH connections from a local computer to a remote downstairs (revealed that 'syn' is sent, 'syn' is received, 'ack' is sent back, 'ack' is never received by the remote or computer that is attempting to connect to the other). I've found that in our PP the ripd.conf and zebra.conf lack a configuration but my inexperience in working "that deep" in the equipment keeps me from understanding what all needs to be there for routing. There was a possible firewall issue in our ASR that may need remedying but that fix may or may not be able to happen. Does anyone have any thoughts on troubleshooting this issue? Any help would be greatly appreciated.
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #1 - Feb 18th, 2014 at 3:06am  
Hi,

Have you changed QoS recently? I have seen this happen in the past with an issue in the QoS.

Try revert the QoS to default and see if this works.

Have you restarted the services on the NMS?

Hopefully you find the issue soon. If not, the TAC is always there to help. Smiley
Back to top
 
 
IP Logged
 
Pages: 1