Creating a Connection is the most common activity on the ECX Fabric portal.
There are many ways to begin the process. From the landing page, all users with at least one port or virtual device globally will see buttons to Order or Create.
You can also Create a Connection from other places, including Inventory.
Or when viewing the Device Details.
All of these entry points lead to the same place.
Learn more about the generic workflow for creating a connection on the ECX User Guide. The remainder of this article covers those elements which are unique to NE. You can also watch a short video of creating connections with a virtual device.
Each connection must have an A-End (sometimes also called a source or origin) - this can be either a physical port or a virtual device. All available options for each location display during Metro and Device selection
Once a location is selected, the user can choose from the list of available options by name. Ports and devices are displayed differently.
If you have both ports and virtual devices available, your list may look more like this:
PLEASE NOTE: any devices that are not eligible for this connection are greyed out and not selectable. Mouse over the ineligible device to see why. Some reasons include license not active or all interfaces full.
If your provider mandates redundancy (Microsoft Azure, for example), you will be asked to make a second selection in the same way as ECX port selection occurs. You will consume the same device and interface as primary in this case, until HA options are made available.
From this point, the rest of the Create Connections process proceeds as explained in the ECX documentation: Connecting To Other Layer 2 Cloud Service Providers (CSPs).
At the end of the process, you'll see a success screen that differs only slightly from the traditional ECX model. It will show the virtual device as the Origin.
Once you have finished, go to the inventory screen to view your connection and ensure it is fully provisioned and running. Consult the ECX fabric documentation or your specified cloud provider to ensure you have coordinated any tasks or configuration settings with them.