Data Domain - "net config vethXX up" command performed by Cyber Recovery failing with error code 61
Resumo: To provide the air-gap feature of Cyber Recovery (CR), it ups and downs replication interfaces on Data Domain. There is a timing issue, with bonded interface configuration, that results in link status down being reported. ...
Este artigo aplica-se a
Este artigo não se aplica a
Este artigo não está vinculado a nenhum produto específico.
Nem todas as versões do produto estão identificadas neste artigo.
Sintomas
When putting replication interfaces down in the Data Domain for enforcing the air gap, Cyber Recovery (CR) reports the following alert:
Alert Message ID : 2002
CreationDate :
CreatedBy : crsecurity officer
Category : Storage
Severity : Critical
Summary : Unable to initiate a Data Domain replication synchronization job.
Description : An attempt to start a Data Domain replication synchronization job is unsuccessful.
Remedy :
1. Verify that Data Domain credentials were not updated.
2. Verify the health of the Data Domain storage system: DD Boost, Network, Filesystem status.
3. Verify connectivity from the Cyber Recovery Management Host to this Data Domain storage system.
Tags :
Policy Name:
Storage Name:
Action:
sync-copy-lock
Error:
Process exited with status 61 stderr:
****interface vethXX is enabled but is not running.
Check cable and connections
At the same time the Data Domain logs show an error like this:
sysadmin: command "net config vethXX up" exited with code: 61
Causa
There is a timing issue between bonded interface configuration and interface status up in the kernel in Juno Platforms (DD6900, DD9400, DD9900).
The error messages and error reason code are because of this mismatch.
A bonded interface will often go into "Running" state a few seconds later and become usable, however, Cyber Recovery does not check the running state before it generates the error and corresponding alert. CR also does not down the interface if this issue were to be encountered.
The error messages and error reason code are because of this mismatch.
A bonded interface will often go into "Running" state a few seconds later and become usable, however, Cyber Recovery does not check the running state before it generates the error and corresponding alert. CR also does not down the interface if this issue were to be encountered.
Resolução
Fix is available in the upcoming following releases and later ones;
Fix Version/s: DDOS-7.10.1.20, DDOS-8.0.0.0, DDOS-7.13.1.0
Temporarily, a workaround for this issue is to use a single physical interface instead of bonded interfaces. However this would mean that the CR Policy would must be updated with the protected interface name to match the new configuration. See the CR documentation on changing policy change pre-reqs. Also not this workaround would not guarantee high availability if a single network interface goes down.
Fix Version/s: DDOS-7.10.1.20, DDOS-8.0.0.0, DDOS-7.13.1.0
Temporarily, a workaround for this issue is to use a single physical interface instead of bonded interfaces. However this would mean that the CR Policy would must be updated with the protected interface name to match the new configuration. See the CR documentation on changing policy change pre-reqs. Also not this workaround would not guarantee high availability if a single network interface goes down.
Produtos afetados
Cyber Recovery Series, Data DomainPropriedades do artigo
Número do artigo: 000202629
Tipo de artigo: Solution
Último modificado: 02 abr. 2024
Versão: 2
Encontre as respostas de outros usuários da Dell para suas perguntas.
Serviços de suporte
Verifique se o dispositivo está coberto pelos serviços de suporte.