Solaris 10 X86

  • Follow


Hello all,
1st Prob. 
I have installed Solaris 10 on a x86 machine. Is there any possibility
to check which Network Interface (Hardware) during installation was
installed (if at all)? The PC has an ON-Board INTEL Pro/100 VE NIC,
which is registered in HCL. After all trials to install, ifconfig -a
prompt only 127.0.0.1.
2nd Prob. 
I've  looked a lot of papers (Manual, HowTo etc.) in Google and
BigAdmin, but i could not get success. For example, I found nothing to
set the Standardgateway.  Does anybody know a good description to
configure network on Solaris 10 for x86?

TIA & greetings
Klaus
0
Reply Klaus 2/23/2005 4:31:55 PM

Klaus Jaeger wrote:
> Hello all,
> 1st Prob. 
> I have installed Solaris 10 on a x86 machine. Is there any possibility
> to check which Network Interface (Hardware) during installation was
> installed (if at all)? The PC has an ON-Board INTEL Pro/100 VE NIC,
> which is registered in HCL. After all trials to install, ifconfig -a
> prompt only 127.0.0.1.
> 2nd Prob. 
> I've  looked a lot of papers (Manual, HowTo etc.) in Google and
> BigAdmin, but i could not get success. For example, I found nothing to
> set the Standardgateway.  Does anybody know a good description to
> configure network on Solaris 10 for x86?
> 
> TIA & greetings
> Klaus
i guess that is an iprb interface.
try # ifconfig iprb0 plumb
     # ifconfig iprb 192.168.0.1 netmask 255.255.255.0 broadcast 
192.168.0.1 up
and man iprb
/J�rgen
0
Reply Jorgen 2/24/2005 12:27:35 AM


Jorgen Moquist wrote:
> Klaus Jaeger wrote:
> 
>> Hello all,
>> 1st Prob. I have installed Solaris 10 on a x86 machine. Is there any 
>> possibility
>> to check which Network Interface (Hardware) during installation was
>> installed (if at all)? The PC has an ON-Board INTEL Pro/100 VE NIC,
>> which is registered in HCL. After all trials to install, ifconfig -a
>> prompt only 127.0.0.1.
>> 2nd Prob. I've  looked a lot of papers (Manual, HowTo etc.) in Google and
>> BigAdmin, but i could not get success. For example, I found nothing to
>> set the Standardgateway.  Does anybody know a good description to
>> configure network on Solaris 10 for x86?
>>
>> TIA & greetings
>> Klaus
> 
> i guess that is an iprb interface.
> try # ifconfig iprb0 plumb
>     # ifconfig iprb 192.168.0.1 netmask 255.255.255.0 broadcast 
> 192.168.0.1 up
> and man iprb
> /J�rgen
sorry my fingers are faster than my brain !
should be
  # ifconfig iprb0 192.168.0.1 netmask 255.255.255.0 broadcast 
192.168.0.255 up
0
Reply Jorgen 2/24/2005 12:29:13 AM

On Wed, 23 Feb 2005 17:31:55 +0100, Klaus Jaeger wrote:

> Hello all,
> 1st Prob. 
> I have installed Solaris 10 on a x86 machine. Is there any possibility
> to check which Network Interface (Hardware) during installation was
> installed (if at all)? The PC has an ON-Board INTEL Pro/100 VE NIC,
> which is registered in HCL. After all trials to install, ifconfig -a
> prompt only 127.0.0.1.

You may need to read that HCL entry again.

http://www.sun.com/bigadmin/hcl/data/sol/components/details/377.html

In particular the part about:

"Driver Info:  	Add iprb "pci8086,103d" to /etc/driver_aliases"

Then execute devfsadm.

> 2nd Prob. 
> I've  looked a lot of papers (Manual, HowTo etc.) in Google and
> BigAdmin, but i could not get success. For example, I found nothing to
> set the Standardgateway.  Does anybody know a good description to
> configure network on Solaris 10 for x86?

After getting the OS to recognize the device execute sys-unconfig.

0
Reply Dave 2/24/2005 1:55:32 AM

Dave Uhring wrote:

> 
> After getting the OS to recognize the device execute sys-unconfig.
> 
why ?
/J�rgen
0
Reply Jorgen 2/24/2005 2:16:58 AM

On Thu, 24 Feb 2005 03:16:58 +0100, Jorgen Moquist wrote:

> Dave Uhring wrote:
> 
>> 
>> After getting the OS to recognize the device execute sys-unconfig.
>> 
> why ?

Because for a newbie it is the easiest way to get networking properly
configured.  The man page for sys-unconfig(1M) does list the files which
need to be configured but does not suggest the contents of those files.

0
Reply Dave 2/24/2005 2:41:30 AM

Dave Uhring <daveuhring@yahoo.com> writes:

>http://www.sun.com/bigadmin/hcl/data/sol/components/details/377.html

>In particular the part about:

>"Driver Info:  	Add iprb "pci8086,103d" to /etc/driver_aliases"

It's there iby default in S10.

Also, the proper way to do this in S10 is:

	update_drv -a -i '"pci8086,103d"' iprb

which does all the rest automagically.

Casper
-- 
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
0
Reply Casper 2/24/2005 12:03:41 PM

On Thu, 24 Feb 2005 12:03:41 +0000, Casper H. S. Dik wrote:

> Dave Uhring <daveuhring@yahoo.com> writes:
> 
>>http://www.sun.com/bigadmin/hcl/data/sol/components/details/377.html
> 
>>In particular the part about:
> 
>>"Driver Info:  	Add iprb "pci8086,103d" to /etc/driver_aliases"
> 
> It's there iby default in S10.

Shouldn't the NIC then have been properly detected during the DCA phase of
the installation?  Presuming, of course, that the OP had not disabled the
device in his BIOS.

0
Reply Dave 2/24/2005 2:18:53 PM

Dave Uhring <daveuhring@yahoo.com> writes:

> On Thu, 24 Feb 2005 12:03:41 +0000, Casper H. S. Dik wrote:
>
>> Dave Uhring <daveuhring@yahoo.com> writes:
>> 
>>>http://www.sun.com/bigadmin/hcl/data/sol/components/details/377.html
>> 
>>>In particular the part about:
>> 
>>>"Driver Info:  	Add iprb "pci8086,103d" to /etc/driver_aliases"
>> 
>> It's there iby default in S10.
>
> Shouldn't the NIC then have been properly detected during the DCA phase of
> the installation?  Presuming, of course, that the OP had not disabled the
> device in his BIOS.

Or the PC vendor is using a newer release of the NIC hardware, that is not
yet recognized by Solaris 10 x86.

The original poster should post the output from the command "prtconf -pv".
0
Reply Juergen 2/24/2005 3:35:17 PM

Hello,

Am Thu, 24 Feb 2005 08:18:53 -0600, schrieb Dave Uhring :

> Shouldn't the NIC then have been properly detected during the DCA phase of
> the installation?  Presuming, of course, that the OP had not disabled the
> device in his BIOS.

No, the NIC is not disabled. Further there was XP installed and
networking makes no trouble.
In the afternoon I tried your and Jorgen Tipps - whitout success.

> execute sys-unconfig

The Solaris Configuration-Tool didn't ask me about network details
(only language, timezone, etc.), not yet and not while installing the
OS first time. 

> Add iprb "pci8086,103d" to /etc/driver_aliases"

This line was already in the file.

>| ifconfig iprb0 192.168.0.1 netmask 255.255.255.0 broadcast 
>| 192.168.0.255 up

Give the prompt: "no such interface"

Tomorrow I will try Caspers Tipp (and perhaps some which will posted
tonight ;-)

Thank you all for helping
greetings Klaus
0
Reply Klaus 2/24/2005 8:26:35 PM

On Thu, 24 Feb 2005 21:26:35 +0100, Klaus Jaeger wrote:

> Am Thu, 24 Feb 2005 08:18:53 -0600, schrieb Dave Uhring :

>> Add iprb "pci8086,103d" to /etc/driver_aliases"
> 
> This line was already in the file.

As Juergen Keil suggested, your device may use a different alias.  Run
'prtconf -pv' and see if a different alias is detected.  If so then add
that alias as Casper Dik recommended.

Note that you also may see the NIC by running the DCA at boot time; hit
the ESC key when prompted.  Then go into the details after the initial
device scan completes.

0
Reply Dave 2/24/2005 9:08:19 PM

Klaus Jaeger wrote:

>Hello,
>
>Am Thu, 24 Feb 2005 08:18:53 -0600, schrieb Dave Uhring :
>
>  
>
>>Shouldn't the NIC then have been properly detected during the DCA phase of
>>the installation?  Presuming, of course, that the OP had not disabled the
>>device in his BIOS.
>>    
>>
>
>No, the NIC is not disabled. Further there was XP installed and
>networking makes no trouble.
>In the afternoon I tried your and Jorgen Tipps - whitout success.
>
>  
>
>>execute sys-unconfig
>>    
>>
>
>The Solaris Configuration-Tool didn't ask me about network details
>(only language, timezone, etc.), not yet and not while installing the
>OS first time. 
>
>  
>
>>Add iprb "pci8086,103d" to /etc/driver_aliases"
>>    
>>
>
>This line was already in the file.
>
>  
>
>>| ifconfig iprb0 192.168.0.1 netmask 255.255.255.0 broadcast 
>>| 192.168.0.255 up
>>    
>>
>
>Give the prompt: "no such interface"
>
>Tomorrow I will try Caspers Tipp (and perhaps some which will posted
>tonight ;-)
>
>Thank you all for helping
>greetings Klaus
>  
>
Is your system actually connected to a network?  Do you have a link 
light?   If not, I'm not sure the installation will configure the network!
0
Reply Richard 2/24/2005 9:57:05 PM

Dave Uhring wrote:
> On Thu, 24 Feb 2005 03:16:58 +0100, Jorgen Moquist wrote:
> 
> 
>>Dave Uhring wrote:
>>
>>
>>>After getting the OS to recognize the device execute sys-unconfig.
>>>
>>
>>why ?
> 
> 
> Because for a newbie it is the easiest way to get networking properly
> configured.  The man page for sys-unconfig(1M) does list the files which
> need to be configured but does not suggest the contents of those files.
> 
fair enough :-)
0
Reply Jorgen 2/25/2005 2:49:35 AM

Hello,

On Thu, 24 Feb 2005 16:35:17 +0100, in comp.unix.solaris you wrote:

> The original poster should post the output from the command "prtconf -pv".

There is a lot output. And I'm not shure, whether it is good to post
here the complete prompt.  Which section or line is important to
network interface?

prtconf -pv | grep iprb [or pci8086,103d ] prompts unfortunately
nothing.

greetings Klaus

0
Reply Klaus 2/25/2005 6:18:21 PM

Klaus Jaeger <123678@gmx.de> writes:

> On Thu, 24 Feb 2005 16:35:17 +0100, in comp.unix.solaris you wrote:
>
>> The original poster should post the output from the command "prtconf -pv".
>
> There is a lot output. And I'm not shure, whether it is good to post
> here the complete prompt.  Which section or line is important to
> network interface?

Are there any nodes with the string "Ethernet" in the model name?

Or nodes with "class-code:  00020000"?

Post the ~20 lines starting with "Node 0x......" until "vendor-id: ....."
0
Reply Juergen 2/25/2005 6:22:41 PM

Hello,
Am Thu, 24 Feb 2005 16:57:05 -0500, schrieb Richard B. Gilbert :

> Is your system actually connected to a network?  Do you have a link 
> light?   If not, I'm not sure the installation will configure the network!

Yes, the link-LED is active.

greetings Klaus
0
Reply Klaus 2/25/2005 6:45:23 PM

Hello,
Am Fri, 25 Feb 2005 19:22:41 +0100, schrieb Juergen Keil :

> Post the ~20 lines starting with "Node 0x......" until "vendor-id: ....."

There are now another few (Hardware) problems more. It seems to me,
that I need a "standby-admin" to solve them. I think it's better to
surrender. 

Thanks to all, who tried to help me.

greetings Klaus

0
Reply Klaus 3/1/2005 8:08:31 PM

16 Replies
253 Views

(page loaded in 0.3 seconds)


Reply: