Backup & Recovery

 View Only
  • 1.  Unable to configure vdp

    Posted May 29, 2013 12:28 PM

    Hi,

    After trying to reinstall my vdp appliance, I'm unable to configure it :

    Acces to https://vdp:8543/vdp-configure/ is OK

    • I type changeme, fill all the forms, test connection is OK
    • I type Finish -> VDP say me that I is going to reboot, I choose "restart Now"

    VDP reboot, all seem to be fine. Il log again to the web interface  (https://vdp:8543/vdp-configure) with my newly created password but I do not get the page I'm expected. I have the same page as before that ask me to configure my vdp (welcome screen) ...

    Infos :

    • vcenter 5.1U1
    • vdp 5.1.10

    Wath I've tried :

    • use an active directory dedicated user -> Logging OK but vdp is not registred
    • use an system-domain dedicated user -> same as above
    • test to connect to vcenter via FQDN or IP -> same as above
    • verify all my DNS settings

    If someone has any idea...

    Thanks

    Julien



  • 2.  RE: Unable to configure vdp

    Posted May 29, 2013 03:03 PM

    After you complete the configuration, you should control the VDP from the plugin at the Web Client. Can you chack that?



  • 3.  RE: Unable to configure vdp

    Posted May 29, 2013 03:32 PM

    Non, VDP does not appear in the web client



  • 4.  RE: Unable to configure vdp

    Posted Jun 04, 2013 11:10 PM

    I'm having a similar problem (vdp-configure is looping through initial config every time), except in my case this is my 2nd VDP appliance, and the 1st one (upgraded from 5.0 to 5.1) isn't having this problem. The 2nd one actually DOES show up in the 'VDP Appliance' dropdown in the web client, but says is inaccessible.  It's saving the config info, but whatever switch flips the vdp-configure interface from 'initial' to 'operational' isn't getting flipped.

    [Followup] After a couple more passes through the initial config UI and associated reboots, nothing more, it appeared to take.



  • 5.  RE: Unable to configure vdp
    Best Answer

    Posted Jun 07, 2013 06:40 AM

    Finaly I opened a support ticket.

    Resolution is quiet simple : complete the initial config script and reboot until vdp register to vcenter (3 times aprox).

    Support say that it is a known bug...

    Julien