Satellite Internet forum
http://www.satsig.net/cgi-bin/yabb/YaBB.pl
VSAT technology and installation >> iDirect Forum: hubs and terminals >> Stack error- 3100 not logging on
http://www.satsig.net/cgi-bin/yabb/YaBB.pl?num=1210066577

Message started by satweb on May 6th, 2008 at 10:36am

Title: Stack error- 3100 not logging on
Post by satweb on May 6th, 2008 at 10:36am
With a 3100 idirect modem, fininshing of activation at the ground station end the O/S got corrupted because there was an older idirect verison. Syntack error mode . The message left now when trying to log on get the stack error.
Does anybody know how to fix?

Thanks in adviance

sales@satweb.co.uk

Title: Re:  Stack error- 3100 not logging on
Post by TDMAMike on May 6th, 2008 at 11:55am
Stack errors are normally indicative of corruption in falcon (falcon.opt specifically).  You need to reload your options file.  Be advised, that you may or may not be able to negotiate reloading your 3100 if the opt is corrupt.  You are going to have to give it a try and if not able, you may have to copy, cut, and paste it in from console. Try to load it with iSite first, if unsuccessful, you can try WinSCP or do it from the linux prompt on console from the /etc/idirect/falcon directory.  

To save myself some typing, see this thread:
http://www.satsig.net/cgi-bin/yabb/YaBB.pl?board=idirect;action=display;num=1208862320

Use Teraterm Pro instead of hyperterminal (if you have ttpro).  Hyperterm often adds characters when negotiating the cut and paste.

M

Title: Hi Re:  Stack error- 3100 not logging on
Post by satweb on May 6th, 2008 at 12:02pm
Hi Mike
I did see that thread, but wanted to check as this problem (to our inexpereinced eye) seems slighlty different.
The lights are the same

viewing the boot up through the console, FALCON loads ok , the fatal error occurs when trying to load the STACK files.

Do we still do  the same commands and process?




Title: Re:  Stack error- 3100 not logging on
Post by TDMAMike on May 6th, 2008 at 12:24pm
Can you attach to it with iSite?  

I am assuming you are seeing stack errors popping up in telnet...that is, if you are able to connect to it (which I am guessing you are able to telnet to it).

Did you see any fatal errors in the boot process right as falcon is starting (or possibly just before falcon starts)?  

It certainly wont hurt to reload the opt.  That is fairly painless/harmless. If you can attach with iSite it is even easier to load that opt.  

In the past I normally resolved stack errors by either copy and pasting the opt directly into etc/idirect/falcon or I would do it by using WinScp to move it from my desktop into etc/idirect/falcon.  However, if you decide to do it with WinScP save the opt out on your desktop and rename it to falcon (it will take on the .opt extension automatically) and then copy it into etc/idirect/falcon


Title: Re:  Stack error- 3100 not logging on
Post by satweb on May 6th, 2008 at 12:41pm
The installer is not able to use the iSite.
Are the instructions how he would load the option file using Hyper term?

Title: Re:  Stack error- 3100 not logging on
Post by satweb on May 6th, 2008 at 12:56pm
The messages that appears well connected through Hyper term.
On boot:  Failed to initialise ST
He is only able to ping the modem, he is not able to connect using iSite, Winscp, Telnet.

Title: Re:  Stack error- 3100 not logging on
Post by satweb on May 6th, 2008 at 1:31pm
They have tried that procedure and has made no difference, would an alternative option file work?

Powered by YaBB 2.5.2!
YaBB Forum Software © 2000-. All Rights Reserved.