Irix netinstall

New to SGIs? Need help getting things going? This is the forum for you!
Forum rules
Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.
User avatar
LarBob
Donor
Donor
Posts: 96
Joined: Sun Nov 13, 2016 6:43 am
Location: Kentucky, US

Irix netinstall

Unread postby LarBob » Tue Aug 22, 2017 3:14 pm

Hi, I've set up a bridged vbox vm running debian 9. I've configured it to serve the files, but I'm kind of confused on setting up bootp. I followed this tutorial: viewtopic.php?t=16728942 but it doesn't seem to include setting up bootp. I've read other tutorials but I'm kind of at a loss. Obviously without a bootp server it won't boot on the octane. I don't have a scsi cd-rom to install the OS that way, so this is a necessity.
The netaddr is set to 192.168.0.52 and I'm guessing that the hostname is just octane because I have no way of getting to an actual OS and that's what I've read.
:Octane: Aezora - 2xR10k 250 MHz - 1 GB RAM - 6.5.30

User avatar
johnnym
Donor
Donor
Posts: 189
Joined: Sun Sep 04, 2016 9:53 pm

Re: Irix netinstall

Unread postby johnnym » Tue Aug 22, 2017 9:52 pm

LarBob wrote:I followed this tutorial: viewtopic.php?t=16728942 but it doesn't seem to include setting up bootp. I've read other tutorials but I'm kind of at a loss. Obviously without a bootp server it won't boot on the octane.

As the TFTP server's address and path to the binaries is given in the boot commands of the mentioned thread (e.g. "bootp()192.168.0.1:/srv/tftp/1/stand/fx.64") instead of requested from a BOOTP server (e.g. when using "bootp():" alone), it should work without a BOOTP server.

Or do you face problems when running the boot command?
:Indy: :O2: :Octane: :Octane2: :O200: = :O200: - :O200: = :O200: (O200 cluster w/2 GIGAchannel cabinets)
[ ( hp ) ] 712/80 c3000 (dead) :hpserv: (J5600) c3700 c3750 c8000 rp2470 :rx2600: (rx2620) rx4640
| d | i | g | i | t | a | l | AXPpci33 AlphaStation 200 AlphaStation 255 PWS 500au AlphaServer DS20E AlphaServer DS25
C O B A L T Qube 2 Qube 3 RaQ RaQ 2 RaQ 4r RaQ XTR

User avatar
LarBob
Donor
Donor
Posts: 96
Joined: Sun Nov 13, 2016 6:43 am
Location: Kentucky, US

Re: Irix netinstall

Unread postby LarBob » Wed Aug 23, 2017 4:25 am

johnnym wrote:
LarBob wrote:I followed this tutorial: viewtopic.php?t=16728942 but it doesn't seem to include setting up bootp. I've read other tutorials but I'm kind of at a loss. Obviously without a bootp server it won't boot on the octane.

As the TFTP server's address and path to the binaries is given in the boot commands of the mentioned thread (e.g. "bootp()192.168.0.1:/srv/tftp/1/stand/fx.64") instead of requested from a BOOTP server (e.g. when using "bootp():" alone), it should work without a BOOTP server.

Or do you face problems when running the boot command?

When I use the bootp command, it hangs for a long time then just says something like unable to execute, leading me to believe it can’t reach it/get the file.
:Octane: Aezora - 2xR10k 250 MHz - 1 GB RAM - 6.5.30

User avatar
johnnym
Donor
Donor
Posts: 189
Joined: Sun Sep 04, 2016 9:53 pm

Re: Irix netinstall

Unread postby johnnym » Wed Aug 23, 2017 7:48 am

LarBob wrote:
johnnym wrote:Or do you face problems when running the boot command?

When I use the bootp command, it hangs for a long time then just says something like unable to execute, leading me to believe it can’t reach it/get the file.

I'll check the behaviour of my Octane later and post if I can reproduce your problem.
:Indy: :O2: :Octane: :Octane2: :O200: = :O200: - :O200: = :O200: (O200 cluster w/2 GIGAchannel cabinets)
[ ( hp ) ] 712/80 c3000 (dead) :hpserv: (J5600) c3700 c3750 c8000 rp2470 :rx2600: (rx2620) rx4640
| d | i | g | i | t | a | l | AXPpci33 AlphaStation 200 AlphaStation 255 PWS 500au AlphaServer DS20E AlphaServer DS25
C O B A L T Qube 2 Qube 3 RaQ RaQ 2 RaQ 4r RaQ XTR

User avatar
johnnym
Donor
Donor
Posts: 189
Joined: Sun Sep 04, 2016 9:53 pm

Re: Irix netinstall

Unread postby johnnym » Wed Aug 23, 2017 11:16 am

LarBob wrote:When I use the bootp command, it hangs for a long time then just says something like unable to execute, leading me to believe it can’t reach it/get the file.

I assume you're case is one out of 1 to 4 below. And it looks like you indeed need a DHCP/BOOTP server available that answers the IP address requests of the Octane - as you initially assumed. My first answer was wrong in this regard.

OK, here's what I tested:

  1. Wrong setting for netaddr (should be empty or set to 172.16.2.51 but is set to 172.16.2.50) and active DHCP/BOOTP server (configuration below)

    Result:

    Code: Select all

    >> bootp()172.16.0.9:/AC100233
    No server for 172.16.0.9:/AC100233. 
    Your netaddr environment variable may be set incorrectly, or
    the net may be too busy for a connection to be made.
    Unable to execute bootp()172.16.0.9:/AC100233:  could not connect to server


    The Octane tries 8 times in total to contact DHCP/BOOTP server (it takes about 40 seconds until the "No server[...]" message appears), check with e.g.:

    Code: Select all

    $ sudo tcpdump -i eth0 port 67 or port 68 -e -n

    ...on the DHCP/BOOTP server. I haven't looked into the packets yet, but the DHCP/BOOTP server answers to the correct IP address, so it could be that the Octane still tries to get an IP address from the DHCP/BOOTP server, regardless of the setting of the netaddr PROM monitor environment var when using "bootp()[...]:[...]".

    Please take into account that although the directory used by the TFTP server is actually "/srv/tftp" in my case, the TFTP server chroots into this directory, hence all paths to files inside this directory have to start with this directory as "/" (root directory).

  2. Wrong setting for netaddr (as above) and inactive DHCP/BOOTP server

    Result:
    Same as for 1.

  3. netaddr unset and inactive DHCP/BOOTP server

    Result:
    Same as for 1.

  4. Correct setting for netaddr and inactive DHCP/BOOTP server

    Result:
    Same as for 1.

  5. Correct setting for netaddr and active DHCP/BOOTP server

    Result:
    The Octane loads the file and starts it:

    Code: Select all

    >> bootp()172.16.0.9:/AC100233
    Setting $netaddr to 172.16.2.51 (from server )
    Obtaining /AC100233 from server
    6494344+738984 entry: 0xa800000020020000
    ARCS64 Firmware
    Found SGI-IP30, setting up.
    Initial setup done, switching console.
    Copyright (c) 1982, 1986, 1989, 1991, 1993
            The Regents of the University of California.  All rights reserved.
    Copyright (c) 1995-2016 OpenBSD. All rights reserved.  http://www.OpenBSD.org

    OpenBSD 6.0 (GENERIC-IP30.MP) #632: Thu Jul 28 17:57:52 MDT 2016
        deraadt@sgi.openbsd.org:/usr/src/sys/arch/sgi/compile/GENERIC-IP30.MP
    real mem = 2147483648 (2048MB)
    rsvd mem = 1064960 (2MB)
    avail mem = 2120105984 (2021MB)
    warning: no entropy supplied by boot loader
    mainbus0 at root: Octane
    cpu0 at mainbus0: MIPS R12000 CPU rev 2.3 300 MHz, R10000 FPU rev 0.0
    cpu0: cache L1-I 32KB D 32KB 2 way, L2 2048KB 2 way
    cpu1 at mainbus0: MIPS R12000 CPU rev 2.3 300 MHz, R10000 FPU rev 0.0
    cpu1: cache L1-I 32KB D 32KB 2 way, L2 2048KB 2 way
    [...]

  6. Correct setting for netaddr but wrong path and active DHCP/BOOTP server

    Result:
    The Octane loads the file and starts it:

    Code: Select all

    >> bootp()172.16.0.9:/path/to/file
    Setting $netaddr to 172.16.2.51 (from server )
    Obtaining /path/to/file from server
    6494344+738984 entry: 0xa800000020020000
    ARCS64 Firmware
    Found SGI-IP30, setting up.
    Initial setup done, switching console.
    Copyright (c) 1982, 1986, 1989, 1991, 1993
            The Regents of the University of California.  All rights reserved.
    Copyright (c) 1995-2016 OpenBSD. All rights reserved.  http://www.OpenBSD.org

    OpenBSD 6.0 (GENERIC-IP30.MP) #632: Thu Jul 28 17:57:52 MDT 2016
        deraadt@sgi.openbsd.org:/usr/src/sys/arch/sgi/compile/GENERIC-IP30.MP
    real mem = 2147483648 (2048MB)
    rsvd mem = 1064960 (2MB)
    avail mem = 2120105984 (2021MB)
    warning: no entropy supplied by boot loader
    mainbus0 at root: Octane
    cpu0 at mainbus0: MIPS R12000 CPU rev 2.3 300 MHz, R10000 FPU rev 0.0
    cpu0: cache L1-I 32KB D 32KB 2 way, L2 2048KB 2 way
    cpu1 at mainbus0: MIPS R12000 CPU rev 2.3 300 MHz, R10000 FPU rev 0.0
    cpu1: cache L1-I 32KB D 32KB 2 way, L2 2048KB 2 way
    [...]

    Here it still loads the file whose name and path is served by the DHCP server, although it mentions that it is obtaining the file from the given path.

  7. Correct setting for netaddr but wrong path and active DHCP/BOOTP server (with "filename" and "next-server" vars for the octane commented)

    Result:

    Code: Select all

    >> bootp()172.16.0.9:/path/to/file
    Setting $netaddr to 172.16.2.51 (from server )

    TFTP error: File not found (code 1)
    Unable to execute bootp()172.16.0.9:/path/to/file:  invalid argument

    Only for this case it tries to load the file from the path that was given in the "bootp()[...]" command line.

Configuration used for ISC DHCP server on Raspbian Wheezy:

Code: Select all

# /etc/dhcp/dhcpd.conf

# option definitions common to all supported networks...
option domain-name "domain.tld";
option domain-name-servers 172.16.0.1;

default-lease-time 600;
max-lease-time 7200;

authoritative;

subnet 172.16.0.0 netmask 255.255.0.0 {
    range 172.16.1.1 172.16.1.254;
    option routers 172.16.0.1;

    host octane {
        fixed-address octane.domain.tld;
        hardware ethernet 08:00:69:44:55:66;
        filename "/AC100233";
        next-server nfs.domain.tld;
        option host-name "octane";
    }
}


Configuration used for HPA's TFTP server on Debian Jessie:

Code: Select all

# /etc/default/tftpd-hpa

TFTP_USERNAME="tftp"
TFTP_DIRECTORY="/srv/tftp"
TFTP_ADDRESS="0.0.0.0:69"
TFTP_OPTIONS="--secure -vvv"
Last edited by johnnym on Thu Aug 24, 2017 2:17 am, edited 1 time in total.
:Indy: :O2: :Octane: :Octane2: :O200: = :O200: - :O200: = :O200: (O200 cluster w/2 GIGAchannel cabinets)
[ ( hp ) ] 712/80 c3000 (dead) :hpserv: (J5600) c3700 c3750 c8000 rp2470 :rx2600: (rx2620) rx4640
| d | i | g | i | t | a | l | AXPpci33 AlphaStation 200 AlphaStation 255 PWS 500au AlphaServer DS20E AlphaServer DS25
C O B A L T Qube 2 Qube 3 RaQ RaQ 2 RaQ 4r RaQ XTR

User avatar
LarBob
Donor
Donor
Posts: 96
Joined: Sun Nov 13, 2016 6:43 am
Location: Kentucky, US

Re: Irix netinstall

Unread postby LarBob » Wed Aug 23, 2017 1:24 pm

johnnym wrote:I'll check the behaviour of my Octane later and post if I can reproduce your problem.

Thanks so much for testing it in such depth!
Okay, I've gotten it to the point to when I execute

Code: Select all

boot -f bootp()192.168.0.8:/srv/tftp/3/stand/fx.64

(The reason it's 3 is because I have 1 and 2 as the Application disks by accident, but I don't think it really matters)
I get TFTP error: File not found (code 1).
I'm not sure how to fix this as I'm not really sure what's wrong with my configuration. I have it set up as yours is basically, but I don't have the filename declared in the bootp config.
:Octane: Aezora - 2xR10k 250 MHz - 1 GB RAM - 6.5.30

User avatar
japes
Donor
Donor
Posts: 1001
Joined: Thu Nov 08, 2007 4:35 pm
Location: Lynnwood, WA

Re: Irix netinstall

Unread postby japes » Wed Aug 23, 2017 1:44 pm

Test that you can reach the tftp server is reachable by running a client on a working network station. Then you can rule out tftp server not running, tftp server path wrong, tftp server permission problem, and firewall.

It wouldn't hurt to watch the syslog on the tftp server as you try.
:O3000: :Fuel: :Tezro: :Tezro: :Octane2: :Octane: :Octane: :Indigo: :Indigo: :Indigo: :Indigo: :O2: :1600SW: :O2: :1600SW: :1600SW: :Indigo2: :Indigo2: :Indigo2: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :Indy: :O3x0: :O3x02L: :O3x02L:

User avatar
LarBob
Donor
Donor
Posts: 96
Joined: Sun Nov 13, 2016 6:43 am
Location: Kentucky, US

Re: Irix netinstall

Unread postby LarBob » Wed Aug 23, 2017 1:53 pm

japes wrote:Test that you can reach the tftp server is reachable by running a client on a working network station. Then you can rule out tftp server not running, tftp server path wrong, tftp server permission problem, and firewall.

It wouldn't hurt to watch the syslog on the tftp server as you try.

I see

Code: Select all

RRQ from 192.168.0.52 filename /srv/tftp/3/stand/fx.64
sending NAK (1, File not found) to 192.168.0.52

Even though it's there.
It's not an issue with bootp because even if I use a tftp client on the machine it gives the same error.
edit:
Okay, I tried using just /3/stand/fx.64 and the client on my computer was able to receive the client, however, the Octane now says "TFTP error: Request not null-terminated (code 4)".

edit: this was just a simple case of sysctl -w net.ipv4.ip_local_port_range="2048 32767".

once again, edit: I now have another problem. When I go to install system software and input 192.168.0.8 and /3/dist, it says it cannot load sa(sash64) --invalid argument. Shouldn't it be able to load fine if fx.64 could??
oh. okay. I restarted the tftp server and it magically started working!
:Octane: Aezora - 2xR10k 250 MHz - 1 GB RAM - 6.5.30

User avatar
johnnym
Donor
Donor
Posts: 189
Joined: Sun Sep 04, 2016 9:53 pm

Re: Irix netinstall

Unread postby johnnym » Thu Aug 24, 2017 2:36 am

LarBob wrote:edit: this was just a simple case of sysctl -w net.ipv4.ip_local_port_range="2048 32767".

Good catch. Best is to make it permanent in a file in /etc/sysctl.d/ or a line in /etc/sysctl.conf:

Code: Select all

root@nfs:~# cat /etc/sysctl.d/99-sgi-indy.conf
# The firmware of the SGI Indy can only access TCP ports up to
# 32767 when downloading files via TFTP, so take this into
# account.
net.ipv4.ip_local_port_range = 2048 32767

From the description it looks like I first needed this when testing with my first Indy, because this machine came into my hands only after the Octanes. But from your experience it looks like specific Octane firmware revisions have similar issues. Did you make a note of the original firmware revision of your Octane (i.e. before installing IRIX)?

LarBob wrote:once again, edit: I now have another problem. When I go to install system software and input 192.168.0.8 and /3/dist, it says it cannot load sa(sash64) --invalid argument. Shouldn't it be able to load fine if fx.64 could??
oh. okay. I restarted the tftp server and it magically started working!

Glad that you could solve your issues and were able to install IRIX via network - that's something I still have to try. :)
:Indy: :O2: :Octane: :Octane2: :O200: = :O200: - :O200: = :O200: (O200 cluster w/2 GIGAchannel cabinets)
[ ( hp ) ] 712/80 c3000 (dead) :hpserv: (J5600) c3700 c3750 c8000 rp2470 :rx2600: (rx2620) rx4640
| d | i | g | i | t | a | l | AXPpci33 AlphaStation 200 AlphaStation 255 PWS 500au AlphaServer DS20E AlphaServer DS25
C O B A L T Qube 2 Qube 3 RaQ RaQ 2 RaQ 4r RaQ XTR

User avatar
LarBob
Donor
Donor
Posts: 96
Joined: Sun Nov 13, 2016 6:43 am
Location: Kentucky, US

Re: Irix netinstall

Unread postby LarBob » Thu Aug 24, 2017 12:34 pm

johnnym wrote:
LarBob wrote:edit: this was just a simple case of sysctl -w net.ipv4.ip_local_port_range="2048 32767".

Good catch. Best is to make it permanent in a file in /etc/sysctl.d/ or a line in /etc/sysctl.conf:

Code: Select all

root@nfs:~# cat /etc/sysctl.d/99-sgi-indy.conf
# The firmware of the SGI Indy can only access TCP ports up to
# 32767 when downloading files via TFTP, so take this into
# account.
net.ipv4.ip_local_port_range = 2048 32767

From the description it looks like I first needed this when testing with my first Indy, because this machine came into my hands only after the Octanes. But from your experience it looks like specific Octane firmware revisions have similar issues. Did you make a note of the original firmware revision of your Octane (i.e. before installing IRIX)?

LarBob wrote:once again, edit: I now have another problem. When I go to install system software and input 192.168.0.8 and /3/dist, it says it cannot load sa(sash64) --invalid argument. Shouldn't it be able to load fine if fx.64 could??
oh. okay. I restarted the tftp server and it magically started working!

Glad that you could solve your issues and were able to install IRIX via network - that's something I still have to try. :)

Thanks for the help!
:Octane: Aezora - 2xR10k 250 MHz - 1 GB RAM - 6.5.30


Return to “Getting Started, Documentation, Tips & Tricks”

Who is online

Users browsing this forum: No registered users and 1 guest