Plataforma de Gestão PowerFlex — LAG não criado em DvSwitch existentes ao utilizar automatização parcial da rede (PNA)

Summary: Um LAG não é criado em dvSwitches durante a implantação de um Grupo de Recursos usando PNA.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Se os dvSwitches forem criados antecipadamente no VC sem LAG e o modelo exigir a criação de LAG, não serão criados.

O script de automatização PowerFlex 4.5.x não cria LAG em dvSwitches se o modelo apontar para dvSwitches existentes sem LAG.

Falha no script de implementação

  • Confirmação de que todas as definições do switch estão corretas:
    • Canais de porta de switch Dell OS10/VLT
    • Canal de porta Cisco
  • Depois que o script do grupo de recursos falhar, o usuário manualmente cria um atraso no VC e migra para o mesmo, sendo concluída com êxito uma nova tentativa no grupo de recursos.

O seguinte é visto nos logs do thin-deployer: 

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

Impacto 

O script de implementação falha se o dvSwitch existente ainda não tiver um LAG configurado.

Cause

Se o usuário selecionar "usar dvSwtiches existente", o PFxM espera que a configuração dvSwitch existente funcione.

Mesmo que o modelo exija a configuração de um LAG, o PFxM não reconfigurará os uplinks de um dvSwitch existente com um LAG.

Resolution

Se o PFxM criar os novos dvSwitches, o GAL será criado com êxito.

Se dvSwitches são criados antes do tempo, o usuário deve criar LAG sobre eles também.

Se dvSwitches são criados antes do tempo e o usuário se esquece de criar LAG, então o script falha, manualmente criar LAG no Vcenter / dvSwitches, migrar uplinks para eles, em seguida, clique em "retry" em Grupo de Recursos.

 

Versões afetadas

PowerFlex Manager 4.5.x

Correção feita na versão

PowerFlex Manager 4.6.1

Affected Products

PowerFlex rack, PowerFlex Appliance
Article Properties
Article Number: 000225356
Article Type: Solution
Last Modified: 24 May 2024
Version:  1
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.