Networking
Table of Contents
- 1 Introduction
- 2 SGEC Ethernet Controller
- 2.1 interface
- 2.2 station_address
- 2.3 rx_fifo_size
- 3 DEQNA / DESQA / DELQA Ethernet Controller
- 3.1 address
- 3.2 interface
- 3.3 station_address
- 3.4 rx_fifo_size
- 4 DEMNA Ethernet Adapter
- 4.1 xmi_node_id
- 4.2 interface
- 4.3 station_address
- 4.4 rx_fifo_size
- 5 DEBNI Ethernet Adapter
- 5.1 vax_bi_node_id
- 5.2 interface
- 5.3 station_address
- 5.4 rx_fifo_size
- 6 PMAD-AA TurboChannel Ethernet Adapter
- 6.1 interface
- 6.2 station_address
- 6.3 rx_fifo_size
- 7 Packet Port
- 8 Supported Ethernet Q-bus Adapters for DECnet OSI (DECnet Plus)
- 9 Ethernet Q-bus Adapter and Cluster configuration rules
Introduction
To configure CHARON-VAX / CHARON-PDP networking, follow these 3 steps:
Load network adapter (if required)
If you are configuring a DEQNA, DESQA, DELQA, DEUNA, DELUA, DEMNA, DEBNI or PMADAA adapter, use the "load" command as shown below. CHARON-VAX 3100/96/98 and 4000/106/108 emulations automatically load SGEC (with the name "EZA") and therefore no "load" command is required.
Example:Load "packet_port"
Load "packet_port" to connect the SGEC, DEQNA, DESQA, DELQA, DEUNA, DELUA, DEMNA, DEBNI or PMADAA adapter to the host hardware network card (or to a virtual network interface).
Example:
Connect the loaded "packet_port" to the loaded virtual network adapter
Connect the SGEC, DEQNA, DESQA, DELQA, DEUNA, DELUA, DEMNA, DEBNI or PMADAA adapter to the "packet_port" by setting the interface name.
Example:
Network booting is supported with exception of VAX6xxx models.
SGEC Ethernet Controller
The built-in SGEC controller emulator ("EZA") has the following parameters that are specified with the "set" command:
interface
Parameter | interface |
|---|---|
Type | Text String |
Value | Name of the corresponding instance of the "packet_port" component |
station_address
Parameter | station_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:
or
Example:
|
rx_fifo_size
Parameter | rx_fifo_size |
|---|---|
Type | Numeric |
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. |
Example:
DEQNA / DESQA / DELQA Ethernet Controller
CHARON-VAX / CHARON-PDP Q-bus systems provide support for DEQNA, DESQA, DELQA, DEUNA and DELUA Ethernet controllers.
Use the following command to load the instances of DEQNA, DESQA, DELQA, DEUNA or DELUA Ethernet controllers:
|
Example:
|
DEQNA, DESQA, DELQA, DEUNA and DELUA offer the following configuration parameters that can be specified using the "set" command:
address
Parameter | address | |
|---|---|---|
Type | Numeric | |
Value | Specifies the CSR address. The address must be a valid QBUS and UNIBUS address in I/O space. Initial value is 017774440, which is the factory setting for DEQNA, DESQA and DELQA Ethernet controllers. Use the address parameter if loading several instances of DEQNA, DESQA, DELQA, DEUNA and DELUA Ethernet controllers. "address" parameter values must be unique for every instance of an DEQNA, DESQA, DELQA, DEUNA and DELUA Ethernet controller. Example:
|
interface
Parameter | interface |
|---|---|
Type | Text String |
Value | Name of the corresponding instance of the "packet_port" component |
station_address
Parameter | station_address | |||
|---|---|---|---|---|
Type | Text String | |||
Value | "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:
or
Example:
|
rx_fifo_size
Parameter | rx_fifo_size |
|---|---|
Type | Numeric |
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. |
Example:
DEMNA Ethernet Adapter
CHARON-VAX/66X0 systems provide support for the DEMNA Ethernet controller.
Use the following command to load an instance of the DEMNA Ethernet controller:
|
Example:
|
DEMNA Ethernet controllers offer the following configuration parameters that can be specified using the "set" command:
xmi_node_id
Parameter | xmi_node_id |
|---|---|
Type | Number |
Value | Specifies the XMI slot in which the virtual DEMNA controller is placed. For CHARON-VAX/66X0 a free slot between 10 (A) and 14 (E) must be chosen. |
interface
Parameter | interface |
|---|---|
Type | Text String |
Value | Name of the corresponding instance of the "packet_port" component |
station_address
Parameter | station_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 which will run DECnet or when the migrated software uses the permanent address on the network adapter. Format:
or
Example:
|
rx_fifo_size
Parameter | rx_fifo_size |
|---|---|
Type | Numeric |
Value | The "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. |
Example:
DEBNI Ethernet Adapter
CHARON-VAX/63X0 systems provide support for the DEBNI Ethernet controller.
Use the following command to load an instance of the DEBNI Ethernet controller:
|
Example:
|
DEBNI Ethernet controllers offer the following configuration parameters that can be specified using the "set" command:
vax_bi_node_id
Parameter | vax_bi_node_id |
|---|---|
Type | Number |
Value | Specifies the VAXBI slot in which the virtual DEBNI controller is placed. |
interface
Parameter | interface |
|---|---|
Type | Text String |
Value | Name of the corresponding instance of the "packet_port" component |
station_address
Parameter | station_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 which will run DECnet or when the migrated software uses the permanent address on the network adapter. Format:
or
Example:
|
rx_fifo_size
Parameter | rx_fifo_size |
|---|---|
Type | Numeric |
Value | The "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. |
Example:
PMAD-AA TurboChannel Ethernet Adapter
The CHARON-VAX VAXstation 4000 Model 90 system provides support for a PMAD-AA TurboChannel Ethernet controller (in addition to the preloaded SGEC "EZA").
Use the following command to load an instance of a PMAD-AA Ethernet controller:
|
Example:
|
PMAD-AA TurboChannel Ethernet controllers use the following configuration parameters that can be specified using the "set" command:
interface
Parameter | interface |
|---|---|
Type | Text String |
Value | Name of the corresponding instance of the "packet_port" component |
station_address
Parameter | station_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 which will run DECnet or when the migrated software uses the permanent address on the network adapter. Format:
or
Example:
|
rx_fifo_size
Parameter | rx_fifo_size |
|---|---|
Type | Numeric |
Value | The "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 receive queue. Typically, you do not need to change the "rx_fifo_size" parameter. It is available for extended tuning and debugging purposes. |
Example:
Packet Port
The CHARON-specific "packet_port" interface establishes a connection between an Ethernet adapter in the Windows host system and a network adapter in the virtual VAX/PDP11 system.
For every virtual adapter instance loaded, one dedicated host Ethernet physical adapter is required.
To create instances of the "packet_port", use the “load” command in the configuration file as follows:
|
Example:
|
"packet_port" uses several configuration parameters to control its behavior.
interface
Parameter | interface | ||
|---|---|---|---|
Type | Text string | ||
Value | This parameter identifies an Ethernet adapter of the host system dedicated to CHARON-VAX / CHARON-PDP with a keyword "connection" preceeding it. Syntax:
Example:
|
port_enable_mac_addr_change
Parameter | port_enable_mac_addr_change | |
|---|---|---|
Type | Boolean | |
Value | If "true" is specified (default value), CHARON sets the appropriate Ethernet address automatically. If "false" is specified, set the Ethernet address manually. Example:
|
port_retry_on_tx
Parameter | port_retry_on_tx | |
|---|---|---|
Type | Numeric | |
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:
|
port_pending_rx_number
Parameter | port_pending_rx_number | |
|---|---|---|
Type | Numeric | |
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:
|
port_pending_tx_number
Parameter | port_pending_tx_number |
|---|---|
Type | Numeric |
Value | The "port_pending_tx_number" parameter sets the number of buffers the port uses to transmit. The default value is 62. |
© Stromasys, 1999-2025 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.
Need fast, reliable migration? We have done it countless times. Talk to an expert