PDF(41.6 KB) View with Adobe Reader on a variety of devices
ePub(72.9 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(66.9 KB) View on Kindle device or Kindle app on multiple devices
Updated:February 21, 2018
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The information in this document was created from the devices in a specific lab environment. All of the devices in this document started with a cleared (default) configuration following the solution specific Cisco internal installation guidelines. If your solution is live, make sure that you understand the potential impact of any command.
The SAP HANA Scale-Out solutions are configured with two management servers. The management server enables the solution for PXE boot. The second management server exists for fault-tolerance reasons in order to avoid the situation where the servers cannot boot at all in case off the first management server is not available.
Note: Once the HANA server is up and runs well, the management servers can be rebooted without any influence on the HANA servers.
The management server acts as Dynamic Host Configuration Protocol (DHCP) and Trivial File Transfer Protocol (TFTP) server.
The EMC VNX storage acts as Network File System (NFS) server in this solution and provides the nfsroot file system for each server.
The boot process runs through these steps:
The HANA server powers up and does hardware self-checks.
It sends a DHCP request via network interface eth0 (vlan 127) to the management server.
The management server provides the Server IP address and the tftp server IP address.
In the next step, it serves out the kernel and initrd from the tftpboot directory that is build at installation time.
The HANA server loads the kernel and initrd from the tftp server including all necessary drivers available in initrd.
Once loaded the HANA server mounts the nfsroot volume via network interface eth0 (vlan 127).
Finally, the HANA server runs through the default Linux init process to complete the startup.
At the time of the PXE boot process of the UCS servers, the Linux init process stops for approximately 8 minutes when the network interfaces are activated. Afterwards, the startup process continues without any further issues.
When the HANA server runs through the default Linux init process, it reads the network configuration files as well and re-activates the network interfaces. The reason is the boot option onboot is set to yes by default. This means the HANA server sends an additional DHCP request to the management server and loses the file handler for the nfsroot volume at the same time which stops the init process to continue.
There are no error messages visible in the console. In case you enter the boot options debug initcall_debug, you notice the NFS server stopped to respond for approximately 8 minutes with this log message generated. An example of the error message "nfs: server 192.168.127.11 not responding, still trying" in the boot log information.
Change the configuration file /etc/sysconfig/network/ifcfg-eth0 and add the option ONBOOT='no'.