Specifications
Steel-Belted Radius v6.1.1 Release Notes
12 Resolved Issues
Windows Installer must be told server's role during upgrade—When you
upgrade from a previous release of Steel-Belted Radius, the installer does not
remember whether the host was a standalone server, a primary server, or a
replica server. If you give a different answer during the upgrade, results are
unpredictable. To avoid this, enter the same answer (standalone, primary, or
replica) as before. (8587)
SBR Administrator may reject a valid license—If you enter a license key using
the SBR Administrator License menu, you may see a message similar to
Registration failed - '1634 xxxx xxxx xxxx xxxx xxxx xxxx' is not compatible with this
edition of product
, even if your license key is compatible with the edition of the
product. If this occurs, use a text editor to open the
radius.lic file and remove
any licenses belonging to other editions. Add the new license key. Restart
Steel-Belted Radius. (8550)
Configuring Oracle—If you configure SBR on a Solaris computer with an
Oracle 9.2 client, the configure script prompts for the path of the Oracle shared
libraries:
Enter path for Oracle shared libraries (/app/oracle/lib):
The default response will not work in some cases, because Oracle has moved
certain 32-bit Oracle libraries to a new subdirectory. Because they are not being
will not be found. the server will not start. (8446)
To avoid this problem, reply to the prompt, replacing the default
/lib response
with
/lib32:
Enter path for Oracle shared libraries (/app/oracle/lib): /app/oracle/lib32
Import—If you export an SBR server's database and then import the data into
another SBR server, the order of ordered, multi-valued attributes such as
Calling-Station-ID may be changed. This only occurs if there are more than nine
values. This does not affect most customers. If this occurs, consider using the
LDAP Configuration Interface to move such items. (8440)
Publishing—If the scripts directory contains files larger than about 25KB,
publishing can take minutes. Avoid very large scripts. (8536)
Editing certificate information on a replica server—If the SBR Administrator
is connected to a replica server and you make a change in the Certificates
panel, the change may not be not saved, and a message box displays the
following:
</pre></BODY></HTML>
To resolve this problem, modify the certificate information on the primary
server. (8523, 8525)
Replicate Certificate check box—If the SBR Administrator is connected to a
primary server and you check Replicate Certificate in the Certificates panel
before you install a certificate, an
Error 500 error message appears. If this
occurs, add a certificate and then check Replicate Certificate. (8505)