Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
Table of Contents
Table of Contents | ||
---|---|---|
|
Introduction
To configure CHARON-VAX networking, follow these 3 steps:
...
Include Page | ||||
---|---|---|---|---|
|
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 corresponding instance of "packet_port" or "tap_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:
|
Div | ||
---|---|---|
| ||
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 receive queue. Typically, you do not need to change the "rx_fifo_size" parameter. It is available for extended tuning and bug hunting purposes. |
...
Include Page | ||||
---|---|---|---|---|
|
DEQNA / DESQA / DELQA Ethernet Controller
CHARON-VAX Q-bus systems provide support for DEQNA, DESQA, DELQA, DEUNA and DELUA Ethernet controllers.
...
DEQNA, DESQA, DELQA, DEUNA and DELUA offer the following configuration parameters that can be specified with "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. "address" parameter value must be unique for every instance of DEQNA, DESQA, DELQA, DEUNA and DELUA. Example:
|
Div | ||
---|---|---|
| ||
interface
Parameter | interface |
---|---|
Type | Text String |
Value | Name of corresponding instance of "packet_port" or "tap_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 receive queue. Typically, you do not need to change the "rx_fifo_size" parameter. It is available for extended tuning and bug hunting purposes. |
...
Include Page | ||||
---|---|---|---|---|
|
Div | ||
---|---|---|
| ||
DEMNA Ethernet Adapter
CHARON-VAX/66X0 systems provide support for the DEMNA Ethernet controller.
...
DEMNA Ethernet controller offers the following configuration parameters that can be specified with "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 corresponding instance of "packet_port" or "tap_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 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 | "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 bug hunting purposes. |
...
Include Page | ||||
---|---|---|---|---|
|
DEBNI Ethernet Adapter
CHARON-VAX/63X0 systems provide support for the DEBNI Ethernet controller.
...
DEBNI Ethernet controller offers the following configuration parameters that can be specified with "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 corresponding instance of "packet_port" or "tap_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 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 | "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 bug hunting purposes. |
...
Include Page | ||||
---|---|---|---|---|
|
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").
...
PMAD-AA TurboChannel Ethernet controller offers the following configuration parameters that can be specified with "set" command:
interface
Parameter | interface |
---|---|
Type | Text String |
Value | Name of corresponding instance of "packet_port" or "tap_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 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 | "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 bug hunting purposes. |
...
Include Page | ||||
---|---|---|---|---|
|
Packet Port
The CHARON-specific "packet_port" interface establishes a connection between an Ethernet adapter in the Linux host system and a network adapter in the virtual VAX system.
...
"packet_port" offers several configuration parameters controlling its behavior.
interface
Parameter | interface | ||
---|---|---|---|
Type | Text string | ||
Value | This parameter Identifies an Ethernet adapter of the host system dedicated to CHARON-VAX. Syntax:
Example:
|
port_enable_mac_addr_change
Parameter | port_enable_mac_addr_change | |
---|---|---|
Type | Boolean | |
Value | If "true" is specified, CHARON sets the appropriate Ethernet address automatically. If "false" is specified, set the Ethernet address manually. The default value is "true". Example:
|
port_retry_on_tx
Parameter | port_retry_on_tx | |
---|---|---|
Type | Numeric | |
Value | The "port_retry_on_tx" parameter controls the number of times the port will attempt to transmit the packet before giving up. By default, the value is 3. Increasing this value may introduce problems in carrier loosing logic because not all NIC drivers support 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 | "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 | "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:
|
log
Parameter | log | ||||
---|---|---|---|---|---|
Type | Text string | ||||
Value | If this parameter is set to some valid file name or a directory where the log files for each individual session will be stored CHARON logs Recv and Xmit packets at the emulated port layer. If an existing directory is specified, CHARON automatically enables creation of individual log files, one for each session using the same scheme as used for the generation of the rotating log files. If the "log" parameter is omitted, CHARON does not create log. In certain situations enabling this parameter may help to detect loss of packets. Example:
|
...
Include Page | ||||
---|---|---|---|---|
|
Supported Ethernet Q-bus Adapters for DECnet OSI (DECnet Plus)
The only supported Q-bus device is the DELQA adapter model.
...
Include Page | ||||
---|---|---|---|---|
|
Ethernet Q-bus Adapter and Cluster configuration rules
In a VMS Cluster using VMS V 5.5 and above, use only DELQA and DESQA Ethernet adapters that are supported (VMS Cluster SPD).
...