Hello Dipesh,
lazy was a joke sorry if this looked like not respectful, I understand the location is critical
But you have already made a list of requirements and this is a good starting point.
1) means to use appropriate route-maps in order to control redistribution
prefix-lists invoked in the route-map are the best tool for this task
2) you can use network command in BGP instead of implementing mutual redistribution. BGP network command looks for the prefix in the IP routing table and works also for routes learned by EIGRP. This allows to simplify your configuration and to make the setup safer. Highly recommended.
3) once EIGRP is active between CE and core you don't need to redistribute static routes anymore.
you can make static routes floating with AD > 170 = EIGRP D EX routes AD so if a route is missing in EIGRP you can pick up the floating static route instead.
you can even verify the EIGRP topology on internal switches before making the static routes floating on core switch.
First of all you build EIGRP neighborships on all required links
CE1- core switch
CE2 -core switch
core switch -distrib1
core switch-distrib2
no redistribution is performed at this point all routing to remote sites use the static routes.
on CE1 and CE2 under router bgp you add network commands for all prefixes of central site with the correct subnet mask ( important if auto-summary is disabled).
internal prefixes are not learned via EIGRP at this point keep the redistribute static in BGP for now
on remote site A you configure a new subnet A.B.C.D for testing purposes with only SVIs or subifs on it.
On CE1 and CE2 you redistribute this prefix A.B.C.D from BGP to EIGRP t
on core switch you verify using EIGRP topology the presence of A.B.C.D prefix
show ip eigrp topology all-links
at this point if core switch has a static route for A.B.C.D the sh ip route A.B.C.D shows two static routes one to CE1 and one to CE2.
now you make these two static routes floating by rewriting them with a 201 at the end of the line (new AD)
at this point the EIGRP route for A.B.C.D should be installed on core switch
the same should be received and installed on distrib1 and distrib2.
the same process can be used for a test subnet on core site:
prefix E.F.G.H is a subnet of core site connected to distrib1 and distrib2. it can be an existing one, or one you use for testing.
have the prefix advertised in EIGRP using
router eigrp
network
+
passive-interface command
on distrib1, distrib2
under router bgp on CE1 and CE2 add a network statement for prefix E.F.G.H
the prefix should be advertised to PE nodes and received on remote site CE node(s).
on site A where A.B.C.D is defined you should see E.F.G.H
now pinging from A.B.C.D to E.F.G.H should work both directions and using EIGRP at central site and eventually on remote site A.
if all this has worked you have the working configuration and you need just to extend it to cover all prefixes in core site and on all remote sites (if necessary, this may be already in place)
Hope to help
Giuseppe
