Satellite Internet

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

iDirect TCP traffic problem

(Read 3697 times)
Ex Member
Ex Member


Apr 24th, 2012 at 12:30am  
Hi,

I have a customer who was using iDirect connectivity from our hub for quite a long time.  All of a sudden from last month the iDirect modem started to have some issues.

The modem stays connected on the RF level, all the RF specs are good no warning or alarm on modem but the TCP traffic going through the modem stops...I have seen some UDP traffic going through but all the TCP traffic stops and the modem needs to get power cycled to restore the connectivity.

TCP acceleration was switched off and the issue happened again...the frequency of these hang ups is after every 3-4 days......I have captured some packets to analyze if the modem is under TCP sync flood attach but the TCP traffic passing through seems to be legitimate....

Can anyone suggest what other things needs to be checked....I am doubting on iDirect modem because only this device needs to be restarted to restore the connectivity.....what might be the issue here...??


Regards,
saiahmed
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #1 - Apr 24th, 2012 at 11:52am  
Is anything connected to the backplane, other than the client?  Good chance you may have something viral that is exhausting the iDirect CPU (due to tcp sessions, etc). What is baffling is that you say occasional UDP passes.

Suggest you check the CPU duty cycle (via CLI) the next time this condition manfests itself on the your system.
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #2 - Apr 24th, 2012 at 5:47pm  
I have checked the CPU load and it was 22% at the moment when modem was not passing any TCP traffic...a lot of errors were also there on the ixp0 port..see below the port specs taken during the problem...

ixp1   

RX Bytes: 1637744836 Packets: 9142598 Errors: 12603 Drops: 0
      
RX FIFO: 0 Frame: 12603 Compressed: 0 Multicast: 304096


One thing to add here...this modem is connected to a Passport switch and we can see FCS errors occuring on the switch port even during the modem's normal operation.....and at the time of hangup these errors can be seen on iDirect ixp0 port.....but during normal operation iDirect ixp0 port doesn't have any errors....only the passport switch shows few errors every minute or two.......any suggestions...
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #3 - May 1st, 2012 at 9:27am  
I have come across this many times. it is because of so many NAT sessions opened. to solve it you need to disable DHCP and use an Static IP in the LAN interface of the modem.

login to the modem and run below command to see NAT sessions status

   nat stats
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #4 - May 4th, 2012 at 7:48pm  
Hi Zein,

I am already using a static IP on the modem so the problem is not related to NAT sessions. We are not doing NATing. The modem also has 0 NAT sessions.

We have sort of isolated the problem by changing the cable between the modem and the switch. So far, the modem is running fine since last week. We are not seeing any more FCS errors on the ethernet port so hopefully we have found the solution as initially unshielded cable was used.  Let's see...how it goes...

Saiahmed
Back to top
 
 
IP Logged
 
Pages: 1