Partition repair guidelines
...................................................................................................................................................................................................................................
When to use partition repair
Only provision nodes to be Partition Repair Capable in an area, if a Single Point of
Failure otherwise cannot be avoided for that area. If more than one Level-2 entry into
an area is used, partition repair is a valid mechanism.
How to use partition repair
To allow the healing of a partitioned area, two nodes must be provisioned as Partition
Repair Capable as follows:
• At the area boundary, connecting Level-2 node(s) in (an) other area(s)
• The potential virtual link (tunnel) should reduce the SPF’s in the area to a
minimum.
In case an area is partitioned due to a single failure, the two partition repair capable
level-2 nodes in each partition will establish a level-1 tunnel through the level-2
subdomain, in order to repair level-1 connectivity between all nodes in the two related
partitions.
CISCO
WRONG
CORRECT
PP
OS
OS
P
P
OS
OS
ROUTER
No partition repair needed, when a Level-1 ring
in an area is used. A fiber-cut does not
partition repair is
needed: no level-1
ring in the area.
No partition repair
is needed, because
the external router
closes the level-1
ring.
partition the area, and the level-2 nodes should
NOT be provisioned to be partition repair
capable.
partition repair is not
needed, because a
ring is used in each
area
Level-1 subnetwork
Level-1+2 link
data-communication link (level-1)
A Level-2 node / router
A Level-1 node / router
LAN
Level-2 LAN
A Partition Repair Capable Level-2 node / router
Level-1 tunnel through the Level-2 subdomain
P
Legend:
Management communication setup
...................................................................................................................................................................................................................................
4-30
Alcatel-Lucent - Proprietary
See notice on first page
365-312-807R7.2
Issue 4, May 2007
To Next Page
Loading...
