Service manual
5. Identify the interface on the discovered device that you are conguring.
• Identify Ethernet LAN adapters by their "Description" name. This is the Windows connection
name. SiteCong reads this name from the device and displays it at the top of this dialog box.
This is the most accurate way to identify the network adapter on the discovered device that
you are conguring.
6. Congure naming settings as follows:
For network interface Control TeamSetting...
The device host name. Required.Interface Name
Not recommendedSet To Default
Allowed, if applicable to the network. The DNS sufx is added to the
interface name.
DNS Sufx
Not allowedAliases
Unselected is required. Since not selected, the default behavior occurs, which
is to use the device host name in the hosts le.
Use Interface
Name/Aliases in
Host Files
For any network interface of type iSCSISetting...
"Unused" is recommended. Displaying this text here serves as an aid in
understanding SAN networks.The iSCSI network has no name resolution
via the hosts le or otherwise, so the text you enter here is not actually use
for name resolution.
Interface Name
Not recommendedSet To Default
Not allowedDNS Sufx
Not allowedAliases
Selected is recommended. Since this interface’s network has its names
excluded from the hosts le, this setting has no affect. The interface name
is excluded from the hosts le, regardless of settings here.
Use Interface
Name/Aliases in
Host Files
NOTE: There is no FTP/streaming network for a SAN K2 client. On the K2 SAN,
FTP/streaming goes to the K2 Media Server.
7. Evaluate settings on the Planned tab and change if necessary.
• Compare settings on the Planned tab with settings on the Current tab.
• If you want to keep the current settings as reported in the Current tab, click Remove to remove
the planned settings.
• Do not specify multiple IP addresses for the same interface. Do not use the Add button.
2013 07 20 K2 Installation and Service Manual 91
Planning and implementing a K2 SAN with SiteCong