Grass Valley Aurora Browse v.7.0 Installation - Manual (Page 92)

92 Aurora Browse Installation and Configuration Guide April 6, 2010
Chapter 5 Configuring the system
Configure K2 MDI
This page configures the Managed Device Interface (MDI) for a stand-alone K2 client
or a K2 client on a K2 Storage System (SAN). MediaFrame depends on the K2 MDI
to make K2 assets visible across the system.
As you configure the K2 MDI, make sure that you associate the K2 MDI and K2 host
names correctly.
Multiple K2 MDIs run on a single machine (the MDI Server), but they each need their
own process port number. For this purpose, enter incrementing numbers 9160 - 9169
in the “Port” field. The MDIs and their port numbers must match settings as in
“Configure MediaFrame ASK: Register components” on page 84 . To make the
configurations easier to read for troubleshooting purposes, add MDIs sequentially so
there is a correlation between the port number and any number in the MDI name.
If you have a K2 Storage System, designate one of the K2 clients on the K2 Storage
System to be the managed device for the entire storage system.
1. On the MDI server, select Programs| Grass Valley | MediaFrame Config . Select the
MDI Configuration tab and the K2 icon.
2. Enter the name of the MediaFrame server. Do not modify Port 9010. See “Ports and
services mapping” on page 47 .
3. Under Registered K2 Devices, click Add.
4. Enter the K2 MDI. Use the ... button to choose the MDI.
5. Increment 9160-9169 so each K2 MDI has a unique process port. For each FSM,
there should be one K2 MDI.