High Availability:Software:Signaling Stack:CAS
From TBwiki
(Difference between revisions)
(Creation) |
(replace tmedia with tdev) |
||
| (One intermediate revision by one user not shown) | |||
| Line 1: | Line 1: | ||
== High Availability == | == High Availability == | ||
| − | The [[CAS]] protocol doesn't have an innate high availability feature. The only way to increase the reliability of a system using [[CAS]] is to mix the stacks between the provider and the | + | === Live Reconfiguration === |
| + | |||
| + | With [[Toolpack]], it is possible to add/modify/remove any [[CAS]] stacks without needing to stop the whole system. | ||
| + | |||
| + | === Redundancy === | ||
| + | |||
| + | The [[CAS]] protocol doesn't have an innate high availability feature. The only way to increase the reliability of a system using [[CAS]] is to mix the stacks between the provider and the [[Tdev]] hardware, when available. | ||
Here is an example: | Here is an example: | ||
[[Image:Cas_Ha_Distribution.png|widthpx|]] | [[Image:Cas_Ha_Distribution.png|widthpx|]] | ||
Latest revision as of 09:47, 15 February 2011
High Availability
Live Reconfiguration
With Toolpack, it is possible to add/modify/remove any CAS stacks without needing to stop the whole system.
Redundancy
The CAS protocol doesn't have an innate high availability feature. The only way to increase the reliability of a system using CAS is to mix the stacks between the provider and the Tdev hardware, when available.
Here is an example:
