Onboard Cloud Connectors to Oracle Enterprise Communications Platform (Oracle ECP) to make the hardware manageable remotely and prepare it for physical installation on the network on customer premises or in the field.

1. Click the Edge Nodes Inventory tab, and click Add Hardware to start the guided process for onboarding hardware.
2. Click Start in the first panel.
   Oracle ECP displays the step number and action for each step of the process.
3. For Hardware Type, click Edge Nodes.
4. For Onboarding Method, click Manually add edges.
5. For the Edge 1 section, do the following:

   Name (Required)	Enter a friendly name for the Cloud Connector. Must be unique for the tenant. Must start with alphanumeric characters. Allowed characters: alphanumeric characters, underscore, hyphen, and space. Leading and trailing spaces are not allowed. Allowed character length: 2-100.
   Serial Number (Required)	Enter the Cloud Connector serial number. This value is found on the Cloud Connector's local UI.
   Make	Select Oracle from the drop-down list.
   Model	Select the appropriate model from the drop-down list.
   Organization	Select the organization to which you want this Cloud Connector to belong. This field is optional. If you select an organization, the Cloud Connector is associated with that organization. If you do not select an organization during onboarding, the Cloud Connector is onboarded as Unassigned and is not associated with any organization.
   MAC	Enter the 12 characters of the Media Access Control (MAC) address that will serve as the WAN address for this Cloud Connector in one of the following formats: XX:XX:XX:XX:XX:XX XX-XX-XX-XX-XX-XX XXXX.XXXX.XXXX
   Description	Enter additional details about the Cloud Connector. Allowed characters: alphanumeric characters,underscore, hyphen, comma, and space. Allowed character length: 0 to 255. Must be between 1 and 100 characters.
   Primary Internet Connection	Ethernet. Not editable.
   Secondary Internet Connection	Select the checkbox for one or more secondary internet connection types. Cloud Connector onboarding requires at least one Integrated Circuit Card ID (ICCID) found on the back of the SIM card, and one subscription plan. However, when Ethernet and dual SIM are enabled, SIM1 automatically receives a 1GB included data plan, while SIM2 requires the user to select a subscription plan. For information on the latest subscriptions offered, see Cloud Connector Subscriptions in What's New.
   Cellular - SIM 1 ICCID (Required)	The ICCID number that identifies the SIM card in slot #1. Note: Do not change the global Vodafone SIM shipped and installed in this slot on the Cloud Connector. (Optional) Use the toggle to activate the SIM card during onboarding.
   Cellular - SIM 1 Cellular Subscription (Required)	Select the subscription plan for this Cloud Connector. When onboarding a Cloud Connector with a second SIM, this value is prepopulated with the 1 GB included data plan. For information on the latest subscriptions offered, see Device and Cloud Connector Subscriptions in What's New.
   SIM 2 ICCID	Required when you use a second SIM card. The ICCID number that identifies the SIM card in slot #2. When you enter the ICCID for the second SIM card, Oracle ECP displays the Activate toggle for the second SIM card. (Optional) Use the toggle to activate the SIM card during onboarding.
   Cellular - SIM 2 Cellular Subscription	Select the subscription plan for the second SIM card. For information on the latest subscriptions offered, see Device and Cloud Connector Subscriptions in What's New.
   Authentication	Select a method for how you want the Cloud Connector to authenticate before connecting to the Cloud. This setting Must match what is provisioned on the Cloud Connector at activation time. Certificate (Default) Client Secret Allowed character length: 8-40.
   Registration/Deployment address	Enter the address, and then select a valid address from the suggested results when the registration address and deployment location are the same.
   Deployment coordinates	Shows the latitude and longitude for the deployment location. Oracle ECP automatically fills these values when you select a valid address. If an address is not available or cannot be resolved, enter the latitude and longitude manually. You can also adjust the deployment location by dragging the pushpin marker on the map.
   Registration address different from deployment location	Select this option when the business or service address used for connectivity registration is different from the physical deployment location of the edge node.
   Edge will be moving	Select this if the Cloud Connector will be in motion (for example, installed in a moving vehicle).

6. For the Authentication section, do the following:

   Authentication

   Select a method for how you want the Cloud Connector to authenticate before connecting to the Cloud. This setting Must match what is provisioned on the Cloud Connector at activation time. Certificate (Default) Client Secret Allowed character length: 8-40.

7. If you are onboarding the Cloud Connector with Satellite connectivity, you must do the following in the Registration address section:

   Edge will be moving	Select this if the Cloud Connector will be in motion (for example, installed in a moving vehicle).
   Satellite Starlink Identifier	Enter a valid Kit Serial Number or Terminal Serial Number.
   Satellite Subscription	Select the subscription plan for this Cloud Connector. For information on the latest subscriptions offered, see Device and Cloud Connector Subscriptions in What's New.
   Country	Click to select the country where the Cloud Connector will be installed. When you choose United States, Oracle ECP requires entries for the remaining address fields. When you choose a country other than the United States, Oracle ECP requires only the Street Address.
   Street Address	Enter the street address for the building where the Cloud Connector will be installed. Required for all Satellite connectivity, regardless of country. Must start with alphanumeric character. Allows alphanumeric characters along with spaces and dots. Allowed character length: 0-100.
   City/Town	Enter the city or town where the Cloud Connector will be installed. When the selected country is the United States, Oracle ECP requires the city or town. Allowed character length: 0-100.
   State/Region/Province	United States—Select the state where the Cloud Connector will be installed. When the selected country is the United States, Oracle ECP requires the State. All other countries—Enter the state, region or province manually. Allowed character length: 1-100.
   Zip/Postal Code	Enter the postal code for the location.
   Latitude (Required for Satellite Connectivity)	Enter the latitude of the satellite kit location. Must be between -90° and +90°, supporting up to six decimal places.
   Longitude (Required for Satellite Connectivity)	Enter the longitude of the satellite kit location. Must be between -180° and +180°, supporting up to six decimal places.

   Note:

   If your service location has no street address, enter it's coordinates in the Latitude and Longitude fields.
8. To onboard additional Cloud Connectors, Click the + character opposite Edge 1 to display another set of empty specification fields to onboard another Cloud Connector. You can onboard up to five Cloud Connectors at a time this way.

   Note:

   You cannot add other hardware types in this step. All additions must be Cloud Connectors.
9. Click Continue to validate the information you just entered.
   Oracle ECP either moves to the Review and Submit screen with a notification about your onboarding request. If validation is not successful, error messages appear at the top of the form. If fields do not pass validation, provide or correct information as detailed in the error message.
10. Click Submit on the Review and Submit screen to complete the onboarding process. Oracle ECP will move to the Onboarding Request Details screen so you can monitor this onboarding request.
    The Review and Submit screen summarizes the onboarding details for all Cloud Connectors specified.
    You can download a report about this onboarding request from the Onboarding Request Details screen.