Service manual

Configure static IP address on Server 2008
This task required on systems with Microsoft Windows Server 2008 operating system only.
SiteCong cannot discover systems with the Microsoft Windows Server 2008 operating system that
have no IP address, such as those that are congured for DHCP. Therefore you must congure the
system with a static IP address. You can use any IP address.
Removing a K2 Media Server
In a functioning K2 SAN, you should not permanently remove a K2 Media Server that takes the
role of media le system/metadata server, as this changes system capabilities and results in the
failure of some or all of the media operations for which the system was designed. Remove a K2
Media Server only under the direct supervision of qualied Grass Valley personnel.
If you are replacing a faulty server with a replacement server, follow the documented procedure.
Replacing a K2 Media Server
The requirements for replacing a K2 Media Server on an existing K2 SAN are as follows:
• You must be logged in to the K2Cong application with permissions equivalent to K2
administrator or higher.
Use this procedure if a K2 Media Server in a working system is faulty or otherwise needs to be
replaced with a new K2 Media Server.
NOTE: If you are replacing a non-redundant media le system/metadata server, you lose all
media during the replacement process.
1. If the server hosts an iSCSI interface adapter, copy down iSCSI bandwidth settings for K2 clients
and other iSCSI clients that use the faulty server as their iSCSI target, as follows:
a) In the K2Cong application, select the K2 SAN in the tree view and then click the button in
the toolbar to view client iSCSI assignments. A page opens that displays each client’s primary
and secondary iSCSI targets.
b) In the tree view, select one of the clients that have the faulty server as a primary or secondary
iSCSI target.
c) Open the client’s iSCSI Initiator Conguration page and click Modify. The Bandwidth Input
dialog box opens.
d) Copy down the bandwidth settings congured for that client and then close the Bandwidth
Input dialog box.
e) Repeat these steps for each client that has the faulty server as a primary or secondary iSCSI
target.
2. If the server hosts an iSCSI interface adapter, in the K2 System Conguration application, for
the faulty K2 Media Server, open the iSCSI bridge page and make a note of the IP addresses.
3. Copy down network and hostname settings for the faulty K2 Media Server. You can do this from
SiteCong or from the K2Cong application Network Conguration page.
4. Save a copy of the host table from the faulty K2 Media Server. You can use SiteCong hosts
le features or you can nd the host table at the following location on the K2 Media Server:
C:\WINDOWS\system32\drivers\etc\hosts
288 K2 Installation and Service Manual 2013 07 20
Administering and maintaining the K2 SAN