AMMRL: Topspin on CentOS 6.x

From: David Richardson <David.Richardson_at_ucf.edu>
Date: Fri, 3 May 2013 19:38:19 +0000

Hi all,
Anyone out there attempted running Topspin 3.2 on CentOS 6? We have encountered an interesting error and I was hoping someone might have a suggestion. We cannot get the console and the computer to communicate correctly. The error is with the dhcp client on the computer giving addresses to the various boards. I assume the problem is with addressing the IPSO, but am not sure.

We pulled the dhcp log and can see the console request address 149.236.99.90. The dhcp client properly assigns the address but it gets stuck in a loop and the console just continues to ask for the address. We can see from the acp table that the computer has accepted the request with the proper ip and mac, but the console continues on. Reboots and cycling the power have not worked. We have also tried removing the x64 dhcp packages and installing their i686 counterparts. The Topspin install log did indicate it was upset with a few of the packages, namely tftp-server and a part of dhcp-common, but we have since reinstalled Topspin with the package changes and no errors are generated. Connecting the cable from the console back to the old host (a Windows XP box running Topspin 2.1.6) results in a working instrument.

If it means anything to anyone, the code displayed on the IPSO board is d2 (or I suppose ZP if I am looking at it the wrong way).

I had initially setup the computer with CentOS 5 and we were able to connect without a problem. Is anyone aware of a change in the dhcp packages from 5 to 6 that the console doesn't like?

Our options at this point are to update the firmware on the boards (the console is an Avance III from 2008 and the one time I did successfully open Topspin 3.2 on the new host, when it was running CentOS 5, it asked for numerous firmware updates) and hope that the dhcp error gets resolved, spin up a CentOS 5 vm and take a look at the dhcp client and what might have changed, or just go ahead and redo the computer with CentOS 5. That last option is not a great one because our Varian (I may one day get used saying Agilent, but that day is not today) instruments are all running on CentOS 6 and for our various scripts and the sake of continuity I would prefer to have all of them on the same OS.

Any help would be appreciated.

Thank you,

David Richardson, Ph.D.
NMR Instrumentation Specialist
University of Central Florida
Department of Chemistry
PO Box 162366
Orlando, FL 32816-2366
david.richardson_at_ucf.edu<mailto:david.richardson_at_ucf.edu>
office: PS236 (407) 823-2961<tel:%28407%29%20823-2961>
lab: CH335 (407) 882-0117<tel:%28407%29%20882-0117>, PS151 (407) 823-2906<tel:%28407%29%20823-2906>
fax: (407) 823-2252<tel:%28407%29%20823-2252>
Received on Fri May 03 2013 - 09:38:23 MST

This archive was generated by hypermail 2.4.0 : Sun Jun 18 2023 - 15:42:51 MST