Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1.
2.
Now we need to generate a .toc file for the package. It will be done through following command:
1.
3.
Now package is ready for installation. Well use SMITTY for installation. Go to smitty install. Select Install and Update
Software Update Installed Software to Latest Level (Update All). Here give the path of package directory
(/software/SP2/) and Enter.
Now a questionnaire will appear. Here you MUST select yes for ACCEPT NEW LICNESE AGREEMENT. Else default
values are ok. Now enter and press enter again for confirmation of warning messages. Installation progress will start
appearing until it is finished. Logs can be found in /smit.log
4.
Status
active
Above output shows that xntpd daemon is running and it must be stopped before changing ntp configuration.
root@omnibus1:/etc# stopsrc -s xntpd
5.
This procedure keeps security in mind. The idea is to turn on screen sharing while you need it, and then turn it off when youre done. Also,
the write-ups of Tim Boland and Chris Brewer were very helpful in figuring this out.
a) SSH into your remote OS X machine with an administrators log in and password.
b)) Enable Remote Desktop (a.k.a. Screen Sharing, a.k.a. VNC) with this command:
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -activate configure -access -on -clientopts -setvnclegacy -vnclegacy yes -clientopts -setvncpw -vncpw mypasswd restart -agent -privs all
c)) Login using a VNC client. As I mentioned, TightVNC worked for me; for some reason, RealVNC and UltraVNC didnt. Your password is
mypasswd (see the -vncpw flag in the above command; you can and should change this).
d) When you are done, turn of screen sharing using your SSH session:
6.
1) Obtain the files. Its downloadable here: http://sourceforge.net/projects/openssh-aix/. Or you can find it on the expansion CD. Or the
Linux toolkit for AIX CD.
2) Install. If youre using a CD, follow my directions for installing lsof from here (of course, replace openssh with lsof). Otherwise, I have
some installp examples here.
3) Start your SSH.
AIX61# startsrc -g ssh
4) Edit your /etc/hosts.allow file. Otherwise youll see an error that says this:
ssh_exchange_identification: Connection closed by remote host
5) Test it out.
Linux# ssh AIX61
7.
8.
With some regularity I see questions about how to connect graphic applications to PC's running windows and/or Linux. Read more for
some answers!
The oldest approach is to have an X-server package running. There are various commercial, shareware, and freeware packages
available. I am not going to discuss the packages, only the basic steps needed to get AIX to connect to your X-server package.
Basically, for a single application, the easiest step to take is to export your display. For example, my PC has the address
192.168.129.27 and I am running a X-server package. On AIX I would enter:
$ export DISPLAY=192.168.129.27:0.0
$ aixterm &
This HOWTO describes how to combine two standard AIX technologies that can be used to simplify centralized collection and
distribution of software updates for AIX.
Rather than use SUMA on every system I setup SUMA on separate systems based on their level of AIX - AIX 5.3 and AIX 6.1. As no new
TL or SP are planned for AIX 5.2 and I am phasing AIX 5.2 out I am not using this process for updating the one or two AIX 5.2 systems.
For all others I now use SUMA to collect updates and distribute them to other systems via a software server. And since I like pushing
resources, I have integrated SUMA into my NIM resources. I'll discuss the how and why below.
Step 1: Collecting updates using SUMA
For years I have just downloaded filesets and/or compressed tar files of AIX updates. For a few years there has been an alturnate
solution - SUMA, or Service UpdateManagement Assistant. I liked the fileset approach because I had done it that way since I got
started and try not to change just for the sake of change. SUMA (I kept telling myself) is just another interface.
And then IBM changed the way FixCentral works - and now it was hard to do things the way I was accustommed to. And so SUMA
became more than just another way! SUMA became the way - well, after I finally bit the bullet and took a serious look at SUMA.
Preparation
SUMA is setup using smit. Although you can set it up to be fully automated via cron I continue using it via smit. Automated updates
could be handy for critical fixes but for my goal of centralized update management the focus is on TL (technology level) and and SP
The main screen I am interested in is the Task Defaults - because here I change /usr/sys/inst.images to my preferred location. One of
my "defaults" is to avoid putting anything in /usr whenever possible.
Back at the main screen, choose the Download Updates Now (Easy).
This pretty much takes care of getting the updates. What about applying them?
Step 2: Integrating SUMA downloads into NIM resources
On my NIM server I create a lpp_source that points at /data/suma on the system doing the downloads.
Note - the machine serving the resource is not the master nim server, but a client machine (here x054).
root@nim:[/]lsnim -l lpp_5307_suma
lpp_5307_suma:
class = resources
type = lpp_source
comments = SUMA maintained updates for AIX 5307
arch = power
Rstate = ready for use
prev_state = unavailable for use
location = /data/suma
alloc_count = 0
server = x054
So, on the nim server I can use the update option to push updates to nim clients as well as update the nim master. However, when I
do an update I get a message about Superseded Filesets.
Superseded Fileset Updates
-------------------------Fileset updates listed in this section will not be installed.
Newer updates which supersede (replace) these were selected instead (either by
you or automatically by theinstallation program). Make sure that the
superseding updates listed passed pre-installation verification.
This is a common occurance when you just keep downloading updates. Fortunately, IBM developed a program for AIX to assist NIM
with managing lpp_sources. This program is called lppmgr. You can use this command from the command line, but it is very easy to
use via smit as well.
The fast path is: smit nim_lppmgr
So we choose the lpp_source of interest....
And we get this dialog: Note: by default, it is a preview operation. When you switch that to "Preview-> no" the default action is to
delete the filesets. You can save these in a an alturnate location. In terms of lppmgr command syntax this is a move operation. For
your first time - I suggest performing the preview.