telnet 0 issue

Your options file in it is corrupt or the wrong type (something is cetainly wrong with it).  

falcon_monitor (daemon) is detecting a problem with the falcon process (probably due to a corrupt opt) and is rebooting falcon.....continuously. That is why you cannot telnet 0 to falcon (your opt).

Since eth0 is dead, you are going to have to cut and paste a good options file into it (in linux).  

1. Do you have a good options file?  
2. Do you have a console cable?

I would actually like to LOOK AT the first few lines of your OPT so I can confirm you do not have a HUB SIDE options file?  Can you copy it into the forum (blank out any IPs, etc).

To save me some typing, the instructions you need are contained in this thread:

https://www.satsig.net/cgi-bin/yabb/YaBB.pl?board=idirect;action=display;num=122...

So, you are switching from a provider that used 7.1.1 back to one that requires 6.0.9.7?  

From the looks of it, you have the right image (pkg) for the box (6.0.9.7), but your options file is remaining 7.1.  To confirm, you pasted the 6.0.9 opt in? Correct?  That cut and paste should have worked.  Are you certain that you copied the 6.X options file and not the 7.1 optiosn file?  The below instructions should work everytime.  

1. Open the GOOD options file in notepad  
2. Control-A and (right click) Copy ONLY the text portion of the options file. NOTHING MORE...just the text.  
3. From console (the prompt should look like this - #) type cd .. (be advised there is a single space between cd and ..)  
4. Then type cd /etc/idirect/falcon/
5. type ls -l (you should see a filename falcon.opt which is your options file on the box).  
6. type cat > falcon.opt (there is a space on both sides of > ) Enter.
7. (on the next line) paste in the copied options file (the one you copied in notepad)  
8. Once the options file pastes in, hit the <enter> key once and then Control D (for done).  
9. This should bring you back to the # prompt.  
10. Type reboot to reset the unit.

If you have an 6.0.9.7 then you will need a 6.X options file. 

Yes, definitely stop falcon before cut and pasting (keeps the unit from rebooting)  Command at the prompt is:

service idirect_falcon stop

Beyond that, the instructions should fix your problem.....

Please ensure that you are running that cat > falcon.opt command from the /etc/idirect/falcon directory.  You can confirm that you are in that directory by typing pwd when you think you are there.  pwd will tell you what directory you are presently in.  It should be etc/idirect/falcon

Your options are limited at this point.  You possibly have a corrupt or wrong options file - which confines you to console or an ssh connection (with WinSCP for example).....or your image may not be 6.X like you think it is.

Are you certain that you have a 6.0.9.7 image on that iDirect unit?  How are you confirming that the image on the box is 6.X if you are unable to telnet to falcon?   

A 3100-NB will not work with version 6 hub. You will have to move to a provider that offers service on a version 7 hub or replace your modem.

Ah....this is a narrowband modem (devil is in the details).

Like dot said, it wont work.  It is doubtful you will be able to jam that 7.X opt in it to make falcon happy.  You can try it, but I would limit your expectations.

Hi Dot, can you confirm to me that 3100 will not work with version 6? because the problem I'm having with 3000 Series is that; at the 1st site, I was able to track the satellite (NSS10) but was experiencing drops at particular intervals (don't know what is the cause of the drops). At the 2nd site, I could not even get a signal. What could be the problem?

Hi Eric,
Thanks for being there.
How can I paste the captured screen for you to visualise? What I meant is;
At the 1st site, the RSSI is 4. for an interval of time, then drops to 1. then could up to 13. and come down to 1. and so on.
At the 2nd site, the problem is successfully peak up and receive the wanted satellite carrier.
Note: those sites are in 2 different cities
Thanks

The interval of time is close to 10 to 15 seconds then, the green band on the iSite monitor stops and goes to either red or yellow for 1 or 2 seconds, then back to green and the scenario repeats.

I didn't force the drop. Actually we noticed this when we setup the equipment for testing at our head office and thought this could be a local interference, thinking there would be no problem at our costumer's site.  But surprisingly, it's the same scenario.

There was no cell phone next to the coax cable or lying on the modem. I will cross-check whether there is an air conditioning or Flashing neon sign there.

The marks "Polarization" and "Cross" on the OMT are maching.

It is a C band receive system with 1.8m and our Hub is 3.8m

When the RSSI drops, do you drop link or observe low C/N?  i.e. lose the downstream carrier? 

You need to determine if the low RSSI corresponds with low rx snr. To check your rx snr, you can open a telnet session to the iDirect and run the rx snr command at the time you see the RSSI drop.  That, or use iSite to display your SATCOM stats (if you have that level of access).   

Are any other remotes (in this beam) reporting this condition? 

The modem should unlock (lose the TDM downstream carrier) with erratic signal levels, like you mention.  Need to confirm that.  If C/N is fluctuating, then you need to look hard at your LNB, associated cabling, and the DC that the iDirect is providing to the LNB...if DRO, consider PLL. 

Actually, I think the proper way to do it is to copy it and rename it.  Then when you overwrite falcon.opt with the "good" opt, you have a fall back plan with the one that was renamed.