DGS (General)takahiro.yamamoto - 21:59 Wednesday 04 February 2026 (36284)
Print this reportupgrade of k1cam0After all cameras on k1cam0 had been moved to k1cam2 (klog#36217), k1cam0 was no longer used. So I applied a same upgrade to k1cam0 as k1cam2 though the hardware is still an old V0 server. After then, all cameras on k1cam1 except OMC_TRANS were moved to k1cam0. Remaining OMC_TRANS will be migrated to the new pylon-camera-server with the update of OMC_LSC guardian (see also klog#36226).
----- At first, I tried to make a new boot disk of k1cam0 as the copy of the master disk. But the old V0 server doesn't support UEFI though the master disk was generated as the UEFI boot. So I newly installed OS as the legacy BIOS mode. After purchasing new server hardware, it may be better to re-install as UEFI mode. (Default mode of recent hardware is UEFI mode and installing as BIOS mode to such hardware is sometimes troublesome.) Installation procedure can be found as JGW-T2516613 and it takes ~40min. So re-installation can be done within the half day in the weekly maintenance.
After the OS installation, I moved cameras on k1cam1 which is still running as the old camera-server to k1cam0. Then I noticed that POP and POP_P images were swapped. So I checked information on Wiki, S-number on JGWDoc and old/new camera configurations carefully, and then I found a mistake in the management of the serial number of camera devices. The old camera-server accesses each camera by using IP address. On the other hand, the new pylon-camera-server accesses by using an inquiry of serial number with the broadcast packets. So it wasn't a serious problem on the old camera-server in the past. Anyway, the serial number of camera devices for POP and POP_P had been swapped on Wiki and JGWDoc and these wrong information were revised in this time.
Now only OMC_TRANS camera is still running on the old k1cam1 because of the compatibility issue with the OMC_LSC guardian. So I planned to migrate it with the modification of OMC_LSC guardian in the next maintenance day. After then, we can remove k1cam1 (and rename k1cam2 as k1cam1 if necessary). We also need to replace the computer hardware for k1cam0, but it's a task containing a purchase in the next fiscal year.