similar to: Link Aggregation limitations

Hi, Can you tell why my vnic built on top of an aggregation of 2 NICs of 1 Gbit/s doesn''t report a speed of 2 GBit/s ? [root at nazgul /]# dladm show-dev bge0 link: up speed: 1000Mb duplex: full bge1 link: down speed: 0Mb duplex: unknown bge2 link: down speed: 0Mb duplex: unknown bge3 link: down speed: 0Mb

On OpenSolaris 2009.06 I created a flow, half a dozen VNICs, and I set some properties, and everything was working, then I rebooted my system and everything disappeared from show-vnic, show-flow, and show-prop. When I tried to re-create the objects, dladm said they already existed. While I could not see the objects, I could delete them. Example: # dladm show-vnic # dladm create-vnic -l bge0

Crossbow team, The following is of interest to the Crossbow project. Since a large chunk of these changes also exist in the Crossbow gate, the delivery of this wad will result in fewer lines of changes for Crossbow''s delivery. If someone on Crossbow could participate in this review, that would be a bonus (Eric Cheng made original changes in the Crossbow gate at some point last year).

Using OpenSolaris 2008.11 build 110. Created vnic''s and etherstub''s and they are displayed using dladm show-links but when the server is rebooted a ''dladm show-link'' is empty although the vnic and etherstub devices are still there and function properly. That is a real inconvenience, so why do the no longer show after a reboot or shutdown/start? Is there a

Howdy, I just installed the crossbow snapshot from opensolaris.org, and bumped into an issue when attempting to create a virtual nic: $ dladm create-vnic -i 192.168.1.101 -d ni0 2 dladm: VNIC creation failed: No such file or directory (unknown diagnostic) When I truss the process, it looks like it''s failing when attempting to open the vnic pseudo-device: 100878/1:

Howdy, I just finished reading through the Crossbow presentation: http://blogs.sun.com/sunay/resource/crossbow.pdf And have one question. If you create a virtual NIC with dladm: $ dladm create-vnic -d bge0 -m 0:1:2:3:4:5 -b 10000 1 Can you then add vnic1 directly to the zone? e.g.: zonecfg -z zone1 zonecfg:zone1> create zonecfg:zone1> set zonepath=/zones/zone1 zonecfg:zone1> add net

Hello, I am a rather new user to OpenSolaris and I have been loving every minute of it. I have spent quite a lot of time looking around for bandwidth management features and Project Crossbow is just amazing. It is truly amazing compared to what Linux has to offer. I would like to use flowadm to do some bandwidth management on a tun interface. The problem is that it is not recognized by the dladm

redirecting to crossbow-discuss... On 03/12/09 15:17, Andrew Gabriel wrote: > In snv_108, I''m playing with creating a vnic over an etherstub, and I > might not be doing it right, but the behaviour I''m seeing doesn''t look > right either. > > So this is what I did... > > # dladm create-etherstub estub0 > # dladm create-vnic -l estub0 vnic0 > #

I just BFU''ed up to B61 and started to play with IP Instances. I''m having trouble making my zone happy: root at aeon zones$ zoneadm -z testing1 boot zoneadm: zone ''testing1'': WARNING: unable to hold network interface ''skge0''.: Invalid argument root at aeon zones$ dladm show-dev nge0 link: up speed: 100Mb duplex: full

Basically what I am trying to attempt here is to have multiple vm''s in a private network that is seperate from any of the physical networking devices. So far all I have really been able to do is connect the vm''s to an etherstub, but cannot get them to communicate with eachother. I have been using this (http://blogs.sun.com/droux/entry/private_virtual_networks_for_solaris) as a

On 03/25/09 12:30, James Carlson wrote: > Girish Moodalbail writes: > >> bash-3.2# dladm show-link >> LINK CLASS MTU STATE PROMISC OVER >> e1000g0 phys 1501 up off -- >> e1000g1 phys 1502 up on -- >> > > That (plus or minus some column alignment) seems

I opened a bug report earlier today but it doesn''t seem to have been added to the bugs database. I''m posting here in case one of the Crossbow developers might see it and confirm this behavior. Description Duplicate packets are generated whenever an aggregate is introduced into the network configuration. We''ve ruled out switch ports and physical bge interfaces as

Folks, I''m playing with maxbw on links (as opposed to flows) in Crossbow, and I have a couple of questions. First, the limts seem only advisory. The first example has the main host talking to a zone that has 172.16.17.100 configured on znic0. When there is no maxbw, the throughtput is as expected; when maxbw is 55M the throughput only drops to 76 Mbps: # netperf -H

Hi, I''m afraid I have some problems understanding how crossbow is supposed to work ;) On my machine (OpenSolaris, snv_111) I''m running VirtualBox with couple of linux / XP installation and additionally a zone with exclusive IP. My network configuration looks like this: [6]elsinore:~>dladm show-link LINK CLASS MTU STATE OVER bge0 phys 1500 up

I decided to take a stab at 6601421 dladm set-linkprop should support multiple -p options along with some related linkprop fixes, but when I looked into dladm.c, was surprised to find that "dladm_parse_props()" is called from do_create_aggr and do_create_vlan in addition to the expected (by me, at least) do_create_vnic *linkprop functions. What happened here? Why do we pass in

On 03/10/10 10:48 AM, Mahesh wrote: > Hi all, > > I need some help in debugging the gldv3 driver performance issue on sparc. The driver has single Tx queue and 4 Rx queues and performs at almost the line rate(10G) on Sun intel boxes but the same driver performs very badly on sparc. The code is identical for sparc and intel except swapping involved since the hardware is little endian .

Has anyone gotten a transparent firewall working? I''m using snv_125 on an IBM x346 (snv_130 goes into endless boot loops on this hardware). I can create a working bridge with dladm, but can''t stop packets, even with "block in quick all". That stops packets on my management interface bge0, but not on the bridge. :( tim at ghost:~# ifconfig -a lo0:

Ok, I''m hoping this is a fairly trivial issue, and I''m missing something. I''m trying to use Solaris zones (Nevada Build 117) to act as a DMZ and a router, using exclusive IPs, VNICs (from Crossbow), and connecting to the internet (static IP from my ISP). I''ve got the DMZ working - that zone sees the internet, can do name lookups, ftp, telnet, ssh, etc etc etc.

So, just to play with vnics with 106, I have... e1000g2 plumb''d with 192.168.85.10 vnic0 is created on top of e1000g2 with 192.168.85.22 I snoop on e1000g2 to see the traffic. I ping 192.168.85.22 and it works. I stop the snoop on e1000g2. I ping 192.168.85.22 and it doesn''t work. I start the snoop on e1000g2. I ping 192.168.85.22 and ping works. Is this a new feature with

Hi, >From what I have read, the create-vnic feature in dladm is only available within the context of crossbow...? Specifically, what I am wondering is whether it is at all possible to successfully install crossbow on top of Sun''s "Standard/sunsolve supported" Solaris 10/08 rather than OpenSolaris, per. Se.... Is this at all feasible? Many thanks in advance.. Best