From: note@ji-net.com
Date: Tue Jan 25 2005 - 14:54:48 GMT-3
Dear all expert.
I have a question about core migration step for service provider..then .. If in the old core network is used multiple OSPF area for IGP & running MP-BGP
for apply MPLS VPN service to customer. Different service has binded in the different VRF, Existing core have 4 core router ( P ) & run MP-BGP for promoted to RR
(Router Reflector) without cluster for a lot of all PE client, (I known that it is bad design haha!). 4 P router have 2 peer group, 1st peer group is fullmesh for 4 P & 2nd
group peer to some PE in some area,...PE can separate to 4 group, all PE in each group peer to 1 P with promoted own to RR of all PE in the area group
(1 PE have 1 peer to 1P). Bad design again.....
PE is not have route reflector redundancy......but still stable...very lucky!! until..subscriber has grown very fast..so we need to implement new core for serve it ...
redesign routing & achitecture & route reflector with clustor should be done.... I redesigning 1 PE in the some area group have 2 peer to 2 RR & select 2 PE
in the same & near area group to route reflector, 2 PE route refector in the same clustor id for avoid routing loop & design new 4 PE with 2 different clustor id!
clustor 1 have 2 PE has promoted to RR & all PE in the same 2 RR area is router client with have 2 peer to 2 RR for redundncy. clustor 2 is in the same concept
but use the different 2 PE in different area. In each 4 PE RR router reflector create full mesh peer group for advertise routing update to all 4 PE in different 2 clustor
Is it a good design ??? Do you have any comment?
Until.. implementation process about physical is already finished, but the best difficult step that to say is migration service to new core !!! New core have 4 P & use
new link to 2 old gateway interconnect to PE of ISP network (not running MPLS). What should be recomended & considered before migration? & how can I do first?
In my opinion .. first i will configuring 4 new P in the same old backbone area of OSPF & recheck IGP all of them can update & have corrected path. In the next step
I'm not sure.... require suggestion from any expert to advise me for do in the next step.. How to migrate old MPLS core which use P to the router reflector without clustor
and have 2 peer group (1st for full mesh between P, 2st is RR in Hub-spoke topology for PE) & all PE in the all area have 1 peer to 1 RR(P) to the newcore which have
new 4 PE has promoted own to new RR & have 2 different clustor id ( 2PE in 1 clustor id), 4 new PE have 2 peer group (1st for fullmesh peer between 4PE across
different clustor id , 2nd is patial mesh for all PE in distributed area) & all PE in distributed area have 2 RR peer to 2 new PE in same clustor for redundancy & avoid loop.
Don't forgot it about cut over all PE in distributed area to the 4 new P & 4 new P don't run BGP for reduce cpu load, P should be responsibility for forwarding more packet
so that it should not for handle more load such as more routing update!
How I can do this ...........for the migration step............so difficult ...& more complexity.. the best important issue is minimize all downtime of the migration step. Please help me!
Thanks you very much in advance.
Best Regards,
Ralf
Service Provider Solution Developer & Network Engineering.
Email : note@ji-net.com
This archive was generated by hypermail 2.1.4 : Wed Feb 02 2005 - 22:10:25 GMT-3