Changes

no edit summary
Line 4: Line 4:     
__TOC__
 
__TOC__
==2023.04.13 Changes to adding RMS devices==
     −
On April 18th, 2023 Teltonika's '''[[RMS|Remote Management System]]''' ('''[[RMS]]''') will receive an update that will change how Teltonika devices connect to RMS.
+
==2023.05.18 New mandatory connection IP addresses and ports==
 +
 
 +
On June 19th, 2023 Teltonika's '''[[RMS|Remote Management System]]''' ('''[[RMS]]''') will receive an update that will change how Teltonika devices connect to RMS.
    
{| class="wikitable"
 
{| class="wikitable"
Line 13: Line 14:  
|-
 
|-
 
| style="text-align: left; background: white;" |Change type
 
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Devices now have to reach an additional port to connect to RMS.<br>
+
| colspan="2" style="text-align: left; background: white;" |Devices now have to reach additional IP addresses and ports to connect to RMS.<br>
 
|-
 
|-
 
| style="width: 221px; text-align: left; background: white;" |Detailed description
 
| style="width: 221px; text-align: left; background: white;" |Detailed description
| style="width: 908px; text-align: left; background: white;" |Devices will additionally need to reach a new port for the device to successfully connect to the RMS platform. This port will be necessary every time the device attempts to connect to the RMS, e.g. after a reboot, a connection disruption, or any other reason why the device disconnected from the platform.
+
| style="width: 908px; text-align: left; background: white;" |Devices will additionally need to reach new IP addresses and ports for the device to connect to the system and have a stable RMS connection. These addresses and ports will be necessary every time a device attempts to connect to the RMS, e.g. after a reboot, a connection disruption, or any other reason why the device disconnected from the platform. These changes should not concern you in case you don't have any firewall rules to block IP addresses and ports that the firewall is not aware of.
    
Before the update, for the device to successfully connect to the RMS, it had to reach the IP address '''18.196.62.30''' and ports:
 
Before the update, for the device to successfully connect to the RMS, it had to reach the IP address '''18.196.62.30''' and ports:
Line 22: Line 23:  
* 15009
 
* 15009
 
* 15010
 
* 15010
 +
* 15011 (optional)
 +
 +
After the update - the list of required IP addresses are as follows:
 +
 +
* 18.196.62.30
 +
* '''3.77.70.198'''
 +
* '''3.69.112.66'''
 +
* '''35.157.156.54'''
 +
* '''18.157.218.160'''
 +
* '''3.77.251.245'''
 +
* '''3.78.70.211'''
 +
* '''18.158.123.134'''
   −
After the update - the same address '''18.196.62.30''' and ports:
+
All listed IP addresses will use the following ports:
 +
 
 +
* Device Access to RMS: 15009, 15010, 15011, '''15039''', '''15040''';
 +
* Maintenance ports: '''15041-15100'''
   −
* 15009
  −
* 15010
  −
* '''15011 (new)'''
   
|-
 
|-
 
| style="text-align: left; background: white;" |Change reasons
 
| style="text-align: left; background: white;" |Change reasons
 
| colspan="2" style="text-align: left; background: white;" |
 
| colspan="2" style="text-align: left; background: white;" |
RMS security improvements
+
RMS scalability and redundancy improvements
 +
|-
 +
| style="text-align: left; background: white;" |Change implementation date
 +
| colspan="2" style="text-align: left; background: white;" |June 19th, 2023
 +
|-
 +
|}
 +
{| class="wikitable"
 +
|+
 +
! colspan="3" style="text-align: left; background: white;" |Change impact
 +
|-
 +
| style="width: 221px; text-align: left; background: white;" |Risk assessment
 +
| colspan="2" style="width: 908px; text-align: left; background: white;" |Any solutions that whitelist certain IP addresses and ports in their private networks will now also need to allow communication via these new IP addresses and ports.
 +
|-
 +
|-
 +
| style="width: 221px; text-align: left; background: white;" |Suggested implementation plan
 +
| colspan="2" style="width: 908px; text-align: left; background: white;" |Please contact your sales representative concerning any issues in regard to these changes.
 +
|-
 +
|}
 +
 
 +
{| class="wikitable"
 +
|+
 +
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
 +
|-
 +
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification, Teltonika will presume that the fact of this change has been acknowledged and can implement the change as indicated above.
 +
|-
 +
|}
 +
 
 +
==2023.04.21 Additional secondary connection port==
 +
 
 +
On April 21st, 2023 Teltonika's '''[[RMS|Remote Management System]]''' ('''[[RMS]]''') has received an update that adds a secondary connection port to the RMS platform.
 +
 
 +
{| class="wikitable"
 +
|+
 +
! colspan="3" style="text-align: left; background: white;" |Change description
 +
|-
 +
| style="text-align: left; background: white;" |Change type
 +
| colspan="2" style="text-align: left; background: white;" |Port 15011 has begun being used as a secondary connection port to RMS.<br>
 +
|-
 +
| style="width: 221px; text-align: left; background: white;" |Detailed description
 +
| style="width: 908px; text-align: left; background: white;" |Port 15011 has begun being used as a secondary fallback for primary connection ports or for future maintenance purposes. As of this notification, the port currently remains optional, though as it increases platform stability and flexibility in cases of any platform downtime, it is highly recommended to have this port open or whitelisted in your device network.
 +
|-
 +
| style="text-align: left; background: white;" |Change reasons
 +
| colspan="2" style="text-align: left; background: white;" |RMS redundancy improvements
 
|-
 
|-
 
| style="text-align: left; background: white;" |Change implementation date
 
| style="text-align: left; background: white;" |Change implementation date
| colspan="2" style="text-align: left; background: white;" |April 18th, 2023
+
| colspan="2" style="text-align: left; background: white;" |April 21st, 2023
 
|-
 
|-
 
|}
 
|}
Line 42: Line 97:  
|-
 
|-
 
| style="width: 221px; text-align: left; background: white;" |Risk assessment
 
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Any solutions that whitelist certain IP addresses and ports in their private networks will now also need to allow communication via this new port - 15011.
+
| colspan="2" style="width: 908px; text-align: left; background: white;" |Any solutions that whitelist certain IP addresses and ports should also allow communication via this new port - 15011.
 
|-
 
|-
 
|-
 
|-
Line 57: Line 112:  
|-
 
|-
 
|}
 
|}
 +
 +
 +
==2023.04.13 Changes to adding RMS devices==
 +
 +
This change did not take place. This Product Change Notification is obsolete as of 2023.04.18.
     

Navigation menu