Other Topic Library Versions

Modifying K2 client managed network interfaces

  • The physical device you are configuring must be discovered and must be assigned to a device in the SiteConfig system description.
  • SiteConfig must have communication with the device.
  • The device must be defined in the system description with an appropriate network interface.
Use this task to modify managed network interfaces on a K2 SAN device as follows:
  • K2 Summit Production Client
  1. In the tree view select a K2 client, then in the Interfaces list view, identify interfaces as follows:
    • The SAN K2 client's control interface is a team. Modify the control team interface first. The control team is comprised of two individual interfaces, one for Control Connection #1 and one for Control Connection # 2. Do not modify these two individual interfaces.
    • For a SAN K2 client on a basic (non-redundant) K2 SAN, identify the iSCSI (non-Redundant) interface. After the control team, modify this interface as instructed in this procedure. Do not configure any other iSCSI interface, as only one iSCSI interface is used for a basic K2 SAN.
    • For a SAN K2 client on a redundant K2 SAN, identify the iSCSI (Primary Redundant) interface and the iSCSI (Primary Secondary) interface. After the control team, modify these interfaces as instructed in this procedure.
    • The SAN K2 client has no interface for FTP/streaming. All FTP/streaming goes to the K2 Media Server.
  2. In the Interfaces list view determine the interface to configure, as follows:
    • Identify the interface with which SiteConfig is currently communicating, indicated by the green star overlay icon. This should be the control network interface.
    • Verify that the interface over which SiteConfig is currently communicating is in fact the interface defined for the control network in the system description. If this is not the case, you might have the control network cable connected to the wrong interface port. The control connection should always be the first port on the motherboard, except when you have a loopback connection.
    • Configure the control network interface first before configuring any of the other interfaces.
    • After you have successfully configured the control network interface, return to this step to configure each remaining interface.
  3. In the Interfaces list view, check the icon for the interface you are configuring.

    If the icon has a red stop sign overlay, it indicates that current settings and planned settings do not match or that there is some other problem. Hover over the icon to read a tooltip with information about the problem.

  4. In the Interfaces list view, right-click the interface you are configuring and select Edit.

    The Managed Network Interface Details dialog box opens.



  5. Identify the interface on the discovered device that you are configuring.
    • Identify Ethernet LAN adapters by their "Description" name. This is the Windows connection name. SiteConfig reads this name from the device and displays it at the top of this dialog box. This is the most accurate way to identify the network adapter on the discovered device that you are configuring.
  6. Configure naming settings as follows:
    Setting... For network interface Control Team
    Interface Name The device host name. Required.
    Set To Default Not recommended
    DNS Suffix Allowed, if applicable to the network. The DNS suffix is added to the interface name.
    Aliases Not allowed
    Use Interface Name/Aliases in Host Files Unselected is required. Since not selected, the default behavior occurs, which is to use the device host name in the hosts file.

    Setting... For any network interface of type iSCSI
    Interface Name "Unused" is recommended. Displaying this text here serves as an aid in understanding SAN networks.The iSCSI network has no name resolution via the hosts file or otherwise, so the text you enter here is not actually use for name resolution.
    Set To Default Not recommended
    DNS Suffix Not allowed
    Aliases Not allowed
    Use Interface Name/Aliases in Host Files Selected is recommended. Since this interface’s network has its names excluded from the hosts file, this setting has no affect. The interface name is excluded from the hosts file, regardless of settings here.
    Note: There is no FTP/streaming network for a SAN K2 client. On the K2 SAN, FTP/streaming goes to the K2 Media Server.
  7. Evaluate settings on the Planned tab and change if necessary.
    • Compare settings on the Planned tab with settings on the Current tab.
    • If you want to keep the current settings as reported in the Current tab, click Remove to remove the planned settings.
    • Do not specify multiple IP addresses for the same interface. Do not use the Add button.
  8. To modify planned settings, do the following:
    1. Select the network settings and click Edit.

      The Edit IP Address dialog box opens.



    2. Edit IP address settings as follows:
      Setting... For network interface Control Team
      Network Control is required
      Address Allocation Static is recommended.
      IP Address The IP address for this interface on the network. Required.

      Setting... For basic SAN network interface Media Connection #1
      Network iSCSI (non-Redundant) is required
      Address Allocation Static is required.
      IP Address The IP address for this interface on the network. Required.

      Setting... For redundant SAN network interface Media Connection #1
      Network iSCSI (Primary Redundant) is required
      Address Allocation Static is required.
      IP Address The IP address for this interface on the network. Required.

      Setting... For redundant SAN network interface Media Connection #2
      Network iSCSI (Secondary Redundant) is required
      Address Allocation Static is required.
      IP Address The IP address for this interface on the network. Required.

      The networks listed in the Edit IP Address dialog box are those currently defined in the system description, with available settings restricted according to the network definition. If you require settings that are not available, you can close dialog boxes and go to the Network Configuration | Networks tab to modify network settings, then return to the Edit IP Address dialog box to continue.

  9. When you have verified that the planned settings are correct, click OK, then Yes to apply settings to the device and close. A Contacting Device message box reports progress.
  10. After configuring control network settings, do the following
    1. If a message informs you of a possible loss of communication, click OK.

      This message is normal, since this is the network over which you are currently communicating.

    2. In the Device list view, observe the device icon and wait until the icon displays the green star overlay before proceeding.

      The icon might not display the green star overlay for several seconds as settings are reconfigured and communication is re-established.

    3. In the Interface list view, right-click the interface and select Ping.

      The Ping Host dialog box opens.

      If ping status reports success, the interface is communicating on the control network.


Copyright © 2017 Grass Valley Canada. All rights reserved. K2 Summit 9.7 gvtp_20170317_08:51:20