The following messages are seen in the VNM.OUT/Spectrum Control Panel:
ERROR TRACE at CsCorbaMgr.cc(1254): Failed to connect to CORBA Naming Service on corbaloc::SERVERNAME:14006/NameService, will retry in 5 seconds.
You may also see:
ERROR TRACE at CsCorbaMgr.cc(1260): Could not create a root naming context. Maximum number of retries exceeded.
CORBA exception: Exception: CORBA::NO_PERMISSION
Completion Status: NO
1. Check the following line in the $SPECROOT/.jcorbarc file which must be false:
Also in the .corbarc in the same location, the line must also be false:
2. Review the $SPECROOT/bin/VBNS/NAMINGSERVICE.OUT. If you see this message in regards to "Anonymous ciphers" then you have a policy that blocks them:
org.omg.CORBA.INITIALIZE: Couldn't not resolve ServerManager:
org.omg.CORBA.BAD_PARAM: Anonymous Ciphers must be enabledif No certificates are present
You will need to either update your policy to allow anonymous ciphers or disable the ability to use secure corba. If you must use secure CORBA then you must update your policy to allow for anonymous ciphers.
To disable the ability to use secure CORBA, please do the following:
a. Edit BOTH the $SPECROOT/.corbarc and the $SPECROOT/.jcorbarc and change this to true:
Also verify this is false. If it is true, change it to false:
After changes are made the SpectroSERVER must be shutdown, and processd restarted.
For details on restarting processd, please reference the "Setting Up a Distributed SpectroSERVER Environment" section of the documentation.
Enhanced Functionality to utilize secure ciphers is in DX NetOps Spectrum 21.2.1 onwards - Secure CORBA Enhancements. See here: https://knowledge.broadcom.com/external/article?articleId=189064
How to ENABLE secure CORBA: https://knowledge.broadcom.com/external/article?articleId=72596