Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
...
They can be configured in 3 modes:
- Direct mapping to the host resources
- Usage of "presentation mode" of connected or external storage controllers
- Pass Through mode
Below is an example of a KGPSA-CA controller loading:
...
Follow this link for details on the KGPSA-CA controllers configuration.
Include Page KBCOMMON:DOC-GoToToc KBCOMMON:DOC-GoToToc
Div | ||
---|---|---|
| ||
Anchor | ||||
---|---|---|---|---|
|
...
Optionally it is possible to configure the folIowing models of PBXDA-xx family controllers.
VIrtual PBXDA-xx
Syntax for loading PBXDA-xx family serial lines adapters:
|
Example:
load PBXDA_AC/DIGI TXA |
The adapter instance name ("TXA
" in the example above) is used then for parametrization, for example:
set TXA line[2]="COM1:" |
The numbers in the square brackets represent line number on the virtual PBXDA adapter starting from 0.
...
Non-US-EN installations of Windows may present “Location:” string in local language, but "host_bus_location" parameter requires English notation, so the words “PCI”, “bus”, “device”, and “function” must be specified in English.
Auto boot
The CHARON VM Charon-AXP can be configured to automatically boot an operating system at start up by specifying the default boot device and setting the 'auto_action' parameter to 'restart' from the console.
Example: dka0 is defined as the default boot device
|
Network boot
Charon-AXP can be configured to boot on network if the legacy operating system allows it via MOP. MOPv3 (DECnet) and MOPv4 (LANCP) are supported.
Usage/example:
P00>>>boot [-flags ...] [-file ...] ewa0 |
Both EW and EI adapters are supported for MOP network boot.
Include Page | ||||
---|---|---|---|---|
|