Mistake installing solaris 10 in server Sun Sparc Entreprise 220r

Hello I am installing solaris 10 in a server Sun Sparc Enterprise220r, it starts with CD1 and the following mistake appears:
THE FILE JUST LOADED DOES NOT APPEAR TO BE EXECITABLE

Perhaps instead of opening a new post, you might have just continued your original thread from a few days ago. It seems to be the same issue - bad burn of the optical media.
http://forum.java.sun.com/thread.jspa?threadID=5229606
Generic instructions for downloading and creating your installation media is here:
http://www.sun.com/software/solaris/download_instruction.xml

Similar Messages

Installation of Solaris 10 on SUN Sparc M4000

Hi
I am trying to install Solaris 10 on SUN SPARC M4000.
Here is the error I have:
+Enter filename [kernel/sparcv9/unix]: /platform/sun4v/kernel/sparcv9/unix+
+Enter default directory for modules [platform/sun4v/kernel /kernel /usr/kernel]:+
krtld: load_exec: fail to expand cpu/$CPU
krtld: error during initial load/link phase
panic - boot: exitto64 returned from client program
Program terminated
It seems that version of Solaris I trying to install is not support by the Hardware, when I use another Solaris 10 DVD, it works...
But the problem is that I need to install this Solaris version because others softwares are depending on that.
If someone knows how to make this installation possible, it will be very helpfull.
Thanks in advance.
BR
Racine

Minimum Supported
Solaris[tm] Operating Environment Versions for the M4000 are as follows
OpenSolaris 2009.06
SPARC64 VI:
10 - 11/06 (U3) plus required patches (minimum)
10 - 08/07 (U4) (recommended)
SPARC64 VII:
10 - 08/07 (U4) plus required patches (minimum)
10 - 5/08 (U5) (recommended)
A full matrix for the M4000 which details the minimum patch requirements to support the h/w is available from https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1145383.1

How to Install Solaris 10 on Sun Server

Dear All,
Can any one help me to Install Solaris 10 on Sun Server.
Or if you guys can suggest me which document i can refer for Solaris 10 installation.
Thnaks in advance to all.
Rgds,
Shrinet

You can go to doc.sun.com for all Solaris documentation. This should be the link you need, which is for the latest version of Solaris 10 (10/09).
http://docs.sun.com/app/docs/coll/1236.11?l=en
If you need an older version, you can find them all here:
http://docs.sun.com/app/docs/prod/solaris.10?l=en&a=view
-- Alan

Problem in installing solaris 10 in sun blade 1000

Dear all,
I am trying to install solaris 10 in sun blade 1000 and getting a problem that disk doesn't exist ......... After several tentatives, I understood that I need to format a harddrive as it is new. I formeted it with boot cdrom -s and the problem still persists.
I bought a 73g HDD and the machine recognize it as 68,38g .. is there any upgrade I need to perform for it
Could someone please help me to solve this problem
Thanks a lot for your help and reply ...

I have the same problem ..ubuntu installs fine
TIA
Dale

How to install Solaris 10 on sun ultra enterprise 450

I just got a used sun ultra enterprise 450 and need to get a username and password. If I cannot get easily how do I reinstall the OS. What OS can I put on its? I am new to some equipment. It also came with a a storage unit for extra hard drives and how would I use it and set it up also?
It now says type ctrl-d. What do I do?
http://www.unix.com/sun-solaris/114206-how-get-root-password-how-install-sun-os.html
http://www.linuxquestions.org/questions/solaris-opensolaris-20/how-to-install-solaris-10-on-sun-ultra-enterprise-450-739614/

This same question was cross-posted to another forum site
[http://www.linuxquestions.org/questions/solaris-opensolaris-20/how-to-install-solaris-10-on-sun-ultra-enterprise-450-739614/|http://www.linuxquestions.org/questions/solaris-opensolaris-20/how-to-install-solaris-10-on-sun-ultra-enterprise-450-739614/]
with the same unintelligible drivel.
O.P.
Go to Docs.Sun.Com and get the system's documentation. Also go get the OBP 3.x Command Reference manual while you are there. All you questions are answered in that documentation, except for those that are easily found with Google.
[Example of a Google search for your question.|http://www.google.com/#hl=en&q=solaris+root+password&aq=f&oq=&aqi=g9&fp=KxYPMM6r3XA]

Trying to install solaris 10 on sun file v210

Rebooting with command: boot net - install nowin
Boot device: /pci@1f,700000/network@2 File and args: - install nowin
1000 Mbps FDX Link up
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
4000 1000 Mbps FDX Link up
Requesting Internet address for 0:3:ba:60:36:d
I am trying to install solaris 10 (sparc) on a sun fire v210 and I get kernel dump and
the following crash messages:
Any suggestion would be very welcome indeed as this the first of 250 systems...
Lydia
SunOS Release 5.10 Version Generic_118833-33 64-bit
Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Cannot find /system/contract
/kernel/fs/sparcv9/procfs: undefined symbol 'default_copyops'
/kernel/fs/sparcv9/procfs: undefined symbol 'cpu_decay'
WARNING: mod_load: cannot load module 'procfs'
WARNING: Cannot mount /proc
WARNING: file system 'mntfs' version mismatch
WARNING: Cannot mount /etc/mnttab
WARNING: Cannot find /etc/svc/volatile
WARNING: Cannot find /system/object
/kernel/fs/sparcv9/procfs: undefined symbol 'default_copyops'
/kernel/fs/sparcv9/procfs: undefined symbol 'cpu_decay'
WARNING: mod_load: cannot load module 'procfs'
WARNING: Failed to process interrupt for ali1535d+-power0 due to down-rev nexus driver isa0
WARNING: power_attach: failed to add high-level interrupt handler.
WARNING: power button driver failed to install
WARNING: Failed to process interrupt for rmc_comm0 due to down-rev nexus driver isa0
WARNING: rmc_comm failed to install
WARNING: Could not install rmclomv driver
WARNING: Failed to process interrupt for pcf85840 due to down-rev nexus driver isa0
WARNING: i2c_0 failed to retrieve iblock cookie. Operating in POLL MODE only
fs/sockfs:sock_getfasync() not defined properly
/kernel/sys/sparcv9/c2audit: undefined symbol 'sogetpeername'
/kernel/sys/sparcv9/c2audit: undefined symbol 'sogetsockname'
WARNING: mod_load: cannot load module 'c2audit'
WARNING: c2audit: unable to resolve dependency, module 'fs/sockfs' not found
misc/consconfig:consconfig_get_usb_kb_path() not defined properly
panic[cpu1]/thread=180e000: mod_hold_stub: Couldn't load stub module misc/consconfig
000000000180b890 genunix:mod_hold_stub+1f0 (0, 185f800, 18ac878, 60000c44fb0, 1817328, 0)
%l0-3: 0000000001843ac8 000006000136e000 0000000001811cf8 0000000000000000
%l4-7: 0000000000000000 0000000000000064 0000000000000064 0000000000000001
000000000180b940 unix:stubs_common_code+30 (21dead78c0, 960010, 53555554, 0, 31f400, 0)
%l0-3: 000000000180b209 000000000180b2e1 000000123e000000 0000000000000001
%l4-7: 0000000000000000 0000000001817338 0000000000000000 0000060000c1abc0
000000000180ba10 genunix:main+134 (18accd0, 18a8800, 18364c0, 1861400, 183b400, 1814000)
%l0-3: 0000000070002000 0000000000000001 0000000000000000 0000000000000002
%l4-7: 00000000018afef8 00000000018afc00 00000000018acce0 00000000018acc00

I am using jet to do the jumpstart and the config file for jet is list below.
The install server is solaris 10 sparc
SunOS nereid 5.10 Generic_125100-10 sun4u sparc SUNW,Sun-Blade-1500
The version I am trying to install is 118855-33 (sol10-u3 - i believe). I have downloaded
the latest recommended patchset which should bring me to 118855-36 plus the latest
minor kernel patches.
nereid-root (482)>cat m1001
# Client template file
# Client: m1001 (derived from quintor.js)
# Created: Wed Mar 8 14:38:51 GMT 2006
# This file was automatically generated using 'make_template'
# Product: base_config
# Synopsys: Basic host information
# Architecture type:
# sun4c : e.g. SS1, SS2, SS IPX
# sun4d : e.g. SS1000, SS2000
# sun4e : ?
# sun4m : e.g. SS LX, SS4, SS5, SS10, SS20
# sun4u : UltraSparc - U1, U2, E3x00, E4x00 etc
# sun4u1 : E10K
# i86pc : Intel X86
# Ethernet can be obtained from the 'banner' command at OBP
# OS is one of the values you used to register the solaris media using
# the add_solaris_location command
base_config_ClientArch="sun4u"
base_config_ClientEther=00:03:ba:60:36:0d
base_config_ClientOS="sol10_u3"
# Client allocation
# The mechanism used to build this client; by default, the options listed
# in /opt/jet/etc/jumpstart.conf will be tried; you should only set this
# if this particular client needs to do something different.
base_config_client_allocation="newboot"
# products is the set of products to install after base_config; this
# should be updated automatically by make_template, so you
# will only need to change it, if you wish to omit certain
# modules when testing/debugging.
base_config_products=" custom"
# JumpStart sysidcfg information
# The sysidcfg file provides information at initial boot time so that the
# system can properly identify itself. The interface and ip address defined
# here MUST be on the same subnet as the JumpStart server. The root password
# is set here also and must be written in encrypted format. The default value
# shown here is "newroot". The timeserver is normally the IP address of the
# JumpStart server.
# nameservice examples:
# NONE
# NIS { domain_name=uk.sun.com name_server=nis.uk.sun.com(129.159.91.1) }
# or for DNS
# DNS { domain_name=uk.sun.com name_server=192.168.1.1 search=uk.sun.com }
# network_interface:
# le0, hme0
# or PRIMARY (the default interface - net in OBP)
# N.B. PRIMARY is only valid from Solaris 7 upwards
# locale:
# en_UK for Solaris 2.6
# en_GB for Solaris 7 and above
# timeserver: Where the client gets the current time from.
# Leave blank to default the the JumpStart server
# Alternatively, set to 'localhost' to trust the current
# hardware clock on the client
# terminal: terminal type (vt100/vt220/sun etc)
# security_policy: Kerberos policy (Solaris 8 +)
# protocol_ipv6: Use ipv6 or not (Solaris 8 +)
# default_route: Solaris 9 allows a default route to be set
# (ignored on all other versions of Solaris, less than 9)
base_config_sysidcfg_nameservice=NONE
base_config_sysidcfg_network_interface=PRIMARY
base_config_sysidcfg_ip_address=172.17.3.1
base_config_sysidcfg_netmask=255.255.0.0
base_config_sysidcfg_root_password="xxxxxxxxxxxx"
base_config_sysidcfg_system_locale="en_GB.ISO8859-15"
base_config_sysidcfg_timeserver=
base_config_sysidcfg_timezone="GB"
base_config_sysidcfg_terminal=vt100
base_config_sysidcfg_security_policy=NONE
base_config_sysidcfg_protocol_ipv6=no
base_config_sysidcfg_default_route=
# X86, X64 specific settings. If this is an x86 client, then you may need
# to configure these settings. They are ignored for SPARC builds.
# base_config_x86_nowin:
# This stops Solaris from trying to run windows during the install.
# the default value is yes.
# base_config_x86_console:
# Set the console to the correct tty port. This is used for doing installs
# via the serial port or the SP. b1600,v20z and v40z use ttya. lx50, v60x,
# and v65x use ttyb. NOTE: you only need to set this if you are NOT going
# to connect a keyboard and monitor to the client.
# base_config_disable_acpi:
# Disable ACPI - sometimes disabling ACPI makes the install go
# better due to how the interrupts are handled. Non-Null disables ACPI.
# base_config_x86_safetoreboot:
# The Solaris installer can't control the BIOS, therefore does not
# know if its safe to reboot the client as it may simply jumpstart
# again. If your PXE boot is a one time option, and the next reboot
# will attempt to boot from disk, then you probably want to set this
# option to "yes". Otherwise, leave it as it is so that it won't reboot
# and therefore allow you to manually change your BIOS to boot from disk.
base_config_x86_nowin=""
base_config_x86_console=""
base_config_x86_disable_acpi=""
base_config_x86_safetoreboot=""
# Want to create your own custom profile ? if so, use this variable to
# reference a file relative to the Clients/<clientname> directory, otherwise
# fill in the other details below to get toolkit to create one for you.
base_config_profile=""
# JumpStart profile information
# A limited profile can be automatically generated here. If further
# customisation is required, then you can manually create a profile in the
# client directory and reference it in the base_config_profile variable.
# Cluster:
# SUNWCrnet : Minimal. Solaris 10 only
# SUNWCreq : Required - really basic, good for testing
# SUNWCuser : User collection
# SUNWCprog : User + Developers collection
# SUNWCall : All packages
# SUNWCXall : All + OEM packages (mandatory for E10K)
# usedisk: defines the disk that the OS will be loaded on to - bootdisk
# (if this is set to rootdisk. , then the current boot disk will
# be used)
# dontuse: defines disks that should not be used..
# ** N.B. This will only be used if 'usedisk' is NOT set
# Space seperated list of disks of the form c?t?d?
# partition sizes:
# if partitions are not required simply leave blank. In order to maintain
# consistency the partitions will always use the same slice number:
# / s0
# swap s1
# /var s5
# /usr s6
# /opt s7
# at most one partition can have the size 'free' which denotes all the
# unallocated/spare space on a disk.
base_config_profile_cluster=SUNWCall
base_config_profile_usedisk=rootdisk.
base_config_profile_dontuse=""
base_config_profile_root=8192
base_config_profile_swap=4096
# If you are using VxVM and want your boot disk to look like the mirror, then
# leave slices 3 and 4 empty. If you do not care about keeping the two disks
# looking cosmetically the same, please just make sure you have two free slices
# somewhere on the disk for VxVM!
# If you are not using VxVM, then you can use s3 and s4 for whatever you wish!
base_config_profile_s3_mtpt=""
base_config_profile_s3_size=""
base_config_profile_s4_mtpt=""
base_config_profile_s4_size=""
base_config_profile_s5_mtpt=""
base_config_profile_s5_size=""
base_config_profile_s6_mtpt=""
base_config_profile_s6_size=""
# If you are using DiskSuite, the default behaviour is to use slice 7 as a
# location for metastate databases. If you are using DiskSuites default config,
# please avoid using s7 for data!
base_config_profile_s7_mtpt="/export/disk/1"
base_config_profile_s7_size="free"
# You can specify additional disks to use/configure here
# additional_disks is a space separated list of c?t?d? type disk names
# For each disk listed in additional_disks, a pair of variables of the form
# base_config_profile_disk_c?t?d?s?_mtpt="...."
# base_config_profile_disk_c?t?d?s?_size="...."
# should be defined for each slice required on the disk.
# N.B. DO NOT SET THE BOOT DISK UP HERE !
base_config_profile_additional_disks=""
base_config_profile_disk_c0t3d0s0_mtpt=""
base_config_profile_disk_c0t0d0s0_size=
# Additional locales/geos e.g. N_Europe, C_Europe
base_config_profile_add_locales=""
base_config_profile_del_locales=""
base_config_profile_add_geos=""
base_config_profile_del_geos=""
# UFS Logging
# Solaris 7 and above support UFS+, which allows for a logging filesystem
# under UFS. If you want to use this feature on any of the UFS mount points,
# please specify the mount points here, as a space seperated list, or enter
# the keyword "all" to enable logging on all UFS filesystems.
# Solaris 9 09/04 enables logging by default. You can also specify mountpoints
# preceded by a - sign to say that you DON'T want logging enabled on that
# filesystem, or you can use the keyword "none" to say you don't want any
# ufs logging turned on at all.
# N.B. root (/) can be included in the list, and is included by default if
# using either the "all" or "none" keyword.
# Finally, you can't mix keywords and mountpoints. i.e. "all -/" is NOT
# valid.
# e.g. base_config_ufs_logging_filesys="all" : log all filesystems
# base_config_ufs_logging_filesys="none" : log no filesystems
# base_config_ufs_logging_filesys="-/ /var -/usr" : log /var, but not / and /usr.
base_config_ufs_logging_filesys="all"
# Packages to add to/remove from the selected cluster
# Use this to populate the profile with package <pkg> <add|delete> entries
base_config_profile_add_packages=""
base_config_profile_del_packages="SFWrpm SFWexpct SUNWzebrar SUNWa2psr SUNWmysqlr SUNWffiltersr SUNWopensslr SUNWserr SUNWsmbar SUNWa2psu SUNWant SUNWbison SUNWflexlex SUNWfreetype2 SUNWggrp SUNWgimpprint SUNWgm4 SUNWgnome-a11y-gok SUNWgnome-a11y-reader SUNWgnome-camera SUNWgnome-games SUNWgnome-img-editor SUNWgnome-img-viewer SUNWgnome-media-player SUNWgnome-project SUNWgscr SUNWgtar SUNWGtku SUNWhpijs SUNWimagick SUNWmozilla SUNWmoznspr-devel SUNWmysqlt SUNWmysqlu SUNWncft SUNWopenjade SUNWopensp SUNWopenssl-commands SUNWpsutils SUNWPython SUNWsmbac SUNWsmbau SUNWsmcmd SUNWTcl SUNWtexi SUNWTk SUNWwebminu SUNWwgetu SUNWzsh SUNWjavaapps SUNWmozapoc-adapter SUNWmozchat SUNWmozdom-inspector SUNWmozgm SUNWmozilla-devel SUNWmozjs-debugger SUNWmozmail SUNWmoznspr SUNWmoznss SUNWmoznss-devel SUNWmozpsm SUNWmozspell SUNWopenjade-devel SUNWopenjade-root SUNWopenjade-share SUNWopensp-devel SUNWopensp-root SUNWopensp-share SUNWseru SUNWserweb SUNWsfinf SUNWsfman SUNWsmdoc SUNWzebrau SUNWpostgr SUNWpostgr-contrib SUNWpostgr-docs SUNWpostgr-jdbc SUNWpostgr-libs SUNWpostgr-pl SUNWpostgr-server SUNWpostgr-server-data SUNWpostgr-tcl"
# Clusters to add to/remove
# Use this to populate the profile with cluster <cluster> <add|delete> entries
base_config_profile_add_clusters=""
base_config_profile_del_clusters="SUNWCpm SUNWCpmx SUNWCdial SUNWCdialx"
# Remote file systems (NFS)
# Specify these as space seperated list of pairs as follows, using ? as
# the seperator (as : has special meanings with nfs!)
# e.g. to mount 1.1.1.1:/fs on /fs you would create the entry
# base_config_nfs_mounts="fs?1.1.1.1:/fs"
base_config_nfs_mounts=""
# Host information
# This section defines most things network related etc.
# In addtion, if the machine will be JumpStarted as one name/address and
# needs to have a different name/address once installed, this is where you
# can set that information.
# nodename: the value for /etc/nodename if it's not the default
# hostname
# defaultrouter: the value for /etc/defaultrouter.
# notrouter: if this is set, the file /etc/notrouter will be created
# dns_domain: domain entry for /etc/resolv.conf
# dns_nameservers: nameserver entries for /etc/resolv.conf
# (list of ip addresses, space separated)
# dns_searchpath: list of entries to go in the search line
# dns_disableforbuild: If there is no DNS available in the build
# environment, set this to delay the configuration
# of DNS until later on.
base_config_nodename=""
base_config_defaultrouter=""
base_config_notrouter=""
base_config_dns_domain=""
base_config_dns_nameservers=""
base_config_dns_searchpath=""
base_config_dns_disableforbuild="yes"
# NTP configuration
# Specify a list of names or ip addresses for the NTP servers. The first
# one will be given a 'prefer' tag. This section will only place lines
# of the form: server <ipaddress/name> [prefer]
# into the /etc/inet/ntp.conf file. If you require more control of ntp,
# please use the custom module to deploy your own custom ntp.conf file.
# N.B. If you do use names, they must be resolvable in your name service.
base_config_ntp_servers=""
# Network Interface information
# networkifs: a list of interfaces to be defined,
# space seperated "le0 hme0".
# N.B. the sysidcfg interface will already be configured
# Logical interfaces should be defined using _'s rather
# than :'s.
# networkif_<ifname>: the details of the interface <if>
# "netname netmask hostname address"
# netname: arbritrary name for /etc/networks
# netmask: netmask of this if (e.g. 255.255.255.0)
# hostname: unique hostname (N.B. not multihomed)
# address: IP address of this interface
# For example:
# base_config_networkifs="ge0 ge0_1"
# base_config_networkif_ge0="bkp 255.255.255.0 me-bkp 192.168.1.0"
# base_config_networkif_ge0_1="bkp2 255.255.255.0 me-bkp2 192.168.2.0"
base_config_networkifs="beg1"
base_config_networkif_beg1="data 255.255.0.0 d1001 172.18.3.1"
# N.B. Logical interfaces MUST use _ rather than : as illustrated below
base_config_networkif_le0_1=""
# IP Multipathing (Solaris 8+)
# IPMP default mode is automatic failback.
# To change this mode edit /etc/default/mpathd
# ipmp_networkifs: a list of interfaces to be defined under ipmp control
# a space separated list of pairs only
# e.g. "qfe0_qfe4 qfe1_qfe5"
# N.B. If the primary interface is used in an ipmp group, the
# system must be rebooted manually after installation to
# activate ipmp.
# N.B. Can only setup ipmp group with pairs of interfaces in one
# of the following configurations:
# active-standby failover:
# Set ipmp mode = s, and specify one logical
# hostname/ip address pair.
# failover with outbound load spreading:
# Set ipmp mode = l, and specify one logical
# hostname/ip address pair.
# active-active with outbound load spreading:
# Set ipmp mode = l, specify a second logical
# hostname/ip address pair for the second interface.
# ipmp_networkif_<if>_<if>: "netgroup mode test1 test2 mask hostname log-ip hostname2 log-ip2"
# details of the interfaces in the ipmp group
# e.g. networkif_ipmp_qfe0_qfe4
# netgroup: ipmp interface group name
# e.g. database-net
# ipmp mode: s = standby (failover only)
# ** test addresses are allocated last,
# ** first test address will be on the
# ** first virtual interface of the
# ** first physical adapter. Second
# ** test address will be on the second
# ** physical adapter.
# l = load spreading / active-active
# ** test addresses are allocated on
# ** first virtual interfaces on both
# ** the first and second physical
# ** adapters.
# To force the test addresses onto the physical
# adapters, use the suffix 'p' to the above
# modes, i.e. 'sp' or 'lp'. This is not
# recommended and may break certain applications.
# test1: ipmp test address1
# test2: ipmp test address2
# N.B. these addresses must not be used or
# placed in the hosts file
# mask: netmask for ipmp pair
# hostname: unique hostname for logical ip
# log-ip: logical ip address for first i/f of pair
# N.B. The following two parameters are for active-active
# configurations only. Do not specify them for an
# active-standby configuration.
# hostname2: unique hostname for logical ip
# log-ip2: logical ip address for second i/f
# of pair
# Example:
# base_config_ipmp_networkifs="qfe0_qfe1"
# base_config_ipmp_networkif_qfe0_qfe1="database-net l 10.0.0.1 10.0.0.2 24 oracle-db 10.0.0.3 apache 10.0.0.4"
base_config_ipmp_networkifs=""
base_config_ipmp_networkif_qfe0_qfe1=""
# Misc options
# this section is a catchall for other options not included above
# update_terminal: if set, put the sysidcfg terminal type into inittab
# enable_savecore: if set to any value, enable save core (Solaris 2.6 only)
# dumpadm_minfree: set a limit so that crash dumps don't fill up the
# dump filesystem. See dumpadm(1M) -m option for
# possible values.
# noautoshutdown: if set to any value, disable power management
# enable_rootlogin: if set to any value, enable network root login
# from both telnet/rsh and ssh
# enable_rootftp: if set to any value, enable root ftp access
# shutup_sendmail: if set, create an alias hostname. to shut up sendmail
# poweroff_afterbuild: if set, shut the machine down once it has been built
# base_config_dedicated_dump_device:
# if set, dumpadm will configure the partition as a
# Dedicated Dump Device. See dumpadm(1M) for supported
# Operating Environments.
# (Device path e.g. /dev/dsk/c?t?d?s?)
# N.B. This partition is for the SOLE use of the crashdump utility !
# enable_altbreak: if set, enable alternate break sequence
# disable_sysid_probe: if set, skip the sysid stuff on the first reboot; this
# usually just tries to rarp ip addresses for additional
# interfaces and takes ages on machines with lots
# of unused network adapters.
base_config_update_terminal="yes"
base_config_enable_savecore="yes"
base_config_dumpadm_minfree="20000k"
base_config_noautoshutdown="pm_disabled"
base_config_enable_rootlogin="yes"
base_config_enable_rootftp=""
base_config_shutup_sendmail=""
base_config_poweroff_afterbuild=""
base_config_dedicated_dump_device=""
base_config_enable_altbreak=""
base_config_disable_sysid_probe="yes"
# NFSv4
# Set up the NFSv4 domain to prevent being prompted at first reboot.
# If not set, this will default to the entry in base_config_dns_domain,
# and if that is not set, to the value 'domain', which is the default
# in /etc/default/nfs
base_config_nfsv4_domain=""
# N.B. Unless you need to point this client at alternate media for patches
# and packages that is not held on this server, please skip this section!
# productdir is where to find the products. This should be an NFS style
# path, i.e. 192.168.1.1:/export/install but if the server
# is the JumpStart server, then it should just be specified
# as a normal path.
# patchdir is where to find the patches. Same format as productdir.
# Leaving the following blank means they will be populated using jumpstart.conf
# and the JumpStart servers ip address. This is the default behaviour
# and should only be changed if your patch/package repository is not held
# on this server.
base_config_productdir=""
base_config_patchdir=""
# Last one - mainly for developing JumpStart scripts!
# If you set this, the rc3.d/S99jumpstart script will be disabled
# (set to rc3.d/s99jumpstart) every time it is processed - this allows you
# to run it by hand and invoke each reboot step
base_config_debug_jumpstart_postinstall=""
# Product: Custom
# Synopsis: The custom product can install packages and patches that
# would not otherwise be included by the standard
# installation products.
# Which additional packages are to be installed
# (by default, these get added during the main Solaris installation phase)
# O.S. Specific versions:
# as a side effect, if a directory exists under the package dir named
# after the OS, (uname -r), the subdirectory will be used instead of the
# main package directory
# i.e /export/install/pkgs/custom/sparc/5.8 takes preference over
# /export/install/pkgs/custom/sparc for a Solaris 8 box
# Package Response files:
# If a custom package needs a response file, create a directory called
# /opt/jet/Clients/<clientname>/responses
# and put the response file in to it, named the same as the package.
# i.e. for a package called Fred, on client1, use pkgask to create
# pkgask -r /opt/jet/Clients/client1/responses/Fred Fred
# (Space seperated list of packages)
custom_packages=""
# Custom packages at subsequent boots
custom_packages_1=""
custom_packages_n=""
# Which additional patches are to be installed
# (by default, these get added during the main Solaris installation phase)
# (Space seperated list of patches)
custom_patches=""
# Custom patches at subsequent boots
custom_patches_1=""
custom_patches_n=""
# Custom patch sets... create a directory in the patch directory named after
# the set, and put a patch_order file in it, along with the patches...
# (Space seperated list of patch set names)
# N.B. as a side effect, if a directory exists under the patch set dir named
# after the OS, (uname -r), the subdirectory will be used instead of the
# main patchset directory
# i.e /export/install/patches/patchset/5.8 takes preference over
# /export/install/patches/patchset
custom_patchsets=""
# Custom patchsets at subsequent boots
custom_patchsets_1=""
custom_patchsets_n=""
# Search paths
# The files and scripts sections below will look for source files relative
# to the Clients/<clientname> directory. If you wish to look in other places
# for files, please fill out the search path option below. Items in the
# search path are relative to the Clients/<clientname> directory, since the
# client has no knowledge of the filesystem layout of the server
# e.g. for a client 'fred', the default location for all custom files/scripts
# is /opt/jet/Clients/fred
# if the search path was set to "../common" then the installation routines
# would look first in Clients/fred then
# Clients/fred/../common (or Clients/common in this case)
# Search path is a space separated list of places to search
# THE SEARCHPATH IS ONLY VALID FOR files & scripts. NOT PACKAGES/PATCHES!
custom_search_path="../common.files"
# Files to be copied to the client. The filenames must be of the form
# filename1:a:filename2
# Where filename1 is the name of the source file in the
# /opt/jet/Clients/<clientname> directory
# filename2 is the full path of the file on the installed client
# and the middle option is whether to a - append, or o - overwrite the file
# (by default, these get added during the main Solaris installation phase)
# (Space seperated list of tuples)
# N.B. Please see section above regarding where to place the source files
# N.B. (2):
# appending to /etc/hosts is a special case; instead of just appending
# the file, the module will do an 'intelligent merge' of the new hosts
# file with the existing one.
# custom_files="hosts:a:/etc/hosts"
#custom_files="system:a:/etc/system"
custom_files=""
custom_files_1="NISHost:a:/etc/inet/hosts QuintorNFS:a:/etc/vfstab authorized_keys:o:/.ssh/authorized_keys SGEServices:a:/etc/services"
# Custom files at subsequent boots
custom_files_n=""
# Scripts to be run on the client at the end of the build
# The scripts must be placed in the directory
# /opt/jet/Clients/<clientname>
# and will be copied to the client.
# Note: we don't allow you to run custom scripts during the Jumpstart
# phase because its kinda dangerous.
# If you need to do this, the best way is to create
# your own custom module to do this.
# Custom scripts at subsequent boots
custom_scripts_1="DurhamUni_PostInstall.ksh fixup_ssh"
custom_scripts_n=""
# Special JumpStart 'Begin' phase scripts
# If you need to run scripts in the 'begin' phase of the JumpStart, you
# can supply them here. Please note, that in the 'begin' phase, the
# new OS has not been installed and the majority of the OS running will
# be read-only from the JumpStart server.
custom_scripts_b=""
nereid-root (483)>

Failed to install solaris on new "Sun Fire V100"

Hi All,
I'm new to solaris. I have a new server Sun Fire v100. Just after power on the server I got a following message on the console screen
*" No memory Detected! Cannot proceed further !!!"*
Actually I want to install solaris 10 update 4 on this server.
Any help would be greatly appreciated.
Thanks,
Sachin

That system may be new for you, but Sun stopped selling them in March 2006.
Now, as for the "No memory Detected" message ?
There are four DIMM slots on the systemboard.
Make sure they actually have RAM installed to them.
The manuals for your "new" V100 can be found at:
http://docs.sun.com/app/docs/coll/v100

Install Solaris 8 on Ultra Sparc 5

Hello! All
I am trying to format my hard Drive which running on Solaris 7 and install Solaris 8. Could someone tell me the step by step process(in detail) to finish this job?
Thanks
John

at the <ok> prompt,
boot cdrom -s
when you get the # prompt, type format. select the disk you want to put S8 on, I guess it will be c0t3d0...
select format again from within the format menu and this will format your disk..
When this is done, shutdown and then boot from S8 cd and just follow the 'noddy' instructions to load S8.
M

Upgrading Solaris 8 to Solaris 10 on SUN Sparc E2900 server

Hi,
We have a Sparc E2900 server which has Solaris 8 & Veritas Volume Manager 4.0. UFS & VXFS filesystems are under Veritas control.
We are planning to upgrade Solaris 8 to Solaris 10.
My questions are as follows
1) Can we upgrade from Solaris 8 to Solaris 10 directly ?
2) If Yes does Solaris 10 support Veritas Filesystem ?
3) Which is the best site to get information regarding upgradation ?
Regards,
Tejas J Raval

2) If Yes does Solaris 10 support Veritas Filesystem ?No, it dows not. If you want to use VxFS you still need to have Veritas products installed on this server

Help! Having Trouble Installing Solaris 10 on a SPARC machine

Hi All,
I recently found a new job, and one of the requirements is I learn Solaris 10. I have successfully loaded the most recent x86 version on a laptop, but.....
My workplace has a sun blade 2500 (several actually) and I am trying to load the newest Solaris 10 SPARC version that I just downloaded. I downloaded it on my PC (Windows vista, yech), unpacked the ISO using winzip, and burned the files to a DVD. When I put that newly burned DVD into the sunblade 2500, I press stop-a, then type "boot cdrom", and after the reboot, I get a message saying
Bad magic number in disk label
Can't open disk label package
Can't open boot device
{0} ok
So for some reason my burned DVD is giving me a "bad magic number" error - and its not just one machine, all the machines I tried to load it on said the same thing.
Fortunately, a co-worker that recently left the company had Solaris 10 burned to a set of CDs (5 plus the language CD) and that installed well (albeit version 08/07 of Solaris 10).
So I am at the point where I can probably figure out how to upgrade the machine, but it bothers me that I couldnt successfully download the ISO from sun, unpack the contents, burn said contents to a DVD (using Windows), then take that DVD and install SPARC Solaris 10 on a sun blade 2500. I know that at some point I wont have the crutch of those CDs. Does anyone know what I was doing wrong? Is there a certain way you have to burn the DVD, or use a certain package to unpack the ISO for the SPARC version?
Thanks,
Brent

Hi,
Make sure that write your DVD at 8X speed.
Also Refer thread:
http://www.motherboardpoint.com/bad-magic-number-disk-label-t146549.html
Regards,
X A H E E R

Getting an error 'Cannot open Boot device' while trying to install Solaris

Hi,
We were trying to install Solaris * on a Sun Sparc system and the CD rom drive does not seem to get recognised. When we try booting from cd rom we get an error 'Cannot open boot device' .
This server was up & running and we were trying to remove a hard disk that had failed and modified the vfstab script . After that the system failed to even boot up. So when we tried reinstalling the OS we are running into this problem.
Am new to this technology ...And any help would be greatly appreciated. .....
Thanks

Cdrom drive must be scsi device 6
I assume you are running < boot cdrom> at the ok prompt
also at the ok prompt run the command <probe-scsi> (without the angled brackets) you need to see the following:
Target 6
Unit 0 Removable read only device TOSHIBA XM.......bigpileofnumbers
If not, check the cdrom drive and the cdrom inside
hope this helps
Alan

Are there any rough processes for Solaris administrator to setup Sun LDAP as nameing server at Sun sparc host? like: 1st: modify /etc/nfsswitch.nfs 2nd: add LDAP server in /etc/hosts. 3rd: ......

Besides, can we install the LDAP server in sparc hosts as nameing system? Can we use Sun LDAP server or iPlanet Directory Server? or need BIND DNS server too?

There is a nice book from Michael Haines and Tom Bialaski: "Solaris and LDAP Naming Services" which contains all you need to configure Directory Server, LDAP, Naming Switch...
Ludovic.

Needed help in Installing Solaris 10 on sparc box from windows remotely

Hi All,
I have few Sun Ultra Sparc boxes. I m accessing them only through putty session(serail port) from my windows system.
Now there is a need for me to install Solaris 10 in the sparc box. But the sparc box doesn't have any DVD drive. I have an external DVD drive.
Can somebody help me out to install Solaris on the sparc box with the components I have.
1) Windows system with putty
2) External DVD drive
3) Sun sparc box.
Thanks for your help,
T.R.Santhosh

If you run into a problem that causes the machine not to boot, you can't interact with it via putty. You'd need a physical connection, usually either the keyboard and screen or a serial connection. I would always plan to be able to do so during an upgrade.
If you have sufficient disk space, the easiest thing to do would be to copy over the DVD iso, then mount it up with lofi, and do a live upgrade.
Windows doesn't read rockridge format disks. I would worry that having the windows machine read the ISO filesystem and send the files over would cause name issues. That's why getting the full ISO and mounting it locally on the Sparc is best. Fortunately, it doesn't require a physical drive.
Darren

SAP Performance Problem with Oracle 10 on Sun SPARC T5240 server

Dear Friends,
We have a performance problem after migrating our SAP ERP 6.0 basis system. We moved to new servers a month ago.
According to SAP EarlyWatchAlert Report, CPU response time is too high, altough CPU utilization is never more than 5%,
The current system is :
Database server : Sun SPARC Enterprise T5240 Server - 2 CPU´s with 6 core, 8 thread, 1.2 Ghz 32 GB RAM
and we use another identical configured server as an application server.
Database is Oracle 10.2.0 and operating system is Solaris 10.
The problem is average CPU response time is 450 ms, and max. CPU load is %5 percent.
Pre-migration configuration with old servers, we had CPU response : 150 ms and max CPU load: 50%.
Old configuration : 2 X HP rp3440, 2 X PA 8800 CPU (2 core, 1.0 GHz).
Have you got any experience with a similar situation, which setting might be wrong for not fully utilizing server CPU´s?
or do you know any similar configuration for benchmark?
Thanks in advance
Uzan

Our organization upgraded an application - The vendor had originally suggested a T2000. When we finally migrated onto it, the performance was worse than the older version of the application. The vendor hadn't yet tested the combination of T2000 and 10.2 with their application when they had made that hardware recommendation, they subsequently revised their recommendations. We ended up with an M4000.
The application performance, IMHO, still stinks. But that's because it's a java based application written for database independence.
The interesting item to note here, is that in the application teams 'selective' testing - everything worked fine. When the testing was extended to include users who didn't follow the 'test plan', they found performance begin to tank. Then with more users, more testing, they found that the T2000 was not going to perform well. The test plan by the apps team was not sufficient to find the issues, and they did not include any load testing!
Edited by: dbtoo on Jun 5, 2009 11:20 AM

Install Solaris 8 on SPARC system

Hi,
I'm new in Unix/Solaris. I tried to install solaris 8 on a sparc system, I downloaded (SOL-8-1_01-FCS-BIN-SPARC-V1 and V2) and i burned 2 CD as. On the sparc system is already SUNOS 5.6 installed. But each time I tried to boot the system it "hang" after the message:" starting rpc services: rcpbind keyserv nis_cachemgr done." What ever I type after this message has no effect at all. I'm allowed to format the disk (home user). The CD-rom player is attached to the Sparc but can not boot the CD. Is there anyone who can help me.
I downloaden olso the pdf files but they were no use for me at this moment.

Hello,
you will have to go to OK prompt and then boot with CDROM.
1.login as root and then type
#eeprom auto-boot?=false
2.reboot the system. the system will stop at the OK prompt.
3. then type:
OK boot cdrom install
you should see Solaris install program and follow its instruction.
And the error you see seems to be caused by bad network connection

Mistake installing solaris 10 in server Sun Sparc Entreprise 220r

Similar Messages

Maybe you are looking for