AIX hostid and IP address
Michael MASCHEK
Has anybody encountered a problem with the AIX hostid after changing
the IP address and rebooting the machine ?
If yes, I would be delighted to know why is this changing happen ?
Michael
Simon Travaglia
: Hi,
: Has anybody encountered a problem with the AIX hostid after changing
: the IP address and rebooting the machine ?
: If yes, I would be delighted to know why is this changing happen ?
How did you change it? With smit, or by editing the files direct?
If you edited the files direct, make the changes thru smit and reboot.
Editing the fiels can cause all sorts of problems, one of the quickest
to notice is the failure/misbehaviour of cde...
Simon Travaglia, (s...@waikato.ac.nz) Unix Systems Administrator,
University of Waikato, Private Bag 3105, Hamilton, New Zealand..
Willis B. Boyce
: Hi,
: Has anybody encountered a problem with the AIX hostid after changing
: the IP address and rebooting the machine ?
: If yes, I would be delighted to know why is this changing happen ?
Michael,
AIX sets the hostid from the IP address in /etc/rc.net when you boot up.
You'll have to change /etc/rc.net or reset the hostid later in the boot
sequence.
--
Support the Blue Ribbon Campaign for free speech online ()
http://www.eff.org/BlueRibbon/bluehtml.html /\
Tom F. Randall
>
> Michael MASCHEK (10061...@compuserve.com) wrote:
> : Hi,
>
> : Has anybody encountered a problem with the AIX hostid after changing
> : the IP address and rebooting the machine ?
>
> : If yes, I would be delighted to know why is this changing happen ?
>
> If you edited the files direct, make the changes thru smit and reboot.
> Editing the fiels can cause all sorts of problems, one of the quickest
> to notice is the failure/misbehaviour of cde...
>
> Simon Travaglia, (s...@waikato.ac.nz) Unix Systems Administrator,
> University of Waikato, Private Bag 3105, Hamilton, New Zealand..
I concur with Simon. If this is AIX 4.1.4, this feature drives me
nuts. I like editing the files directly, and it would consistently
change things back to some default, like the install file. I used smit
to make changes, and all seems well now. The workaround where one
changes the corresponding install file usually put into one of the
directories called inst_root located throughout the system, at times
produces very bad results and sometimes works.
This arises the question of /etc/rc. Have you been able to modify
this file and been able to successfully reboot?
--
---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---
Tom F. Randall Internet: tran...@slomms.facsrv.calpoly.edu
Facility Services _---_ VM Sites: DU196 AT CALPOLY
Cal Poly State University |OvO| Telephone: (805) 756-2321
San Luis Obispo, CA 93407 /|w w|\ FAX: (805) 756-6114
---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---
Charles Kuhlman
approved, supported way of making O/S level
changes to AIX has been through the command line
or SMIT.
Traditional hacking methods like directly editing
ascii files may or may now work, and the changes
introduced may or may not 'stuck', and the changed
introduced may (or may not!) produce the desired
effect.
4.1.xx is more so in this regard than 3.2.xx ever
was.
Those who are serious about using and managing AIX
take this for granted instead of fighting and
complaining. AIX is not going to change, the ODM
is here to stay, like it or not.
You have to measure and place a value on sysadmins
time. Would you rather get the task done quickly,
accurately, and completely (the FIRST time!) or
would you like to play and hack and never quite
get it right no matter what you try.
Charles Kuhlman
approved, supported way of making O/S level
changes to AIX has been through the command line
or SMIT.
Traditional hacking methods like directly editing
ascii files may or may now work, and the changes
introduced may or may not 'stick', and the changed
Bob Larson
Charles Kuhlman <ckuh...@ultranet.com> wrote:
>You have to measure and place a value on sysadmins
>time. Would you rather get the task done quickly,
>accurately, and completely (the FIRST time!) or
>would you like to play and hack and never quite
>get it right no matter what you try.
Most of us prefer to get it done quickly, accuratly, and completly the
first time. That's why we prefer editing configuration files to
incomplete poorly designed gui's and badly documented non-standard
command line interfaces.
While IBM is better than most vendors in getting their gui working, it
doens't always and there are stupid limitations built in. Some of the
command line interfaces are better and more powerfull, but even they
don't always work, and the documentation is frequently incomplete.
(IBM is much worse than most vendors in reinventing the wheel with its
command line interfaces.)
I've found no good reason for ODM. There are pleanty of bad ones:
Reduce system reliablity.
Make system difficult to administer.
Lock users into propritary systems.
--
Bob Larson (blars) work: bla...@usc.edu home: bla...@blars.la.ca.us
www: http://sundry.hsc.usc.edu/blars.html
It [the Internet] scares any sane person. -- Erik Fair
It scares a few of the rest of us too. -- Dave Crocker