Correct. I confused with MX-VC that supports it. By the way, the way you get that info on CLI is using "show virtual-chassis vc-port statistics vcp-x/y/z extensive" which is translated into the RPC call used in the script of the KB article you posted.
On Monday, 19 August 2013, Giuliano Medalha wrote: > There is no option for: > > > show interface queue vcp-x/y/z > > > It does not support it. > > > I think that the following KB solved the problem for EX8208 and > EX4200/4500/4550: > > > http://kb.juniper.net/InfoCenter/index?page=content&id=KB27711&actp=RSS > > > Thanks a lot, > > Giuliano > > > > > WZTECH is registered trademark of WZTECH NETWORKS. > Copyright © 2013 WZTECH NETWORKS. All Rights Reserved. > > The information transmitted in this email message and any attachments are > solely for the intended recipient and may contain confidential or > privileged information. If you are not the intended recipient, any review, > transmission, dissemination or other use of this information is > prohibited. If you have received this communication in error, please notify > the sender immediately and delete the material from any computer, including > any copies. > > > On Fri, Aug 16, 2013 at 8:32 PM, Diogo Montagner < > [email protected] <javascript:_e({}, 'cvml', > '[email protected]');>> wrote: > >> The problem of this approach is that you are assuming all packets will >> have the same size. >> >> You could use the timestamp of each collection to calculate how many >> packets traversed the interface in that period. It doesn't have a good >> accuracy but will give something very close. >> >> What about getting the pps and bps from the show interface queue >> vcp-x/y/z ? >> >> Thanks >> >> On Saturday, 17 August 2013, Giuliano Medalha wrote: >> >>> People, >>> >>> We are doing a custom management system for VCP interfaces monitoring >>> using >>> NETCONF in JUNOS. >>> >>> The following stats are the only one reported to us: >>> >>> T2 >>> <input-packets>3966099</input-packets> >>> <output-packets>3985901</output-packets> >>> >>> T1 >>> <input-packets>3966000</input-packets> >>> <output-packets>3985850</output-packets> >>> >>> >>> How is possible to calculate the input rate and the ouput rate ? >>> >>> The MTU for the interface is 1514. >>> >>> Can we consider something like: >>> >>> 1514 x 8 x (3966099-3966000) / (T2 - T1) >>> >>> It can be considering a goog mean value ? Or we will have so much >>> variations for packet size ? >>> >>> packet size for JUNOS (VCP interface) is the same as ethernet frame-size >>> ? >>> >>> Thanks a lot, >>> >>> Giuliano >>> _______________________________________________ >>> juniper-nsp mailing list [email protected] >>> https://puck.nether.net/mailman/listinfo/juniper-nsp >>> >> >> >> -- >> ./diogo -montagner >> JNCIE-SP 0x41A >> > > -- ./diogo -montagner JNCIE-SP 0x41A _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
