-
Networking requirements
Your PromethION can use copper or fibre interfaces for connecting to your local infrastructure. The type of port is labelled on the diagram of the back of the PromethION below:
This connection will be used for:
- Sending telemetry* information to Oxford Nanopore Technologies
- Receiving software and firmware updates to the device
- Streaming biological sequence data to your local storage infrastructure
To implement the PromethION into the local infrastructure, *all appropriate cabling must be provided by the customer.
* Telemetry contains metadata about the settings and conditions of a sequencing run. Nothing specific about the genomic content of individual reads is included - only generic information is logged, such as sequence length and q-score.
-
Copper or fibre data transfer connections can be used - but not both.
You can run with copper or fibre connections for your data transfer. We do not recommend one over the other, however, it is down to your local network environment for which connectivity you may prefer to use.
Note: Please only attach copper or fibre cables. Using both is not supported and will cause networking issues.
A summary of the connectivity options is shown in the diagram below. Please consult the instructions below to ensure the PromethION network connections are set up correctly.
-
Instructions for setting up a copper connection
-
Single copper port on DHCP service
- Open a Terminal window and enter the following command:
ont-network-settings --dhcp --interfaces eno2 --overwrite
2. Power cycle the PromethION.Connections:
Use only the lower RJ45 port for this configuration.
-
Dual copper ports on DHCP service
- Open a Terminal window and enter the following command:
ont-network-settings --dhcp --interfaces copper --bond failover --overwrite
2. Power cycle the PromethION.Note: If using LACP/Cisco/802.3ad, then enter:
--bond lacp
Connections:
Use both RJ45 ports for this configuration.
-
Dual copper ports with a static IP address
- Open a Terminal window and enter the following command:
ont-network-settings --address 1.1.1.1 --subnet 255.255.255.0 --gateway 1.1.1.254 --dns 1.1.1.2,1.1.1.3 --search mycompany.local --bond failover --interfaces copper --overwrite
2. Power cycle the PromethION.Note: You must change the IP addresses above according to your site's network configuration.
Connections:
Use both RJ45 ports for this configuration; however, the configuration will also function with only the bottom port occupied.
-
Instructions for setting up a fibre connection
-
Single fibre port on DHCP service
- Open a Terminal window and enter the following command:
ont-network-settings --dhcp --interfaces enp129s0f1 --overwrite
2. Power cycle the PromethION.Connections:
Use the right fibre port for this configuration: -
Dual fibre ports on DHCP service
- Open a Terminal window and enter the following command:
ont-network-settings --dhcp --interfaces fibre --bond failover --overwrite
2. Power cycle the PromethION.Note: If using LACP/Cisco/802.3ad, then enter:
--bond lacp
Connections:
Use both fibre ports for this configuration.
- Open a Terminal window and enter the following command:
-
Dual fibre ports with a static IP address
- Open a Terminal window and enter the following command:
ont-network-settings --address 1.1.1.1 --subnet 255.255.255.0 --gateway 1.1.1.254 --dns 1.1.1.2,1.1.1.3 --search mycompany.local --bond failover --interfaces fibre --overwrite
2. Power cycle the PromethION.Note: You must change the IP addresses above according to your site's network configuration.
Connections:
Use both fibre ports for this configuration; however, the configuration will also function with only the right port port occupied.
-
Validate the IP address
You can use the command:
ifconfig
to validate that the IP address has been set correctly using a static or DHCP address.The returned information will contain the IP address for the Ethernet link, as below:
prom@PRO00001:~$ ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:35:39:60:40 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.150.60.13 netmask 255.255.255.0 broadcast 10.150.60.255
inet6 fe80::78cf:8a5c:26ec:4611 prefixlen 64 scopeid 0x20<link>
ether 3c:7c:3f:be:02:81 txqueuelen 1000 (Ethernet)