• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About asiawatcher

  • Rank
  1. I have tried all DSM versions and high availability has worked for me only on the old 5.2.5592 dsm, anyone has the same problem with me ? using supermicro pizza box atom servers
  2. asiawatcher

    DSM 6.2 Loader

    no its still there you install it from package center separately
  3. asiawatcher

    DSM 6.2 Loader

    high availability doesn't work on any of the ds918 loaders 1.03 or 1.04 with 6.2.1 or 6.2 does anyone know why ? while it sets it up ok then it cant find passive server at least on vmware only with 5.2.5592.2 high avail. with corresponding boot loader works cheers
  4. asiawatcher

    DSM 6.2 Loader

    seems i cannot create high availability cluster i get this error with both filesystems btrfs and ext4 using x2 vmware machines anyone else has the same problem ? cheers
  5. asiawatcher

    DSM 6.2 Loader

    s/n generator is dead how can i create s/n for a new machine i got ? cheers
  6. bare metal loader 1.01 works fine but high availability setup gives me error, it says i have to disable dhcp server while its already disabled and wont let me setup the high availability, the rest seem to work fine.
  7. You are right i must check that how do i add something to be run on boottime on xpenology ? Cheers
  8. using xpenology on x2 qnap's ts-459u work great better than production grade whoever uses qnaps like me only use 5.2-5592.2 update 4, later versions dont work i tried everything.
  9. solved the issue by adding this routing table route add -net netmask dev eth1:HA ip route flush cache login as: root root@cluster's password: BusyBox v1.16.1 (2015-06-29 18:21:52 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. cluster> ip route list default via dev eth1 dev eth0 proto kernel scope link src dev eth0 proto kernel scope link src dev eth1 scope link src dev eth1 scope link
  10. asterisk worked flawlessly while i had it on standalone function on the single nas only in cluster ip it seems to have a problem it again works flawlessly if i use the nas lan card ip, it only cant find asterisk if i use the redundant floating ip all other services such as dns radius mariadb etc work flawlessly with the floating ip only asterisk has problem the phones time out they cannot find the server if phone tries to connect to the floating ip but in the nas direct ip it connects great. This is beyond me really as both ips floating and the nas one are on the same machine whil
  11. so i have created a cluster between my x2 xpenology diskstations which works great except the fact that i CANNOT connect my extensions to the floating ip for asterisk, when i do it times out and does nothing while if i connect my extensions directly to the diskstation original ip (not the floating one) it works sql server dns server radius server etc all work fine with the floating ip except asterisk anyone has the same problem and/or a solution ? running 5.2-5592.2 update 4 xpenology cheers
  12. Hi there anyone tried the images of on dual core atom qnaps such as 459u-rp? Does it work without issues? Cheers