Jumpstart installation from Solaris 10 zone

Hi,
I am using a Sol 10 zone as a jumpstart server, and have encountered a problem.
Due to not being able to use the out-of-the-box nfs server, as it does not run in a local zone on Sol 10, I have looked at using a user-space nfs server, unfsd.
unfsd runs fine, and can be used by a client to nfs-mount a directory, but when it comes to using the client's flash archive to build the client, I get this error below in my snoop output:
10:54:46.04754 js-client -> js-server MOUNT3 C Mount /flash_archives/TEST/js-client.flar
10:54:46.04779 js-server -> js-client MOUNT3 R Mount Not a directory
Which implies to me that the jumpstart client is trying to nfs-mount a file, and unfsd does nto allow this.
Any advice/suggestions on how to resolve this would be appreciated.
Richard.
Edited by: Richard on Jun 22, 2012 8:51 AM

Just to provide an update.
I switched to using ftp to get the flar file from the jumpstart server, which works fine.
I do believe that the issue with NFS is because the Solaris in-built NFS will allow a file to be NFS-mounted, but the user-space NFS daemon I used ( unfsd ) does not allow this, although I've not done sufficient snooping to prove this.
Richard.

Similar Messages

Warning: Solaris 10 x86 jumpstart (grub) from Solaris 8 server

Hi all,
I'm just posting this here in case someone comes across the same problem I did.
When trying to do a custom jumpstart installation on x86 boxes from a Solaris 8 SPARC server, Grub was failing to do TFTP of the "multiboot" and "x86.miniroot" files. A snoop of the traffic would reveal some "TFTP Error: not defined" packets.
Turns out this is a known bug:
http://sunsolve.sun.com/search/document.do?assetkey=1-1-6395719-1
The bug doesn't make any reference to jumpstart, and because of this it took me a while to find it.
I copied the in.tftpd binary from a Solaris 9 box, and it worked like a charm. (Would it be very difficult to issue a Solaris 8 patch?)
kind regards,

Here is the error output:
# ./add_install_client -i 192.168.1.51 -c sun1:/jumpstart/ -p sun1:/jumpstart/Sysidcfg/Solaris_10-intel/ host2 i86pc
unmount: warning: /tftboot/I86PC.Solaris_10-1 not in mnttab
unmount: /tftpboot/I86PC.Solaris_10-1 no such file or directory
mount: Mount point /tftboot.I86PC.Solaris_10-1 does not exist.
cleaning up preexisting install client "host2"
removing host2 from bootparams
rm: /tftboot/ is a directory
updating /etc/bootparams
ln: cannot create /tftpboot//pxegrub.I86PC.Solaris_10-1: File exists
Create a grub boot flloppy and edit GRUB menu to contain
the following entry:
title Solaris netinstall
rarp
kernel /I86PC.Solaris_10-1/multiboot kernel/unix -B install_media=192.168.1.100:/jumpstart/OS/intel
module /I86PC.Solaris_10-1/x86.miniroot
------------- end ---------------
So, I have tried this with the -i, -e -i+-e, with -s and without.
I have an entry in /etc/ethers and /etc/hosts. However, I don't think it is a FQDN or simular issue. Looks like a script issue.
/tftpboot/ ends up with
boot/
nbp. -> pxegrub.I86PC.Solaris_10-1
pxegrub.I86PC.Solaris_10-1
rm.192.168.1.51
/tftpboot/boot/
grub/
/tftpboot/boot/grub/
menu.1st
# cat menu.1st
default 0
timeout=30
title Solaris_10 jumpstart
kernel /i86PC.Solaris_10-1/multiboot kernel/unix -B install_config=192.168.1.100:/jumpstart,sysid_config=192.168.1.100:/jumpstart/Sysidcfg/Solaris_10-1-intel/,install_media=192.168.1.100:/jumpstart/OS/intel
module /I86PC.Solaris_10-1/x86.miniroot
---- end ----
Thanks for the help.
Aaron

SAP AS JAVA installation in Solaris Zone envirn throws OUT of Memory error.

Hi,
We are installing SAP NW2004s 7.0 SR3 AS JAVA on Solaris 10 in zone environment. Thsi was prod server getting build where on top of this we will install GRC 5.3.
We have faced no issues in development build.
But during the Prod build at databse create step, we are getting the below error
ORA-27102: out of memory
SVR4 Error: 22: Invalid argument
Disconnected
SAPinst log entries where error messages started:
04:43:58.128
Execute step createDatabase of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0
INFO 2011-04-01 04:45:14.590
Working directory changed to /tmp/sapinst_exe.16718.1301647358.
INFO 2011-04-01 04:45:14.595
Working directory changed to /tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS.
INFO 2011-04-01 04:45:14.609
Working directory changed to /tmp/sapinst_exe.16718.1301647358.
INFO 2011-04-01 04:45:14.621
Working directory changed to /tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS.
INFO 2011-04-01 04:45:14.850
Account oraac5 already exists.
INFO 2011-04-01 04:45:14.852
Account dba already exists.
INFO 2011-04-01 04:45:14.852
Account oraac5 already exists.
INFO 2011-04-01 04:45:14.853
Account dba already exists.
INFO 2011-04-01 04:45:14.867
Working directory changed to /tmp/sapinst_exe.16718.1301647358.
INFO 2011-04-01 04:45:14.899
Working directory changed to /tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS.
ERROR 2011-04-01 04:45:32.280
CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-27102: out of memory
SVR4 Error: 22: Invalid argument
Disconnected
. SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
ERROR 2011-04-01 04:45:32.286
MUT-03025 Caught ESAPinstException in Modulecall: ORA-27102: out of memory
SVR4 Error: 22: Invalid argument
Disconnected
ERROR 2011-04-01 04:45:32.453
FCO-00011 The step createDatabase with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0|createDatabase was executed with status ERROR ( Last error reported by the step :Caught ESAPinstException in Modulecall: ORA-27102: out of memory
SVR4 Error: 22: Invalid argument
Disconnected
ora_sql_results.log
04:45:15 SAPINST ORACLE start logging for
SHUTDOWN IMMEDIATE;
exit;
Output of SQL executing program:
SQL*Plus: Release 10.2.0.4.0 - Production on Fri Apr 1 04:45:15 2011
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
Disconnected
SAPINST: End of output of SQL executing program /oracle/AC5/102_64/bin/sqlplus.
SAPINST found errors.
SAPINST The current process environment may be found in sapinst_ora_environment.log.
2011-04-01, 04:45:15 SAPINST ORACLE stop logging
================================================================================
2011-04-01, 04:45:15 SAPINST ORACLE start logging for
STARTUP NOMOUNT;
exit;
Output of SQL executing program:
SQL*Plus: Release 10.2.0.4.0 - Production on Fri Apr 1 04:45:15 2011
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
ORA-27102: out of memory
SVR4 Error: 22: Invalid argument
Disconnected
SAPINST: End of output of SQL executing program /oracle/AC5/102_64/bin/sqlplus.
SAPINST found errors.
SAPINST The current process environment may be found in sapinst_ora_environment.log.
2011-04-01, 04:45:32 SAPINST ORACLE stop logging
Already viewed S-note
724713 - parameter settings for Solaris 10 - (Parameters are set as per this note)
743328 - Composite SAP note: ORA-27102 - (no much information in memory problem on zones)
Please provide your suggestions/resolution.
Thankyou.

Hi,
@ Sunny: Thanks for response, the referred note was already checked and parameters are in sync as per note.
@Mohit: SAP wouldn't proceed till create database if Oracle software was not installed. thanks for the response.
@Markus: Thanks I agree with you, but I have doubt in this area. Isn't it like project.max-shm-memory was new parameter we need to set in local zone rather using shmsys:shminfo_shmmax in /etc/system. Do we need to still maintain this parameter in /etc/system in global zone.
As per SUN doc below parameter was obsolete from Solaris 10.
The following parameters are obsolete.
■ shmsys:shminfo_shmmni
■ shmsys:shminfo_shmmax
As per your suggestion, do we need to set below parameters in that case, please clarify.
Parameter                           Replaced by Resource Control      Recommended Value
semsys:seminfo_semmni   project.max-sem-ids                      100
semsys:seminfo_semmsl   process.max-sem-nsems               256
shmsys:shminfo_shmmax project.max-shm-memory             4294967295
shmsys:shminfo_shmmni   project.max-shm-ids                       100
Also   findings of /etc/release
more /etc/release
Solaris 10 10/08 s10s_u6wos_07b SPARC
Regards,
Sitarama.

Access manager installation on solaris zone

Hi
I have installed the Access manager 7.0, Sun java system app server 8.1, Sun sirectory server 5.2 through JES installer on solaris 10 zone AM55-zone. Installer summarry is below, which shows installtion complete without error, but I am not able to launch the amserver login page.
Any suggestion, what I did wrong? any thoughts?
Sid
Installation Complete
Software installation has completed successfully. You can view the installation
summary and log by using the choices below. Summary and log files are available
in /var/sadm/install/logs/.
Your next step is to perform the postinstallation configuration and
verification tasks documented in the Postinstallation Configuration and Startup
Chapter of the Sun Java(TM) Enterprise System Installation Guide. See: http:
//docs.sun.com/doc/819-2328.
Enter 1 to view installation summary and Enter 2 to view installation logs
[1] {"!" exits} 1
Installation Summary Report
Install Summary
Java Enterprise System : Installed
Sun Java(TM) System Message Queue 3 2005Q4 Enterprise Edition : Installed
Sun Java(TM) System Application Server Enterprise Edition 8.1 2005Q4 : Installed
Sun Java(TM) System Directory Preparation Tool : Installed
Sun Java(TM) System Directory Server 5 2005Q4 : Installed
Sun Java(TM) System Access Manager 7 2005Q4 : Installed
Configuration Data
Sun Java(TM) System Application Server Enterprise Edition 8.1 2005Q4 :
Domains and Instance Configuration Directory : /var/opt/SUNWappserver
Application Server Installation Directory : /opt/SUNWappserver
Sun Java(TM) System Directory Preparation Tool :
Directory Preparation Tool Installation Directory : /opt/SUNWcomds
Sun Java(TM) System Directory Server 5 2005Q4 :
Directory Server Admin User : admin
Directory Server Manager : cn=Directory Manager
Directory Server Identifier : AM55-zone
Directory Server Port : 389
Directory Server Root Suffix : dc=ipsolutionshowcase,dc=com
<--[33%]--[ENTER To Continue]--[n To Finish]--> {"!" exits}
Directory Server Administration Domain : ipsolutionshowcase.com
System User : root
System Group : root
Existing Configuration Directory : 0
Configuration Directory Host : AM55-zone.ipsolutionshowcase.com
Configuration Directory Port : 389
Configuration Directory Admin User : admin
Existing User Directory : 0
User Directory Host : AM55-zone.ipsolutionshowcase.com
User Directory Port : 389
User Directory Admin User : admin
User Directory Suffix : dc=ipsolutionshowcase,dc=com
Disable Schema Checking : 0
Add Sample Entries : 0
Populate Database : 1
Sun Java(TM) System Access Manager 7 2005Q4 :
Access Manager Installation Directory : /opt
Access Manager Protocol : http
Access Manager Port : 8080
LDAP User ID : amldapuser
<--[66%]--[ENTER To Continue]--[n To Finish]--> {"!" exits}
Administrator User ID : amAdmin
Web Container : AppServer
Access Manager Application Server Installation Directory :
/opt/SUNWappserver/appserver
Document Root : /var/opt/SUNWappserver/domains/domain1/docroot
Access Manager Console Host (for Existing console) : AM55-zone.
ipsolutionshowcase.com
Access Manager Console Deploy URI : amconsole
Access Manager Password Deploy URI : ampassword
Access Manager Host : AM55-zone.ipsolutionshowcase.com
Access Manager Services Deploy URI : amserver
Access Manager Cookie Domain List : .ipsolutionshowcase.com
Access Manager Common Domain Deploy URI : amcommon
Access Manager Directory Server Host Name : AM55-zone
Access Manager Directory Server Host : AM55-zone.ipsolutionshowcase.com
Access Manager Directory Server Port : 389
Access Manager Directory Root Suffix : dc=ipsolutionshowcase,dc=com
Access Manager Directory Manager DN : cn=Directory Manager
Organization Marker Object Class : sunISManagedOrganization
User Marker Object Class : inetorgperson
Organization Naming Attribute : o
User Naming Attribute : uid
<--[100%]--[ENTER To Continue]--[n To Finish]--> {"!" exits}
Enter 1 to view installation summary and Enter 2 to view installation logs
[1] {"!" exits} !
You have new mail in /var/mail/root
bash-3.00#
bash-3.00# cd /var/opt/mps/serverroot/slapd-AM55-zone
bash-3.00# ./start-slapd

Thanks samk,
After the installation, I have started the Directory server,admin,and console with following commands:
bash-3.00# directoryserver start
bash-3.00# directoryserver start-admin
SunONE-WebServer-Enterprise/6.0SP3 B05/19/2004 02:48
warning: daemon is running as super-user
[LS ls1] http://AM55-zone.ipsolutionshowcase.com <http://AM55-zone.ipsolutionshowcase.com> , port 390 ready to accept requests
startup: server started successfully
bash-3.00# directoryserver startconsole
Recieved the Login console window,logged in and got the ipsolutionshowcase tree.
What are the next steps I need to folow in order to launch the Access Manager page?
Ant thoughts?
Thanks for ye help
Sid

'flash_reboot_processing' file error while Sol9/05 jumpstart installation

I do Solaris 9/05 jumpstart installation from flash image. I have the following error:
Extracted 621.00 MB ( 99% of 622.37 MB archive)
Extracted 622.00 MB ( 99% of 622.37 MB archive)
Extracted 622.37 MB (100% of 622.37 MB archive)
Extraction complete
Postdeployment processing
No local customization defined
cp: cannot create /a/etc/init.d/flash_reboot_processing: No such file or directory
Can not set reboot customization scripts
ERROR: Error while processing system postdeployment script
ERROR: Postdeployment processing failure
ERROR: Flash installation failed
So when I reboot the server it says:
Boot device: /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w500000e0112b7631,0:b File and args:
Boot load failed.
The file just loaded does not appear to be executable.
I guess maybe it is connected with
http://docs.sun.com/app/docs/doc/817-3804/6mjcffkoi?a=view
on some way ..
Please help.

I get the same error message after Solaris10 6/06 WAN Boot installation.
Extraction complete
Postdeployment processing
No local customization defined
cp: cannot create /a/etc/init.d/flash_reboot_processing: No such file or directory
Can not set reboot customization scripts
ERROR: Error while processing system postdeployment script
ERROR: Postdeployment processing failure
ERROR: Flash installation failed
Has anyone successfully completed a Solaris 10 6/06 WAN boot installation?
I have found that most of the Solaris 10 WAN Boot Install documentation has been incorrect on out of date. I have had to modify and rebuild my configuration files and webserver many times after each new error encountered. Going on two weeks that I have been at this. This is crazy...

Zfs core dumps in Solaris Zones after patchcluster installation

Hi
I've installed the recommended patch cluster for Solaris 10 (SPARC) on my T2000 Server.
Now after the reboot all the Solaris Zones (got about 10 of them) instantly do zfs core dumps when their booted.
Some Output:
Dec 15 15:34:43 XXXXX genunix: NOTICE: core_log: zfs[1711] core dumped: /var/core/core_XXXXXX_zfs_0_0_1292423682_1711
bash-3.00# svcs
STATE STIME FMRI
online 13:58:50 svc:/system/svc/restarter:default
online 13:58:51 svc:/system/filesystem/root:default
online 13:58:51 svc:/network/loopback:default
online 13:58:53 svc:/network/pfil:default
online 13:58:54 svc:/system/installupdates:default
online 13:58:55 svc:/system/boot-archive:default
online 13:58:56 svc:/network/physical:default
online 13:58:57 svc:/system/filesystem/usr:default
online 13:58:57 svc:/system/identity:node
online 13:58:58 svc:/system/device/local:default
online 13:58:58 svc:/system/keymap:default
online 13:58:58 svc:/milestone/devices:default
online 13:58:58 svc:/system/filesystem/minimal:default
online 13:58:58 svc:/system/rmtmpfiles:default
online 13:58:58 svc:/system/cryptosvc:default
online 13:58:59 svc:/system/identity:domain
online 13:58:59 svc:/system/name-service-cache:default
online 13:58:59 svc:/system/coreadm:default
online 13:58:59 svc:/network/ipsec/ipsecalgs:default
online 13:58:59 svc:/application/print/ppd-cache-update:default
online 13:58:59 svc:/network/ipsec/policy:default
online 13:59:00 svc:/milestone/network:default
online 13:59:00 svc:/network/initial:default
online 13:59:00 svc:/system/manifest-import:default
online 13:59:00 svc:/network/service:default
online 13:59:00 svc:/milestone/single-user:default
online 13:59:00 svc:/network/dns/client:default
online 13:59:00 svc:/network/routing-setup:default
online 13:59:00 svc:/milestone/name-services:default
online 13:59:03 svc:/milestone/sysconfig:default
online 13:59:03 svc:/system/utmp:default
online 13:59:03 svc:/system/console-login:default
offline 13:58:51 svc:/system/sysidtool:net
offline 13:58:51 svc:/network/rpc/bind:default
offline 13:58:51 svc:/system/sysidtool:system
offline 13:58:52 svc:/network/nfs/status:default
offline 13:58:52 svc:/network/nfs/nlockmgr:default
offline 13:58:52 svc:/network/nfs/cbd:default
offline 13:58:52 svc:/network/nfs/mapid:default
offline 13:58:52 svc:/network/inetd:default
offline 13:58:52 svc:/network/nfs/client:default
offline 13:58:52 svc:/system/filesystem/autofs:default
offline 13:58:53 svc:/system/system-log:default
offline 13:58:53 svc:/network/smtp:sendmail
offline 13:58:53 svc:/system/cron:default
offline 13:58:53 svc:/milestone/multi-user:default
offline 13:58:54 svc:/application/management/snmpdx:default
offline 13:58:54 svc:/application/management/dmi:default
offline 13:58:54 svc:/application/management/seaport:default
offline 13:58:54 svc:/network/ssh:default
offline 13:58:54 svc:/milestone/multi-user-server:default
offline 13:58:54 svc:/application/font/fc-cache:default
offline 13:58:55 svc:/application/management/sma:default
offline 13:58:58 svc:/system/sac:default
offline 13:59:00 svc:/network/shares/group:default
offline 13:59:00 svc:/system/boot-archive-update:default
maintenance 15:34:43 svc:/system/filesystem/local:default
uninitialized 13:58:52 svc:/network/rpc/gss:default
uninitialized 13:58:54 svc:/application/font/stfsloader:default
uninitialized 13:58:55 svc:/network/rpc/rstat:default
uninitialized 13:58:55 svc:/application/print/rfc1179:default
uninitialized 13:58:55 svc:/application/x11/xfs:default
uninitialized 13:58:55 svc:/network/finger:default
uninitialized 13:58:55 svc:/network/ftp:default
uninitialized 13:58:56 svc:/network/login:rlogin
uninitialized 13:58:56 svc:/network/nfs/rquota:default
uninitialized 13:58:56 svc:/network/rpc/rusers:default
uninitialized 13:58:56 svc:/network/rpc/smserver:default
uninitialized 13:58:57 svc:/network/security/ktkt_warn:default
uninitialized 13:58:57 svc:/network/shell:default
uninitialized 13:58:57 svc:/network/telnet:default
uninitialized 13:58:58 svc:/network/rpc-100235_1/rpc_ticotsord:default
uninitialized 13:58:58 svc:/network/rpc/cde-calendar-manager:default
uninitialized 13:58:59 svc:/network/rpc/cde-ttdbserver:tcp
bash-3.00# svcs -x
svc:/system/filesystem/local:default (local file system mounts)
State: maintenance since Wed Dec 15 15:34:43 2010
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/system-filesystem-local:default.log
Impact: 24 dependent services are not running. (Use -v for list.)
svc:/network/rpc/gss:default (Generic Security Service)
State: uninitialized since Wed Dec 15 13:58:52 2010
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: gssd(1M)
Impact: 11 dependent services are not running. (Use -v for list.)
svc:/network/rpc/rstat:default (kernel statistics server)
State: uninitialized since Wed Dec 15 13:58:55 2010
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: rpc.rstatd(1M)
See: rstatd(1M)
Impact: 1 dependent service is not running. (Use -v for list.)
bash-3.00# cat /var/svc/log/system-filesystem-local:default.log
[ Jul 10 03:41:35 Enabled. ]
[ Jul 10 03:43:45 Rereading configuration. ]
[ Jul 10 03:44:17 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 03:44:18 Method "start" exited with status 0 ]
[ Jul 10 12:44:36 Enabled. ]
[ Jul 10 12:44:45 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 12:44:45 Method "start" exited with status 0 ]
[ Jul 10 12:45:03 Enabled. ]
[ Jul 10 12:45:09 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 12:45:09 Method "start" exited with status 0 ]
[ Jul 10 13:54:39 Enabled. ]
[ Jul 10 13:54:46 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 13:54:46 Method "start" exited with status 0 ]
[ Jul 18 12:34:19 Enabled. ]
[ Jul 18 12:34:27 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 18 12:34:27 Method "start" exited with status 0 ]
[ Jul 18 17:29:08 Enabled. ]
[ Jul 18 17:29:15 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 18 17:29:15 Method "start" exited with status 0 ]
[ Jul 19 11:13:34 Enabled. ]
[ Jul 19 11:13:42 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 11:13:42 Method "start" exited with status 0 ]
[ Jul 19 11:32:23 Enabled. ]
[ Jul 19 11:32:30 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 11:32:31 Method "start" exited with status 0 ]
[ Jul 19 11:57:06 Enabled. ]
[ Jul 19 11:57:13 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 11:57:13 Method "start" exited with status 0 ]
[ Jul 19 12:40:05 Enabled. ]
[ Jul 19 12:40:12 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 12:40:12 Method "start" exited with status 0 ]
[ Jul 20 15:51:46 Enabled. ]
[ Jul 20 15:51:54 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 20 15:51:54 Method "start" exited with status 0 ]
[ Jul 24 11:42:17 Enabled. ]
[ Jul 24 11:42:25 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 24 11:42:25 Method "start" exited with status 0 ]
[ Jul 27 12:05:06 Stopping because service disabled. ]
[ Jul 27 12:05:07 Executing stop method (null) ]
[ Jul 27 12:13:10 Enabled. ]
[ Jul 27 12:13:17 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 27 12:13:17 Method "start" exited with status 0 ]
[ Jul 27 13:10:26 Stopping because service disabled. ]
[ Jul 27 13:10:26 Executing stop method (null) ]
[ Jul 27 13:18:19 Enabled. ]
[ Jul 27 13:18:26 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 27 13:18:26 Method "start" exited with status 0 ]
[ Jul 31 10:12:31 Enabled. ]
[ Jul 31 10:12:38 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 31 10:12:39 Method "start" exited with status 0 ]
[ Aug 7 10:08:52 Stopping because service disabled. ]
[ Aug 7 10:08:52 Executing stop method (null) ]
[ Aug 7 10:34:50 Enabled. ]
[ Aug 7 10:34:57 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 7 10:34:58 Method "start" exited with status 0 ]
[ Aug 9 09:14:50 Stopping because service disabled. ]
[ Aug 9 09:14:50 Executing stop method (null) ]
[ Aug 9 09:55:03 Enabled. ]
[ Aug 9 09:55:10 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 9 09:55:11 Method "start" exited with status 0 ]
[ Aug 16 10:46:43 Enabled. ]
[ Aug 16 10:46:50 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 10:46:50 Method "start" exited with status 0 ]
[ Aug 16 12:06:56 Enabled. ]
[ Aug 16 12:07:02 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 12:07:02 Method "start" exited with status 0 ]
[ Aug 16 13:45:10 Enabled. ]
[ Aug 16 13:45:16 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 13:45:16 Method "start" exited with status 0 ]
[ Aug 16 14:36:59 Enabled. ]
[ Aug 16 14:37:07 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 14:37:07 Method "start" exited with status 0 ]
[ Aug 16 15:00:40 Enabled. ]
[ Aug 16 15:00:47 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 15:00:47 Method "start" exited with status 0 ]
[ Aug 22 16:00:13 Enabled. ]
[ Aug 22 16:00:21 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 22 16:00:21 Method "start" exited with status 0 ]
[ Aug 23 09:49:04 Enabled. ]
[ Aug 23 09:49:10 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 23 09:49:11 Method "start" exited with status 0 ]
[ Aug 23 09:49:23 Stopping because service disabled. ]
[ Aug 23 09:49:23 Executing stop method (null) ]
[ Aug 23 10:04:13 Enabled. ]
[ Aug 23 10:04:20 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 23 10:04:20 Method "start" exited with status 0 ]
[ Aug 23 10:06:57 Enabled. ]
[ Aug 23 10:07:04 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 23 10:07:05 Method "start" exited with status 0 ]
[ Oct 23 08:43:05 Enabled. ]
[ Oct 23 08:43:14 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Oct 23 08:43:14 Method "start" exited with status 0 ]
[ Nov 21 14:51:50 Enabled. ]
[ Nov 21 14:51:58 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Nov 21 14:51:59 Method "start" exited with status 0 ]
[ Nov 29 15:33:19 Enabled. ]
[ Nov 29 15:33:26 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Nov 29 15:33:27 Method "start" exited with status 0 ]
[ Dec 18 13:37:35 Enabled. ]
[ Dec 18 13:37:42 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 18 13:37:42 Method "start" exited with status 0 ]
[ Dec 19 08:48:07 Enabled. ]
[ Dec 19 08:48:14 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 19 08:48:14 Method "start" exited with status 0 ]
[ Dec 19 08:56:07 Enabled. ]
[ Dec 19 08:56:14 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 19 08:56:14 Method "start" exited with status 0 ]
[ Dec 19 08:57:41 Enabled. ]
[ Dec 19 08:57:48 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 19 08:57:48 Method "start" exited with status 0 ]
[ Feb 1 10:39:48 Enabled. ]
[ Feb 1 10:39:55 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Feb 1 10:39:56 Method "start" exited with status 0 ]
[ Feb 8 11:12:50 Enabled. ]
[ Feb 8 11:12:57 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Feb 8 11:12:57 Method "start" exited with status 0 ]
[ Jun 6 10:08:34 Enabled. ]
[ Jun 6 10:08:44 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jun 6 10:08:46 Method "start" exited with status 0 ]
[ Aug 8 09:45:48 Enabled. ]
[ Aug 8 09:46:35 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 8 09:46:36 Method "start" exited with status 0 ]
[ Aug 14 17:53:59 Enabled. ]
[ Aug 14 17:54:06 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 14 17:54:06 Method "start" exited with status 0 ]
[ Aug 14 17:55:20 Enabled. ]
[ Aug 14 17:55:27 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 14 17:55:27 Method "start" exited with status 0 ]
[ Aug 18 15:19:17 Enabled. ]
[ Aug 18 15:19:24 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 18 15:19:24 Method "start" exited with status 0 ]
[ Aug 29 12:56:48 Enabled. ]
[ Aug 29 12:56:55 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 29 12:56:55 Method "start" exited with status 0 ]
[ Oct 13 11:59:43 Enabled. ]
[ Oct 13 11:59:50 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Oct 13 11:59:51 Method "start" exited with status 0 ]
[ Feb 26 16:47:00 Enabled. ]
[ Feb 26 16:47:07 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Feb 26 16:47:07 Method "start" exited with status 0 ]
[ Apr 14 15:54:17 Enabled. ]
[ Apr 14 15:54:24 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Apr 14 15:54:25 Method "start" exited with status 0 ]
[ Aug 28 08:49:58 Stopping because service disabled. ]
[ Aug 28 08:49:58 Executing stop method (null) ]
[ Aug 28 08:52:54 Enabled. ]
[ Aug 28 08:53:01 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 28 08:53:01 Method "start" exited with status 0 ]
[ Aug 28 09:08:20 Stopping because service disabled. ]
[ Aug 28 09:08:20 Executing stop method (null) ]
[ Sep 1 16:05:36 Enabled. ]
[ Sep 1 16:06:05 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 1 16:06:05 Method "start" exited with status 0 ]
[ Sep 1 19:29:19 Enabled. ]
[ Sep 1 19:29:27 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 1 19:29:27 Method "start" exited with status 0 ]
[ Sep 1 23:04:00 Enabled. ]
[ Sep 1 23:04:08 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 1 23:04:08 Method "start" exited with status 0 ]
[ Sep 2 00:23:41 Stopping because service disabled. ]
[ Sep 2 00:23:42 Executing stop method (null) ]
[ Sep 2 00:46:46 Enabled. ]
[ Sep 2 00:46:53 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 2 00:46:54 Method "start" exited with status 0 ]
[ Sep 26 12:04:34 Enabled. ]
[ Sep 26 12:04:41 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 26 12:04:42 Method "start" exited with status 0 ]
[ Oct 20 13:05:09 Stopping because service disabled. ]
[ Oct 20 13:05:10 Executing stop method (null) ]
[ Oct 20 13:24:01 Enabled. ]
[ Oct 20 13:24:08 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 20 13:24:09 Method "start" exited with status 0 ]
[ Oct 21 16:30:59 Enabled. ]
[ Oct 21 16:31:09 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 21 16:31:09 Method "start" exited with status 0 ]
[ Oct 21 16:32:42 Stopping because service disabled. ]
[ Oct 21 16:32:42 Executing stop method (null) ]
[ Oct 21 16:42:05 Enabled. ]
[ Oct 21 16:42:15 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 21 16:42:15 Method "start" exited with status 0 ]
[ Oct 21 17:27:37 Enabled. ]
[ Oct 21 17:27:47 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 21 17:27:47 Method "start" exited with status 0 ]
[ Oct 22 11:08:34 Enabled. ]
[ Oct 22 11:08:43 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 22 11:08:43 Method "start" exited with status 0 ]
[ Dec 9 09:17:33 Stopping because service disabled. ]
[ Dec 9 09:17:33 Executing stop method (null) ]
[ Dec 10 11:47:14 Enabled. ]
[ Dec 10 11:47:24 Executing start method ("/lib/svc/method/fs-local") ]
[ Dec 10 11:47:25 Method "start" exited with status 0 ]
[ Dec 15 10:52:25 Stopping because service disabled. ]
[ Dec 15 10:52:25 Executing stop method (null) ]
[ Dec 15 12:42:16 Enabled. ]
[ Dec 15 12:42:26 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 12:42:28 Method "start" exited with status 95 ]
[ Dec 15 13:13:19 Enabled. ]
[ Dec 15 13:13:28 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 13:13:30 Method "start" exited with status 95 ]
[ Dec 15 13:58:51 Enabled. ]
[ Dec 15 13:59:00 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 13:59:03 Method "start" exited with status 95 ]
[ Dec 15 15:34:41 Leaving maintenance because clear requested. ]
[ Dec 15 15:34:41 Enabled. ]
[ Dec 15 15:34:41 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 15:34:43 Method "start" exited with status 95 ]
bash-3.00# /usr/sbin/zfs mount -a
internal error: Unknown error
Abort (core dumped)
Before that I've installed the patch cluster with halted solaris zones which produced following output:
Application of patches finished : 2010.12.15 12:08:43
Following patches were applied :
119254-77 119812-10 125719-31 140159-03 142911-01
141588-04 119900-11 125731-05 142292-01 142933-02
142251-02 119906-16 126206-05 141444-09 142909-17
118666-28 120460-17 126363-08 141500-07 143140-04
118667-28 121012-03 126365-16 141502-02 143502-01
118777-16 121308-20 126868-04 141506-09 143506-01
140860-02 122212-40 127724-02 141514-02 143615-02
119059-56 122261-03 136998-09 141518-12 143731-01
119213-23 122675-05 137000-07 141552-03 143733-01
124628-10 123003-04 137080-05 141558-01 143977-01
119252-29 123590-12 137147-06 141586-01 144053-04
119280-23 123893-22 138195-04 141590-02 144106-01
124188-03 124393-11 138822-07 141874-09 144254-01
120199-15 124457-02 138826-07 141876-07 144488-04
119534-19 124630-42 138880-02 142084-04 144492-01
120272-28 125215-03 139099-04 142397-01 145124-01
119757-18 125388-03 139620-01 142529-01 145796-01
119783-15 125555-07
Following patches were skipped :
Patches already applied
120900-04 119063-01 119810-05 123005-07 137093-01
121133-02 119081-25 119986-03 124444-01 138866-03
119317-01 119130-33 120061-02 124939-03 137137-09
121296-01 123611-04 120201-05 124943-01 137871-02
138215-01 140899-01 120292-02 124997-01 138181-01
127884-01 122640-05 120329-02 125279-05 138361-01
118712-23 126897-02 121975-01 125539-06 138373-02
118918-24 127755-01 120719-02 125891-01 138647-01
138217-01 125503-02 120830-06 126440-01 141016-01
119578-30 125547-02 121095-02 126540-02 139555-08
121453-02 140796-01 121606-04 127127-11 139967-01
121453-02 120011-14 124171-07 136882-02 140455-01
121118-16 139520-02 123630-03 137032-01 140563-01
118833-36 119764-06
Patches obsoleted by one or more patches already applied
118731-01 124204-04 122660-10
Patches not applicable to packages on the system
121181-03 120410-33 121211-02 125533-15 143317-03
119115-35 120412-11 122259-03 125541-06 143510-01
119117-52 120414-27 122470-03 125952-20 143725-01
119315-19 120543-21 122911-24 137004-08 143727-01
119548-14 120739-06 122958-06 138387-01 143739-01
119903-02 120811-09 123938-02 138824-07 144325-01
120094-30 120849-04 125136-24 138876-01 145006-02
120185-21 121104-11 125137-24 139986-01 145080-01
119368-04 121136-02 125332-14 142244-02 145200-01
120286-03
Installation of patch set complete. PLEASE REBOOT THE SYSTEM.
when i tried to reboot the system by init 6 the service iscsi hanged and produced syslog errors about a unkown iocall -> killed the process. System rebooted w/o errors.
Does anyone have got an idea how to find out which patch or whatever do produce these errors?

Hi,
I'm having the same issue of diskmon core dumps after upgrading grid and database from 11.2.0.1 to 11.2.0.2 on Solaris 10 x86-64. Following this thread, I'm trying to deinstall the Oracle 11.2.0.1 grid home.
I answered the following questions asked by the grid deinstall tool:
1. ASM configuration was not detected in this Oracle home. Was ASM configured in this Oracle home (y|n): y
2. Specify the ASM Diagnostic Destination: /db01/app/oracle/diag/asm/+ASM
3. Specify the diskgroups that are managed by this ASM instance: DATA FRA
4. De-configuring ASM will drop all the diskgroups at cleanup time. Do you want deconfig tool to drop the diskgroups:
If I answer no to question 1, the tool exits with error.
How do I answer question #4? (confused about this question of dropping diskgroups, it's already been upgraded)
Deinstall of Oracle db Home 11.2.0.1 was successful.
The +ASM instance has been upgraded and is running fine under 11.2.0.2 except for the excessive diskmon core dumps.
Thanks,
Lisa
Edited by: user12018917 on Apr 19, 2011 10:21 AM

1) How to Boot from SAN for T4-1 Server with Solaris 11.1 OS on the disk? 2) How to SMI Label/Format a disk while OS Installation in Solaris 11.1?

FYI....boot from SAN is required for physical server (T4-1) (not OVM).
1) How to Boot from SAN for T4-1 Server with Solaris 11.1 OS on the disk?
The SAN disks allocated are visible in ok prompt. below is the output.
(0) ok show—disks
a) /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0, 2/hub@2/hub@3/storage@2/disk
b) /pci@400/pci@2/pci@0/pci€a/SUNW, ezalxs@0, l/fp@0, 0/disk
e) /pci@400/pci@2/pci@0/pci@a/SUNW, ealxs@0/fp@0, 0/disk
d) /pci@400/pci@2/pci@0/pci@8/SUNW, emlxs@0, l/fp@0, 0/disk
e) /pci@400/pci@2/pci@0/pci@8/SUNW,enlxs@0/fp@0,0/disk
f) /pci@400/pci@2/pci@0/pci@4/scsi@0/disk
g) /pci@400/pci@1/pci@0/pci@4/scsi@0/disk
h) /iscsi—hba/disk
q) NO SELECTION
valid choice: a. . .h, q to quit c
/pci@400/pci@2/pci@0/pci@a/SUNW, ealxs@0/fp@0, 0/disk has been selected.
Type “Y ( Control—Y ) to insert it in the command line.
e.g. ok nvalias mydev “Y
for creating devalias mydev for /pci@400/pci@2/pci@0/pci@a/SUNW,emlxs@0/fp@0,0/disk
(0) ok set—sfs—boot
set—sfs—boot ?
We tried selecting a disk and applying sfs-boot at ok prompt.
Can you please help me providing detailed pre-requesites/steps/procedure to implement this and to start boot from SAN.
2) How to SMI Label/Format a disk while OS Installation in Solaris 11.1?
As we know that ZFS is the default filesystem in Solaris 11.
We have seen in the Oracle documentation that for rpool below are recommended:
- A disk that is intended for a ZFS root pool must be created with an SMI label, not an EFI label.
- Create root pools with slices by using the s* identifier.
- ZFS applies an EFI label when you create a storage pool with whole disks.
- In general, you should create a disk slice with the bulk of disk space in slice 0.
I have seen the solution that using format -e, we change the labelling but all the data will be lost, whats the way to apply a SMI Label/Format on a rpool disks while OS Installation itself.
Please provide me the steps to SMI Label a disk while installaing Solaris 11.1 OS.

Oracle recommends below things on rpool: (thats reason wanted to apply SMI Label)
I have seen in the Oracle documentation that for rpool below are recommended:
- A disk that is intended for a ZFS root pool must be created with an SMI label, not an EFI label.
- Create root pools with slices by using the s* identifier.
- ZFS applies an EFI label when you create a storage pool with whole disks.
- In general, you should create a disk slice with the bulk of disk space in slice 0.

How do can I use Jumpstart to boot Solaris from Slave Drive

Hi all,
I have XP on Master Drive and I used Jumpstart to install Solaris on Slave Drive.
This is the profile:
install_type     initial_install
system_type     standalone
usedisk          c0d1
boot_device      c0d1 update
root_device     c0d1s0
fdisk           c0d1 solaris all
partitioning     explicit
filesys          c0d1s0 10000 /
filesys          c0d1s1 1111 swap
filesys          c0d1s7 free /export/home
cluster          SUNWCreq
Now, I specified that the boot_device is c0d1 but after the installation the boot device is c0d0 which is my Master Drive...
...when I use Windows Boot Manager to boot Solaris... it cannot find the boot files on the master drive so it runs the DCA...
... so under the DCA I have to tell Solaris that the boot files are in my Slave Drive then I save it.
...I don't want to make this change everytime
any ideas that would make this install hands free?

...don't know the answer to that but here is an alternative:
... use this as your finish script
... it changes the bootpath in bootenv.rc to point to the slave drive
#!/usr/bin/perl
open(INFILE,"/a/boot/solaris/bootenv.rc");
open(OUTFILE,">/a/boot/solaris/bootenv.rc_out");
while(<INFILE>) {
chomp;
#--cmdk@0,0 is the master drive
#--cmdk@1,0 is the slave drive
s/cmdk\@0\,0/cmdk\@1\,0/g;
print OUTFILE "$_\n";
#...replace bootenv.rc_out with bootenv.rc
...happy programming

Solaris 8 - Installation from network

Hi,
Can I to install Solaris 8 from network, booting installation from diskette?
I have the packages downloaded from www.sunfreeware.com in my disk, but no encountred how install this SO.
Thank you.

I'm not quite sure what you are asking. Solaris 8 is not available from sunfreeware, only additional freeware packages to be loaded after Solaris is installed. Solaris 8 can be downloaded and "burned" to CD from : http://wwws.sun.com/software/solaris/binaries/get.html

How do I get from Branded Zones to "real" Solaris 10 Zones?

My head is beginning to spin! I am beginning to think I have been led down a blind alley.
We have vast numbers of old Solaris 8 systems that we want to consolidate on new hardware in Solaris 10 Zones. We have been bombarded with advice that the way to go is to move it first to Branded Zones, as a stepping stone, and then migrate/upgrade it from there to Solaris 10. So we have started on our journey.
We now have our first bunch of Solaris 8 containers happily installed and running. And yes, it was relatively easy and painless, and the tool support was good. But now what? What are the steps and tools that will make the second step, from Solaris 8 to Solaris 10?
Everything out there hints that it is supposed to be easy. But every time I try and spec out the steps for our teams to follow I come unstuck. Does Live Upgrade feature in this anywhere? (And if so, at what point does my zone lose its Brand identity?) Is there some way to use archives? (And if so, how do I only include the bits I need to move?) Is there something magic under the covers of the Zone administration commands? (And if so, what pulls in my Solaris 8 stuff?) Is there at least some tool somewhere that will capture the configuration I need and build me a new one?
If the answer is that I just define the new Zone by hand and re-install all my applications from scratch, then can somebody explain just what I have achieved so far, and in what way it can be construed as a "stepping stone"?

Correct. But we have now invested in the time taken to learn about Branded Zones, do the migrations, teach the support teams how to manage them... Plus we are paying the subscription for the Branded Zone software. And we still have pure Solaris 8 applications staring end-of-support in the face. We could have made the same investment to re-install the applications in a real Solaris 10 Zone and make them work "properly". All the publicity tells me I've made my migration to Solaris 10 much easier, but I still can't see how I'm any nearer my end point.Here's where your losing it. There is no real distinction between what you call a normal Solaris 10 zone and a Solaris Branded 8 zone. They could have called it something else and you would still insist that somehow one is normal and one is not. There are a variety of Branded Zones. There's a Solaris 8, Solaris 9, and Linux Branded Zones. They differ from what you call "normal" zones in that you basically are adding an OS to the Base OS and are not just copying files from the Base OS. That's the only difference. In all other respects they are the same. The only differentiators is for a Branded Zone you are adding the files from some other OS, even if it's just an earlier version of Solaris.
How do you migrate from a Solaris 8 zone to a Solaris 10 zone. The same way that you moved from the Solaris 8 physical box to the Solaris 8 branded zone. The steps should be the same. Implicite_Order pretty much said the same thing.
You seem to have a hang up on the words "normal zone." Yea I know, you've spent time and money and educated everyone and now your looking for the payoff. As I already stated and has been echoed by I_O, contact the vendor to see if they have Solaris 10 support, if they do, create a zone on a dev box, do some testing, and then create the zone on the real box, do the install, migrate the data. Just as you already did from the Solaris 8 box. If they don't have a Solaris 10 specific version you can still setup a test box, create a "normal" zone, install the app and some test data, make sure it works, and then create the "normal" zone, install the app, migrate the data, and relax.
alan

Solaris 10 U6 jumpstart installation always goes into interactive mode desp

While doing the Solaris 10 U6 jumpstart installation, it is going into interactive mode for netmask.
This is the sysidcfg file configuration being used :
bash-3.00# cat /export/home/iserver/jumpstart/donau1/sysidcfg
system_locale=en_US
name_service=none
network_interface=ce2
{hostname=donau1 netmask=255.255.252.0 ip_address=10.50.57.24 protocol_ipv6=no default_route=10.50.56.1}
security_policy=none
terminal=vt100
timezone="MET"
timeserver=10.50.57.214
nfs4_domain=dynamic
root_password=5YcgZqC0krYjo
bash-3.00#
Here the network interface specified is "ce2" and the netmask is as shown above. Still, we observe the problem all the times.
and I have seen the following messages on the screen
Attempting to configure interface ce3...
Skipped interface ce3
Attempting to configure interface ce2...
Configured interface ce2
ip_arp_done: init failed
ifconfig: setifflags: SIOCSLIFFLAGS: ce2: Cannot assign requested address
Attempting to configure interface ce1...
Skipped interface ce1
Attempting to configure interface ce0...
Skipped interface ce0
Reading ZFS config: done.
Setting up Java. Please wait...
Serial console, reverting to text install
Beginning system identification...
Searching for configuration file(s)...
Using sysid configuration file 10.50.57.214:/export/home/iserver/jumpstart/donau1/sysidcfg
Search complete.
Discovering additional network configuration...
Completing system identification...
after this it is going into interactive mode and prompting for netmask . After providing the netmask, installation goes through successfully.
so please suggest me some solution to avoid it going into interactive mode.

I have seen this too over the years and it ultimately comes down to something innate:
Here are a few suggestions:
1. Try and use interface ce0.
2. Check default route on both jumpstart server and client.
3. The arp cache may need to be flushed on the Jumpstart server.
4. Use snoop and see what happens during the actual RARPing phase between the server and host.
5. Switch the order in the sysid config file as indicated below:
system_locale=en_US
name_service=none
network_interface=ce2
{hostname=donau1 ip_address=10.50.57.24 netmask=255.255.252.0 protocol_ipv6=no default_route=10.50.56.1}
security_policy=none
terminal=vt100
timezone="MET"
timeserver=10.50.57.214
nfs4_domain=dynamic
root_password=*****************
Please note I blanked your root password. Let me know if this helps.

Solaris installation from CD

Hi all,
I am stack with a Collaboration Suite installation in Solaris. I have install well Application Server but the Information Storage part doesn´t takes the second CD.
I have copy the files on a temp folder with the same names they have on CDs but it didn´t work.
Any idea?? Thankfully,
M.A. Ugalde

Unpacking all files to the same directory does not work, because the Instaløler expect to find a catalog named "Disk2" to continue installation. Create a directory for each CD named "Disk1", "Disk2" and so on, and copy the content of each cd to their respective directory.
Lars

Installation of Solaris 9 Intel Version in Windows XP PC

I am very much interested in installation of Solaris 9 intel version in my PC which is windows XP version.
My PC Processor : AMD Athlon
I am not able to install solaris 9 in my PC.
Sun boot version is Sun OS secondary boot version 3.0.
During installation,i am going untill selection of type of installation. After selecting the Interactive type,the system is rebooting again without installing.
Select the type of installation you want to perform
(1) Solaris Interactive
(2) Custom Jumpstart
After selecting from above,the system is rebooting again without installing.
Please help me with the installation.

Try on HCL BigAdmins website to know if your hardware is supported

Installation of Solaris 9 intel version in windows XP

I am very much interested in installation of Solaris 9 intel version in my PC which is windows XP version.
My PC Processor : AMD Athlon
I am not able to install solaris 9 in my PC.
Sun boot version is Sun OS secondary boot version 3.0.
During installation,i am going untill selection of type of installation. After selecting the Interactive type,the system is rebooting again without installing.
Select the type of installation you want to perform
(1) Solaris Interactive
(2) Custom Jumpstart
After selecting from above,the system is rebooting again without installing.
Please help me with the installation.

Are you trying to install Solaris 9 onto a server that is already running Windows XP and to keep Windows XP too?
You'll need to create a partition on which to install Solaris, - search for Solaris Windows Dual Boot on docs.sun.com for more information.

Upgrade from Solaris 11 Express to Solaris 11 Release (11/11); Guide MIA?

Would there be an easy way to upgrade from Solaris 11 Express to Solaris 11 Release (11/11)? The FAQ for Solaris 11 Release has the following hopeful text:
Can I upgrade to Oracle Solaris 11 from Oracle Solaris 11 Express or Oracle Solaris 11 Early Adopter?
Yes. Customers can upgrade to Oracle Solaris 11 by using the package management tools. Refer to the Oracle Solaris 11
Transition Guide (http://www.oracle.com/pls/topic/lookup?ctx=E23824&id=MF JAI) for more information
But that link comes up with an error page 404, "topic not found".
The one transition guide I can find is:
http://download.oracle.com/docs/cd/E23824_01/html/E21799/index.html
But that covers Solaris 10 jumpstart, not Solaris 11 Express or Early Adopter.
The Solaris 11 documentation at:
http://www.oracle.com/technetwork/server-storage/solaris11/documentation/index.html
Also seems to mention only Solaris 10, not 11 Express or Early Adopter.
I have already downloaded the full repo for Solaris 11 Release, and the live installer, but I'm hoping it's something as simple as pointing the ips manager to a new repository, or just loading the full repo I already have as a local source. I would also like to keep the dtrace and sun studio set up I have now in the Express version, without reinstalling them on a new release version on bare metal.
If it keeps the features of the express version while ironing out a few kinks (gdm authentication bug, etc.), that would rock.
Many Thanks,
Gordon

Alan, Thank You, that worked with no problem at all. 11 Express was already using the correct repository, and only required a pkg command update, then other updates.
So here's what I'm guessing:
1. The Oracle Solaris maintained repository for Express and Early Adopter are now the same as Release, but they do require an updated pkg executable and pkg update command.
2. The second form of the command mentioned in the update guide:
# pkg set-publisher -g http://pkg.oracle.com/solaris/release
-G http://internal.co.com/solaris solaris
is for using a local copy of the repository within our lan or vpn wan.
3. Updates should be fairly regular now that Solaris 11 is in release version.
I think the new hash (SHA 256) fried some of our old gdm settings for our users, so we're creating new user accounts, and migrating the older accounts. We don't have too many, so it's not a problem for us. But that brings up another point:
4. The graphical user manager in Express is now gone, and user and group management are now done with command line interface.
That's fine with me as well. I always use ssh to connect to the machine and then run the screen command for administration. The graphical user manager was always kludgy in Express, and I couldn't get it to work correctly anyway.
This is great stuff so far. Well done.
Gordon

Jumpstart installation from Solaris 10 zone

Similar Messages

Maybe you are looking for