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

Similar Messages

Solaris 9 in a Sun Fire V100 Box ServerSocket Bug

I am running Solaris 9 in a Sun Fire V100
I am having a problem openning Sockets where programs are written in Java.
The program is written in Java with the ServerSocket class.
I wrote a very simple class to test.
The port is available of course I already verified it.
I checked with the SecurityManager to verify this is not a
security policy but I receive a null from the System.getSecurityManager
which means there is no securityu manager installed.
I have many other apllications that are able to open ports and listen, but Java seams
to be having problem in Solaris 9. I have tried 5 different versions of Java. Last version
I tried is jsdk 1.4.2_05.
The same thing happens with Tomcat that crashes while
trying to open a listening Socket.
ServerSocket server;
try
server = new ServerSocket(8005,1024, InetAddress.getByName("127.0.0.1"));
System.out.println("BINDING SUCCESFUL");
catch(Exception e)
System.out.println(e);
System.exit(-1);
while(true)
try
Socket clientSocket = server.accept();
ClientHandler2 t = new ClientHandler2(clientSocket);
t.start();
catch(IOException e)
System.err.println( e );
Is this a well known bug...
Can anyone be so kind to help me up with this terrible matter
Thank you,
Juanpablo Lajud

Hi,How to set my link up in solaris 10 ?
I dont know want happend to my machine solaris v440 it suddenly disconnected from n/w and finally i came to know that is a problem with NIC card..i din't find any light's glowing back side of the machine at NIC card.
can any one help me in this pls how can i proceed furture for getting my NIC back?
and i have excuted few commands
#ndd -set /dev/ce instance 0
#ndd -set /dev/ce adv_1000fdx_cap 1
#ndd -set /dev/ce adv_autoneg_cap 0
I have got dladm show-dev is
ce0 link: unknown speed: 1000 Mbps duplex: full
ce1 link: unknown speed: 0 Mbps duplex: unknown
I dont understand that why my link is showing still unknown ...any help..

How to install Oracle VM server on Sun Fire v100 server

Hi All
I have just a Sun Fire V100 Server.
How to install Oracle VM server on Sun Fire v100 server?
Thankyou and best regards,
Thiensu

user8248216 wrote:
I have install Oracle VM Server successful on PC Core 2 dual 2.93Ghz.
But Oracle VM Server does not detect onboard Network card.Your NIC needs to be supported by Oracle Linux 5 Update 3 to work with Oracle VM Server 2.2. If it's too new, then it will not be seen. Also, please start a new topic for each question. This new question is not relevant to the original topic.
Edited by: Avi Miller on Aug 19, 2011 12:46 PM

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]

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

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)>

Clone the Solaris OS from Sun Fire X4200 M2 to Sun Fire X4100 M2

Dear all,
May anyone help me?
I want to clone the all slices (whole hard disk) in Solaris 10 OS from Sun Fire X4200 M2 Server and then restore it back to Sun Fire X4100 M2 Server. Is it possible to do this? If "Yes", may show me how to do it?
I appreciate for your help.
Thanks you in advance,
Soret,

Hi.
It's possible, but depend of used file systems, used or not voluem manager, hardware configuration.
Possible steps:
1) Make Backup x4200 ( on internal disk or third NFS storage )
2) Boot x4100 from installation DVD in to Single user.
2.1 Partitioning disk
2.2 Create New FS
2.3 Restore backup on new FS. ( need configuree network, and mount disks with backups over NFS )
2.4 use devfsadm for rebuild device tree
chroot <new_root> devfsadm
2.5 Make neaded customization on new system.
2.6 Install grub and bootblok ( installboot )
2.7 Umount all new FS; halt system.
3) Try normal boot new system.
Some step for create new disk you may do on original server. Install new disk and make restore on it.
After- return this disk to x4100.
Regards.

Installation of Solaris 8 in Sun Fire V215

Hello.
I'm trying to install Solaris 8 on a Sun Fire V215 which comes with Solaris 10 pre-installed. I'm doing so because some of the software we developed seems to have problems onSolaris other than version 8.
Is Sun Fire V215 compatible with solaris 8??
I get the following error when trying to install SOlaris 8 update 2/04 from a CD:
Invalid install CD-ROM for karch "sun4u"
I've been looking all over the documentation of SUn Fire V215 to see whether it was possible or not to install such an old version of Solaris, but unluckily I never found anything. Can anyone help me?
Thank you very much
Jorge

That is not ever going to work.
Solaris 8 is a discontinued product.
That hardware will only work with SOlaris 10 and one specific release of Solaris 9.
http://sunsolve.sun.com/handbook_pub/Systems/SunFireV215/SunFireV215.html
If you want a more complete explanation,
go back to your Sun sales representative, else open a support case with Sun.

Migrate Solaris 10 from Sun-Fire-V240 to T5140

Hi everyone.
Is it possible to migrate Solaris 10 running Oracle 10g RAC on a Sun-Fire-V240 to a T5140 without having to reinstall OS + Oracle-DB-software from scratch?
Because both servers are based on a SPARC-processor, I am guessing that it should be possible to patch/configure the OS to run on a T5140 instead of a V240.
Well, I have tried the following:
1) Booting the T5140 using "disk1" (c1t0d0).
2) Formatting "disk2" (c1t1d0) in the same number of slices I have on the V240.
3) newfs on every slice, mounting and copying from V240 to T5140 using "ufsdump/ufsrestore" over ssh.
4) Editing the /etc/vfstab.
5) installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t1d0s0
...Because I haven't got the correct platform for T5140 on the V240-install (even though it is patched recently), I used the one on the T5140.
6) Removed the /etc/path_to_inst and tried to "boot -ar" (after switching disk2 to "disk1-controller-position").
When 1-6 did not work, I tried a few other things:
a) Replace the /platform and /usr/platform with the ones on the T5140 (Generic_137111-06 sun4v sparc SUNW,T5140).
b) Replace the /kernel with the one from the T5140 (Generic_137111-06 sun4v sparc SUNW,T5140).
c) Replace the /etc/path_to_inst with the one from the T5140.
No luck so far.
So I am left with my initial question - is it possible to patch or configure the V240-Solaris10-installation, so it will run on a T5140?
Thanks,
Niels

In theory you can, but the question is if you want the issues. Migrating between architectures is only recommended for sparse zones, but not for any other. In this case it's you go from sun4u to sun4v which will give you enough of issues beside te changing hardware paths and configuration items.

Failed to install Solaris 10 with Jump Start

Hi all:
When install Solaris 10 with Jump Start method. I met below error:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
{3} ok boot net -install
SC Alert: Host System has Reset
Probing system devices
Probing memory
Probing I/O buses
screen not found.
Rebooting with command: boot net -install
Use is subject to license terms.
whoami: no domain name
Hardware watchdog enabled
WARNING: exec(nstall) failed (file not found).
(Could not start init) Program terminated
{1} ok
Thanks a lots!

thats because you wrote "-install", which will be parsed as "-i nstall", hence your system will try to execute a kernel named "nstall".
The proper syntax is "boot net - install", with spaces on both sides of the -.
.7/M.

How to install megaraid manager on sun fire x4170 m2 running on oracle vm

hi..
hope some can help me about below issue
1.how to install lsi megaraid manager on sun fire x4170 m2 running on oracle vm server 3.0.3 ?
sun fire x4170 m2 --> oracle vm server 3.0.3
sun fire x4170 m2 --> oracle linux 6.2 ( install lsi megaraid manager and able to open megaraid manager locally )
what i want is install megaraid manager or agent on oracle vm server , then i can use oracle linux with megaraid manager to ocntrol raid disk on oracle vm server 3.0.3 , i download the driver and software from my oracle support , unlucky not include oracle vm 3.0.3 .
hope some one can help me
tq

889759 wrote:
1.how to install lsi megaraid manager on sun fire x4170 m2 running on oracle vm server 3.0.3 ?You can't: MegaRAID Manager is not supported on Oracle VM 3.0.

Disk Access Failed while Installing Solaris Container.

I have setup 5 guest domains together with the Control Domain.
$ ldm list
Name State Flags Cons VCPU Memory Util Uptime
primary active -t-cv SP 4 4G 0.8% 2d 2h 15m
secondary active -t--v 5000 4 2G 0.5% 3h 5m
dmz active -t--- 5001 8 2G 0.0% 46m
sunray inactive -----
application inactive -----
identity active -t--- 5002 4 4G 0.1% 1h 2m
In each of the guest domain, I plan to install a number of Solaris Containers to run different applications. While installing one Solaris container (zoneadm �z <zone name> install) in dmz domain, I start the installation/configuration (either zoneadm �z <zone name> install or zlogin �C <zone name>) of another Solaris container in identity domain. Everything starts OK until half way I get an error message as follow:
Jun 13 18:33:16 dmz vdc: NOTICE: [1] disk access failed.
The installation of the Solaris Container in dmz halts as soon as I see the message above. Nothing will work except a force stop in the Control Domain using ldm stop �f dmz and restart.
What happen to the Solaris Container installation/configuration in identity domain? It either continues the process without error or fails with the same error message shortly after. For example,
Jun 13 18:33:24 identity vdc: NOTICE: [1] disk access failed.
The vdisks for each guest domain are setup by following the steps on section �Using ZFS Over a Virtual Disk� in LDoms 1.0 Administration Guide. Each guest domain is booted from a disk image in the Control Domain and has two 9GB data vdisks (mapped to two physical 9GB disks on A5200 disk array) running ZFS striping. Each guest domain vdisks are serviced by a separate vdisk server.
Any idea?

I am not sure if multiple virtual disk servers are officially supported under current LDoms release.
I had tried using only one virtual disk server. The same problem exhibited. I thought may be the vds was not able to keep up with the virtual disk I/O. That's why I setup multiple vds.

Fail to install solaris 8 for intel

hello. i downloaded three files and made a CD for each one. but during the installing on a Dell PowerEdge 6450
(4 x Pentium III 550)which has two AIC 7899 ultra160/m SCSI adapters and a Dell PERC RAID controller (i note they are not included in the hardware compatibility list of solaris 8 for
intel), the install process stopped when it was "I2O Nexus:
initializing IO processor 0" and didn't go any further. when i attempt to intall it on another machine(2 x PIII 1000) which has a AIC 7892 ultra160/m SCSI adapter, the process
stopped saying "no disks that meet the criteria in the solaris installer documentation found" after solaris web start began to run. before this, it has reported resource conflict of PNP0C01
and ISY0050. and the installing stopped when "using RPC bootparams for network configuration information" on a PIII 800 PC. what's wrong with my installing. is it due to the incompatibility of hardware or something else?how to resolve it if possible? help is in need very much.besides,what does
DCA mean?sorry, i'm a newbie in this field.
thanks
xoing

Hi,
Problem with PERC RAID controller card.
You try to install the driver for AIC 7899 and Dell PERC RAID controller card. In dell computers, they have dell PERC RAID controller driver for Solaris 7 version. They don't have the driver for solaris 8 version.
You can download driver for SCSI AIC 7899 from this URL:
http://www.adaptec.com/worldwide/support/driverdetail.html?cat=/Product/ASC-39160&filekey=u160_slrs_v121_dd.img.Z
Then you check with your local dell support provider for PERC RAID controller driver for solaris 7 and solaris 8.
Thanks.
revert back.
regards,
Senthilkumar
SUN - DTS

How can I do to make the Sun Fire V100 quieter?

It is rated at 60 decibels when idling! And I would like to have it in my lounge, what is the first suggestions for making it quieter? Has anybody done this before?
[http://sunsolve.sun.com/handbook_pub/validateUser.do?target=Systems/SunFireV100/spec&source=|http://sunsolve.sun.com/handbook_pub/validateUser.do?target=Systems/SunFireV100/spec&source=]

Use
myDialog m_dlg = new myDialog(appletFrame);Instead of
myDialog m_dlg = new myDialog();

Failed to install solaris on new "Sun Fire V100"

Similar Messages

Maybe you are looking for