• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1238
  • Last Modified:

Sun Fire X2100 can't see one ethernet card

Hi Solaris gurus. We have Sun Fire X2100 server which has two ethernet ports physically present but I can see only one port in ifconfig -a. Kindly can you guyz help.

# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index
 1
        inet 127.0.0.1 netmask ff000000
nge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.92.1.250 netmask ffff8000 broadcast 10.92.127.255
        ether 0:e0:81:5a:42:88
0
dayakadam
Asked:
dayakadam
  • 6
  • 4
1 Solution
 
advegaCommented:
Hi, can you tell me if you have two /etc/hostname.nge# files? or just one (assumed hostname.nge0) ? you need to have both files created in order to see the interface id '1' every time you boot up. or try pluggin' it:

root@box# ifconfig nge1 plumb
(if at this point you don't have any error, continue..)
root@box# ifconfig nge1 inet 1.2.3.4 netmask 255.255.128.0 netmask + up
At this point it should be working if a utp cable was already plugged to the network port.
BUT this will be lost if you reboot, avoid it to happen creating the /etc/hostname.nge1 file
for this:
root@box# cd /etc
root@box# cp -p hostname.nge0 hostname.nge1
root@box# vi hostname.nge1   <--- Here you will edit the IP or hostname for this network port
root@box# edit hosts       <---- Here you have to add another entry for the new IP hostname pair.
hope this helps...
0
 
dayakadamAuthor Commented:
I tried plumb and creating those files but it didn't work. Same problem persists. I can't see device file for second ethernet in /dev.
0
 
advegaCommented:
Ok, if you can have a time offline, go down OBP :
ok> setenv auto-boot? false
ok> reset-all
( wait until it's again at the 'ok' prompt)
ok> watch-net-all
and see how many instances of ethernet ports it reports! if it does NOT report both as expected then the hardware is NOT ok,  use the warranty service from sun so they replace the mother board of your server. (if your hardware is still covered by )...
If no problems occurr at the OBP then something at OS leves is happening, try a reconfig boot:
ok> boot -r

and try to do it from serial console and with a tip connection or an hyperterminal so you can collect all the messages about harware POST results and so on ...
now, one question to you..

when you do the "plumb" stuff did you get an error message? checking again with ifconfig -a to see if something changed?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
dayakadamAuthor Commented:
This is intel based system it doesn't have OK prompt. I got following error after plumb.
bash-3.00# ifconfig bge0 plumb
ifconfig: plumb: bge0: no such interface
0
 
advegaCommented:
Hi, yes it is AMD based server rigth, my mistake, but hey! why are you doing a bge0 plumbing? it should be nge driver but second instance (nge1) rigth?

or did I miss something?

regards...
0
 
advegaCommented:
all rite, I checked at sunsolve and it is bge the driver used in this server, now lets see, if you plug a cable into the port does  it lit?
have you looked for the latest bios for that server ?
http://www.sun.com/servers/entry/x2100/downloads.jsp
what version and release of Solaris are you running?
or at least a showrev -p | grep 116666     (116666 is the patch for bge on Solaris x86) the latest is 116666-05...
0
 
dayakadamAuthor Commented:
Hey Advega.. The current version is 5.10. Also I did showrev -p|grep 116666 it doesn't return anything.
bash-3.00# uname -X
System = SunOS
Node = newhost
Release = 5.10
KernelID = Generic
Machine = i86pc
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 1


bash-3.00# showrev -p|grep 116666
bash-3.00#

0
 
advegaCommented:
all rite! then it's Sol 10, ok, then lets see what level of bge driver do you have...
please, issue:
# showrev -p | grep 122028
# file /etc/hostname.bge*
# grep bge /etc/path_to_inst

0
 
dayakadamAuthor Commented:
This is the output of all commands
bash-3.00# showrev -p|grep 122028
bash-3.00#  file /etc/hostname.bge*
/etc/hostname.bge*:     cannot open: No such file or directory
bash-3.00# grep bge /etc/path_to_inst
bash-3.00#
0
 
advegaCommented:
the last line (grep is to see how many instances of the bge driver are loaded on Solaris at boot time it should read something like
root@ftpserver etc #> grep hme path_to_inst
"/sbus@3,0/SUNW,hme@3,8c00000" 0 "hme"
"/sbus@7,0/SUNW,hme@3,8c00000" 1 "hme"

In this example, notice of the different phisical paths to each hme instance 0 and 1.

If the BIOS is reporting all the hardware to the OS, then you should see something like that in your /etc/path_to_inst file, of course that with bge driver instead of hme.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now