Versions Compared

Old Version 4

changes.mady.by.user Kirill Nikolaev (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Kirill Nikolaev (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
TopNetPage
TopNetPage
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

All the emulated controllers are loaded and configured in the same way.

(warning)(warning) The Ethernet adapter in the Windows host system must support dynamic changes of its MAC address (i.e. no reboot of the host system is required to change the MAC address), which is the case with nearly all modern Ethernet adapters.

(info) By default the PCI Ethernet adapters use first available PCI slot. If instead some particular slot is needed, refer to this section for details of specific placement of PCI peripherals on CHARON-AXP PCI bus.

Div
classpagebreak

 

Configuration steps

To configure CHARON-AXP networking, follow these 3 steps:

  1. Load network adapter (if required)

    Use the "load" command as shown below.

    Example:

    For DEC21040 adaptersFor Intel i8255x adapters


    load DE500BA/dec21x4x NIC



    load DE602/i8255x NIC



    Note

    In AlphaStation 400 configuration use the following syntax for network adapter loading:

    load DE500AA/dec21x4x NIC irq_bus=isa



    (info)(info) By default each loaded virtual network adapter uses first available PCI slot. If instead some particular slot is neded, r    efer to this section for details of specific placement of PCI peripherals on CHARON-AXP PCI bus.

  2. Load "packet_port"

    Load "packet_port" to connect network adapter to the host hardware network card (or to a virtual network interface).

    Example:

    load packet_port/chnetwrk NDIS interface = "connection:Charon"
               


  3. Connect the loaded "packet_port" to the loaded virtual network adapter

    Connect the network adapter to the "packet_port" by setting the interface name.

    Example: 

    set NIC interface = NDIS


Back to Table of Contents

...

Each virtual network controller has the following parameters that are specified with the "set" command:

interface

Parameterinterface
Type

Value

interface

Text String

Value

Name of the corresponding instance of the "packet_port" component

station_address

Parameterstation_address
Type

Text String

Value

The "station_address" provides the ability to configure the adapter’s permanent address. By default the adapter’s permanent address is read from the host system’s NIC

.Set the "station_address" when you need to configure a satellite (remotely booted) system that will run DECnet or when the migrated software uses the permanent address on the network adapter

.

Format:

XX-XX-XX-XX-XX-XX

or

XX:XX:XX:XX:XX:XX

Example:

 

set EWA station_address="AF:01:AC:78:1B:CC"


rx_fifo_size

Parameter

rx_fifo_size

TypeNumeric
Value

"rx_fifo_size" sets the receive FIFO size.

The value is specified in Kb and, by default, is pre-calculated from the connected port’s size of the receive queue.

Typically, you do not need to change the "rx_fifo_size" parameter. It is available for extended tuning and debugging purposes.

adapter_mode

Parameteradapter_mode
TypeText String
Value
Defines

Assigns the link speed and the duplex settings of the virtual network adapter (except for DE602/DE602AA - see below).

The values are:

ParameterDescription
"Auto"Auto-negotiate (default)
"10BaseT-HD"10Mbps half duplex
"10BaseT-FD"10Mbps full duplex
"100BaseT-HD"100Mbps half duplex
"100BaseT-FD"100Mbps full duplex

Example:

set EWA adapter_mode="100BaseT-HD"


Warning

...

Please note that this parameter controls only the setting which the emulated network adapter reports to the guest operating system running on CHARON. It does not change any settings of the host adapter mapped to the virtual adapter! In case if the settings of the host adapter have to be changed please refer to the host Operating System User's Guide for details on how to do it.

In case if "Auto" value is set CHARON collects the settings from the mapped host network adapter directly, assuming that all speeds above 100Mbps are represented as 100Mbps (maximum value). The resulting duplex setting corresponds to the duplex setting of the mapped host network adapter.


Example

load packet_port/chnetwrk EWA0 interface = "connection:Charon"
set EWA interface = EWA0
set EWA station_address="0C:FE:35:AA:67:3B"

Back to Table of Contents

...

So mode propagation is implemented in CHARON-AXP via SRM console EIx0_MODE environment variable :

...

("x" is A, B, C... depending on CHARON-AXP configuration), for example:

>>>help set

usage: set <variable-name> <value>
set <variable-name> ""

set

eix0

eia0_mode { Twisted | Full | Fast | FastFD | Auto* }

>>>

_

(warning)(warning) The EIx0_MODE variable name is case insensitive, while its values are case sensitive! This is feature of OpenVMS EIDRIVER.

The values are:

ParameterDescription
"Auto"Auto-negotiate (default)
"Twisted"10Mbps half duplex
"Full"10Mbps full duplex
"Fast"100Mbps half duplex
"FastFD" 100Mbps full duplex

Example:

>>>set
eix0
eia0_mode FastFD


Warning

Please note that EIx0_MODE environment variable controls only the setting which the emulated network adapter reports to the guest operating system running on CHARON. It does not change any settings of the host adapter mapped to the virtual adapter! In case if the settings of the host adapter have to be changed please refer to the host Operating System User's Guide for details on how to do it.

In case if "Auto" value is set CHARON collects the settings from the mapped host network adapter directly, assuming that all speeds above 100Mbps are represented as 100Mbps (maximum value). The resulting duplex setting corresponds to the duplex setting of the mapped host network adapter.

Back to Table of Contents

...

To create instances of the "packet_port", use the “load” command in the configuration file as follows:

load packet_port/chnetwrk <instance-name>

Example:

load packet_port/chnetwrk NDIS

"packet_port" uses several configuration parameters to control its behavior.

interface

Parameterinterface
Type

Value

interface

Text string

Value

This parameter identifies an Ethernet adapter of the host system dedicated to CHARON-AXP

with a

. The leading keyword "connection:"

preceeding it

is mandatory.

Syntax:

set <name> interface="connection:<adapter>"

Example:

set NDIS interface="connection:Charon"


port_enable_mac_addr_change

Parameter

port_enable_mac_addr_change

TypeBoolean
Value

If "true" is specified (default value), CHARON-AXP sets the appropriate Ethernet address automatically.

If "false" is specified, set the Ethernet address manually.

Example:

set NDIS port_enable_mac_addr_change=false


port_

...

retry_on_

...

tx

Numeric
Parameter
The "

port

_ignore_on

_

rx" parameter provides the ability to shutdown the port when a specified number of sequential "on receive" errors is exceeded.

Typically, errors "on receive" indicate serious (unrecoverable) errors.

By default, the value is set to the value of the "port_pending_rx_number" parameter. A value of ‘0’ means infinite.

Example:

set NDIS port_ignore_on_rx=16
port_

retry_on_tx

TypeNumeric
Value

The "port_retry_on_tx" parameter controls the number of times a port will attempt to transmit a packet before giving up.

By default, the value is 3.

Increasing this value may introduce problems in carrier loss logic, because not all NIC drivers support a carrier status query.

Typically, you do not need to increase the value.

Example:

set
pp_1
NDIS port_retry_on_tx=8


port_pending_rx_number

Parameter

port_pending_rx_number

TypeNumeric
Value

The "port_pending_rx_number" parameter sets the number of pending receive buffers.

The default value is 63. The maximum value allowed is 195.

You may want to increase the "port_pending_rx_number" when you have very busy networking and experience problems like losing connections not related to the carrier loss.

Typically, you do not need to change this parameter.

Example:

set NDIS port_pending_rx_number=128


port_pending_tx_number

Parameter

port_pending_

rx

tx_number

TypeNumeric
Value

The "port_pending_tx_number" parameter sets the number of buffers the port uses to transmit.

The default value is 62.

You may want to increase the "port_pending_tx_number" value if the log file indicates dropped TX packets due to TX queue overflow.

Typically, you do not need to change this parameter.

Example:

set NDIS port_pending_
rx
tx_number=128


suspend_msg_on_mac_change

Parameter

suspend_msg_on_mac_change

TypeBoolean
Value

To avoid confusion arising from non critical errors during a MAC address change, logging is by default suppressed (default value is "true").

To enable tracing during a MAC address change set this parameter to "false"

Example:

set NDIS suspend_msg_on_mac_change=false

 

...


legacy_mode

Parameterlegacy_mode
TypeBoolean
Value

If this parameter is set to "true" CHARON-AXP tries to use very first implementation of "packet_port" having certain restrictions such as inability to automatically change MAC address on given interface etc.

This setting may be needed if CHARON-AXP runs in VMware environment for example.

In other situations please do not change its default value ("false").

Example:

set NDIS legacy_mode=true


Info

This parameter is required only if you do not want to allow promiscuous traffic for the VMware adapter/port. In this mode, CHARON-AXP uses legacy MAC address change logic, so use of this option is not desirable.

Thus for ESXi networking configuration:

  1. Create the port with e1000 adapter;
  2. Enable the promiscuous traffic;
  3. do not use legacy_mode option in Charon's configuration file


Info

TruCluster alias vMAC option may not operate correctly in combination with "legacy_mode=true" when host is VMware virtual machine. This is because vMAC option sets adapter to promiscuous mode which does not seem operating correctly on VMware adapters.


Example

load DE500BA/dec21x4x EWA
load packet_port/chnetwrk EWA0 interface="connection:Charon"
set EWA interface=EWA0


Info

CHARON-AXP supports VLAN adapters. If for some reasons you are going to use them, proceed with their installation and configuration according to the network adapter's vendor's User's Guide and then use the resulting VLAN interface the same way as the regular network interface.

...