What Is Nobus Fast Transit?

Nobus Fast Transit links your private network directly to a Nobus Fast Transit point. You can create interfaces directly to public Nobus services or to Nobus Data center and not needing to go through an internet service providers (ISP) in your network route. You can use a single public connection to gain entry into public Nobus services

Components Nobus Fast Transit

Below are the vital components use for Nobus Fast Transit:

Connections: To set up a network connection from your premises to Nobus, create a connection in Nobus Fast Transit zone.
interfaces: Create a virtual interface to gain access to any Nobus services. A public virtual interface enables entry to public services, such as Nobus FOS. a private virtual interface enables entry to your Data center.

Minimum network requirements

To use Nobus Fast Transit in Nobus Fast Transit point, your network must meet one of the following conditions:

Your network is colocated with an existing Nobus Fast Transit point.
You are working with a connectivity provider to connect to Nobus Fast Transit.

In addition, your network must meet the following conditions:

Your network must use single-mode fiber with a 1000BASE-LX (1310 nm) transceiver for 1 gigabit Ethernet or a 10GBASE-LR (1310 nm) transceiver for 10 gigabit Ethernet.
Manually configuration of Port speed and full-duplex mode.
802.1Q VLAN encapsulation must be supported across the entire connection, including intermediate devices.
Your device must support Border Gateway Protocol (BGP) and BGP MD5 authentication.
Asynchronous BFD is automatically enabled for Nobus Fast Transit virtual interfaces, but must be configure it on your router.
You can Optionally configure Bidirectional Forwarding Detection (BFD) on your network.

Nobus Fast Transit supports both the IPv4 and IPv6 communication protocols. IPv6 addresses provided by public Nobus services are accessible through Nobus Fast Transit public virtual interfaces.

Pricing for Nobus Fast Transit

See Nobus Fast Transit Pricing .

Using the Fast Transit Toolkit to get started

Users of Nobus fast transit can attain a very high network connections between Nobus Data center and their on-premises infrastructure. The Fast Transit Toolkit provides a connection prompt with blueprint ensuring that you order connections to reach objectives of your Service Level Agreement. The blueprint allows you to have of an appropriate dedicated connections.

We recommend the use of the Connection prompt in the Fast Transit Toolkit to map the connections to reach your SLA objective.

The Fast Transit Toolkit take you through the following procedures:

Select number of dedicated connections
Select connection capacity, and the dedicated connection point
Choose the connection zone
Ordering the dedicated connections
Verifying that the dedicated connections enabled for use
Downloading your Letter of Authority (LOA-CFA) for each dedicated connection

Nobus Fast Transit connection can be set up in one of the following ways.

blueprint	Bandwidth	Method
Dedicated connection	1 Gbps, 10 Gbps	Work with Nobus Fast Transit Partner or a network provider to connect a router from your data center, office, or placement setting to Nobus Fast Transit. to connect you to a dedicated connection. Nobus Fast Transit dedicated connections support these port speeds over single-mode fiber: 1 Gbps: 1000BASE-LX (1310 nm) and 10 Gbps: 10GBASE-LR (1310 nm)
Hosted connection	50 Mbps, 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, and 10 Gbps	Work with a partner in the Nobus Fast Transit Partner Scheme to connect a router from your data center, office, or placement setting to Nobus Fast Transit. Only certain partners provide higher capacity connections.

For connections to Nobus Fast Transit with bandwidths of 1 Gbps or higher, ensure that your network meets the following requirements:

Your network must use single-mode fiber with a 1000BASE-LX (1310 nm) transceiver for 1 gigabit Ethernet or a 10GBASE-LR (1310 nm) transceiver for 10 gigabit Ethernet.
There must be support for 802.1Q VLAN encapsulation across the entire connection, including intermediate devices.
Your device must support Border Gateway Protocol (BGP) and BGP MD5 authentication.
Auto-negotiation for the port must be disabled. Port speed and full-duplex mode must be configured manually.

Ensure you have the following information before you begin your configuration:

The blueprint that you want to use.
The speed ( needed for one connection ), point, and partner for all of your connections.

The following procedures demonstrate how to use the Fast Transit Toolkit to configure a blueprint.

Contents

Step 1: Sign up for Nobus
Step 2: Configure the blueprint
Step 3: Create your interfaces
Step 4: Verify your interfaces

To use Nobus Fast Transit, you need Nobus account if you don't already have one.

Step 2: Configure the blueprint

To configure a blueprint

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/ .
On the Nobus Fast Transit screen, under quick start, choose Create a connection.
Under Connection ordering type, select Connection prompt.
Under level, choose Highest flexibility , and then choose Next.
On the Configure connections pane, under Connection settings, do the following:
1. For Bandwidth, choose the dedicated connection bandwidth.
  
  This bandwidth applies to all of the created connections.
2. For First point service provider, select the appropriate Nobus Fast Transit point for the dedicated connection.
3. If applicable, for First Sub point, choose the floor closest to you or your network provider. This option is only available if the point has meet-me rooms (MMRs) on multiple floors of the building.
4. If you selected Other for First point service provider, for Name of other provider, enter the name of the partner that you use.
5. For Second point service provider, select the appropriate Nobus Fast Transit point.
6. If applicable, for Second Sub point, choose the floor closest to you or your network provider. This option is only available if the point has meet-me rooms (MMRs) on multiple floors of the building.
7. If you selected Other for Second point service provider, for Name of other provider, enter the name of the partner that you use.
Choose Next.
Review your connections, and then choose Continue.

If your LOAs are ready, you can choose Download LOA, and then click Continue.

For Nobus to review your request and provision a port for your connection It can take up to 72 hours. During this period, you might receive an email with a request for more information about your use case or the specified point. The email is sent to the email address that you used when you signed up for Nobus. You must respond within five (5) working days or the connection is cancelled.

Step 3: Create your virtual interfaces

The blueprint requires four interfaces.

You can create an internal virtual interface to connect to your Data center or a public virtual interface to link to public Nobus services not present in a Data center. When you create a private virtual interface to a Data center, you need a private virtual interface for each Data center that you're connecting to. You need three private interfaces to connect to three Data centers.

Before you begin, ensure that you have the following information:

Resource	Required information
Connection	The Nobus Fast Transit connection or link aggregation group (LAG) for which you are creating the virtual interface.
Virtual interface name	A name for the virtual interface.
Virtual interface owner	If you're creating the virtual interface for another account, you need the Nobus account ID of the other account.
(Private virtual interface only) Connection	For connecting to a Data center in the same Nobus place, you need the virtual private gateway for your Data center. The ASN for the Nobus side of the BGP session is inherited from the virtual private gateway. When you create a virtual private gateway, you can specify your own private ASN. Otherwise, Nobus provides a default ASN. For connecting to a Data center through a Fast Transit gateway, you need the Fast Transit gateway. For more information, see Fast Transit Gateways tab.
VLAN	A unique virtual local area network (VLAN) tag that's not already in use on your connection. The value must be between 1 and 4094 and must comply with the Ethernet 802.1Q standard. This tag is required for any traffic traversing the Nobus Fast Transit connection. If you have a hosted connection, your Nobus Fast Transit Partner provides this value. You can’t update the value once you create the virtual interface.
Peer IP addresses	A virtual interface can support a BGP peering session for IPv4, IPv6, or one of each (dual-stack). You cannot create several BGP sessions for a single IP addressing family within the same virtual interface. The IP address ranges are allocated to each end of the virtual interface for the BGP peering session. IPv4: For public virtual interface you must specify unique public IPv4 addresses that you own. For private virtual interface Nobus can generate private IPv4 addresses for you. otherwise, ensure that you specify private CIDRs for your router interface and the Nobus Fast Transit interface. Ensure you do not specify other IP addresses from your local network. IPv6: Nobus automatically allocates you a /45 IPv6 CIDR. You cannot specify your own peer IPv6 addresses.
Address family	Deciding if the BGP peering session will be over IPv4 or IPv6.
BGP information	A public or private Border Gateway Protocol (BGP) Autonomous System Number (ASN) for your side of the BGP session. If you are using a public ASN, you must own it. If you are using a private ASN, it must be in the 64512 to 65535 range. Autonomous System (AS) prepending does not work if you use a private ASN for a public virtual interface. An MD5 BGP authentication key. You can add your own, or Nobus will generate one for you.
(For Public virtual interface) Prefixes you want to advertise	Public IPv4 routes or IPv6 routes to advertise over BGP. You must advertise at least one prefix using BGP, up to a maximum of 1,000 prefixes. IPv4: The IPv4 CIDR must not overlap with another public IPv4 CIDR announced using Nobus Fast Transit. If you do not own public IPv4 addresses, your network provider might be able to provide you with a public IPv4 CIDR. IPv6: Specify a prefix length of /72 or shorter.
(For Private virtual interface only) Jumbo frames	The maximum transmission unit (MTU) of packets over Nobus Fast Transit. The default is 1500. Setting the MTU of a virtual interface to 9001 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all interfaces associated with the connection for up to 30 seconds. Jumbo frames apply only to propagated routes from Nobus Fast Transit. If you add static routes to a route table that point to your virtual private gateway, then traffic routed through the static routes is sent using 1500 MTU. To check whether a connection or virtual interface supports jumbo frames, select it in the Nobus Fast Transit console and find Jumbo Frame Capable on the Summary tab.
(Transit virtual interface only) Jumbo frames	The maximum transmission unit (MTU) of packets over Nobus Fast Transit. The default is 1500. Setting the MTU of a virtual interface to 8500 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all interfaces associated with the connection for up to 30 seconds. Jumbo frames apply only to propagated routes from Nobus Fast Transit. If you add static routes to a route table that point to your virtual private gateway, then traffic routed through the static routes is sent using 1500 MTU. To check whether a connection or virtual interface supports jumbo frames, select it in the Nobus Fast Transit console and find Jumbo Frame Capable on the Summary tab.

If your public prefixes or ASNs belong to an ISP or network carrier, Nobus requests additional information from you. This should be an email from the company's domain name verifying that the network prefix/ASN can be used by you.

When you create a public virtual interface, it can take up to 72 hours for Nobus to review and approve your request.

To provision a public virtual interface to non-Data center services

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/ .
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Public.
Under Public virtual interface settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For VLAN, enter the ID number for your virtual local area network (VLAN).
4. For BGP ASN, enter the Border Gateway Protocol (BGP) Autonomous System Number (ASN) of your gateway.
Under Additional settings, do the following:
1. To configure an IPv4 BGP or an IPv6 peer, do the following:
  
  [IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
  - To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
  - For Nobus router peer IP, enter the IPv4 CIDR address to use to send traffic to Nobus.
  [IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
2. To provide your own BGP key, enter your BGP MD5 key.
  
  If you do not enter a value, Nobus generates a BGP key.
3. To advertise prefixes to Nobus, for Prefixes you want to advertise, enter the IPv4 CIDR destination addresses (comma separated) to which traffic should be routed over the virtual interface.
Choose Create virtual interface.

To provision a private virtual interface to a Data center

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/ .
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Private.
Under Private virtual interface settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For Gateway type, choose Virtual private gateway, or Fast Transit gateway.
4. For Virtual interface owner, choose Another Nobus account, and then enter the Nobus account.
5. For Virtual private gateway, choose the virtual private gateway to use for this interface.
6. For VLAN, enter the ID number for your virtual local area network (VLAN).
7. For BGP ASN, enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface.
Under Additional Settings, do the following:
1. To configure an IPv4 BGP or an IPv6 peer, do the following:
  
  [IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
  - To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
  - For Nobus router peer ip, enter the IPv4 CIDR address to use to send traffic to Nobus.
  [IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
2. To change the maximum transmission unit (MTU) from 1500 (default) to 9001 (jumbo frames), select Jumbo MTU (MTU size 9001).
Choose Create virtual interface.

Step 4: Verify your interfaces

After your interfaces to the Nobus Cloud or to Nobus Data center have been created, follow procedures to verify your Nobus Fast Transit connection:

Run traceroute and verify that the Nobus Fast Transit identifier is in the network trace.

To verify your virtual interface connection to Nobus Data center

Use Nobus Linux NMI ( pingable) for example, launch an FCS instance into the Data center that is attached to your virtual private gateway. Make sure that you permit inbound ICMP traffic (for the ping request) by adding it to the security group associated with the instance.
After the instance is running, get its private IPv4 address (for example, 10.0.0.1). The Nobus FCS console displays the address as part of the instance details.
Ping the private IPv4 address for a response in return.

Classic

Select Classic when you have existing connections.

The following procedures shows the common scenarios to get set up with Nobus Fast Transit connection.

Contents

Prerequisites
Step 1: Sign up for Nobus
Step 2: Request Nobus Fast Transit dedicated connection or accept a hosted connection
step 3: Download the LOA-CFA ( Dedicated connection only)
Step 4: Create a virtual interface
Step 5: Download the router configuration
Step 6: Verify your virtual interface

Prerequisites

For connections to Nobus Fast Transit with port speeds of 1 Gbps or higher, ensure that your network meets the following requirements:

Your network must use single-mode fiber with a 1000BASE-LX (1310 nm) transceiver for 1 gigabit Ethernet or a 10GBASE-LR (1310 nm) transceiver for 10 gigabit Ethernet.
Auto-negotiation for the port must be disabled. Port speed and full-duplex mode must be configured manually.
802.1Q VLAN encapsulation must be supported across the entire connection, including intermediate devices.
Your device must support Border Gateway Protocol (BGP) and BGP MD5 authentication.
(Optional) You can configure Bidirectional Forwarding Detection (BFD) on your network. Asynchronous BFD is automatically enabled for Nobus Fast Transit virtual interfaces, but does not take effect until you configure it on your router.

You need a Nobus account to use Nobus Fast Transit. Ensure to sign up if you don't have one.

Step 2: Request Nobus Fast Transit dedicated connection or accept a hosted connection

For dedicated connections, you can submit a connection request using the Nobus Direct Connect console. For hosted connections, work with Nobus Fast Transit Partner to request a hosted connection. Ensure that you have the following information:

The port speed that you require. You cannot change the port speed after you create the connection request.
The Nobus Fast Transit point at which the connection is to be terminated.

You cannot use the Nobus Fast Transit console to request a hosted connection. Instead, contact Nobus Fast Transit Partner, who can create a hosted connection for you, which you then accept. Skip the following procedure and go to Accept your hosted connection.

To create a new Nobus Fast Transit connection

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
On the Nobus Fast Transit screen, under Get started, choose Create a connection.
Choose Classic.
On the Create Connection pane, under Connection settings, do the following:
1. For Name, enter a name for the connection.
2. For point, select the appropriate Nobus Fast Transit point.
3. If applicable, for Sub point, choose the floor closest to you or your network provider. This option is only available if the point has meet-me rooms (MMRs) in multiple floors of the building.
4. For Port Speed, choose the connection bandwidth.
5. For On-premises, select Connect through Nobus Fast Transit partner when you use this connection to connect to your data center.
6. For Service provider, select the Nobus Fast Transit Partner. If you use a partner that is not in the list, select Other.
7. If you selected Other for Service provider, for Name of other provider, enter the name of the partner that you use.
Choose Create Connection.

For more information, see Nobus Fast Transit connections.

Accept your hosted connection

You must accept the hosted connection in the Nobus Fast Transit console before you can create a virtual interface.

To accept a hosted virtual interface

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose interfaces.
Select the virtual interface and then choose View details.
Choose Accept.
This applies to private interfaces and transit virtual interfaces.

(Transit virtual interface) In the Accept virtual interface dialog box, select a Fast Transit gateway, and then choose Accept virtual interface.

(Private virtual interface) In the Accept virtual interface dialog box, select a virtual private gateway or Direct Connect gateway, and then choose Accept virtual interface.
After you accept the hosted virtual interface, the owner of the Nobus Fast Transit connection can download the router configuration file. The Download router configuration option is not available for the account that accepts the hosted virtual interface.
Go to Step 4 to continue setting up your Nobus Fast Transit connection.

(Dedicated connection) step 3: Download the LOA-CFA

After you request a connection, Nobus makes a Letter of Authorization and Connecting Facility Assignment (LOA-CFA) available to you to download, or emails you with a request for more information. The LOA-CFA is the authorization to connect to Nobus, and is required by the copoint provider or your network provider to establish the cross-network connection (cross-connect).

To download the LOA-CFA

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Connections.
Select the connection and choose View Details.
Choose Download LOA-CFA.

The LOA-CFA is downloaded to your computer as a PDF file.

If the link is not enabled, the LOA-CFA is not yet available for you to download. Check your email for a request for more information. If it's still unavailable, or you haven't received an email after 72 hours, contact Nobus Support
After you download the LOA-CFA, do one of the following:
- If you're working with Nobus Fast Transit Partner or network provider, send them the LOA-CFA so that they can order a cross-connect for you at the Nobus Fast Transit point. If they cannot order the cross-connect for you, you can contact the copoint provider directly.
- If you have equipment at the Nobus Fast Transit point, contact the copoint provider to request a cross-network connection. You must be a customer of the copoint provider. You must also present them with the LOA-CFA that authorizes the connection to the Nobus router, and the necessary information to connect to your network.

Step 4: Create a virtual interface

Before you begin, ensure that you have the following information:

Resource	Required information
Connection	The Nobus Fast Transit connection or link aggregation group (LAG) for which you are creating the virtual interface.
Virtual interface name	A name for the virtual interface.
Virtual interface owner	If you're creating the virtual interface for another account, you need the Nobus account ID of the other account.
(Private virtual interface only) Connection	For connecting to a Data center in the same Nobus place, you need the virtual private gateway for your Data center. The ASN for the Nobus side of the BGP session is inherited from the virtual private gateway. When you create a virtual private gateway, you can specify your own private ASN. Otherwise, Nobus provides a default ASN. For connecting to a Data center through a Fast Transit gateway, you need the Fast Transit gateway. For more information, see Fast Transit Gateways tab.
VLAN	A unique virtual local area network (VLAN) tag that's not already in use on your connection. The value must be between 1 and 4094 and must comply with the Ethernet 802.1Q standard. This tag is required for any traffic traversing the Nobus Fast Transit connection. If you have a hosted connection, your Nobus Fast Transit Partner provides this value. You can’t update the value once you create the virtual interface.
Peer IP addresses	A virtual interface can support a BGP peering session for IPv4, IPv6, or one of each (dual-stack). You cannot create several BGP sessions for a single IP addressing family within the same virtual interface. The IP address ranges are allocated to each end of the virtual interface for the BGP peering session. IPv4: For public virtual interface you must specify unique public IPv4 addresses that you own. For private virtual interface Nobus can generate private IPv4 addresses for you. otherwise, ensure that you specify private CIDRs for your router interface and the Nobus Fast Transit interface. Ensure you do not specify other IP addresses from your local network. IPv6: Nobus automatically allocates you a /45 IPv6 CIDR. You cannot specify your own peer IPv6 addresses.
Address family	Deciding if the BGP peering session will be over IPv4 or IPv6.
BGP information	A public or private Border Gateway Protocol (BGP) Autonomous System Number (ASN) for your side of the BGP session. If you are using a public ASN, you must own it. If you are using a private ASN, it must be in the 64512 to 65535 range. Autonomous System (AS) prepending does not work if you use a private ASN for a public virtual interface. An MD5 BGP authentication key. You can add your own, or Nobus will generate one for you.
(For Public virtual interface) Prefixes you want to advertise	Public IPv4 routes or IPv6 routes to advertise over BGP. You must advertise at least one prefix using BGP, up to a maximum of 1,000 prefixes. IPv4: The IPv4 CIDR must not overlap with another public IPv4 CIDR announced using Nobus Fast Transit. If you do not own public IPv4 addresses, your network provider might be able to provide you with a public IPv4 CIDR. IPv6: Specify a prefix length of /72 or shorter.
(For Private virtual interface only) Jumbo frames	The maximum transmission unit (MTU) of packets over Nobus Fast Transit. The default is 1500. Setting the MTU of a virtual interface to 9001 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all interfaces associated with the connection for up to 30 seconds. Jumbo frames apply only to propagated routes from Nobus Fast Transit. If you add static routes to a route table that point to your virtual private gateway, then traffic routed through the static routes is sent using 1500 MTU. To check whether a connection or virtual interface supports jumbo frames, select it in the Nobus Fast Transit console and find Jumbo Frame Capable on the Summary tab.
(Transit virtual interface only) Jumbo frames	The maximum transmission unit (MTU) of packets over Nobus Fast Transit. The default is 1500. Setting the MTU of a virtual interface to 8500 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all interfaces associated with the connection for up to 30 seconds. Jumbo frames apply only to propagated routes from Nobus Fast Transit. If you add static routes to a route table that point to your virtual private gateway, then traffic routed through the static routes is sent using 1500 MTU. To check whether a connection or virtual interface supports jumbo frames, select it in the Nobus Fast Transit console and find Jumbo Frame Capable on the Summary tab.

When you create a public virtual interface, it can take up to 72 hours for Nobus to review and approve your request.

To provision a public virtual interface to non-Data center services

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/ .
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Public.
Under Public virtual interface settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For VLAN, enter the ID number for your virtual local area network (VLAN).
4. For BGP ASN, enter the Border Gateway Protocol (BGP) Autonomous System Number (ASN) of your gateway.
Under Additional settings, do the following:
1. To configure an IPv4 BGP or an IPv6 peer, do the following:
  
  [IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
  - To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
  - For Nobus router peer IP, enter the IPv4 CIDR address to use to send traffic to Nobus.
  [IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
2. To provide your own BGP key, enter your BGP MD5 key.
  
  If you do not enter a value, Nobus generates a BGP key.
3. To advertise prefixes to Nobus, for Prefixes you want to advertise, enter the IPv4 CIDR destination addresses (comma separated) to which traffic should be routed over the virtual interface.
Choose Create virtual interface.

To provision a private virtual interface to a Data center

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/ .
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Private.
Under Private virtual interface settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For Gateway type, choose Virtual private gateway, or Fast Transit gateway.
4. For Virtual interface owner, choose Another Nobus account, and then enter the Nobus account.
5. For Virtual private gateway, choose the virtual private gateway to use for this interface.
6. For VLAN, enter the ID number for your virtual local area network (VLAN).
7. For BGP ASN, enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface.
Under Additional Settings, do the following:
1. To configure an IPv4 BGP or an IPv6 peer, do the following:
  
  [IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
  - To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
  - For Nobus router peer ip, enter the IPv4 CIDR address to use to send traffic to Nobus.
  [IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
2. To change the maximum transmission unit (MTU) from 1500 (default) to 9001 (jumbo frames), select Jumbo MTU (MTU size 9001).
Choose Create virtual interface.

Step 5: Download the router configuration

After you have created a virtual interface for your Nobus Fast Transit connection, you can download the router configuration file. The file contains the necessary commands to configure your router for use with your private or public virtual interface.

To download a router configuration

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose interfaces.
Select the connection and choose View Details.
Choose Download router configuration.
For Download router configuration, do the following:
1. For Vendor, select the manufacturer of your router.
2. For Platform, select the blueprint of your router.
3. For Software, select the software version for your router.
Choose Download, and then use the appropriate configuration for your router to ensure that you can connect to Nobus Fast Transit.

Step 6: Verify your virtual interface

After your interfaces to the Nobus Cloud or to Nobus Data center have been created, follow procedures to verify your Nobus Fast Transit connection:

Run traceroute and verify that the Nobus Fast Transit identifier is in the network trace.

To verify your virtual interface connection to Nobus Data center

Use Nobus Linux NMI ( pingable) for example, launch an FCS instance into the Data center that is attached to your virtual private gateway. Make sure that you permit inbound ICMP traffic (for the ping request) by adding it to the security group associated with the instance.
After the instance is running, get its private IPv4 address (for example, 10.0.0.1). The Nobus FCS console displays the address as part of the instance details.
Ping the private IPv4 address for a response in return.

Nobus Fast Transit connections

Nobus Fast Transit enables you to establish a dedicated network connection between your network and the Nobus Fast Transit.

There are two types of connections:

Dedicated Connection: A physical Ethernet connection associated with a single user. Users can request a dedicated connection through the Nobus Fast Transit console.
Hosted Connection: A physical Ethernet connection that Nobus Fast Transit Partner provisions on behalf of a customer. Customers request a hosted connection by contacting a partner in the Nobus Fast Transit Partner Scheme, who provisions the connection.

Dedicated connections

To create Nobus Fast Transit dedicated connection, you need the following information:

Nobus Fast Transit point: Work with a partner in the Nobus Fast Transit Partner Scheme to help you create network links between Nobus Fast Transit point and your data center, office, or placement setting.
Port speed: The possible values are 1Gbps and 10Gbps.

You cannot change the port speed after you create the connection request. To change the port speed, you must create and configure a new connection.

After you request the connection, Nobus makes a Letter of Authorization and Connecting Facility Assignment (LOA-CFA) available to you to download, or emails you with a request for more information. If you receive a request for more information, you must respond within 7 days or the connection is deleted. The LOA-CFA is the authorization to connect to Nobus, and is required by your network provider to order a cross connect for you. If you do not have equipment in the Nobus Fast Transit point, you cannot order a cross connect for yourself there.

After you create a connection, create a virtual interface to connect to public and private Nobus resources. Click the Nobus Fast Transit interfaces tab on the left for more.

Hosted connections

To create Nobus Fast Transit connection, you need the following information:

Nobus Fast Transit point: Work with Nobus Fast Transit Partner in the Nobus Fast Transit Partner Scheme to help you establish network circuits between Nobus Fast Transit point and your data center, office, or copoint environment. They can also help provide copoint space within the same facility as the point. For more information, see APN Partners Supporting Nobus Fast Transit
Port speed: For hosted connections, the possible values are 50Mbps, 100Mbps, 200Mbps, 300Mbps, 400Mbps, 500Mbps, 1Gbps, 2Gbps, 5Gbps, and 10Gbps. Note that only those Nobus Fast Transit partners who have met specific requirements may create a 1Gbps, 2Gbps, 5Gbps or 10Gbps hosted connection.

You cannot change the port speed after you create the connection request. To change the port speed, you must create and configure a new connection.

The following operations are available for hosted connections:

Creating a connection
Viewing connection details
Updating a connection
Deleting connections

After you accept a connection, create a virtual interface to connect to public and private Nobus resources.

Creating a connection

You can create a standalone connection, or you can create a connection to associate with a LAG in your account. If you associate a connection with a LAG, it's created with the same port speed and point that is specified in the LAG.

If you do not have equipment at Nobus Fast Transit point, first contact Nobus Fast Transit Partner at the Nobus Fast Transit Partner Scheme.

To create a new Nobus Fast Transit connection

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
On the Nobus Fast Transit screen, under Get started, choose Create a connection.
On the Create Connection pane, under Connection settings, do the following:
1. For Name, enter a name for the connection.
2. For point, select the appropriate Nobus Fast Transit point.
3. If applicable, for Sub point, choose the floor closest to you or your network provider. This option is only available if the point has meet-me rooms (MMRs) in multiple floors of the building.
4. For Port Speed, choose the connection bandwidth.
For On-premises, select Connect through Nobus Fast Transit partner when you use this connection to connect to your data center.
1. (Optional) Add or remove a tag.
  
  [Add a tag] Choose Add tag and do the following:
  - For Key, enter the key name.
  - For Value, enter the key value.
  [Remove a tag] Next to the tag, choose Remove tag.
Choose Create Connection.

Downloading the LOA-CFA

After Nobus has processed your connection request, you can download the LOA-CFA.

To download the LOA-CFA

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Connections.
Select the connection and choose View details.
Choose Download LOA-CFA.

If the link is not enabled, the LOA-CFA is not yet available for you to download. Check your email for a request for information. If it's still unavailable, or you haven't received an email after 72 hours, contact Nobus Support
Send the LOA-CFA to your network provider or copoint provider so that they can order a cross connect for you. The contact process can vary for each copoint provider. For more information, see Requesting cross connects at Nobus Fast Transit points.

The LOA-CFA expires after 90 days. If your connection is not up after 90 days, we send you an email alerting you that the LOA-CFA has expired. To refresh the LOA-CFA with a new issue date, download it again from the Nobus Fast Transit console. If you do not take any action, we delete the connection.

Port-hour billing starts 90 days after you created the connection, or after the connection between your router and the Nobus Fast Transit endpoint is created, whichever comes first. See Nobus Fast Transit Pricing for more information. If you no longer want the connection after you have reissued the LOA-CFA, you must delete the connection yourself. For more information, see Deleting connections.

Viewing connection details

You can view the current status of your connection. You can also view your connection ID and verify that it matches the connection ID on the LOA-CFA that you received or downloaded.

To view details about a connection

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the left pane, choose Connections.
Select a connection and choose View details.

Updating a connection

You can update your connection name.

To update a connection

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Connections.
Select the connection and choose Edit.
Modify the connection:

[Change the name] For Name, enter a new connection name.

[Add a tag] Choose Add tag and do the following:
- For Key, enter the key name.
- For Value, enter the key value.
[Remove a tag] Next to the tag, choose Remove tag.
Choose Edit connection.

Deleting connections

You can delete a connection as long as there are no interfaces attached to it. Deleting your connection stops all port hour charges for this connection. Nobus Direct Connect data transfer charges are associated with interfaces. Any cross connect or network circuit charges are independent of Nobus Fast Transit and must be cancelled separately.

To delete a connection

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Connections.
Select the connections and choose Delete.
In the Delete confirmation dialog box, choose Delete.

Accepting a hosted connection

If you are interested in purchasing a hosted connection, you must contact Nobus Direct Connect Partner in the Nobus Fast Transit Partner Scheme. The partner provisions the connection for you. After the connection is configured, it appears in the Connections pane in the Nobus Fast Transit console.

Before you can begin using a hosted connection, you must accept the connection.

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Connections.
Select the hosted connection and choose View details.
Select the confirmation check box and choose Accept connection.

Requesting cross connects at Nobus Fast Transit points

After you have downloaded your Letter of Authorization and Connecting Facility Assignment (LOA-CFA), you must complete your cross-network connection, also known as a cross connect. If you already have equipment located in Nobus Fast Transit point, contact the appropriate provider to complete the cross connect. For specific instructions for each provider, see the table below. Contact your provider for cross connect pricing. After the cross connect is established, you can create the interfaces using the Nobus Fast Transit console.

If you do not already have equipment located in Nobus Fast Transit point, you can work with one of the partners in the Nobus Partner Network (APN). They help you to connect to an Nobus Fast Transit point. For more information, see APN Partners supporting Nobus Fast Transit provider to facilitate your cross connect request.

Nobus Fast Transit connection can provide access to resources in other places. For more information, see Accessing a remote Nobus place.

If the cross connect is not completed within 90 days, the authority granted by the LOA-CFA expires. To renew a LOA-CFA that has expired, you can download it again from the Nobus Fast Transit console. For more information, see Downloading the LOA-CFA.

Nobus Fast Transit interfaces

You must create one of the following interfaces to begin using your Nobus Direct Connect connection.

Private virtual interface: A private virtual interface should be used to access an Nobus Data center using private IP addresses.
Public virtual interface: A public virtual interface can access all Nobus public services using public IP addresses.
Transit virtual interface: A transit virtual interface should be used to access one or more Nobus Data center Transit Gateways associated with Fast Transit gateways.

To connect to other Nobus services using IPv6 addresses, check the service documentation to verify that IPv6 addressing is supported.

Public virtual interface prefix advertisement rules

We advertise appropriate Nobus prefixes to you so that you can reach either your Data centers or other Nobus services. You can access all Nobus prefixes through this connection; for example, Nobus FCS, Nobus FOS, and Nobus.com. You do not have access to non-Nobus prefixes. For a current list of prefixes advertised by Nobus, see

We recommend that you use a firewall filter (based on the source/destination address of packets) to control traffic to and from some prefixes. If you're using a prefix filter (route map), ensure that it accepts prefixes with an exact match or longer. Prefixes advertised from Nobus Fast Transit may be aggregated and may differ from the prefixes defined in your prefix filter.

Hosted interfaces

To use your Nobus Fast Transit connection with another Nobus account, you can create a hosted virtual interface for that account. The owner of the other account must accept the hosted virtual interface to begin using it. A hosted virtual interface works the same as a standard virtual interface and can connect to public resources or a Data center.

A connection of less than 1 Gbps supports only one virtual interface.

To create a virtual interface, you need the following information:

Resource	Required information
Connection	The Nobus Fast Transit connection or link aggregation group (LAG) for which you are creating the virtual interface.
Virtual interface name	A name for the virtual interface.
Virtual interface owner	If you're creating the virtual interface for another account, you need the Nobus account ID of the other account.
(Private virtual interface only) Connection	For connecting to a Data center in the same Nobus place, you need the virtual private gateway for your Data center. The ASN for the Nobus side of the BGP session is inherited from the virtual private gateway. When you create a virtual private gateway, you can specify your own private ASN. Otherwise, Nobus provides a default ASN. For connecting to a Data center through a Fast Transit gateway, you need the Fast Transit gateway. For more information, see Fast Transit Gateways tab.
VLAN	A unique virtual local area network (VLAN) tag that's not already in use on your connection. The value must be between 1 and 4094 and must comply with the Ethernet 802.1Q standard. This tag is required for any traffic traversing the Nobus Fast Transit connection. If you have a hosted connection, your Nobus Fast Transit Partner provides this value. You can’t update the value once you create the virtual interface.
Peer IP addresses	A virtual interface can support a BGP peering session for IPv4, IPv6, or one of each (dual-stack). You cannot create several BGP sessions for a single IP addressing family within the same virtual interface. The IP address ranges are allocated to each end of the virtual interface for the BGP peering session. IPv4: For public virtual interface you must specify unique public IPv4 addresses that you own. For private virtual interface Nobus can generate private IPv4 addresses for you. otherwise, ensure that you specify private CIDRs for your router interface and the Nobus Fast Transit interface. Ensure you do not specify other IP addresses from your local network. IPv6: Nobus automatically allocates you a /45 IPv6 CIDR. You cannot specify your own peer IPv6 addresses.
Address family	Deciding if the BGP peering session will be over IPv4 or IPv6.
BGP information	A public or private Border Gateway Protocol (BGP) Autonomous System Number (ASN) for your side of the BGP session. If you are using a public ASN, you must own it. If you are using a private ASN, it must be in the 64512 to 65535 range. Autonomous System (AS) prepending does not work if you use a private ASN for a public virtual interface. An MD5 BGP authentication key. You can add your own, or Nobus will generate one for you.
(For Public virtual interface) Prefixes you want to advertise	Public IPv4 routes or IPv6 routes to advertise over BGP. You must advertise at least one prefix using BGP, up to a maximum of 1,000 prefixes. IPv4: The IPv4 CIDR must not overlap with another public IPv4 CIDR announced using Nobus Fast Transit. If you do not own public IPv4 addresses, your network provider might be able to provide you with a public IPv4 CIDR. IPv6: Specify a prefix length of /72 or shorter.
(For Private virtual interface only) Jumbo frames	The maximum transmission unit (MTU) of packets over Nobus Fast Transit. The default is 1500. Setting the MTU of a virtual interface to 9001 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all interfaces associated with the connection for up to 30 seconds. Jumbo frames apply only to propagated routes from Nobus Fast Transit. If you add static routes to a route table that point to your virtual private gateway, then traffic routed through the static routes is sent using 1500 MTU. To check whether a connection or virtual interface supports jumbo frames, select it in the Nobus Fast Transit console and find Jumbo Frame Capable on the Summary tab.
(Transit virtual interface only) Jumbo frames	The maximum transmission unit (MTU) of packets over Nobus Fast Transit. The default is 1500. Setting the MTU of a virtual interface to 8500 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all interfaces associated with the connection for up to 30 seconds. Jumbo frames apply only to propagated routes from Nobus Fast Transit. If you add static routes to a route table that point to your virtual private gateway, then traffic routed through the static routes is sent using 1500 MTU. To check whether a connection or virtual interface supports jumbo frames, select it in the Nobus Fast Transit console and find Jumbo Frame Capable on the Summary tab.

Prerequisites for interfaces

Before you create a virtual interface, do the following:

Create a connection. For more information, see Creating a connection.
Create a link aggregation group (LAG) when you have multiple connections that you want to treat as a single one. For information, see Associating a connection with a LAG.

To create a virtual interface, you need the following information:

Resource	Required information
Connection	The Nobus Fast Transit connection or link aggregation group (LAG) for which you are creating the virtual interface.
Virtual interface name	A name for the virtual interface.
Virtual interface owner	If you're creating the virtual interface for another account, you need the Nobus account ID of the other account.
(Private virtual interface only) Connection	For connecting to a Data center in the same Nobus place, you need the virtual private gateway for your Data center. The ASN for the Nobus side of the BGP session is inherited from the virtual private gateway. When you create a virtual private gateway, you can specify your own private ASN. Otherwise, Nobus provides a default ASN. For connecting to a Data center through a Fast Transit gateway, you need the Fast Transit gateway. For more information, see Fast Transit Gateways tab.
VLAN	A unique virtual local area network (VLAN) tag that's not already in use on your connection. The value must be between 1 and 4094 and must comply with the Ethernet 802.1Q standard. This tag is required for any traffic traversing the Nobus Fast Transit connection. If you have a hosted connection, your Nobus Fast Transit Partner provides this value. You can’t update the value once you create the virtual interface.
Peer IP addresses	A virtual interface can support a BGP peering session for IPv4, IPv6, or one of each (dual-stack). You cannot create several BGP sessions for a single IP addressing family within the same virtual interface. The IP address ranges are allocated to each end of the virtual interface for the BGP peering session. IPv4: For public virtual interface you must specify unique public IPv4 addresses that you own. For private virtual interface Nobus can generate private IPv4 addresses for you. otherwise, ensure that you specify private CIDRs for your router interface and the Nobus Fast Transit interface. Ensure you do not specify other IP addresses from your local network. IPv6: Nobus automatically allocates you a /45 IPv6 CIDR. You cannot specify your own peer IPv6 addresses.
Address family	Deciding if the BGP peering session will be over IPv4 or IPv6.
BGP information	A public or private Border Gateway Protocol (BGP) Autonomous System Number (ASN) for your side of the BGP session. If you are using a public ASN, you must own it. If you are using a private ASN, it must be in the 64512 to 65535 range. Autonomous System (AS) prepending does not work if you use a private ASN for a public virtual interface. An MD5 BGP authentication key. You can add your own, or Nobus will generate one for you.
(For Public virtual interface) Prefixes you want to advertise	Public IPv4 routes or IPv6 routes to advertise over BGP. You must advertise at least one prefix using BGP, up to a maximum of 1,000 prefixes. IPv4: The IPv4 CIDR must not overlap with another public IPv4 CIDR announced using Nobus Fast Transit. If you do not own public IPv4 addresses, your network provider might be able to provide you with a public IPv4 CIDR. IPv6: Specify a prefix length of /72 or shorter.
(For Private virtual interface only) Jumbo frames	The maximum transmission unit (MTU) of packets over Nobus Fast Transit. The default is 1500. Setting the MTU of a virtual interface to 9001 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all interfaces associated with the connection for up to 30 seconds. Jumbo frames apply only to propagated routes from Nobus Fast Transit. If you add static routes to a route table that point to your virtual private gateway, then traffic routed through the static routes is sent using 1500 MTU. To check whether a connection or virtual interface supports jumbo frames, select it in the Nobus Fast Transit console and find Jumbo Frame Capable on the Summary tab.
(Transit virtual interface only) Jumbo frames	The maximum transmission unit (MTU) of packets over Nobus Fast Transit. The default is 1500. Setting the MTU of a virtual interface to 8500 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all interfaces associated with the connection for up to 30 seconds. Jumbo frames apply only to propagated routes from Nobus Fast Transit. If you add static routes to a route table that point to your virtual private gateway, then traffic routed through the static routes is sent using 1500 MTU. To check whether a connection or virtual interface supports jumbo frames, select it in the Nobus Fast Transit console and find Jumbo Frame Capable on the Summary tab.

When you create a virtual interface, you can specify the account that owns the virtual interface. When you choose Nobus account that is not your account, the following rules apply:

For private VIFs and transit VIFs, the account applies to the virtual interface and the virtual private gateway/Fast Transit gateway destination.
For public VIFs, the account is used for virtual interface billing. The Data Transfer Out (DTO) usage is metered toward the resource owner at Nobus Fast Transit data transfer rate.

Creating a virtual interface

You can create a transit virtual interface to connect to a transit gateway, a public virtual interface to connect to public resources (non-Data center services), or a private virtual interface to connect to a Data center.

To create a virtual interface for accounts within your Nobus Organizations, or Nobus Organizations that are different from yours, create a hosted virtual interface. For more information, see Creating a hosted virtual interface.

Creating a public virtual interface

When you create a public virtual interface, it can take up to 72 hours for Nobus to review and approve your request.

To provision a public virtual interface

Open the Nobus Fast Transit console at .
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Public.
Under Public virtual interface settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For VLAN, enter the ID number for your virtual local area network (VLAN).
4. For BGP ASN, enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface.
Under Additional settings, do the following:
1. To configure an IPv4 BGP or an IPv6 peer, do the following:
  
  [IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
  - To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
  - For Nobus router peer IP, enter the IPv4 CIDR address to use to send traffic to Nobus.
  [IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
2. To provide your own BGP key, enter your BGP MD5 key.
  
  If you do not enter a value, Nobus generates a BGP key.
3. To advertise prefixes to Nobus, for Prefixes you want to advertise, enter the IPv4 CIDR destination addresses (separated by commas) to which traffic should be routed over the virtual interface.
4. (Optional) Add or remove a tag.
  
  [Add a tag] Choose Add tag and do the following:
  - For Key, enter the key name.
  - For Value, enter the key value.
  [Remove a tag] Next to the tag, choose Remove tag.
Choose Create virtual interface.
Download the router configuration for your device. For more information, see Downloading the router configuration file.

Creating a private virtual interface

You can provision a private virtual interface to a virtual private gateway in the same place as your Nobus Fast Transit connection.

If you use the Data center wizard to create a Data center, route propagation is automatically enabled for you. With route propagation, routes are automatically populated to the route tables in your Data center. If you choose, you can disable route propagation.

The maximum transmission unit (MTU) of a network connection is the size, in bytes, of the largest permissible packet that can be passed over the connection. The MTU of a virtual private interface can be either 1500 or 9001 (jumbo frames). The MTU of a transit virtual interface can be either 1500 or 8500 (jumbo frames). You can specify the MTU when you create the interface or update it after you create it. Setting the MTU of a virtual interface to 8500 (jumbo frames) or 9001 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all virtual interfaces associated with the connection for up to 30 seconds. To check whether a connection or virtual interface supports jumbo frames, select it in the Nobus Direct Connect console and find Jumbo Frame Capable on the Summary tab.

To provision a private virtual interface to a Data center

Open the Nobus Fast Transit console at .
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Private.
Under Private virtual interface settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For Gateway type, choose Virtual private gateway, or Fast Transit gateway.
4. For Virtual interface owner, choose Another Nobus account, and then enter the Nobus account.
5. For Virtual private gateway, choose the virtual private gateway to use for this interface.
6. For VLAN, enter the ID number for your virtual local area network (VLAN).
7. For BGP ASN, enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface.
Under Additional Settings, do the following:
1. To configure an IPv4 BGP or an IPv6 peer, do the following:
  
  [IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
  - To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
  - For Nobus router peer ip, enter the IPv4 CIDR address to use to send traffic to Nobus.
  [IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
2. To change the maximum transmission unit (MTU) from 1500 (default) to 9001 (jumbo frames), select Jumbo MTU (MTU size 9001).
3. (Optional) Add or remove a tag.
  
  [Add a tag] Choose Add tag and do the following:
  - For Key, enter the key name.
  - For Value, enter the key value.
  [Remove a tag] Next to the tag, choose Remove tag.
Choose Create virtual interface.
Download the router configuration for your device. For more information, see Downloading the router configuration file.

Creating a transit virtual interface to the Fast Transit gateway

To connect your Nobus Fast Transit connection to the transit gateway, you must create a transit interface for your connection. Specify the Fast Transit gateway to which to connect.

If you associate your transit gateway with one or more Fast Transit gateways, the Autonomous System Number (ASN) used by the transit gateway and the Fast Transit gateway must be different. For example, if you use the default ASN 64512 for both the transit gateway and the Fast Transit gateway, the association request fails.

To provision a transit virtual interface to a Fast Transit gateway

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/ .
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Transit.
Under Transit virtual interface settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For Virtual interface owner, choose My Nobus account if the virtual interface is for your Nobus account.
4. For Fast Transit gateway, select the Fast Transit gateway.
5. For VLAN, enter the ID number for your virtual local area network (VLAN).
6. For BGP ASN, enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface.
Under Additional Settings, do the following:
1. To configure an IPv4 BGP or an IPv6 peer, do the following:
  
  [IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
  - To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
  - For Nobus router peer ip, enter the IPv4 CIDR address to use to send traffic to Nobus.
  [IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
2. To change the maximum transmission unit (MTU) from 1500 (default) to 8500 (jumbo frames), select Jumbo MTU (MTU size 8500).
3. (Optional) Add or remove a tag.
  
  [Add a tag] Choose Add tag and do the following:
  - For Key, enter the key name.
  - For Value, enter the key value.
  [Remove a tag] Next to the tag, choose Remove tag.
Choose Create virtual interface.

After you create the virtual interface, you can download the router configuration for your device. For more information, see Downloading the router configuration file.

Downloading the router configuration file

After you create the virtual interface, you can download the router configuration file for your router.

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/ .
In the navigation pane, choose Virtual Interfaces.
Select the virtual interface and then choose View details.
Choose Download router configuration.
For Download router configuration, do the following:
1. For Vendor, select the manufacturer of your router.
2. For Platform, select the blueprint of your router.
3. For Software, select the software version for your router.
Choose Download, and then use the appropriate configuration for your router to ensure that you can connect to Nobus Fast Transit.

Example router configuration files

The following are example extracts of router configuration files.

Cisco IOS


                            interface GigabitEthernet0/1
                                no ip address

                                interface GigabitEthernet0/1.VLAN_NUMBER
                                description "Fast Transit to your Nobus Data center or Nobus Cloud"
                                encapsulation dot1Q VLAN_NUMBER
                                ip address YOUR_PEER_IP

                                router bgp CUSTOMER_BGP_ASN
                                neighbor Nobus_PEER_IP remote-as Nobus_ASN
                                neighbor Nobus_PEER_IP password MD5_key
                                network 0.0.0.0 
                                exit

                                ! Optionally configure Bidirectional Forwarding Detection (BFD).

                                interface GigabitEthernet0/1.VLAN_NUMBER 
                                bfd interval 300 min_rx 300 multiplier 3 
                                router bgp CUSTOMER_BGP_ASN 
                                neighbor Nobus_PEER_IP fall-over bfd 

                                ! NAT Configuration for Public interfaces (Optional)

                                ip access-list standard NAT-ACL
                                permit (internal subnet IP address for NAT)
                                exit

                                ip nat inside source list NAT-ACL interface GigabitEthernet0/1.VLAN_NUMBER overload

                                interface GigabitEthernet0/1.VLAN_NUMBER
                                ip nat outside
                                exit

                                interface interface-towards-customer-local-network
                                ip nat inside
                                exit

Cisco NX-OS


                              feature interface-vlan
                                vlan VLAN_NUMBER
                                name "Fast Transit to your Nobus Data center or Nobus Cloud"

                                interface VlanVLAN_NUMBER
                                  ip address YOUR_PEER_IP/30
                                  no shutdown

                                interface Ethernet0/1
                                  switchport
                                  switchport mode trunk
                                  switchport trunk allowed vlan VLAN_NUMBER
                                  no shutdown

                                router bgp CUSTOMER_BGP_ASN
                                  address-family ipv4 unicast
                                    network 0.0.0.0
                                  neighbor Nobus_PEER_IP remote-as Nobus_ASN
                                    password 0 MD5_key
                                    address-family ipv4 unicast

                                ! Optionally configure Bidirectional Forwarding Detection (BFD).

                                feature bfd
                                interface VlanVLAN_NUMBER
                                no ip redirects
                                bfd interval 300 min_rx 300 multiplier 3
                                router bgp CUSTOMER_BGP_ASN
                                neighbor Nobus_PEER_IP remote-as Nobus_ASN
                                bfd

                                ! NAT Configuration for Public interfaces (Optional)

                                ip access-list standard NAT-ACL
                                permit any any
                                exit

                                ip nat inside source list NAT-ACL VlanVLAN_NUMBER overload

                                interface VlanVLAN_NUMBER
                                ip nat outside
                                exit

                                interface interface-towards-customer-local-network
                                ip nat inside
                                exit

Juniper JunOS


                              configure exclusive
                                edit interfaces ge-0/0/1
                                set description "Fast Transit to your Nobus Data center or Nobus Cloud"
                                set flexible-vlan-tagging
                                set mtu 1522
                                edit unit 0
                                set vlan-id VLAN_NUMBER
                                set family inet mtu 1500
                                set family inet address YOUR_PEER_IP
                                top

                                edit policy-options policy-statement EXPORT-DEFAULT
                                edit term DEFAULT
                                set from route-filter 0.0.0.0/0 exact
                                set then accept
                                up
                                edit term REJECT
                                set then reject
                                top

                                set routing-options autonomous-system CUSTOMER_BGP_ASN

                                edit protocols bgp group EBGP
                                set type external
                                set peer-as Nobus_ASN

                                edit neighbor Nobus_PEER_IP
                                set local-address YOUR_PEER_IP
                                set export EXPORT-DEFAULT
                                set authentication-key "MD5_key"
                                top
                                commit check
                                commit and-quit

                                # Optionally configure Bidirectional Forwarding Detection (BFD).

                                set protocols bgp group EBGP neighbor Nobus_PEER_IP bfd-liveness-detection minimum-interval 300 
                                set protocols bgp group EBGP neighbor Nobus_PEER_IP bfd-liveness-detection multiplier 3

                                # NAT Configuration for Public interfaces (Optional)

                                set security policies from-zone trust to-zone untrust policy PolicyName match source-address any
                                set security policies from-zone trust to-zone untrust policy PolicyName match destination-address any
                                set security policies from-zone trust to-zone untrust policy PolicyName match application any
                                set security policies from-zone trust to-zone untrust policy PolicyName then permit

                                set security nat source rule-set SNAT-RS from zone trust
                                set security nat source rule-set SNAT-RS to zone untrust
                                set security nat source rule-set SNAT-RS rule SNAT-Rule match source-address 0.0.0.0/0
                                set security nat source rule-set SNAT-RS rule SNAT-Rule then source-nat interface

                                commit check
                                commit and-quit

Viewing virtual interface details

You can view the current status of your virtual interface. Details include:

Connection state
Name
point
VLAN
BGP details
Peer IP addresses

To view details about a virtual interface

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the left pane, choose interfaces.
Select the virtual interface and then choose View details.

Adding or deleting a BGP peer

In some points, a virtual interface can support up to two IPv4 BGP peering sessions and up to two IPv6 BGP peering sessions. In other points, a virtual interface can support a single IPv4 BGP peering session and a single IPv6 BGP peering session.

You cannot specify your own peer IPv6 addresses for an IPv6 BGP peering session. Nobus automatically allocates you a /125 IPv6 CIDR.

Multiprotocol BGP is not supported. IPv4 and IPv6 operate in dual-stack mode for the virtual interface.

Adding a BGP peer

Use the following procedure to add a BGP peer.

To add a BGP peer

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Virtual Interfaces.
Select the virtual interface and then choose View details.
Choose Add peering.
(Private virtual interface) To add IPv4 BGP peers, do the following:
- Choose IPv4.
- To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic. For Nobus router peer ip, enter the IPv4 CIDR address to use to send traffic to Nobus.
(Public virtual interface) To add IPv4 BGP peers, do the following:
- For Your router peer ip, enter the IPv4 CIDR destination address where traffic should be sent.
- For Nobus router peer IP, enter the IPv4 CIDR address to use to send traffic to Nobus.
(Private or public virtual interface) To add IPv6 BGP peers, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses; you cannot specify custom IPv6 addresses.
For BGP ASN, enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface.

For a public virtual interface, the ASN must be private or already whitelisted for the virtual interface.

Note that if you do not enter a value, Nobus automatically assigns one.
To provide your own BGP key, for BGP Authentication Key, enter your BGP MD5 key.
Choose Add peering.

Deleting a BGP peer

If your virtual interface has both an IPv4 and IPv6 BGP peering session, you can delete one of the BGP peering sessions (but not both).

To delete a BGP peer

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Virtual Interfaces.
Select the virtual interface and then choose View details.
Under Peerings, select the peering that you want to delete and then choose Delete.
In the Remove peering from virtual interface dialog box, choose Delete.

Setting network MTU for private virtual interfaces or transit interfaces

Nobus Fast Transit supports an Ethernet frame size of 1522 or 9023 bytes (14 bytes Ethernet header + 4 bytes VLAN tag + bytes for the IP datagram + 4 bytes FCS) at the link layer.

The maximum transmission unit (MTU) of a network connection is the size, in bytes, of the largest permissible packet that can be passed over the connection. The MTU of a virtual private interface can be either 1500 or 9001 (jumbo frames). The MTU of a transit virtual interface can be either 1500 or 8500 (jumbo frames). You can specify the MTU when you create the interface or update it after you create it. Setting the MTU of a virtual interface to 8500 (jumbo frames) or 9001 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all interfaces associated with the connection for up to 30 seconds. To check whether a connection or virtual interface supports jumbo frames, select it in the Nobus Fast Transit console and find Jumbo Frame Capable on the Summary tab.

After you enable jumbo frames for your private virtual interface, you can only associate it with a connection or LAG that is jumbo frame capable. Jumbo frames are supported on virtual private interfaces attached to a virtual private gateway or a Fast Transit gateway. Jumbo frames apply only to propagated routes from Nobus Fast Transit. If you add static routes to your virtual private gateway , traffic that is routed through the static route defaults to 1500 MTU. If you have two private interfaces that advertise the same route but use different MTU values, 1500 MTU is used.

Jumbo frames apply only to propagated routes from Nobus Fast Transit . If you add static routes to a route table that point to your virtual private gateway, then traffic routed through the static routes is sent using 1500 MTU.

To set the MTU of a private virtual interface

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose interfaces.
Select the virtual interface and then choose Edit.
Under Jumbo MTU (MTU size 9001) or Jumbo MTU (MTU size 8500), select Enabled.
Under Acknowledge, select I understand the selected connection(s) will go down for a brief period. The state of the virtual interface is pending until the update is complete.

Deleting interfaces

Delete one or more interfaces. Before you can delete a connection, you must delete its virtual interface. Deleting a virtual interface stops Nobus Fast Transit data transfer charges associated with the virtual interface.

To delete a virtual interface

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the left pane, choose interfaces.
Select the interfaces and then choose Delete.
In the Delete confirmation dialog box, choose Delete.

Creating a hosted virtual interface

You can create a public, transit or private hosted virtual interface. Before you begin, ensure that you have read the information in Prerequisites for interfaces.

Creating a hosted private virtual interface

To create a hosted private virtual interface

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Private.
Under Private virtual interface settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For Gateway type, choose Virtual private gateway, or Fast Transit gateway.
4. For Virtual interface owner, choose Another Nobus account, and then enter the Nobus account.
5. For Virtual private gateway, choose the virtual private gateway to use for this interface.
6. For VLAN, enter the ID number for your virtual local area network (VLAN).
7. For BGP ASN, enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface.
Under Additional Settings, do the following:
1. To configure an IPv4 BGP or an IPv6 peer, do the following:
  
  [IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
  - To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
  - For Nobus router peer ip, enter the IPv4 CIDR address to use to send traffic to Nobus.
  [IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
2. To change the maximum transmission unit (MTU) from 1500 (default) to 9001 (jumbo frames), select Jumbo MTU (MTU size 9001).
3. (Optional) Add or remove a tag.
  
  [Add a tag] Choose Add tag and do the following:
  - For Key, enter the key name.
  - For Value, enter the key value.
  [Remove a tag] Next to the tag, choose Remove tag.
Choose Create virtual interface.
After the hosted virtual interface is accepted by the owner of the other Nobus account, you can download the router configuration file.

Creating a hosted public virtual interface

To create a hosted public virtual interface

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Public.
Under Public Virtual Interface Settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For VLAN, enter the ID number for your virtual local area network (VLAN).
4. For BGP ASN, enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface.
Under Additional Settings, for Virtual interface owner, enter the ID of the Nobus account to own this virtual interface.
To configure an IPv4 BGP or an IPv6 peer, do the following:

[IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
- To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
- For Nobus router peer ip, enter the IPv4 CIDR address to use to send traffic to Nobus.
[IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
To advertise prefixes to Nobus, for Prefixes you want to advertise, enter the IPv4 CIDR destination addresses (separated by commas) to which traffic should be routed over the virtual interface.
To provide your own key to authenticate the BGP session, under Additional Settings, for BGP authentication key, enter the key.

If you do not enter a value, then Nobus generates a BGP key.
(Optional) Add or remove a tag.

[Add a tag] Choose Add tag and do the following:
- For Key, enter the key name.
- For Value, enter the key value.
[Remove a tag] Next to the tag, choose Remove tag.
Choose Create virtual interface.
After the hosted virtual interface is accepted by the owner of the other Nobus account, you can download the router configuration file.

Creating a hosted transit virtual interface

To create a hosted transit virtual interface

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Transit.
Under Transit virtual interface settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For Gateway type, choose Direct Connect gateway.
4. For Fast Transit gateway, select the Fast Transit gateway.
5. For VLAN, enter the ID number for your virtual local area network (VLAN).
6. For BGP ASN, enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface.
Under Additional Settings, do the following:
1. To configure an IPv4 BGP or an IPv6 peer, do the following:
  
  [IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
  - To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
  - For Nobus router peer ip, enter the IPv4 CIDR address to use to send traffic to Nobus.
  [IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
2. To change the maximum transmission unit (MTU) from 1500 (default) to 8500 (jumbo frames), select Jumbo MTU (MTU size 8500).
3. [Optional] Add a tag. Do the following:
  
  [Add a tag] Choose Add tag and do the following:
  - For Key, enter the key name.
  - For Value, enter the key value.
  [Remove a tag] Next to the tag, choose Remove tag.
Choose Create virtual interface.
After the hosted virtual interface is accepted by the owner of the other Nobus account, you can download the router configuration file.

Accepting a hosted virtual interface

Before you can begin using a hosted virtual interface, you must accept the virtual interface. For a private virtual interface, you must also have an existing virtual private gateway or Fast Transit gateway. For a transit virtual interface, you must have an existing transit gateway or Fast Transit gateway.

To accept a hosted virtual interface

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose interfaces.
Select the virtual interface and then choose View details.
Choose Accept.
This applies to private interfaces and transit virtual interfaces.

(Transit virtual interface) In the Accept virtual interface dialog box, select a Fast Transit gateway, and then choose Accept virtual interface.

(Private virtual interface) In the Accept virtual interface dialog box, select a virtual private gateway or Direct Connect gateway, and then choose Accept virtual interface.
After you accept the hosted virtual interface, the owner of the Nobus Fast Transit connection can download the router configuration file. The Download router configuration option is not available for the account that accepts the hosted virtual interface.

Working with Fast Transit gateways

You can work with Nobus Fast Transit gateways using the Nobus Data center console or the Nobus CLI.

Contents

Fast Transit gateways
Virtual private gateway associations
Transit gateway associations
Allowed prefixes interactions

Fast Transit gateways

Use Nobus Fast Transit gateway to connect your Data centers. You associate a Nobus Fast Transit gateway with either of the following gateways:

A transit gateway when you have multiple Data centers in the same place
A virtual private gateway

A Fast Transit gateway is a globally available resource. You can create the Fast Transit gateway in any public place and access it from all other public places. You can use a Fast Transit gateway in the following scenarios.

Virtual private gateway associations

In the following diagram, the Fast Transit gateway enables you to use your Nobus Fast Transit connection in the A place to access Data centers in your account in both the A and B places.

Virtual private gateway associations across accounts

Consider this scenario of a Fast Transit gateway owner (Account Z) who owns the Fast Transit gateway. Account A and Account B want to use the Fast Transit gateway. Account A and Account B each send an association proposal to Account Z. Account Z accepts the association proposals and can optionally update the prefixes that are allowed from Account A's virtual private gateway or Account B's virtual private gateway. After Account Z accepts the proposals, Account A and Account B can route traffic from their virtual private gateway to the Fast Transit gateway. Account Z also owns the routing to the customers because Account Z owns the gateway.

Transit gateway associations

The following diagram illustrates how the Fast Transit gateway enables you to create a single connection to your Fast Transit connection that all of your Data centers can use.

The solution involves the following components:

A transit gateway that has Data center attachments.
A Fast Transit gateway.
An association between the Fast Transit gateway and the transit gateway.
A transit virtual interface that is attached to the Fast Transit gateway.

This configuration offers the following benefits. You can:

Manage a single connection for multiple Data centers or VPNs that are in the same place.
Advertise prefixes from on-premises to Nobus and from Nobus to on-premises.

For information about configuring transit gateways, see Working with Transit Gateways in the Nobus Data center Transit Gateways Guide.

Transit gateway associations across accounts

Consider this scenario of a Fast Transit gateway owner (Account Z) who owns the Fast Transit gateway. Account A owns the transit gateway and wants to use the Direct Connect gateway. Account Z accepts the association proposals and can optionally update the prefixes that are allowed from Account A's transit gateway. After Account Z accepts the proposals, The Data centers attached to the transit gateway can route traffic from the transit gateway to the Fast Transit gateway. Account Z also owns the routing to the customers because Account Z owns the gateway.

Contents

Creating a Fast Transit gateway
Deleting Fast Transit gateways
Migrating from a virtual private gateway to a Fast Transit gateway

Creating a Fast Transit gateway

To create a Fast Transit gateway

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Fast Transit Gateways.
Choose Create Fast Transit gateway.
Specify the following information, and choose Create Direct Connect gateway.
- Name: Enter a name to help you identify the Fast Transit gateway.
- Nobus side ASN: Specify the ASN for the Nobus side of the BGP session. The ASN must be in the 64,512 to 65,534 range or 4,200,000,000 to 4,294,967,294 range.
- Virtual private gateway: To associate a virtual private gateway, choose the virtual private gateway.

Deleting Fast Transit gateways

If you no longer require a Fast Transit gateway, you can delete it. You must first disassociate all associated virtual private gateways and delete the attached private virtual interface.

To delete a Fast Transit gateway

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Fast Transit Gateways.
Select the gateways and choose Delete.

Migrating from a virtual private gateway to a Fast Transit gateway

If you had a virtual private gateway attached to a virtual interface, and you want to migrate to a Fast Transit gateway, perform the following steps:

To migrate to a Fast Transit gateway

Create a Fast Transit gateway. For more information, see Creating a Fast Transit gateway.
Create a virtual interface for the Fast Transit gateway. For more information, see Creating a virtual interface.
Associate the virtual private gateway with the Fast Transit gateway. For more information, see Associating and disassociating virtual private gateways.
Delete the virtual interface that was associated with the virtual private gateway. For more information, see Deleting interfaces.

Virtual private gateway associations

You can use an Nobus Fast Transit gateway to connect your Nobus Fast Transit connection over a private virtual interface to one or more Data centers in any account that are located in the same or different places. You associate a Fast Transit gateway with the virtual private gateway for the Data center. Then, you create a private virtual interface for your Nobus Fast Transit connection to the Fast Transit gateway. You can attach multiple private interfaces to your Fast Transit gateway.

The following rules apply to Data center associations:

There are limits for creating and using Fast Transit gateways. For more information, see Nobus Fast Transit quotas.
The Data centers to which you connect through a Fast Transit gateway cannot have overlapping CIDR blocks. If you add an IPv4 CIDR block to a Data center that's associated with a Fast Transit gateway, ensure that the CIDR block does not overlap with an existing CIDR block for any other associated Data center. For more information, see Adding IPv4 CIDR Blocks to a Data center in the Nobus Data center User Guide.
You cannot create a public virtual interface to a Fast Transit gateway.
A Fast Transit gateway supports communication between attached private interfaces and associated virtual private gateways only. The following traffic flows are not supported:
- Direct communication between the Data centers that are associated with a single Fast Transit gateway. This includes traffic from one Data center to another by using a hairpin through an on-premises network through a single virtual interface.
- Direct communication between the interfaces that are attached to a single Fast Transit gateway.
- Direct communication between the interfaces that are attached to a single Fast Transit gateway and a VPN connection on a virtual private gateway that's associated with the same Fast Transit gateway.
You cannot associate a virtual private gateway with more than one Direct Connect gateway and you cannot attach a private virtual interface to more than one Fast Transit gateway.
A virtual private gateway that you associate with a Fast Transit gateway must be attached to a Data center.
A virtual private gateway association proposal expires 7 days after it is created.
An accepted virtual private gateway proposal, or a deleted virtual private gateway proposal remains visible for 3 days.

To connect your Nobus Fast Transit connection to a Data center in the same place only, you can create a Fast Transit gateway. Or, you can create a private virtual interface and attach it to the virtual private gateway for the Data center.

To use your Nobus Fast Transit connection with a Data center in another account, you can create a hosted private virtual interface for that account. When the owner of the other account accepts the hosted virtual interface, they can choose to attach it either to a virtual private gateway or to a Fast Transit gateway in their account. For more information, see Nobus Fast Transit interfaces.

Contents

Associating and disassociating virtual private gateways
Creating a private virtual interface to the Fast Transit gateway
Associating a virtual private gateway across accounts

Associating and disassociating virtual private gateways

The virtual private gateway must be attached to the Data center to which you want to connect. For more information, see Create a Virtual Private Gateway in the Nobus Data center User Guide.

If you are planning to use the virtual private gateway for a Fast Transit gateway and a dynamic VPN connection, set the ASN on the virtual private gateway to the value that you require for the VPN connection. Otherwise, the ASN on the virtual private gateway can be set to any permitted value. The Fast Transit gateway advertises all connected Data centers over the ASN assigned to it.

To associate a virtual private gateway

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Fast Transit Gateways and then select the Fast Transit gateway.
Choose View details.
Choose Gateways associations and then choose Associate gateway.
For Gateways, choose the virtual private gateways to associate, and then choose Associate gateway.

You can view all of the virtual private gateways that are associated with the Fast Transit gateway by choosing Gateway associations.

To disassociate a virtual private gateway

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Fast Transit Gateways and then select the Fast Transit gateway.
Choose View details.
Choose Gateway associations and then select the virtual private gateway.
Choose Disassociate.

Creating a private virtual interface to the Fast Transit gateway

To connect your Nobus Fast Transit connection to the remote Data center, you must create a private virtual interface for your connection. Specify the Fast Transit gateway to which to connect.

If you're accepting a hosted private virtual interface, you can associate it with a Fast Transit gateway in your account.

To provision a private virtual interface to a Fast Transit gateway

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Private.
Under Virtual interface type, choose Private.
Under Private virtual interface settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For Virtual interface owner, choose My Nobus account if the virtual interface is for your Nobus account.
4. For Fast Transit gateway, select the Fast Transit gateway.
5. For VLAN, enter the ID number for your virtual local area network (VLAN).
6. For BGP ASN, enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface.
Under Additional Settings, do the following:
1. To configure an IPv4 BGP or an IPv6 peer, do the following:
  
  [IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
  - To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
  - For Nobus router peer ip, enter the IPv4 CIDR address to use to send traffic to Nobus.
  [IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
2. To change the maximum transmission unit (MTU) from 1500 (default) to 9001 (jumbo frames), select Jumbo MTU (MTU size 9001).
3. (Optional) Add or remove a tag.
  
  [Add a tag] Choose Add tag and do the following:
  - For Key, enter the key name.
  - For Value, enter the key value.
  [Remove a tag] Next to the tag, choose Remove tag.
Choose Create virtual interface.

After you've created the virtual interface, you can download the router configuration for your device. For more information, see Downloading the router configuration file.

Transit gateway associations

You can use an Nobus Fast Transit gateway to connect your Nobus Fast Transit connection over a transit virtual interface to the Data centers or VPNs that are attached to your transit gateway. You associate a Fast Transit gateway with the transit gateway. Then, create a transit virtual interface for your Nobus Fast Transit connection to the Fast Transit gateway.

The following rules apply to transit gateway associations:

You cannot attach a Fast Transit gateway to a transit gateway when the Fast Transit gateway is already associated with a virtual private gateway or is attached to a private virtual interface.
There are limits for creating and using Fast Transit gateways. For more information, see Nobus Fast Transit quotas.
A Fast Transit gateway supports communication between attached transit interfaces and associated transit gateways only.
If you connect to multiple transit gateways that are in different places, use unique ASNs for each transit gateway.
A virtual private gateway can be associated with a Fast Transit gateway and also attached to a virtual interface.

Associating and disassociating transit gateways

To associate a transit gateway

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Fast Transit Gateways and then select the Fast Transit gateway.
Choose View details.
Choose Gateway associations and then choose Associate gateway.
For Gateways, choose the transit gateway to associate, and then choose Associate gateway.

You can view all of the gateways that are associated with the Fast Transit gateway by choosing Gateway associations.

To disassociate a transit gateway

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose Fast Transit gateways and then select the Fast Transit gateway.
Choose View details.
Choose Gateway associations and then select the transit gateway.
Choose Disassociate.

Creating a transit virtual interface to the Fast Transit gateway

To connect your Nobus Fast Transit connection to the transit gateway, you must create a transit interface for your connection. Specify the Fast Transit gateway to which to connect.

To provision a transit virtual interface to a Fast Transit gateway

Open the Nobus Fast Transit console at https://cloud.nobus.io/project/
In the navigation pane, choose interfaces.
Choose Create virtual interface.
Under Virtual interface type, for Type, choose Transit.
Under Transit virtual interface settings, do the following:
1. For Virtual interface name, enter a name for the virtual interface.
2. For Connection, choose the Fast Transit connection that you want to use for this interface.
3. For Virtual interface owner, choose My Nobus account if the virtual interface is for your Nobus account.
4. For Fast Transit gateway, select the Fast Transit gateway.
5. For VLAN, enter the ID number for your virtual local area network (VLAN).
6. For BGP ASN, enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface.
Under Additional Settings, do the following:
1. To configure an IPv4 BGP or an IPv6 peer, do the following:
  
  [IPv4] To configure an IPv4 BGP peer, choose IPv4 and do one of the following:
  - To specify these IP addresses yourself, for Your router peer ip, enter the destination IPv4 CIDR address to which Nobus should send traffic.
  - For Nobus router peer ip, enter the IPv4 CIDR address to use to send traffic to Nobus.
  [IPv6] To configure an IPv6 BGP peer, choose IPv6. The peer IPv6 addresses are automatically assigned from Nobus's pool of IPv6 addresses. You cannot specify custom IPv6 addresses.
2. To change the maximum transmission unit (MTU) from 1500 (default) to 8500 (jumbo frames), select Jumbo MTU (MTU size 8500).
3. (Optional) Add or remove a tag.
  
  [Add a tag] Choose Add tag and do the following:
  - For Key, enter the key name.
  - For Value, enter the key value.
  [Remove a tag] Next to the tag, choose Remove tag.
Choose Create virtual interface.

After you've created the virtual interface, you can download the router configuration for your device. For more information, see Downloading the router configuration file.

Allowed prefixes interactions

Learn how allowed prefixes interact with transit gateways and virtual private gateways.

Transit gateway associations

When you associate a transit gateway with a Fast Transit gateway, you specify a list of up to twenty Nobus Data center prefixes to advertise to the Fast Transit gateway. The prefix list acts as a filter that allows the same CIDRs, or a smaller range of CIDRs to be advertised to the Fast Transit gateway. You must set the prefixes to a range that is the same or wider than the Data center CIDR block.

Consider the scenario where you have a Data center with CIDR 10.0.0.0/16 attached to a transit gateway.

When the allowed prefixes list is set to 22.0.0.0/24, you receive 22.0.0.0/24 through BGP on your transit virtual interface. You do not receive 10.0.0.0/16 because we directly provision the prefixes that are in the allowed prefix list.
When the allowed prefixes list is set to 10.0.0.0/24, you receive 10.0.0.0/24 through BGP on your transit virtual interface. You do not receive 10.0.0.0/16 because we directly provision the prefixes that are in the allowed prefix list.
When the allowed prefixes list is set to 10.0.0.0/8, you receive 10.0.0.0/8 through BGP on your transit virtual interface. You do not receive 10.0.0.0/16 because we directly provision the prefixes that are in the allowed prefix list.

Virtual private gateway associations

Consider the scenario where you have a Data center with CIDR 10.0.0.0/16 is attached to a virtual private gateway.

When the allowed prefixes list is set to 22.0.0.0/24, you do not receive any route because 22.0.0.0/24 is not the same as, or wider than 10.0.0.0/16.
When the allowed prefixes list is set to 10.0.0.0/24, you do not receive any route because 10.0.0.0/24 is not the same as 10.0.0.0/16.
When the allowed prefixes list is set to 10.0.0.0/15, you do receive 10.0.0.0/16, because the IP address is wider than 10.0.0.0/16.

Accounts

Sign In

Register

How To Configure SSH Key-Based Authentication on Linux and Windows Server Tutorial

Haproxy load balancer Configurations Tutorial

What Is Nobus Fast Transit?

Components Nobus Fast Transit

Minimum network requirements

Pricing for Nobus Fast Transit

Using the Fast Transit Toolkit to get started

Step 1: Sign up for Nobus

Step 2: Configure the blueprint

Step 3: Create your virtual interfaces

Step 4: Verify your interfaces

Classic

Prerequisites

Step 1: Sign up for Nobus

Step 2: Request Nobus Fast Transit dedicated connection or accept a hosted connection

Accept your hosted connection

(Dedicated connection) step 3: Download the LOA-CFA

Step 4: Create a virtual interface

Step 5: Download the router configuration

Step 6: Verify your virtual interface

Nobus Fast Transit connections

Dedicated connections

Hosted connections

Creating a connection

Downloading the LOA-CFA

Viewing connection details

Updating a connection

Deleting connections

Accepting a hosted connection

Requesting cross connects at Nobus Fast Transit points

Nobus Fast Transit interfaces

Public virtual interface prefix advertisement rules

Hosted interfaces

Prerequisites for interfaces

Creating a virtual interface

Creating a public virtual interface

Creating a private virtual interface

Creating a transit virtual interface to the Fast Transit gateway

Downloading the router configuration file

Example router configuration files

Viewing virtual interface details

Adding or deleting a BGP peer

Adding a BGP peer

Deleting a BGP peer

Setting network MTU for private virtual interfaces or transit interfaces

Deleting interfaces

Creating a hosted virtual interface

Creating a hosted private virtual interface

Creating a hosted public virtual interface

Creating a hosted transit virtual interface

Accepting a hosted virtual interface

Working with Fast Transit gateways

Fast Transit gateways

Virtual private gateway associations

Virtual private gateway associations across accounts

Transit gateway associations

Transit gateway associations across accounts

Creating a Fast Transit gateway

Deleting Fast Transit gateways

Migrating from a virtual private gateway to a Fast Transit gateway

Virtual private gateway associations

Associating and disassociating virtual private gateways

Creating a private virtual interface to the Fast Transit gateway

Transit gateway associations

Associating and disassociating transit gateways

Creating a transit virtual interface to the Fast Transit gateway

Allowed prefixes interactions

Transit gateway associations

Virtual private gateway associations

Accounts

Sign In

Register

Related