Manage your FSC on Linux

Following are tools to assist you in administering your FMS configuration running on Linux: To verify the FSC is running, enter the following: %./fscadmin.sh -s http://hostname:port fsc-ID/status Example: Copy %./fscadmin.sh -s http://EVALSUN8:4544 FSC_EVALSUN8_user1/status To check the status of the read cache, enter the following: %./fscadmin.sh -s http://hostname:port fsc-ID/cachesummary/read Example: Copy %./fscadmin.sh -s http://EVALSUN8:4544 FSC_EVALSUN8_user1/cachesummary/read To check the status of the write cache, enter the following: %./fscadmin.sh -s http://hostname:port fsc-ID/cachesummary/write Example: Copy %./fscadmin.sh -s http://EVALSUN8:4544 FSC_EVALSUN8_user1/cachesummary/write To stop the FSC, enter the following: %./fscadmin.sh -s http://hostname:port fsc-ID/stop Example: Copy %./fscadmin.sh -s http://EVALSUN8:4544 FSC_EVALSUN8_user1/stop If the FSC fails to start The FSC can fail to start after a reboot of Linux systems. This can occur when other services upon which the FSC depends have not yet started. For example, the ypbind service can take additional time to start. Because the ypbind service was not operational when the FSC attempted to start, the su operation failed to switch to the user required to start the FSC. In this case, correct the reason the ypbind service launches slowly. Because Siemens Digital Industries Software is not directly contributing to the slow launch of the ypbind service, the resolution must be investigated by your IT department on a case-by-case basis. One workaround is to add a pause in the startup script. A sleep value of 120 seconds is sufficient in test systems. The sleep command must be added to the startup script in the rcname.d directory. Do not modify the rc scripts under the TC_ROOT directory; these are not the scripts first called. Note Renaming the rc script in the rcname.d directory to force the service to boot later in the boot order does not provide sufficient time to allow the ypbind service to start in test systems. If a RedHat Linux system does not accept connections from Windows systems or other sources Connections may not be accepted due to a known RedHat Linux TCP daemon issue caused by third-party software. Perform the following steps on each RedHat Linux system if you encounter this issue. Log in as a system admin (root). Edit the /etc/sysctl.conf file, adding the following setting: Copy net.ipv4.tcp_timestamps=0 Reboot the Linux system and restart all servers.