Hi
I am currently in the process of reviewing our design OSFP for our OT network.
We like to use areas to summaries the route to sites. We have above 100 sits. But I have notice a design issue.
If we only enable the area 1 on R1 and R8, and we use summaries. then at some time its the fiber (a single point of failure) between R12 and R13 gets damages so any links that uses that fiber is broken.
The distance between R1 and R8 is 40km.
The distance between R1 and R15 is 50km.
At the R1 and R8 the route to the site is summeries to "10.1.0.0/16". Before being distributed.
When the fiber is broken network 10.1.1.0/27 and 10.1.2.0/27, can not reach 10.1.3.0/27 and traffic from other areas will depend on what router they take.
So I figure my options are:
- Don't use summaries
- Include all routers in area 0, to all my other areas.
- Make Physical Link between all ABR, for the different combinations of ABR.
Don't use summaries
This will flood the system with a lot of small routes. this will make managing OSPF harder, and we need to use hardware that support a lot of routes.
Include all routers in area 0, to all my other areas
This will also flood the system, but will be limited to the backbone. It would mean we need to change config of all backbone routers everytime we make changes to areas. That will make managing OSPF harder.
Make Physical Link between all ABR, for the different combinations of ABR.
We do have a lot of fiber and link distance are manageable, but do to the number of sits, this will eat up the all the shared capacity. C/DWDM is possible but even harder to manageable, when different sits are involved, and the knowledge floor for C/DWDM is high.
Other options
There are related functionalities in OSPF, that would fit my need but they have limitations:
- OSPF support virtual links over non-backbone areas, but not the other way around.
- Juniper and Cisco support "Shame links over MPLS", but can't be enable without MPLS.
Am I missing something?
No comments:
Post a Comment