How much bandwith does a cloud managed device needs to connect to Cirrus ?

Topic

How much bandwidth does a cloud managed Stellar AP or OmniSwitch needs to register and securely maintain contact with OmniVista Cirrus and provide information to the Dashboard?

I mean here application and user statistics, configuration change, etc.

Please note that I’m looking for pure control plane bandwidth: this doesn’t have to include firmware update, configuration backup or other particular operating conditions.

Date
05.04.2018
answers
2
views
31
Author
Asked by klentil

Answers

Thanks for the feedback! it helps. Nether the less it would be interesting to know what are the requirements per device. for example, In a deployment using a business VDSL connection rated at 15 MB/S Downlink and 700Kb uplink, am I still OK with a 1 or 2 cloud managed AP and a switch ?

Date
05.04.2018
Author
Asked by klentil
Add Comment
Vote
Comments
<p>Khadif,</p> <p>Considering the amount of data currently exchanged, this should fit comfortably.</p>
<p>Sorry for fat fingering your name, KhadiR. Oops.</p>

I haven’t seen per-device bandwidth requirements, but this information below is extracted from the prerequisites OVC page (http://www.ovcirrus.com/direct/getting_started/getting_started_subscription.html#device_prerequisites):
To enable statistics data transfer, status queries, configuration commands, and other requests/responses between devices and OmniVista Cirrus, a minimum of 1 Mbps end-to-end network throughput is recommended between the customer premise and the OmniVista Cirrus hosting infrastructure.

Date
05.04.2018
Author
Asked by sherifshalaby
Add Comment
Vote
Comments
<p>Bandwidth Requirements </p> <p>For Onboarding<br /> For basic onboarding of devices and connection to the OmniVista Cirrus Server, a minimum of 10 kbps end-to-end network throughput is recommended between the customer premise and the OmniVista Cirrus hosting infrastructure. </p> <p>For Advanced Management<br /> To enable statistics data transfer, status queries, configuration commands, and other requests/responses between devices and OmniVista Cirrus, a minimum of 512 kbps end-to-end network throughput is recommended between the customer premise and the OmniVista Cirrus hosting infrastructure.</p> <p>For Proxy Requirements<br /> If a device is accessing the Internet via an HTTP/HTTPs proxy, the proxy server must be specified in DHCP Option 43, Sub-option 129 (Server) and Sub-Option 130 (Port). The server may be specified in 1 of 2 formats: 1) “URL=http://server.domain”, or 2) “IP-address=8.8.8.8”. The port is specified as a number (8080). </p>