Maybe somebody could generate a 'how to' doc...
On Sat, Mar 19, 2011 at 11:42 AM, Claas Hilbrecht <
claas.hilbrecht+maillinglists.sipx...@linum.com> wrote:
> > I guess I'm not sure why a duplicate tftp server would be needed (unless
> > you are doing custom stuff... but then you should have a ba
> I guess I'm not sure why a duplicate tftp server would be needed (unless
> you are doing custom stuff... but then you should have a backup of the
> custom stuff). If the phones reboot and there's no TFTP server there
> they should retain their configurations.
E.g. a remote with a slow WAN link
True, but this box likely should have little else on it... really would
need to be custom for each customer...
On Thu, Mar 17, 2011 at 8:51 AM, wrote:
> Yep, true, but an "out-of-the-box" solution could be easier to
> maintain/less likely to be forgotten.
>
> Paul
>
> Michael Picher wrote on 1
Yep, true, but an "out-of-the-box" solution could be easier to
maintain/less likely to be forgotten.
Paul
Michael Picher wrote on 17-03-2011 13:34:39:
> You could just rsync that folder (/var/sipx to another box (funny
> how i say that without ever setting up rsync :-) )
> On Wed, Mar 16, 20
You could just rsync that folder (/var/sipx to another box (funny how i say
that without ever setting up rsync :-) )
On Wed, Mar 16, 2011 at 6:47 AM, wrote:
> It would be nice to have a secondary tftp server so that you could put a
> "slave" provisioning box in the DMZ for remote workers.
>
> Pa
It would be nice to have a secondary tftp server so that you could put a
"slave" provisioning box in the DMZ for remote workers.
Paul
Michael Picher wrote on 15-03-2011 20:41:23:
> I guess I'm not sure why a duplicate tftp server would be needed
> (unless you are doing custom stuff... but th
I guess I'm not sure why a duplicate tftp server would be needed (unless you
are doing custom stuff... but then you should have a backup of the custom
stuff). If the phones reboot and there's no TFTP server there they should
retain their configurations.
Plus, it's not like you're going to make c
[...]
> I think a "backup" tftp server on the secondary systems would be useful.
> This would be a good case of where a synced directory makes sense for
> fault tolerance. Perhaps you can open a jira/improvement request on this?
Ok, so this I the "normal" behaviour. I just want to make sure that
On Tue, Mar 15, 2011 at 9:34 AM, Claas Hilbrecht <
claas.hilbrecht+maillinglists.sipx...@linum.com> wrote:
> Hello,
>
> I try to setup a sipxecs cluster and I wonder if the tftp service is really
> handeled only on the primary node? On the secondary system the tftp root
> directory (/var/sipxdata/
Hello,
I try to setup a sipxecs cluster and I wonder if the tftp service is really
handeled only on the primary node? On the secondary system the tftp root
directory (/var/sipxdata/configserver/phone/profile/tftproot) is not synced
with the content from the primary server. But the /etc/dhcpd.co
10 matches
Mail list logo
