NCR 1530 WS

[Dropcam]

Terminal was set up and working properly, all of a sudden not sure how or we were not told but When trying to log into terminal we get error "System redundancy limit has been exceeded Restore your file server to continue. However when trying to restore from Aloha normal the screen would flash on the other stations but it appears file server recovery does nothing. The server can see the station and vise versa, firewall is not an issue. The 2 other stations are functional and working properly, some reason this terminal thinks it's in redundancy. Can't seem to find a resolution any where thanks in advance.

 

[ClayTaco]

My first bet would be a cabling issue. Reset all connections between term and fs to make sure you've got a good connection.
Is the aloha license for 3 terms?
What happens when you reboot the term? Are you able to recover it if it is the only live term?
You should also unregister and register your iberpath. Occasionally pathing can get screwed up.

Running a fileserver recovery is actually something you can do manually but check these items first. Doing a manual fileserver recovery can get you stuck in a pretty nasty reboot loop.

 

[AlohaRoss]

The issue has to do with DNS. From terminal in question run a ping to alohaBOH or what ever name your boh is, Is the IP that shows up the same IP as your aloha network. If not, then you have figured out why you are getting that error. to fix, you need to get your IP address worked out and make sure dhcp is not running on your FOH or BOH. Set IP for both to be below the range of internet. example if internet is 192.168.1.x then aloha should be 192.168.0.X. if internet is 10.0.0.X well then you have an issue. you would have to set aloha ip to something like 1.1.1.X (not advised) remember no gateway or DNS on FOH computers either.
Lastly after you have fixed IP run a ipconfig /flushdns on all FOH and reboot each.

AlohaRoss

http://www.needaholahelp.com

3rd Party support

 

[ClayTaco]

A DNS issue wouldn't explain the sudden failure would it? I haven't run into any issues with network settings changing unexpectedly.

Not that this isn't a good thing to check as it would explain this disconnect between the FOH and BOH.

 

[AlohaRoss]

Has you system been up for more than 30 days? Had same issue last year with new system, worked for 30 days no issue and then that error. after 4 hours, I figured out the issue by just running a ping from foh to boh and see what Ip foh thought BOH was. Sure enough it had different IP. changed host file to point to boh and never had issue again.

AlohaRoss

http://www.needaholahelp.com

3rd Party support