Contents

General Information

This section provides information on basic aspects of configuring an Ethernet interface for the emulator. For details on the configuration parameters used and for additional parameters, please refer to the Configuration File Reference.

The emulated Ethernet interfaces of Charon-PAR can be linked either to a

• physical host interface, or

• to a TAP interface on the host.

Notes for TAP interfaces:

• A TAP interface can either be created by the user or will be created automatically by the emulator if it does not already exist.

• For automatically created TAP interfaces, the user can specify a name or let the emulator select a name.

• A automatically created TAP interface is not automatically added to a bridge, this must be configured via the initialize_command.

• An automatically created TAP interface is deleted automatically upon emulator stop.

By default, emulated models have one Ethernet device. Depending on the model, more Ethernet devices can be added.

The emulated network devices

• DE 500 PCI based cards (for 64-bit systems), and

• LASI-82596 cards (for the 32-bit system)

do not support Jumbo frames. For physical interfaces, this feature must be disabled in the emulator configuration (together with any other offloading parameters) using the initialize_command parameter.

Basic Configuration Components

Ethernet Interface Names

Names on 64-bit systems:

The name of the Ethernet interface in the emulator configuration file has the format EWXN with the following definitions:

• X  - an uppercase letter starting with A for the first interface and then continues with B, C, etc. for additional interfaces. The possible number of network cards depends on the features of the original physical system. The absolute maximum number is 16.

• N - the device number of the card starting with 0 for each value of x.

Names on 32-bit systems:

The currently supported 32-bit system supports only one Ethernet card named system.lan0.card.

Minimal Configuration Parameters

The configuration of each network interface must at least have two basic components as shown below:

64-bit system (example shows the first Ethernet card EWA0):

• Interface definition (EWA0.iface)

• Interface initialization command: (EWA0.initialize_command)

32-bit system:

• Interface definition (system.lan0.card.iface)

• Interface initialization command: (system.lan0.card.initialize_command)

The default configuration assumes that a physical network interface will be used.

Please refer to the Configuration File Reference and the configuration template of your model for more information.

Basic Configuration Example

Example of a basic network card configuration using a physical interface on a 64-bit emulated system:

The variable IFACE is set automatically by the emulator upon start. The initialize_command parameter is used to turn off all relevant offloading parameters on the interface used by the emulator.

Adding Additional Emulated Network Cards

Please note: if / how many additional Ethernet controllers can be loaded depends on the emulated model.

This section will show an example. Please refer to the section I/O Slot Configuration in the Configuration File Reference chapter and the Emulated Model Hardware Configuration Details chapter for details.

To add an additional Ethernet controller to your emulator configuration, you must perform the following steps:

• Identify a free PCI slot (model configuration template or Emulated Model Hardware Configuration Details).

• Add a load command to the configuration to load an Ethernet module into the identified emulator slot (see the Configuration File Reference chapter for details).

• Add the network card configuration to your configuration file.

• Start the emulator and configure the interface in the guest system.

Step 1: identify a free PCI slot for your emulated model. The available slots depend on your model and the existing configuration.

Step 2: Add the load command for the Ethernet module to the configuration file.

Step 3: Add the network card configuration to your configuration file selecting the correct host interface name (example: eth2). Note that the name of the second emulated interface is EWB0.

Example (important: the initialization command must be in one continuous line):

Step 4: Start the emulator, boot the guest system and configure the second interface.

• On PA3, use the ISL > ODE > RUN MAPPER2 command (access from console via: Interaction with IPL) to verify the existence of the new interface and the correct device path.

• The above command also works on PA9, but on HP-UX you can also use the lanscan command to verify the existence of the new interface (on HP-UX it is normally lan1).

• Configure the interface.

  • The easiest way on HP-UX is to use SAM > Network and Communication > Network Interface Cards (Actions > Configure).

  • On MPE/iX, the interface must be added via NMMGR (for interactive use, xhpterm can be used to access this tool), and the interface must be started using the NETCONTROL command. Please refer to the documentation of your operating system for further information.

The following image shows a sample of a HP-UX system with two Ethernet interfaces:

Open

The following shows a sample of the second Ethernet interface being configured on device path 0/8/0/0:

Open

On an MPE/iX system, the device path is needed to configure the new network link.

The following shows a sample of two active Ethernet interfaces on MPE/iX: