Howdy, As part of the Nemo / crossbow implementations, are there any plans to add tools to monitor (V)NIC utilization? Brendan Gregg wrote the super nifty nicstat utility: http://users.tpg.com.au/adsln4yb/K9Toolkit/nicstat And I am curious if something similar will be provided with crossobow? Thanks, - Ryan -- UNIX Administrator http://prefetch.net
Hello,
the existing dladm show-vnic -s displays the number of bytes IN/OUT/dropped.
We''ll be delivering more tools for monitoring (V)NICs utilization:
basically tools to answer the following two questions:
. How is the bandwidth available on a given link is getting
utilized between
the flows (VNICs and others) that share it.
. How much CPU resources these flows are consuming .
Mike Lim will be sending the proposed tool on this list soon.
Thanks,
Kais.
Matty wrote:
>
> Howdy,
>
> As part of the Nemo / crossbow implementations, are there any plans to
> add tools to monitor (V)NIC utilization? Brendan Gregg wrote the super
> nifty nicstat utility:
>
> http://users.tpg.com.au/adsln4yb/K9Toolkit/nicstat
>
> And I am curious if something similar will be provided with crossobow?
>
> Thanks,
> - Ryan
> --
> UNIX Administrator
> http://prefetch.net
> _______________________________________________
> crossbow-discuss mailing list
> crossbow-discuss at opensolaris.org
> http://opensolaris.org/mailman/listinfo/crossbow-discuss
And BTW, since VNICs are Nemo/GLDv3 MACs, the basic set of kstats are exported for them by the MAC layer. This means that Brendan''s nicstat utility should work as-is with VNICs. Nicolas. Kais Belgaied wrote:> Hello, > > the existing dladm show-vnic -s displays the number of bytes > IN/OUT/dropped. > We''ll be delivering more tools for monitoring (V)NICs utilization: > basically tools to answer the following two questions: > . How is the bandwidth available on a given link is getting utilized > between > the flows (VNICs and others) that share it. > . How much CPU resources these flows are consuming . > > Mike Lim will be sending the proposed tool on this list soon. > > Thanks, > Kais. > > Matty wrote: > >> >> Howdy, >> >> As part of the Nemo / crossbow implementations, are there any plans to >> add tools to monitor (V)NIC utilization? Brendan Gregg wrote the super >> nifty nicstat utility: >> >> http://users.tpg.com.au/adsln4yb/K9Toolkit/nicstat >> >> And I am curious if something similar will be provided with crossobow? >> >> Thanks, >> - Ryan >> -- >> UNIX Administrator >> http://prefetch.net >> _______________________________________________ >> crossbow-discuss mailing list >> crossbow-discuss at opensolaris.org >> http://opensolaris.org/mailman/listinfo/crossbow-discuss > > > _______________________________________________ > crossbow-discuss mailing list > crossbow-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/crossbow-discuss-- Nicolas Droux, Solaris Kernel Networking Sun Microsystems, Inc. http://blogs.sun.com/droux
On Mon, 16 Oct 2006, Nicolas Droux wrote:> And BTW, since VNICs are Nemo/GLDv3 MACs, the basic set of kstats are > exported for them by the MAC layer. > > This means that Brendan''s nicstat utility should work as-is with VNICs.Hi Nicolas, This is awesome to hear. Brendan''s script is super useful, and I am hopeful that ''dladm show-vnic -s'' will provide similar information. Realtime statistics are super useful for troubleshooting problems, and having the tools installed by default will be extremely handy! Thanks again for the reply, - Ryan -- UNIX Administrator http://prefetch.net
Matty wrote:> > On Mon, 16 Oct 2006, Nicolas Droux wrote: > >> And BTW, since VNICs are Nemo/GLDv3 MACs, the basic set of kstats are >> exported for them by the MAC layer. >> >> This means that Brendan''s nicstat utility should work as-is with VNICs. > > Hi Nicolas, > > This is awesome to hear. Brendan''s script is super useful, and I am > hopeful that ''dladm show-vnic -s'' will provide similar information. > Realtime statistics are super useful for troubleshooting problems, and > having the tools installed by default will be extremely handy!As of now, dladm show-vnic -s doesn''t have average size, utilization and saturation per vnic. I plan to have utilization in a netstat option which will provide network statistics per flow. -Mike
Kais Belgaied wrote:> Hello, > > the existing dladm show-vnic -s displays the number of bytes > IN/OUT/dropped. > We''ll be delivering more tools for monitoring (V)NICs utilization: > basically tools to answer the following two questions: > . How is the bandwidth available on a given link is getting utilized > between > the flows (VNICs and others) that share it. > . How much CPU resources these flows are consuming . > > Mike Lim will be sending the proposed tool on this list soon.Here''s my current proposal. Comments welcome... netstat -u (proposed) CrossBow would add -u -uv and-U options to display network usage information by flow. For the first form netstat -u, the input/output bytes and errors since startup will be displayed. The second form netstat -uv is more verbose and adds the device, flow description and resource information. The third form netstat -U will provide network flow statistics in a manner similar to BSD top or prstat(1M). Usage #netstat -u Name ibytes ipkts ierrs obytes opkts oerrs vnic1 123456789 12345678 123 10.1% 12346789 12345678 123 10.2% vnic2 123456789 12345678 123 10.1% 12346789 12345678 123 10.2% tcp_888 123456789 12345678 123 10.1% 12346789 12345678 123 10.2% tcp_25 123456789 12345678 123 10.1% 12346789 12345678 123 20.2% Usage-verbose #netstat -uv Name Dev desc resource ibytes ipkts ierrs obytes opkts oerrs vnic1 bge0 IP=1.2.3.4 bw=2000kbps 123456789 12345678 123 10.1% 123456789 12345678 123 20.2% vnic2 bge0 MAC=0:22:33:44:55 bw=2000kbps 123456789 12345678 123 10.1% 123456789 12345678 123 20.2% tcp_888 vnic1 DPORT=888 bw=2000kbps 123456789 12345678 123 10.1% 123456789 12345678 123 20.2% tcp_25 vnic1 DPORT=25 bw=1000kbps 123456789 12345678 123 10.1% 123456789 12345678 123 20.2% Usage-top #netstat -U CPU Input Output Name ID Use bps pkt/s bps pkt/s tcp_888 0 0.2% 12.23M 12345 20.1% 12.23M 12345 30.2% vnic1 1 1.0% 12.22M 12345 10.1% 12.24M 12345 10.2% tcp_25 1 0.3% 123.12K 12345 8.1% 12.25M 12345 10.2% vnic2 2 1.1% 1.23M 12345 4.1% 12.21K 12345 33.2% unused 79.8% 39.6% -Mike
David.Comay at Sun.COM
2006-Oct-17 21:51 UTC
[crossbow-discuss] Tools to view NIC utilization?
> netstat -u (proposed)I believe 4.x BSD''s netstat(1) uses "-u" to select the printing of UNIX domain sockets. dsc
Michael Lim wrote:> As of now, dladm show-vnic -s doesn''t have average size, utilization and > saturation per vnic. I plan to have utilization in a netstat option > which will provide network statistics per flow.I have a level-zero question whether this should be part of show-vnic, or show-link. Each nic has some speed (ifspeed in kstat) thus showing the utilization as a percentage would be a useful thing. This has implications not only on what we show, but also what crossbow functionality is available for what datalinks. Will there be a future when I can set a bandwidth limit on bge0? On bge33000 (a VLAN interface)? Or will I always have to define a VNIC on top of them, even if I don''t want multiple VNICs, just to I can - limit the bandwidth? - observe the utilization? Erik
David.Comay at sun.com wrote:>> netstat -u (proposed) > > I believe 4.x BSD''s netstat(1) uses "-u" to select the printing of UNIX > domain sockets.Thanks for catching this. I only checked the options to Solaris netstat. This functionality *may* be included in another CrossBow utility if that''s more appropriate. -Mike
Erik Nordmark wrote:> Michael Lim wrote: > >> As of now, dladm show-vnic -s doesn''t have average size, utilization and >> saturation per vnic. I plan to have utilization in a netstat option >> which will provide network statistics per flow. > > I have a level-zero question whether this should be part of show-vnic, > or show-link.To show-link... maybe, to show-vnic... no, see below.> > Each nic has some speed (ifspeed in kstat) thus showing the utilization > as a percentage would be a useful thing. > > This has implications not only on what we show, but also what crossbow > functionality is available for what datalinks. > > Will there be a future when I can set a bandwidth limit on bge0? On > bge33000 (a VLAN interface)?Yes, that''s the plan. Bandwidth limits/guarantees as well as priorities will be properties of data-links in general, not just VNICs. Sub-flows will be defined using netrcm(1M) on top of any data-links, which can be VNICs, physical devices, etc. (Note also that VLANs will move to the VNIC layer)> Or will I always have to define a VNIC on top of them, even if I don''t > want multiple VNICs, just to I can > - limit the bandwidth? > - observe the utilization?That would be suboptimal. Nicolas.> > Erik > > _______________________________________________ > crossbow-discuss mailing list > crossbow-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/crossbow-discuss-- Nicolas Droux, Solaris Kernel Networking Sun Microsystems, Inc. http://blogs.sun.com/droux
Nicolas Droux wrote:> > > Erik Nordmark wrote: >> Michael Lim wrote: >> >>> As of now, dladm show-vnic -s doesn''t have average size, utilization and >>> saturation per vnic. I plan to have utilization in a netstat option >>> which will provide network statistics per flow. >> >> I have a level-zero question whether this should be part of show-vnic, >> or show-link. > > To show-link... maybe, to show-vnic... no, see below.perhaps dladm show-link -u ?>> Each nic has some speed (ifspeed in kstat) thus showing the >> utilization as a percentage would be a useful thing. >> >> This has implications not only on what we show, but also what crossbow >> functionality is available for what datalinks. >> >> Will there be a future when I can set a bandwidth limit on bge0? On >> bge33000 (a VLAN interface)? > > Yes, that''s the plan. Bandwidth limits/guarantees as well as priorities > will be properties of data-links in general, not just VNICs. Sub-flows > will be defined using netrcm(1M) on top of any data-links, which can be > VNICs, physical devices, etc.Once Clearview''s vanity naming is available, we could always create the vnic and rename it to the original datalink name. -Mike
Michael Lim wrote On 10/17/06 16:04,:> Nicolas Droux wrote: > >> >> >> Erik Nordmark wrote: >> >>> Michael Lim wrote: >>> >>>> As of now, dladm show-vnic -s doesn''t have average size, >>>> utilization and >>>> saturation per vnic. I plan to have utilization in a netstat option >>>> which will provide network statistics per flow. >>> >>> >>> I have a level-zero question whether this should be part of >>> show-vnic, or show-link. >> >> >> To show-link... maybe, to show-vnic... no, see below. > > > perhaps dladm show-link -u ?sounds right.> >>> Each nic has some speed (ifspeed in kstat) thus showing the >>> utilization as a percentage would be a useful thing. >>> >>> This has implications not only on what we show, but also what >>> crossbow functionality is available for what datalinks. >>> >>> Will there be a future when I can set a bandwidth limit on bge0? On >>> bge33000 (a VLAN interface)? >> >> >> Yes, that''s the plan. Bandwidth limits/guarantees as well as >> priorities will be properties of data-links in general, not just >> VNICs. Sub-flows will be defined using netrcm(1M) on top of any >> data-links, which can be VNICs, physical devices, etc. > > > Once Clearview''s vanity naming is available, we could always create the > vnic and rename it to the original datalink name.the creation of a VNIC named after the actual physical NIC would happen under the hood. Kais> > -Mike > _______________________________________________ > crossbow-discuss mailing list > crossbow-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/crossbow-discuss
Kais Belgaied wrote:>>>> Each nic has some speed (ifspeed in kstat) thus showing the >>>> utilization as a percentage would be a useful thing. >>>> >>>> This has implications not only on what we show, but also what >>>> crossbow functionality is available for what datalinks. >>>> >>>> Will there be a future when I can set a bandwidth limit on bge0? On >>>> bge33000 (a VLAN interface)? >>> >>> >>> Yes, that''s the plan. Bandwidth limits/guarantees as well as >>> priorities will be properties of data-links in general, not just >>> VNICs. Sub-flows will be defined using netrcm(1M) on top of any >>> data-links, which can be VNICs, physical devices, etc. >> >> >> Once Clearview''s vanity naming is available, we could always create the >> vnic and rename it to the original datalink name. > > > the creation of a VNIC named after the actual physical NIC would happen > under the > hood.Our current design doesn''t require VNICs to be used internally to define sub-flows or assign bandwidth policies to data-links in general, so this would not be needed. -- Nicolas Droux, Solaris Kernel Networking Sun Microsystems, Inc. http://blogs.sun.com/droux
> netstat -u (proposed)> > CrossBow would add -u -uv and-U options to display network usage > information by flow. For the first form netstat -u, the input/output > bytes and errors since startup will be displayed. The second form > netstat -uv is more verbose and adds the device, flow description and > resource information. The third form netstat -U will provide network > flow statistics in a manner similar to BSD top or prstat(1M). Nit: please prefer ''link'' to device -- unless we really want this to show the physical device name regardless of what the administrator has chosen to name the link. -- meem