Actions

High Availability Overview: Difference between revisions

(re-arrange links)
m (formatting)
Line 3: Line 3:
# First and foremost, to recover from a system failure to minimize the system down time or instability as much as possible. This is achieve with a fault tolerant and redundancy architecture.
# First and foremost, to recover from a system failure to minimize the system down time or instability as much as possible. This is achieve with a fault tolerant and redundancy architecture.
# Secondly, to keep active calls open after a fail-over whenever possible.
# Secondly, to keep active calls open after a fail-over whenever possible.


'''Important''':[[Tmedia]] high availability features are described [[Redundancy_&_High_Availability|here]]
'''Important''':[[Tmedia]] high availability features are described [[Redundancy_&_High_Availability|here]]


== TelcoBridges High Availability ==
== TelcoBridges High Availability ==


TelcoBridges High Availability should be seen as a collection of high availability and redundancy features instead of one single feature. This means that customer can go as little or as far as they want to create a high availability system.
TelcoBridges High Availability should be seen as a collection of high availability and redundancy features instead of one single feature. This means that customer can go as little or as far as they want to create a high availability system.


== Definitions ==
== Definitions ==
Line 37: Line 40:
*[[High Availability:Hardware:Tdm Interfaces|Tdm Interfaces]] (OC3/STM-1 APS){{Check_X_Mark| y}}
*[[High Availability:Hardware:Tdm Interfaces|Tdm Interfaces]] (OC3/STM-1 APS){{Check_X_Mark| y}}
*[[High Availability:Hardware:Clocking|Clocking]] (Multiple clock sources){{Check_X_Mark| n}}
*[[High Availability:Hardware:Clocking|Clocking]] (Multiple clock sources){{Check_X_Mark| n}}


==== TelcoBridges Hardware HA Product Checklist  ====
==== TelcoBridges Hardware HA Product Checklist  ====
Line 77: Line 81:
|}
|}


<br>


=== Software Features ===
=== Software Features ===
Line 83: Line 86:
*[[High_Availability:Software:CDR | CDR]]{{Check_X_Mark| y}}
*[[High_Availability:Software:CDR | CDR]]{{Check_X_Mark| y}}
*[[High_Availability:Software:Configuration_Database | Configuration Database]]{{Check_X_Mark| y}}
*[[High_Availability:Software:Configuration_Database | Configuration Database]]{{Check_X_Mark| y}}
*Signaling Stack{{Check_X_Mark| n}}
*Signaling Stack{{Check_X_Mark| y}}
**[[High_Availability:Software:Signaling_Stack:CAS|CAS]]
**[[High_Availability:Software:Signaling_Stack:CAS|CAS]]
**[[High_Availability:Software:Signaling_Stack:ISDN|ISDN]]
**[[High_Availability:Software:Signaling_Stack:ISDN|ISDN]]

Revision as of 10:49, 15 February 2011

This article will describe the TelcoBridges Tdev High Availability feature. The hardware and software are design with the following 2 goals in mind:

  1. First and foremost, to recover from a system failure to minimize the system down time or instability as much as possible. This is achieve with a fault tolerant and redundancy architecture.
  2. Secondly, to keep active calls open after a fail-over whenever possible.


Important:Tmedia high availability features are described here


TelcoBridges High Availability

TelcoBridges High Availability should be seen as a collection of high availability and redundancy features instead of one single feature. This means that customer can go as little or as far as they want to create a high availability system.


Definitions

Here is a list of terms used in the description of the high availability features:


High Availability Features

Hardware High Availability Features

| Y | YES

| y

| yes = YesY | N | NO | n | no = NoN | N/A }}

  • Networking {{#switch: n

| Y | YES

| y

| yes = YesY | N | NO | n | no = NoN | N/A }}

| Y | YES

| y

| yes = YesY | N | NO | n | no = NoN | N/A }}

| Y | YES

| y

| yes = YesY | N | NO | n | no = NoN | N/A }}

| Y | YES

| y

| yes = YesY | N | NO | n | no = NoN | N/A }}

  • Clocking (Multiple clock sources){{#switch: n

| Y | YES

| y

| yes = YesY | N | NO | n | no = NoN | N/A }}


TelcoBridges Hardware HA Product Checklist

This checklist provides a quick overview of each Tdev models and their high availability support

Products Hardware High Availability Features
Dual Power Supply Control Network Redundancy Dual Voip Network Host Redundancy
TMP800 {{#switch: n Y YES y yes = YesY N NO n no = NoN N/A

}}

{{#switch: n Y YES y yes = YesY N NO n no = NoN N/A

}}

{{#switch: n Y YES y yes = YesY N NO n no = NoN N/A

}}

{{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}}

TMP5900 {{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}}

{{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}}

{{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}}

{{#switch: n Y YES y yes = YesY N NO n no = NoN N/A

}}

TMP6400 {{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}} (with 2 U)

{{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}}

{{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}}

{{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}}

TMP7900 {{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}}

{{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}}

{{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}}

{{#switch: Y Y YES y yes = YesY N NO n no = NoN N/A

}}


Software Features

| Y | YES

| y

| yes = YesY | N | NO | n | no = NoN | N/A }}

| Y | YES

| y

| yes = YesY | N | NO | n | no = NoN | N/A }}

  • Signaling Stack{{#switch: y

| Y | YES

| y

| yes = YesY | N | NO | n | no = NoN | N/A }}

| Y | YES

| y

| yes = YesY | N | NO | n | no = NoN | N/A }}


Installation, Maintenance and Provisioning

This section will show how to install, upgrade and configure a high availability system.

First, we will look at the software installation and provisioning (Host redundancy).