원하는 형태에 따라서 구현할 수 있겠다. 역시 어떠한 목적을 가져갈 것인가와 그 특징을 사전에 알고 구성하기를 바란다.
Issue
In different environments, the networking schema used on the hypervisor nodes might differ. Here is the explanation of the different possible layouts, and a howto.
Environment
- Red Hat Enterprise Virtualization v2.1
- Various hypervisor nodes with various networking layouts and Logical Networks*
* please refer to the RHEV Administration Guide for an explanation on Logical Network management
Resolution
The Basic Network Layout
A basic network layout consists of a physical NIC on a host, bridged to a Logical Network bridge (set up using the bridge-utils package), to which in turn, the Guest VMs will connect using their virtual NICs.
This is the basic configuration used during the initial setup of a RHEV host, unless specified otherwise.
Network Layout using 2 (or more) NICs in a bonded configuration
In this layout, we set up two (or more) physical NICs on the host in a bonded configuration, attach a Logical Network bridge to the bond, and plug the Guest VMs into that bridge. Bonding will provide with NIC fault tolerance, and depending on the bonding mode - with bandwidth extension.
In order to set up a bond:
1. Go into the hosts tab, select a host
2. Open the Network Interfaces sub-tab
3. Ctrl+Click the interfaces you wish to bond - a "Bond" button will become available
A "Bond Network Interfaces"window will pop up. In this window it is possible to:
- Attach the new bond to a certain Logical Network
- Provide custom bonding options (same format as in the standard ifcfg scripts. If none are provided, the bond will be set as mode=4, miimon=150)
- Provide a static or a dynamic IP for the bond
Basic Network Layout with a VLAN tag on the NIC
In case VLAN tagging is required, the simple solution is to set up a tagged Eth interface on top of the physical NIC, and build a Logical Network bridge on top of the tagged Eth.
In order to set up a new Logical Network with a VLAN tag, when creating the Logical Network in the Data Center tab, check the "Enable VLAN Tagging" checkbox in the configuration window that is shown in Figure 3.24
Follow the Administration Guide through attaching the Logical Network to the Cluster (if required).
Then open the Hosts tab, select a host, open the Logical Networks subtab, edit an available NIC and change the "Network" parameter to the new Logical Network.
A new VLAN-tagged Eth.xxx instance will be created, and used with the new Logical Network.
Multiple VLAN Network Layout with a single NIC
In case the host should be communicating with several VLANs, it is possible to set up a few tags on a single physical NIC.
This is done by simply repeating the steps described above, in "Basic Network Layout with a VLAN tag on the NIC" with several tagged Logical Networks.
Every time an Eth interface is assigned a VLAN tagged Logical Network, a new Eth.xxx interface will be created and set up with its own Logical Network bridge.
When creating or configuring the virtual NICs on VMs, for every NIC there will be an option to choose to which bridge the NIC of a VM will be attached.
Multiple VLAN Network Layout with a NIC bond
In most cases, a single NIC is not enough to hold several Logical Networks, which calls for a bond setup. This is the supported layout:
To set this up:
1. Follow the procedure for setting up a bond, described in "Network Layout using 2 (or more) NICs in a bonded configuration". This will create the BondX interface for the Host.
2. Folow the procedure for "Multiple VLAN Network Layout with a single NIC", but use the new bond interface with the tagged Logical Networks. for each Logical Network attached to the bond, this will create a BondX.xxx interface, used by each Logical Network.
첫댓글 이누기님 왜 전 png 파일 그림 몇개가 깨져보이죠....ㅠㅠ슬픈현실..