07-03-2008 05:39 AM
I'm finding myself spending a whole lot of time correlating WAN throughput reports and WAN Performance reports from CMS to determine the cause of performance issues in a WXC equipped WAN. Which got me thinking that it wouldn't be so difficult to develop a report in CMS that breaks down the sources of inbound traffic from service tunnels.
I have a client with several spoke sites that unexpectedly appear to be significant "sinks" of data coming from a couple of different hubs. We're seeing high rates of loss and latency on the circuits at these spokes during peak periods, and it seems to be due to two or more hubs simultaneously accelerating data to the spoke and flooding the circuit. I'll probably have to resolve this using Bandwidth Management, but it would be really nice to have a report that pulls together and correlates the "WAN throughput to <destination>" stats from all the other devices in the community, so that we can put some science behind the "minimum circuit speed" settings, or whatever other QoS adjustments we make. The data is all there, it just needs crunching.
I reckon this would be a powerful troubleshooting report if it were linked to the WAN Performance monitor reports - it would very quickly show if congestion was the cause of WAN performance issues, saving time spent looking for non-existent problems in the carriage service.
How about it? Any community members agree? Any Juniper folks feel like copying that into Cinnabar? (No, I can't put a dollar value on it for you...)
07-07-2008 03:24 AM
Christopher Howarth CISSP RHCE JNCIS-FWV JNCIA-WX/SSL
07-08-2008 03:01 PM
Thanks for submitting the request!
I've always been sceptical of that dollar value field in Cinnabar, and having done my time in PLM at Nortel, I think it's warranted! ;-)