Advertisment: Broadband via satellite
Advertisment: Worldwide satellite services from Ground Control Company

www.satsig.net

Satellite Internet Forum.

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

3100 rebooting

(Read 6961 times)
beedee
Member
★★
Offline



Posts: 7
Sep 11th, 2008 at 6:11pm  
Hi,

I'm configuring the iDirect 3100 and after following procedure and upgrading to 7.0.5 , the modem just reboots constantly.

I've tried reloading options, then the image (7.0.5) with no success. Cannot telnet 0 either as falcon is not running. Startup err : falcon Warning: This board is incapable of being a '<UNKNOWN_TYPE>'!

I can console and ssh into the unit as root. Any thing I'm missing?
Back to top
 

Regards&&beedee
 
IP Logged
 
Ex Member
Ex Member


Reply #1 - Sep 11th, 2008 at 7:59pm  
Your system is contantly rebooting because falcon monitor is detecting something wrong with the options file you have loaded, or the lack of an options file entirely.  

If you get on console of that 3100, you can type service idirect_falcon stop which will keep it from rebooting. However, you are going to have to copy and paste an options file into that box from the linux command line/prompt.  Because Eth0 (which is identified by the options file) of that box is more than likely dead.

Here are the procedures you need to follow for the command line/paste to host:

*Prior to starting ensure your type: service idirect_falcon stop (to keep it from rebooting).

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.

The system should come up on the options file you pasted in.  
Back to top
« Last Edit: Nov 27th, 2008 at 10:54pm by N/A »  
 
IP Logged
 
beedee
Member
★★
Offline



Posts: 7
Reply #2 - Sep 11th, 2008 at 8:28pm  
Mike,

I've followed instructions as per 'recovery procedure' and again as you described, just in case I missed something - but the result is the same (falcon not running). I've even reloaded the image to make sure.

I'm using the original options file which I'd saved on iBuilder.

Back to top
 

Regards&&beedee
 
IP Logged
 
Ex Member
Ex Member


Reply #3 - Sep 11th, 2008 at 8:31pm  
What iDS? Gonna have to think about this one.  
Back to top
 
 
IP Logged
 
beedee
Member
★★
Offline



Posts: 7
Reply #4 - Sep 11th, 2008 at 8:34pm  
7.0.5
Back to top
 

Regards&&beedee
 
IP Logged
 
Ex Member
Ex Member


Reply #5 - Sep 11th, 2008 at 8:36pm  
What iDS were you upgrading from?  
Back to top
« Last Edit: Sep 12th, 2008 at 11:42am by N/A »  
 
IP Logged
 
beedee
Member
★★
Offline



Posts: 7
Reply #6 - Sep 11th, 2008 at 8:41pm  
Upgrading from 6.0.9 - modem only using iSite. Hub and NMS already at 7.0.5

# falcon --version
Code Version: 7.0.5.0
Build Comment: Release build
Build Label: NetModem-7_0_5
Back to top
 

Regards&&beedee
 
IP Logged
 
beedee
Member
★★
Offline



Posts: 7
Reply #7 - Sep 11th, 2008 at 9:42pm  
Thanks Mike,

Seems to be resolved now - bad options file format. I'll configure more remotes tomorrow and review/revise my procedure.

New at this...learning along the way, with help from the forum.

Ta
Back to top
 

Regards&&beedee
 
IP Logged
 
Ex Member
Ex Member


Reply #8 - Sep 11th, 2008 at 9:59pm  
Good to hear....

It sounded as if you had a Hub-Side options file in it (especially since you mentioned it was displaying "unknown type")!   I beleive if you plug a HUB side options file (instead of a remote side opt) in it, you get that error. 

Was that the case?

Have a good one.
Back to top
« Last Edit: Oct 7th, 2008 at 11:56am by N/A »  
 
IP Logged
 
beedee
Member
★★
Offline



Posts: 7
Reply #9 - Sep 12th, 2008 at 8:27am  
Yes Mike,

That was exactly it - using hub-side config file. My colleague has transferred the procedure to me before leaving for a few weeks but something was "lost in translation".

I'm doing more remotes today and hopefully have a better procedure.

Much appreciated.
Back to top
 

Regards&&beedee
 
IP Logged
 
Pages: 1