NCS540 Good Middle of the Road Box
June 12, 2019

NCS540 Good Middle of the Road Box

Ben Wiechman | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Cisco 500 Series Network Convergence System (NCS 500)

Two primary use cases: 1)10G port aggregation at the SP edge (RPHY aggregation, 10G E-UNI/NNI ports, access aggregation) where higher 10G port density is required than is possible on the ASR9001 routers we typically have installed in a CO location. 2) POP router for small POP expansions with unknown growth potential. Reasonable trade-off between port density and cost, especially in greenfield deployments with unknown market potential.

Pros

  • Pay as you grow
  • Operating system is consistent with other establish equipment (IOS-XR) — using primarily NCS540
  • Support for 25G port speeds

Cons

  • MPLS feature set on NCS520
  • Full support for RFC2544, Y.1564 across the product line
  • Greater clarity of the impact of smaller buffers on NCS540 when compared to other Qumran chipsets — some use cases like RPHY aggregation at network core are not a good fit.
  • Better price point for network edge
  • Cisco 9000 Series Aggregation Services Routers (ASR 9000)
Higher 10G port density on NCS540
Availability of 25G/40G/100G provides greater flexibility
Good choice when full line rate is not needed
Good choice when full capabilities of ASR9000 are not required

Well suited for10G aggregation at network edge. Small managed networks such as school districts or distributed enterprise campus. Not well suited to RPHY aggregation at network core — queuing in NCS540 results in jitter and poor RPHY performance. Allow port license purchases in smaller units. Better support for SLA performance monitoring capabilities would allow use as a box for 10G aggregation for Carrier Ethernet NNI handoff.

Comments

  • Prakash Daga | TrustRadius Reviewer
    Great review. 1- It has 4Gb of buffer . I am curious to understand why would you think this as small ? 2- It also has added performance management capabilities for Carrier Ethernet NNI handoff. 3-It also has full MPLS capability with state-of-the-art Segment Routing as well. It definitely can not match full ASR9000 capabilities
    • Ben Wiechman | TrustRadius Reviewer
      1-Under certain traffic conditions involving a high packet rate of packets in placed into a high priority QoS queue the the first level cache limit can be exceeded resulting in jitter/frame delay variation that may be unacceptable in certain use cases. In our specific circumstance we had deployed the NCS540 as a router used to aggregate 10 Gbps ports on the CIN network connecting a CBR8 with RPHY nodes. When QoS was configured in alignment with best practices the high rate of frames for RPHY node timing and DEPI/UEPI session maintenance were experiencing unacceptable levels of jitter (5-10ms) resulting in poor throughput for DOCSIS services. Other use cases involving a high PPS rate of packets in a high priority queue might also experience similar issues. 2- Cisco has been expanding support for various MEF performance management capabilities, however at the time I wrote the review those were not supported. They may be at this time. However at the time I wrote the review they were not so it was fair to point that out. 3- The topic of the review, as asked by TrustRadius, was the NCS500 line overall. While the NCS540 and above do indeed have a broad MPLS feature set, at the time the review was written the NCS520 most certainly did not. There was no support for MPLS, and that fact was not entirely clear in the documentation. It was indicated as a roadmap item. If considering the NCS520 please carefully review Cisco's progress in this area if MPLS capabilities are critical requirements. As a side note since the previous review we have encountered additional issues with the IP fast reroute capabilities of the NCS540. Under certain conditions with high numbers of equal cost routes the route table may not be built correctly unless LFA IP-FRR is disabled or IGP metrics are modified to prioritize one path over another. I am unaware of a current fix. Workarounds are to disable LFA or modify metrics. This was noted in multiple scenarios using ISIS as the IGP in conjunction with MPLS LDP. Unknown if the same conditions apply to SR/TI-LFA, SRv6, or OSPF/LDP configurations.

More Reviews of Cisco 500 Series Network Convergence System (NCS 500)