Integrazione di Avamar e Cloud Disaster Recovery: Impossibile aggiungere Avamar al Cloud Disaster Recovery Appliance a causa di una stringa della community SNMPv2 vuota

Riepilogo: Impossibile aggiungere Avamar a Cloud Disaster Recovery Appliance (CDRA) a causa di una stringa della community SNMPv2 vuota configurata nel Data Domain collegato in Avamar.

Questo articolo si applica a Questo articolo non si applica a Questo articolo non è legato a un prodotto specifico. Non tutte le versioni del prodotto sono identificate in questo articolo.

Sintomi

Impossibile aggiungere Avamar come backup server per Cloud Disaster Recovery Appliance (CDRA).

Nel file di registro di CDRA possono essere visualizzati i seguenti errori:
cdra/logs/cdra/cdra.log

ERROR [2023-05-22 19:07:53,734] [taskScheduler-18] [AvamarBackupService:reconnectAndGetHealthDetails:166]: Avamar is unhealthy; no connectivity. No response due to invalid hostname: avamar.example.com, or port number 9443, org.apache.axis2.AxisFault: Connection refused (Connection refused)
 
cdra/logs/cdra/cdra.log

DEBUG [2023-04-27 16:14:04,931] [taskScheduler-28] [AvamarSoapClientAPI:connect:88]: Trying to connect to avamar with host name: avamar.example.com
ERROR [2023-04-27 16:14:05,109] [taskScheduler-28] [AvamarSoapClientAPI:connect:99]: RemoteException caught in AvamarSoapClientAPI due to invalid host or port number Connection or outbound has closed
ERROR [2023-04-27 16:14:05,109] [taskScheduler-28] [BackupServersManager:addAdapter:194]: Could not initialize Avamar adapter.
com.emc.cloud_dr.cdr.commons.common_models.exceptions.NoConnectivityException: No response due to invalid host name: avamar.example.com, or port number 9443, org.apache.axis2.AxisFault: Connection or outbound has closed
        at com.emc.cloud_dr.cdr.adapters.avamar_adapter_soap.AvamarSoapClientAPI.connect(AvamarSoapClientAPI.java:102)
        at com.emc.cloud_dr.cdr.commons.backup_service.impl.avamar.AvamarBackupService.init(AvamarBackupService.java:46)
        at com.emc.cloud_dr.cdr.commons.backup_servers_manager.impl.BackupServersManager.addAdapter(BackupServersManager.java:189)
        at com.emc.cloud_dr.cdr.cdra.cdra_backup_servers_manager.CdraBackupServersManager.addAdapter(CdraBackupServersManager.java:96)
        at com.emc.cloud_dr.cdr.commons.remote_server.model.AbstractRemoteServersManager.getAdapterInstance(AbstractRemoteServersManager.java:154)
        at com.emc.cloud_dr.cdr.commons.monitor.impl.collectors.AbstractRemoteServerDataCollector.getAdapterDetails(AbstractRemoteServerDataCollector.java:52)
        at com.emc.cloud_dr.cdr.commons.monitor.impl.collectors.AbstractRemoteServerDataCollector.lambda$collectData$2(AbstractRemoteServerDataCollector.java:
41)

ERROR [2023-04-27 16:14:05,109] [taskScheduler-28] [AbstractRemoteServersManager:getAdapterInstance:157]: could not initialize adapter 2b356007-de19-42c4-9346
-067ce80f68ab

Sul server Avamar, nel registro mcserver viene registrata la seguente chiamata API SOAP:
/usr/local/avamar/var/mc/server_log/mcserver.log.0

05/25-08:30:43.00047 [MCWebServices-MCSDK-QueuedThreadPool-295#295] com.avamar.mc.axis2.logging.LogHandler.invoke
WARNING: MCSDK[mcsdk20] Call[urn:getTaskInfo][urn:uuid:3362594b-c177-4fe9-89eb-a042c6f8e889] end with error. SOAP output:




soapenv:Receiver


java.lang.RuntimeException: Can not serialize OM Element Envelope





Sul server Avamar, lo stack di eccezioni completo viene registrato nel log axis2:
/usr/local/avamar/var/mc/server_log/axis2.log

2023-05-25 09:21:56,914 [MCWebServices-MCSDK-QueuedThreadPool-293] ERROR org.apache.axis2.transport.http.AxisServlet  - Can not serialize OM Element Envelope
java.lang.RuntimeException: Can not serialize OM Element Envelope
        at org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:963)
        at org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler.invoke(SOAPMonitorHandler.java:101)
        at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
        at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
        at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
        at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:427)
        at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:43)
        at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114)
        at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
        at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
        at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:542)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1700)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1667)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
        at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)
        at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:152)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
        at org.eclipse.jetty.server.Server.handle(Server.java:505)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
  at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
        at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:427)
        at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:321)
        at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:159)
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
        at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
        at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:786)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:743)
        at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.axis2.databinding.ADBException: snmpCommunity cannot be null!!
        at com.avamar.mc.sdk20.DdrConfigInfo.serialize(DdrConfigInfo.java:675)
        at com.avamar.mc.sdk20.TaskInfo.serialize(TaskInfo.java:619)
        at com.avamar.mc.sdk20.TaskInfo.serialize(TaskInfo.java:476)
        at com.avamar.mc.sdk20.GetTaskInfoResponse.serialize(GetTaskInfoResponse.java:120)
        at com.avamar.mc.sdk20.GetTaskInfoResponse.serialize(GetTaskInfoResponse.java:81)
        at org.apache.axis2.databinding.ADBDataSource.serialize(ADBDataSource.java:90)
        at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:635)
        at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:556)
        at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:846)
        at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:214)
        at org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:120)
        at org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:108)
        at org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:957)
        ... 49 more

Causa

La root cause dell'errore è definita dalla seguente eccezione:
Caused by: org.apache.axis2.databinding.ADBException: snmpCommunity cannot be null!!
Quando Data Domain è integrato con Avamar, SNMP è configurato in modo che Avamar possa eseguire query su Data Domain per informazioni e Data Domain archivia Avamar come host trap.

Durante la configurazione di SNMP tra Avamar e Data Domain, è necessario fornire una stringa della community nell'interfaccia utente di Avamar.
 
Stringa di community SNMP fornita per Avamar
Figura 1. Stringa di community SNMP fornita per Avamar 

Risoluzione

Passare a Avamar Administrator > Navigazione > Server > Server Management > Edit Data Domain System > SNMP.

Configurare la stringa della community SNMP, come l'immagine mostrata nella sezione Causa di questo articolo.

Prodotti interessati

Avamar, Cloud Disaster Recovery
Proprietà dell'articolo
Numero articolo: 000214335
Tipo di articolo: Solution
Ultima modifica: 08 gen 2026
Versione:  5
Trova risposta alle tue domande dagli altri utenti Dell
Support Services
Verifica che il dispositivo sia coperto dai Servizi di supporto.