Architecture and strategies Networks
U41855-J-Z125-3-76 39
Dokuschablonen 19x24 Version 7.4de für FrameMaker V7.x vom 09.02.2010 © cognitas GmbH 2001-2010
19. March 2018 Stand 18:25.47 Pfad: P:\FTS-BS\Server\SE-Server\SE-Doku\1303912_BuV_062\BuV_e\buv.k02
2.3.4 Integration of the XenVM guest systems into the LAN (only SU x86)
The Linux/Windows systems on the XenVMs communicate with each other or with external
systems via software instances which are known as virtual switches (or vSwitches for
short). Virtual switches are made available as XenVM devices. A XenVM is connected
either when the XenVM is created or at a later point in time by assigning a virtual Network
Interface Card to the vSwitch.
Depending on the connection type provided, a distinction is made between two types of
vSwitches:
● Internal vSwitch
An internal vSwitch enables the XenVMs connected to it to use a communication
connection which is protected locally. Internal vSwitches can also be used by the
BS2000 Native system and by BS2000 VMs (see “BRGLAN (only SU x86)” on
page 38).
● External vSwitch
An external vSwitch uses a LAN interface which permits an external LAN connection.
All XenVMs connected to this vSwitch use this connection to communicate with external
systems.
If more than one unused LAN interface is available, an external vSwitch can also use
two LAN interfaces. In this case, the XenVM connection is configured with redundancy
(also referred to as "bonding").
The virtual switches and their current assignment to XenVMs are displayed in the SE
Manager by selecting Devices
→ [<se server>(SE<model>) →] <unit> (SU<x86>)→ XenVM
devices on the Virtual switches tab. New virtual switches can be created there and unused
switches can be deleted.
I Only PCI ports can be used for the external vSwitches.
LAN interfaces (PCI ports) cannot be used more than once (e.g. for multiple virtual
switches or for a virtual switch and a ZASLAN).
To Next Page
Loading...
Need help?
General