Deployment of Base-Node via iSCSI in Server 2012R2 HPC cluster fails (can not join domain)
we evaluating server 2012r2 hpc pack upcoming project.
sadly stuck @ deploying base node. node boots via pxe (ipxe) , connects iscsi, installs windows seems unable join domain.
once deployment fails node remains windows installed on iscsi drive.
able manually join domain , log in domain user.
can pink server both ips.
ping cluster.local or head-node.cluster.local resolved ip of servers nic private network (.10.1)
running deployment tests yields only:
warning: enterprise network not configured first in binding order on default gateways. might cause problems communicating active directory domain services.
-----------------------------------------------------------------------------------------
test: deployment: binding order test
14-7-2015 20:20:32 [information] network "private" description: intel(r) i210 gigabit network connection #2
14-7-2015 20:20:32 [information] network interface type: ethernet
14-7-2015 20:20:32 [information] address: 192.168.10.1
14-7-2015 20:20:32 [information] network "enterprise" description: intel(r) i210 gigabit network connection
14-7-2015 20:20:32 [information] network interface type: ethernet
14-7-2015 20:20:32 [information] address: 192.168.178.5
14-7-2015 20:20:32 [information] microsoft hpc diagnostic test host.
14-7-2015 20:20:32 [information] creating test instances from: pdcnet.dll:microsoft.hpc.diagnostics.tests.bindingorder.
14-7-2015 20:20:32 [verbose] failed load assembly originalpath: not load file or assembly 'file:///\\head-node\diagnostics\1125\pdcnet.dll' or 1 of dependencies. system cannot find file specified..
@ system.reflection.runtimeassembly._nload(assemblyname filename, string codebase, evidence assemblysecurity, runtimeassembly locationhint, stackcrawlmark& stackmark, intptr pprivhostbinder, boolean throwonfilenotfound, boolean forintrospection, boolean suppresssecuritychecks)
@ system.reflection.runtimeassembly.internalloadassemblyname(assemblyname assemblyref, evidence assemblysecurity, runtimeassembly reqassembly, stackcrawlmark& stackmark, intptr pprivhostbinder, boolean throwonfilenotfound, boolean forintrospection, boolean suppresssecuritychecks)
@ system.reflection.runtimeassembly.internalloadassemblyname(assemblyname assemblyref, evidence assemblysecurity, runtimeassembly reqassembly, stackcrawlmark& stackmark, boolean throwonfilenotfound, boolean forintrospection, boolean suppresssecuritychecks)
@ system.reflection.runtimeassembly.internalloadfrom(string assemblyfile, evidence securityevidence, byte[] hashvalue, assemblyhashalgorithm hashalgorithm, boolean forintrospection, boolean suppresssecuritychecks, stackcrawlmark& stackmark)
@ system.reflection.assembly.loadfrom(string assemblyfile)
@ microsoft.hpc.diagnostics.testhost.program.createtestinstance(string assemblyname, string classname)
14-7-2015 20:20:32 [verbose] retrying location: c:\program files\microsoft hpc pack 2012\bin\pdcnet.dll
14-7-2015 20:20:32 [verbose] failed load assembly exepath: not load file or assembly 'file:///c:\program files\microsoft hpc pack 2012\bin\pdcnet.dll' or 1 of dependencies. system cannot find file specified..
@ system.reflection.runtimeassembly._nload(assemblyname filename, string codebase, evidence assemblysecurity, runtimeassembly locationhint, stackcrawlmark& stackmark, intptr pprivhostbinder, boolean throwonfilenotfound, boolean forintrospection, boolean suppresssecuritychecks)
@ system.reflection.runtimeassembly.internalloadassemblyname(assemblyname assemblyref, evidence assemblysecurity, runtimeassembly reqassembly, stackcrawlmark& stackmark, intptr pprivhostbinder, boolean throwonfilenotfound, boolean forintrospection, boolean suppresssecuritychecks)
@ system.reflection.runtimeassembly.internalloadassemblyname(assemblyname assemblyref, evidence assemblysecurity, runtimeassembly reqassembly, stackcrawlmark& stackmark, boolean throwonfilenotfound, boolean forintrospection, boolean suppresssecuritychecks)
@ system.reflection.runtimeassembly.internalloadfrom(string assemblyfile, evidence securityevidence, byte[] hashvalue, assemblyhashalgorithm hashalgorithm, boolean forintrospection, boolean suppresssecuritychecks, stackcrawlmark& stackmark)
@ system.reflection.assembly.loadfrom(string assemblyfile)
@ microsoft.hpc.diagnostics.testhost.program.createtestinstance(string assemblyname, string classname)
14-7-2015 20:20:32 [verbose] retrying location: c:\program files\microsoft hpc pack 2012\bin\diagtests\pdcnet.dll
14-7-2015 20:20:32 [verbose] doing test on test type: microsoft.hpc.diagnostics.tests.bindingorder.
14-7-2015 20:20:32 [information] got domain controller name: head-node.cluster.local
14-7-2015 20:20:32 [information] resolved ip address dc. got 4 ip addessses.
14-7-2015 20:20:32 [information] routing address: 192.168.10.1.
-----------------------------------------------------------------------------------------
changing binding order in advanced settings resolved neither test nor actual deployment.
-----------------------------------------------------------------------------------------
nic settings
enterprise
intel(r) i210 gigabit network connection
cluster.local
ipv6 - disabled
ipv4
192.168.178.5
255.255.255.0
192.168.178.1
dns
212.54.40.25
192.168.178.1
qos packed scheduler - enabled
link-layer topology discovery mapper i/o driver - enabled
link-layer topology discovery responder - enabled
private
intel(r) i210 gigabit network connection #2
cluster.local
ipv6 - disabled
ipv4
192.168.10.1
255.255.255.0
no default gateway
dns
127.0.0.1
qos packed scheduler - enabled
link-layer topology discovery mapper i/o driver - enabled
link-layer topology discovery responder - enabled
-----------------------------------------------------------------------------------------
control panel\network , internet\network connections\advanced\advanced settings\adapter and bindings\connections
enterprise
private
[remote access connections]
-----------------------------------------------------------------------------------------
c:\users\administrator>wmic nicconfig description,settingid
description settingid
wan miniport (l2tp) {06e102f9-e21b-4cef-b0ca-64f4829a9a7c}
wan miniport (sstp) {577b93d0-f1fd-4c7b-b41e-53b4ba94a579}
wan miniport (ikev2) {1af75d00-449a-4cc1-9ed1-fb440172aed2}
wan miniport (pptp) {a235d4b4-600a-4ffa-8e12-9ba09e6daf65}
wan miniport (pppoe) {4e1b3d6c-934d-43df-9301-da9cc9e8a407}
wan miniport (ip) {3f6e7537-f2f8-4aea-8b72-b7a4d7298d4e}
wan miniport (ipv6) {041b181e-0469-42fd-b6b4-f32842b6495b}
wan miniport (network monitor) {c9875a41-724d-4987-9f2d-a41f8ae84e2f}
microsoft kernel debug network adapter {c7568b63-c424-48b3-ab9b-6d1f004d5afc}
ras async adapter {d0fa3b2f-90bf-4a07-83e3-81165d8b28ef}
intel(r) i210 gigabit network connection {5bc77c5e-0e79-4c01-9c9a-a28cfa94f898}
intel(r) i210 gigabit network connection #2 {0260fc73-5abf-4814-ab52-d16deffa4875}
microsoft isatap adapter {266e5ae1-245a-4d47-9e73-f37affe434a4}
microsoft teredo tunneling adapter {d9b3f7f2-a448-4513-bd48-a1b215c54dcf}
microsoft isatap adapter {40f0b15b-06da-4e06-a43c-89ad60918dec}
microsoft isatap adapter {dfa7713a-b5dc-4144-bb90-3a546c0ee42e}
microsoft failover cluster virtual adapter {341d1797-925c-49cc-9c24-50afc0f0c105}
microsoft isatap adapter {8be73b7c-14de-4e5c-92fa-1f6c8cf0fbf6}
hyper-v virtual ethernet adapter {a71bd6f0-072f-4c9a-8963-780ee41c896c}
-----------------------------------------------------------------------------------------
registry: [hkey_local_machine\system\currentcontrolset\services\tcpip\linkage]
\device\{5bc77c5e-0e79-4c01-9c9a-a28cfa94f898}
\device\{a71bd6f0-072f-4c9a-8963-780ee41c896c}
\device\{341d1797-925c-49cc-9c24-50afc0f0c105}
\device\{0260fc73-5abf-4814-ab52-d16deffa4875}
\device\{c7568b63-c424-48b3-ab9b-6d1f004d5afc}
-----------------------------------------------------------------------------------------
hardware:
server
asrock j1900d2y, 16 gb, 3tb hdd
windows server 2012r2 evaluation
roles: ad ds, dhcp (for private), dns (for private), wds, hpc cluster head-node
lan1: enterprise, 192.168.178.5 (static)
lan2: private, 192.168.10.1 (static)
ipmi: 192.168.178.6 (static), 192.168.178.28 (dhcp)
base-node
asrock q1900tm-itx, 4 gb, no hdd
windows 8.1 embedded
(the important thing quick-sync)
lan: private, 192.168.10.6 (dhcp)
cluster nodes meant encode parts of large video , join parts.
hardware requirements our nodes are: intel quick-sync, low power consumption, small form factor.
-----------------------------------------------------------------------------------------
deployment log:
time message
10-7-2015 23:57:18 reverted
10-7-2015 23:57:17 disassociating template node cluster\encoder1000
10-7-2015 23:57:17 the operation failed due errors during execution.
10-7-2015 23:57:17 the operation failed , not retried.
10-7-2015 23:57:17 the operation failed due errors during execution.
10-7-2015 23:57:17 the operation failed , not retried.
10-7-2015 23:57:17 exit code 1: incorrect function
10-7-2015 23:57:05 joining domain: cluster.local
10-7-2015 23:57:03 exit code 1: incorrect function
10-7-2015 23:56:51 joining domain: cluster.local
10-7-2015 23:56:49 exit code 1: incorrect function
10-7-2015 23:56:37 joining domain: cluster.local
10-7-2015 23:56:35 exit code 1: incorrect function
10-7-2015 23:56:23 joining domain: cluster.local
10-7-2015 23:56:21 exit code 1: incorrect function
10-7-2015 23:56:09 joining domain: cluster.local
10-7-2015 23:56:07 exit code 1: incorrect function
10-7-2015 23:55:55 joining domain: cluster.local
10-7-2015 23:55:53 exit code 1: incorrect function
10-7-2015 23:55:41 joining domain: cluster.local
10-7-2015 23:55:39 exit code 1: incorrect function
10-7-2015 23:55:27 joining domain: cluster.local
10-7-2015 23:55:25 exit code 1: incorrect function
10-7-2015 23:55:13 joining domain: cluster.local
10-7-2015 23:55:10 exit code 1: incorrect function
10-7-2015 23:54:58 joining domain: cluster.local
10-7-2015 23:54:56 exit code 1: incorrect function
10-7-2015 23:54:44 joining domain: cluster.local
10-7-2015 23:54:42 exit code 1: incorrect function
10-7-2015 23:54:30 joining domain: cluster.local
10-7-2015 23:54:28 exit code 1: incorrect function
10-7-2015 23:54:16 joining domain: cluster.local
10-7-2015 23:54:14 exit code 1: incorrect function
10-7-2015 23:54:02 joining domain: cluster.local
10-7-2015 23:54:00 exit code 1: incorrect function
10-7-2015 23:53:48 joining domain: cluster.local
10-7-2015 23:53:46 exit code 1: incorrect function
10-7-2015 23:53:34 joining domain: cluster.local
10-7-2015 23:53:32 exit code 1: incorrect function
10-7-2015 23:53:20 joining domain: cluster.local
10-7-2015 23:53:18 exit code 1: incorrect function
10-7-2015 23:53:06 joining domain: cluster.local
10-7-2015 23:53:04 exit code 1: incorrect function
10-7-2015 23:52:52 joining domain: cluster.local
10-7-2015 23:52:50 exit code 1: incorrect function
10-7-2015 23:52:38 joining domain: cluster.local
10-7-2015 23:52:36 exit code 1: incorrect function
10-7-2015 23:52:24 joining domain: cluster.local
10-7-2015 23:52:22 exit code 1: incorrect function
10-7-2015 23:52:10 joining domain: cluster.local
10-7-2015 23:52:08 exit code 1: incorrect function
10-7-2015 23:51:55 joining domain: cluster.local
10-7-2015 23:51:53 exit code 1: incorrect function
10-7-2015 23:51:41 joining domain: cluster.local
10-7-2015 23:51:39 exit code 1: incorrect function
10-7-2015 23:51:27 joining domain: cluster.local
10-7-2015 23:51:25 exit code 1: incorrect function
10-7-2015 23:51:13 joining domain: cluster.local
10-7-2015 23:51:11 exit code 1: incorrect function
10-7-2015 23:50:59 joining domain: cluster.local
10-7-2015 23:50:57 exit code 1: incorrect function
10-7-2015 23:50:45 joining domain: cluster.local
10-7-2015 23:50:43 exit code 1: incorrect function
10-7-2015 23:50:31 joining domain: cluster.local
10-7-2015 23:50:29 exit code 1: incorrect function
10-7-2015 23:50:17 joining domain: cluster.local
10-7-2015 23:50:15 exit code 1: incorrect function
10-7-2015 23:50:03 joining domain: cluster.local
10-7-2015 23:50:01 exit code 1: incorrect function
10-7-2015 23:49:49 joining domain: cluster.local
10-7-2015 23:49:47 exit code 1: incorrect function
10-7-2015 23:49:35 joining domain: cluster.local
10-7-2015 23:49:33 exit code 1: incorrect function
10-7-2015 23:49:21 joining domain: cluster.local
10-7-2015 23:49:19 exit code 1: incorrect function
10-7-2015 23:49:06 joining domain: cluster.local
10-7-2015 23:49:04 exit code 1: incorrect function
10-7-2015 23:48:52 joining domain: cluster.local
10-7-2015 23:48:50 exit code 1: incorrect function
10-7-2015 23:48:38 joining domain: cluster.local
10-7-2015 23:48:36 exit code 1: incorrect function
10-7-2015 23:48:24 joining domain: cluster.local
10-7-2015 23:48:22 exit code 1: incorrect function
10-7-2015 23:48:10 joining domain: cluster.local
10-7-2015 23:48:08 exit code 1: incorrect function
10-7-2015 23:47:56 joining domain: cluster.local
10-7-2015 23:47:54 exit code 1: incorrect function
10-7-2015 23:47:42 joining domain: cluster.local
10-7-2015 23:47:40 exit code 1: incorrect function
10-7-2015 23:47:28 joining domain: cluster.local
10-7-2015 23:47:26 exit code 1: incorrect function
10-7-2015 23:47:14 joining domain: cluster.local
10-7-2015 23:47:12 exit code 1: incorrect function
10-7-2015 23:47:00 joining domain: cluster.local
10-7-2015 23:46:58 exit code 1: incorrect function
10-7-2015 23:46:46 joining domain: cluster.local
10-7-2015 23:46:44 exit code 1: incorrect function
10-7-2015 23:46:32 joining domain: cluster.local
10-7-2015 23:46:30 exit code 1: incorrect function
10-7-2015 23:46:18 joining domain: cluster.local
10-7-2015 23:46:16 exit code 1: incorrect function
10-7-2015 23:46:04 joining domain: cluster.local
10-7-2015 23:46:02 exit code 1: incorrect function
10-7-2015 23:45:50 joining domain: cluster.local
10-7-2015 23:45:48 exit code 1: incorrect function
10-7-2015 23:45:45 joining domain: cluster.local
10-7-2015 23:45:38 disabling windows recovery mode (optimization iscsi-boot scenario)
10-7-2015 23:45:36 waiting iscsi boot nodes boot , start windows setup
10-7-2015 23:32:48 sending pxe command boot node current os
10-7-2015 23:32:44 sending pxe command boot node current os
10-7-2015 23:29:19 sending pxe command boot node current os
10-7-2015 23:29:15 sending pxe command boot node current os
10-7-2015 23:06:48 installing windows (expected time: 30 minutes)
10-7-2015 23:06:43 customizing windows unattended installation script
10-7-2015 23:06:37 cleaning wim file
10-7-2015 23:02:16 extracting wim c:\win8.1 embedded industry.wim c:\install
10-7-2015 23:02:11 creating local directory install media
10-7-2015 22:58:17 copying: images\win8.1 embedded industry.wim
10-7-2015 22:57:53 configuring disk partitions
10-7-2015 22:57:48 copying: config\diskpart.txt
10-7-2015 22:57:42 mounting installation shared folder on head node
10-7-2015 22:54:32 sending pxe command boot node winpe (expected boot time: 5-15 minutes)
10-7-2015 22:54:22 sending pxe command boot node winpe (expected boot time: 5-15 minutes)
10-7-2015 22:54:17 waiting node boot winpe
10-7-2015 22:54:17 initiating configuration operations template: default base template
10-7-2015 22:54:17 computer account encoder1000 created
10-7-2015 22:54:17 the computer account encoder1000 not exist; creating new account in active directory.
10-7-2015 22:54:17 searching existing account in active directory
10-7-2015 22:54:16 connecting domain controller: cluster.local
10-7-2015 22:54:16 initiating provisioning operations template: default base template
10-7-2015 22:54:16 creating dhcp reservation 192.168.10.6 on scope 192.168.10.0
10-7-2015 22:54:16 setting dhcp option 17 iscsi:192.168.10.1::::iqn.1991-05.com.microsoft:head-node-encoder1000-base-target
10-7-2015 22:54:16 setting dhcp option 12 encoder1000
10-7-2015 22:54:16 setting dhcp option 203 iqn.1991-05.com.microsoft:encoder1000.cluster.local
10-7-2015 22:54:16 creating reservation network adapter: d0509947b72c
10-7-2015 22:54:16 mapping successful
10-7-2015 22:54:16 mapping client [iqn.1991-05.com.microsoft:encoder1000.cluster.local] target lun [encoder1000-base] on storage array [127.0.0.1]
10-7-2015 22:54:15 remote disk disconnected
10-7-2015 22:53:44 disconnecting remote disk
10-7-2015 22:53:34 configuring bootloader
10-7-2015 22:53:31 copying winpe files
10-7-2015 22:53:29 placing bootloader
10-7-2015 22:53:29 mount successful at: c:\windows\temp\uhusex01.bsn
10-7-2015 22:53:16 connection established, mounting disk
10-7-2015 22:53:15 connecting iscsi target: 192.168.10.1 / iqn.1991-05.com.microsoft:head-node-encoder1000-base-target
10-7-2015 22:53:15 mapping successful
10-7-2015 22:53:14 mapping client [iqn.1991-05.com.microsoft:head-node.cluster.local] target lun [encoder1000-base] on storage array [127.0.0.1]
10-7-2015 22:53:14 base lun creation complete
10-7-2015 22:53:14 creation successful
10-7-2015 22:53:13 creating base lun "encoder1000-base"
10-7-2015 22:53:12 setting boot-initiator information
10-7-2015 22:53:12 associating template default base template node cluster\encoder1000
10-7-2015 22:53:12 moving node cluster\encoder1000 state unknown state provisioning
10-7-2015 22:53:11 assigning template default base template node encoder1000
-----------------------------------------------------------------------------------------
questions:
can 1 please point in right direction?
why test claim binding order off, while seems ok?
how can resolve binding order , make test pass?
real problem? if not how narrow down or can 1 directly tell problem is?
running out of ideas on try.
hi holly1975,
i not familiar hpc, have sysprep hpc node hpc pack deploy them through wds? if yes, can not found 2012r2 wds supported os list hpc node, may potential issue.
same time: “ping cluster.local or head-node.cluster.local resolved ip of servers nic private network (.10.1” situation seems wds may have incorrect network binding order, when have multiple nic can tracert "www.bing.com" found default gateway send request out, if not work expected need check in registry editor working nic,
for example have 2 default gateways "192.168.1.10" server's own ip , "192.168.1.2" correct default gateway. need edited default gateway nic in registry editor , deleted server's ip there. detail registry location please refer following kb.
ip address , default gateway settings assigned incorrectly in windows vista, in windows server 2008, in windows 7, , in windows server 2008 r2
https://support.microsoft.com/en-us/kb/2473489
there have specific forum hpc support, hpc deploy question may post in hpc support forum better choose:
windows hpc server
http://social.microsoft.com/forums/en-us/home?forum=windowshpcitpros
i’m glad of you!
please remember mark replies answers if , unmark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com
Windows Server > High Availability (Clustering)
Comments
Post a Comment