VxFlex Ready Node

Denne artikel indeholder links til PowerFlex-softwaredokumentation.

Dette dokument fremhæver minimumversioner samt anbefalede og nyeste kodeversioner for Dell Technologies Enterprise- og Datacenterinfrastruktur-produkter. Vi evaluerer og overvåger omhyggeligt kodeimplementeringsdata for at sikre, at produktudgivelser lever op til vores strenge forventninger om at give vores kunder pålidelige produkter og løsninger.

Denne artikel forklarer hver komponent i 4.x PowerFlex-systemet.

Installation af SDC version 3.6.0.4 mislykkes på Windows-værter.

Dette afsnit indeholder oplysninger om PowerFlex Manager 3.X-kompatibilitet for PowerFlex-rackkomponenter.

This procedure describes how to add another IP address subnet for use by the MDM cluster. This addresses scenarios where the MDM cluster uses a single network, or when an existing network must be replaced by a different one or to simply add another network (to an already multiple-network cluster). The MDM supports up to eight networks.

Ryd enhedsfejl.

Retrieve the OS device paths in a Linux-based or ESXi based SVM server PowerFlex system with NVMe devices configured.

Retrieve the OS device path for a specific virtual drive (VD) in a Linux-based, Windows, or ESXi running PERCCLI server PowerFlex system with an H730p/H740p controller.

Retrieve the OS device paths in a Linux-based or ESXi based Storage Virtual Machine (SVM) server PowerFlex system with an HBA330 controller.

Configure network throttling to control the flow of traffic over the network.

get_info.sh - collect diagnostic information from a PowerFlex host and pack it into a support bundle

After MDM switchover, SDSs cannot reconnect and MDMs crash.

SDS gets decoupled - the system might experience DU occasionally if more than one SDS decouples concurrently or in case the SDS decouples during a rebuild.

When a vMotion clone of a VM guest is submitted, it takes a lot longer than expected. Scenario Due to an environmental configuration issue, there was contention on the vMotion configured NICs that conflicted with iSCSI and VxFlex SDC traffic, causing reduced performance.

SDS fails to start up.

After restart of ESXi/SVM, the SDS comes up but is in a disconnect state in the UI/CLI.

Når du har fulgt NDU-flowet og skiftet til 1_node MDM-klynge, opgraderet sekundære/TB MDM'er og forsøgt at sætte computeren tilbage i klyngen, opstår der en fejl.

Opgraderingen starter/afslutter ikke færdiggørelsestrinnet, da MDM vises i en igangværende opgraderingstilstand.

Når du forsøger at oprette og knytte en diskenhed til en beregningsnode i OpenStack, tager handlingen meget længere tid (sammenlignet med de andre noder), og klienten logger fejl mod den nyoprettede enhed.

Network connectivity issues cause Secondary MDM/s status to become Not synchronized.

Der er kun én SDC, der har problemer med ydeevne.

SDS reports sockets closed without any network events or evidence of networking issues.

Errors are present whenever rebooting the SDC. IO times out from PowerFlex Gateway.

Issue Description vSphere ESXi hosts hang and become inaccessible randomly after experiencing high latency within the datastores.

Programmer, der bruger PowerFlex-diskenheder, rapporterer beskadigelse, når RMcache er aktiveret.

In PowerFlex Manager 4.0, performing a Linux Compute Only deployment using a SLES 15 SP3 ISO gets stuck during the OS installation phase.

Multiple SDS nodes may intermittently panic with a NO_RESOURCES assertion in spef_SynchronizeExtentDataWithIoCommitPhaseCk during high internal SPEF resource utilization.

The customer is using the SDC monitoring pod (also called the sdc-monitor sidecar) and noticed an excessive amount of CPU is being used by it.

Using PowerFlex Manager Deployment or Upgrade will fail in Diskless nodes due to the backplane. When performing deployments on diskless Compute Only (CO) nodes, if the backplane shows as non-compliant PFxM attempts to upgrade and it Fails.