11.3.1 Network planning for the HMC and SE Plan the HMC and SE network connectivity carefully to allow for current and future use. Many  of the IBM Z capabilities benefit from the various network connectivity options that are  available. The following functions, which depend on the HMC connectivity, are available to the  HMC: These examples are shown in Figure 11-9. GLYPH<SM590000> Lightweight Directory Access Protocol (LDAP) support, which can be used for HMC user  authentication GLYPH<SM590000> Network Time Protocol (NTP) client/server support GLYPH<SM590000> RSF through broadband GLYPH<SM590000> HMC access through a remote web browser GLYPH<SM590000> Enablement of the SNMP and CIM$^{1}$ APIs to support automation or management  applications, such as IBM System Director Active Energy Manager (AEM) Figure 11-9 HMC connectivity FTP, FTPS, and SFTP support FTP, FTPS, and SFTP protocols are now supported on HMC/SE environment. All three FTP  protocols require login and password credentials.  FTPS is based on Secure Sockets Layer cryptographic protocol (SSL) and requires  certificates to authenticate servers. SFTP is based on Secure Shell cryptographic protocol  (SSH) and requires SSH keys to authenticate servers. Required certificates and key pairs are  hosted on the z14 HMC Console.  All three protocols are supported for tasks that previously used only FTP. Although several  tasks used only removable media, FTP connections are used with z14 HMC console. The  recommended network topology for HMC, SE, and FTP server is shown in Figure 11-10 on  page 370. 1 CIM support was removed from the HMC with Version 2.14.0. Chapter 11. Hardware Management Console and Support Elements  369