Grass Valley SiteConfig Migration Instructions - Manual (Page 35)

Network interfaces
When SiteConfig discovers a device, it attempts to map the actual device's network
interfaces to the placeholder device's network interfaces. If the actual device's network
interfaces are connected or configured differently than those in the placeholder device,
SiteConfig frequently maps the interfaces incorrectly. This is especially true of the
control network interface. If this problems occurs, the typical solution requires
removing and adding interfaces to the placeholder device. Therefore, if your actual
device's network interfaces do not match its device model's network interfaces, when
you develop your system description you should customize that placeholder device's
network interfaces, rather than use the network interfaces as provided by the device
model. This allows you to define each placeholder network interface exactly as it is
connected and configured on the actual device. This requires more steps and a longer
process before you begin device discovery, but results in fewer problems, less
troubleshooting, and less rework as you discover and assign devices.
For example, your device might have its network connections reversed compared to
the device model. An example of reversed connections is the control connection
connected to port 2 (2
nd
port on the motherboard) and the streaming connection
connected to port 1. To solve this problem, remove both interfaces from the placeholder.
Then add the first interface and select the streaming network from the list of networks.
This tells SiteConfig which network that interface connects to. Then add the second
interface and choose the control network from the network list. Your placeholder
interfaces now match the actual devices interfaces.
Software roles
When SiteConfig checks software to prepare for software deployment, it provides
software deployment tasks based on the software roles assigned to the device in the
system description. If the actual device's software roles are different than those assigned
to the device in the system description, SiteConfig can not provide the appropriate
software deployment tasks and you can not deploy the software. Therefore, if your
actual device's software roles do not match its device model's software roles, when
you develop your system description you should customize that device's software
roles, rather than use the roles as provided by the device model. This allows you to
define each role exactly as it is on the actual device. This requires more steps and a
longer process before you begin software deployment, but results in fewer problems,
less troubleshooting, and less rework as you deploy software.
Qualifying network interfaces
Check network connections on your actual system devices and make sure that what
SiteConfig expects, as configured in the placeholder device, matches what is on the
actual device. Network interfaces as identified by SiteConfig typically correspond to
rear panel connectors on devices as follows:
02 July 2009 SiteConfig Migration Instructions 35
Evaluate and prepare devices for SiteConfig