Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1004615.1
Update Date:2012-10-11
Keywords:

Solution Type  Problem Resolution Sure

Solution  1004615.1 :   Sun Fire[TM] 12K/15K/E20K/E25K: IDPROM layout for OpenBoot PROM failed  


Related Items
  • Sun Fire 15K Server
  •  
  • Sun Fire E20K Server
  •  
  • Sun Fire E25K Server
  •  
  • Sun Fire 12K Server
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-Exxk
  •  
  • .Old GCS Categories>Sun Microsystems>Servers>High-End Servers
  •  

PreviouslyPublishedAs
206401


Applies to:

Sun Fire 12K Server - Version All Versions and later
Sun Fire 15K Server - Version All Versions and later
Sun Fire E20K Server - Version All Versions and later
Sun Fire E25K Server - Version All Versions and later
All Platforms

Symptoms

In the platform messages, and the messages of the affected domain, one or more of the following symptoms can be found:

mand : Network IP information layout for MAN failed: ecode=1

osd : Write REBOOTARGS file failed 13
osd : Read REBOOTARGS file failed 4716
osd : file open failed: file=/var/opt/SUNWSMS/SMS1.6/data/O/nextbootpath, ecode=13
osd : Read IDPROM file failed 1
osd : file open failed: file=/var/opt/SUNWSMS/SMS1.6/data/O/nvramdata, ecode=13
osd : chmod failed: file=/var/opt/SUNWSMS/SMS1.6/data/O/nvramdata, mode=384, ecode=1

dsmd : send event failed: event=400, text=14, ecode=1
dsmd : IDPROM layout for OpenBoot PROM failed: ecode=1
dsmd : send event failed: event=401, text=14, ecode=4716
dsmd : Reboot arguments layout for OpenBoot PROM failed: ecode=4716
dsmd : Setting boot string for next boot failed, rc = 13

setkeyswitch: send event failed: event=400, text=14, ecode=1
setkeyswitch: IDPROM layout for OpenBoot PROM failed: ecode=1
setkeyswitch: send event failed: event=401, text=14, ecode=4716
setkeyswitch: Reboot arguments layout for OpenBoot PROM failed: ecode=4716

 


When booting the domain, the banner can look like this:

Sun Fire E25K, using IOSRAM based Console
Copyright 2009 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.30.4, 16384 MB memory installed, Serial #0.
Ethernet address 0:0:0:0:0:0, Host ID: 00000000.


The IDPROM contents are invalid

{160} ok

 


On the domain, idprom information in the prtconf output has all zeros:

# prtconf -pv|grep idprom
   idprom:  00000000.00000000.00000000.00000000.00000000.00000000.00000000.00000000
       device_type:  'idprom'
       name:  'idprom'    idprom:  00000000.00000000.00000000.00000000.00000000.00000000.00000000.00000000
        device_type:  'idprom'
        name:  'idprom'
#


On the domain, the hostid command can fail:

# hostid
bad hostid format
 
#

 

Changes

This error would be seen when configuring a new domain or at time of a domain boot of an existing domain.

Cause

If this error occurs during setkeyswitch of a previously configured domain, then the possibility of idprom.image file corruption exists, or improper file permissions / ownership exists on the file or the directory where it resides.

Solution

Troubleshooting

From the SC, execute 'sysid -d[a-r]'. Verify expected output similar to:

sms-svc> sysid -da

IDPROM in /var/opt/SUNWSMS/data/A/idprom.image for domain A

Format = 0x01
Machine Type = 0x82
Ethernet Address = 0:0:be:a8:4:be
Manufacturing Date = Thu Oct 11 20:24:00 BST 2001
Serial number (Host ID) = 0xa804be (11011262)
Checksum = 0xe2



If the sysid command fails with 'error reading IDPROM', verify that these files are in the right domain location,
specifically the idprom.image file:

sms-svc> cd /var/opt/SUNWSMS/data/[A-R]
sms-svc> ls -al
total 28
drwxrwx---+  2 root             sms           512 Jan  9 16:58 .
drwxrwxr-x+ 22 root             sms           512 Mar 11 17:49 ..
-rw-r--r--   1 sms-osd          bin           269 Oct 11 19:39 bootparamdata
-rw-r--r--   1 sms-osd          bin            32 Oct 11 20:24 idprom.image
-rw-r--r--   1 sms-osd          bin          8192 Oct 11 19:39 nvramdata

If the idprom.image file exists, verify that the permissions and ownership and directory structure matches those listed above.

 

If the permissions are incorrect, the domain banner will not have a hostid and not have an ethernet address:

{160} ok banner

Sun Fire E25K, using IOSRAM based Console
Copyright 2009 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.30.4, 16384 MB memory installed, Serial #0.
Ethernet address 0:0:0:0:0:0, Host ID: 00000000.


The IDPROM contents are invalid

{160} ok

 
If the permissions are incorrect, and the domain is booted, the hostid command will fail:

# hostid
bad hostid format
 
#

 
If the permissions are correct, the file may be corrupted and must be restored.
If the file does not exist, then the idprom.image file must be restored or recreated.

 

Resolution

If the files listed above do not exist in the location listed above, check the location on the spare SC to determine if the files exist and copy them over to the main SC.
If the files listed above do not exist in the location listed above on either SC, recover them from a previous smsbackup using the smsrestore utility.
If a previous Explorer has been run, check its contents for the files in question and recover to the location on the SC.


If file recovery fails, you can either seek for help in the Oracle Sparc Enterprise Servers community or contact Oracle Support for assistance with generating a new set of 18 idprom.image files for the domains.

For generating new idprom.image files youneed to supply the first MAC address for that system (it is printed on the yellow customer info sheets that ship with the system).

 

How to generate idprom.images on Sun Fire[TM] 12K - E25K (Doc ID 1008184.1)

 

References

System Management Software (SMS) Administrator Guide

 

 

Additional background information

It is possible to recreate the idprom.image file using the sys_id command.  However, you will need the system serial number and domain MAC address, from which the hostid can be determined.  For example, to create a new idprom.image file with domain R MAC address/system serial number:

sms-svc> sysid -d r -e 0:0:be:a8:4:a7 -s 143A2008
sms-svc> sysid -d r

IDPROM in /var/opt/SUNWSMS/data/R/idprom.image for domain R

Format = 0x01
Machine Type = 0x82
Ethernet Address = 0:0:be:a8:4:a7
Manufacturing Date = <NOT YET MANUFACTURED>
Serial number (Host ID) = 0x00008f (143)
Checksum = 0xb9


<add hostid>

sms-svc> sysid -d r -H 0xa804a7
sms-svc> sysid -d r

IDPROM in /var/opt/SUNWSMS/data/R/idprom.image for domain R

Format = 0x01
Machine Type = 0x82
Ethernet Address = 0:0:be:a8:4:a7
Manufacturing Date = <NOT YET MANUFACTURED>
Serial number (Host ID) = 0xa804a7 (11011239)
Checksum = 0x3d

sms-svc> sysid -d r -m 200110292105


<this adds the date>

 
NOTE: the -m option means manufacturing date. The number following is

2001 10 29 21 05
^^^^ ^^ ^^ ^^ ^^

Year Month Day HH MM

sms-svc> sysid -d r

IDPROM in /var/opt/SUNWSMS/data/R/idprom.image for domain R

Format = 0x01
Machine Type = 0x82
Ethernet Address = 0:0:be:a8:4:a7
Manufacturing Date = Mon Oct 29 21:05:00 GMT 2001
Serial number (Host ID) = 0xa804a7 (11011239)
Checksum = 0x63
sms-svc>

 


Internal Comments

None.

starcat, 15k, 12k, e20k, e25k, idprom.image, sysid
Previously Published As
48144

 Keywords: idprom, hostid, mac, sms


Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback