
50Chapter 2: EIU messaging protocols
has an Ethernet card). Such nodes have to be on the same subnet as the CM to be configured through the BOOTP server on the CM, except if the maximum hops count accepted by the server is increased.
File transfer protocol
File transfer protocol has been implemented on all the
FTP implementation contains client as well as server software. The client software lets the user application connect to a remote FTP server. The server can be on any node within the SuperNode switch or a node external to the SuperNode switch. The communication with the external node is through the EIU. At least one EIU must be
An FTP client has been implemented for launching manual FTP client sessions from any
> ftp ‘<nnn.nnn.nnn.nnn>’ [x]
where
nnn.nnn.nnn.nnnis the IP address of the FTP server
x | x is an optional port number |
Observe that the IP address is enclosed within single quotes. For manual FTP, a path name in lower case must be enclosed within single quotes. If the path name is not enclosed within quotes and starts with a slash character(/), the path name must be prefixed by a colon character (:). These restrictions are specific to SuperNode CI.
There are three separate file systems supported by FTP:
•SFDEV (on all nodes)
•SLM volumes on CM
Also, access to the IOC is available. SLM volumes and SFDEV are record- oriented file systems, whereas FTFS volumes are
For example, LOAD68K files require