Overview

Edge Connect is a solution that peers your Webex meetings traffic with an Equinix Cloud Exchange (ECX) location. This peering improves the in-meeting user experience by providing guaranteed bandwidth and quality of service (QoS), which minimizes network latency, packet loss, and jitter.

The link between the Customer Premise Equipment (CPE) and the Webex Provider Edge router will have low latency, but the actual user experience may vary depending on your location. As a rule of thumb: the closer you are to your regional Webex Meetings Data Center, the lower your network latency. Large customers that have a national or international network should peer with Webex in multiple regions to minimize latency.

For reference, see the ECX Fabric Workflow documentation at https://docs.equinix.com/.


Network latency can negatively affect the Webex user experience. Latency can be influenced by geographic location, Internet routing patterns, user network connectivity method (LAN versus Wi-Fi), and the overall health of the network paths between each connection point.

Requirements for Edge Connect

The following are the base requirements for establishing Edge Connect peering:

  • An active connection on the Equinix Cloud Exchange that is established through Equinix, see the ECX Fabric Workflow documentation at https://docs.equinix.com/.

  • Public Border Gateway Protocol (BGP) Autonomous System Number (ASN) that you own.

  • An IP space that is public and provider-independent.

  • An IT team with knowledge of BGP and peering principles.

  • A network device capable of running BGP and 802.1Q tagging.


Edge Connect does not accept private prefix advertisements like RFC1918.

Provisioning Overview

  1. Layer 1 – Physical Connectivity through Equinix.

  2. Layer 2 – Data-link Connectivity through Equinix.

  3. Layer 3 – Network Connectivity with Cisco Webex through the Equinix Cloud Exchange Portal.

To set up Edge Connect, you first work with an Equinix representative on two tasks: establishing Physical Connectivity and establishing Data-link Connectivity. When these tasks are complete, you can continue to the third task: establishing Network Connectivity with Cisco Webex through the Equinix Cloud Exchange Portal.

The diagram illustrates the Layer 1, Layer 2, and Layer 3 connections that must be set up to configure Edge Connect in the corresponding tasks.

The diagram illustrates the Layer 1, Layer 2, and Layer 3 connections that must be set up to configure Edge Connect in the corresponding tasks.

Physical and Data-Link Connectivity

Physical Connectivity

You will need to consult with an Equinix representative to set up your Physical and Data-link connectivity. There are three available methods for provisioning physical connectivity for Edge Connect.

  1. An Equinix local facility cross-connect between your router in an Equinix facility and the ECX switch. The purple segment below shows the connection that must be made between your cage and the ECX switch.


    This type of physical connectivity is only available in the following cities:

    US Locations

    International Locations

    • Ashburn, VA

    • Chicago, IL

    • Dallas, TX

    • New York, NY

    • Silicon Valley, CA

    • Amsterdam, NL

    • London, GB

    • Singapore, SG

    • Sydney, AU

    • Tokyo, JP

  2. A Partner Network Connection that creates a circuit between your building and the closest Equinix facility that colocates with the Webex cloud. The purple segment below shows the connection that must be made between your building and an Equinix facility.

  3. There is an Equinix facility, Facility A, close to your building but it does not colocate with the Webex cloud. You can create a circuit between your building and Facility A. Equinix then connects Facility A with a Facility that colocates with the Webex cloud, Facility B, using their network.

    The purple segment and cloud in the image below shows the connection that must be made to the ECX switch in Equinix Facility A, the connecting circuit between the Equinix facility closest to you, and the Equinix colocation facility.

Data-link Connectivity

You must provision an Ethernet virtual circuit connection to Webex using the Equinix Cloud Exchange portal.

https://ecxfabric.equinix.com.

Network Connectivity

Network Connectivity

Before you begin

Make sure to collect the following information. You will need it when you configure the Network Connectivity for Webex.

  • Webex router IP address.

  • Your router IP address.

  • Subnet mask for a point-to-point link.

  • Your advertised prefixes.

  • Your Border Gateway Protocol (BGP) Autonomous System Number (ASN).

  • Technical contact email address.

  • Technical contact phone number.

  • Complete Physical and Data-link Connectivity with an Equinix representative.

1

Sign in to https://ecxfabric.equinix.com and then select Create A Connection.

2

Select Connect to a Service Provider.

3

Select Webex Communications.


 

Search for "Webex" to find the tile quickly.

4

Select Create a connection.

5

Choose the Origin Location and Port.

6

Choose the Destination Location and select Next.

7

For Connection Information:

  • Enter a Name, such as [EXAMPLE-ECX-CONNECTION].

  • Enter a VLAN ID.

8

Enter everything in Additional Buyer Options, and select Next.

9

Choose a connection speed and select Next.

10

Review the order, then select Submit Your Order.

Step Result: Your connection request is submitted immediately. It is now up to the seller to accept or reject the request.

Routing Details

Route Policy Technical Details

Route Policy Technical Details

  • The Webex public BGP ASN is 13445.

  • The maximum length prefix that Webex advertises is /24. The maximum length prefix that Webex accepts is /29.

  • The number of routes that Webex advertises may change over time. We recommend that customers allow 50 routes from Webex on the BGP peering.

  • The maximum number of routes Webex accepts is 100.

  • Customers can use Bidirectional-Forwarding Detection (BFD). BFD is enabled with a default value of 300 ms x 3 on the Webex Perimeter Edge routers.

  • All Webex routes are included in the BGP advertisements.

  • Customer traffic-engineering techniques such as NAT, BGP AS-PATH prepending, or predefined BGP communities are available to influence traffic flows within the Cisco Backbone. BGP communities may be implemented to limit the scope of customer route propagation between the Webex geographic theaters.

  • Customers can use the Webex Looking Glass portal to see advertised BGP routes and perform ping and traceroute tests.

Webex Public IP Block Ranges By Theater

Webex Public IP Block Ranges By Theater

We encourage customers to accept all Webex routes with a prefix length that is less than or equal to /24. Route advertisements may change over time so customers shouldn’t set up filters using IP prefix lists. Alternatively, customers may create custom filters using BGP communities to accept routes based on geographic theater.

AMER

  • 64.68.96.0/19

  • 64.68.104.0/21

  • 64.68.120.0/21

  • 66.114.160.0/20

  • 66.114.160.0/21

  • 66.114.168.0/21

  • 66.163.32.0/19

  • 66.163.46.0/23

  • 173.39.224.0/19

  • 173.243.0.0/20

  • 207.182.160.0/19

  • 207.182.172.0/22

  • 209.197.192.0/19

  • 209.197.192.0/21

  • 216.151.128.0/19

  • 216.151.128.0/20

APAC

  • 69.26.176.0/20

  • 69.26.176.0/22

  • 69.26.180.0/22

  • 69.26.184.0/21

  • 114.29.192.0/19

  • 114.29.200.0/23

  • 114.29.202.0/23

  • 114.29.204.0/22

  • 114.29.208.0/21

  • 210.4.192.0/20

  • 210.4.198.0/24

  • 210.4.206.0/23

EMEA

  • 62.109.192.0/18

  • 69.26.160.0/20

Global Anycast

  • 66.163.52.0/24

  • 66.163.53.0/24

  • 69.26.160.0/24

BGP Communities

The following BGP communities are honored by Webex inbound route policies and may be used by customers to influence Direct Connect link priority.

Link Priority Communities

  • None — Default (least desirable path and/ or hot potato)

  • 13445:200 — Local Preference 200

  • 13445:300 — Local Preference 300

  • 13445:400 — Local Preference 400

  • 13445:500 — Local Preference 500

  • 13445:600 — Local Preference 600

  • 13445:700 — Local Preference 700

  • 13445:800 — Local Preference 800

  • 13445:900 — Local Preference 900 (Most desirable path)

Route Propagation Scoping Communities

Customers that have a global peering arrangement with Webex may want to limit route advertisements within the Cisco Webex cloud to the local geographic theater. The following communities may be used to limit customer route propagation across the Webex network.

  • None — Default permit global reachability

  • 13445:677 — Permit local theater reachability

Webex Route Origin Communities

Webex applies BGP community tags to indicate where the Webex prefix originates. This can be helpful if you want to perform route filtering based on location tag. The following BGP communities indicate the origin of the Webex prefix.

  • 13445:10000 — AMER

  • 13445:10010 — EMEA

  • 13445:10020 — APAC