Networker 8.1 VBA not registered

Hi,

Did you check your firewall rules?

Port 7444, 8543 and 443 between VBA and vCenter

Port 902 between ESX and VBA

And Port range 7937-9936 between VBA and Networker Server

Did you try to configure a normal Networker client for you VBA Aplliance?

Hope it will help you.

Cheers

Greg

Hello,

What sort of licensing do you use ?

Regards,

F@b

F@b, I'm still under evil as I'm waiting for EMC to license my install ... I would have thought I could still register the VBA even under eval?

This could be it, I'll have a check ...

Thanks Gregory,

I have no firewall in between those servers. As for configuring a client, it detects a networker client installed (I haven't completed the setup my NW8.1 is a windows box and can't mount the snapshots for this Linux appliance)

So some communication is working, just not the one for registration ...

DDBoost user is a DD admin. Is there a specific place where I can check why registration is failing ?

Hi,

You can check /usr/local/avamar/var/ebr/server_log/ebr-configure.log

Maybe you will find which is wrong.

Keep us informed please.

Regards,

F@b

Found the following in ebr-configure.log :

2014-03-13 12:24:50,818 INFO  [RegistrationWithNetworker]-listeners.NwServletContextListener$RegisterRunnable: nw ping using VM187.mydomain.com.au      8080    VMUser

2014-03-13 12:24:51,377 INFO  [RegistrationWithNetworker]-listeners.NwServletContextListener$RegisterRunnable: ping to Networker successful

2014-03-13 12:24:51,448 INFO  [RegistrationWithNetworker]-listeners.NwServletContextListener$RegisterRunnable: vba hostname: emc09.mydomain.com.au

2014-03-13 12:24:51,449 INFO  [RegistrationWithNetworker]-listeners.NwServletContextListener$RegisterRunnable: vba port: 8543

2014-03-13 12:24:51,449 INFO  [RegistrationWithNetworker]-listeners.NwServletContextListener$RegisterRunnable: vba user: MCUser

2014-03-13 12:24:51,449 INFO  [RegistrationWithNetworker]-listeners.NwServletContextListener$RegisterRunnable: vcenter host: vcenter.mydomain.com.au

2014-03-13 12:24:51,449 INFO  [RegistrationWithNetworker]-listeners.NwServletContextListener$RegisterRunnable: vcenter user: vsphere.local\EMCBackupRecovery

2014-03-13 12:24:51,449 INFO  [RegistrationWithNetworker]-listeners.NwServletContextListener$RegisterRunnable: vcenter port: 443

2014-03-13 12:24:51,450 INFO  [RegistrationWithNetworker]-listeners.NwServletContextListener$RegisterRunnable: Calling networker registration web service

2014-03-13 12:24:56,157 ERROR [RegistrationWithNetworker]-listeners.NwServletContextListener$RegisterRunnable: Error Occurred registering with networker server.

javax.xml.ws.WebServiceException: Could not send Message.

        at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:145)

        at com.sun.proxy.$Proxy80.registerVbaNode(Unknown Source)

        at com.emc.networker.config.listeners.NwServletContextListener$RegisterRunnable.registerWithNetworker(NwServletContextListener.java:104)

        at com.emc.networker.config.listeners.NwServletContextListener$RegisterRunnable.run(NwServletContextListener.java:57)

        at java.lang.Thread.run(Unknown Source)

Caused by: org.apache.cxf.transport.http.HTTPException: HTTP response '400: Bad Request' when communicating with http://VM187.mydomain.com.au:8080/soap

        at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1592)

        at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1520)

        at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1428)

        at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)

        at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:658)

        at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)

        at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)

        at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:532)

        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:464)

        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:367)

        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:320)

        at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:89)

        at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:134)

        ... 4 more

2014-03-13 12:40:02,619 INFO  [http-nio-8543-exec-10]-servlet.LoginServlet: Attempting to authenticate user...

Doesn't look too good ....

Few things!!

1. Virtual backup appliance as other backups still works with EVAL and doesn't need capacity based Licenses.

2. Does your DDBOOST user have admin priv. It is recommended.

3. Does your DDBOOST password consists of any special characters like ! or @ etc.

4. What is the exact error you are getting ?

5. Can you make sure there is a device configured under Devices on NMC and it is mounted and enabled.

6. Does the VBA (VM) is resolvable from both VCenter and Networker Server. nslookups working fine.

7. Are you configuring backups on DD attached to Networker server or another storage node.

1 - EVAL : thanks for the confirmation

2 - DDBOOST User is an admin on DD. At no time, EBR is prompting me for DDBoost account. Considering EBR can work without DataDomain, I'm guessing this shouldn't be the issue.

3 - spaces are the only special characters

4 - Networker logs a "Registration failed for VBA"

5 - Devices lists the DD box as well as a "Default VBA Device"

6 - VBA name resolvable (short and FQDN). DNS entries created prior to VBA deployment. VBA is also successfully registered in vCenter.

7 - I haven't even started. The error i'm getting is straight after the initial configuration of the VBA. Some things are created in networker (VMware backup policy, VBA default device) showing that communication is working. Just not the one registering the appliance.

Can you possibly change the ddboost password on DD and then change into Avamar I mean VBA.

Also I hope you have allocated at least 1 TB of storage.

Please let me know if you require command to change password on VBA.

Sent from my iPhone

Also EBR will never prompt you for DDBOOST PASSWORD, however it is when you integrate a boost device to run a backup, or choose a media pool. VBA as it is Avamar and MCCLI does not support special characters as of now.

Sent from my iPhone

Two things!!!

Are you looking at logs under monitoring tab which says registration of VBA failed..

Or somewhere else.

Did you got a chance to check any default policy being created.

Are you able to create a new policy.

Another thing is you mentioned both connection tests with VCenter and Networker were successful.

I would like to ask you, what version of VCenter you are using, and what version of NW.

Did you created a support case!!!

Sent from my iPhone

Sometimes I've seen issues where new AFTD's aren't correctly labeled during creation(and the internal storage in the VBA is indeed a AFTD). Last time I ran into this when deploying a VBA, I just labeled the device manually like I would do with any other device. Then I rebooted the VBA through vcenter and everything was fine.

/tony

Any updates on this???

the following is the command which can be used.

mccli dd edit --name=fqdn --password=nnnnn --password-confirm=nnnnn --user-name=boostuser