El gateway de PowerFlex 4.x perdió la conexión con el clúster de MDM durante la reconfiguración de MDM

Summary: El gateway de PowerFlex no puede conectarse al clúster de MDM principal cuando la función principal se cambia con frecuencia.

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

  • La operación de reconfiguración de MDM falla, lo que indica que no se puede conectar al gateway de PowerFlex.
  • Las operaciones de inventario del gateway de PowerFlex comenzarán a fallar después de la operación de reconfiguración de MDM.
  • En el panel Resource, el gateway de PowerFlex muestra "PowerFlex unreachable" o unhealthy
  • El scaleio.log/scaleio_trace.log informa errores similares a los siguientes, que comienzan después de la solicitud de SwitchMdmOwnership :
2022-07-13 17:28:37,810 [https-openssl-nio-443-exec-5] DEBUG c.e.s.s.s.ConnectionServiceImpl - Send request SwitchMdmOwnership to MDM
2022-07-13 17:28:37,811 [https-openssl-nio-443-exec-5] DEBUG c.e.e.n.c.LayeredProtocolConnection - Cipher suites supported by server: [TLS_AES_256_GCM_SHA384, TLS_AES_128_GCM_SHA256, TLS_CHACHA20_POLY1305_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
2022-07-13 17:28:37,811 [https-openssl-nio-443-exec-5] DEBUG c.e.e.n.c.LayeredProtocolConnection - Default or requested cipher suites: [TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_GCM_SHA256]
2022-07-13 17:28:37,811 [https-openssl-nio-443-exec-5] DEBUG c.e.e.n.c.LayeredProtocolConnection - Intersection of the supported and requested cipher suites: [TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_GCM_SHA256]
2022-07-13 17:28:37,813 [https-openssl-nio-443-exec-5] DEBUG c.e.e.u.s.X509TrustManagerExtended - Trusting all the certificates
2022-07-13 17:28:37,975 [https-openssl-nio-443-exec-1-ReceiveLoop-1293774449] ERROR c.e.e.n.c.LayeredProtocolConnection - LPC-1293774449 #9dc0fdda29f79ec8 [192.168.150.26:8611]: IOException in receive loop: java.net.SocketException: Connection reset
2022-07-13 17:28:37,975 [https-openssl-nio-443-exec-1-ReceiveLoop-1293774449] INFO  c.e.e.n.c.LayeredProtocolConnection - LPC-1293774449 #9dc0fdda29f79ec8 [192.168.150.26:8611]: Attempting to re-connect
2022-07-13 17:28:37,975 [https-openssl-nio-443-exec-5] DEBUG c.e.s.s.s.ConnectionServiceImpl - Got rc SUCCESS for command SwitchMdmOwnership
2022-07-13 17:28:37,975 [command-service-0-ReceiveLoop-1271882087] ERROR c.e.e.n.c.LayeredProtocolConnection - LPC-1271882087 #858e689a28e91ed7 [192.168.150.26:8611]: IOException in receive loop: java.net.SocketException: Connection reset
 


 

Cause

El gateway de PowerFlex no puede conectarse al clúster de MDM principal cuando la función principal se cambia con frecuencia entre diferentes miembros del clúster de MDM. Esto se ha observado durante la reconfiguración de MDM cuando se solicita la transferencia de varias funciones de MDM.

Resolution

Para solucionar este problema, el usuario debe reiniciar el pod del gateway de PowerFlex.

Se puede utilizar el siguiente comando para reiniciar el gateway de PowerFlex.

kubectl delete pod -n powerflex $(kubectl get pods -A | grep block-legacy-gateway | grep -v mds | grep -i running | awk ' {print $2}')

Affected Products

PowerFlex Appliance, PowerFlex Software
Article Properties
Article Number: 000202170
Article Type: Solution
Last Modified: 27 May 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.