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/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
