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.

# 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

# dladm show-link
LINK        CLASS     MTU    STATE    BRIDGE     OVER
bge0        phys      1500   up       --         --

# dladm show-phys
LINK         MEDIA                STATE      SPEED  DUPLEX    DEVICE
bge0         Ethernet             up         100    full      bge0

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.

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

-----Original Message-----
From: Keith Wesolowski [mailto:[email protected]] 
Sent: Monday, September 22, 2014 4:00 PM
To: [email protected]; [email protected]
Subject: Re: [smartos-discuss] Network Problem

On Mon, Sep 22, 2014 at 03:38:54PM +0200, [email protected] 
wrote:

> ·  Broadcom Corporation NetXtreme BCM5723 Gigabit Ethernet PCIe
> 
> *     Driver: bge
> *     PCI ID: 14e4,165b
> *     Originating manifest: driver-network-bge.mf
> 
> According to: http://illumos.org/hcl/
> 
> And that’s my card, so why cant I get networking up?!

Reading everything in the entire history contained in this message, it appears 
that "networking" *is* up.  That is to say, whatever difficulties you are 
having are unrelated to the device driver or the hardware and are instead at 
layer 3.

When faced with issues of this sort, there are two tactics I like to employ to 
debug the problem:

1. Disconnect the system from larger upstream networks.  Attach a single 
crossover cable (or two straight-through cables and a known-good hub) between 
the admin network device of the system being debugged and a network device that 
is known to work on another host (this is one of the few things laptops are 
especially good for).  Note that gigabit Ethernet does not require crossover 
cabling as it is required by the standard to be autosensing, although as with 
any standard one should not rely on proper implementation in a system that is 
known not to be working.  One can then experiment with extremely simple layer 3 
configurations on the two hosts to validate conclusively that layers 1 and 2 
are working properly.  If in fact this does not work with even the most trivial 
possible layer 3 configuration, proceed to tactic #2...

2. Bypass layer 3 entirely by using a layer 2 protocol.  We ship, and enable by 
default, LLDP, making that a good choice for this.  An intermediate step here 
is to manually set ARP entries on both hosts to rule out layer 2 broadcast 
issues; you may wish to try that before moving on to LLDP or another layer 2 
protocol.  By default, the system should transmit and listen for LLDP frames on 
all network devices that are up (which yours is).  You can verify that this is 
occurring via truss, DTrace, snoop, and other tools.  Once you have found that 
the packets are being sent by lldpd on the system being debugged, use whatever 
network tracing software is available to you on the peer host to determine 
whether they are being received properly.  If they are, you have ruled out 
layer 1 and 2 problems generally.  If not, your next step depends on whether 
there are no packets being received at all or if they are being received with 
some kind of corruption.  In either case, your likely next step will be to use 
DTrace to determine whether the packets are making it to your hardware device 
or being dropped somewhere in the kernel.  If they are making it to the device, 
you may wish to use an oscilloscope to determine conclusively that they are not 
making it onto the wire (condemn NIC); if they are not, you will need to 
determine what software is dropping them and why, using DTrace and source code 
analysis.

The overwhelmingly likely outcome of this will be that you exonerate layers 1 
and 2 and will need to proceed to understand the layer 3 misconfiguration 
involved.  Typical tools here include ping, traceroute, dig, and netstat.  
Debugging layer 3 problems involves very little SmartOS-specific knowledge, and 
you can find plenty of information on appropriate tactics by searching the 
Internet (from a working host, naturally).  Unfortunately, we do not know the 
details of the networks to which your host is attached, so it is impossible to 
provide more specific guidance; however, there is nothing SmartOS-specific 
about getting layer 3 connectivity to the GZ working via the admin network.

> From: [email protected] 
> [mailto:[email protected]]
> Sent: Friday, September 19, 2014 1:11 PM
> To: [email protected]; [email protected]
> Subject: RE: [smartos-discuss] Network Problem
> 
>  
> 
> Correction:
> 
>  
> 
> # dladm show-link
> 
> LINK        CLASS     MTU    STATE    BRIDGE     OVER
> 
> bge0        phys      1500      up     --         --
> 
>  
> 
> From: [email protected] 
> [mailto:[email protected]]
> Sent: Friday, September 19, 2014 1:06 PM
> To: [email protected]; [email protected]
> Subject: RE: [smartos-discuss] Network Problem
> 
>  
> 
> # prtconf -dD | grep bge
> 
>             pci103c,705d (pciex14e4,165b) [Broadcom Corporation 
> NetXtreme BCM5723 Gigabit Ethernet PCIe], instance #0 (driver name: 
> bge)
> 
>  
> 
> # dladm show-link
> 
> LINK        CLASS     MTU    STATE    BRIDGE     OVER
> 
> bge0        phys      1500   down     --         --
> 
>  
> 
> Still cant ping out … or oing the server from the LAN.
> 
>  
> 
> From: [email protected] 
> [mailto:[email protected]]
> Sent: Wednesday, September 17, 2014 9:03 AM
> To: [email protected]; [email protected]
> Subject: RE: [smartos-discuss] Network Problem
> 
>  
> 
> Ok, as advised on IRC #smartos, I connected to the server via the serial 
> port. Now can copy and paste.
> 
>  
> 
> # 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 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255
> 
>         ether b4:b5:2f:a0:c1:36
> 
> lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 
> 8252 index 1
> 
>         inet6 ::1/128
> 
>  
> 
> # dladm show-phys
> 
> LINK         MEDIA                STATE      SPEED  DUPLEX    DEVICE
> 
> bge0         Ethernet             up         100    full      bge0
> 
>  
> 
> # cat /usbkey/config
> 
> #
> 
> # This file was auto-generated and must be source-able by bash.
> 
> #
> 
>  
> 
> # admin_nic is the nic admin_ip will be connected to for headnode zones.
> 
> admin_nic=b4:b5:2f:a0:c1:36
> 
> admin_ip=192.168.1.2
> 
> admin_netmask=255.255.255.0
> 
> admin_network=...
> 
> admin_gateway=192.168.1.2
> 
>  
> 
> headnode_default_gateway=192.168.1.1
> 
>  
> 
> dns_resolvers=8.8.8.8,8.8.4.4
> 
> dns_domain=<*dn*>.co.zm
> 
>  
> 
> ntp_hosts=0.smartos.pool.ntp.org
> 
> compute_node_ntp_hosts=192.168.1.24
> 
>  
> 
> From: [email protected] 
> [mailto:[email protected]]
> Sent: Tuesday, September 16, 2014 5:49 PM
> To: [email protected]; 'Usama Ahmad'
> Subject: RE: [smartos-discuss] Network Problem
> 
>  
> 
> Zpool import zones fails saying “cant import zones; a pool with the same name 
> is already creaded/imported”
> 
> Login in as root/root also fails …
> 
>  
> 
> From: Usama Ahmad via smartos-discuss 
> [mailto:[email protected]]
> Sent: Sunday, September 07, 2014 10:20 PM
> To: [email protected]
> Subject: Re: [smartos-discuss] Network Problem
> 
>  
> 
> Boot into noinstall mode
> 
> login user/pass is root/root
> 
>  
> 
> zpool import zones
> zpool destroy zones
> reboot
> 
>  
> 
> And you are done it will start up asking initial config questions
> 
>  
> 
>  
> 
> On Sun, Sep 7, 2014 at 3:47 PM, <[email protected]> wrote:
> 
> “Maybe try to reinstall SmartOS by rebooting into no install mode and 
> zpool destroy zones.” Time to fire up google I guess, talk about a 
> newbie stuck on a nic issue …
> 
>  
> 
> From: Usama Ahmad via smartos-discuss 
> [mailto:[email protected]]
> Sent: Sunday, September 07, 2014 7:47 PM
> To: [email protected]; [email protected]
> Subject: RE: [smartos-discuss] Network Problem
> 
>  
> 
> 
> On Sep 6, 2014 6:58 AM, <[email protected]> wrote:
> >
> > Hi
> >
> > Please note that I cant even ssh into the server. So cant copy 
> > /usbkey/config, I have to type out ...
> >
> > 1.  /usbkey/config
> >
> > admin_ip=192.168.1.2
> > admin_netmask=255.255.255.0
> > admin_network=...
> > admin_gateway=192.168.1.2
> >
> > headnode_default_gateway=192.168.1.1
> >
> > dns_resolvers=8.8.8.8,8.8.8.4
> >
> > 2.dlam show-phys
> >
> > Link    media           state   speed   duplex  device
> > bge0    ethernet        up      100     full    bge0
> >
> > 3. ifconfig -a
> >
> > bge0:
> > inet 192.168.1.2
> >
> > 4. netstat -rn -f inet
> > Destination     Gateway interface
> > Default         192.168.1.1     bge0
> > 192.168.1.0     192.168.1.2     bge0
> >
> > 5.ipadm show-addr
> > Bge0    static  ok      192.168.1.2/24
> >
> > 6.#ping 192.168.1.2
> > 192.168.1.2 is alive
> >
> > 7. ping 192.168.1.1
> > No answer from 192.168.1.1
> >
> > 8. unplug cable from server and connect to mylaptop with same 
> > ip192.168.1.2, I can ping 192.168.1.1
> >
> > !?
> 
> Hello,
> 
> Could you try to change your IP address for box from 192.168.1.2 to something 
> else for example 192.168.1.101 or any other unused IP. This is to rule out 
> your router as the bottle neck since you mention same IP used for your laptop.
> 
> Keep hope, it should work, most likely something very simple and basic is 
> causing this issue.
> 
> Maybe try to reinstall SmartOS by rebooting into no install mode and zpool 
> destroy zones.
> 
> Hope this helps.
> 
> Usama
> >
> > -----Original Message-----
> > From: Jonathan Perkin via smartos-discuss 
> > [mailto:[email protected]]
> > Sent: Friday, September 05, 2014 4:02 PM
> > To: [email protected]; [email protected]
> > Subject: Re: [smartos-discuss] Network Problem
> >
> > It's difficult to diagnose your problem without seeing all the 
> > details, and it doesn't help that your mail client likes to mangle 
> > plain text so that we cannot be sure your settings are correct.
> >
> > If you provided plain text attachments of the following:
> >
> >  - /usbkey/config
> >  - 'dladm show-phys' output
> >  - 'ifconfig -a' output
> >  - 'netstat -rn -f inet' output
> >  - anything else you think may be relevant for your setup
> >
> > we may be able to help.  The rule of thumb is that you can never 
> > provide too much information.
> >
> > Thanks,
> >
> > --
> > Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com
> >
> >
> > -------------------------------------------
> > 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/? <https://www.listbox.com/member/?&;> 
> > &
> > 78
> > 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/24697919-04ed9bf0
> 
> > Modify Your Subscription: https://www.listbox.com/member/? 
> > <https://www.listbox.com/member/?&;> & Powered by Listbox: 
> > http://www.listbox.com
> 
> 
> smartos-discuss |  
> <https://www.listbox.com/member/archive/184463/=now> Archives  
> <https://www.listbox.com/member/archive/rss/184463/26461380-1faa08ce> 
> |  <https://www.listbox.com/member/?&;> Modify Your Subscription
> 
>  <http://www.listbox.com>
> 
>  
> 
>  
> 
> 
> smartos-discuss |  
> <https://www.listbox.com/member/archive/184463/=now> Archives  
> <https://www.listbox.com/member/archive/rss/184463/26461380-1faa08ce> 
> |  <https://www.listbox.com/member/?&;> Modify Your Subscription
> 
>  <http://www.listbox.com>
> 
>  
> 
> 
> smartos-discuss |  
> <https://www.listbox.com/member/archive/184463/=now> Archives  
> <https://www.listbox.com/member/archive/rss/184463/26461380-1faa08ce> 
> |  <https://www.listbox.com/member/?&;> Modify Your Subscription
> 
>  <http://www.listbox.com>
> 
>  
> 
> 
> smartos-discuss |  
> <https://www.listbox.com/member/archive/184463/=now> Archives  
> <https://www.listbox.com/member/archive/rss/184463/26461380-1faa08ce> 
> |  <https://www.listbox.com/member/?&;> Modify Your Subscription
> 
>  <http://www.listbox.com>
> 
>  
> 
> 
> smartos-discuss |  
> <https://www.listbox.com/member/archive/184463/=now> Archives  
> <https://www.listbox.com/member/archive/rss/184463/26461380-1faa08ce> 
> |  <https://www.listbox.com/member/?&;> Modify Your Subscription
> 
>  <http://www.listbox.com>
> 
>  
> 
> 
> smartos-discuss |  
> <https://www.listbox.com/member/archive/184463/=now> Archives  
> <https://www.listbox.com/member/archive/rss/184463/26461380-1faa08ce> 
> |  <https://www.listbox.com/member/?&;> Modify Your Subscription
> 
>  <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/22141660-bde6cadb
> Modify Your Subscription: 
> https://www.listbox.com/member/?&;
> 6b55b9ac 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/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