[jwhat]

Hi kokoboi,

I know that you are sure that this is not related to DS1742W battery, but to verify serial "stickiness" can you print out the L1 log, after powering down (removing from power completely) and then up.

If the machine is re-initialising the serial as part of L1 startup then it will be in the L1 log.

If it is resetting the serial you will see something like this:

>> M200XXXX-192.168.XXX.XXX-L2>l1 log
>> 001c07:
>> 11/01/20 23:41:34 checksum Error - common header initialized
>> 11/01/20 23:41:34 nvram checksum error - initializing core data.
>> 11/01/20 23:41:34 nvram checksum error - initializing extended data.
>> 11/01/20 23:41:34 nvram checksum error - log pointers invalid, log pointers reset
>> 11/01/20 23:41:34 L1 booting 1.44.0
>> 11/01/20 23:41:34 ChiServ IP59
>> 11/01/20 23:41:34 Checking for Type
>> 11/01/20 23:41:34 -- ChiServ Type set
>> 11/01/20 23:41:36 ** fixing invalid SSN value
>> 11/01/20 23:41:36 ** fixing BSN mismatch
>> 11/01/20 23:41:36 USB0: waiting on open
>> 11/01/20 23:41:41 USB0: opened
>> 11/01/20 23:41:41 USB0: registered for events
>> 11/01/20 23:41:42 INFO: System serial number reassigned (8000) to M200XXXX from attached L2.
>> 11/01/20 23:43:37 L1 booting 1.44.0
>> 11/01/20 23:43:37 ChiServ IP59
>> 11/01/20 23:43:37 Checking for Type
>> 11/01/20 23:43:37 -- ChiServ Type set
>> 11/01/20 23:43:40 USB0: waiting on open
>> 11/01/20 23:43:41 USB0: opened
>> 11/01/20 23:43:41 USB0: registered for events

I say "something like" as this was from O350 node, which reports as "ChiServ" and took on the serial from the NUMALINK connected machines.

Cheers from Oz,

jwhat/John.