similar to: property parsing in dladm

(Bcc''ed to networking discuss). Hi All, Have enclosed man page draft for dlstat(1M) herewith. This is part of the effort to gain better visibility into network traffic in light of crossbow features like virtual NICs, interrupt vs. polling modes etc. This in turn would greatly assist network performance analysis. It is also aimed at segregating link/flow configuration from

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

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

Following is a short description on assigning priorities to a link (via dladm). Flows will have a similar mechanism (via flowadm). thanks, -venu ---------------------------------------------------------------------------- The components associated with a link or flow, such as Soft Ring Sets, Soft Rings and squeues, have kernel threads processing inbound/outbound packets. The scheduler

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

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 > #

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

Hi All, I have bfu''ed to net-virt_xb-21_snv_81_021308. The dladm command on my machine does not have create-etherstub option. Please let me know what could be the issue. Thanks Khushal

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

Hi all, Link protection is a new feature we are planning to introduce to Solaris and we would like to solicit your feedback on it. Please see attached document for details.

I see in NexentaStor''s announcement of Community Edition 3.0.3 they mention some backported patches in this release. Aside from their management features / UI what is the core OS difference if we move to Nexenta from OpenSolaris b134? These DeDup bugs are my main frustration - if a staff member does a rm * in a directory with dedup you can take down the whole storage server - all with

Hi, Pradeep: I believe you had some questions about modifying bandwidth for flows/VNICs. I believe that should be fine in the recently released bits, could you please check and lets know if you still have any questions about this. Bandwidth limits can be modified using: links: dladm set-linkprop -p maxbw=<value> linkname flows: flowadm set-flowprop -p maxbw=<value> flowname (I

Folks, I just posted an updated Crossbow virtualization architecture document. The new revision is available at: http://opensolaris.org/os/project/crossbow/Docs/crossbow-virt.pdf The main changes are the addition of support for multiple MAC addresses per client, and an explicit separation between consolidation private and project private MAC API entry points. See in particular the

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

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

Hi ! In snv_127 I suddenly face a problem I never had before. Xvm can''t attach a vif to my primary physical nic any longer: $ pfexec xm start ulrac1 Error: Device 0 (vif) could not be connected. error: Failed to create vnic over yukonx1 with MAC address 00:16:36:3c:bf:70 This worked fine in all previous snv_12x releases I tested, including snv_126. I think there is a privilege

Hi, I''m running snv_89 on an X4150 with a CentOS-5 guest. I cannot seem to get my second network interface to work properly. I followed the virt-install instructions, and even saw the FAQ entry about adding a second network instance in the XML config. I see my second device in the guest but it''s either connected to the wrong interface or not at all. I''d like to

1 simple question about network statistics for vnics: We noticed that the statistics for vnics (used by Virtualbox guests) are not there. When the nics are plumped in the host OS, we do see them showing up, but all all records are 0. Can someone tell me how to get the correct network info via snmp on the Vbox Host?? Thanks in advance. IF-MIB::ifDescr.1 = STRING: lo0 IF-MIB::ifDescr.2 = STRING:

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