Dell Active System Manager Version 7.0 Livre blanc Page 13
- Page / 26
- Table des matières
- MARQUE LIVRES
Noté. / 5. Basé sur avis des utilisateurs
Use Case Study: Using Active System For VMware Cluster Environment Configuration
13
Create Deployment Template
Before moving forward with configuration of the chassis, this section describes creating the
Deployment Template for the ESXi hosts. This template will specify the various settings required to
configure the BIOS, RAID, and Networking for the servers, as well as the server facing ports of the I/O
Module. In this example, a Deployment Template will be created which will configure the servers to
boot to the redundant SD module containing a factory-installed ESXi image. This will also configure
fabric A and fabric B Broadcom CNAs to support iSCSI offload on fabric A for the ESXi data volume
connections and the network partitioning on fabric B for the various standard Ethernet networking
required by each host.
To create a deployment template, select “Create Deployment Template” from either the “Home” or
the “Templates” menu. Create a name and a description for your deployment template. Select the
minimum CPU and memory capabilities for the host, which will allow servers that don’t meet your
minimum requirements to be filtered from the available hardware.
Specify the necessary BIOS settings for your ESXi host. In this example, it’s important to ensure that
“Processor Virtualization Technology” is enabled and that the internal RAID is disabled since the server
will be booting from the SD modules and using iSCSI storage.
Next, the template for networking required on the servers must be configured. There is a fabric A and
fabric B Broadcom 57810 2 port 10Gb CNA in each server. On fabric A both ports will be used to provide
a redundant 10Gb connection to the iSCSI storage distribution device, thus this CNA will not be
partitioned. On fabric B, both ports will be used to provide 4 redundant connections to the various
networks outlined earlier in this document.
Active System Manager presents the concept of Virtual NICs which are synonymous with partitions on a
port of your networking devices. Each partition, or Virtual NIC, will be seen as an individual networking
and/or storage adapter device in the operating system. For each partition, a dedicated portion of the
available 10Gb bandwidth will be specified. You can also enable Bandwidth Oversubscription, or the
ability to allow Virtual NICs to consume more than their guaranteed portion of the bandwidth in the
event that it is available and not being used by other partitions. In this case, Bandwidth
Oversubscription has been disabled.
Active System Manager provides a wizard which will allow you to create each CNA partition. In this
example, a Virtual NIC will be created for the iSCSI data volume connectivity. First, specify a name for
the virtual NIC, or partition, on the CNA port. Then set the connection type to “SAN (iSCSI)”. Setting
the network type will assist with configurations by filtering out networks that are not associated with
SAN(iSCSI) to help ensure you are not assigning the wrong network to your template.
In Active System Manager we have specified the Native VLAN in the Deployment Template as
Storage16. Selecting the native VLAN in an ASM Deployment Template has the effect of configuring the
server facing port of the I/O Module for untagged traffic. Specifying this Native VLAN in Active System
Manager means that traffic ingressing from the server into this port must be untagged (in other words,
it cannot be tagged by the CNA or by software in the OS). Once this traffic enters the I/O Module, the
switch configuration will tag this traffic with the Native VLAN, in this case VLAN 16. This is important
because the storage distribution device is expecting tagged traffic with VLAN 16. Using the native VLAN
in the scenario of iSCSI data volume connections is optional; one could choose to tag in the operating
system before making these connections. This method has been chosen simply to avoid that
- System Manager 1
- Contents 3
- Introduction 4
- Active Infrastructure 4
- Active System Manager (ASM) 4
- iSCSI-Only Network Diagram 6
- Figure 1 6
- LAN-Only Network Diagram 7
- Figure 2 7
- Network Partitioning (NPAR) 8
- Pre-Requisites Introduction 8
- VMware vCenter 9
- Deploy Active System Manager 9
- IQN Naming Specification 10
- Figure 3 10
- VLAN Usage and Fabrics 11
- Table 1 11
- Discover Chassis 12
- Create Management Template 12
- Create Deployment Template 13
- Figure 4 15
- Configure Chassis 16
- Deploy Servers 17
- Create Cluster 19
- Add Hosts to Cluster 19
- Customer Networks 20
- Add Shared Storage 23
- Using A Host Profile 24
- Glossary 25
Produits connexes et manuels pour Mise en réseau Dell Active System Manager Version 7.0
Mise en réseau Dell SupportAssist Version 1.3 For OpenManage Essentials Manuel de démarrage rapide
(16 pages)
(16 pages)
Mise en réseau Dell Management Plug-in for VMware vCenter version 1.0.1 Manuel d'utilisateur
(114 pages)
(114 pages)
Mise en réseau Dell R2 Guide de démarrage rapide
(136 pages)
(136 pages)
Mise en réseau Dell N2000 Comment utiliser
(21 pages)
(21 pages)
KitchenAid KEMS378SSS02 manuels
Manuels d'utilisation et guides de l'utilisateur pour Cuisiniers KitchenAid KEMS378SSS02.
Nous fournissons des manuels en pdf 1 KitchenAid KEMS378SSS02 à télécharger gratuitement par type de document : Manuel de l'utilisateur
Commentaires sur ces manuels