some of you maybe encountered following issue during the deployment of the Azure Stack RTM PoC.
Lets look on the field configuration:
One server HP DL360 G8
NIC Type 1GBE Intel i360 (HP OEM Label)
Two Public IPv4 Adresses published directly to the host and host configured as exposed host in the border gateway firewalls
No Firewall Rules for that host on the gateways
Switchports for that host configured as Trunk/Uplink ports with VLAN tagging enabled
We use Azure AD for Authentication
In my case, the important point is the port trunk and the VLAN tagging.
Normally VLAN tagging is no issue because the deployment toolkit should set the tag automatically during deployment for all VMs required and the host system.
In my case and during many test and validation deployments, that didn’t happen. After I start the deployment, a new virtual switch will be deployed and a virtual NIC named “deployment” will be configured for the host. Afterwards the deployment starts. Around 3 hours later, the deployment stops in step 60.120.121 and could not connect to the identity provider.
Whats the reason for the failure?
First you should know, that the Azure Stack Deployment switches between host and BGPNAT VM for internet communication. Mostly all traffic runs through the NAT VM but in that case, the host communicates directly with the internet.
So what happend? After creating the “deployment” NIC for the host, the deployment tool didn’t set the VLAN Tag on that virtual NIC. That breaks the network communication for the host, for the VMs there isn’t any issue because the VLAN is set for the NAT VM correctly.
What is the Workaround?
Start the deployment and configure it like normal
Let the deployment run into the failure
Open a new PowerShell with admin permissions (Run as Administrator)
Data disk drive configuration: All data drives must be of the same type (SAS or SATA) and capacity. If SAS disk drives are used, the disk drives must be attached via a single path (no MPIO, multi-path support is provided)
HBA configuration options: 1. (Preferred)Simple HBA
2. RAID HBA – Adapter must be configured in “pass through” mode
3. RAID HBA – Disks should be configured as Single-Disk, RAID-0
Supported bus and media type combinations
RAID SSD (If the media type is unspecified/unknown*)
SATA SSD + SATA HDD**
SAS SSD + SAS HDD**
* RAID controllers without pass-through capability can’t recognize the media type. Such controllers will mark both HDD and SSD as Unspecified. In that case, the SSD will be used as persistent storage instead of caching devices. Therefore, you can deploy the Microsoft Azure Stack POC on those SSDs.
** For tiered storage, you must have at least 3 HDDs.
Example HBAs: LSI 9207-8i, LSI-9300-8i, or LSI-9265-8i in pass-through mode
While the above configuration is generic enough that many servers should fit the description, we recommend a couple of SKUs: Dell R630 and the HPE DL 360 Gen 9. Both these SKUs have been in-market for some time.