These
Summit MDI
settings for SAN and/or
Summit MDI
settings for standalone are required on all
GV STRATUS
systems.
This type of MDI manages K2 Summit Production Client systems. This
topic describes settings for a K2 Summit SAN system.
To locate these settings, click Core | MDI Configuration | Add | Summit
Designate one of the
SAN-attached K2 Summit systems to be the managed device for the entire K2 SAN
storage system. Configure a
Summit MDI
for only that K2 Summit system on the K2 SAN.
If you have multiple standalone
K2 Summit systems, multiple K2 SAN systems, or a combination of standalone and
K2 SAN systems, each system must have its own Summit MDI.
When you have multiple
Summit
MDIs, they must each have their own process port number. For this purpose,
numbers 9160 - 9169 increment in the
Port
field.
| Setting or button
|
Description
|
| MDI Type
|
The Managed Device
Interface (MDI) type to which these settings apply.
|
| MDI Name
|
A name for this
instance of the MDI type.
Do not use spaces in the MDI
name.
The MDI name
could be renamed later, if desired.
Note: After renaming the Summit MDI, you must restart the Render Engine server and its
services. Then, reconfigure other settings on the
GV STRATUS Control Panel (such as Send Destinations, Rules, K2 Central
storage, etc.) to use the new Summit MDI
name.
|
| Hostname of device
running the MDI
|
The name of the
GV STRATUS server that hosts this
MDI.
|
| Port number
|
The process
port for this instance of the MDI type. Each instance must have its own process
port. Port numbers must be in range 9160-9169.
|
| Type of K2
device
|
Specifies either
SAN-attached K2 Summit system or Standalone K2 Summit system.
When SAN is selected, settings
are as follows.
|
| SAN Name |
The name of the K2
SAN, as named in K2Config. You can also enter the name of
third party storage device, if you have them in your
operation. |
| Primary Device
|
The
SAN-attached K2 Summit system designated to be the
managed device for the entire K2 SAN storage system. Or
the managed device for the third party storage system in
your operation.
|
| User Name
|
The
user name that this MDI uses to access the K2 Summit system.
This is the internal system account, which by default is GVAdmin.
|
| Domain
|
If on
a domain, it must be a fully qualified domain that this
MDI uses to access the designated managed device. This
field should only be set for fully qualified domain of
third party storage system in your operation.
|
| Password
|
The
password that this MDI uses to access the K2 Summit
system. Note: Do not enter a domain or
otherwise modify account settings except under the supervision of qualified
Grass Valley Support personnel. Extensive system configuration is required to
achieve a working GV STRATUS system.
|
| FTP Server Name
|
The FTP
server name for the remote K2 Summit system. The
drop-down list consists of all FTP servers belonging to
the Summit SAN. For the typical system where there
is a separate FTP network, this is the name of the K2 SAN's
FTP server with the _he0
suffix added. The _he0
suffix specifies the FTP network. |
| Maximum
concurrent transfers
|
The maximum number of concurrent
transfers allowed. The maximum is set in K2Config. You
may select the maximum or a lesser number as designed
for your system. The number of concurrent transfers as
well as the device status can be checked once the system
is configured in Resource Monitor of the GV STRATUS Control Panel. |
| FTP User Account
|
The FTP user
name for the K2 Summit system this MDI accesses. Typically this is
movie.
|
| FTP Password
|
The FTP
password for the K2 Summit system this MDI accesses. When this field is blank
the system automatically uses the default password.
|
If you changed MDI settings, you
must restart the GV STRATUS Core server system and the K2 Summit
system. If SAN MDI settings, you must restart the entire K2 SAN system,
including K2 Media Servers, attached K2 Summit systems, and other SAN
clients. If you are changing
multiple K2 Summit MDI settings, you can make all those settings first before
restarting these systems. Restarting the systems once is sufficient for multiple
K2 Summit MDI settings changes.
When
adding back a previously deleted Summit MDI, you can re-sync the MDI with all
data retained in the
GV STRATUS
database by doing the following:
- Reuse the same MDI name that was previously deleted
- Reuse the same port number that was used with the deleted MDI
