Topic
1 reply Latest Post - ‏2014-07-04T20:25:19Z by shiv tiwari
dboman
dboman
1 Post
ACCEPTED ANSWER

Pinned topic VIOS installation from HMC

‏2012-01-10T13:31:17Z |
Hi

I'm trying to install the VIOS Server from the HMC, but it has stopped on the 0608 code (+Explanation: Attempting to retrieve the client.info file with tftp. Note: Note that a flashing 608 indicates multiple attempt(s) to retrieve the client_info file are occurring.+)

In the log below things have been replaced.
xxx = is always the same everywhere
yyy = is always the same everywhere
zzz = is always the same everywhere
hostname = is always the same everywhere
domain = is always the same everywhere


End of Separately licensed code for rpm V3.0.5, cdrtools
V1.9-------------------------------------

Do you accept the license agreement? y/n: y
Starting RPC portmap daemon done
Starting kernel based NFS server done
nimol_config MESSAGE: Added "REMOTE_ACCESS_METHOD /usr/bin/rsh" to the file "/etc/nimol.conf"
nimol_config MESSAGE: Created /tftpboot.
nimol_config MESSAGE: Removed "disable = yes" from the file "/etc/xinetd.d/tftp"
nimol_config MESSAGE: Added "disable = no" to the file "/etc/xinetd.d/tftp"
Shutting down xinetd: done
Starting INET services. (xinetd) done
nimol_config MESSAGE: Removed "SYSLOGD_PARAMS=" from the file "/etc/sysconfig/syslog"
nimol_config MESSAGE: Added "SYSLOGD_PARAMS=-r " to the file "/etc/sysconfig/syslog"
nimol_config MESSAGE: Removed "local2,local3.* -/var/log/localmessages" from the file "/etc/syslog.conf"
nimol_config MESSAGE: Added "local3.* -/var/log/localmessages" to the file "/etc/syslog.conf"
nimol_config MESSAGE: Added "local2.* /var/log/nimol.log" to the file "/etc/syslog.conf"
rm: rm outside of $HOME or /tmp has been restricted
Shutting down syslog services done
Starting syslog services done
nimol_config MESSAGE: Executed /usr/sbin/nimol_bootreplyd -l -d -f /etc/nimoltab -s 192.168.202.14.
nimol_config MESSAGE: Successfully configured NIMOL.
nimol_config MESSAGE: target directory: /extra/default1
nimol_config MESSAGE: source directory: /media/cdrom/nimol/ioserver_res
nimol_config MESSAGE: Copying /media/cdrom/nimol/ioserver_res/booti.chrp.mp.ent.Z to /extra/default1...
nimol_config MESSAGE: Copying /media/cdrom/nimol/ioserver_res/ispot.tar.Z to /extra/default1...
/bin/tar: ./SPOT/usr/lpp/bos/inst_root/proc: implausibly old time stamp 1970-01-01 02:00:00
nimol_config MESSAGE: Copying /media/cdrom/nimol/ioserver_res/mksysb to /extra/default1/mksysb...
nimol_config MESSAGE: Copying /media/cdrom/nimol/ioserver_res/bosinst.data to /extra/default1/bosinst.data...
nimol_config MESSAGE: Added "/extra/default1 *(rw,insecure,no_root_squash)" to the file "/etc/exports"
nimol_config MESSAGE: Successfully created "default1".
nimol_install MESSAGE: The hostname "hostname.domain" will be used.
nimol_install MESSAGE: Added "CLIENT hostname.domain" to the file "/etc/nimol.conf"
nimol_install MESSAGE: Added "hostname:ip=xxx.yyy.zzz.20:ht=ethernet:gw=xxx.yyy.zzz.1:sm=255.255.255.0: bsaprdvio101.crosskey.fi:sa=xxx.yyy.zzz.14:ha=e41f13fb5c11" to the file "/etc/nimoltab"
nimol_install MESSAGE: Executed kill -HUP 30466.
nimol_install MESSAGE: Created /tftpboot/hostname.domain.
nimol_install MESSAGE: Executed /sbin/arp -s hostname.domain e4:1f:13:fb:5c:11 -i eth0.
nimol_install MESSAGE: Executed /usr/sbin/iptables -I INPUT 1 -s hostname.domain -j ACCEPT.
nimol_install MESSAGE: Created /extra/default1/scripts/hostname.domain.script.
nimol_install MESSAGE: Created /tftpboot/hostname.domain.info.
nimol_install MESSAGE: Successfully setup hostname.domain for a NIMOL install
  1. Connecting to hostname
  2. Connected
  3. Checking for power off.
  4. Power off complete.
  5. Power on hostname to Open Firmware.
  6. Power on complete.
  7. Client IP address is xxx.yyy.zzz.20.
  8. Server IP address is xxx.yyy.zzz.14.
  9. Gateway IP address is xxx.yyy.zzz.1.
  10. Subnetmask IP address is 255.255.255.0.
  11. Getting adapter location codes.
  12. /pci@80000002000020c/pci@0/pci@2/ethernet@0 ping successful.
  13. Network booting install adapter.
  14. bootp sent over network.
  15. Network boot proceeding, lpar_netboot is exiting.
  16. Finished.
This is where it ended in the console windows that I have conncected to the HMC.
And in the web interface the VIOS server is stuck on ref.code 0608.

Is there anyone that knows why?
Is this a step that will take a very long time?

Thanks in advance.
  • shiv tiwari
    shiv tiwari
    1 Post
    ACCEPTED ANSWER

    Re: VIOS installation from HMC

    ‏2014-07-04T20:25:19Z  in response to dboman

    Hi,

    I am also facing same issue.

    @dboman; have you found the solution ?