Sponsored Content
Operating Systems AIX NIM install hangs on LED 0608 Post 302124336 by touny on Friday 29th of June 2007 05:57:59 PM
Old 06-29-2007
Hi

I have checked the /etc/bootptab file and is correct.
I have checked the /tftpboot and is correct.
I have rechecked the network used by the client and is correctly defined.
Everything is exported properly. I have done another installation to another client in the same subnet of the nim master and it works well.

The client has all the resources allocated to be installed.
Cstate = BOS installation has been enabled
prev_state = ready for a NIM operation


I have put the tftpd on verbose mode and have this on syslog.log:

Jun 30 08:10:33 myservernim daemon:info tftpd[4694168]: [00000108] EZZ7044I : mytestmachine RRQ <file=Received , mode=/tftpboot/mytestmachine.info, recognized options: octet>
Jun 30 08:10:33 myservernim daemon:info tftpd[4694168]: [00000108] EZZ7029I : Status Read request for mytestmachine : /tftpboot/mytestmachine .info
Jun 30 08:10:39 myservernim daemon:err|error tftpd[4694168]: [00000206] EZZ7039I : Status Timeout


The status Timeout of the tftpd could be generated by a firewall ?
Any idea ?

thanks in advance
Cheers
Al.
 

10 More Discussions You Might Find Interesting

1. AIX

Linux install from NIM

Has anyone ever done this and is it easy to do with SLES9/10? All I can find so far is this link http://www-941.ibm.com/collaboration/wiki/display/Wikip5/16Jan07+Using+NIM+to+Install+VIO+and+Linux Can you still use all the feature of autoyast etc? TIA. (1 Reply)
Discussion started by: backslash
1 Replies

2. AIX

AIX 5.1 install bos.sysmgt.nim.master failed

I was trying to install bos.sysmgt.nim.master on AIX 5.1 with a mounted NFS source, but it failed: # installp -agXd /nfs/aix51cd1 bos.sysmgt.nim.master installp: APPLYING software for: bos.sysmgt.nim.master 5.1.0.50 restore: 0511-123 The volume on... (0 Replies)
Discussion started by: ezlee
0 Replies

3. AIX

NIM client installation hangs at 0608

Hi All, I am facing very strange problem. I have created NIM server with 6.1 TL4SP3. I am having SPOT and MKsysb of the same version. I am able to install the client using this spot and mksysb. Now I got the requirement of installing the 5.3 ML11SP3 client. So using the mksysb of 5.3 ML11SP3, I... (3 Replies)
Discussion started by: falgun6666
3 Replies

4. Solaris

Solaris Cluster Install Hangs

Greetings Forumers! I tried installing Solaris Cluster 3.3 today. I should say I tried configuring the Cluster today. The software is already installed on two systems. I am trying to configure a shared filesystem between two 6320 Blades. I selected the "Custom" install because the "Typical"... (2 Replies)
Discussion started by: bluescreen
2 Replies

5. AIX

OS install from NIM fails

Hi Guys, The ping is failing SMS menu on the client to the interface for a network boot from NIM. I checked the cables, they are plugged in and lights are blinking. this is the error i am getting when I am pushing the OS on NIM Command: OK stdout: yes stderr: no ... (2 Replies)
Discussion started by: ithinksgreen
2 Replies

6. Solaris

10_Recommended patches install - hangs!

Got a Solaris 10 05/09 machine recently built. Trying to run installcluster --s10cluster like Ive done loads of times before. On this particular machine, it just sits there, no output on command line. Any ideas what to try to see whats going wrong? (3 Replies)
Discussion started by: paulfoel
3 Replies

7. AIX

NIM - install up-to-date VIOS ?

Hello, Is it possible to install up-to-date vios in one NIM operation ? For example I have vios v2.1 DVD and current vios version is v2.2.1.3(we update to fixpack v2.2.1.1_FP25 and apply service pack 2.2.1.3-FP25-SP01) I know it's possible if we install AIX using NIM - we just update... (0 Replies)
Discussion started by: vilius
0 Replies

8. Red Hat

Install hangs on laptop

I have an older laptop the "management" wants me to use instead of buying something that works. Not an antique but a couple years old. An HP with Turion AMD CPU, ATI video. When I try to install in graphical mode, it hangs after package selection. Doesn't matter whether I select server or... (6 Replies)
Discussion started by: RocketGuy
6 Replies

9. AIX

NIM Restore hangs at the start

Hello Gurus, I have a couple of questions, I'm trying to do a mksysb restore from backup and it has just hung at the start. RS/6000 Firmware Version TCP05287 (c) Copyright IBM Corp. 2000 All rights reserved. -------------------------------------------------------------------------------... (8 Replies)
Discussion started by: elcounto
8 Replies

10. AIX

Install RPM from NIM LPP without smitty

I want to install single RPM from LPP on NIM system without doing it interactively (with single non-interactive command), so I 'got' that command from smitty this way: # smitty nim > Install and Update Software > Install Software Select the LPP_SOURCE containing the install images >... (5 Replies)
Discussion started by: n.i.b
5 Replies
FIREHOL(1)						      General Commands Manual							FIREHOL(1)

NAME
firehol - An easy to use but powerful iptables stateful firewall SYNOPSIS
firehol start|try|stop|restart|condrestart|status|panic|save|debug|helpme firehol configfile [start|debug|try] firehol nothing DESCRIPTION
firehol is an iptables firewall generator producing stateful iptables packet filtering firewalls, on Linux hosts and routers with any num- ber of network interfaces, any number of routes, any number of services served, any number of complexity between variations of the services (including positive and negative expressions). firehol is a language to express firewalling rules, not just a script that produces some kind of a firewall. The goals of firehol are: o Being as easy as possible Independently of the security skills he/she has, firehol allows to create and understand complex firewalls in just a few seconds. The configuration files are very easy to type and read. o Being as secure as possible. By allowing explicitly only the wanted traffic to flow firehol secures your system. firehol produces stateful rules for any service or protocol, in both directions of the firewall. o Being as open as possible. Althoug firehol is pre-configured for a large number of services, you can configure any service you like and firehol will turn it into a client, a server, or a router. o Being as flexible as possible. firehol can be used by end users and guru administrators requiring extremely complex firewalls. firehol configuration files are BASH scripts; you can write in them anything BASH accepts, including variables, pipes, loops, conditions, calls to external programs, run other BASH scripts with firehol directives in them, etc. o Being as simple as possible. firehol is easy to install on any modern Linux system; only one file is required, no compilations involved. Options start Activates the firewall configuration. The configuration is expected to be found in /etc/firehol/firehol.conf. try Activates the firewall, but waits until the user types the word commit. If this word is not typed within 30 seconds, the previous firewall is restored. stop Stops a running iptables firewall by running /etc/init.d/iptables stop. This will allow all traffic to pass unchecked. restart This is an alias for start and is given for compatibility with /etc/init.d/iptables. condrestart Starts the firehol firewall only if it is not already active. It does not detect a modified configuration file, only verifies that firehol has been started in the past and not stopped yet. status Shows the running firewall, as in /sbin/iptables -nxvL | less panic It removes all rules from the running firewall and then it DROPs all traffic on all iptables tables (mangle, nat, filter) and pre- defined chains (PREROUTING, INPUT, FORWARD, OUTPUT, POSTROUTING), thus blocking all IP communication. DROPing is not done by changing the default policy to DROP, but by adding just one rule per table/chain to drop all traffic, because the default iptables scripts sup- plied by many systems (including RedHat 8) do not reset all the chains to ACCEPT when starting (firehol resets them correctly). When activating panic mode, firehol checks for the existance of the SSH_CLIENT shell environment variable (set by SSH). If it find this, then panic mode will allow the established SSH connection specified in this variable to operate. Notice that in order for this to work, you should have su without the minus (-) sign, since su - overwrites the shell variables and therefore the SSH_CLIENT variable is lost. Alternativelly, after the panic argument you can specify an IP address in which case all established connections between this IP address and the host in panic will be allowed. save Start the firewall and then save it using /sbin/iptables-save to /etc/sysconfig/iptables. Since v1.64, this is not implemented using /etc/init.d/iptables save because there is a bug in some versions of iptables-save that save invalid commands (! --uid-owner A is saved as --uid-owner !A) which cannot be restored. firehol fixes this problem (by saving it, and then replacing --uid-owner ! with ! --uid-owner). Note that not all firehol firewalls will work if restored with: /etc/init.d/iptables start because FireHOL handles kernel modules and might have queried RPC servers (used by the NFS service) before starting the firewall. Also, firehol automatically checks current ker- nel configuration for client ports range. If you restore a firewall using the iptables service your firewall may not work as expected. debug Parses the configuration file but instead of activating it, it shows the generated iptables statements. explain Enters an interactive mode where it accepts normal configuration commands and presents the generated iptables commands for each of them, together with some reasoning for its purpose. Additionally, it automatically generates a configuration script based on the suc- cessfull commands given. When in directive mode, firehol has the following special commands: o help Present some help o show Present the generated firehol configuration o quit Exit interactive mode and quit firehol helpme Tries to guess the firehol configuration needed for the current machine. firehol will not stop or alter the running firewall. The con- figuration file is given in the standard output of firehol, thus /etc/init.d/firehol helpme >/tmp/firehol.conf will produce the output in /tmp/firehol.conf. The generated firehol configuration should and must be edited before used on your systems. You are required to take many decisions and the comments of the generated file will instruct you for many of them. configfile A different configuration file. If no other argument is given, the configuration file will be tried (default = try). Otherwise the argument next to the filename can be one of start, debug, try. nothing Presents help about firehol usage. FILES
/etc/firehol/firehol.conf AUTHOR
firehol written by Costa Tsaousis <costa@tsaousis.gr>. Man page written by Marc Brockschmidt <marc@marcbrockschmidt.de>. SEE ALSO
firehol.conf(5), iptables(8), bash(1) 2003-04-30 FIREHOL(1)
All times are GMT -4. The time now is 04:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy