Deploying Windows Server 2012 R2 to Dell servers in BARE-METAL mode. Part 1

    imageIn this article, we will create an installation image of Windows Server 2012 R2 installed on a Dell PowerEdge R620 server with a 4-port Intel Ethernet 10G 2P X520 Adapter (2 1Gbit \ sec + 2 10Gbit / sec ports, support VLANs , Teaming , Jumbo Packet and Download via iSCSI \ PXE ). The image will contain all the drivers and preinstalled software. To create the image and then deploy it, we will use the Windows Server component : “Windows Deployment Services (WDS)”
    As we have already indicated, we will deploy the test platform on Dell PowerEdge servers of the R620 series, with 4-port Intel Ethernet 10G X520 network adapters (two of which are 10GB) and an Extreme Networks Summit X670V switch stack (10GB ports). As storage, we will use one of the servers on which the component of Windows Server 2012 R2 is installed - “File and iSCSI Services - iSCSI Target Server” and the HITACHI HUS110 hardware storage system (to evaluate all the advantages of Multipath I / O).
    On the computer from which we will create the image for further deployment over the network via WDS, install all the necessary drivers and updates (for example, to fully use the network adapter, you need a driver from Intel, and not the one that the system installs on its own. and he, in turn, needs an Update for Windows Server 2012 R2 (KB2883200) After installing all the necessary drivers and updates, add the MPIO system component (there will be a lot of pictures, so don’t be angry if we ruffle a bit;):


    and configure it (add support for iSCSI and SAS devices):

    After rebooting (required after enabling support for iSCSI and SAS devices), we will go on to network settings.
    Here are the required minimum settings on the switch side:
    configure jumbo-frame-size 9014
    enable jumbo-frame ports all

    create vlan "iSCSI"
    configure vlan iSCSI tag 11
    create vlan "VLAN10"
    configure vlan VLAN10 tag 10

    enable sharing 1:26 grouping 1:26, 2:26 algorithm address-based L2 lacp
    enable sharing 1:25 grouping 1:25, 2:25 algorithm address-based L2 lacp
    enable sharing 1:25 grouping 1:27, 2:27 algorithm address-based L2 lacp
    enable sharing 1:28 grouping 1:28, 2:28 algorithm address-based L2 lacp
    enable sharing 1:29 grouping 1:29, 2:29 algorithm address-based L2 lacp

    configure vlan iSCSI add ports 1: 1, 1: 25-29 tagged
    configure vlan VLAN10 add ports 1: 1, 1: 25-29 tagged


    Now let's move on to the server side configuration. To begin with, we will make a network card union (Teaming) - in our case (LACP, we connect each port to a separate physical unit of the switch stack) - this is not only aggregation of channels, but also increased fault tolerance. This can be done both by means of the Windows Server 2012 R2 OS, and using the driver settings. We will go the second way :)
    many pictures:
    open "Network and Sharing Center - Change adapter settings - Properties -Configure"















    make sure the Jumbo Packet is turned on and its size is 9014 Bytes:


    create a new group, come up with a name for it





    select the necessary adapters (ports)


    and the highlight is the type of configuration for timing:

    We chose the IEEE 802.3ad Dynamic Link Aggregation. Here are the key features of this configuration:

    • IEEE 802.3ad supports two to eight ports per group
    • all ports must support the same speed
    • all group members must work in full duplex mode
    • The switch must be configured properly and preferably before the group is created. and of course - it must support the 802.3ad standard
    • creating adapter groups (ports) in this configuration involves balancing all traffic


    The result of our efforts:



    VLAN10 is a general-purpose network, iSCSI is for interacting with storages ...

    Now you can connect iSCSI disks (we will omit the steps for configuring storages here - the topic is for a separate article):
    ISCSI Initiator:











    The donor computer is ready, you can proceed to the next step - creating an image (preparing the sysprep utility with saving drivers and software, capturing the image and placing it on WDS, installing the prepared image on clean servers and, as an additional option, loading the server from a disk connected by iSCSI).
    To be continued…

    Also popular now: