please help!

I have a sun blade with 2 x nics configured, both on different subnets. The eri0 interface (192.168.0.100) is connected to my router (192.168.0.1), but if i try to ping the router, it times out.

any suggestions are welcome - i noticed the 2 mac addresses are the same, i've set local-mac-address to false & rebooted - but they are still the same. /etc/defaultgateway & defaultrouter both point to 192.168.0.1. Any ideas?

# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 in
 1
        inet 127.0.0.1 netmask ff000000
eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 192.168.0.100 netmask ffffff00 broadcast 192.168.0.255
        ether 0:3:ba:11:95:f6
qfe0: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 3
        inet 10.192.80.13 netmask ff000000 broadcast 10.255.255.255
        ether 0:3:ba:11:95:f6

# netstat -rn

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface
-------------------- -------------------- ----- ----- ---------- ---------
default              192.168.0.1          UG        1         44
10.0.0.0             10.192.80.13         U         1          0 qfe0
192.168.0.0          192.168.0.100        U         1         45 eri0
224.0.0.0            192.168.0.100        U         1          0 eri0
127.0.0.1            127.0.0.1            UH        6         38 lo0
#

if you are on solaris 10 please post the output of "dladm show-dev" and "dladm show-link".

btw. local-mac-address=true is the setting for using the mac on the card for the interfaces!

also please use code tags if you post code sniplets...

this is a local machine, so i've tested the network cable in another (windows) box, and connection is fine. i can't help but think i'm missing something obvious, any troubleshooting tips could also be handy. yep its a solaris 10 box.

bash-3.00# dladm show-dev
eri0            link: unknown   speed: 100   Mbps       duplex: full
qfe0            link: unknown   speed: 100   Mbps       duplex: full
qfe1            link: unknown   speed: 0     Mbps       duplex: unknown
qfe2            link: unknown   speed: 0     Mbps       duplex: unknown
qfe3            link: unknown   speed: 0     Mbps       duplex: unknown

bash-3.00# dladm show-link
eri0            type: legacy    mtu: 1500       device: eri0
qfe0            type: legacy    mtu: 1500       device: qfe0
qfe1            type: legacy    mtu: 1500       device: qfe1
qfe2            type: legacy    mtu: 1500       device: qfe2
qfe3            type: legacy    mtu: 1500       device: qfe3

are there error messages in "/var/adm/messages" if you pull the cable on eri0? something like "link down...".

Hmm - i think you're onto something. I ran a tail -f on messages, pulled out the cable...and nothing. I put it back in...nothing, jiggled it about & presto, i get the 'link up' notification:

bash-3.00# tail -f /var/adm/messages
Mar 23 21:14:23 blade pseudo: [ID 129642 kern.info] pseudo-device: wrsmd13
Mar 23 21:14:23 blade genunix: [ID 936769 kern.info] wrsmd13 is /pseudo/wrsmd@13
Mar 23 21:14:23 blade pseudo: [ID 129642 kern.info] pseudo-device: wrsmd14
Mar 23 21:14:23 blade genunix: [ID 936769 kern.info] wrsmd14 is /pseudo/wrsmd@14
Mar 23 21:14:23 blade pseudo: [ID 129642 kern.info] pseudo-device: wrsmd15
Mar 23 21:14:23 blade genunix: [ID 936769 kern.info] wrsmd15 is /pseudo/wrsmd@15
Mar 23 21:14:23 blade pseudo: [ID 129642 kern.info] pseudo-device: fcp0
Mar 23 21:14:23 blade genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
Mar 23 21:14:23 blade pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Mar 23 21:14:23 blade genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
Mar 23 21:31:27 blade eri: [ID 786680 kern.notice] SUNW,eri0 : 100 Mbps full dup
lex link up

looks promising...

hmm ok i disabled eri0, got qfe1 configured instead - but still cant ping the router. I think i need to sleep on this & look again with a fresh pair of eyes.

many thanks for your help dukenuke - its definitely given me a couple of more avenues to investigate/troubleshoot.