Prev: fsck error: "BAD STATE 0x52 TO BLKERR"
Next: fsck -n
From: social on 4 Aug 2006 13:30
Is there a way to disable a NIC from OK/ALOM on a t2000. I looked
at disablecomponent, but that disbales a whole slot? OK prompt did not
recognize asr-disable*

Thanks
Ashok

From: James Carlson on 5 Aug 2006 20:30
"social" <mail4ashok(a)gmail.com> writes:
> Is there a way to disable a NIC from OK/ALOM on a t2000. I looked
> at disablecomponent, but that disbales a whole slot? OK prompt did not
> recognize asr-disable*

Why? What are you trying to do?

--
James Carlson, KISS Network <james.d.carlson(a)sun.com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
From: social on 6 Aug 2006 07:34

James Carlson wrote:
> Why? What are you trying to do?
>

During a jumpstart using flasharchives, the phase that takes the most
amount of time is the miniboot trying to get IP's for 8 NIC's using
RARP.
Modifying the miniboot just for this specific server configuration, I
thought is ugly.
I only wanted the one NIC to be seen by the kernel

From: social on 6 Aug 2006 09:31
social wrote:

> During a jumpstart using flasharchives, the phase that takes the most
> amount of time is the miniboot trying to get IP's for 8 NIC's using
> RARP.
> Modifying the miniboot just for this specific server configuration, I
> thought is ugly.
> I only wanted the one NIC to be seen by the kernel

miniboot? I meant boot directory conatining mini-root

From: James Carlson on 7 Aug 2006 08:03
"social" <mail4ashok(a)gmail.com> writes:
> James Carlson wrote:
> > Why? What are you trying to do?
> >
>
> During a jumpstart using flasharchives, the phase that takes the most
> amount of time is the miniboot trying to get IP's for 8 NIC's using
> RARP.
> Modifying the miniboot just for this specific server configuration, I
> thought is ugly.
> I only wanted the one NIC to be seen by the kernel

Ah, ok. Yes, this is a known defect in the install code.
Unfortunately, other than removing hardware, I don't think there are
any known work-arounds.

--
James Carlson, KISS Network <james.d.carlson(a)sun.com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
 |  Next  |  Last
Pages: 1 2
Prev: fsck error: "BAD STATE 0x52 TO BLKERR"
Next: fsck -n