ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins. Read more for important details.
ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins.Read more for important details.

BorderManager 3.9 iManager Plugin Problems

Absent Member.
Absent Member.
0 2 3,029
0 Likes
If you have installed a new BorderManager 3.9 on a NetWare 6.5 SP6.

BorderManager was installed with DNS, HTTP/S, Real Player/RTSP proxies and not the VPN option, but when trying to access any of the BM settings in iManager, the browser doesn't show anything.

iManager works fine for all other products and configurations.

You...

  • Restarted Apache/Tomcat.

  • Reinstall BorderManager.

  • Uninstall/reinstall the iManager plugins.

  • Ran the fillattr process.

  • Put a eDirectory replica on the server.

  • Ran dsrepair on the Master and R/W replicas and didn't get any errors.

  • Check timesync for all server and didn't get any errors.


But...the problem still remains.

Try this.

First Phase



  • With ConsoleOne check all BM´s attributes in the server, specially BDRSRVR: PROXY Info DeviceXLM attribute.

  • If you see a lot of zeros (0) into BDRSRVR: PROXY Info DeviceXLM attribute, follow to next step -- if not go to Second Phase.

  • The BDRSRVR: PROXY Info DeviceXLM attribute has a long configuration in this attrib, something like this:



<romaAGDevice ConfigUserName="config.ics.ics_tree" ManagementAddress="164.99.171.223" ManagementPort="1443" ConfigPassword="Hd93k01@3fdKh3" DeviceDescription="" DeviceLocation="" DisplayName="164.99.171.223" DeviceVersion="1.5.0000.DEV" DeviceType="ag" exA>




  • With any LDAP Administrator software (Softerra LDAP Administrator is well), replace this attribute or copy it from another BorderManager 3.9 server.

  • Run a DSrepair and check for any messages.



Second Phase



  • Through an old NWadmin with BorderManager 3.8 snapins, modify the configuration of the BM server. (This wrote the configuration in format 3,8 or lower in the server object).

  • In the Logger (server console) see a message reporting something like "the change should be made with iManager".

  • Import the configuration with the FILLATTR utility.

  • ¡Ready! iManager can read the configuration in the proxy section.



I hope this helps.
Tags (2)
2 Comments
Absent Member.
Absent Member.
This is clearly a good answer, but some people might not interpret some of it the same way the writer does. Also, some people may need to have some steps included that the writer naturally assumes they will know to take, so those steps are skipped over.

If you are going to document, please document completely. And assume nothing, as far as your readership is concerned.
Absent Member.
Absent Member.
Thanks Chirock by your suggestion.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.