Remote logins using netldi specified by port number may fail
Login with gem on remote node may fail when NRS specified port for #netldi, and NetLDI has non-default name
Using the NetLDI's port number instead of a name in the NRS for a remote login avoids the need to add the NetLDI name to the services database for each node.
However, when starting a remote shared page cache and specifying the NetLDI by port rather than by name in the NRS, the NetLDI identifier is not propagated correctly to the remote host. When the remote host contacts the stone's host to create the page server for the remote cache, it uses the default NetLDI name, gs64ldi. If the NetLDI on the stone's host is not running with the name gs64ldi, it cannot connect, and the remote login will fail.
Last updated: 12/16/15