in trio qxchip is responsible for H-QOS. you can check it's memory utilization thru this command:
hostname>request pfe execute command "show qxchip 0 memory" target tfeb0 SENT: Ukern command: show qxchip 0 memory GOT: GOT: QX Linkram : 0 GOT: Total buffers in use: 6 (0%) GOT: Bank 0 in use: 3 (0%) GOT: Bank 1 in use: 3 (0%) GOT: Use meter regions: GOT: region up-threshold down-threshold GOT: ------ ------------ -------------- GOT: 0 68% 0% <--- current region GOT: 1 87% 65% GOT: 2 93% 83% GOT: 3 100% 89% GOT: QX Linkram : 1 GOT: Total buffers in use: 6 (0%) GOT: Bank 0 in use: 3 (0%) GOT: Bank 1 in use: 3 (0%) GOT: Use meter regions: GOT: region up-threshold down-threshold GOT: ------ ------------ -------------- GOT: 0 68% 0% <--- current region GOT: 1 87% 65% GOT: 2 93% 83% GOT: 3 100% 89% LOCAL: End of file 2013/11/7 Scott Harvanek <[email protected]> > Does anyone know if there is there a way to see how much buffer > space/queue space is being used for shaping policies on the MX80 / > MIC-3D-20SFP? I can see queue status but I'm more interested in how much > memory is being consumed for shaping. > > We apply some shaping policies per unit on interfaces and we have _a lot_ > of them, I'm wondering if there is any sort of limit of how many interfaces > can be shaped reliably or how we can check buckets/buffers per physical > port to ensure we are not overflowing / losing the shaping ability. > > Hopefully that question makes sense, thanks. > > -- > Scott H. > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
