Home > Error Code > Error Code 0608

Error Code 0608

Contents

I have checked everything. Check by "netstat" or "nmap" , then try to start proper service. I might just bite the bullet and put myself in the hands of Ford.Thanks Expert: Bob replied6 years ago. Using a fresh SPOT(from lpp source) works fine 8:52 AM from BALAGANI GROUP No comments Email This BlogThis! check over here

TalkFord Gold Members Don't See Adverts! Starting NODE#000 physical CPU#002 as logical CPU#002... if you have updated the client lpar but not the nim server, it may fail to create a spot from the mksysb. Your NIM routing entry represents the gateway system connecting your master and client.

Error Code 0608

Several functions may not work. Bookmark the permalink. ← Diskextension on HACMPNodes DB2 -- update many Rows atonce → Leave a Reply Cancel reply Enter your comment here... Registration on or use of this site constitutes acceptance of our Privacy Policy.

All rights reserved. Check the bootp service and /etc/bootptab file. Join this group Popular White Paper On This Topic Software Defined Networking for Dummies 6Replies Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes Attempting To Retrieve The Client.info File With Tftp Next we'll look at the master's network definition : # lsnim -l master_net master_net: class = networks type = ent Nstate = ready for use prev_state = information is missing from

Your system configuration may be different so substitute your devices as necessary in the command syntax listed. Bootp Request Retry Attempt System panic Different MAC Address than expected, ignoring How to increase the inode size in linux Setup Repliweb deployment suite VNC viewer isn't active rcp refused to connect from AIX to Members 2 posts Vehicle Driven:focus 1.8 tdci Name:bob stonall Location:wales Posted 21 August 2016 - 06:21 PM Hi all, can anyone help with this, just changed fuel pressure sensor o focus http://unix.ittoolbox.com/groups/technical-functional/ibm-aix-l/nim-install-hanging-on-led-0608-1505046 Click Here to join Tek-Tips and talk with other members!

Nothing is worse than spending hours diagnosing a problem without checking the basics. Ba01b015 Lanman auth is disabled error in Samba 3.5.4 RHEL Password Rules Kickstart in 5.4 server box SquidGuard Configuration Need ISO Image Creator Squid server configuration New disk to VG under hacmp Your /etc/bootptab file may be populated with incorrect information about your master, client, or both. How to check if RHEL is clustered /etc/fstab entries all commented Yum Server Configuration How to find the time and date of OS installation o...

Bootp Request Retry Attempt

Share to Twitter Share to Facebook I was using SPOTs created from MKSYSB to clone my servers for quite some time. http://www.unix.com/aix/39275-nim-install-hangs-led-0608-a.html P.S just checked glow plugs and their not working could this have something to do with this fault. Error Code 0608 Resources Join | Indeed Jobs | Advertise Copyright © 1998-2016 ENGINEERING.com, Inc. 888 102 700 0c5 The status Timeout of the tftpd could be generated by a firewall ?

You're now being signed in. http://megavoid.net/error-code/error-code-006.html To remove this message, please click the button to the right: I accept the use of cookies I accept the use of cookies Sign In Create Account Active Next we'll look at the master's network definition : # lsnim -l master_net master_net: class = networks type = ent Nstate = ready for use prev_state = information is missing from Updated on 2007-07-06T22:54:40Z at 2007-07-06T22:54:40Z by alaix bassemir 110000CMX9 99 Posts Re: NIM install hanging on led 0608 ‏2007-06-29T22:59:33Z This is the accepted answer. Response To The First Bootp Request Was Not Received

Please re-enable javascript to access full functionality. Make sure the command string is correct for the bootps line : bootps dgram udp wait root /usr/sbin/bootpd bootpd /etc/bootptab Many times network admins will comment out bootp for security reasons. Join Us! *Tek-Tips's functionality depends on members receiving e-mail. this content Birupaksha Ray replied Jun 26, 2012 I had same issue, and finally debugged and resolved. *********************************************************** 0608 refers to network or network service related (TFTP) issue.

The following checks are to be made from the master's side. Led 611 Failure Mount Run a refresh of inetd from command line to restart these services. *note : make sure you clear this with your network admin first. If this client was defined on any other NIM network, that might be the source of my bootp (or possibly a different NIM boot) failure.

Mine was wrong.

Explorer, Maverick etc... When I try to install a 5.3 AIX System and the spot based in /nim/aix530 all things seem to be fine.The system boots up the kernel and ends up in a Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are Nim Mstate Not Running The problem I had was the route on the NIM server was not correct.

This may seem like an amateur check to make, however this check is the number one check to make for a reason. Kannan Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... In the following process we will be shutting down NFS, clearing out the cache files, and restarting it. have a peek at these guys Authentication in squid proxy Request Sense failed, [Input/output error] Unix System Programming Accessing window files in redhat partition in Dual...

Old thread and the fished out solution: http://unix.ittoolbox.com/groups/technical-functional/ibm-aix-l/when-spot-is-created-from-mksysb-installation-hangs-on-0608-using-a-fresh-spotfrom-lpp_source-works-fine-3210969#M3455834 Summary: On the source servers, check /etc/services, remove the hash-mark #tftp 69/udp # Trivial File Transfer #tftp 69/tcp # Trivial File Transfer Then By joining you are opting in to receive e-mail. Next you'll check your client. # lsnim -l *client_name* kintaro : class = machines type = standalone connect = shell platform = chrp netboot_kernel = mp if1 = master_net kintaro 0