Sun Fire v490 / Solaris 9 booting from CD, Network problems
Hi Folks,
I have built a custom bootable CD ROM based on the Solaris 9 installation disk.
When I boot my Sun Fire v490 from this I have problems with the network.
Part of the boot process calls a script which in turn makes the following call
ifconfig ce0 10.4.20.20 netmask 255.255.0.0 up
However when the script terminates and leaves me at the shell prompt I am unable to ping anything.
The output from ifconfig - a looks like...
lo0 flag=..
inet 127.0.0.1
ce0: flags=1000823<UP BROADCAST,NOTRAILER,MULTICAST,IPv4> mtu 1500 index 2 inet 10.4.20.20 netmask ffff0000 broadcast 10.255.255.255 ether 0:14:4f:0:be:be
The only thing that looks odd to me is that there's no "RUNNING" entry for ce0 that I get if I boot from the same CD on my other machines (Ultra 30s & Ultra 10s)
I'm pretty sure that ce0 is "plumbed", 'cos if I "unplumb" it from the shell prompt then it doesn't even appear in the output from ifconfig.
Does anyone out there have any suggestions as to what's going wrong?
Thanks and regards
Kevin
[1115 byte] By [
Kevin_N] at [2007-11-26 10:39:51]
# 1
helloyour broadcast adress seems to be wrong it should be 10.4.255.255try with ifconfig ce0 10.4.20.20 netmask 255.255.0.0 broadcast 10.4.255.255 upMessage was edited by: jerem81
# 2
Hi,
Thanks for the suggestion
I've tried the following...
ifconfig ce0 10.4.20.20 netmask 255.255.0.0 broadcast 10.4.255.255 up
ifconfig ce0 10.4.20.20 netmask 255.0.0.0 broadcast 10.4.255.255 up
and
ifconfig ce0 10.4.20.20 netmask 255.0.0.0 broadcast up
Including bringing the interface "down" between each trial, but each time the output from ifconfig still reports the broadcast address as 10.255.255.255.
I've tried the same on my other test machines (Ultra 30s with hme NICs)
and they report the same thing (i.e broadcast address 10.255.255.255) but they all seem to work.
The only difference that I can see is that on the Ultra 30s ifconfig shows a "RUNNING" flag
(Which I don't seem to be able to get rid of )
and the V490 doesn't show a RUNNING flag (And I don't seem to be able to turn it on)
Any further suggestions anyone ?
Many thanks
Kevin
# 3
Hello,Could you check what is the content of your /etc/netmasks file ?If influences the ifconfig behaviour.Not clear for me which part of your problem is at boot (by static configuration) or during manual operation then a quick look ...Laurent.
# 4
> Hello,
>
> Could you check what is the content of your
> /etc/netmasks file ?
> If influences the ifconfig behaviour.
> Not clear for me which part of your problem is at
> boot (by static configuration) or during manual
> operation then a quick look ...
>
> Laurent.
Hi,
The /etc/netmasks on my bootable CD (Copied directly from the Solaris installatuion disk that form the basis for my bootable CD) is effectively empty,
it just has some pre-amble / comments but with no actual entries.
My problem is that the v490 that doesn't work
i.e ifconfig -a doesn't show a "RUNNING" flag is a production machine that I only have limited access to.
The test machines (Ultra 30s) that I can access all the time always display the "RUNNING" flag using ifconfig.
Output of ifconfig for production machine is as follows...
ifconfig -a
lo0 flag=..
inet 127.0.0.1
ce0: flags=1000823<UP BROADCAST,NOTRAILER,MULTICAST,IPv4>
mtu 1500 index 2 inet 10.5.20.170 netmask ffff0000 broadcast 10.255.255.255 ether 0:14:4f:0:eb:bc
I've tried playing with the IP Address & Netmasks on my test machines, I've tried using ifconfig to bring the interface "down", I've even tried booting the test machines from my CD with the network cable disconnected.
Nothing seems to get rid of the "RUNNING" flag.
If I can get rid of the "RUNNING" flag on my test machine then I may have some clue to why it's not there on the production box.
At the moment I'm tearing my hair out, which is bad news given the limited supply I have left :-)
Any suggestions - no matter how bizarre - are welcome at this point.
Thanks & Regards
Kevin
# 5
Kevin,
Did you ever manage to get this fixed? I have a new v490 as well and I'm doing a standard installation of S10. However, interface 0 (happens to be ce4) of the embedded NIC won't go to "RUNNING". I have tried any number of configs and the other 5 NICs in the box work just fine, but not this one. Here's my ifconfig:
ce4: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 3
inet 0.0.0.0 netmask ff000000
ether 0:14:4f:4a:c4:fd
ce5: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 0.0.0.0 netmask ff000000
ether 0:14:4f:4a:c4:fc
I realize that ce4 doesn't have an IP address or the associated broadcast or netmask, but as you can see from ce5, that shouldn't matter (and it doesn't). I'm getting ready to log a support case, but thought I would try here first.
Any help would be appreciated. Thanks.
Eric
