PowerFlex Management Platform - LAG niet gemaakt op bestaande DvSwitch's bij gebruik van Partial Network Automation (PNA)

Summary: Er wordt geen LAG gemaakt op dvSwitches tijdens het implementeren van een resourcegroep met 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

Als dvSwitches van tevoren worden gemaakt in VC zonder LAG en de sjabloon vraagt om het maken van LAG, wordt deze niet gemaakt.

PowerFlex 4.5.x automatiseringsscript maakt geen LAG op dvSwitches als de sjabloon verwijst naar bestaande dvSwitches zonder LAG.

Implementatiescript mislukt

  • Bevestiging dat alle switchinstellingen correct zijn:
    • Dell OS10 switchpoortkanalen/VLT
    • Cisco-poortkanaal
  • Nadat het brongroepscript is mislukt, wordt de gebruiker Handmatig maakt een vertraging in VC en migreert ernaar, wordt een nieuwe poging op de resourcegroep voltooid.

Het volgende wordt weergegeven in thin-deployer-logboeken: 

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

Impact 

Implementatiescript mislukt als bestaande dvSwitch niet al een LAG heeft geconfigureerd.

Cause

Als de gebruiker "use existing" dvThreadiches selecteert, verwacht PFxM dat de bestaande dvSwitch-configuratie werkt.

Zelfs als de sjabloon vraagt om het configureren van een LAG, zal PFxM de uplinks van een bestaande dvSwitch met een LAG niet opnieuw configureren.

Resolution

Als PFxM de nieuwe dvSwitches maakt, wordt de LAG gemaakt.

Als dvSwitches van tevoren worden gemaakt, moet de gebruiker er ook LAG op maken.

Als dvSwitches van tevoren worden gemaakt en de gebruiker vergeet LAG te maken, mislukt het script. Maak handmatig LAG in Vcenter/dvSwitches, migreer uplinks naar deze switches en klik vervolgens op "retry" in Resource Group.

 

Versies waarop dit van toepassing is

PowerFlex Manager 4.5.x

Opgelost in versie

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.