bge has worked in Solaris for eons, so I can't offer any advice, sorry.  But 
what I still don't understand is why upgrading the image caused my nic to stop 
working and a complete reinstall to make it working again.



On Wednesday, September 24, 2014 2:19 AM, "[email protected]" 
<[email protected]> wrote:
 


Luck you! I tried the no install option, imported and destroyed the zones, 
still no luck. Am now digging into dtrace, truss, snoop and all … coming from 
Linux.
 
From:G B [mailto:[email protected]] 
Sent: Tuesday, September 23, 2014 11:29 PM
To: [email protected]; 'Keith Wesolowski'; 
[email protected]
Subject: Re: [smartos-discuss] Network Problem
 
Packets are not incoming or outgoing on the rge interface.  
 
After booting the console receives:
2014-09-23T21:01:12+00:00 02-6d-6a-81-ae-21 mDNSResponder: [ID 702911 daemon.err
or] mDNSPlatformSendUDP go error 128 (Network is unreachable) sending packet to 
  224.0.0.251 on interface 192.168.1.15/rge0/2
 
# prtconf -dD |grep rge
     pci1025,61f (pciex10ec,8136) [Realtek Semiconductor Co., Ltd. RTL810
1E/RTL8102E PCI Express Fast Ethernet controller], instance #0 (driver name: rge
)
 
Well, I reinstalled after booting to "noinstall" then ran "zpool import zones" 
and "zpool destroy zones" and went through the setup and the rge interface now 
works.  Not sure what would have caused that from a working June image to 
rebooting with the September images and the NIC wouldn't work, but it does 
after a new installation.
 
Anyway, I had saved all files that I needed from any Zones that were there, so 
nothing lost.  
 
As a longtime AIX and Solaris admin, I must say that SmartOS is great and I let 
everyone know about it.  Since I've had many years with Solaris, when I was 
moving my domains from OpenBSD, my choices were FreeBSD, OpenIndiana, OmniOS or 
SmartOS.  Because of my comfort with Solaris it was going to be one of the 
latter 3, and OI doesn't get updates often, and I preferred the way SmartOS is 
done as a hypervisor over OmniOS.  Will be adding at least two more websites 
soon, too.
 
Just want to say thanks again for SmartOS and the support.
 
On Tuesday, September 23, 2014 12:18 PM, "[email protected]" 
<[email protected]> wrote:
 
Thanks Keith we will do as advised, much appreciated.

-----Original Message-----
From: 'Keith Wesolowski' via smartos-discuss 
[mailto:[email protected]] 
Sent: Tuesday, September 23, 2014 5:20 PM
To: [email protected]
Cc: [email protected]
Subject: Re: [smartos-discuss] Network Problem

On Tue, Sep 23, 2014 at 11:05:11AM +0200, [email protected] wrote:

> 1. I have connected my laptop and the server directed into a switch on my 
> table. I got another laptop and plug it into the same switch and can ping 
> across the laptops. But still can ping the smartos server, from either 
> laptops.
> 
> Got a cross cable and connected the laptops and can ping across. Connected 
> the cross cable to the server, cant ping!
> 
> Am connected also with a console cable to the server.
> 
> # ifconfig -a
> lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 
> index 1
>        inet 127.0.0.1 netmask ff000000
> bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
>        inet 172.16.30.65 netmask ffffff00 broadcast 172.16.30.255
>        ether b4:b5:2f:a0:c1:36
> lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 
> 8252 index 1
> 
> am no expert with Dtrace, but someone suggested this snoop command, and here 
> is what am getting:
> 
> C:\mylaptop>ping 172.16.30.65 -t
> 
> Pinging 172.16.30.65 with 32 bytes of data:
> Reply from 172.16.30.18: Destination host unreachable.
> Reply from 172.16.30.18: Destination host unreachable.
> Reply from 172.16.30.18: Destination host unreachable.
> Reply from 172.16.30.18: Destination host unreachable.
> Reply from 172.16.30.18: Destination host unreachable.
> Reply from 172.16.30.18: Destination host unreachable.
> Reply from 172.16.30.18: Destination host unreachable.

I don't recommend using Windows to debug, unless you are a Microsoft OS 
engineer.  The functionality it provides is limited and what there is, is hard 
to use.

The host unreachable error could indicate a layer 3 configuration problem on 
your test machine, or it could indicate that the test machine is sending ARP 
requests for the destination address and not receiving replies.  You will want 
to move on to ARP debugging as I noted previously.

> # snoop -d bge0
> Using device bge0 (promiscuous mode)
>            ? -> (multicast)  ETHER Type=88CC (Unknown), size=82 bytes
>            ? -> (multicast)  ETHER Type=88CC (Unknown), size=82 bytes
>            ? -> (multicast)  ETHER Type=88CC (Unknown), size=82 bytes
>            ? -> (multicast)  ETHER Type=88CC (Unknown), size=82 bytes
> (broadcast)  ARP C Who is 172.16.30.65

The type 88CC packets are those being sent by lldpd, as I mentioned.
You can Google LLDP and find reasonable descriptions of the protocol.

> 2. Am afraid I am a newbie to smartos stuck on a nic issue! And don’t know 
> anything yet with dtrace, truss or snoop. I may have to google around or if 
> you can help via #smartos IRC let me know the time.

You need to start being more self-sufficient in debugging this.
Numerous people have sent you numerous suggestions for approaches to try, 
commands (you can read the manual for each one with 'man <command>'; e.g., 'man 
arp') that may be useful, and protocols you can research on the Internet.  We 
are not here, in general, to teach you how Ethernet or IP work; those are 
general concepts that are independent of SmartOS which you can and should 
research on your own.

DTrace has its own entire web-based guide, in addition to the command's manual 
page.  See http://dtrace.org/guide.

> If I install Ubuntu on this same server everything works fine. I installed 
> OmniOS and I had the same issue as with smartOs!

Ok.  That rules out a completely nonfunctional NIC.  There are still many 
possibilities; the two most likely theories have already been described to you: 
an incompatibility between the illumos bge driver and your specific MAC ASIC, 
and a layer 3 configuration problem.  Everything you need to start making 
progress toward distinguishing the two has already been provided to you in this 
thread.


-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/26461380-1faa08ce
Modify Your Subscription: https://www.listbox.com/member/?&;
Powered by Listbox: http://www.listbox.com




-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/24559458-54d8e931
Modify Your Subscription: https://www.listbox.com/member/?&;
Powered by Listbox: http://www.listbox.com
 
smartos-discuss | Archives  | Modify Your Subscription  


-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to