Location mcsoc:/Users/socfiles/info/changing_cms_info.html
URL http://sohowww.nascom.nasa.gov/soc/soc/info_files/changing_cms_info.html
Last modified by EBZ
Last modified 06 July 2010

Changing between Command Management System (CMS) hosts/computers

Background information

The ECS can connect to two CMS computers (prime and backup) on the FOT/IMOC side. In order to change the CMS to which the ECS connects, the configuration needs to be changed and the ccommanding side of the ECS software needs to be restarted.

How to change the CMS connection

The new way for changing strings is in the file: Change Strings

The old way is:

The configuration files are in directory /home/ecs/ecs/ecs_config. The current working directory can be changed to this directory with command alias config. The relevant files are:

File Explanation
CMS The actual configuration file read by the ECS system upon software restart
CMS.2 Template file for connecting to the prime CMS (see the table above)
CMS.1 Template file for connecting to the backup CMS (see the table above)

To change the configuration the contents of the file CMS needs to be changed. The easiest way to accomplish this is to copy the suitable template file to file CMS. The new configuration becomes effective after ECS software restart. The necessary steps (all taken in a soc terminal window) are hence:

  1. Close the Command Status Display and Commanding Session Status windows on the xterm
  2. Copy the appropriate template file over the CMS file - can do this before or after the stopcmd (example: cp CMS.1 CMS)
  3. Type stopcmd & log the time and reason
  4. Type startcmd log the time and wait for the process to complete
  5. Open the Command Status Display and Commanding Session Status windows on the tlm
  6. Verify the socket connections by typing sock. The sock output (when connected to the prime CMS should look like below. If not every CMS socket is connected, check with FOT to be sure they have started up all of their software.

soc $ sock           *****redo this when we aren't doing testing*****

 ---------------------------------------------------------------------
 On either CMS1 or CMS2 
 There should be 1 ESTABLISHED and 1 LISTEN -- nrt socket
 There should be 1 ESTABLISHED -- delayed cmd socket
 
 Checking sockets on CMS1: (12910=NRT; 12911=delayed) 
tcp        0      0 0.0.0.0:12910               0.0.0.0:*                   LISTEN      
tcp        0      0 0.0.0.0:12911               0.0.0.0:*                   LISTEN      
tcp        0      0 129.165.38.114:42299        129.165.67.79:12911         ESTABLISHED 
tcp        0      0 129.165.38.114:12910        129.165.67.79:53418         ESTABLISHED 
 
 Checking sockets on CMS2: (10910=NRT; 10911=delayed) 
 
---------------------------------------------------------------------
 Checking sockets with IRTS -- 4 socket connections total
 (5621=VC2; 5620=all others) -- established and listen for both sets
 
tcp        0      0 0.0.0.0:5620                0.0.0.0:*                   LISTEN      
tcp        0      0 0.0.0.0:5621                0.0.0.0:*                   LISTEN      
tcp        1      0 129.165.38.114:5620         129.165.67.74:60432         CLOSE_WAIT  
tcp     9122      0 129.165.38.114:5620         129.165.67.82:35268         ESTABLISHED 
tcp        1      0 129.165.38.114:5621         129.165.67.74:60391         CLOSE_WAIT  
tcp        0      0 129.165.38.114:5621         129.165.67.82:34538         ESTABLISHED