node name re-written: Upgrade from v10 - V11

I came across this issue as well. Fortunately it was a small deployment we had at the time. I could see it was going to be a much big nuisance for our larger deployment when we do upgrade at a later time.

I also recall that there seems to be more restrictions as to what chars can be used in a name ('%' no longer allowed?) under v11.

What is the rationale behind this behaviour in an upgrade? A name is just a label, and a user's choice of what to put in there, within reason, should be respected.

One year on since this question was raised, has this behaviour been changed in a later release, say, v. 11.5.0?

This software is supposed to bridge/converge network and applications, and network admins' usual preference of just using IP addresses in configurations can be a nightmare for administration of applications. I see a lot of examples of naming a virtual server "vs_blah_blah", and in my deployment I tend to use a more intuitive naming scheme, such as, my.service.my.com_443 (":" is not allowed), which makes it easier to find a service amongst a multitude of others.

Just a thought (and a couple of more questions).