Cisco UCS C460 M4 빠른 시작 매뉴얼 - 페이지 2

{카테고리_이름} Cisco UCS C460 M4에 대한 빠른 시작 매뉴얼을 온라인으로 검색하거나 PDF를 다운로드하세요. Cisco UCS C460 M4 2 페이지. For intel xeon v3 series cpus
Cisco UCS C460 M4에 대해서도 마찬가지입니다: 업그레이드 매뉴얼 (11 페이지)

페이지 인쇄
Cisco UCS C460 M4 빠른 시작 매뉴얼
The EMC VNX storage acts as NFS server in this solution providing the nfsroot file system for
each server.
The boot process runs through the following steps:
1.
The HANA server powers up including hardware self-checks.
2.
It sends a DHCP request via network interface eth0 (vlan 127) to the management server.
3.
The management server provides the Server IP address and the tftp server IP address.
4.
In the next step it serves out the kernel and initrd from the tftpboot directory that is build at
installation time.
5.
The HANA server loads the kernel and initrd from the tftpserver including all necessary
drivers available in initrd.
6.
Once loaded the HANA server mounts the nfsroot volume via network interface eth0 (vlan
127).
7.
Finally, the HANA server runs through the default Linux init process to complete the startup.
Problem
During 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 lose the file handler for the nfsroot volume at the same
time which stops the init process to continue.
There are no error messages visible on the console, but when you enter the boot options "debug
initcall_debug" you will notice the NFS server stops responding for approximately 8 minutes
sending "nfs: server 192.168.127.11 not responding, still trying" when reviewing the boot log
information.
Solution
Change the configuration file /etc/sysconfig/network/ifcfg-eth0 and add the option "ONBOOT='no'".
This is an example of the ifcfg-eth0 file:

Related Information

SUSE Documentation:
SUSE Documentation:
"PXE Booting NFS or iSCSI Roots for a Diskless
"SLES Administration - The Linux Boot
Environment"
Process"