Building
A)Normal routing case (both network link sets available) Single Point Code
Link Set id 1
Link Set
Link Set id 0
SIUA
SIUB
Link Set id 2
STPA SSP/SCP
STPB
B) Routing under failure of network link set between SIUA and adjacent STP |
| |
Single Point Code |
| |
Link Set id 1 |
| |
|
| |
Link Set |
|
|
SIUA |
| SSP/SCP |
|
| |
Link Set id 0 |
| |
SIUB |
| |
| Link Set id 2 | STPB |
Transmit Traffic from SIUA |
| |
|
| |
Transmit Traffic from SIUB |
|
|
| Figure 9. Transmit Routing Through Mated STPs |
Table 1 compares the advantages and disadvantages of these methods.
Table 1. Comparison of a Straight Link Configuration vs. a Crossed Link Configuration
Comparison Subject | Straight Configuration | Crossed Configuration |
|
|
|
Load sharing | - | + |
| STPA can only load share traffic | Each STP can load share between the two SIUs, |
| for SIUA and | optimizing the resource utilization |
|
|
|
+ | - | |
failure | SIUA can rely on SIUB to send | When an SIU loses its |
| outgoing traffic upon failure of its | application must activate circuit groups on the |
| entire | surviving SIU (for |
|
|
|
- | + | |
dimensioning | Need to allocate 1/4 of all | Need to allocate a single link, maximizing the |
| network facing links (e.g., 16 | number of |
| network facing links and four | links and one |
| there are two single points of failure in the system. | |
|
| For best resilience, the |
|
| two links spread across two cards in each SIU. |
|
|
|
9