5. Configure naming settings as follows:
For network interface Control ConnectionSetting...
The device host name. Required.Interface Name
Not recommendedSet To Default
Allowed, if applicable to the network. The DNS suffix is added to the
interface name.
DNS Suffix
Not allowedAliases
Unselected is required. Since not selected, the default behavior occurs, which
is to use the device host name in the hosts file.
Use Interface
Name/Aliases in
Host Files
For network interface FTP ConnectionSetting...
The device host name with the "_he0" suffix added is required.Interface Name
Not recommendedSet To Default
Allowed, if applicable to the network. The DNS suffix is added to the
interface name.
DNS Suffix
Not allowedAliases
Selected is requiredUse Interface
Name/Aliases in
Host Files
For any network interface of type iSCSISetting...
The text "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 file or otherwise, so the text you enter here is not
actually use for name resolution.
Interface Name
Not allowedSet To Default
Not allowedDNS Suffix
Not allowedAliases
Selected is recommended. Since this interface’s network has its names
excluded from the hosts file, this setting has no affect. The interface name
is excluded from the hosts file, regardless of settings here.
Use Interface
Name/Aliases in
Host Files
6. 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.
106 K2 SAN Installation and Service Manual 02 February 2012
Planning and implementing a K2 SAN with SiteConfig
To Next Page
Loading...
