similar to: No subject

I've been evaluating Asterisk for a while, and things seem to be going very well. The issue of redundancy and automatic fail-over is now on my mind. I searched the archives and googled for solutions, but didn't really come up with much. We'll be using queues (modified), which precludes some of the standard redundancy solutions, since the queue needs to know all the agents

Hi, I'm wondering what the best option to obtain a high availability asterisk server is. I currently use a TE410P (4 x E1) card. I'm thinking of 2 different solutions: - 2 servers configured with Heartbeat + DRBD (drbd mainly for voicemail....) and the E1 span plugged to the 2 servers (with a TE410P in each server). - 2 servers configures with Heartbeat + DRBD with the E1 span hooked

Hi, I'm using heartbeat as a failover for my asterisk server. on the active server 1 i have 10.10.10.1 eth0 10.10.10.3 secondary eth0 asterisk listens to the secondary ip, so that if server 1 fails, server 2 will then get that IP. so if server 1 fails, server 2 will have the IP 10.10.10.2 eth0 10.10.10.3 secondary eth0 problem is i have to bind asterisk to the secondary IP if dont, i

Hi List, I've setup 2 openldap servers in n-way multimaster replication mode in a test environment, both run centos 6.2, this works well but now i'm trying to make these 2 servers failover using heartbeat. i've got no experience with heartbeat (or setting up clusters in general) however from what i understand heartbeat starts/stops the service if the server has the virtual IP

I'm running a pair of squids as an internal cache for some intermediate data used by a web server farm and currently doing failover by going through an F5 bigip. However, I'd like to avoid the bigip and use heartbeat since there are only two machines. I don't need to sync any content since it is a fast-changing cache and either machine can handle everything. Is it possible to

This is a dialpaln issue. I solved the same problem recently. For 4 digit extensions you need to append the dialplan statement in the sip.cfg configuration file as follows <digitmap dialplan.digitmap="[2-9]11|0T|011xxx.T|[0-1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|[2 -9]xxxT|1xxxT" dialplan.digitmap.timeOut="3"/> Michael > I am not sure what I did but blind transfers do not

Hi, I''ve got a question regarding failover. I''ve set up Xen and DRBD with the versions packaged for CentOS 5.4. Live migration of the domU''s is working between the two xen nodes quite happliy. Each domU has two LVM LVs associated with it, partitioned as swp and root. DRBD is configured to just sync the LV containing the root partition, not swp. I''ve seen

Hi, I've setup two server A + B (debian etch) with drbd + heartbeat in active/passive mode. If the primary server A fails, the shared storage is mounted on B, the virtual ip A-vip moves to the new primary B and samba is started by heartbeat. This works well, but I'm not sure which samba files should be identical on both server. Both have a dedicated machine account at the moment.

Hello, While working on heartbeat/pacemaker for a web service stored on drbd, I've thought what I've learnt could also be applied to samba in order to build a fault tolerant file server in our domain. While digging samba's doc, I've found that CTDB could also fulfill the need and is maybe better suited as it's samba-related. But on the other hand, I'd appreciate to begin

Hello, Assuming we have two (low traffic) servers (on different data centers) replicated using dsync, what is the best way to automatically direct users to the main server when it is up and to the redundant one when the main server is down? Using DNS? I've seen that DNS-based failover has generally issues (for example:

Hello, Could someone experienced suggest good solution for failover advanced router ? The router for which I need redundancy is quite complex: 1) has 5 interfaces 2) uses the same network and the other network IP aliases on some interfaces 3) uses bunch of policy routing rules 4) uses proxyarp feature on some interfaces 5) uses complex iptables setup [propably not important in this

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I think I stumbled on at least two bugs in the CentOS 7.2 pacemaker package, though I'm not quite sure if or where to report it. I'm using the following package to set up a 2-node active/passive cluster: [root at clnode1 ~]# rpm -q pacemaker pacemaker-1.1.13-10.el7_2.4.x86_64 The installation is up-to-date on both nodes as of the

Forgive me if I sent this twice, I think I hit the "send" button by mistake. --- Bj�rn Tore Svinningen <bt@erter.org> wrote: > I''ve seen your post on xen''s forum about running Xen ontop of openssi. > > Have you got''en any further on this idea ? Had the same idea myselves, > but it seems all posts I find end nowhere. Hm, I thought this

Hello, I have two EC2 instances and I would like to setup some sort of failover strategy for them. They currently act as load balancers, forwarding layer 7 traffic using haproxy and stunnel to other EC2 instances. One of these load balancers currently has an elastic IP assigned with an A record pointing to it. What I'm trying to achieve is to remap this elastic IP in the eventuality of an

I was just curious to what your redundancy solution is. I have considered many options, so I thought I would share and get an idea for what others are doing. My setup is two different locations with a 10MB WLAN fiber link between the two. Each location has it's own PRI as well. I have considered and tested many options this last year or so. 1) Using hearbeat and drbd to monitor the

Hello, I've found GlusterFS to be an interesting project. Not so much experience of it (although from similar usecases with DRBD+NFS setups) so I setup some testcase to try out failover and recovery. For this I have a setup with two glusterfs servers (each is a VM) and one client (also a VM). I'm using GlusterFS 3.4 btw. The servers manages a gluster volume created as: gluster volume

I have searched your FAQ''s and read the documentation on your site as well as googling. I am not able to figure this out. If you have any ideas can you please help. I am using the linux-ha failover with redundant firewalls. As part of the function of the linux-ha software consists a service called heartbeat which is a connection from each failover node through a serial cable or ethernet.

First, Something seems to be wrong with the list. I'm not the only person who has expressed seeing their messages either arrive late, or not at all. With that out of the way.. Is anyone aware of any type of failover device for PRI on asterisk? I've found the ISDNGuard, however it is currently not made in the U.S., nor does it run on U.S. power. Is anyone aware of a device that will

Hi, I have one physical server (server1 - CentOS 4) and one vmware (server2 - CentOS running in a VM under Windows 2003). I'm running PHP/MySQL webapps on it. I want to be sure there is a failover, but I don't really need load balancing for now. I run php/mysql/apache with the binaries that comes with CentOS 4. I have installed heartbeat on both and set MySQL replication so that

I am sorry for the long *involved* post, however we are at wits end and advice would be greatly appreciated. Background: We have three servers in this example. Two of the servers (we will call Server A & B) each have a 2.7T raid 5 array that is mirrored with DRBD and monitored for failover with Heartbeat. NFS is running and exporting the array on Heartbeats virtual IP. "Server C"