well documented<\/a> by VMware so there is not much to really discuss on it.\u00a0 Basically it’s a few steps to ensure that the new IP is listed in the database.\u00a0 However, if you don’t perform the last step listed below this can be re-wrtten on a reboot.<\/p>\nThird, Change OVA attributes<\/h3>\n This is the most important step and one that took myself and Jon Hildebrand a little bit of digging.\u00a0 The fact is the appliance on reboots re-checks the original settings in the OVA files.\u00a0 Below are the commands to help you make the final change so you will not have issue on reboot<\/p>\n\n\n\n
root@vcloud [ ~ ]# ovfenv\n[vami.DNS.VMware_vCloud_Director]=10.25.10.101,10.25.10.102\n[vami.domain.VMware_vCloud_Director]=VCD01\n[vami.gateway.VMware_vCloud_Director]=10.25.0.1\n[vami.ip0.VMware_vCloud_Director]=10.25.10.130\n[vami.ip1.VMware_vCloud_Director]=10.25.10.131\n[vami.netmask0.VMware_vCloud_Director]=255.255.240.0\n[vami.netmask1.VMware_vCloud_Director]=255.255.240.0\n[vami.searchpath.VMware_vCloud_Director]=corp.cohesity.rocks\n[vcloudapp.db_ha_type.VMware_vCloud_Director]=primary\n[vcloudapp.enable_ssh.VMware_vCloud_Director]=True\n[vcloudapp.expire_root_password.VMware_vCloud_Director]=False\n[vcloudapp.nfs_mount.VMware_vCloud_Director]=prd-coh01.corp.cohesity.rocks:\/VCDTransfer\n[vcloudapp.ntp-server.VMware_vCloud_Director]=time.nist.gov\n[vcloudapp.varoot-password.VMware_vCloud_Director]=#vf6l7&&9YQn!H&pH\n[vcloudconf.admin_email.VMware_vCloud_Director]=tag-admins@cohesity.com\n[vcloudconf.admin_fname.VMware_vCloud_Director]=vCD Admin\n[vcloudconf.admin_pwd.VMware_vCloud_Director]=Mdu2eaK9w00c@EmlO\n[vcloudconf.admin_uname.VMware_vCloud_Director]=administrator\n[vcloudconf.ceip_enabled.VMware_vCloud_Director]=False\n[vcloudconf.db_pwd.VMware_vCloud_Director]=#5e0#4$s0Mb76Gzgo\n[vcloudconf.inst_id.VMware_vCloud_Director]=1\n[vcloudconf.sys_name.VMware_vCloud_Director]=vcd\n[vcloudnet.routes0.VMware_vCloud_Director]=\n[vcloudnet.routes1.VMware_vCloud_Director]=\n[vm.vmname]=VMware_vCloud_Director\n\n#Determine the values to change which the key ones for me were:\n[vami.ip1.VMware_vCloud_Director]=10.25.10.131\n[vami.netmask1.VMware_vCloud_Director]=255.255.240.0\n\n#Update the Variables as needed\nroot@vcloud [ ~ ]# ovfenv --key vami.ip1.VMware_vCloud_Director --value \"10.10.10.130\"\nroot@vcloud [ ~ ]# ovfenv --key vami.netmask1.VMware_vCloud_Director --value \"255.255.255.0\"<\/pre>\n\n\n\nOnce all this is completed you can reboot the machine multiple times and you should be getting the new database IP consistently.<\/p>\n","protected":false},"excerpt":{"rendered":"
Believe it or not I ran into this problem recently.\u00a0 Suffice to say I realized if you deploy the VMware Cloud Director appliance with the primary and database IP on the same VLAN, some things go a little wonky.\u00a0 A few people mentioned outside the official docs that you should not do this, but it …<\/p>\n","protected":false},"author":2,"featured_media":7839,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[5],"tags":[],"jetpack_publicize_connections":[],"yoast_head":"\n
How to Properly Change The VMware Cloud Director Database IP \u2022 Chris Colotti's Blog<\/title>\n \n \n \n \n \n \n \n \n \n \n \n\t \n\t \n\t \n \n \n \n \n \n\t \n\t \n\t \n