Scannex ip.buffer, Руководство пользователя

Страница: 58 / 152

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
8.2.16. Cloud Server
The central Cloud Server feature of the ip.buffer allows central management of all
configured ip.buffers with a standard web server. This is particularly useful for 'Managed
Services' deployments where out-bound web browsing is allowed on customer sites.
The ip.buffer issues a requests (either with http or https) to the server. The server can
respond and deliver:
•
Lua script updates
•
Firmware upgrades
•
Configuration changes
•
Requests for diagnostic dumps
•
Requests for log files
•
Time synchronisation
•
Reboot requests.
•
Data to be injected in the Source channel of the ip.buffer
Firmware 2.93 adds two additional Cloud Servers that can be used for data
and alerts. However, Cloud Server #1 is the only one that handles the central
management.
Cloud Server #1 (global)
Interface
“
LAN only
” – will connect only using Ethernet
“
Modem only
” – will always use PPP
“
LAN then Modem
” – will try to use Ethernet. If that fails it will
try PPP
“
Modem then LAN
” – will try to use PPP and if that fails it will
try Ethernet.
For the Modem dial-out setup see section 8.2.5 [LAN only]
URL
The full URL. This should be in the form “
http[s]://
[user[:pass]@]server[:port]/directory/resour
ce
”.
You can also specify a choice of https / http by using
“
http?://
” or “
http*://
” as the URL
e.g. “https://192.168.0.240/private/update.php”
e.g. “https://main:pass@192.168.0.241/ipbuffer/get.asp”
e.g. “http://main@192.168.0.241:8081/ipbuffer.php”
[blank]
Managed by “
Cloud Server #1 (default)
” - the server specified by the
URL above will manage the ip.buffer
“
Scannex Support Server
” - the ip.buffer will be managed
Page 54
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
8.2.16. Cloud Server
The central Cloud Server feature of the ip.buffer allows central management of all
configured ip.buffers with a standard web server. This is particularly useful for 'Managed
Services' deployments where out-bound web browsing is allowed on customer sites.
The ip.buffer issues a requests (either with http or https) to the server. The server can
respond and deliver:
•
Lua script updates
•
Firmware upgrades
•
Configuration changes
•
Requests for diagnostic dumps
•
Requests for log files
•
Time synchronisation
•
Reboot requests.
•
Data to be injected in the Source channel of the ip.buffer
Firmware 2.93 adds two additional Cloud Servers that can be used for data
and alerts. However, Cloud Server #1 is the only one that handles the central
management.
Cloud Server #1 (global)
Interface
“
LAN only
” – will connect only using Ethernet
“
Modem only
” – will always use PPP
“
LAN then Modem
” – will try to use Ethernet. If that fails it will
try PPP
“
Modem then LAN
” – will try to use PPP and if that fails it will
try Ethernet.
For the Modem dial-out setup see section 8.2.5 [LAN only]
URL
The full URL. This should be in the form “
http[s]://
[user[:pass]@]server[:port]/directory/resour
ce
”.
You can also specify a choice of https / http by using
“
http?://
” or “
http*://
” as the URL
e.g. “https://192.168.0.240/private/update.php”
e.g. “https://main:pass@192.168.0.241/ipbuffer/get.asp”
e.g. “http://main@192.168.0.241:8081/ipbuffer.php”
[blank]
Managed by “
Cloud Server #1 (default)
” - the server specified by the
URL above will manage the ip.buffer
“
Scannex Support Server
” - the ip.buffer will be managed
Page 54