Other Topic Library Versions

K2Config setup for K2 Central server

If a proxy or conventional SAN already exists on the GV STRATUS system, then verify that the core server is synced before adding/editing configuration files.

  1. In K2Config, click STRATUS | Network Configuration, and ensure that the STRATUS Control Panel Services Host is set to the core server name.
  2. Under STRATUS | Sync to Control Panel, select “Overwrite… “ and Sync now.
  3. Verify that the SiteConfig and K2Config files are up-to-date in the following directories on the GV STRATUS core server:
    • C:\ProgramData\Grass Valley\ConfigurationDataFiles\K2Config
    • C:\ProgramData\Grass Valley\ConfigurationDataFiles\SiteConfig
  4. On the GV STRATUS core server, add/edit the K2Config.config and associated XML file.
  5. Enter a random key GUID for K2 Central in the K2Config.config and XML files.

    Below is a K2Config example of a B1 system with a proxy SAN and the manually added K2 Central SAN named "STRATUSK2C":

    <?xml version="1.0"
              encoding="utf-8" ?>
              <configuration>
              <appSettings>   
              <clear />   
    
              <add key="edcb2b7a-dff6-4f7b-a308-3831 bd511d40" value="c:\programdata\grass
              valley\configurationdatafiles\k2config\proxystorage_B1-proxy-1.xml"
            />    
    
              <add key="[K2Central guid]"
                value="c:\programdata\grass valley\configurationdatafiles\k2config\STRATUSK2C.xml"
                />
    
              </appSettings>
              </configuration>
  6. In the XML file, enter the same K2 Central name as saved in the K2Config.config file.

    Below is the example of an XML file that requires the K2 Central name, GUID, IP addresses, and K2 Summit clients configuration.

    <SAN SANType="Custom" IsRedundant="False Label="STRATUSK2C" CustomSANType="" UniqueId="[K2Central guid]" LiveProduction="True" MulticastIPBase="194"
    MulticastPortBase="31820">    
    
                <Device DeviceType="K2Server" Hostname="[K2Central server name]">    
                <Roles>      
                    <Role RoleType="FsServer" />      
                    <Role RoleType="DbServer" />      
                    <Role RoleType="FTPServer" />      
                    <Role RoleType="NASServer" />    
                </Roles> 
                <DeviceConfiguration>     
                  <NetworkConfiguration>        
                    <NetworkAdapter Label="Control 10G" MACAddress="0C:C4:7A:34:C9:B5" IPAddress="[K2Central Control network IP]" SubnetMask="255.255.254.0" DHCPEnabled="False" />        
                    <NetworkAdapter Label="FTP 10G" MACAddress="0C:C4:7A:34:C9:B4" IPAddress="[K2Central FTP network IP]" SubnetMask="255.255.255.0" DHCPEnabled="False" />     
                  </NetworkConfiguration>      
                  <FtpServerConfiguration FtpPortNumber="21" DataSocketTimeout="60" MaxStreamCount="10"/>   
                 </DeviceConfiguration>  
                </Device>    
    
                <Device DeviceType="Summit" Hostname="[Summit client 1 name]">   
                <DeviceConfiguration>
                  <NetworkConfiguration> 
                     <NetworkAdapter Label="Control Connection #1" MACAddress="00:B0:09:02:A8:63" IPAddress="[Summit Client 1 Control network IP]" SubnetMask="255.255.254.0" DHCPEnabled="False" />     
                  </NetworkConfiguration>      
                  <DatabaseClientConfiguration DbServer1="[K2Central server name]" DbServer2="" FTPHost="[K2Central server name]" />   
                </DeviceConfiguration>  
                </Device>  
    
                <Device DeviceType="Summit" Hostname="[Summit client 2 name]">   
                . 
                . 
                .   
                  </DeviceConfiguration>  
                 </Device>
                </SAN>
  7. Reboot the GV STRATUS core server.

Copyright © 2016 Grass Valley Canada. All rights reserved. GV STRATUS 4.5 gvtp_20160506_02:08:04