TeamcenterKnowledge

System Administration > File Management System > Sample FMS configurations

FCC LAN client failover configuration

This configuration provides a hot local LAN failover configuration. Primary configuration file (FSC_HOME/fmsmaster_fscid.xml) This file is configured similar to the previous examples. See the FSC_HOME/fmsmaster.xml.template file for all available elements. The key point of this configuration's configuration file is: User assigned groups Half of the users are assigned to FSC Cache 1 as the primary FSC, half are assigned to FSC Cache 2. If either FSC cache machine fails, the FCCs fail over to the other FSC. Hot failover Both of the FSC cache machines are caching files. Therefore, if one FSC cache machine fails, the other takes up the additional traffic. There is potential performance degradation. Full system failure If both cache machines fail, no file access is available for clients. The volume servers can be designated as failover machines to cover the unlikely event of a three-box failure scenario. Copy FSC configuration files (FSC_HOME/fsc.xml) See the FSC_HOME/fsc.xml.template file for all available elements. This FSC configuration file for this configuration has the following key points: Redundant configuration servers FSC1 and FSC2 are designated as configuration servers. The other FSC servers specify FSC1 and FSC2 as the primary and failover configuration server, respectively. Copy FSC1 FSC2 FSC3 FscCache1 FscCache2 FCC configuration file (FMS_HOME/fcc.xml) This example of the FCC configuration file is similar to previous examples. The key point is: Configuration failover Two different FSCs are identified as configuration servers. This insures that the FCC can initialize by downloading the configuration file in case one FSC cache machine has failed or is taken down for maintenance. Copy

Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/AWAdmin/fhs4814155880506/uuc1737238583853/xjr1737238604512/fcc_lan_client_failover_config.html · retrieved Fri Jul 31 2026 00:00:00 GMT+0000 (Coordinated Universal Time)