Dedicated Instance Edge Connect

https://apps.cisco.com/Commerce/guest

It is mandatory to check the box against “Redundancy” as Dedicated Instance mandates two connections per region.

Architecture View when selecting 1 link with the redundancy option:

Architecture View when selecting 2 links with the redundancy option:

The details of your order appear. Click Back to Configuration if you'd like to make additional changes to your order.

The View and Save buttons now read, Save and Continue.

https://fabric.equinix.com/

The Connections page appears.

The three possible connection types are:

Port: This option lets you connect using a physical port. If you click Port, the system displays only the metros that you’ve already deployed. The connections that appear depend on your user permissions and the ports you already have set up.

Service token: A service token is a unique Equinix Fabric key that grants you authorization to an interconnection asset. This is not an option available today for Cisco.

Virtual device: This option lets you connect using a virtual connection that you set up. To set up a virtual device, select Network Edge > Create Virtual Device from the top menu bar, and perform the set-up process. The connections that appear when you select Virtual Device depend on your user permissions and the virtual devices you already have set up.

Note: For this example, we’ll follow the procedure for the Port option.

• Select the region.

  • Region options include AMER, EMEA, and APAC. When you select a region, the system displays locations within that region.

  • In this example AMER is selected for Dedicated Instance AMER region. Similarly, following are the region selection in Equinix portal for respective Dedicated Instance regions:

    Region selected in Dedicated Instance	Region to be selected in Equinix Portal	Cities to be selected in Equinix portal
    EMEA	EMEA	London, Amsterdam
    APJC	APAC	Singapore, Tokyo
    AUS	APAC	Melbourne (Service token based activation), Sydney
    EU	EMEA	Frankfurt, Amsterdam
    UK	EMEA	London, Manchester

• Select the origin location under Select Location.

  • The origin location is where the customer equipment resides and where the Equinix port that will be used is located. In this example, Silicon Valley is selected as the origin location.

  • The ports for the location you selected appear under Ports in <name of location>.

• Select the port.

• Under Destination, select the region, and then select the destination.

  • The suggested destination appears under Suggested, and all other possible destinations appear under Remote. In this example, Silicon Valley is selected as the destination location.

  • The destination location is the Webex DC location that will terminate this connection. There is no port to select on the destination side. Webex will associate the port accordingly. If there are multiple connections to the same site for the same customer Cisco will configure those connections over two separate routers (premises equipment) to ensure port and hardware redundancy.

• Click Next, located at the bottom right portion of the page.

The Connection Details page appears.

The following list describes the information you need to provide on the Connection Details page.

Connection: This is the name of the connection that both buyer (customer) and seller (Webex) will see in the Equinix portal. It is helpful that this name be indicative of the customer it is serving and the purpose of the link. For example, if the customer was name Enterprise1 and this connection was their primary in “Silicon Valley” location a helpful naming convention would be Enterprise1_SV_PRI and their secondary connection in the same location could be Enterprise1_SV_SEC.

VLAN ID: (This option is not available when connecting with a virtual device.) The customer side is locally significant between customer and Equinix. We recommend that customers provision their Equinix Cloud Exchange Ethernet port using standard 802.1q (Dot1q) framing with a standard EtherType of 0x8100 for simplicity. These are normal values associated with a trunk and do not include complex Metro ethernet settings that carriers typically use (qinq).

Purchase order number: This field captures the Cisco purchase order number from Cisco CCW. This is used by Cisco to verify the Edge Connect order.

*Important Note: This field “Purchase order number” shows as “(optional)” in the form but is a mandatory field for Cisco to validate the order.

Webex router IP address: The higher IP address from a defined subnet that will be assigned to the Webex router interface.

Your router IP address: The lower IP address from a defined subnet that will be assigned to your router interface.

Subnet mask for point-to-point link: The subnet mask or CIDR prefix for the point-to-point link.

Your advertised prefixes: The addresses to be advertised to Webex. Only 0.0.0.0 default route will be accepted.

Your BGP ASN: This is the BGP autonomous system number. If you already own a BGP that you want to you use, put that number here. If not, Webex also supports private numbers as well.

BGP password: This is an optional item. Type a password if you want to configure password authentication for BGP connectivity on the router.

Technical contact email address: The buyer email address to support notifications.

Technical contract phone number: The buyer phone number to support notifications.

Partner Name: Name of the partner.

Customer Name: Name of the customer.

The speeds shown are the speeds that Cisco has already set for your service profile.