Generate Siebel lbconfig.txt to not conflict with existing Siebel installation

Hello, we have a Siebel version already deployed using a generated lbconfig.txt file, deployed to physical servers. We have upgraded to new physical servers (in parallel) and generated a new lbconfig.txt file but the opbject names in the F5 are now in conflict (EAIObjMgr_enuConnPool, etc.).

 

How can I generate slightly different names in the lbconfig.txt file so I can have two versions running on the same F5 and not have te object / pool names conflict? Are the names tied to some internal F5 functionality so appending a "_2" at the end of the name would cause an issue?

 

Please advise.

 

Thank you.