Creating Private Megaport Connections for Juniper MX and EX Devices

This topic describes how to create a private point-to-point connection between a Juniper MX device and a Juniper EX device on the Megaport network.

Topology

Juniper device topology

Prerequisites

Before proceeding, ensure you have the following:

A Port established in two locations with a Live status, connected with fully deployed Virtual Cross Connects (VXCs). If you haven’t already created a Port, see Creating a Port.
Layer 2 or Layer 3 switches on each end terminating the physical connections.
802.1q trunking enabled on the two links connecting into Megaport.

Deploying a private VXC

This section describes the configuration process on the Megaport side, using the Megaport Portal.

To deploy a private VXC

In the Megaport Portal, go to the Services page and select the originating A-End Port.
Click +Connection.
Click Private VXC.
Select the target Port (the B-End).
Click Next.
Specify the connection details:
- Connection Name – The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable. You can change the name later, if you like.
- Service Level Reference (optional) – Specify a unique identifying number for the VXC to be used for billing purposes, such as a cost center number or a unique customer ID. The service level reference number appears for each service under the Product section of the invoice. You can also edit this field for an existing service.
- Rate Limit – The speed of your connection in Mbps. The maximum speed is displayed. The maximum speed available is limited to the smallest of the originating or destination port.
- VXC State – Select Enabled or Shut Down to define the initial state of the connection. For more information, see Shutting Down a VXC for Failover Testing.
  
  Note
  
  If you select Shut Down, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
- Preferred A-End VLAN – Specify the 802.1q VLAN tag for this connection that you will receive via the A-End VLAN.
- Preferred B-End VLAN – Specify the 802.1q VLAN tag for this connection that you will receive via the B-End VLAN.
  
  The VLAN tags on each end do not have to be the same. This example uses VLAN 3000 on each end of the transport connection between Dallas and Seattle.
- Minimum Term – Select No Minimum Term, 12 Months, 24 Months, or 36 Months. Longer terms result in a lower monthly rate. 12 Months is selected by default.
  Take note of the information on the screen to avoid early termination fees (ETF). See VXC Pricing and Contract Terms and VXC, Megaport Internet, and IX Billing for more information.
Click Add VXC to save the VXC.
Click Order and proceed through the ordering process.

When the VXC is deployed, you can view it in the Portal Services page.

Now that the Megaport side of the configuration is complete, you need to configure the Juniper devices on each end of the circuit.

Configuring the Juniper devices on each end of the circuit

The example uses a supported maximum transmission unit (MTU) of 9100 on the trunk port. MTU is optional. See the results of different MTU settings in Testing the MTU Settings.

To configure the Juniper devices

Configure the Juniper MX80 router located in Dallas like this:

set bridge-domains VL-3000-DAL-SEA vlan-id 3000   
set interfaces xe-1/1/0 description "MP1-10G L2 Port"
set interfaces xe-1/1/0 vlan-tagging    
set interfaces xe-1/1/0 mtu 9100  
set interfaces xe-1/1/0 unit 3000 description MP-DAL-SEA   
set interfaces xe-1/1/0 unit 3000 vlan-id 3000
set interfaces xe-1/1/0 unit 3000 family inet address 10.10.1.1/30

Configure the Juniper EX4600 device located in Seattle like this:

set vlans VL-3000-DAL-SEA vlan-id 3000  
set interfaces xe-0/0/46 description "Megaport SEA-10G"  
set interfaces xe-0/0/46 vlan-tagging  
set interfaces xe-0/0/46 mtu 9100  
set interfaces xe-0/0/46 unit 3000 description MP-DAL-SEA  
set interfaces xe-0/0/46 unit 3000 vlan-id 3000  
set interfaces xe-0/0/46 unit 3000 family inet address 10.10.1.2/30

Testing the MTU settings - Dallas to Seattle

This section shows how different MTU settings work on the configuration from Dallas to Seattle.

###Using 9100 MTU
maverick@BB1-EQ# run ping 10.10.1.2 size 9100 do-not-fragment  
PING 10.10.1.2 (10.10.1.2): 9100 data bytes  
ping: sendto: Message too long  
ping: sendto: Message too long  
ping: sendto: Message too long  
ping: sendto: Message too long  
^C  
--- 10.10.1.2 ping statistics ---  
4 packets transmitted, 0 packets received, 100% packet loss

Using 9055 MTU

maverick@BB1-EQ# run ping 10.10.1.2 size 9055 do-not-fragment  
PING 10.10.1.2 (10.10.1.2): 9055 data bytes  
ping: sendto: Message too long  
ping: sendto: Message too long  
ping: sendto: Message too long  
ping: sendto: Message too long  
^C  
--- 10.10.1.2 ping statistics ---  
4 packets transmitted, 0 packets received, 100% packet loss

Using 9054 MTU: Success

maverick@BB1-EQ# run ping 10.10.1.2 size 9054 do-not-fragment  
PING 10.10.1.2 (10.10.1.2): 9054 data bytes  
9062 bytes from 10.10.1.2: icmp_seq=0 ttl=64 time=60.443 ms  
9062 bytes from 10.10.1.2: icmp_seq=1 ttl=64 time=62.667 ms  
9062 bytes from 10.10.1.2: icmp_seq=2 ttl=64 time=57.640 ms  
9062 bytes from 10.10.1.2: icmp_seq=3 ttl=64 time=65.529 ms  
9062 bytes from 10.10.1.2: icmp_seq=4 ttl=64 time=67.623 ms  
^C  
--- 10.10.1.2 ping statistics ---  
5 packets transmitted, 5 packets received, 0% packet loss  
round-trip min/avg/max/stddev = 57.640/64.212/71.371/4.553 ms

Testing the MTU settings - Seattle to Dallas

This section shows how different MTU settings work on the configuration from Seattle to Dallas.

Using 9100 MTU

maverick@BB1-EQ# run ping 10.10.1.2 size 9100 do-not-fragment  
PING 10.10.1.2 (10.10.1.2): 9100 data bytes  
ping: sendto: Message too long  
ping: sendto: Message too long  
ping: sendto: Message too long  
ping: sendto: Message too long  
^C  
--- 10.10.1.2 ping statistics ---  
4 packets transmitted, 0 packets received, 100% packet loss

Using 9055 MTU

maverick@BB1-EQ# run ping 10.10.1.2 size 9055 do-not-fragment  
PING 10.10.1.2 (10.10.1.2): 9055 data bytes  
ping: sendto: Message too long  
ping: sendto: Message too long  
^C 
--- 10.10.1.2 ping statistics ---  
4 packets transmitted, 0 packets received, 100% packet loss

Using 9054 MTU: Success

maverick@BB1-EQ# run ping 10.10.1.2 size 9054 do-not-fragment  
PING 10.10.1.2 (10.10.1.2): 9054 data bytes  
9062 bytes from 10.10.1.2: icmp_seq=0 ttl=64 time=60.443 ms  
9062 bytes from 10.10.1.2: icmp_seq=1 ttl=64 time=62.667 ms  
9062 bytes from 10.10.1.2: icmp_seq=2 ttl=64 time=57.640 ms  
9062 bytes from 10.10.1.2: icmp_seq=3 ttl=64 time=65.529 ms  
9062 bytes from 10.10.1.2: icmp_seq=4 ttl=64 time=67.623 ms  
^C    
--- 10.10.1.2 ping statistics ---    
5 packets transmitted, 5 packets received, 0% packet loss    
round-trip min/avg/max/stddev = 57.640/64.212/71.371/4.553 ms

Last update: 2024-04-15