uname -i not unique??

[Robert_Jewell]

I have two J6000's that are reporting the same ID from the uname -i command. I had thought that these were supposed to be unique for each system?

See this link for that info..

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xb07c3f490f4ed61190020090279cd0f9,00.html


Thanks,
Bob

[Paul Sperry]

This option cannot display
the unique machine identification number. For
getting the unique machine identification number
refer to the getconf command or confstr call

[Ramkumar Devanathan]

Bob,

The manpage does however mention this about the -i option for uname -

><
Print the machine identification number (system name if the machine identification number cannot be ascertained).
><

Is it that the machine identification no is unascertainable?

- ramd.

[Cheryl Griffin]

They should be unique. If not place a call to HW Support asking the HW CE to run SS_CONFIG to reset the identifier.

[Robert_Jewell]

First off thanks for the quick responses.

Paul - I am currently confirming what the getconf CS_MACHINE_IDENT command reports. Thank you.

Ramd. - Each system reports what looks like a valid number. The problem is that they are both the same.

Cheryl - I had thought that the ss_config/ss_update was only usable on any system that could be a 3000 system? I have also heard that having this run for this purpose was something that HP does not like to do? Perhaps that is outdated information.

-Bob

[Denver Osborn]

Cheryl deserves more points than that! :)

The best course of action you could take is to contact HP and have a CE run SS_Config to correct the problem. This tool can only be used by HP and is used to modify stable storage (prom) where this info is kept

-Denver

[Robert_Jewell]

Yes, I had meant to assign a 4, but I must have slipped with the mouse. If she replies again I will give her the extra points, sorry Cheryl :(

Anyway, thanks for the responses.

-Bob

[Michael Steele_2]

As you surmised.your system id and should be unique. Lots of things are tied to the system id, licensing for instance. Veritas Online JFS 3.3 immediately comes to mind.

Eventually, this will catch up to you if not corrected. Call HP and get a CE out their to set it right. Also call licensing and clarify the error with them for they may have crossed your two servers support agreements and are confusing everything.

[Bill Hassell · Accepted solution]

All HP 3000's and HP 9000's have unique system ID's and ss_config must be run to correct any errors. It is common for a repaired unit to have a new processor board with an unset value (perhaps a negative number) but the repair process requires setting the value to the unique number for this machine. The number is a combination of the serial number, processor info and model. Only an authorized HP repair person can run ss_config. Call HP to correct the problem.

[T G Manikandan]

You need to run 'ssconfig' to store a valid machine identification number.

Call up HP Customer Engr.

Thanks

[Robert_Jewell]

Thanks again for the details. I will see about getting HP to come out. Just seems strange that they would be the same value.

-Bob

[Bill McNAMARA_1]

the problem isn't yours in any case.
Sounds to be like you'll need the two done.

make sure the getconf MACHINE_IDENT is unique.

You may find on partitioned systems the uname -i returns similar 'keys' but the getconf will not.

really this is not a huge problem and you can make it work to your advantage with licences etc!.. It really should never happen. After all m/board replacements you should insist that the id is as it was before to ensure that apps that rely on that identifyier for licencing work again.

Later,
Bill

[Cheryl Griffin]

No problem Robert and Thank you Denver :0)