nV Cluster is EoL, last supported release was XR 5.3.4: https://www.cisco.com/c/en/us/products/collateral/routers/asr-9000-series-aggregation-services-routers/eos-eol-notice-c51-739355.html <https://www.cisco.com/c/en/us/products/collateral/routers/asr-9000-series-aggregation-services-routers/eos-eol-notice-c51-739355.html>
You can find more information here: https://www.cisco.com/c/en/us/support/docs/routers/asr-9000-series-aggregation-services-routers/214280-asr-9000-nv-decluster-procedure.html <https://www.cisco.com/c/en/us/support/docs/routers/asr-9000-series-aggregation-services-routers/214280-asr-9000-nv-decluster-procedure.html> Best Regards Ted > On 3 Jan 2020, at 17:11, Curtis Piehler <[email protected]> wrote: > > As per Cisco documentation the nV edge cluster feature is supported only up > to 5.3.4. While I understand this is the "official documentation" has > anyone used ASR9000 nV edge clustered devices past 5.3.4 (specially in the > 6.X.X line?). > > The aggregate QOS feature comes available in 6.0.1 which is extremely > useful in carrier PE environments (specifically 9001 clustered routers). > Prior to this the aggregate QoS feature one would have to rely on LACP > hot-standby to avoid having a shaper applied to all bundle members > potentially resulting in an incorrect shaper/policer on bundle interface or > sub-interface. > > Has anyone actually ran nV edge cluster devices on 6.X.X devices? Does it > work well, any caveats? Again... please put aside the "official > documentation". I am interested to know if it will actually run. > > Curtis > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
