4 out of 5 (24 Ratings)
May 16, 2017
Cisco and Telus did a very professional job
Apr 26, 2017
Very satified with a solid platform that is scaleable and meets business needs for the present and future.
Apr 11, 2017
Good experience in design and rollout. Since, with the issues Cisco has had, less that desirable.
Mar 9, 2017
The product was easy to install and configure, leaving no room for error
Mar 8, 2017
Generally, in the past, we are satisfied with routers from Cisco. The R&D of new hardware has been satisfactory as to not be a concern. But, the new 4K routers IOS have been one bug after another with serial interfaces, UCM bugs and clocking bugs. We have stopped all deployments with 40+ sitting in a stock room due to intermittent failures in the currently 2-3 deployed sites. We were looking to enhance our remote site capabilities with a better net flow, optimisation, NBAR enhancements and IWAN, at this time, we will pause and wait until we have a more stable device.
Mar 7, 2017
We have a love/hate with both Cisco and their ISR series. We've found the previous gen of HW (18xx) ws actually more powerful from a compute standpoint. Also, if you don't have a cookie cutter break/fix issue then it's almost impossible to get support.
Mar 1, 2017
We received excellent support from Cisco during this implementation.
Feb 22, 2017
The implementation of the 4331 router with IWAN installed with relative ease. The utilization of the legacy Cisco contrller software did not work with the code levels requried on the 4331. We have since learned of a recall on the routers causing us to hlt futher implementatins and replace all existing routers. Cisco is willing to assist with the costs for the replacement.
Feb 21, 2017
As an early adopter of iWAN and PFR, we experienced performance problems and an number of bugs that we did not experience during the pilot phase. Part of the problem was that Cisco sold a solution that was not quite ready. We were given a baseline of the G2 ISR routers, like the 2951, but found that the demands on the cpu were too high. It would have been better to just know, at the beginning, that we needed to step up to the ISR4K.
Feb 16, 2017
Changing of key resources during implementation caused delays to the overall schedule to obtain qualified help from Cisco