AIX, Linux and POWER Portal

Hardware => RS/6000 (Power III and earlier) => Topic started by: Leografix on September 03, 2008, 02:11:10 PM

Title: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on September 03, 2008, 02:11:10 PM
Hello everybody.

Before asking some questions I would like to introduce myself a bit more to rootvg. First of all I?m no native speaker, so please excuse any humble or misunderstandable expression. I will try to do my very best!
I?m a freelance journalist and besides my profession a collector of unusual or rare computing hardware. My background on operating systems is based somewhere in the early days of the Spectrum ZX, later the Ataris and some Amigas but in deep I?m clearly located in the old Mac OS. Mac OS X in special and UNIX in general is still somewhat "uncomfortable" to me when Terminal-related actions are asked or in other words: I?m no UNIX freak. But as a collector I?m now facing UNIX in a very "uncomfortable" way: AIX 4.1.4. I know that this distribution is very old but as long as there is nearly no information available anymore about AIX for older computers I?m contacting any source in order to find some help - that?s why I?m here, now ;-)

Some days ago I was very lucky in getting myself an old Apple Network Server 500/132 (not to be mixed up with "Apple Workgroup Server" or "A/UX Macs"). This old box formerly was managed by two AIX versions: AIX 4.1.4 and later on a 4.1.5 update / upgrade. Other Versions besides the already mentioned ones could NOT be used on that machine, just Yellow Dog Linux 3 and 4 can be used with that strange server. As long as I would like to use that server with the original AIX OS lots of questions are rising...

I already managed to install 4.1.4 on that box facing lots of incompatibilites with original Apple hardware or compatible hardware that is usable in regular Macs. Ok, this is not a catastrophy. What really annoys me is the handling of AIX. It took me nearly 30 minutes to get my display resolution and refresh changed. Now You might have an impression how things look like ;-) While messing around with AIX a bit more I stumbled over the network settings...

Is there any documentation out there available describing the configuration of network settings within AIX in an understandable way? Doesn?t matter if written in English or German.

I?m looking for the Update / Upgrade 4.1.5 Apple once provided for download. I don?t know if the IBM update and the Apple update are the same (in fact the Apple AIX just contained some Apple-specific drivers and some utilities for a Mac OS based computer), so I don?t know if I could use an IBM update - if only one would be available. Can anybody in here help me with these files? The Apple update is preferred...

I?m wondering if there is any possibility to get PHP, MySQL and PHPMyAdmin installed on AIX 4.1.4, furthermore I?m unsure what Apache version can be used with that AIX version.

As You can see I?m pretty lost with that old OS... So any help or information is highly appreciated! Thanks in advance and kind regards from Switzerland

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: John R Peck on September 04, 2008, 02:01:52 AM
J,

Well I bet I hold the record for most judicious museum archiving of AIX  ;)
I still have working 3.2.5, 4.3.3 and 5.1 systems, all of which will run a very old version of NCSA web server I think it is called
- doesn't do name-based hosting, can't remember if it did SSL (I think not) and is very simple.  Don't know if other
versions of Apache proper would work with 4.1.4/5 (which I don't think I ever used for very long - bit of a bug-fest as I recall), but Michael has some experience of compiling Apache on various AIX levels and it might work - those old libraries are going to be a problem I suspect.

For network settings, "smit mktcpip", you shouldn't need to mess with "no" settings or other layers of it to get it working.

However, instead of bothering with all the rotten Apples,  ::)
I recommend you go on eBay or contact a local second hand pSeries seller
and get a proper IBM AIX machine, e.g. a 43P-150 or p505:
- the former is very cheap now, will take you up to 5.3 and is much nicer to work with, rather PC-like,
- the later is ideal to play with LPARs and much dearer but my favourite design of machine (intended for a rack, 1U).
Then you can have a really nice Apache server on it, just like this one.

If any of our other readers would like to plan ahead for Christmas,
ROOTVG would very much like a p505 to play with if
anyone out there happens to be giving one away.
  :)
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on September 06, 2008, 07:52:15 AM
A year earlier and I would have still had the CD's for you - at least to copy from. But I cleaned out my basement.

As far as setting up network, display, etc.. there are some new features, but the basic steps have not change from AIX 3.2.5 for tcpip. Although in those days there was more 'need' for a bsd way of doing things - which is still in AIX 6.1 I believe (the switch to bsd way).

basically, use 'smitty mktcpip' and fill in the dialog.

for your display, 'smitty devices' and look for the correct family of devices (display adapters).

I'll look into getting AIX 4.3.3 documentation - I think I still have that here somewhere - but you could just refer to the AIX 5.1 documentation for the more basic info. I have a link on the home page. What also might interest you is following the hardware infocenter link.

Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on September 06, 2008, 07:56:55 AM
When looking for end-of-life updates, and other 'hard to find' updates, never complete pacjages, refer to ftp://ftp.boulder.ibm.com/software/server/ (http://ftp://ftp.boulder.ibm.com/software/server/)

Something that might be useful to you is a recent addition - maybe nothing: ftp://ftp.boulder.ibm.com/software/server/duplicatemac/ (http://ftp://ftp.boulder.ibm.com/software/server/duplicatemac/)
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on September 21, 2008, 08:17:58 AM
Well, I got a bit further in my quest...

For some odd reason Apple still mentions within an online cocument, that the 4.1.5 Upgrade (which turns out to be a full install) is available from IBM - IBM in return states the 4.1.5 AIX as "not available and unsupported". So in other words: if I can?t find a copy of 4.1.5 I will have to get along with 4.1.4 - which is quite annoying as this AIX doesn?t support some hardware I really need. In addition the old Mac OS utilities are not available anymore, too, so configuration of volumes will take place within AIX only. Those utilities were installed on regular Macs in order to obtain a terminal connection and a disk management utility.

What really annoys me is that hardware compatibility thing. I got myself several PCI Ethernet cards which sometimes refuse to work. When installing a fresh BOS the server recognizes some but only when installed in the upper three PCI slots. Installing these cards after installing the BOS does not work. The strangest thing: the IBM Ethernet card from 1995 does not work in any way...

Now, as I?m still pretty confused with that AIX my major interest is how to determine the MAC adress of a network adapter. Is there a terminal command / smitty input that could deliver such information?

Thanks in advance once again.

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on September 21, 2008, 05:23:58 PM
The easy part: seeing the MAC address:

michael@x054:[/home/michael]netstat -i
Name  Mtu   Network     Address            Ipkts Ierrs    Opkts Oerrs  Coll
en0   1500  link#2      0.9.6b.3e.46.ff    9994565     0  5552487     0     0
en0   1500  192.168.129 x054               9994565     0  5552487     0     0
lo0   16896 link#1                           25026     0    25395     0     0
lo0   16896 127         loopback             25026     0    25395     0     0
lo0   16896 ::1                              25026     0    25395     0     0


My MAC address is: 0x00096b3e46ff (link # line).

Regarding hardware issues: IBM was always very specific about hardware specificatins. Cards not built to "standards" generally failed in an IBM box - even PC's. In the early days of PCI, and especially the ISA interfaces lots of settings had to be set or modified while in the BIOS setup programs. This could explain why cards can be seen/installed at original install, but not afterwards.

However, if you know the real hardware values, you can modify them, and then re-run cfgmgr and/or reboot to activate a card.

On this box: running AIX 4.3.3 I list the addapters: then I examine the two cards. The type is actually seen as the same by AIX, but from the location codes I know one is on the motherboard (integrated) the other is a card (in a PCI slot).

$ su
root's Password:
# lsdev -Cc adapter
sa0    Available 01-C0 Standard I/O Serial Port 1
sa1    Available 01-D0 Standard I/O Serial Port 2
sioka0 Available 01-F0 Keyboard Adapter
sioma0 Available 01-G0 Mouse Adapter
fda0   Available 01-H0 Standard I/O Diskette Adapter
pmc0   Available 01-I0 Power Management Controller
scsi0  Available 04-C0 Wide SCSI I/O Controller
siota0 Available 01-A0 Tablet Adapter
ppa0   Available 01-B0 Standard I/O Parallel Port Adapter
paud0  Available 01-E0 Ultimedia Integrated Audio
ent0   Available 04-B0 IBM PCI Ethernet Adapter (22100020)
ent1   Available 04-02 IBM PCI Ethernet Adapter (22100020)


# lsattr -EHl ent0
attribute     value          description                       user_settable

busio         0x1000100      Bus I/O address                   False
busintr       6              Bus interrupt level               False
intr_priority 3              Interrupt priority                False
tx_que_size   64             TRANSMIT queue size               True
rx_que_size   32             RECEIVE queue size                True
full_duplex   no             Full duplex                       True
use_alt_addr  no             Enable ALTERNATE ETHERNET address True
alt_addr      0x000000000000 ALTERNATE ETHERNET address        True
# lsattr -EHl ent1
attribute     value          description                       user_settable

busio         0x1000120      Bus I/O address                   False
busintr       2              Bus interrupt level               False
intr_priority 3              Interrupt priority                False
tx_que_size   64             TRANSMIT queue size               True
rx_que_size   32             RECEIVE queue size                True
full_duplex   no             Full duplex                       True
use_alt_addr  no             Enable ALTERNATE ETHERNET address True
alt_addr      0x000000000000 ALTERNATE ETHERNET address        True
#



The important values are the ones with the user_settable attribute False. This means that AIX cannot change the value - it is determined by the hardware. For Most PCI/ISA adapters these are bus_io address, interrupt number (busintr) and interrupt priority (intr_priority).

On you system, compare the values that you can read while in the BIOS, or hardware setup programs, and the settings listed. By the way, your card drivers might say True for user_settable, but actually, this means that you can change the setting for the driver, not really change the card settings from AIX.

Probably, this will be a requirement to have any success as when I try to change one of these settings, I get, as is to be expected, an error message.

# chdev -l ent1 -a busintr=3 -P
Method error (/usr/lib/methods/chgent):
        0514-018 The values specified for the following attributes
                 are not valid:
     busintr     Bus interrupt level



As you can see, the command to change a setting is in the form:

# chdev -l device_name -a attr_name=new_value

For example, chdev -l ent0 -a rx_que_size=64 [-P]

The -P argument is to make a change in the settings database (ODM) but not change an active device. It will take effect after the device either goes to Defined state (rmdev -l dev_name) and then gets activated again (cfgmgr, or mkdev -l device_name), or after a reboot if the device cannot be offlined.





Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on September 22, 2008, 06:39:05 AM
Thanks a lot Michael for providing such valuable information. I hope You don't mind my requests, AIX is very new to me and has nothing in common with the operating systems I knew until now.

In the meantime I got a step further. I already found out that a "regular" IBM AIX 4.1.5 Install will not work on my box, it has to be that update from Apple that is lost by now - no need to mention that IBM's support in this case was much better than Apple's constant refuse to give any reply at all. So I am damned to stick to 4.1.4. This reduces my options a bit more: no 100 mbps as far as I can see. The odd thing about this: the Apple 10/100 TX card is "defined"  but not "availble".

I've been experimenting a bit more with that box. I already managed to copy all installation files of the CD to the much faster hard disk and making a DDS-2 and a DLT tape backup from all this - just in case my experiments should end up within a desaster. In addition I added two more disks to the rootvg, expanding the file system. We, might be small steps in Your eyes but to me it's some sort of "first contact".

Still in need of further support and information I hope I'm not annoying the audience too much...

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on September 22, 2008, 08:54:21 PM
Defined means IBM recognizes it as a card, but cannot make it available - i.e. talk with it.

please provide the output of the command:

# lsattr -El ent0 (assuming your card is ent0 that is defined - otherwise change the 0 for the correct #).

And, just in case you thought so - rootvg.net is not IBM. John Peck owns the domain, and I help out as a hobby. google ads and donations keep rootvg.net in the air.

Michael
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: John Peck on September 22, 2008, 09:51:56 PM

"In the air" - is that like something by Howard Hughes :D

Re the audience - personally I'd like more questions like this,
or anything involving shell scripting as the answer,
with less of the VIOS and stuff I cannot abide :-\
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on September 23, 2008, 11:05:57 AM
First of all thanks again!

I knew this domain isn?t bound to IBM - most of valuable information is found outside the major companies, anyway ;-)
@ John: what does VIOS stand for? I?m a classic Mac user, not into deep into commands and stuff alike... I noticed from time to time that asking questions as a complete newbie can annoy an audience pretty fast. I already ordered an AIX 4 book but I didn?t recieve it until now so many questions will be placed here.

But now to the comman line output - the card is ent1 (sorry, no code copy paste, just written by hand):

device_addr: 0xffffffff - Device Address: False
intr_level: 13 - Bus interrupt level: False
intr_priority: 3 - Interrupt priority: False
xmt_que_size: 128 - TRANSMIT queue size: True
rcv_pool_size: 40 - RECIEVE buffer pool size: True
use_alt_addr: no - Enable ALTERNATE ETHERNET address: True
alt_addr: 0x - ALTERNATE ETHERNET address: True
OF_handle: 0x9f52250 - OpenFirmware node handle: False
cfg_addr: 0x - Configuration Space Address: True
full_dpx: auto - Enable Full Duplex Operation: True
xmt_thrs: 0 - Transmit FIFO Threshold: True
capt_fx: no - Enable Capture Effect Avoidance: True

I double-checked my writing...

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: John R Peck on September 23, 2008, 08:40:00 PM

VIOS is where you have a partitioned machine, with multiple operating systems
doing their I/O through one of the partitions that has real resources allocated to it.
This leads to immense over complication, poor performance, but a chance to keep
lots of people in work ::)
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on September 24, 2008, 06:18:37 PM
Ok. quick reply. The address 0xffffffff is probably just a placeholder.

Can you start the machine in BIOS mode and find out what the BIOS says the card is setup as. I assume the card is not hot-pluggable and/or the AIX version you have does not know how to modify the addresses. So I need to know it's addresses, interupt etc..

Once I have those values I can pass a number of commands to manually modify the ODM so the driver gets loaded with the correct (I hope) values.

And I like VIOS - Virtual IO Server - because it keeps me in work. This week I am teaching the course AU78: VIOS Best Practices (as an alternative title - I rarely remember the official one).

And newbs sometimes have the best questions - welcome to rootvg.net!
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on September 25, 2008, 02:19:10 PM
Newbies sometimes ask the best questions - absolutly true! Regarding topics I have some knowledge of I can only testify this statement ;-)

So for now I got a bit further... sort of. I managed to acquire the pure Apple 4.1.5 install CD  :) But it doesn?t solve my problem in some ways. At last I now have german translations in some areas of AIX. Ok, but now to topics:

As far as I know no Apple machine has a "BIOS" but an "Open Firmware" which can be accessed right after booting the machine, so any information stored there surely will look a bit different from what I know of BIOS screens, but I can try if You want to.
Anyway the 100 MBps TX card from Apple still stays "defined" but now I know the type of device the BOS couldn?t "put" into the kernel. When installing the BOS the installer moans about a

device.pci.23100020
devices.pci.pci.1023+2000

As long as I don?t want to outsource Your knowledge too much and fast I thought to myself: "You?ve seen such lines somewhere before" - so I began to roll bookmarks and stumbled over this IBM site:

ftp://ftp.software.ibm.com/aix/fixes/v4/devices/

I scrolled to a line which at least looked a bit like the two lines above but there are many entries that look the same. I decided to download

devices.pci.23100020.diag.4.1.5.1.bff

At least the first three parts look exactly the same, but the "diag", the "4.1.5.1" and the "bff" are different. So I made some brainstorming:

bff = file type extension (?)
4.1.5.1 = version of AIX this driver is supposed to be used within (?)
diag = ????

As far as I understand AIX by now "diag" means some sort of diagnostic routine, so I don?t think this file is actually a driver but something AIX calls "selective fix package". Is it true? The according info file states the same (selective fix package for an IBM PCI 10/100 Mb Et card).
What really annoys me is the fact that a fresh installation of that newly acquired AIX seems (I don?t know exactly) to install a 4.1.5 but not a 4.1.5.1 - so I don?t know if I can use this driver if it is actually a driver that might work.

One supposed to be more simple problem resulting of all this: how do I transfer such a driver? As far as I understood the system by now it should be enough to fill an ISO 9660 CD with all the stuff and drivers needed, throw it into the CD ROM drive and specify that one as source. True?

Another aspect are harddisks. I?ve been exchanging several disks (right now I only can connect one at a time) and installed to see if the server accepts different HD sizes. After shutting down the server via several commands like

shutdown -F
shutdown -h

etc. AIX seems to have some troubles with some drives that worked before. As I don?t know how to format (low-level) a disk I tend to hang them to a Mac and reformat them there (one drive couldn?t get even recognized anymore... 146 GB for the dustbin :( ). Is there a command that can be used in the early boot state to low level format a drive which is stated "unknown to the BOS database"?

Dear, oh dear...

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on September 25, 2008, 02:39:43 PM
In the meantime I already forgot how I copied all files off the CD to the hard disk - to use that hard disk as source for drivers :(

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on September 25, 2008, 04:19:21 PM
I found the way how to copy the files :)

But another update: the BOS identifies the Apple Ethernet Card. It states the 10 MBps functionality as "available" but the 100 MBps functionality only as "defined" - so I suppose it?s just a question of how AIX tries to talk to the right interfaces?

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on September 26, 2008, 12:06:31 PM

So for now I got a bit further... sort of. I managed to acquire the pure Apple 4.1.5 install CD  :) But it doesn?t solve my problem in some ways. At last I now have german translations in some areas of AIX.

Quote
As far as I know no Apple machine has a "BIOS" but an "Open Firmware"

did not know what Apple would call it, but need the values, if possible, that the system says it has. However, we may be able to solve this differently as well.

Try the Apple CD first:
# cfgmgr -i /dev/cd0

This command does a plug and play discovery of devices, and when it finds a device that does not have a driver on system, it checks the installation media (-i) for a driver.
If you get your error message again, try the AIX 4.1.5 disk as well.

To see what is on an IBM media disk use the following command:

# installp -d /dev/cd0 -L

and maybe grep for your device number.

device.pci.23100020
devices.pci.pci.1023+2000

Quote
As long as I don?t want to outsource Your knowledge too much and fast I thought to myself: "You?ve seen such lines somewhere before" - so I began to roll bookmarks and stumbled over this IBM site:

ftp://ftp.software.ibm.com/aix/fixes/v4/devices/

I scrolled to a line which at least looked a bit like the two lines above but there are many entries that look the same. I decided to download

devices.pci.23100020.diag.4.1.5.1.bff

At least the first three parts look exactly the same, but the "diag", the "4.1.5.1" and the "bff" are different.

You came very close:

bff = file type extension (?) -- Backup File Format (as in backup/restore command rather than tar or cpio)
4.1.5.1 = version of AIX this driver is supposed to be used within (?): AIX 4.1.5, patch #1
diag = diagnostics.

More IBM speak now: IBM files sets are delivered as LPP: Licensed Program Packages. LPP are packaged as filesets, and filesets can be bundled. We wont deal with bundles here - just name dropping.

The LPP for this device is: devices.pci.23100020

The filesets are: diag, com, and rte (without looking these are the most common filesets for devices) and then there is the version number as well.

When you use the installp command above to list LPP filesets on media, or in a directory, there are two types: type I and type U (Installable, and Update). Updates only work in combination with an already installed fileset. Installable are installable when it has not been installed before, or it is a higher level the the current version installed. So updates are small by comparison. You can also force an installation (to go backwards, or to reinstall because you doubt the integrity of the installed version).

Quote
As far as I understand AIX by now "diag" means some sort of diagnostic routine, so I don?t think this file is actually a driver but something AIX calls "selective fix package". Is it true?
Yes, a fix for some diagnostics routines, not the driver (in the .com - common, and .rte - run time environment) filesets.

Quote
The according info file states the same (selective fix package for an IBM PCI 10/100 Mb Et card).

What really annoys me is the fact that a fresh installation of that newly acquired AIX seems (I don?t know exactly) to install a 4.1.5 but not a 4.1.5.1 - so I don?t know if I can use this driver if it is actually a driver that might work.

One supposed to be more simple problem resulting of all this: how do I transfer such a driver? As far as I understood the system by now it should be enough to fill an ISO 9660 CD with all the stuff and drivers needed, throw it into the CD ROM drive and specify that one as source. True?

If the driver exists on the media, the cfgmgr command above will install it for you just as if it was a fresh installation.

Quote
Another aspect are harddisks. I?ve been exchanging several disks (right now I only can connect one at a time) and installed to see if the server accepts different HD sizes.

lsdev -Cc disk

will list the disks AIX sees - with a short description of how AIX sees them. NonIBM disks are generally typed as: disk osdisk        scsi  Other SCSI Disk Drive

To get a list of disk types and sizes AIX recognizes use:

lsdev -Pc disk

Quote
After shutting down the server via several commands like

shutdown -F
shutdown -h

I generally use either:

shutdown -Fh #halt system
or
shutdown -Fr #reboot system

the -F option is similar to saying "now" with other versions of UNIX and Linux.
Quote
AIX seems to have some troubles with some drives that worked before.
With the AIX you installed, or with an Apple O/S? Check the list of recognized devices. For an indivudial disk use:

lsattr -EHl hdiskX ## the H argument is optional, for headings

Quote
As I don?t know how to format (low-level) a disk I tend to hang them to a Mac and reformat them there

execute the command:
diag

Go to the third general area: Task Selection
In this area there is an option to format or certify SCSI disks.

Just remember that in the heydays of AIX 4.1.X 4G disks were huge! 320Mbyte and 660Mbyte disks were the standard. Hard to believe!!

Well I hope this takes care of most of your short term issues. I am checking friends of friends for the Apple update.

p.s. I'll look up the command to install the German language filesets - officially, rather than just copying.
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on September 26, 2008, 12:08:56 PM
I found the way how to copy the files :)

But another update: the BOS identifies the Apple Ethernet Card. It states the 10 MBps functionality as "available" but the 100 MBps functionality only as "defined" - so I suppose it?s just a question of how AIX tries to talk to the right interfaces?

J

Please provide the output from command:

# lsdev -Cc adapter
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on October 07, 2008, 07:07:33 AM
An update to keep You informed...

I didn?t get very far until now so further questions / informations will have to wait a bit. In the meantime I got the book which describes AIX 4.1 / 4.3 a bit into deep. This book and some more researches teached me a bit more about my special machine and it?s AIX.

First of all: the ANS is much more close to a RS/6000 system than to a PowerMac 9500 - this explains why lots of Apple hardware won?t work as expected (and in return: much more IBM hardware from this time will work). For example: the Apple 10/100 card will only work with 10 MBps - there is no way to force it to operate in 100 MBps mode. It has to be a 3com for PowerPC systems or several IBM cards. So for now I will have to look out for such a card (got a compatibility list by now <sigh>). The same is for graphics cards.

Now for the AIX versions: AIX 4.1.4 does not contain any other languages than US English. Only option I had is to install the Swiss German keyboard layout which actually works. AIX 4.1.5 contains all other languages so I installed the Swiss German language surroundings. After I?ve noticed that far more informations are only available in English I decided to reinstall AIX 4.1.5 in English language - I can change that later on if the machine is up and running.

For the diag / low-level format thing: As the ANS does not have a BIOS but an OpenFirmware dialog the command "diag" does not exist (who wonders). I have to boot off the CD to get a terminal window and "diag" does exist in this ANS AIX version - but it refuses to format disks larger than 36 GB. In fact AIX destroys drives larger than 36 GB (which killed a 146 GB drive already, not noticable anymore by my macs <sigh again>).

Right now I?m setting up tha ANS again with a clean English AIX 4.1.5 installation (there are absolutely NO 4.1.5.1 packages just 4.1.5.0).

The book is quite helpfull in some aspects but especially the TCP/IP setup confuses me again. Although I already asked for it I still do not understand how to determine the MAC adress of the one 10MBps adapter (SMC, some sort of DEC copy). What do I have to do where to get this information?

Another thought popped up to my head: as I?m dealing with several other old OSses, too I thought about "what about DHCP"? Some older UNIXes like NeXTstep or others do not understand DHCP - but I want to use my D-Link router to provide just one IP address according to the MAC of that adapter. Can this be done? Does AIX get along with such options / settings?

In between I tried to set up AppleTalk within this AIX. As I suppose nobody in here actually uses AppleTalk on their systems I?m pretty sure nobody can help me in here. Just to let You know what I tried in between: exactly following Apple?s guidelines in installing that stack (but without setting up TCP/IP before) the AppleTalk deamon refused to start so I couldn?t use my Macs to contact the ANS at least with AppleTalk.

I know that my way to handle all this is rather unusual and ineffective but I want to understand every single step I?m doing.
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: John Peck on October 07, 2008, 04:49:23 PM
For the MAC address, or other VPD details of adapters, the "lscfg" command should help:
lscfg -vl ent0

 DEVICE            LOCATION          DESCRIPTION                         
                                                                         
 ent0              10-60             IBM 10/100 Mbps Ethernet PCI Adapter
                                     (23100020)                         
                                                                         
       Network Address.............2014BC986EFB      <-- the MAC address                     
       Displayable Message.........PCI Ethernet Adapter (23100020)       
       Device Specific.(YL)........P1/E1                                 

For DHCP at that version of AIX I'm not sure, but from 4.3.3 anyway here's some smit menus:
smit usedhcp  # For your AIX box to use DHCP to get it's IP address with tons of options
smit otherserv  # For three menu options relating to running a DHCP server, client and relay agent
                        to stop and start the relevant SRC services.

For more details, the man pages:
man dhcpsd
man dhcpcd
man dhcprd

For graphical configuration of DHCP, read about this one:
man dhcpsconf

Through all of that I see nothing to suggest that AIX can reserve an IP for a specific MAC at
that AIX level at least.

AIX, and the hardware, has always been very picky about the disks that will work with it.

I recently tried to use a 32GB LVD disk, which was almost identical to a supported IBM one,
taken from a PC RAID array unit going cheap on eBay (thought it might be worth a try at home),
and nothing doing there - at one point it would be seen with garbled lscfg data and then later
with a different connection path it wasn't even detected.  Same thing would happen with
my dear old model 250 machine (about the same time as your Apple) and it's limit of only
1 or 2GB particular disks (amazing now when you can get 8GB on a thumbnail SD card say).
As you have discovered, you must stick to the tested recommended hardware list,
or the results will be uncertain to say the least.  Although in theory, it should be possible
to get anything working if you can do some ODM editing, maybe write your own driver
kernel extension, etc...

One more option for MAC address discovery - if you can ping the IP from another machine,
then on that other machine run "arp -a" you should see the MAC address that has been seen.
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on October 07, 2008, 08:08:34 PM
Quote
Right now I?m setting up tha ANS again with a clean English AIX 4.1.5 installation (there are absolutely NO 4.1.5.1 packages just 4.1.5.0).

With installation media in the drive try:

installp -d /dev/cd0 -L | grep device.pci.2310

With luck there will be a 4.1.5.0 fileset. Once this is installed - you will have the base filesets installed - and now you can use smitty update_all to update the 4.1.5.1 version.

AIX version 4 supports DHCP. If you want it to be a client just use:

# smitty usedhcp

This will make the changes to the config files in /etc and start the dhcpcd demons.
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on October 08, 2008, 06:35:52 AM
With installation media in the drive try:

installp -d /dev/cd0 -L | grep device.pci.2310

Ok, I double-checked my typing (allthough I did not find the "|" key on my swiss german Apple keyboard, I had to copy paste it). When using the command

installp -d /dev/cd0 -L | grep device.pci.2310

while AIX 4.1.5 install CD is in the drive it throws me an 0511-123 The volume on /dev/cd0 is not in backup format followed by a 0503-003 installp: the specified device /dev/cd0 is not a valid device or file error.

As I copied all installation files to my hard drive I re-tried this with the following command:

installp -d /usr/sys/inst.images -L | grep device.pci.2310

After hitting ENTER no error message appears but also no feedback at all. The block cursor just jumps to the next line and blinks. Has it installed something?

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on October 08, 2008, 08:31:24 AM
lscfg -vl ent0

Thanks a lot for this, I?m beginning to understand some command line basics by now. I determined the MAC adresses of the onboard ethernet of the ANS and the MAC adress of the SMC NIcard (a DEC NIC clone I suppose). The MAC adress of the 100 MBit Apple NIC isn?t recognized (who wonders...).

I?m not sure if You understood my DHCP question. I already noticed that AIX can act as a DHCP server (although I still don?t know what to configure where) but this is not what I?m aiming at.
I?m using a D-Link router which acts as a DHCP server providing static IP adresses to all of my machines in accordance to the MAC adress of their NI. I don?t want to set up my ANS as DHCP routing machine, it just has to "get" it?s static IP adresses from the router while every NI in the ANS gets it?s own IP adress (a maximum of 7 possible IP adresses as the ANS has one onboard ethernet port and up to six possible PCI NI ports).

I already reserved my wanted IP adresses within the D-Link router and bound them to the MAC adresses of the ANS. Sorry for being not too exact with my question: is AIX able to "get" the IP adresses provided by the D-Link -> dynamically <- or do I have to configure AIX -> manually <- to self-assign this IP adress? For example NeXTstep 3.3 isn?t able to get IP adresses dynamically (unless you are installing an additional DHCP package NOT from NeXT). If You are not using this package You have to edit Your network settings by hand "reserving" the wanted IP adress inside the NeXTstep OS AND (!) within the used D-Link router.

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on October 08, 2008, 03:04:31 PM
Re: DHCP.

If you have configured your DHCP server to reply with a specific IP address to a specific MAC address then the command:

# smitty usedhcp

will take you into the AIX smit dialog to select the interface (en0, en1, etc) that you want configured via the DHCP client.

Re: installp ... -L - this only lists (L) the software found on installation media. As the first command gave an error, I must be making an error myself. For syntax you might try: installp -? to get the syntax message.

lslpp -L >x; grep 2310 x (rather than the pipe | character) to see if the devices.pci.2310* are installed.

Question: if you run cfgmgr is it still complaining about missing drivers?
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on October 10, 2008, 01:31:27 PM
When running cfgmgr it throws 0514-040 Error initializing a device into the kernel message (Method Error (/usr/lib/methods/cfgde)).

When running lslpp -L >x; grep 2310 x simply nothing happens, just a line break (the "#" now missing) and a blinking block cursor. So I don?t think it installed anything.

In the meantime I was able to "configure" TCP/IP at least a bit. Might be a small step for You but for me it is indeed a very large one! The AIX interfaces are still very confusing to me. So for now a 10MBps line is up on et1 and et0 and I was able to ping these from Mac OS X so this first step is the basis for all following =)

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on October 10, 2008, 05:45:25 PM
et0 and et1!

That is unusual. Seems Apple is using IEEE 802.3 rather than "Xerox Park" protocol.

The OSI layer two (or LAN) devices are entX and the OSI layer three devices are enX and etX.

regarding lslpp -L >x

what does wc x say. Maybe there is no software for you device on the CDROM.

I will try to figure which device is the method cfgde (cfgent is for configuring ent, or ethernet interfaces iirc. So I am looking for a device best described by 'de'.
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on October 11, 2008, 05:31:57 AM
et0 and et1!

That is unusual. Seems Apple is using IEEE 802.3 rather than "Xerox Park" protocol.

The OSI layer two (or LAN) devices are entX and the OSI layer three devices are enX and etX.

Well, I'm not sure about this but it seems to me that any network interface on the ANS runs two protocols at the same time within every single interface adapter. When calling the communication devices from SMIT every interface offers a "et" and an additional "802.3" so it's up to You to choose one.

I've been fiddeling around with that box yesterday quite some time and I discovered several things that appear unusual to me. Regarding networking it took me some time to figure out that one single TCP/IP stack is handling ALL network interfaces at the same time - before I thought there is a single stack for every single interface as the ANS can handle up to seven interfaces at the same time.

Another strange thing which I have to resolve: the ANS utilizes a level 2 cache chip which is - to my surprise - not "configured" after a clean BOS install. I know that AIX notes every single chip and device so I thought as long as this is a "standard" chip from  Apple their version of AIX should have been "installing" it. I didn't notice it from within SMIT but from the early startup diagnostics (didn't know until yesterday that turning the key switch in to service position before boot up it evokes this service diagnostics). Compared to other Macs this machine really lacks in-deep documentation in very essential points.

I also noticed that the ANS can handle a Quantum 40 GB DLT tape drive for backups but - instead of the built-in DDS2 tape drive - it can not rewind the tape for example in  order to boot of that DLT tape and restore the system. When booting off the installation CD the tape can at least be used for OS and system restoration. At any other point the DLT seems to work fine. The DDS2 can boot and install / restore but I don't know how to activate the hardware compression (must be software-driven as this Apple tape DDS doesn't feature jumpers for this option). 4 GB of tape space is not as much as I may need in the future. Thanks to the DLT it uses hardware compression so I'm having the option of 80 GB per tape.

Another odd thing about the ANS: Apple states the tray drives as "automatically terminated and SCSI ID given". While the drives really do get their correct SCSI ID dependig on the drive tray they are in the SCSI chain is not terminated or at least not terminated correctly. You still have to use jupers for that one meaning that several Seagate drives can not be used at the end of the chain because they lack termination by jumper setting.

After all my ANS seems to be very close to an IBM 43p machine - a Pro at least told me that  so I hope this can solve some compatibility questions a bit better.

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on October 11, 2008, 08:27:57 AM
AIX uses one IP stack for IPv4, all interfaces, and in the newer versions (starting with AIX 4.3.0) an additional stack for IPv6.

Focusing on IPv4 and AIX 4.1: each ethernet adapter runs at one speed (10 or 100) and either half or full duplex, depending on driver support.

The configuration of the adapter can be read by: lsattr -El entX
The actual status of an active adapter can be read by: entstat -d entX (output similiar to netstat -m, but not exactly the same)

Each ether adapter supports two IP protocols: what I call "Xerox Park" - iirc the original Ethernet LAN (layer 2) description; and IEEE 802.3 (also know as dot 3, token ring, e.g. is dot 5, or 802.5, etc., etc..). In AIX IP interface terms these interfaces are, respectively: { adapter, Xerox, dot 3 } :: { entX, enX, etX }

IP interfaces can be configured via ODM settings via:
chdev -l enX -a netaddr=10.168.1.1 -a netmask=255.255.255.0 -a state=up
or directly via ifconfig
ifconfig enX 10.168.1.1 netmask=255.255.255.0 up

To see if an interface is configured via ODM, or what it should ODM think it should be:
lsattr -El enX

To bring an interface down/up without destroying any configuration information:
rmdev -l enX or ifconfig enX detach ## may also clear some routing information
Online: mkdev -l enX

To restore default routing, as far as interfaces permit:
mkdev -l inet0

These commands are what smit is executing for you. Review $HOME/smit.script to see what commands smit has performed. $HOME/smit.log has the output from these commands.
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: John Peck on October 12, 2008, 02:08:54 AM
It is not usual to see the level 2 cache configured as a device - proc0,1,... for the processors is as far as it usually goes,
the cache is being used seamlessly.

Normally tape drives are configured with hardware compression enabled.  That can be disabled with "smit chgtpe" as a rule.
It's also possible to use the dot number extensions to the device file to call on attributes of a tape drive - although not compression as such, just density (i.e. different versions of tape formats as in DDS2, 3, 4 etc).  From "man rmt":

Special File Name Rewind-on-Close Retension-on-Open Bytes per Inch 
/dev/rmt* Yes No Density setting #1                                 
/dev/rmt*.1 No No Density setting #1                               
/dev/rmt*.2 Yes Yes Density setting #1                             
/dev/rmt*.3 No Yes Density setting #1                               
/dev/rmt*.4 Yes No Density setting #2                               
/dev/rmt*.5 No No Density setting #2                               
/dev/rmt*.6 Yes Yes Density setting #2                             
/dev/rmt*.7 No Yes Density setting #2   

 1. The values of density setting #1 and density setting #2 come from tape     
    drive attributes that can be set using SMIT. Typically density setting #1 
    is set to the highest possible density for the tape drive while density   
    setting #2 is set to a lower density. However, density settings are not   
    required to follow this pattern.                                           
 2. The density value (bytes per inch) is ignored when using a magnetic tape   
    device that does not support multiple densities. For tape drives that do   
    support multiple densities, the density value only applies when writing to
    the tape. When reading, the drive defaults to the density at which the tape
    is written.                                                               
 3. Most tape drives use 512-byte block size. The 8mm tape drive uses a minimum
    block size of 1024 bytes. Using SMIT to lower the block size, will waste   
    space.                                                                                               


Another one to look at is the "tctl" command, which does rewinding for you.

In the actual 43P machine the internal SCSI cable is a loop from mother board to devices
and back again - each device has to have jumper set SCSI id and the termination is
in the motherboard.  If you connect inappropriate devices (wrong SCSI type), that will
give SCSI termination errors - only a select band of devices is supported and will work !

Anyone would think my knuckles drag on the ground now  :D
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on October 13, 2008, 10:05:53 AM
It is not usual to see the level 2 cache configured as a device - proc0,1,... for the processors is as far as it usually goes,
the cache is being used seamlessly.

Hmm... When running "diag -a" it mourns about a new resource that -> may <- require software installation:

- L2cache0     00-L0     L2 Cache

Within the ANS the Level 2 cache is a single additional chip which is placed on the mainboard and not the processor board. Removing it is no option as I know what can happen from other Macs.

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: John Peck on October 13, 2008, 11:29:15 AM

Actually, as Simon Cowel says on occasion, I got that wrong. 
L2cache0 I see as "available" on a proper machine with such cache using "lsdev -C".
If your box genuinely requires software to be installed for it, then I would expect
the device not to be "available" but "defined".  If it is "defined", it's not in use,
forget about it.  If it's available, it's in use and will make no difference whatever
I expect.
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on April 01, 2011, 04:43:03 PM
Hello back again...

There is a simple reason for my absence: my first Apple Network Server has gone to its maker, the power supply blew off so this is why I wasn't here for more than some years by now. In the meantime I got myself a second box of that kind, the first one is a spare part server by now <sigh>.

By now the second one is up and running on AIX for ANS 4.1.5 and I was able to configure it at least a bit. I learned several things and I was reading tons of documents. For now it looks like I will have to stay with what I got: one 50 pin SCSI HD containing the AIX and four 68 pin SCSI HDs with 36 GB capacity each, two network interfaces by now, both running at 10 MBps. Nothing less, nothing more.

I can't tell exactly how I actually did this but by now I am able to ping the onboard ethernet interface (en0 and et0) from other machines in my LAN. Both installed interfaces use DHCP.

Now there are some questions I did not find any answers to. I am hoping You don't mind me asking some more questions...

Network

As I already stated I have two physical installed interfaces, one onboard ethernet (defined and available, en0 and et0) and one PCI card (en1 and et1). The onboard interface keeps its data on every shutdown and reboot but not the second one. So here is the first question:

After reboot / boot I always have to reconfigure the PCI interface to respond to pings. By using

/usr/bin/mktcpip (and else)

I am able to ping the installed PCI card but on every reboot / shutdown this configuration gets lost (in other words I have to configure the desired settings again). Is there any possibility to keep these settings upon every reboot / shutdown and if yes what do I have to configure where? When using the graphical interface of Smit the running man keeps biting the dust...

Regarding this double interface question there is a more general one: as I assume two network interfaces make some sense for my aim to use that box as a web server. I want to use one ethernet interface for general administration purposes over my LAN and the second one with a different IP address for web based requests, to be more exact: the PCI interface should respond to any HTTP request in the future. Maybe there will be a third interface for FTP requests but this will be a different story.

Does this make sense or do You have other advices? My box should use an old Apache HTTP server in the future for serving a simple HTML, nothing more, nothing less. Any FTP and administration requests will run over my LAN (no FTP requests from the outside will be possible).

What I also found out by now: any network interface attached to that box will have to be configured in order to use a special network protocol. To be more exact: any interface will be able to "use" ethernet, 803.22, TokenRing or what ever but You will have to configure every protocol before it can be used. What looks like a disadvantage on first sight might be an advantage, right now I have configured both interfaces on standard ethernet and 803.22. All the AppleTalk stuff will be ignored for now, this will be a different story...

Harddisks

As already mentioned I am using a 50 pin HD with 4 GB as the operating system carrier (rootvg resides on that one). I tried to add the other four drives (36 GB 68 pin each) to the rootvg but wasn't succesful, AIX mourned something about partition size and else as far as I can remember. After thinking for a while I decided to group these four disks together in its own group (datavg).

Question:

As I want to store some downloadable data and the HTTP server seperated from the rootvg does it make sense to install and store everything within this volume group "datavg"? Or would You go another way?

DynDNS

It looks like that there will be no other way for me to use DynDNS for my future purposes. Before I am spending to much time in experimenting: do the provided update clients from DynDNS actually work within AIX 4.1.5 and if yes what do I have to do / which client provided by DynDNS do I have to choose?

Apache

As already written I will have to use Apache (1.3 I think, I wasn't able to find the NSCA server software of that time). As far as I understand all this I have to compile that provided distribution on my ANS in order to use it one day. Simple question (but I know what efforts it will take for You to describe it): how do I compile? I never did such stuff before....

Thanks for any possible reply  -  once more...

Jens
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on April 01, 2011, 11:08:38 PM
Well, glad for you that you are able to get a second Apple going.

AIX 4.1.5 - and firewalls - not sure when the bos.net.ipsec fileset appeared, but that will take care of packet filtering if it is available in AIX 4.1. Dont forget - or maybe you did not know, AIX 4.2 started in 1997 (if not 1996!).

Most of you other questions I should be able to help you with. But it will help me -  to help you get it into the ODM - if you tell me what commands you actually run to get things operational.

Check in your home directory for smit.script if you are always using smit - otherwise cut/paste from CLI - command line interface.
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on April 02, 2011, 01:26:36 PM
Hello Michael.

Sorry, my fault regarding the commands - so I will be more precise in the future. So for configuring the TCP IP for second NI interface (10 MBps PCI card) I used Smit as root, in the beginning using the graphical interface. Because this did not work I turned over to the terminal by using:

# /usr/bin/mktcpip -h localhost -a 10.0.1.31 -i et1

and

# /usr/bin/mktcpip -h localhost -a 10.0.1.31 -i en1

Please note that my onboard LAN with et0 and en0 also uses "localhost", the same subnet mask (obviously) but the different IP 10.0.1.30. When hitting return following lines appear in the terminal:

et1
localhost
inet0 changed
et1 changed

According lines appear when changing en0. After this I can pin 10.0.1.31 from within my LAN using any terminal (mostly OS X) using: ping 10.0.1.31, but this gets lost when rebooting or shutting down. Please also note that the en0 and et0 (onboard LAN) are always ping-able, no matter if rebooting or shut down.
When using Smit in graphical mode as root I clicked on "Communications Applications and Services" > "TCP/IP" > "Minimum Configuration & Startup". Then I chose en1 (Standard Ethernet Network Interface) or et1 (IEEE 802.3 Ethernet Network Interface) and filled in the fields:

* Hostname localhost
* Internet Address (dotted decimal) 10.0.1.31
Network Mask (dotted decimal) 255.255.255.0
* Network Interface et1

NAMESERVER
Internet Address (dotted decimal) * left blank because I do not know what to enter here *
Domain name * also left blank because I again do not know what to enter here *
Default Gateway address 10.0.1.1
Cable type N/A
Start now yes

When clicking "OK" the running man starts and after some seconds the following appears.

et1
localhost
inet0 changed
et1 changed
Method error (/usr/lib/methods/chginet):
0514-066 Cause not known
0821-279 writing to routing socket: Do not specify an existing file.
Do not specify an existing file.
0821-207 chginet: Cannot add route record to CuAt.
/usr/sbin/mktcpip: Problem with chdev command, return code= 1


Regarding DynDNS:

I don?t know which software to use. There are two update clients available that can be used with DynDNS. ddclient or inadyn, both available from http://www.dyndns.com/support/clients/unix.html.

Regarding Apache:

It seems to me that version 1.3.1 is the only one I can use with that old AIX. The version I already downloaded is the source for Apache 1.3.1 with a binary precompiled for platform rs6000-ibm-aix-32. I don?t know if I can use later (more secure /stable versions) and I don?t know if other versions are compileable on my ANS.

Again thanks for any reply!

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on April 02, 2011, 01:32:53 PM
By the way:

http://www.softpanorama.org/Commercial_unixes/AIX/index.shtml is my "reference" for many infos I am looking for by now so hopefully I do not have to ask too many questions in here ;-)

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on April 04, 2011, 11:19:29 AM
I like Questions! So ask away!

And, if you are looking for a Quick Reference we have one here as well:

http://www.rootvg.net/component/option,com_wrapper/Itemid,99/

This was a reference I helped Erik Kluit write - 10 Years ago.

Very unfortunately, I was not able to find a way to "celebrate" 10 years of assisting AIX Administrators. But, FYI, if not the first and hence oldest, rootvt.net (and .com and .org) is certainly the oldest still functioning AIX information portal.

If anyone knows of a portal dedicated to AIX that is older than rootvg.net - do tell!!
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on April 04, 2011, 11:32:08 AM
Now, regarding setting up your network.

After you enter:
Quote
# /usr/bin/mktcpip -h localhost -a 10.0.1.31 -i et1

and

# /usr/bin/mktcpip -h localhost -a 10.0.1.31 -i en1

I would expect et1 and en1 to both have IP address 10.0.1.31 with netmask 255.0.0.0. I am unaware of AIX automatically giving an interface 255.255.255.0 as a netmask. I think you are lucky that the pings work if you are using 255.255.255.0 on your other systems.

Probably you do not need the et1 interface. That is 802.3 protocol and there are very few systems that use that. Having the same address on two interfaces (Level 3 - enX and etX are two interfaces) is not wise. You are "lucky" that the stack is using the right interface.

The smit command I would recommend is:

# smitty mktcpip

Explanation: "smitty" - always starts the character based interface. You might need to set your terminal type first, e.g.
# export TERM=vt100

"mktcpip" is the fastpath to setup tcpip using SMIT interface on AIX. I suggest you only configure the en1 interface.

To see the command(s) smit is executing, press Esc-6 (Escape key followed by 6 key - fairly quickly, roughly within 1 sec) to emulate pressing F6 (Function6 key).

Basically, the key additional command  this executes is:

# chdev -l en1 -a netaddr=10.0.1.31 -a netmask=255.0.0.0 -a state=up

Note: when you are in the dialog it is easy to specify your netmask of 255.255.255.0 as well as give a default route.

The error messages you are getting comes from using "Start now: yes". Leave that to no. It is for something going back to before 1995 I think as AIX 4 and beyond has never needed it after a normal boot. All the daemons are already running.

To see the state of an interface definition in the ODM:

# lsattr -E -l en1

Note: there are also notes in /etc/rc.tcpip for how you can configure tcpip on AIX without using the ODM (then you script the commands "hostname", "ifconfig", "route", etc.
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on April 05, 2011, 11:00:24 AM
Well, still not quite there where I want to be...

Anyway, I used smitty mktcpip to configure my interfaces as You suggested. First of all I removed the "et"-parts (as long as 802.3 isn?t "popular" and I don?t have machines using that protocol (besides a very old Shiva Fastpath 4 waiting to be configured for my non-Ethernet Macs one day)) so I still have en0 and en1 right now. Still the en0 responds to pings while using the 255.255.255.0 netmask, the en1 does not respond, the OS X terminal mourns about time outs. This happens after a "clean" install of AIX 4.1.5 with all hardware already added before installation, DHCP and TCP / IP configuration just after clean install. After every reboot or fresh start of that server the en0 interface is up and running - and responding. en1 is not responding. This is what # lsattr -E -l en1 states:

mtu   1500    Minimum IP Packet size for this device TRUE
remmtu 576 Minimum IP packet size for remote networks TRUE
netaddr  10.0.1.31 Internet address   TRUE
state  up  Current Interface Status TRUE
arp  on  Address resolution protocol (ARP) TRUE
netmask 255.255.255.0  Subnet Mask  TRUE
security none Security level TRUE
authority  Authorized users  TRUE
broadcast  Broadcast address TRUE

It looks the same for en0 - just the IP address is different: 10.0.1.30 (instead of 10.0.1.31). Just being a bit confused by now why one interface responds and the other one doesn?t: do I have to configure a route to en1 to make it respond?

While using SMIT and configuring DHCP I only had the choice between

any (= first available interface)
en0 (= onboard)
en1 (= PCI card)

There is no list entry that enables both at the same time. So do I get it right: is DHCP able to be configured only to one interface? Does not sound very logical to me as I was able to ping en1 after using # /usr/bin/mktcpip -h localhost -a 10.0.1.31 -i en1.

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on April 05, 2011, 06:25:29 PM
As I do not know what
Quote
# /usr/bin/mktcpip -h localhost -a 10.0.1.31 -i en1
does, what you could do is:
# erase definition of en1
# rmdev -dl en1
# create empty definition of en1
# cfgmgr
# get it configured and working
# /usr/bin/mktcpip -h localhost -a 10.0.1.31 -i en1

# test with ping that it is working, if yes

# ifconfig en1


And the other command I would try, to check on the en1 interface traffic:

# tcpdump -i en1 -I

I dont think the -I argument is needed anymore. If I remember correctly the -I argument was needed for Immediate echo of incoming packets.

Also, netstat -in (numeric) will show IP addresses and traffic (incoming/outgoing packet counts), e.g.
Name  Mtu   Network     Address           ZoneID    Ipkts Ierrs    Opkts Oerrs  Coll
en0   1500  link#2      9.9.69.3e.49.f9        - 99879491     0 84879283     0     0
en0   1500  192.168.129 192.168.129.54         - 99879491     0 84879283     0     0
en1   1500  link#3      9.9.6b.ce.49.30        -  4545511     0  1169347     0     0
en1   1500  62.163.7    162.63.17.53           -  4545511     0  1169347     0     0
lo0   16896 link#1                             -   695417     0   708011     0     0
lo0   16896 127         127.0.0.1              -   695417     0   708011     0     0


For dhcpcd - just add a second line to /etc/dhcpcd.ini - it can be as simple as:


interface en0
{
}
interface en1
{
}


If you are going to try to use dhcp to configure your system - undo the static setup - from a console!
Edit the file /etc/dhcpcd.ini to define the interfaces you want to be initialized, then the following commands:

# rmdev -dl en0
# rmdev -dl en1
# cfgmgr

# smitty otherserv


go to the dhcpcd selection and select both - OR - execute this command

# /usr/sbin/chrctcp -S -a dhcpcd

Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on April 06, 2011, 12:41:19 PM
Hmmm...

I?ve been trying to modify the dhcpcd.ini as You suggested - with no success. As expected (and configured before by me) there is a setting for "any" network interface (i.o.w.: the first available:

interface any
{
option 19 0
option 20 0
option 27 0
option 29 0
option 30 0
option 31 0
option 34 0
option 36 0
option 39 0
}

I?ve been un-commenting these lines and added

interface en0
{
}

interface en1
{
}

and rebooted the server. This time no interface was ping-able, not even en0. After adding the options from "any" to both en0 and en1 and rebooting I could ping en0 - but not en1.

Regarding the "-i": the usage definition states "-i" as "Interface to associate with the -a IP adress".

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on April 06, 2011, 08:28:51 PM
I should have re-read the documentation, rather than trust old memory that turn out to be wrong ones.

smitty is doing it correctly - specifying any as the interface. I have not been able to find out how to make it do ALL interfaces. I guess you should choose one.

You may need to delete /etc/dhcpc.opt (or rename it) - just to be sure of a clean start.

You could also consider running /usr/sbin/dhcpcd from a script - twice; or once for the "other" interface.

re: dyndns - I found a program that might work - if the version of perl needed is not too specific (maybe you can modify it if it needs new perl statements).

http://sourceforge.net/apps/trac/ddclient/wiki -- ddclient 3.8.0
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on April 07, 2011, 07:03:18 AM
Don?t worry about Your memory - I do have the same problems sometimes when I?m dealing with old Mac systems before 8.0. Although I own quite a bunch of documentation I am simply sometimes too lazy to re-read those. And memories can be tricky ;-)

Anyway, I feared it would end up that way being able to use just one port for dhcp - although it doesn?t make much sense to me as I could fit up to 6 PCI NICs into that box (and Apple states this expandability as a major plus of that box). So why having up to seven interfaces when only four protocols can be used and only one interface could be dhcp-ed? Doesn?t matter, as long as I need only one interface for dhcp in order to use DynDNS it shouldn?t be that tragic.

Before I will set up DynDNS and Apache I will have to deal with AppleTalk. As some of my old Macs will never be able to use any kind of ethernet interface the ANS will have to do some AppleTalk/TCPIP routing - will be a major pain, I guess but at least this part is a bit documentated by Apple.

So for now "just" these questions:

- How do I determine if perl is installed and which version it is?
- How do I compile (if needed anyway) the Apache 1.3.1 binaries? What prerequisites do I have to have?

Once again many "Thank You?s" for Your very valuable help!
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on April 07, 2011, 02:16:49 PM
Just a short side note on what oddity I discovered today:

I re-installed the whole bunch, now this time configuring en1 as the DHCP interface - I kept the IP settings for both interfaces (10.0.1.30 and 10.0.1.31). Guess what happened: without using

# /usr/bin/mktcpip -h localhost -a 10.0.1.30 -i en0

for the onboard interface I was able to ping -> both <- interfaces. After re-booting this was gone.

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on April 08, 2011, 05:32:24 PM
I had to clean up, having another major clean up session now as well, when I, with pain on my heart, got rid of my Inside Macintosh Volumes 1-5.

A lot of the information in those books was no longer completely valid after HFS came out, but still, I spent several years programming Macs from the FatMac (512Mbyte) to OS version 6.X.Y.

Last year I cleaned up an 11 vol series on AIX documentation - for AIX 4.1.4. That information is all available on DVD now - the most important volumes then being Vol 1 and Vol 2 (which are now the six manual voulmes) and Vol 3 and Vol 4 (The two Technology Volumes).

You sound like some one who will also read a manual. I would recommend reading the AIX 5.1 PDF
(as close as I can get easily, to AIX 4.1 via the rootvg.net link at:
http://www.rootvg.net/component/option,com_wrapper/Itemid,203/

Now about your fresh installation - before reboot you should save the output of the commands:
lsattr -El ent0 and lsattr -El ent1

Also the output of ifconfig -a.

Perl - if it is installed, something like this:
michael@x054:[/data/home/michael]perl -v

This is perl, v5.8.8 built for aix-thread-multi

Copyright 1987-2006, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.


For rebuilding Apache - I would look for an older version of gcc as compiler if you must go the complier route. Standard with all those source packages is that you run the command ./configure and it tells you what is needed.

As an experiment you could try downloading a version of Apache I built for AIX 5.3 (http://dl.aixtools.org/apache2/). I don't expect it to work, but it might. Surprises happen. And I am looking at recompiling a version of Apache 2.2 for AIX 4.3.3 (I don't think I have any copies of AIX 4.1.5 to reinstall).

Re: AppleTalk - IBM had a product it sold/supported - I cannot think of the name right now. The product was to help integrate many different protocols into/with TCPIP protocols.

Lastly: although I like the ODM solution - very much - when I first started at IBM I wondered often - why bother? I was so used to using vi and going into /usr/sys/* and /etc/* files to configure everything that I really did not see the value. That came when I started needing to install 10 to 30 systems in an hour, and might get disturbed. It was just much easier to have commands that made synchronous changes in three or four places.
So, this is just one system, ODM/dhcp is not working the way we want it - lets look at the "Berkeley" way which has been in AIX since AIX version 3.0.

Step #1 - verify/change the bootup_option (in the ODM :) )

# ]lsattr -El inet0
authm         65536 Authentication Methods              True
bootup_option no    Use BSD-style Network Configuration True
gateway             Gateway                             True
hostname      x054  Host Name                           True
route               Route                               True


Change to BSD (Berkeley Software Distribution) Network Style
# chdev -l inet0 -a bootup_option=yes
inet0 changed


In /etc/rc.tcpip look for the following:
Code: [Select]
# check the bootup_option flag in the configuration database
option=`lsattr -E -l inet0 -a bootup_option -F value`
Skip over the if [ "$option" = "no"  ] block...
so that we end with
Quote
else
        src_running=""
fi

There should be a file /etc/rc.bsdnet -- ignore it. You will need to edit the file: /etc/rc.net instead. Update "Part II"
##################################################################
# Part II - Traditional Configuration.
##################################################################
# An alternative method for bringing up all the default interfaces
# is to specify explicitly which interfaces to configure using the
# ifconfig command.  Ifconfig requires the configuration information
# be specified on the command line.  Ifconfig will not update the
# information kept in the ODM configuration database.
#
# Valid network interfaces are:
# lo=local loopback, en=standard ethernet, et=802.3 ethernet
# sl=serial line IP, tr=802.5 token ring, xs=X.25
#
# e.g., en0 denotes standard ethernet network interface, unit zero.
#
# Below are examples of how you could bring up each interface using
# ifconfig.  Since you can specify either a hostname or a dotted
# decimal address to set the interface address, it is convenient to
# set the hostname at this point and use it for the address of
# an interface, as shown below:
#
#/bin/hostname robo.austin.ibm.com      >>$LOGFILE 2>&1
#
# (Remember that if you have more than one interface,
# you'll want to have a different IP address for each one.
# Below, xx.xx.xx.xx stands for the internet address for the
# given interface).
#
#/usr/sbin/ifconfig lo0 inet loopback    up >>$LOGFILE 2>&1
#/usr/sbin/ifconfig en0 inet `hostname`  up >>$LOGFILE 2>&1
#/usr/sbin/ifconfig et0 inet xx.xx.xx.xx  up >>$LOGFILE 2>&1
#/usr/sbin/ifconfig tr0 inet xx.xx.xx.xx  up >>$LOGFILE 2>&1
#/usr/sbin/ifconfig sl0 inet xx.xx.xx.xx  up >>$LOGFILE 2>&1
#/usr/sbin/ifconfig xs0 inet xx.xx.xx.xx  up >>$LOGFILE 2>&1
#
#
# Now we set any static routes.
#
# /usr/sbin/route add 0 gateway                 >>$LOGFILE 2>&1
# /usr/sbin/route add 192.9.201.0 gateway       >>$LOGFILE 2>&1

You will need to remove comments. Note: you may use any command you want, e.g.
/usr/bin/mktcpip

The choice is not very common, but it is an official method. Maybe this solves the reboot issues for you.

The last bit I am thinking of goes back to when I had an old model (P40 model, the first to support ISA and PCI). These cards were not all auto-configureable. This is why I need/want to see the output of the commands:

lsdev -Cc adapter

and of all the entX adapters the command
lsattr -El entX

For some cards, that "reboot" fail to recognize correctly, it may be necessary to manually make changes in the ODM.

On one of my "old" systems:
mamfelt@x121:[/usr/sbin]lsattr -El ent0
busio         0x1000100      Bus I/O address                   False
busintr       6              Bus interrupt level               False
intr_priority 3              Interrupt priority                False
tx_que_size   64             TRANSMIT queue size               True
rx_que_size   32             RECEIVE queue size                True
full_duplex   no             Full duplex                       True
use_alt_addr  yes            Enable ALTERNATE ETHERNET address True
alt_addr      0x0000c50dd140 ALTERNATE ETHERNET address        True


Run the lsattr command to see if you can change any of the busio, busintr, or intr_priority (and note whether these are different after "install" versus after "reboot"

On the one hand, I dont think you have any problems here, but I want to get you prepared for some of the ways to investigate.


Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on April 09, 2011, 02:58:36 PM
Funny! I still keep my Inside Macintosh Volume I - III (first edition!) just for nostalgia reasons also the once only internally published "think different" campaign booklet and many other rarities but yes: I am actually keeping and reading manuals when I got hold of them. Regarding the Apple Network server it took me lots of time to get my fingers on some printed and otherwise written material... Where do I get that DVD You mentioned?

I swept out some hardware in the meantime, too. Right now I am sticking to my three Twentieth Anniversary Macintoshes (one in original state, the other one upgraded to it´s possible maximum running iTunes 1.1 and besides that BeOS 5 Pro), my NeXTcube, my upgraded 512k, the Bandai Pippin AtMark, Apples Set Top Box, some older PowerBooks for Rhapsody and alike and a Quadra 700 with A/UX (still hoping to get a 900 or 950 Quadra though...). I do not really know what to do with the rest (Apple //e, all three Cobalt Qubes, some Ataris and else), maybe I am selling or keeping them. I am still longing for a BeBox but I guess this will stay a dream...

Ok, now back to topics. For ent0 following is listed when lsattr -El ent0:

device_addr        0xffffffff      Device Address                  False
dma_addr           0xffffffff      DMA Address                     False
x_intr_level         23              Transmit Interrupt Level     False
r_intr_level         22              Receive Interrupt Level       False
x_int_priority       3                Transmit Interrupt Priority  False
r_int_priority       3                Receive Interrupt Priority   False
xmt_que_size      128              TRANSMIT queue size          True
rcv_pool_size      40               RECEIVE buffer pool size      True
use_alt_addr       no              Enable alternate ethernet address  True
alt_addr             0x               Alternate ethernet address      True
OF_handle          0x1ff480b8   OpenFirmware node handle     False

For ent1 it looks this: 

device_addr        0xf5100000      Device Address                  False
intr_level         29                     Bus Interrupt Level             False
intr_priority      3                      Interrupt Priority                False
xmt_que_size      128                TRANSMIT queue size          True
rcv_pool_size      40                  RECEIVE buffer pool size      True
use_alt_addr       no              Enable alternate ethernet address  True
alt_addr             0x               Alternate ethernet address      True
OF_handle          0x1ff524b0   OpenFirmware node handle     False
cfg_addr             0x              Configuration Space Address   True
full_dpx              auto            Enable Full Duplex Operation   True
xmt_thrs            160              Transmit FIFO threshold         True
capt_fx              no                Enable Capture Effects Avoidance  True

Entering "ifconfig -a" throws me this:

0821-515 ifconfig: error loading /usr/lib/drivers/if -a: A file or directory in the path name does not exist. Without "-a" it shows me the flags possible to use. Entering "ifconfig et0" (not ent0) results this:

et0: flags=8080822<BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST>

with et1 it looks exactly the same.

I am not sure if I understood Your comment regarding Perl right. As long as I do not know UNIX and AIX in deep very much I had to search for it in the InfoExplorer - but did not find anything. But by now it seems to me that no AIX 4.1.x version included Perl in any way so I have to compile that one, too (I think it will be Perl version 5).

IBM once made or offered an "AppleShare (file) server" based on AppleTalk - seems to have gone lost... And I have been searching for it very intensively. I´ve had some success in AppleTalk by now. I connected an old PowerBook 520c via Ethernet, configured AppleTalk for routing purposes on en0, configured AURP (AppleTalk over TCP) and some services for a Macintosh client software bundle. This bundle contains

- a disk management utility (for setting up VGs, LVMs and else)
- a VT102 CommandShell
- a Fractal Demo
- a Status Demo

I was able to connect the disk management utility as guest, setting up a root connection throws me a "cannot send xyz to host" error - maybe this is caused by the old MacTCP control panel. All the other utilities can not get connected as guest or root. But the PowerBook "sees" the server via AppleTalk in the chooser and it notes the AppleTalk zone.

For GCC: after some research and investigation on the net I found GCC 2.8.1 (http://ftp.gnu.org/gnu/gcc/) - seems to be the adequate version for my purposes. I will try to install that one (and other things needed) - I have never done such stuff before and I am somehow a bit nervous... GCC 2.9 and up seem to be for AIX 4.3. But besides this many sites on the web tell me that IBMs ANSI C compiler is a lot easier to use than GCC and produces much less errors in compiling. Is that true? Where do I get this ANSI C compiler for my box?

I am so happy that You seem (...) to have some fun in helping me in my quest!
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on April 18, 2011, 05:09:32 AM
A small "update", better: some new experiences...

I was trying to install GCC (now in version 3.1, to me the last one that was compiled and tested in 4.1.5 successfully). I did not came very far as I don't understand the GCC manual regarding the installation and prerequisites topics. Nevertheless I started ./configure and ./configure.guess.

While fiddling around with tar and else I wondered about some aspects of the AIX file system. I wanted to trash several objects from the GCC installation (for example the tar itself). In any attempt to do this the File Manager throwed me an error of that kind: "Not enough space on that device". In other words: I had to trash small bunches of files one after the other. Now: as far as I found out the "Trash" is located as a directory in /.dt/Trash. What is strange to me: how can a directory be defined as a device? I know that mounting a file system of a CD ROM for example handles the directory "/cdrom" as a device but I do not understand, why "Trash" also is a device.
As I didn't find out how to increase the possible size of the Trash directory I started to modify the file system sizes of /, /home, /tmp and else - but this did not change (capacity) the size of the Trash itself or at least not to the amount I needed ist to be.

Which brings up another question: right now I have 4 drives with 36 GB each, rootvg on hd0, all the other drives not assigned to any vg by now. Following the rule of thumb (I know this is not ideal as long as I now don't know how my workload will look like later on) I assigned the double of my physical RAM - 1024 MB as paging space to that single hd0. I am going to upgrade my drives to 73 GB ones soon.

Is there any rule of thumb how the file systems should be resized when leaving rootvg on one single drive (in return any rule of thumb if rootvg is "spanned" over more disks)?

As long as I don't plan to use my box as a development machine in extreme I tend to find a balanced mixture between average availability and average performance. I am going to use it as a http and maybe as a ftp server, AppleTalk just for internal use. To me it appears to be "enough" to assign all available hard disks to the rootvg (not other vg's for server purposes). Am I correct in this?

And if someone in here has some experience with installing and building GCC I would appreciate some more help pretty much.

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on April 18, 2011, 09:58:32 AM
Very slow line: short answers.

CDE (Common Desktop Environment) is the GUI that comes with AIX. Licensed from HP Openview if i recall correctly. Trash is a directory, in root (/) in your case. I would look around for settings to delete files immediately, or use a command prompt and use the command rm.

I generally read the README and/or INSTALL files, or names similar, before running ./configure.

A simple test is helloworld.c
Code: [Select]
#include <stdio.h>
main()
{
    printf("Hello World\n");
}

then use:
$ cc helloworld.c
$ ./a.out

If it says hello your compiler is installed and working.

Regarding memory: a rule of thumb was paging space 2x physical memory. However in your case I would keep it smaller for now - 512M to 1G, and monitor usage with the command
lsps -s

regarding your other disks: if you had them as a volume group before:

# importvg -y vgMyData hdisk1

otherwise the command will use mkvg (to make a volume group). I'll work up something for you on that asap.
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on April 20, 2011, 09:00:21 AM
Well, I am not that familiar with technical English and this is why I'm getting a bit confused by the installation instructions of GCC. Anyway I will try to find a german translation.

Yesterday my 5 hard disks arrived, each 72 GB with 15.000 RPM - the maximum this box can handle. Right now I only have 4 of them inside the trays as I will have to look for a fifth SCSI interconnect board (maybe I will make one on my own if I can't find one at eBay's). It was pretty hard to get such drives with 68 Pin connector - the ANS does not have SAS connectors.

Right now hd0 is carrying the rootvg, all the other drives are just formatted (without certify as it does not work with drives larger than 36 GB) and not assigned to any vg. These are the outputs of

#lsvg rootvg

Volume group: rootvg
VG state: active
VG permission: read/write
Max LVs: 256
LVs: 8
Open LVs: 7
Total PVs: 1
Stale PVs: 0
Active PVs: 1
VG Identifier: 0024d7e8e93c8b7c
PP size: 128 megabyte(s)
Total PPs: 546 (69888 megabytes)
Free PPs: 522 (66816 megabytes)
Used PPs: 24 (3072 megabytes)
Quorum: 2
VG descriptors: 2
Stale PPs: 0
Auto on: yes
_______________________________________ __________
The paging space was modified by me after installation:

#lsps -a

Page Space: hd6
Physical volume: hdisk0
Volume Group: rootvg
Size: 1024 MB (exactly the double of my physically installed RAM!)
%Used: 4
Active: yes
Auto: yes
Type: lv
_______________________________________ _______________
#df -k

Filesystem                   1024-blocks          Free         %Used       Iused       %Iused         Mounted on
/dev/hd4                      131072                118136     10             1400         3                 /
/dev/hd2                     1310720               70644        95            22450        7                /usr
/dev/hd9var                 131072                126332      4               173          1                 /var
/dev/hd3                      131072                126756      4               30            1                /tmp
/dev/hd1                      131072                126804      4               38            1                /home

Note that all the installable software from the CDROM was copied to the harddisk hd0 right after installation (is this why /usr is used tp 95 %?).

Regarding IBM's ANSI C Compiler...

I had contact to IBM Germany and they told me that no version of that compiler for AIX 4 is available anymore (I wasn't astonished about that fact too much...). So I've been searching the net and found out that the ANSI C compiler is part of "IBM Visual Age C++ Professional" - and I own that one in Version 6.0 for AIX 5 L (I got AIX 5 L some time ago alongside with a RS/6000 machine). But version 6.0 (and even 5.0) seem to be made for AIX at least version 4.3.3 - so if anyone here has version -> 4.0 <- of that Visual Age C++ archived and wants to trade it please let me know - I am not in need of AIX 5 L and the bunch of IBM CDs that lie around here by now.

There is absolutly no hurry to answer my requests this time as I will be on the road the next days, too ;-)

J
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Michael on April 21, 2011, 01:00:34 PM
What would be interesting (to me), and perhaps helpful to you, would be to see if a migration update to AIX 4.3.3 is possible. As there is no support for AIX 4.1.X, not having support for AIX 4.3.3 should not be an issue. Only thing I can think of that might be an issue is whether AIX will be able to create a boot image for the Apple platform.

Re: the version of xLC that you have. The higher versions were a must for newer versions of AIX, but often supported older versions. I have been using xlC version 7, that was released for AIX 5.2 iirc on AIX 5.3 and even AIX 6.1. The newer versions were backward compatible - for a bit. Check the documentation with your release.

You have a very serious hobby it seems. My pleasure to be assisting you.
Title: Re: Apple Network Server 500/132 & AIX 4.1.4
Post by: Leografix on April 21, 2011, 02:15:36 PM
Well, it is a hobby but I am taking it not too serious. I am just somewhat picky about my projects as they are rather unusual. To give You an impression: I once set up a PM 9500 with MKLinux, Windows 95 and 98, Mac OS 7.6 up to 9.2.2 and pre-release OS X versions - all at the same time with a G4 upgrade just to see if it works (and it does). A Quadra is set up with A/UX, this box right now is the LocalTalk Ethernet Bridge (the Apple Network Server hopefully will do that job later on when this project is finished). I once ran a little http server on a Mac Plus... I always want test how far I can go with unusal setups. So this is why I am not owning many but truly not ordinary computers. Imagine a Newton 2100 as a http server ;-)

Back to topics:

I am pretty sure that any update to 4.2 or 4.3 will not be possible - I researched that many times before. There are just two notes mentioning that Apple once planed to go that way but they never made it. Another ANS owner once tried it with regular IBM versions - leaving his ANS completly unbootable (as far as I know he never got that ANS back to work). I suppose it has something to do with the Apple Open Firmware and the implementation of the cache and ROM (the ROM is somewaht a stripped version of a 9500 PM - without any Mac OS code in it). So AIX for the ANS is not just an AppleTalked version of AIX but a adapted version to the specialities of that machine. I have been looking IBMs sources for any possibility to upgrade but the special drivers for some hardware components of the ANS (not used in any RS/6000 as far as I know) are all ending at level 4.1.5.0. So this road will lead to nowhere for pretty sure.

Regarding xCL and else:

I could use my RS/6000 for compiling purposes, I know. But I want to build "native" versions of GCC and Apache (maybe Pearl and else) just on that box. I want to write about my experiences in compiling on that machine to give other ANS owners as much hints as possible later on. Although it truly will be much easier to compile on AIX 5 L / RS/6000 this is only my second choice. So I will try to find the 4.0 version of VisualAge. If I am not successful I will deal with GCC (to be more exact: I will deal with GCC until I find the 4.0 version).

But for now I will be offline for two weeks. Vacation is a hobby I am taking more serious than any beloved machine I own (I like the black RS machines - but to be honest: my NeXTcube looks slightly better ;-)). So I hope to be back here as soon as possible.

Once again thank You very much for Your highly apreciated help!

J