COMPGROUPS.NET | Search | Post Question | Groups | Stream | About | Register

Sun Fire V440 Network Boot

  • Follow


Dear All,

Arch: Sun Fire V440
OE : Sun Solaris 8
Problem: Trying to boot from Network without success.  The  Install/
Boot server  are on the same subnet.


While booting from network, I always get the below given response:

{3} ok boot net1 - install
Boot device: /pci@1f,700000/network@1  File and args: - install
/pci@1f,700000/network@1: link down
/pci@1f,700000/network@1: link down
/pci@1f,700000/network@1: link down
/pci@1f,700000/network@1: link down

Can't open boot device




What I've is like below:

{3} ok show-nets
a) /pci@1f,700000/network@1
b) /pci@1c,600000/network@2
q) NO SELECTION
Enter Selection, q to quit: q
{3} ok
{3} ok watch-net /pci@1f,700000/network@1
/pci@1c,600000/network@2: link down
/pci@1f,700000/network@1 ?
{3} ok
{3} ok apply watch-net /pci@1f,700000/network@1
/pci@1f,700000/network@1: link down
{3} ok
{3} ok devalias
bootdisk                 /pci@1f,700000/scsi@2/disk@0,0
net                      /pci@1c,600000/network@2
net1                     /pci@1f,700000/network@1
net0                     /pci@1c,600000/network@2
cdrom                    /pci@1e,600000/ide@d/cdrom@0,0:f
ide                      /pci@1e,600000/ide@d
disk3                    /pci@1f,700000/scsi@2/disk@3,0
disk2                    /pci@1f,700000/scsi@2/disk@2,0
disk1                    /pci@1f,700000/scsi@2/disk@1,0
disk0                    /pci@1f,700000/scsi@2/disk@0,0
disk                     /pci@1f,700000/scsi@2/disk@0,0
scsi                     /pci@1f,700000/scsi@2
i2c                      /pci@1e,600000/isa@7/i2c@0,320
sc-control               /pci@1e,600000/isa@7/rmc-comm@0,3e8
ttyb                     /pci@1e,600000/isa@7/serial@0,2e8
ttya                     /pci@1e,600000/isa@7/serial@0,3f8
pci1f                    /pci@1f,700000
pci1e                    /pci@1e,600000
pci1d                    /pci@1d,700000
pci1c                    /pci@1c,600000
isa                      /pci@1e,600000/isa@7
name                     aliases


During this session, the network port behind the system gets down
( LEDs turned OFF ) and port on switch gets re-initialized ( it first
gets down, then gets amber and after I get the second OK prompt above,
the switch ports' LED gets green ). This Network Interface works
perfectly with already Solaris OS Installed.

Hence I cannot boot from the network. although the boot-server is
allowing clients to boot from network but this particular Sun Fire-
V440 is not booting up

Any Help will be highly appreciated...


Regards,
Moody.
0
Reply Moody 3/3/2008 2:21:26 PM 

Moody <nasir.mahmood@gmail.com> wrote:
> Dear All,
> 
> Arch: Sun Fire V440
> OE : Sun Solaris 8
> Problem: Trying to boot from Network without success.  The  Install/
> Boot server  are on the same subnet.
> 
> 
> While booting from network, I always get the below given response:
> 
> {3} ok boot net1 - install
> Boot device: /pci@1f,700000/network@1  File and args: - install
> /pci@1f,700000/network@1: link down
> /pci@1f,700000/network@1: link down
> /pci@1f,700000/network@1: link down
> /pci@1f,700000/network@1: link down
> 
> Can't open boot device
> 
> 
> 
> 
> What I've is like below:
> 
> {3} ok show-nets
> a) /pci@1f,700000/network@1
> b) /pci@1c,600000/network@2
> q) NO SELECTION
> Enter Selection, q to quit: q
> {3} ok
> {3} ok watch-net /pci@1f,700000/network@1
> /pci@1c,600000/network@2: link down
> /pci@1f,700000/network@1 ?
> {3} ok
> {3} ok apply watch-net /pci@1f,700000/network@1
> /pci@1f,700000/network@1: link down
> {3} ok
> {3} ok devalias
> bootdisk                 /pci@1f,700000/scsi@2/disk@0,0
> net                      /pci@1c,600000/network@2
> net1                     /pci@1f,700000/network@1
> net0                     /pci@1c,600000/network@2
> cdrom                    /pci@1e,600000/ide@d/cdrom@0,0:f
> ide                      /pci@1e,600000/ide@d
> disk3                    /pci@1f,700000/scsi@2/disk@3,0
> disk2                    /pci@1f,700000/scsi@2/disk@2,0
> disk1                    /pci@1f,700000/scsi@2/disk@1,0
> disk0                    /pci@1f,700000/scsi@2/disk@0,0
> disk                     /pci@1f,700000/scsi@2/disk@0,0
> scsi                     /pci@1f,700000/scsi@2
> i2c                      /pci@1e,600000/isa@7/i2c@0,320
> sc-control               /pci@1e,600000/isa@7/rmc-comm@0,3e8
> ttyb                     /pci@1e,600000/isa@7/serial@0,2e8
> ttya                     /pci@1e,600000/isa@7/serial@0,3f8
> pci1f                    /pci@1f,700000
> pci1e                    /pci@1e,600000
> pci1d                    /pci@1d,700000
> pci1c                    /pci@1c,600000
> isa                      /pci@1e,600000/isa@7
> name                     aliases
> 
> 
> During this session, the network port behind the system gets down
> ( LEDs turned OFF ) and port on switch gets re-initialized ( it first
> gets down, then gets amber and after I get the second OK prompt above,
> the switch ports' LED gets green ). This Network Interface works
> perfectly with already Solaris OS Installed.
> 
> Hence I cannot boot from the network. although the boot-server is
> allowing clients to boot from network but this particular Sun Fire-
> V440 is not booting up
> 
> Any Help will be highly appreciated...
> 
> 
> Regards,
> Moody.

are you having duplex/speed errors that don't allow a link?

you can force them like this

boot net:speed=100,duplex=full -v blah blah blah

and so forth.
0
Reply Cydrome 3/3/2008 7:18:54 PM 


On Mar 4, 12:18 am, Cydrome Leader <prese...@MUNGEpanix.com> wrote:
> Moody <nasir.mahm...@gmail.com> wrote:
> > Dear All,
>
> > Arch: Sun Fire V440
> > OE : Sun Solaris 8
> > Problem: Trying to boot from Network without success.  The  Install/
> > Boot server  are on the same subnet.
>
> > While booting from network, I always get the below given response:
>
> > {3} ok boot net1 - install
> > Boot device: /pci@1f,700000/network@1  File and args: - install
> > /pci@1f,700000/network@1: link down
> > /pci@1f,700000/network@1: link down
> > /pci@1f,700000/network@1: link down
> > /pci@1f,700000/network@1: link down
>
> > Can't open boot device
>
> > What I've is like below:
>
> > {3} ok show-nets
> > a) /pci@1f,700000/network@1
> > b) /pci@1c,600000/network@2
> > q) NO SELECTION
> > Enter Selection, q to quit: q
> > {3} ok
> > {3} ok watch-net /pci@1f,700000/network@1
> > /pci@1c,600000/network@2: link down
> > /pci@1f,700000/network@1 ?
> > {3} ok
> > {3} ok apply watch-net /pci@1f,700000/network@1
> > /pci@1f,700000/network@1: link down
> > {3} ok
> > {3} ok devalias
> > bootdisk                 /pci@1f,700000/scsi@2/disk@0,0
> > net                      /pci@1c,600000/network@2
> > net1                     /pci@1f,700000/network@1
> > net0                     /pci@1c,600000/network@2
> > cdrom                    /pci@1e,600000/ide@d/cdrom@0,0:f
> > ide                      /pci@1e,600000/ide@d
> > disk3                    /pci@1f,700000/scsi@2/disk@3,0
> > disk2                    /pci@1f,700000/scsi@2/disk@2,0
> > disk1                    /pci@1f,700000/scsi@2/disk@1,0
> > disk0                    /pci@1f,700000/scsi@2/disk@0,0
> > disk                     /pci@1f,700000/scsi@2/disk@0,0
> > scsi                     /pci@1f,700000/scsi@2
> > i2c                      /pci@1e,600000/isa@7/i2c@0,320
> > sc-control               /pci@1e,600000/isa@7/rmc-comm@0,3e8
> > ttyb                     /pci@1e,600000/isa@7/serial@0,2e8
> > ttya                     /pci@1e,600000/isa@7/serial@0,3f8
> > pci1f                    /pci@1f,700000
> > pci1e                    /pci@1e,600000
> > pci1d                    /pci@1d,700000
> > pci1c                    /pci@1c,600000
> > isa                      /pci@1e,600000/isa@7
> > name                     aliases
>
> > During this session, the network port behind the system gets down
> > ( LEDs turned OFF ) and port on switch gets re-initialized ( it first
> > gets down, then gets amber and after I get the second OK prompt above,
> > the switch ports' LED gets green ). This Network Interface works
> > perfectly with already Solaris OS Installed.
>
> > Hence I cannot boot from the network. although the boot-server is
> > allowing clients to boot from network but this particular Sun Fire-
> > V440 is not booting up
>
> > Any Help will be highly appreciated...
>
> > Regards,
> > Moody.
>
> are you having duplex/speed errors that don't allow a link?
>
> you can force them like this
>
> boot net:speed=100,duplex=full -v blah blah blah
>



{3} ok boot net1:speed=100,duplex=full - install
Boot device: /pci@1f,700000/network@1:speed=100,duplex=full  File and
args: - install
/pci@1f,700000/network@1: Cannot establish link via non-Auto-
Negotation
/pci@1f,700000/network@1: link down
/pci@1f,700000/network@1: Cannot establish link via non-Auto-
Negotation
/pci@1f,700000/network@1: link down

Can't open boot device

This is all I got... Any help further


Regards,
Moody.
> and so forth.
0
Reply Moody 3/4/2008 9:21:43 AM 

Moody schrieb:
> On Mar 4, 12:18 am, Cydrome Leader <prese...@MUNGEpanix.com> wrote:
>> Moody <nasir.mahm...@gmail.com> wrote:
>>> Dear All,
>>> Arch: Sun Fire V440
>>> OE : Sun Solaris 8
>>> Problem: Trying to boot from Network without success.  The  Install/
>>> Boot server  are on the same subnet.
>>> While booting from network, I always get the below given response:
>>> {3} ok boot net1 - install
>>> Boot device: /pci@1f,700000/network@1  File and args: - install
>>> /pci@1f,700000/network@1: link down
>>> /pci@1f,700000/network@1: link down
>>> /pci@1f,700000/network@1: link down
>>> /pci@1f,700000/network@1: link down
>>> Can't open boot device
>>> What I've is like below:
>>> {3} ok show-nets
>>> a) /pci@1f,700000/network@1
>>> b) /pci@1c,600000/network@2
>>> q) NO SELECTION
>>> Enter Selection, q to quit: q
>>> {3} ok
>>> {3} ok watch-net /pci@1f,700000/network@1
>>> /pci@1c,600000/network@2: link down
>>> /pci@1f,700000/network@1 ?
>>> {3} ok
>>> {3} ok apply watch-net /pci@1f,700000/network@1
>>> /pci@1f,700000/network@1: link down
>>> {3} ok
>>> {3} ok devalias
>>> bootdisk                 /pci@1f,700000/scsi@2/disk@0,0
>>> net                      /pci@1c,600000/network@2
>>> net1                     /pci@1f,700000/network@1
>>> net0                     /pci@1c,600000/network@2
>>> cdrom                    /pci@1e,600000/ide@d/cdrom@0,0:f
>>> ide                      /pci@1e,600000/ide@d
>>> disk3                    /pci@1f,700000/scsi@2/disk@3,0
>>> disk2                    /pci@1f,700000/scsi@2/disk@2,0
>>> disk1                    /pci@1f,700000/scsi@2/disk@1,0
>>> disk0                    /pci@1f,700000/scsi@2/disk@0,0
>>> disk                     /pci@1f,700000/scsi@2/disk@0,0
>>> scsi                     /pci@1f,700000/scsi@2
>>> i2c                      /pci@1e,600000/isa@7/i2c@0,320
>>> sc-control               /pci@1e,600000/isa@7/rmc-comm@0,3e8
>>> ttyb                     /pci@1e,600000/isa@7/serial@0,2e8
>>> ttya                     /pci@1e,600000/isa@7/serial@0,3f8
>>> pci1f                    /pci@1f,700000
>>> pci1e                    /pci@1e,600000
>>> pci1d                    /pci@1d,700000
>>> pci1c                    /pci@1c,600000
>>> isa                      /pci@1e,600000/isa@7
>>> name                     aliases
>>> During this session, the network port behind the system gets down
>>> ( LEDs turned OFF ) and port on switch gets re-initialized ( it first
>>> gets down, then gets amber and after I get the second OK prompt above,
>>> the switch ports' LED gets green ). This Network Interface works
>>> perfectly with already Solaris OS Installed.
>>> Hence I cannot boot from the network. although the boot-server is
>>> allowing clients to boot from network but this particular Sun Fire-
>>> V440 is not booting up
>>> Any Help will be highly appreciated...
>>> Regards,
>>> Moody.
>> are you having duplex/speed errors that don't allow a link?
>>
>> you can force them like this
>>
>> boot net:speed=100,duplex=full -v blah blah blah
>>
> 
> 
> 
> {3} ok boot net1:speed=100,duplex=full - install
> Boot device: /pci@1f,700000/network@1:speed=100,duplex=full  File and
> args: - install
> /pci@1f,700000/network@1: Cannot establish link via non-Auto-
> Negotation
> /pci@1f,700000/network@1: link down
> /pci@1f,700000/network@1: Cannot establish link via non-Auto-
> Negotation
> /pci@1f,700000/network@1: link down
> 
> Can't open boot device
> 
> This is all I got... Any help further
> 
> 
> Regards,
> Moody.
>> and so forth.
> 

is your network switch set to auto-negotiation? AFAIK it is best to set 
both ends to auto-negotiation, and only if this fails force a certain 
setting, but then consistently on both ends.

- Thomas
0
Reply Thomas 3/4/2008 9:27:07 AM 

On Mar 4, 2:27 pm, Thomas Maier-Komor <tho...@maier-komor.de> wrote:
> Moody schrieb:
>
>
>
> > On Mar 4, 12:18 am, Cydrome Leader <prese...@MUNGEpanix.com> wrote:
> >> Moody <nasir.mahm...@gmail.com> wrote:
> >>> Dear All,
> >>> Arch: Sun Fire V440
> >>> OE : Sun Solaris 8
> >>> Problem: Trying to boot from Network without success.  The  Install/
> >>> Boot server  are on the same subnet.
> >>> While booting from network, I always get the below given response:
> >>> {3} ok boot net1 - install
> >>> Boot device: /pci@1f,700000/network@1  File and args: - install
> >>> /pci@1f,700000/network@1: link down
> >>> /pci@1f,700000/network@1: link down
> >>> /pci@1f,700000/network@1: link down
> >>> /pci@1f,700000/network@1: link down
> >>> Can't open boot device
> >>> What I've is like below:
> >>> {3} ok show-nets
> >>> a) /pci@1f,700000/network@1
> >>> b) /pci@1c,600000/network@2
> >>> q) NO SELECTION
> >>> Enter Selection, q to quit: q
> >>> {3} ok
> >>> {3} ok watch-net /pci@1f,700000/network@1
> >>> /pci@1c,600000/network@2: link down
> >>> /pci@1f,700000/network@1 ?
> >>> {3} ok
> >>> {3} ok apply watch-net /pci@1f,700000/network@1
> >>> /pci@1f,700000/network@1: link down
> >>> {3} ok
> >>> {3} ok devalias
> >>> bootdisk                 /pci@1f,700000/scsi@2/disk@0,0
> >>> net                      /pci@1c,600000/network@2
> >>> net1                     /pci@1f,700000/network@1
> >>> net0                     /pci@1c,600000/network@2
> >>> cdrom                    /pci@1e,600000/ide@d/cdrom@0,0:f
> >>> ide                      /pci@1e,600000/ide@d
> >>> disk3                    /pci@1f,700000/scsi@2/disk@3,0
> >>> disk2                    /pci@1f,700000/scsi@2/disk@2,0
> >>> disk1                    /pci@1f,700000/scsi@2/disk@1,0
> >>> disk0                    /pci@1f,700000/scsi@2/disk@0,0
> >>> disk                     /pci@1f,700000/scsi@2/disk@0,0
> >>> scsi                     /pci@1f,700000/scsi@2
> >>> i2c                      /pci@1e,600000/isa@7/i2c@0,320
> >>> sc-control               /pci@1e,600000/isa@7/rmc-comm@0,3e8
> >>> ttyb                     /pci@1e,600000/isa@7/serial@0,2e8
> >>> ttya                     /pci@1e,600000/isa@7/serial@0,3f8
> >>> pci1f                    /pci@1f,700000
> >>> pci1e                    /pci@1e,600000
> >>> pci1d                    /pci@1d,700000
> >>> pci1c                    /pci@1c,600000
> >>> isa                      /pci@1e,600000/isa@7
> >>> name                     aliases
> >>> During this session, the network port behind the system gets down
> >>> ( LEDs turned OFF ) and port on switch gets re-initialized ( it first
> >>> gets down, then gets amber and after I get the second OK prompt above,
> >>> the switch ports' LED gets green ). This Network Interface works
> >>> perfectly with already Solaris OS Installed.
> >>> Hence I cannot boot from the network. although the boot-server is
> >>> allowing clients to boot from network but this particular Sun Fire-
> >>> V440 is not booting up
> >>> Any Help will be highly appreciated...
> >>> Regards,
> >>> Moody.
> >> are you having duplex/speed errors that don't allow a link?
>
> >> you can force them like this
>
> >> boot net:speed=100,duplex=full -v blah blah blah
>
> > {3} ok boot net1:speed=100,duplex=full - install
> > Boot device: /pci@1f,700000/network@1:speed=100,duplex=full  File and
> > args: - install
> > /pci@1f,700000/network@1: Cannot establish link via non-Auto-
> > Negotation
> > /pci@1f,700000/network@1: link down
> > /pci@1f,700000/network@1: Cannot establish link via non-Auto-
> > Negotation
> > /pci@1f,700000/network@1: link down
>
> > Can't open boot device
>
> > This is all I got... Any help further
>
> > Regards,
> > Moody.
> >> and so forth.
>
> is your network switch set to auto-negotiation? AFAIK it is best to set
> both ends to auto-negotiation, and only if this fails force a certain
> setting, but then consistently on both ends.
>


Switch is Cisco-3550 and doesn't have a 'negotiation' command  in
enable mode.... Secondly I tried  to boot using  a cross cable with
the server, but I don't see any progress.... like below:


{3} ok  boot  net1:speed=100,duplex=full - install
Probing system devices
Probing memory
Probing I/O buses
screen not found.
keyboard not found.
Keyboard not present.  Using ttya for input and output.

Sun Fire V440, No Keyboard
Copyright 1998-2004 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.16.4, 16384 MB memory installed, Serial #64856575.
Ethernet address 0:3:ba:dd:a1:ff, Host ID: 83dda1ff.

Rebooting with command: boot  net1:speed=100,duplex=full - install
Boot device: /pci@1f,700000/network@1:speed=100,duplex=full  File and
args: - install
/pci@1f,700000/network@1: 100 Mbps full duplex 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 /pci@1f,700000/network@1: link down
/pci@1f,700000/network@1: link down
/pci@1f,700000/network@1: link down
/pci@1f,700000/network@1: link down
panic - boot: Cannot prom_open network device /pci@1f,700000/
network@1.
Program terminated
{3} ok


Secondly I don't see any activity on the network install server when I
run the 'rpc.bootparamd' with a debugging enabled..

Thanks for your help.........

Regards,
Moody.

> - Thomas
0
Reply Moody 3/5/2008 7:11:54 AM 

On 2008-03-05, Moody <nasir.mahmood@gmail.com> wrote:
> Rebooting with command: boot  net1:speed=100,duplex=full - install
> Boot device: /pci@1f,700000/network@1:speed=100,duplex=full  File and
> args: - install
> /pci@1f,700000/network@1: 100 Mbps full duplex link up
> Timeout waiting for ARP/RARP packet

You'll need an RARP daemon up and running in your local network
and the Ethernet address of this box must be entered into the
�ethers� database.  Try �svcadm enable rarp� under Solaris 10.

Andreas.
0
Reply comp 3/6/2008 11:53:50 PM 

On Mar 7, 4:53 am, comp.unix.sola...@expires-
on-2008-03-15.usenet.andreas-borchert.de (Andreas F. Borchert) wrote:
> On 2008-03-05, Moody <nasir.mahm...@gmail.com> wrote:
>
> > Rebooting with command: boot  net1:speed=3D100,duplex=3Dfull - install
> > Boot device: /pci@1f,700000/network@1:speed=3D100,duplex=3Dfull  File an=
d
> > args: - install
> > /pci@1f,700000/network@1: 100 Mbps full duplex link up
> > Timeout waiting for ARP/RARP packet
>
> You'll need an RARP daemon up and running in your local network
> and the Ethernet address of this box must be entered into the
> =BBethers=AB database.  Try =BBsvcadm enable rarp=AB under Solaris 10.
>
> Andreas.

I'm using Solaris 8 for both install-server and client to be
installed....


Regards,
Nasir
0
Reply Moody 3/7/2008 11:44:15 AM 

On 2008-03-07, Moody <nasir.mahmood@gmail.com> wrote:
> I'm using Solaris 8 for both install-server and client to be
> installed....

in.rarpd and rpc.bootparamd are started during booting by Solaris 8
when the /tftpboot directory exists. Just add the ethernet address
of the to be installed machine to /etc/ethers and its IP address in
/etc/hosts. Then take the first of the two Solaris 8 installation CDs
and look for the Solaris_8/Tools subdirectory where you will find the
scripts setup_install_server and add_install_client. The first script
copies the contents of the installation CD to your disk and the second
script prepares the installation of your other machine.  (You will also
need to invoke setup_install_server on the second CD if you haven't done
it yet.)  add_install_client creates /tftpboot if this does not exist
yet and also starts in.rarpd and rpc.bootparamd, if necessary.

Andreas.
0
Reply comp 3/9/2008 12:14:05 AM
comp.unix.solaris 25707 articles. 78 followers.

7 Replies
418 Views

(page loaded in 0.111 seconds)

Similiar Articles:

Sun Fire V440 Network Boot - comp.unix.solaris
Dear All, Arch: Sun Fire V440 OE : Sun Solaris 8 Problem: Trying to boot from Network without success. The Install/ Boot server are on the same su...

Sun Fire v250 boot from dvd - comp.sys.sun.admin
Sun Fire V440 Network Boot - comp.unix.solaris Sun Fire 280R doesn't boot from S10 DVD - comp.unix.solaris ... ... V215, V240, V245, V250, V440 ... vs. ce0 vs. connectors ...

(newbie) SCSI Problem with SUN Fire V440 - comp.unix.solaris ...
... let me know if there is any problem ... There is a bug in early Sun Fire V440 ... Sun Fire V240 SCSI Errors explained - comp.unix.solaris V440 Network Boot Moody 7 113 ...

Booting Netra X1 from external USB CD-ROM device - comp.unix ...
I've never done solaris install over network/jumpstart so I don't ... How to bootable installation CD for Sun Fire - comp.unix.solaris ... Booting Netra X1 from external ...

error: timeout waiting for ARP/RARP packet - comp.unix.solaris ...
Sun Fire V440 Network Boot - comp.unix.solaris error: timeout waiting for ARP/RARP packet - comp.unix.solaris ... Sun Fire V440 Network Boot - comp.unix.solaris > are you ...

V440 server reboot for no reason - comp.unix.solaris
(newbie) SCSI Problem with SUN Fire V440 ... in... ... on sunfire 280r; Sun Sunfire V880 won't boot up -… ... A42-XCB2-04HDSun Fire V440 ... How to change network interface ...

password recovery sun v440 - comp.unix.solaris
Sun Fire V440 Network Boot - comp.unix.solaris password recovery sun v440 - comp.unix.solaris Solaris 10 network access from 'boot cdrom -s'? - comp.sys ... Sun Fire V440 ...

uname command - comp.unix.solaris
... the > > platform type in the o/p is >>> SUNW,Sun-Fire-V440 ... actually my N440 server is operating for a GSM network :) ... How to boot from the detached mirror disk of zfs ...

Use of ce0 interface on V440 - comp.unix.solaris
Sun Fire V440 Network Boot - comp.unix.solaris V215, V240, V245, V250, V440 ... vs. ce0 vs. connectors) Sun Fire V240 can't see ... Sun Fire V440 Server Product Notes Use ...

vxvm:vxconfigd: enable failed: Error in disk group configuration ...
... ok boot SC Alert: Host System has Reset screen not found. keyboard not found. Keyboard not present. Using ttya for input and output. Sun Fire V440, No ... network ...

Sun Fire V440 Network Boot - Database Support @ dbaspot.com ...
Dear All, Arch: Sun Fire V440 OE : Sun Solaris 8 Problem: Trying to boot from Network without success. The Install/ Boot server are on the same subnet. While booting ...

Sun Fire V440 Network Boot - comp.unix.solaris | Computer Group
Dear All, Arch: Sun Fire V440 OE : Sun Solaris 8 Problem: Trying to boot from Network without success. The Install/ Boot server are on the same su...

7/24/2012 12:53:35 PM


Reply:



Privacy Policy | All Times Are GMT(UTC) | powered by