SGI: Hardware

Before I start I'd very much like to reiterate that I am *NOT* responsible for any damages resulting from the use or misuse of any information I provide on this forum nor am I responsible if your Origin suddenly becomes sentient and decides to take over the world.

Now that that's out of the way, onto some good stuff.

This all started when I had some problems with my R brick on my O300...the l1 wouldn't start (was getting the couldn't contact L1 error on the display). I'd experienced this before when the Dallas chip had either fallen out of it's socket (usually during shipping) or failed. I borrowed a Dallas chip from a spare fuel motherboard, since they both use the same type (DS1742W-120) and it fixed my issue, but also seemed to yield some additional unexpected fruit:



After seeing that, I set out to determine whether or not this could be reproduced, or if my serial number was simply corrupted when my R brick went haywire. I bought another R brick off of ebay and several of the previously mentioned Dallas DS174W-120 chips from quest components ( http://www.questcomp.com ).

Here's the procedure as I followed it:
I started by powering up the R brick and making sure it already had a serial number set:



As you can see, the Local system serial number and the serial from my L2 controller don't match.

After noting this, I proceeded to install one of the brand new chips in the router brick and reboot. The brick seemed to come up alright, but I wasn't sure how to address it from the L2 controller as the rack and brick numbers were now reading as ---r--- on the display. It didn't take me long to realize that the old fuel I had sitting in the corner would once again become useful. I pulled the chip out of the R brick, installed it in the fuel motherboard, attached to the fuels L1 serial port on the motherboard, and issued and did the following:



This set rack and slot numbers on the chip for me, so I then reinstalled it into the R brick and powered it up again with the following results:



And there you have it...from start to finish. Now clearly one doesn't have to use a fuel to set those parameters on the chip, if you look at the data sheet, it's quite simple to read/write/and even clear it. The Fuel was just the quickest means to an end that I could think of. If I get bored maybe I'll build a little device to program these things...or perhaps someone else wants to pick up the torch and run some more?

One further item, you'll notice in the log that there's some uninitialized data in there...it's probably a good idea to load the defaults after you've performed this, just to make sure all of the settings start at something reasonable.

I've been meaning to do this for awhile, and I apologize thoroughly for not getting to it sooner.

Please use this knowledge responsibly.
-Jesse

http://www.nekochan.net/wiki/ ... Origin_300



R.

Score. Thanks Regan!

-Jesse

holy crap, i am excited!

good work zerolapse!

Thanks dude!

-Jesse

Ok, so here's a simpler way to do it and all you need is a blank/new chip.

1. Power down your router brick
2. replace the chip with a new one
3. power up the router brick and connect it to your l2 controller, making sure that all of your serial numbers are already set how you need them
4. log into the l2 controller and do a config verbose and find the unit with no rack and slot id assigned like so:

Eos-001-L2>config verbose
L2 192.168.20.15: - 001 (IR 80a8140f, C 00000000) (LOCAL)
L1 192.168.20.15:2:0 - 001c07 (b1;p2/1;d4 /dev/sgil1_2)
L1 192.168.20.15:1:0 - 001c06 (b1;p1;d2 /dev/sgil1_1)
L1 192.168.20.15:4:0 - 001c03 (b1;p2/4;d6 /dev/sgil1_4)
L1 192.168.20.15:3:0 - 001c01 (b1;p2/2;d5 /dev/sgil1_3)
L1 192.168.20.15:0:0 - ---r-- (no rack and slot ID set) (b2;p2/1;d3 /dev/sgil1_0)
L2 Clients:
127.0.0.1: (IR 8aa8140f) sgi (sgi) @ localhost running 'l2part'
127.0.0.1: (IR 86a8140f) sgi (sgi) @ localhost running 'l2gui'
127.0.0.1: (IR 88a8140f) sgi (sgi) @ localhost running 'l2flash'

5. in the output to the right of the unit with no slot id you'll notice sgil1_0, the number at the end is the port number, in this case 0
6. issue the command :portnumber:0 brick rackslot 1 27 (or whatever you want it set to) and then :portnumber:0 reboot_l1 like so:



7. Profit!!

Thanks!

http://www.nekochan.net/wiki/ ... her_update

R.

Time to resurrect this well aged thread...

I just confirmed that this procedure works for CX bricks with serial security enabled

*Highfive!* Thanks for reporting on that!

-Jesse