Other Topic Library Versions

About SiteConfig and K2Config settings

Many settings and operations, such as network settings, adding/removing devices, and software versions, are managed by both the SiteConfig application and the K2Config application. Each application has its own XML file in which information is stored. You can keep the applications in synch by using an orderly task flow as you configure the K2 SAN.

When doing initial installation and configuration tasks, you can export/import system information from one application’s XML file to the other application’s XML file. You can also merge from K2Config into an existing SiteConfig system description. These export/import/merge features support a one-time process in which a system as described in the XML file of one application is imported into the XML file in the other application. The target XML must not already contain the system being imported.

When you change a setting in one application, it is not automatically updated directly in the other application. The applications do not communicate dynamically with one another. However, both applications can read settings as currently configured on the actual physical device and update their XML file accordingly. This is the method you must use to keep the applications in synch.

When you change a setting that is managed by both applications, you should change it first in SiteConfig, as a general rule. This application gives you the best context for the system as a whole and provides features to identify and verify changes. Once the change is implemented on the actual physical device, you must then open the relevant page in the K2Config application. This causes the K2Config application to refresh its settings from the device and write the change to its XML file. It also allows you to verify your change within the context of the K2Config application.

The following table summarizes operations that involve interaction between SiteConfig and K2Config.
Operation Task flow context and policies Additional information
Import SiteConfig system description file into K2Config Use this operation for initial install/commission (greenfield) sites. First define the site topology using SiteConfig and complete network configuration and software deployment. Then import the SiteConfig system description into K2Config and complete the K2 SAN configuration. This operation creates a K2 SAN in K2Config with SiteConfig defined devices. Uses the site name to check if the K2 SAN already exists. The operation will not import if the K2 SAN exists with the same name. The operation can import all sites which are K2 SANs from a single system description file in a single import step.
Import K2Config XML into SiteConfig Use this operation when you're running SiteConfig for the first time at a site with existing K2 SANs that have already been configured with K2Config. This allows you to seed the SiteConfig system description with device information that is already in the K2Config XML file. After you have done this operation for the first time, do not do it again. This operation creates a SiteConfig site with K2Config defined devices. The operation removes all other sites.
Merge K2Config XML into SiteConfig system description Use this operation when you've already defined some sites using SiteConfig and you later want to bring in another K2Config defined K2 SAN that doesn't exist in SiteConfig. Do not merge a K2Config XML that you've already merged. If you do so, it is likely that SiteConfig will create a new site with the same devices. This operation creates a SiteConfig site with K2Config defined devices but leaves existing sites as is.
Rename Site\SAN Rename first in SiteConfig. Then rename in K2Config. Do not import\merge into SiteConfig or K2Config.
Remove Site\SAN Remove first in SiteConfig. Then remove in K2Config. Do not import\merge into SiteConfig or K2Config.
Remove device Remove from both SiteConfig and K2Config.
Add device Add in SiteConfig first, do network configuration and software deployment. Then, add in K2Config and configure using K2Config.
Create a new site\SAN Use SiteConfig to create site, add devices, configure network and deploy software, then import into K2Config and configure each device
Change hostname Perform hostname change using SiteConfig. Remove and re-add to K2Config. If changing the hostname of a media file system/metadata K2 Media Server, re-configure all clients on the K2 SAN using K2Config
Change IP address (except address of TOE on K2 Media Server) Use SiteConfig for IP address changes. Then in K2Config, click on the changed device's network configuration node. This refreshes the K2Config view of IPs from the device.
Change IP address of TOE on K2 Media Server For TOE IP changes and/or TOE card removal, use K2Config.
Modify K2 SAN redundancy - redundant to non-redundant or vice versa Use SiteConfig to recreate the site using the appropriate redundancy models and configure network and deploy software. Remove K2 SAN from K2Config. Import site into K2Config. Configure using K2Config.

Copyright © 2019 Grass Valley Canada. All rights reserved. GV STRATUS 6.8 gvtp_20190318_01:43:25