Install Solaris 10 Sparc on Ultra 40

I am trying to install solaris 10 Sparc on an Sun Ultra 40 i386 pc. Is that able to be done. I have libraries that only work on sparc machines. Thanks for any help.

SPARC and i386 are different CPUs. They are not compatible.
You run SPARC installations on SPARC hardware, you run x86 installations on x86 hardware.
Darren

Similar Messages

  • 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]

  • Solaris 8 SPARC SUN ULTRA 10 - WP event on CPU0

    Hii everyone
    My Server SUN 5.8 has rebooted itself after having been generated internally out of the ordinary events related to CPU.
    The log en the file.messages and output of prtdiag is:
    {color:#ff0000}Apr 15 21:20:10 server1 SUNW,UltraSPARC-IIi: [ID 727863 kern.warning] WARNING: [AFT1] WP event on CPU0, errID 0x000091eb.e4c47547{color}
    {color:#ff0000}Apr 15 21:20:10 server1 AFSR 0x00000000.00800040<WP> AFAR 0x000001ff.dbfffdd8{color}
    {color:#ff0000}Apr 15 21:20:10 server1 AFSR.PSYND 0x0040(Score 95) AFSR.ETS 0x00 Fault_PC 0x4e3a98{color}
    {color:#ff0000}Apr 15 21:20:10 server1 UDBH 0x0000 UDBH.ESYND 0x00 UDBL 0x0000 UDBL.ESYND 0x00{color}
    {color:#ff0000}Apr 15 21:20:10 server1 unix: [ID 836849 kern.notice] {color}
    {color:#ff0000}Apr 15 21:20:10 server1 ^Mpanic[cpu0]/thread=30001d205a0: {color}
    {color:#ff0000}Apr 15 21:20:10 server1 unix: [ID 401469 kern.notice] [AFT1] errID 0x000091eb.e4c47547 WP Error(s){color}
    {color:#ff0000}Apr 15 21:20:10 server1 See previous message(s) for details{color}
    {color:#ff0000}Apr 15 21:20:10 server1 unix: [ID 100000 kern.notice] {color}
    {color:#ff0000}Apr 15 21:20:10 server1 genunix: [ID 723222 kern.notice] 000002a10091d6c0 SUNW,UltraSPARC-IIi:cpu_aflt_log+4e0 (2a10091d77e, 1, 10143958, 2a10091d908, 2a10091d7cb, 10143980){color}
    {color:#ff0000}Apr 15 21:20:10 server1 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000001 000002a10091d9e0 0000000000000003 0000000000000010{color}
    {color:#ff0000}Apr 15 21:20:10 server1 %l4-7: 0000000000000001 00000000845d5bc0 0000000084407f7c 0000000000000000{color}
    {color:#ff0000}Apr 15 21:20:10 server1 genunix: [ID 723222 kern.notice] 000002a10091d910 SUNW,UltraSPARC-IIi:cpu_async_error+7dc (1, 1ffdbfffdd8, 800040, 0, 0, 0){color}
    {color:#ff0000}Apr 15 21:20:10 server1 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000000 0640000000800040 0000000000000000 0000000000800040{color}
    {color:#ff0000}Apr 15 21:20:10 server1 %l4-7: 000002a10091d9e0 000002a10091dba0 0000000000000000 0000000000000000{color}
    {color:#ff0000}Apr 15 21:20:10 server1 unix: [ID 100000 kern.notice]{color}
    Apr 15 21:20:10 server1 genunix: [ID 672855 kern.notice] syncing file systems...
    Apr 15 21:20:10 server1 genunix: [ID 733762 kern.notice] 6
    Apr 15 21:20:11 server1 genunix: [ID 733762 kern.notice] 3
    Apr 15 21:20:12 server1 genunix: [ID 904073 kern.notice] done
    Apr 15 21:20:13 server1 genunix: [ID 353387 kern.notice] dumping to /dev/dsk/c0t0d0s1, offset 107479040
    Apr 15 21:20:24 server1 genunix: [ID 409368 kern.notice] ^M100% done: 13157 pages dumped, compression ratio 3.21,
    Apr 15 21:20:24 server1 genunix: [ID 851671 kern.notice] dump succeeded
    Apr 15 21:21:08 server1 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.8 Version Generic_108528-09 64-bit
    Apr 15 21:21:08 server1 genunix: [ID 913631 kern.notice] Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
    Apr 15 21:21:08 server1 genunix: [ID 678236 kern.info] Ethernet address = 0:3:ba:c:c6:5e
    Apr 15 21:21:08 server1 unix: [ID 389951 kern.info] mem = 1048576K (0x40000000)
    Apr 15 21:21:08 server1 unix: [ID 930857 kern.info] avail mem = 1027547136
    Apr 15 21:21:08 server1 rootnex: [ID 466748 kern.info] root nexus = Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 440MHz)
    Apr 15 21:21:08 server1 rootnex: [ID 349649 kern.info] pcipsy0 at root: UPA 0x1f 0x0
    Apr 15 21:21:08 server1 genunix: [ID 936769 kern.info] pcipsy0 is /pci@1f,0
    Apr 15 21:21:08 server1 pcipsy: [ID 370704 kern.info] PCI-device: pci@1,1, simba0
    Apr 15 21:21:08 server1 genunix: [ID 936769 kern.info] simba0 is /pci@1f,0/pci@1,1
    Apr 15 21:21:08 server1 pcipsy: [ID 370704 kern.info] PCI-device: pci@1, simba1
    Apr 15 21:21:08 server1 genunix: [ID 936769 kern.info] simba1 is /pci@1f,0/pci@1
    Apr 15 21:21:18 server1 simba: [ID 370704 kern.info] PCI-device: ide@3, uata0
    Apr 15 21:21:18 server1 genunix: [ID 936769 kern.info] uata0 is /pci@1f,0/pci@1,1/ide@3
    Apr 15 21:21:18 server1 uata: [ID 114370 kern.info] dad0 at pci1095,6460
    Apr 15 21:21:18 server1 uata: [ID 347839 kern.info] target 0 lun 0
    Apr 15 21:21:18 server1 genunix: [ID 936769 kern.info] dad0 is /pci@1f,0/pci@1,1/ide@3/dad@0,0
    Apr 15 21:21:19 server1 dada: [ID 365881 kern.info] <ST320414A cyl 39533 alt 2 hd 16 sec 63>
    Apr 15 21:21:19 server1 uata: [ID 114370 kern.info] dad1 at pci1095,6460
    Apr 15 21:21:19 server1 uata: [ID 347839 kern.info] target 1 lun 0
    Apr 15 21:21:19 server1 genunix: [ID 936769 kern.info] dad1 is /pci@1f,0/pci@1,1/ide@3/dad@1,0
    Apr 15 21:21:20 server1 dada: [ID 365881 kern.info] <Maxtor 6E040L0 cyl 19156 alt 2 hd 16 sec 255>
    Apr 15 21:21:20 server1 swapgeneric: [ID 308332 kern.info] root on /pci@1f,0/pci@1,1/ide@3/disk@0,0:a fstype ufs
    Apr 15 21:21:20 server1 simba: [ID 370704 kern.info] PCI-device: ebus@1, ebus0
    Apr 15 21:21:20 server1 ebus: [ID 521012 kern.info] power0 at ebus0: offset 14,724000
    Apr 15 21:21:20 server1 genunix: [ID 936769 kern.info] power0 is /pci@1f,0/pci@1,1/ebus@1/power@14,724000
    Apr 15 21:21:20 server1 ebus: [ID 521012 kern.info] su0 at ebus0: offset 14,3083f8
    Apr 15 21:21:20 server1 genunix: [ID 936769 kern.info] su0 is /pci@1f,0/pci@1,1/ebus@1/su@14,3083f8
    Apr 15 21:21:20 server1 ebus: [ID 521012 kern.info] su1 at ebus0: offset 14,3062f8
    Apr 15 21:21:20 server1 genunix: [ID 936769 kern.info] su1 is /pci@1f,0/pci@1,1/ebus@1/su@14,3062f8
    Apr 15 21:21:21 server1 rootnex: [ID 349649 kern.info] ffb0 at root: UPA 0x1e 0x0
    Apr 15 21:21:21 server1 genunix: [ID 936769 kern.info] ffb0 is /SUNW,ffb@1e,0
    Apr 15 21:21:21 server1 unix: [ID 987524 kern.info] cpu0: SUNW,UltraSPARC-IIi (upaid 0 impl 0x12 ver 0x91 clock 440 MHz)
    Apr 15 21:21:21 server1 ebus: [ID 521012 kern.info] se0 at ebus0: offset 14,400000
    Apr 15 21:21:21 server1 genunix: [ID 936769 kern.info] se0 is /pci@1f,0/pci@1,1/ebus@1/se@14,400000
    Apr 15 21:21:22 server1 hme: [ID 517527 kern.info] SUNW,hme0 : PCI IO 2.0 (Rev Id = c1) Found
    Apr 15 21:21:22 server1 simba: [ID 370704 kern.info] PCI-device: network@1,1, hme0
    Apr 15 21:21:22 server1 genunix: [ID 936769 kern.info] hme0 is /pci@1f,0/pci@1,1/network@1,1
    Apr 15 21:21:25 server1 genunix: [ID 454863 kern.info] dump on /dev/dsk/c0t0d0s1 size 512 MB
    Apr 15 21:21:26 server1 hme: [ID 517527 kern.info] SUNW,hme0 : Internal Transceiver Selected.
    Apr 15 21:21:26 server1 hme: [ID 517527 kern.info] SUNW,hme0 : Auto-Negotiated 100 Mbps Half-Duplex Link Up
    Apr 15 21:22:36 server1 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
    Apr 15 21:22:36 server1 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
    Apr 15 21:23:36 server1 named[184]: [ID 295310 daemon.notice] starting. in.named BIND 8.2.2-P5 Wed Jan 15 04:35:48 PST 2003
    Apr 15 21:23:36 server1 Generic Patch-5.8-January 2003
    Apr 15 21:23:37 server1 named[221]: [ID 295310 daemon.notice] Ready to answer queries.
    Apr 15 21:23:37 server1 named[221]: [ID 295310 daemon.warning] check_hints: A records for L.ROOT-SERVERS.NET class 1 do not match hint records
    Apr 15 21:23:38 server1 savecore: [ID 570001 auth.error] reboot after panic: [AFT1] errID 0x000091eb.e4c47547 WP Error(s)
    Apr 15 21:23:38 server1 See previous message(s) for details
    Apr 15 21:23:57 server1 pseudo: [ID 129642 kern.info] pseudo-device: tod0
    Apr 15 21:23:57 server1 genunix: [ID 936769 kern.info] tod0 is /pseudo/tod@0
    Apr 15 21:23:57 server1 pseudo: [ID 129642 kern.info] pseudo-device: pm0
    Apr 15 21:23:57 server1 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
    Apr 15 21:23:59 server1 pseudo: [ID 129642 kern.info] pseudo-device: vol0
    Apr 15 21:23:59 server1 genunix: [ID 936769 kern.info] vol0 is /pseudo/vol@0
    Apr 15 21:23:59 server1 scsi: [ID 365881 kern.info] /pci@1f,0/pci@1/scsi@1 (glm0):
    Apr 15 21:23:59 server1 Rev. 6 Symbios 53c875 found.
    Apr 15 21:23:59 server1 scsi: [ID 365881 kern.info] /pci@1f,0/pci@1/scsi@1 (glm0):
    Apr 15 21:23:59 server1 glm0 supports power management.
    Apr 15 21:23:59 server1 simba: [ID 370704 kern.info] PCI-device: scsi@1, glm0
    Apr 15 21:23:59 server1 genunix: [ID 936769 kern.info] glm0 is /pci@1f,0/pci@1/scsi@1
    Apr 15 21:23:59 server1 scsi: [ID 193665 kern.info] sd0 at uata0: target 2 lun 0
    Apr 15 21:23:59 server1 genunix: [ID 936769 kern.info] sd0 is /pci@1f,0/pci@1,1/ide@3/sd@2,0
    Apr 15 21:24:02 server1 pseudo: [ID 129642 kern.info] pseudo-device: fcode0
    Apr 15 21:24:02 server1 genunix: [ID 936769 kern.info] fcode0 is /pseudo/fcode@0
    Apr 15 21:24:06 server1 ebus: [ID 521012 kern.info] fd0 at ebus0: offset 14,3023f0
    Apr 15 21:24:06 server1 genunix: [ID 936769 kern.info] fd0 is /pci@1f,0/pci@1,1/ebus@1/fdthree@14,3023f0
    Apr 15 21:24:26 server1 pseudo: [ID 129642 kern.info] pseudo-device: pm0
    Apr 15 21:24:26 server1 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
    ================================= *{color:#0000ff}DATOS DE DIAGNOSTICO{color}* ============================================
    server1 ROOT [9] psrinfo -v
    Status of processor 0 as of: 04/16/08 09:45:18
    Processor has been on-line since 04/15/08 21:21:20.
    The sparcv9 processor operates at 440 MHz,
    and has a sparcv9 floating point processor.
    server1 ROOT [10]
    server1 ROOT [9] uname -a
    SunOS server1 5.8 Generic_108528-09 sun4u sparc SUNW,Ultra-5_10
    server1 ROOT [19] /usr/platform/sun4u/sbin/prtdiag -v
    System Configuration: Sun Microsystems sun4u Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 440MHz)
    System clock frequency: 110 MHz
    Memory size: 1024 Megabytes
    ========================= CPUs =========================
    Run Ecache CPU CPU
    Brd CPU Module MHz MB Impl. Mask
    0 0 0 440 2.0 12 9.1
    ========================= IO Cards =========================
    Bus# Freq
    Brd Type MHz Slot Name Model
    0 PCI-1 33 1 ebus
    0 PCI-1 33 1 network-SUNW,hme
    0 PCI-1 33 2 SUNW,m64B ATY,GT-C
    0 PCI-1 33 3 ide-pci1095,646.1095.646.3
    0 PCI-2 33 1 scsi-glm Symbios,53C875
    Bus Freq
    Brd Type MHz Slot Name Model
    0 UPA 110 30 FFB, Double Buffered SUNW,501-4788
    No failures found in System
    ===========================
    ========================= HW Revisions =========================
    ASIC Revisions:
    Cheerio: ebus Rev 1
    FFB Hardware Configuration:
    Board rev: 2
    FBC version: 0x3241906d
    DAC: Brooktree 9070, version 1
    3DRAM: Mitsubishi 130b, version 2
    System PROM revisions:
    OBP 3.29.0 2000/12/20 18:45 POST 3.1.0 2000/06/27 13:56
    === *{color:#0000ff}SECOND TEST{color}*
    server1 ROOT [4] /usr/platform/`uname -i`/sbin/prtdiag -v
    System Configuration: Sun Microsystems sun4u Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 440MHz)
    System clock frequency: 110 MHz
    Memory size: 1024 Megabytes
    ========================= CPUs =========================
    Run Ecache CPU CPU
    Brd CPU Module MHz MB Impl. Mask
    0 0 0 440 2.0 12 9.1
    ========================= IO Cards =========================
    Bus# Freq
    Brd Type MHz Slot Name Model
    0 PCI-1 33 1 ebus
    0 PCI-1 33 1 network-SUNW,hme
    0 PCI-1 33 2 SUNW,m64B ATY,GT-C
    0 PCI-1 33 3 ide-pci1095,646.1095.646.3
    0 PCI-2 33 1 scsi-glm Symbios,53C875
    Bus Freq
    Brd Type MHz Slot Name Model
    0 UPA 110 30 FFB, Double Buffered SUNW,501-4788
    No failures found in System
    ===========================
    ========================= HW Revisions =========================
    ASIC Revisions:
    Cheerio: ebus Rev 1
    FFB Hardware Configuration:
    Board rev: 2
    FBC version: 0x3241906d
    DAC: Brooktree 9070, version 1
    3DRAM: Mitsubishi 130b, version 2
    System PROM revisions:
    OBP 3.29.0 2000/12/20 18:45 POST 3.1.0 2000/06/27 13:56
    ============================================
    I don't know exactly what is the origin of the problem, How to solver or how to prevent to avoid further problems. This is the first time I have had this Kind of problem on my Server SUN.
    I appreciate greatly, any tip o help.
    Jimmy

    Yup.
    EOL in November 2002
    Which means EOSL November 2007
    http://sunsolve.sun.com/handbook_pub/validateUser.do?target=Systems/U10/U10
    Unless you've somehow maintained a service contract on that system,
    by specific system serial number,
    your best bet is to haunt an online auction site (such as Ebay),
    and get a replacement cpu or cpus for shelf stock.
    Your current OBP patch level is only down two patch levels,
    but your kernel patch level is essentially "never patched".
    If it were patched better it may have noticed the issue a lot sooner.
    Expect to replace that cpu.

  • Unable to install solaris 8/9 on Ultra 10

    Tried solaris 8/9 , downloaded from sun website , burned using Nero, gives error:
    boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f file and args:
    bad magic number in disk label
    cant open disk label package
    cant open boot device
    tried most of the suggestions from sun installation website but couldnt solve the problem yet..
    OBP , version 3.11, 12
    show-disks -> a) /pci@1f,0/pci@1,1/ide@3/cdrom
    tried nvalias cdrom1 /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f
    boot cdrom1 but still same error
    probe-ide gives device2 (secondary master)
    removable atapi model: crd-8240B
    i dont have another cdrom to check whether it is a bad cdrom..
    pleaseeee help
    machine is ultra 10 , 4.3gb, 300 mhz , 256 mb ram from ebay

    From your post I do not believe the CD drive is at fault. I believe the machine you wrote the CD is at fault. I would create another set of bootable CD's using a different machine with a CD-R/W drive. I would write the CD at 4 speed and try again. Some Ultra 10's have the slower 4 speed CD drive. What OBP is telling you is the CD appears to be 'blank' or 'corrupted', that's the cause for the 'bad magic number' error. If you can find a bootable Solaris Installation CD I'm sure it would boot just fine. Another thing you might look at, I've seen this be a problem with CD's, is the recordable surface. Are there any finger prints, smears etc? If so, clean the record surface then try booting the Ultra 10 again.
    Michael

  • Error while installing Solaris 10 using Solaris CD

    I'm getting an error while installing Solaris 10 in an Ultra 10 box.
    I have Solaris CDs (Total 4) and I have installed Solaris 10 in a Ultra 250 box , I did not get any problem. That means CDs are fine.
    But when I try to boot the CD 1 from bootPROM mode by giving the following command
    ok boot cdrom
    I get the following error :
    rebooting with CD command boot cdrom
    boot device : /pci@1f, 0/pci@1 , 1/idi@3/cdrom@2 ,0:f file and args
    Cant read disk label
    Cant open disk label package
    evaluating : boot cdrom
    Cant open boot device
    Then the box boots up with Solaris 8 which it has now..
    Can anyone please help me to solve this issue ?
    Thanks

    With the above information , I just wanted to tell you that the CD rom is getting detected as i can view all files in the CD.,,

  • How I can emulate Solaris 10 sparc on a Virtual Machine?

    Hi for all.
    Guys, I need to emulate an environment Solaris 10 in my job. We have an application that just run in this kind of environment. But, I found some problems when I try to install Solaris 10 Sparc on Virtual Box. I think that the problem is the type of architecture that are differents.
    So, someone knows a way to emulate Solaris 10 sparc architecture on a Virtual Machine. Doesn't matter the Virtual Machine application (Virtual Box, VMWare, etc..). Somebody Help me?

    HI Srini_Chavali
    I'm using the Solaris 10 u11.
    In fact, Virtual Box supports Solaris u6 and higher. I have an installation of Virtual Box running Solaris x86. But, the problem occurs when I try to create a Virtual machine to work with Solaris 10 Sparc architecture.
    The errors that appears on the screen are:
    "No bootable medium found! System Halted" and "FATAL: Could not read from the boot medium! System halted"
    This error occurs just with Architecture sparc.

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

  • How to Enable firewall on Solaris 10 SPARC Machine?

    Hi All,
    I have installed Solaris 10 SPARC & by default the firewall is disabled.
    Now i need to enable firewall?
    Can i know how to enable firewall Solaris 10 SPARC Machine?
    Also can i know how to open up specific TCP & UDP ports?

    What exactly are you looking for? By default Solaris is a secure operating system, but can be tuned to be more or less secure. The link above on IP Filtering is one way to make a system more secure, and is can be used to set up a firewall.
    -- Alan

  • Need help installing Solaris 10

    Hello expert,
    I installed solaris 10 on my Ultra 2 box a few months back, for learning purposes, then I stopped using it. NOW I FORGOT ALL THE PASSWORD, INCLUDING ROOT PASSWORD.
    I want to resintall solaris 10, but how do i get to the ok prompt if I don't remember the root password?
    Please let me know if there is any other way that I can reinstall solaris from scratch.
    thanks for all your help

    This question is asked in these forums about every six weeks.
    It's answered every time.
    Most of the answers are finally....
    Use Google.
    search with solaris root password
    see 2 milion results from such a search
    the information isn't a secret
    (you won't need to go beyond the first page of search results.)
    Google does indeed work for this issue.
    Oh, and have your OS installation CD's ready.
    You'll need them to repair your computer.
    ... and yes, you can repair it without reinstalling anything.
    .( teach a man to fish, versus give a man a fish )

  • 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

  • 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

  • Ethernet problems installing Solaris 10 on Ultra 5

    I am trying to install on a Sun Sparc Ultra 5 which I have inherited. The machine booted up OK with Solaris 7 with the old user's set up, but I do not have his ids or passwords.
    When I try to install Solaris 10, early in the boot it comes up with "attempting to configure interface hme0..."
    the a wait for a while then "Skipped interface hme0"
    The network is OK and so is the cable - I checked them by swapping the leads with my lap top which could access the network fine.
    I then went through and selected the language (English), selected 'networked', 'dhcp' then 'IPv6' then it comes up with "just a moment" then a long wait before "Could not contact a dhcp server on network interface hme0"
    The dhcp server on the University network was fine.
    I would be very grateful for any ideas or suggestions.
    Many thanks,
    Chris.

    Christian,
    The integrated NIC may or may not be working.
    I'm going to presume you have a Sun keyboard, a Sun mouse and a monitor connected.
    I'm also going to presume, unless you tell us otherwise, that you have never worked with Sun systems, before this Ultra-5.
    Boot the system.
    Just as you see a signal successfully activate the monitor, hold the STOP key and press the letter "A".
    This stop-a sequence will halt the boot process and leave you at OpenBoot. Your screen prompt will the the word <b>OK</b>
    There are many tests that you can perform at OBP, without invoking any OS. For today's tasks, you can prepare the chassis for a network circuit test.
    Do ...
    <b> OK set-defaults</b> <enter>
    <b>OK setenv auto-boot? false</b> <enter> (note the question mark character)
    <b>OK reset-all</b> <enter>
    Those three items will clear the OBP of any confusing or customized settings, then it will prepare the chassis to always stop automatically at the OK prompt, then it will write your choices to the PROM and reboot the system.
    You can reset the <i>auto-boot?</i> back to true when you are finished.
    After the reboot it should automatically stop at OK.
    If it does not do so, then you had a typo in your commands.
    Type <b>sifting watch</b> to be presented with all the command syntax that includes the word "watch". Find the network test that checks for connectivity.
    Do ...
    <b>OK watch-net</b> <enter>
    If the Ethernet port has link to a valid network, you will see dots scroll along. An occasional 'X' is a lost packet.
    You can download the 211+ page PDF file for the OBP 3.x command reference from Sun's documentation site, Docs.Sun.Com.
    http://docs.sun.com/app/docs/coll/1140.2?q=openboot+command+ reference
    This is all described in that PDF.

  • Problem installing Solaris on a Ultra 10

    I have been trying to install Solaris 10 but I can�t I don�t know why, after the first boot my Sparc 10 (Serial #16605019 � Host ID: 80fd5f5b � Ethernet address: 8:0:20:fd:5f:5b)) stop on the following step:
    Boot device: disk File and args:
    SunOs Release ��..
    Copyright �� All rights reserved.
    So, I tried to install Solaris 8 just to check with the problem was a media issue but the same thing happens
    Boot device: disk File and args:
    SunOS Release 5.8 Version Generic_108528-01 64-bit
    Copyright 1983-2000 Sun Microsystems, Inc. All rights reserved
    Therefore, OpenBSD works fine at the same machine.
    In conclusion, my Sparc 10 machine can�t run Solaris (even 8 or 10). Is it possible someone help me with this issue ?
    Following my workstation hardware configuration:
    UltraSPARC-Iii 440MHz
    1 GB Memory
    70GB Hard Drive
    DVD-RW
    OpenBoot 3.25, 1024 MB (50ns)

    ok probe-ide
    Device 0 ( Primary Master )
    ATA Model: MAXTOR STM380215A
    Device 1 ( Primary Slave )
    Not Present
    Device 2 ( Secondary Master )
    Removable ATAPI Model: HL-DT-STDVD-RAM GSA-H55N
    Device 3 ( Secondary Slave )
    Not Present
    ok boot -v
    Boot device: /pci@1f,0/pci@1,1/ide@3/disk@0,0 File and args: -v
    Size: 344496+88281+61647 Bytes
    SunOS Release 5.8 Version Generic_108528-01 64-bit
    Copyright 1983-2000 Sun Microsystems, Inc. All rights reserved.
    Ethernet address = 8:0:20:fd:5f:5b
    mem = 1048576K (0x40000000)
    avail mem = 1030299648
    root nexus = Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 440MHz)
    pcipsy0 at root: UPA 0x1f 0x0
    pcipsy0 is /pci@1f,0
    PCI-device: pci@1,1, simba0
    simba0 is /pci@1,1/pci@1,1
    PCI-device: pci@1, simba1
    simba1 is /pci@1f,0/pci@1
    PCI-device: ide@3, uata0
    uata0 is /pci@1f,0/pci@1,1/ide@3
    dad0 at pci1095,6460 target 0 lun 0
    dad0 is /pci@1f,0/pci@1,1/ide@3/dad@0,0
    <DEFAULT cyl 38307 alt 2 hd 16 sec 255>
    root on /pci@1f,0/pci@1,1/ide@3/disk@0,0:a fstype ufs
    PCI-device: ebus@1, ebus0
    power0 at ebus0: offset 14,724000
    power0 is /pci@1f,0/pci@1,1/ebus@1/power@14,724000
    su0 at ebus0: offset 14,3083f8
    su0 is /pci@1f,0/pci@1,1/ebus@1/su@14,3083f8
    su1 at ebus0: offset 14,3062f8
    su1 is /pci@1f,0/pci@1,1/ebus@1/su@14,3062f8
    PCI-device: SUNW,m64B@2, m640
    m640 is /pci@1f,0/pci@1,1/SUNW,m64B@2
    m64#0: 1280x1024, 4M mappable, rev 4750.7c
    cpu0: SUNW,UltraSPARC-IIi (upaid 0 impl 0x12 ver 0x91 clock 440MHz)

  • How can I install new versions of Fifefox on Solaris 9 Sparc?

    I use Firefox 2.0.0.20 on Solaris 9 Sparc, but I couldn't install any verions of Firefox major version 3.
    There is a great site, http://www.sunfreeware.com/mozilla.html, that looks it has a possibles version compatibles whit my OS, but the links don`t work.
    Any suggestions?
    More detail about my OS:
    Solaris 9 9/05 HW s9s_u9wos_06b SPARC
    Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
    se is subject to license terms.
    Assembled 25 September 2006

    Hi,
    Please also see [http://unixpackages.com/packages/mozilla this] (from http://www.sunfreeware.com/). It looks like 2.0.0.23 is the last supported version for Solaris 9.

  • Install newest JRE on Solaris 9 Sparc (64-bit)

    Note: This message has also been posted on the JRE forum. This is the second attempt to post it here.
    I would like to know the best method to replace the JRE that is installed with a Solaris 9 (SPARC) installation. A clean installation of Solaris 9 comes with JRE 1.4 and I would prefer 1.4.1 (64-bit) or newer. Sun provides self-extracting archive downloads of the latest JREs for Solaris, but I have been unsuccessful in using these. I followed the instructions at:
    http://java.sun.com/j2se/1.4.2/install-solaris.html
    for doing a self-extracting installation, but this does not replace the contents of /usr/j2se with the new JRE. Additionally a pkginfo still points to the old JRE. I also read the instructions at:
    http://java.sun.com/j2se/1.4.2/install-solaris-64.html
    which stated I should install the 32-bit version, and then the 64-bit version. Finally, both set of instructions mention installation from packages, yet I am unable to find the packages to download. What is the best method to remove the JRE from a Solaris installation and install a newer version of the JRE so the pkginfo is updated and the new JRE resides in /usr/j2se? Any assistance is appreciated.

    I found by issue "mount -v" that our disk slices are
    UFS type. So we don't need apply patch 5257399,
    right? Please confirm. Thanks!!!For your information, you are asking the user community to confirm, not Oracle. Some (many?) of us are not employed by Oracle.
    Therefore, the only answers you can get are from 'friends'. Nothing would be official and Oracle (and Oracle Support) would not be legally responsible.
    Your safest bet would be to escalate the request wityh Oracle Support.

Maybe you are looking for