Subscriber session variation during LC and RP based subscriber config at BNG/ASR9K
BNG config has two options.In first i can config based on RP, where the subscriber session limit is 128k but when i used the LC based sub,it reach to 32 k session per line-card i.e 8*32 k per ASR9K box.
How the control plane behave in both the option and what are pros and cons in opting any options ?
Re: Subscriber session variation during LC and RP based subscriber config at BNG/ASR9K
If you consider the subscriber scale per NP, it doesn't matter whether the session is terminated on the RP or on the LC.
Decision on RP vs LC depends on your topology and scale. With the introduction of BNG Geo-Redudancy the trend in distributed solution is towards LC based because you can scale higher and don't need to rely on link bundling for redundancy, you can simply fail over to standby in case of link failure. For centralised solutions PW-Ether is very interesting because you're cutting the whole network layer (no need for aggregation PE), but at the cost of lower max scale per chassis.
CCO documentation lists out the ability to do a password recovery for eXR with a ZTP/PXE boot.
One can also perform the operation manually, like a "turboboot" for classic XR in this facinity.
this procedure will wipe out the complete system and install a...
Below is a link to a video showing how to analyze traceroute output in L3VPN and look up CEF forwarding and MPLS/TE/SR/SR-TE forwarding for labels through a domain. Some basic examples of traffic engineering are used but the concepts lend the...
This document summarises various health checks that can be done on a Cisco VIM pod.
Cloud sanity checks the health status of network, storage and various openstack infrastructure components like mariadb, rabbitmq etc....
The following pre-requisites are necessary for the migration from RSP440 to RSP880-LT to be successful.
Make sure that you have console access to the router.
Verify that the system is running a minimum o...
BGP flowspec in a nutshell is a feature that will allow you to receive IPv4/IPv6 traffic flow specification (source X, destination Y, protocol UDP, source port A .. etc) and actions that need to be taken on that traffic (...