Piattaforma di gestione PowerFlex - LAG non creato su DvSwitch esistenti quando si utilizza l'automazione parziale della rete (PNA)

Se i dvSwitch vengono creati in anticipo in VC senza LAG e il modello richiede la creazione di LAG, non verranno creati.

Lo script di automazione di PowerFlex 4.5.x non crea LAG sui dvSwitch se il modello punta a dvSwitch esistenti senza LAG.

Script di deployment non riuscito

• Conferma della correttezza di tutte le impostazioni dello switch:
  • Canali delle porte switch Dell OS10/VLT
  • Canale della porta Cisco
• Dopo l'esito negativo dello script del gruppo di risorse, l'utente Manualmente crea un ritardo in VC e ne esegue la migrazione, un nuovo tentativo sul gruppo di risorse viene completato correttamente.

Nei registri del thin deployer viene visualizzato quanto segue: 

exception.log:

#<RuntimeError: env --unset=RUBYOPT --unset=GEM_HOME --unset=RUBYLIB --unset=GEM_PATH --unset=BUNDLE_BIN_PATH RUBYLIB=/opt/service/lib:/opt/asm-deployer/lib:/opt/puppetlabs/puppet/lib:/opt/dependencies/dell-asm-util/lib 

INFO [2023-11-14T19:54:02.015289] 64760: service_deployment.rb:1351:in `block in process_components': VXFM011::An error occurred during the processing of cluster components.
ERROR [2023-11-14T19:54:02.038406] 64760: service_deployment.rb:653:in `process': env --unset=RUBYOPT --unset=GEM_HOME --unset=RUBYLIB --unset=GEM_PATH --unset=BUNDLE_BIN_PATH RUBYLIB=/opt/service/lib:/opt/asm-deployer/lib:/opt/puppetlabs/puppet/lib:/opt/dependencies/dell-asm-util/lib PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/puppetlabs/puppet/bin:/opt/puppetlabs/bin puppet asm process_node --debug --trace --filename /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/resources/vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt__2.yaml --run_type apply --statedir /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/resources --always-override vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt failed; output in /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt__2.out
ERROR [2023-11-14T19:54:02.038551] 64760: service_deployment.rb:654:in `process': ["/opt/dependencies/dell-asm-util/lib/asm/util.rb:398:in `block in run_command_streaming'", "/opt/jruby/jruby-9.3.9.0/lib/ruby/stdlib/open3.rb:219:in `popen_run'", "/opt/jruby/jruby-9.3.9.0/lib/ruby/stdlib/open3.rb:101:in `popen3'", "/opt/dependencies/dell-asm-util/lib/asm/util.rb:366:in `block in run_command_streaming'", "org/jruby/RubyIO.java:1148:in `open'", "/opt/dependencies/dell-asm-util/lib/asm/util.rb:365:in `run_command_streaming'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1673:in `block in process_generic'", "/opt/asm-deployer/lib/asm/private_util.rb:1251:in `block in wait_until_available'", "/opt/asm-deployer/lib/asm.rb:762:in `wait_on_counter_threshold'", "/opt/asm-deployer/lib/asm/private_util.rb:1250:in `wait_until_available'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1620:in `process_generic'", "/opt/asm-deployer/lib/asm/type/base.rb:616:in `process_generic'", "/opt/asm-deployer/lib/asm/provider/cluster/vmware.rb:885:in `provision_cluster!'", "/opt/asm-deployer/lib/asm/type/base.rb:441:in `delegate'", "/opt/asm-deployer/lib/asm/type/cluster.rb:25:in `provision_cluster!'", "/opt/asm-deployer/lib/asm/service_deployment.rb:3895:in `process_cluster'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1511:in `block in create_component_thread'"]
INFO [2023-11-14T19:54:02.038907] 64760: service_deployment.rb:656:in `process': Status: Error


vcenter-xxxxx___2:

Debug: Found dvswitch: VmwareDistributedVirtualSwitch 'brp-dpf-vdi-thy-01-dvs-fe'
Error: Could not locate specified LACP lag lag1 on dvswitch brp-dpf-vdi-thy-01-dvs-fe during vmk and vmnic migration
Error: /Stage[main]/Asm::Resource_wrapper/Vc_dvswitch_migrate[brp-dpf-hci-thy-dn508-u11.hhsprod.mgmt:brp-dpf-vdi-thy-01-dc/brp-dpf-vdi-thy-01-dvs-fe]/vmnic2: change from 'vSwitch0' to 'brp-dpf-vdi-thy-01-dvs-fe-Uplinks-27' failed: Could not locate specified LACP lag lag1 on dvswitch brp-dpf-vdi-thy-01-dvs-fe during vmk and vmnic migration
Error: /Stage[main]/Asm::Resource_wrapper/Vc_dvswitch_migrate[brp-dpf-hci-thy-dn508-u11.hhsprod.mgmt:brp-dpf-vdi-thy-01-dc/brp-dpf-vdi-thy-01-dvs-be]/vmnic3: change from to 'brp-dpf-vdi-thy-01-dvs-be-Uplinks-25' failed: Could not locate specified LACP lag lag1 on dvswitch brp-dpf-vdi-thy-01-dvs-be during vmk and vmnic migration
Error: Could not locate specified LACP lag lag1 on dvswitch brp-dpf-vdi-thy-01-dvs-be during vmk and vmnic migration
Error: /Stage[main]/Asm::Resource_wrapper/Vc_dvswitch_migrate[brp-dpf-hci-thy-dn508-u11.hhsprod.mgmt:brp-dpf-vdi-thy-01-dc/brp-dpf-vdi-thy-01-dvs-be]/vmnic5: change from to 'brp-dpf-vdi-thy-01-dvs-be-Uplinks-25' failed: Could not locate specified LACP lag lag1 on dvswitch brp-dpf-vdi-thy-01-dvs-be during vmk and vmnic migration	


asm-deployer-init.log:

ERROR [2023-11-14T19:54:02.045020] 64760: util.rb:26:in `block in execute_async': env --unset=RUBYOPT --unset=GEM_HOME --unset=RUBYLIB --unset=GEM_PATH --unset=BUNDLE_BIN_PATH RUBYLIB=/opt/service/lib:/opt/asm-deployer/lib:/opt/puppetlabs/puppet/lib:/opt/dependencies/dell-asm-util/lib PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/puppetlabs/puppet/bin:/opt/puppetlabs/bin puppet asm process_node --debug --trace --filename /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/resources/vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt__2.yaml --run_type apply --statedir /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/resources --always-override vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt failed; output in /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt__2.out

Impatto 

Lo script di deployment ha esito negativo se il dvSwitch esistente non dispone già di un LAG configurato.

Se l'utente seleziona "use existing" dvSwtiches, PFxM prevede che la configurazione dvSwitch esistente funzioni.

Anche se il modello richiede la configurazione di un LAG, PFxM non riconfigurerà gli uplink di un dvSwitch esistente con un LAG.

Se PFxM crea i nuovi dvSwitch, il LAG verrà creato correttamente.

Se i dvSwitch vengono creati in anticipo, l'utente deve creare LAG anche su di essi.

Se i dvSwitch vengono creati in anticipo e l'utente dimentica di creare il LAG, lo script ha esito negativo. Creare manualmente il LAG in Vcenter/dvSwitches, migrare gli uplink a essi, quindi cliccare su "retry" in Resource Group.

Versioni interessate

PowerFlex Manager 4.5.x

Risolto nella versione

PowerFlex Manager 4.6.1