Edgecore Networks Corporation

END USER LICENSE AGREEMENT

LEASE READ THIS END USER LICENSE AGREEMENT (THE “AGREEMENT”) CAREFULLY BEFORE USING SOFTWARE FROM EDGECORE. BY USING EDGECORE SOFTWARE (THE “SOFTWARE”), YOU SIGNIFY YOUR ASSENT TO AND ACCEPTANCE OF THIS END USER LICENSE AGREEMENT AND ACKNOWLEDGE YOU HAVE READ AND UNDERSTAND THE TERMS. AN INDIVIDUAL ACTING ON BEHALF OF AN ENTITY REPRESENTS THAT HE OR SHE HAS THE AUTHORITY TO ENTER INTO THIS END USER LICENSE AGREEMENT ON BEHALF OF THAT ENTITY. IF YOU DO NOT ACCEPT THE TERMS OF THIS AGREEMENT, THEN YOU MUST NOT USE THE SOFTWARE. THIS END USER LICENSE AGREEMENT DOES NOT PROVIDE ANY RIGHTS TO EDGECORE SERVICES SUCH AS SOFTWARE MAINTENANCE, UPGRADES OR SUPPORT. PLEASE REVIEW YOUR SERVICE OR SUBSCRIPTION AGREEMENT(S) THAT YOU MAY HAVE WITH EDGECORE OR OTHER AUTHORIZED EDGECORE SERVICE PROVIDERS REGARDING SERVICES AND ASSOCIATED PAYMENTS.

1) Trademarks:

Edgecore, regardless of capital or lower case, is a registered trademark of Edgecore Networks Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners. Protected trademarks are not marked as such herein. This does not mean, however that they may be used freely.

2) License grant:

"SOFTWARE” means the software contained in this package and any subsequent versions or upgrades received as a result of having down loaded this package. Edgecore grants YOU a license to use one copy of the version of this SOFTWARE only on a single Edgecore hardware. "YOU" or “BUYER” means a company, an entity or an individual taken as the original purchaser of the SOFTWARE. "USE" means storing, loading, installing, executing or displaying the SOFTWARE. YOU may not modify the SOFTWARE or disable any licensing or control features of the SOFTWARE except as an intended part of the SOFTWARE's programming features. This license is not transferable to any other company, entity or individual. YOU may not publish any registration information (serial numbers, registration keys, etc.) or pass it to any other company, entity or individual. BUYER may not electronically transfer the program from one Edgecore hardware to the other devices over any type of network. BUYER may not distribute copies of the SOFTWARE or the accompanying documentation to others either for a fee or without charge. BUYER may not modify or translate the SOFTWARE or documentation. BUYER may not disassemble the SOFTWARE or allow it to be disassembled into its constituent source code. BUYER's use of the SOFTWARE indicates his/her acceptance of these terms and conditions. If BUYER does not agree to these conditions, return the distribution media, documentation, and associated materials to the vendor from whom the SOFTWARE was obtained, and erase the SOFTWARE from any and all storage devices upon which it may have been installed.

3) Open Source Software:

Certain components of the SOFTWARE may incorporate “open source” software. To the extent required by an Open Source License that applies to Open Source Software included in or provided with the Software: (a) the terms of such Open Source License will apply to such Open Source Software instead of the terms of the license grant in this Agreement; and (b) any restrictions prohibited by such Open Source License that are contained in this Agreement will not apply to such Open Source Software. Notwithstanding the foregoing, SONiC is an open source Network Operating System (NOS) project and all the open source components and links to associated source code are available on the github at https://github.com/Azure/SONiC. The github will continuously get updated as the community adds new open source components to SONiC. Details are available on the Edgecore Networks Corporation, website (www.edge-core.com).

4) Ownership and Copyright:

The SOFTWARE is owned and copyrighted by Edgecore or Edgecore’s licensors. Your license confers no title or ownership of the SOFTWARE and should not be construed as a sale of any rights for the SOFTWARE. YOU acknowledge that the title and full ownership rights to the SOFTWARE will remain the exclusive property of Edgecore or Edgecore’s licensors and YOU will not acquire any rights to the SOFTWARE except as expressly set forth in this license. YOU agree that any copies of the SOFTWARE will contain the same proprietary notices which appear on and in the SOFTWARE.

5) Unauthorized Use:

YOU affirm that YOU will not attempt to reverse compile, modify, translate, or disassemble the SOFTWARE in whole or in part. It is strictly prohibited for YOU to use copy, rent, lease, sell, modify, decompile, disassemble, otherwise reverse engineer, or transfer the SOFTWARE except as provided in this Agreement. Any such unauthorized use shall result in immediate and automatic termination of this Agreement.

6) No Warranties:

This SOFTWARE is provided on an "AS IS" basis. Edgecore disclaims all warranties relating to this SOFTWARE, whether expressed or implied, including but not limited to any implied warranties of merchantability, non-infringement or fitness for a particular purpose. Neither Edgecore nor anyone else who has been involved in the creation, production, or delivery of this SOFTWARE shall be liable for any indirect, consequential, or incidental damages arising out of the use or inability to use such SOFTWARE, even if Edgecore has been advised of the possibility of such damages or claims. The person using the SOFTWARE bears all risk as to the quality and performance of the SOFTWARE. Some jurisdictions may not allow the exclusion of implied warranties or limitations on how long an implied warranty may last, or the exclusion or limitation of incidental or consequential damages, so that the above given limitations or exclusions may not apply to YOU.

7) Limited Liability:

BUYER acknowledges that the SOFTWARE may not be free from defects and may not satisfy all of BUYER's needs. Edgecore warrants all media on which the SOFTWARE is distributed for 90 days to be free from defects in materials and workmanship under normal use. The SOFTWARE and any accompanying written materials are licensed "AS IS". BUYER's exclusive remedy during the warranty period shall consist of replacement of distribution media if determined to be faulty. In no event will Edgecore be liable for direct, indirect, incidental or consequential damage or damages resulting from loss of use, or loss of anticipated profits resulting from any defect in the program, even if it has been advised of the possibility of such damage. In no event will Edgecore's liability for any claim, whether in contract, tort or any other theory of liability, exceed the aggregate amount paid by YOU for the SOFTWARE.

8) Compliance with laws:

Each party agrees to comply with all applicable laws, rules and regulations in connection with its activities under this Agreement. Without limiting the foregoing, YOU acknowledge and agrees that the Software, including technical data, is subject to United States export control laws, including the United States Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. End User agrees to comply strictly with all such regulations and acknowledges that End User has the responsibility to obtain licenses to export, re-export, or import the SOFTWARE.

9) Termination:

Without prejudice to any other rights, Edgecore may immediately terminate this license without notice if YOU fail to comply with any terms and conditions of this Agreement. In such event, YOU must: 1. Cease all use of the SOFTWARE; 2. Destroy or return to Edgecore the original and all copies of the SOFTWARE; and 3. Delete the SOFTWARE from all Edgecore hardware on which it was resident. All disclaimers of warranties and limitation of liability set forth in this Agreement shall survive termination of this Agreement.

10) Governing Law and Jurisdiction:

This Agreement shall be governed by the laws of California, USA, excluding its conflict of law provisions. To the extent permitted by law, any Dispute any dispute arising out of or relating to this Agreement shall be subject to the exclusive jurisdiction of the state and federal courts located in Orange County, California, USA.

11) General:

This Agreement represents the complete agreement between YOU and Edgecore relating to this license for the SOFTWARE and supersedes all prior agreements, communications, proposals and representations between the parties and prevails over any conflicting or additional terms of any quote, order, acknowledgement or similar communication. This Agreement may only be modified by a written document signed by both parties. If any provision of this Agreement is held by a court of competent jurisdiction to be contrary to law that provision will be enforced to the maximum extent permissible and the remaining provisions of this Agreement will remain in full force and effect. All rights not expressly granted herein are reserved to Edgecore Networks Corporation.

Device Registration and Configuration Follow

mark_chen 陳奕勳

August 17, 2020 15:09
Updated

Registration

A new device can easily be added to a site by inputting (or scanning) the serial number and MAC address of the device into the “Add device” form from the Cloud.

The device’s “site-level configuration inheritance” behavior, mentioned previously must also be selected.

Devices that operate as a backhaul, or any device that the user wishes to be individually configured, should have its site-level configuration inheritance property set to “off”.

Devices that might share common settings with other similar devices, such as the MetroLinq Omni or most Wi-Fi devices, should have “inherit site-level configuration settings” to “on”.

Configuration on the cloud is very flexible - device-level configuration overrides can easily be setup if the need is to inherit only a subset of site-level settings.

Tip: A device’s serial number and MAC address can be found on its product box, or on the main dashboard page of the local web configuration UI.

Here’s the typical process that occurs after a device is registered:

Once a device is added to a site, it goes into the “Pending Registration” state. At this point, the Cloud is waiting for the device to call in for the first time to fetch the credentials it will use for future communication with the Cloud.
After the device makes its initial connection to the Cloud and completes registration, the Cloud checks to see if the device’s site has the “auto firmware upgrade” setting enabled. If so, it checks the device’s firmware to see if it needs to be upgraded, and if so, it creates an auto firmware upgrade task for the device.
After the device is upgraded (or if firmware upgrade is skipped), the device will send up its current configuration to the Cloud. This generates a “Received Config” task, the details of which can be viewed on the device’s Activity page. The Cloud must collect the device’s initial configuration, as well as firmware version, before it can push any new configurations down to the device.
Next, the cloud will merge any site-level configuration settings (assuming inheritance is enabled) with the device’s configuration, and create a “Change Config” task to push the new settings down to the device. If site-inheritance is enabled, the device’s running configuration will be completely replaced with the configuration seen on the device’s Configuration page on the Cloud. Any configuration settings changed via the local UI prior to registration (excluding certain wireless client settings) will be wiped once the cloud sends down the device’s new configuration.

After the initial configuration task is completed, the device will be done with all registration-related activities and will commence normal operation.A device’s “Activity” page can be used at any time to see the point at which the device is in the initial registration and/or configuration process. In summary, there are four possible registration states for a device:

Unregistered: There is no record of the device in the Cloud database when a device is unregistered.
Pending Registration: The Cloud user has added the device record to a site by serial number and MAC, and the Cloud is waiting for the device to make an initial connection. At this point, the device has not yet made any contact with the Cloud. If you see a device in this state for a long time, check its internet connection or your upstream firewall settings.
Registered: The device has made initial contact with the Cloud, completed the registration process, and received its credentials which it will use in any further communication with the Cloud. The “registered” state is the normal operating state of a device on the cloud.
Re-registration: This means the device was previously registered, but is attempting to register again. The system creates an alert for this situation as it requires the user to login to their Cloud account and choose which actions they want to take – such as to allow the device to connect again, and what to do with the device’s new configuration.
Note: you can enable “auto” re-registration from the site properties page so that no manual intervention is required to resolve re-registration alerts.

Configuration

Any time a device’s device-level or site-level configuration is changed, the Cloud must determine which settings should actually be changed and pushed down for a device.

When “site-level configuration inheritance” is enabled for a device, a device's final configuration will be made of merging two different sets of configurations:

The common site level configuration settings for that product type, and
The device's individual configuration, which includes settings not configurable at the site level, such as advanced radio settings, features unique to a single product, and more importantly, any device-level configuration overrides.

Device-level config setting overrides can be created by changing a setting at the device-level config that’s currently being inherited from the site level. These can always be reverted at any time by pressing the purple arrow button next to the setting, or by pressing the “Use Site Settings” button.

You can read more about site-level inheritance and device-level overrides in related articles.

After a user changes configuration for a device, the following will happen:

A “Change Config” task will be created detailing exactly which settings are being changed on the device. This task can be tracked on the device’s Activity page.
The Cloud will push the new configuration down to the device, and wait for a config ACK from the device to acknowledge that the new configuration was successful.
If the ACK is received, the task is marked as complete. If the device loses connectivity after applying the new set of configuration settings, the device will revert to the previous configuration, and send a failure notification to the cloud. This will result in an “out of sync” error.

Configuration Errors and Failures

There are two major errors that may be encountered during the configuration process:

Configuration out of sync error: This error occurs when the device reverts a configuration pushed down from the Cloud because it can’t connect to the Cloud again after the change. This is what “out of sync” means - the device’s running configuration doesn’t match the configuration on the Cloud.
Resolution: This error can be resolved by changing any incorrect settings in your device’s configuration on the Cloud, and pushing the “Resync” button to send them back down. Here’s an example scenario of when this would happen: a device is currently operating in Client mode, but is configured to use AP mode from the device’s Configuration page on the Cloud. After a config push, the device will no longer be able to access the internet or Cloud, until its mode is changed to client from the cloud config
Configuration suspended error: You can read in more detail about this error on the related Configuration Suspension FAQ page.

Comments

0 comments

Article is closed for comments.

Category

Device Registration and Configuration Follow

Registration

Configuration

Configuration Errors and Failures

Comments

Articles in this section

Edgecore Networks Corporation

END USER LICENSE AGREEMENT

1) Trademarks:

2) License grant:

3) Open Source Software:

4) Ownership and Copyright:

5) Unauthorized Use:

6) No Warranties:

7) Limited Liability:

8) Compliance with laws:

9) Termination:

10) Governing Law and Jurisdiction:

11) General:

Category

Registration

Configuration

Configuration Errors and Failures

Related articles

Articles in this section