/
Upgrade option with 2 servers

Upgrade option with 2 servers

Owned by Sonja Malavašič (Unlicensed)
Last updated: Sept 02, 2024
3 min read

First, we get the list of HW equipment available on the property:

  • Find out if the old MW is a physical server, not virtual. (for virtual, it is easier to create new instance)

  • Client can provide a new separate server for the new MW (virtual or physical)

  • If they do have other GW servers with backup MW installed, we could redirect devices there and client reinstalls MW server in peace. We did that on some projects.

  • Check if client has the HW that we still support (server and devices), which means they only need SW upgrade and will work.

  • Check for other integrations: this project has PMS and queuing system integration. It will work on new server.

 

 

What we can do?

They have old server from 2017 where stbs are connecting with the iptv.nevronitv.si link. In the new MW stbs are connecting with the stv.base.ntv. Check if the local network blocks those links.

 

Option 1: We will add redirection in the old MW so new link will be redirected to new MW server. This means new stbs will be connecting to new server, the old will stay on the old.

Benefits: Client can upgrade stbs in peace, no need to upgrade all 400x or more stbs in one day. No serious maintenance downtime. They upgrade the device when the room is free of guests.

Steps:

  1. Prepare the new server - set network settings, copy database.

  2. In old MW server under /etc/named add a new .zone file. We advise duplicating the file and copying the content in it. This way, the rights on the file stays the same. If file exist, change the IP, and check that no old stb uses this base.ntv link.

base.ntv.zone file:

$TTL 3600 ; 1 hour base.ntv. IN SOA ns1.nevron.si. postmaster.nevron.si. ( 2007122042 ; Serial 10800 ; Refresh 3600 ; Retry 604800 ; Expire 86400 ; Minimum TTL ) ; NS Records IN NS ns1.nevron.si. IN NS ns2.nevron.si. ; MX Records IN MX 20 mx.nevron.si. ; A Records @ IN A 192.168.200.249 database IN CNAME @ iptv IN CNAME @ manager IN CNAME @ rest IN CNAME @ stv IN CNAME @

 

3. In the file /etc/named.conf add this new zone file link. If you edited IP in the previous step, you can skip this.

zone "base.ntv" { type master; file "base.ntv.zone"; };

 

4. Restart the named service after the changes

Run a command in terminal:

systemctl restart named

 

5. Disable named and DHCP on the new server. Only one can be in the network.

systemctl stop named systemctl disable named systemctl stop dhcpd systemctl disable dhcpd

 

6. Upgrade stb with the new FW where webplayer apk is included. Ask Support@nevron.eu for instructions.

7. On the new server set the setting that each device that it connects, will grab a homepage link http://stv.base.ntv

Go to file: /opt/nevron/rover/conf/stb.conf

Add the first line for the homepage. Here, it’s possible to add more rover settings if needed. An article about Rover tool is here. In case FW doesn’t support grabbing this link, you set it manually on stb with a rstb (rover tool).

{ "conf:persist.nevron.webp.home": "http://stv.base.ntv", "#gfx": "1280x720", "#prop:persist.led.level": 1, "#timezone": "Europe/Ljubljana", "#mute": false, "#param": "is comment" }

Manual command for all STBs at once:

rstb all set conf:persist.nevron.webp.home http://stv.base.ntv

Manual command for single STB with IP (or MAC) 192.168.200.10:

rstb 192.168.200.10 set conf:persist.nevron.webp.home http://stv.base.ntv

Restart rover service:

systemctl restart rovergw

 

8. Check if STBS are redirected properly. On the new server in a file: /var/www/portal_base/data/domains.json check if base domain is redirected to stv.base.ntv (at the bottom of the file). It shouldn’t be redirected to iptv.nevronitv.si (see line 19 below)

//Base portal -> default filter (return iptv defaults for all requests). // //Notice: //Do not change this filter as in other case new STBs/SmartTVs wont be able to establish the first connection. "title": "base", "rule": { "ip": { "condition": "*", //* = trigger on all IP4s "exact": {} }, "mac": { "condition": "*", //* = trigger on all MACs "exact": {} } }, "host": "http://stv.base.ntv", "rsync": { "images": "images_base", //RSync name for images. "videosds": "videosds_base" //RSync name for SD videos. } } ]

9. Now test on stb if you get new stb connecting to the new server. On the new MW we have new GUI so it’s easy to see that it went to the new server. Or change the channel name on new server.

Always test also rebooting old stb to see if it still works on old MW.

 

10. If that work, then start slowly upgrading the stbs. One by one or multiple together.

Related content