Vidm 3.3.7 Download

[Alfie Overacre]

WhenI had written my previous post on the vRealize Suite Lifecycle Manager, and integrating vIDM with it, I thought I had run up against the most obvious errors I could. See my previous post about this here: Adding Active Directory Integration to #vRealize Lifecycle Manager 2.0

The original specification of hostnames in RFC 952, mandated that labels could not start with a digit or with a minus sign, and must not end with a minus sign. However, a subsequent specification (RFC 1123) permitted hostname labels to start with digits. No other symbols, punctuation characters, or white space are permitted. Internationalized domain names are stored in the Domain Name System as ASCII strings using Punycode transcription.[4] -

Another place this message appears is in /var/log/boot.msg on the vIDM appliance. It will tell you the same, in fact this where the console is getting it from: WARNING: Invalid org name contained in hostname : 000-srv-vidm-01

Another way this error shows up, is if you go to your vIDM setup page. The one that you would normally go through if you where to role out the appliance manually. You can see exactly at what step it got stuck.

This message, i think, is being generated by the vPostgres initialization step. But I could not find another reference to it in the vPostgres logs themselves. I also found nothing at all helpful googling for this, hence I am adding the full error test here, for others.

Thank you for your informative article! It was the only reference online that I could find regarding a hostname prefixed with a number breaking vIDM. I also encountered it when deploying vRA with VRLCM, it refused to proceed with a correct FQDN with a number at the start (in my case, a 9). I created a DNS alias and put this in the retry field and now it is progressing. ?

3a8082e126