From the viewpoint of BS2000 devices, the ZASLAN, LOCLAN and BRGLAN are devices which are used for the LAN connection to the external physical network or for internal communication in the Server Unit. They can be created in the SE Manager (see section "Managing LAN devices") and must, in the case of VM2000, then be assigned to the BS2000 VM concerned.
BS2000 ZASLAN
In the case of a ZASLAN connection, BS2000 uses a LAN interface of its own (Ethernet controller) independently of other LAN interfaces. Only via such a connection does BS2000 obtain a direct view of the physical network.
In VM2000 mode a LAN interface can be used jointly by all connected BS2000 guest systems. To permit this, a separate ZASLAN connection is configured for each BS2000 VM. The associated devices are connected to their particular VM (using the ADD-VM-DEVICES command).
The ZASLAN interfaces are displayed or modified in the SE Manager using Devices -> [<se server>(SE<model>) ->] <unit> (SU<model>) -> BS2000 devices on the LAN tab.
All PCI ports can be used for the ZASLAN connections.
The following must be observed on the SU x86: LAN interfaces cannot be used simultaneously for ZASLAN and virtual switches of XenVMs (see section "Integration of the XenVM guest systems into the LAN (only SU x86)").
LOCLAN
The local LAN is a network implemented by software in the Linux-based basic system concerned (X2000/M2000/HNC). The local LAN connections are consequently not included in the figure illustrating the LAN structure (see Figure 2 in section "Networks"). The connection of BS2000 to the local LAN is implemented on an SU x86 system with connections implemented by software (MANLO: Management Network LOCLAN), and on an SU /390 by FC connections between SU /390 and MU (MANLO) or HNC.
The following addresses are preconfigured for BS2000 and the basic system (X2000/M2000):
System | IP address |
Basic system | 192.168.138.12 |
BS2000 (Native or monitor system) | 192.168.138.21 |
BS2000 guest systems on other VMs | 192.168.138.22 etc. |
A second MU (in case of SU /390) is automatically assigned the addresses 192.168.139.x. If address conflicts occur, the Customer Support can configure other address ranges.
BRGLAN (only SU x86)
A BRGLAN connection connects BS2000 with an internal virtual switch and enables a LAN connection to the other virtual machines (= Xen Linux or Windows guest systems) which are also connected to the same virtual switch.
A BRGLAN connection is required to implement one of the following connections:
The Native BS2000 system for the XenVMs on the same virtual switch
BS2000 VMs for XenVMs on the same virtual switch
If only BS2000 VMs communicate with each other, LOCLAN connections should be used.
The BRGLAN connection is a protected internal connection in the Server Unit which is implemented in the software and thus does not occupy any slots.
With BRGLAN the packet size can be up to 1500 bytes.
An internal virtual switch is configured using the SE Manager. A separate BRGLAN connection is configured in X2000 for each VM with a BS2000 guest system. The associated devices are assigned to the relevant VM.
The BRGLAN connection requires that at least one virtual switch exists. Virtual switches can be configured only in conjunction with the operation of XenVMs, i.e. a XenVM license must exist. For details, see "Integration of the XenVM guest systems into the LAN (only SU x86)".
BRGLAN connections are virtual network connections and are therefore not displayed in the physical LAN structure (see Figure 2 in section "Networks").