Network Ports

The following provides information on the SEE network ports.

The SEE provides the following pre-configured (active) network ports. 


Provides SSH access to the Secure Foundation Platform (SFP) (hypervisor) when the x86 mainboard has been powered on.

Use the private SSH key provided with the SEE delivery since there is no SSH password access to the SFP.


Provides a virtual switch (bridge) connected to the virtual machine(s). The SFP uses the Open vSwitch software to configure the bridge. Your application will require network access. Note that two additional (physical) ports ETH2 and ETH3 can be used for network traffic to and from your application.

Apart from configuring a bridge (virtual switch), you can configure the virtual machine (executing your application) to use port forwarding or to pass the physical network port to the virtual machine. However, using the pre-configured bridge hspbr1 is recommended.


Provides SSH to the PiLO ARM board. The default user name and password are both root. There are currently no security issues with direct access to the PiLO but it is recommended to specify a new secure password when you first log into the PiLO.

Your PiLO access may have been secured by allowing only public key authentication for ssh access. If this is the case, then the PiLO shh private key will have been delivered along with the ssh SFP private key.

Location of Network Ports

The following displays the location of the network ports.

  • ETH0, ETH1, and MGMT ports are pre-configured upon delivery and are possible to re-configure.
  • ETH2 and ETH3 ports are not pre-configured and can be configured. 
  • The right-most port is unused and not connected to any device and is reserved for future use. 

Next, for information on how to power on the SEE and access PrimeKey’s integrated Lights On (PiLO), see Power On the SEE.