What is ClusterNet? Components of ClusterNet ClusterNet in TRANSip What should I do before deploying ClusterNet?

What is ClusterNet?

Often, it is desirable to have switching assets in different geographic locations. This may be due to geographically dispersed office facilities, the size of the facilities, security concerns, or even something as simple as cable length. Generally, this is accomplished via trunking between two distinct switches. Traditional signaling protocols such as MF, ISDN and even SS7 have limited capabilities for conveying information between the switches that are intended to share information about operations and maintenance, billing record collection and host remote applications.

Using REDCOM’s ClusterNet™ technology, multiple locations equipped with compatible REDCOM equipment behave as a single, integrated system. This approach allows you to increase the manageability and survivability of the entire system.

Components of ClusterNet

ClusterNet technology needs two separate paths to function properly:

  1. Data Path (Inter-Cluster Link)
  2. Voice Path (Cross Office Highway)

The data path carries information about the status of the switches including the subscriber status, trunk status, maintenance notes and any other information that can be expected from a single system. The voice path carries the voice between two clusters to make both systems work as a single unit.

clusternet.jpg

ClusterNet in TRANSip

Traditionally, the data channel has been supplied over DS0 channels if the switches were geographically separated, and supplied over Ethernet if the switches were co-located. In both cases, the voice channel was provisioned over T1 or E1 trunks.

TRANSip technology allows the use of the IP layer for ClusterNet connectivity. All of the messages (including data and voice paths) can be carried over the IP network, forming a ClusterNet system. The use of the IP layer saves bandwidth because dedicated DS0 channels are no longer required and the information is sent when it is generated.

The chart below outlines the possible ClusterNet operations between REDCOM products.

 

HDX

SLICE

SLICE 2100

SLICE IP

HDX

TDM & IP

TDM

TDM & IP

IP

SLICE

TDM

TDM

TDM

X

SLICE 2100

TDM & IP

TDM

TDM & IP

IP

SLICE IP

IP

X

IP

IP

What should I do before deploying ClusterNet?

REDCOM’s ClusterNet allows a single point of administration and operations for separate switching systems. In order to benefit from ClusterNet, one should be aware of the following:

  • All equipment must have the same software version
  • The Cluster feature must be enabled
  • There should be enough resources for voice path (either TDM trunks or MSC board)
  • The transmission delay between clusters needs to be considered

The REDCOM Customer Service Group is ready to help you with technical questions. They can be reached from 8am to 5pm EST at 1-585-924-6500 and by e-mail at service@redcom.com

 
^ Back to Top