Other Topic Library Versions

Configure fsnameservers on servers-class devices

This task applies to SAN systems with one or more SNFS servers that have had their Broadcom driver updated to version 7.0.11.0. On those SAN systems, all devices with a V: drive to the SAN's storage (all SNFS servers and SNFS clients) must have their fsnameservers file configured. This includes the following type of SAN systems:
  • An online or production K2 SAN — If the SAN's SNFS server, which is the K2 Media Server with role of media file system server (FSM), has had its Broadcom driver updated to version 7.0.11.0, then this task applies to the following server-class devices on that SAN:
    • The one K2 Media Server (if non-redundant) or two K2 Media Servers (if redundant). This device is the SAN's SNFS server.
    • If a GV STRATUS system, the GV STRATUS Proxy Encoder. This device is an SNFS client on the SAN.
    • If an A1 GV STRATUS system, the GV STRATUS Proxy Server. This device is an SNFS client on the SAN.
    • Any other SAN-attached server-class devices, such as NH FTP servers. This device is an SNFS client on the SAN.
  • A nearline K2 SAN — If the SAN's SNFS server, which is the K2 Media Server with role of media file system server, has had its Broadcom driver updated to version 7.0.11.0, then this task applies to the following server-class devices on that SAN:
    • The one K2 Media Server (if non-redundant) or two K2 Media Servers (if redundant). This device is the SAN's SNFS server.
    • Any other SAN-attached server-class devices, such as NH FTP servers. This device is an SNFS client on the SAN.
  • A GV STRATUS Proxy Storage system — If the SAN's SNFS server, which is the Proxy Storage file system server, has had its Broadcom driver updated to version 7.0.11.0, this task applies to the following server-class device:
    • The Proxy Storage file system server. This device is the SAN's SNFS server.

The SAN must be in an offline mode before doing this task.

You must know your server's names and IP addresses.

  1. On the SAN's SNFS server that has had its Broadcom driver updated, login to the server as Administrator.
  2. In Notepad, open the following file: D:\SNFS\config\fsnameservers
  3. In the file, identify the server name of the local server. If a redundant SAN, identify the server names of both of the redundant servers.
  4. Edit the line of text and replace the server name with the server's IP address. If a redundant SAN, replace both server names with their IP addresses. Make sure you leave text lines intact. Do not alter the line returns, spaces, other elements of the text line.
  5. Save the file.
  6. Copy the fsnameservers file to an external location, such as a network share or a USB drive, that allows access by the other devices of the SAN.
  7. Restart the server.
  8. If redundant SNFS servers, do the following on the other redundant server:
    1. Copy (overwrite) the fsnameservers file onto the device. On SNFS servers, the file's location is D:\SNFS\config\fsnameservers.
    2. Restart the device.
  9. On other server-class devices that are SNFS clients, do the following:
    1. Copy (overwrite) the fsnameservers file onto the device. On SNFS clients, the file's location is C:\SNFS\config\fsnameservers.
    2. Restart the device.

You must also configure fsnameservers on all remaining SNFS clients on the SAN. Refer to the related topic later in the upgrade process.

Parent topic: Upgrading a K2 SAN

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