Configure k2 mdi – Grass Valley Aurora Browse v.6.5 Installation User Manual
Page 58
58
Aurora Browse Installation and Configuration Guide
November 1, 2008
Chapter 3 Configuring the system
Configure K2 MDI
This page configures the Managed Device Interface (MDI) for a stand-alone K2
Media Client or a K2 Media 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 Media Frame ASK: Register components” on page 51
. 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 Media 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
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.