PymbleSoftware wrote:
Its not transferable between different model systems ..?
Looks like somebody <with balls-of-steel> is gonna have to be the first to try it <or at least the first on record>.......
PymbleSoftware wrote:
OK, I have started a wiki topic anyway...
Just looked at the wiki and it's mention of swapping the NIC from an Octane to a Fuel. I haven't looked at the system board of a Fuel close enough to be certain that there's not a number-in-a-can <too many air ducts and wires for a clear view>, but I was under the impression that if you wanted to change the sysid on any system with an L1 controller, all you need to do is plug in an L2 Controller preprogrammed with the desired local system serial number.
The local system serial number <in IP35 systems> is eight characters in length - a letter followed by seven digits. On most of the L1 equipped stuff I have <O300, O350 and Tezro - I'll have to fire up the Fuel to be certain>, the sysid is derived from the seven digits if the local system serial number - either as just the seven digit string or the seven digit string with a different leading alpha character. This process happens every time you link O3x0 modules with different local serial numbers <or connect a single compute module to an L2 controller with a different system serial number>. Its only fair to point out to anyone who might like to try this that there is a element of risk involved. The system type is at least in part derived from the leading alpha character <see
this thread and/or
this one for examples>, and I don't think I'd try a contrived serial number <just in case there's some sort of check digit in the serial number string>.
EDIT: While the serial number label on the rear of O300, O350 and Tezro are in the newer alpha + seven digit format mentioned above <e.g.
M1234567 in the case of the O3x0s and
P1234567 on the Tezro>, the Fuel does not use the same format for the local system serial number or sysid. The serial number label on the Fuel's rear bulkhead is in the same 080069xxxxxx <MAC address> format used by some of the earlier generation hardware, and the IRIX command sysid returns a portion of that string as the sysid.
When "serial all" is run on the Fuel L1 controller it includes the following reference to the MAC address in the 'EEPROM' section:
Code:
001a01-L1>serial all
Data Location Value
------------------------------ ------------ --------
Local System Serial Number EEPROM 08:00:69:10:xx:xx
Local Brick Serial Number EEPROM MMN520
Reference Brick Serial Number NVRAM MLS623
EEPROM Product Name Serial Part Number Rev T/W
---------- -------------- ---------- -------------------- --- ------
NODE IP34 MMN520 030_1707_003 H 00
MAC MAC ADDRESS NA NA NA NA
PIMM IP34PIMM MRS271 030_1730_001 G 00
XIO ASTODYV10 MVT940 030_1826_003 A 00
...and the L1 command eeprom includes a mention of the writing the Fuel EEPROM data to the MAC EEPROM:
Code:
001a01-L1>hlp eeprom
eeprom
show brick eeprom data.
eeprom <exp> <exp> <exp>
show brick eeprom data at <eeprom> <offset> <length>.
eeprom Fuel write default
write standard Fuel EEPROM data to MAC EEPROM
Until advised otherwise by someone with actual experience with the Fuel L1 command "eeprom Fuel write default", I'd suggest treading cautiously.
Login
Register
FAQ
Search
J5600, 2 x Mac, 3 x SUN, Alpha DS20E, Alpha 800 5/550, 3 x RS/6000, Amiga 4000 VideoToaster, Amiga4000 -030, 733MHz Sam440 AmigaOS 4.1 update 1. Tandem Himalaya S-Series Nonstop S72000 ServerNet. 
Octane R10000 225MHz, 2GB RAM, 1x36GB HDs, 21" monitor, SSI (no TRAM) graphics
