Comentarios (5)

1 CG_Karthik ha hecho un comentario el Enlace permanente

Thats Infromative Chris.. So The only way for us is to summarize the usage on all of the Client LPAR's and identify how much IO is being transferred through a particular FC adapter at the VIOS. <div>&nbsp;</div> Another way that I can think of is, to get the statistics from your SAN Admin at the Switch port level. It will be real quick if you are managing the SAN too :)

2 Alok Mani ha hecho un comentario el Enlace permanente

i was keep looking this options , even i open an pmr with IBM , but did not get any success , however recently we update the vio server with 2.2.2.2 version now atleat i can see the data bu using fcstat -client <div>&nbsp;</div> dev hostname inreqs outreqs ctrlreqs inbytes outbytes DMA_errs Elem_errs Comm_errs <br /> fcs0 g44ulpvio01 2183828752 384513025 25624392 60940090523140 3588210709504 0 11 0 <br /> vioclh1 186311 7507823 197224 2694179376 36862984192 0 11 0 <br /> vioclp1 164940 7284093 392638 7673730752 48371888128 0 11 0 <br /> vioclp10 210594 14201982 441885 8396580552 81027809280 0 11 0 <br /> vioclp12 111960528 70227399 3341929 5434777307656 892747074560 0 11 0 <br /> vioclp13 54475 16135687 391802 4424845352 98602090496 0 11 0 <br /> vioclp14 22558 7267168 595031 322337916 160177275904 0 11 0 <br /> vioclp15 55048 7252357 395985 4538679008 47578615808 0 11 0 <br /> vioclp16 1044655 6622777 390942 53065186320 43732930560 0 11 0 <br /> vioclp17 37390 6395441 196246 3329114200 37409862656 0 11 0 <br /> vioclp19 99236 15262406 392770 4561026384 107670882304 0 11 0 <br /> vioclp2 143681 8817110 1190092 6399742452 82582437376 0 11 0 <br /> vioclp20 29896 15432883 392497 2639645488 84494008320 0 11 0 <br /> vioclp21 2265514744 39899348 537372 56702015403360 332776955904 0 11 0 <br /> vioclp26 44364 16475904 594872 5305808032 87077830656 0 11 0 <br /> vioclp4 40310691 32066164 9253079 2098612963024 634713994752 0 11 0 <br /> vioclp5 6809 6586072 187389 89813348 29625901056 0 11 0 <br /> vioclp7 56815 4231806 793321 2948891532 27508154880 0 11 0 <br /> vioclp8 29766 16951587 197353 2620692352 106339822592 0 11 0 <br /> vioclp9 42099 1876487 138244 919828604 13433035264 0 11 0 <br /> viocls1 354613 6669017 517476 21941404624 42453999616 0 11 0 <br /> viocls10 99604 15931965 2182505 12014862056 87720435712 0 11 0 <br /> viocls12 15803 3094414 196435 248736968 15504397824 0 11 0 <br /> viocls16 44796 1623694 196784 2254096944 11001445376 0 11 0 <br /> viocls19 116891 37908553 419141 13558015120 223911700992 0 11 0 <br /> viocls4 111826 650701 21847 1618506600 13125791232 0 11 0 <br /> viocls6 22523767 10395860 2567815 3747829768456 77108234240 0 11 0 <br /> viocls7 20797 903451 395875 1838671024 5462908928 0 11 0 <br /> viocls8 0 0 16 0 0 0 11 0 <br /> fcs1 g44ulpvio01 540 0 89 185400 0 0 0 0 <br /> vioclp4 0 0 26 0 0 0 0 0

3 cggibbo ha hecho un comentario el Enlace permanente

Thanks Alok! Very interesting.

4 cggibbo ha hecho un comentario el Enlace permanente

Hmmm, I tried 'fcstat -client' and it dumps core (segmentation fault). Apparently this is a known issue and will not be fixed until the next release?! <div>&nbsp;</div> My VIOS is running 2.2.2.2 with all the latest ifixes. <div>&nbsp;</div> Oh well, I'll wait for the next release and try again.

5 DanBraden ha hecho un comentario el Enlace permanente

To monitor thruput on real FC adapters in a VIOS when using NPIV (or a combination of NPIV and other IO) there are 3 methods I am aware of: <div>&nbsp;</div> 1) $ nmon -&gt; then press ^ <br /> 2) nmon recordings run thru the NMON analyzer <br /> 3) fcstat <div>&nbsp;</div> The fcstat command only provides a point in time total since boot so using it requires doing some math.

Añadir un comentario Añadir un comentario