Call Pilot 100 Config Issue

[HUCHIMAMA]

Ok, Call Pilot 100 sw3.1 on MICS with 4.1 I am having trouble getting the call pilot to boot up. Did the normal connected everything like we do for every install. Power up the CP100 LED's start blinking ETC. Come back from lunch and KSU does not see the CP. Check Port/DN status nothing.

So I reboot using a serial cable to watch the boot up process. And everything seems to load fine until the end I get a message "SysConfig file does not exist. USe default !!!!.

So I press enter and get a login and password. I am clueless on what is happening.

I have rebooted half a dozen times and let sit for 20-30 minutes each bootup.

Any thoughts guys.

kgrant

 

[senk1s]

sysconfig file doesnt exist use default"

this is NOT an error message, it is normal - just let it go ...dont press enter or anything

3.1 is supported on 7.0 and above (as per compatibility)

 

[HUCHIMAMA]

senk1s Thanks for input. I brought the cp back to our office and noticed just keeps going the a reboot process. Also had put it on a 7.0 and same thing.

I had even tried to get into with the NIC and no luck.


kgrant

 

[Johnthephoneguy]

You have to have it connected to a Norstar to get it completely up.

 

[HUCHIMAMA]

It is on a Norstar CICS 7.0 I left it running all night. And still no luck. I checked the station ports with a phone and they are good. Hooked up another CP100 3.1 and works fine.

I noticed on my computer that is running hyper terminal. The CP keeps rebooting. After I get this message "sysconfig file doesnt exist use default" I get a following message "access failed system will restart" Then in a few secounds the LEDS start blinking again for reboot.

kgrant

 

[Johnthephoneguy]

if you have a known good one working and this one doesn't, it sounds like this one is doa

 

[HUCHIMAMA]

I believe I just determined it to be the software. Swapped the software and booted up fine. I should have looked into it more before I posted it.

Thatnks for the help guys.

kgrant

 

[bdalida]

Try upgrading the boot load firmare if it is at 1.5.19. Upgrade it to 1.5.21. That might fix it.

 

[HUCHIMAMA]

bdalida - I am sorry to say I have no idea how to do that. Is there a good procedure for doing this.

kgrant

 

[senk1s]

Bootloader may not be the issue - as that is the first thing that happens (but there is a FAQ on that). It may not gte as far as trying to start ACCESS

Try reloading the software, there is a FAQ for that as well

Try using just the software from teh other working CP and see if it boots up