HSRP would require static routes and this will not scale that well, as you need to update the ASBR(s) each time the customer introduces a new network into one VRF.
Using eBGP as "PE-CE" protocol will give you the redundancy required with the control desired. Per VRF the design can be that of a redundant internet access for an enterprise customer, as the other side is seen like a CE. BGP is built for primary/backup scenarios, so local preference could be used.
Essentially your design question can be rephrased to: How do I offer redundant MPLS VPN access to a customer?
The answer typically will be eBGP or OSPF.
Both protocols have their pros and cons, so a more detailed look into requirements would help to decide for either one.
Thanks for your valuable suggestions and sorry for my delayed response.
I will definitely consider option B as suggested by you, for the time being I have already implemented the previous option and it is looking good so far. The plan is to migrate to option B as we scale further.
Thanking you once again for your helpful comments.
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...