Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Known Problems and Limitations

This section lists known problems and limitations identified in SBR Carrier 8.4.0. For the most complete and latest information about known defects, use the Juniper Networks online Problem Report Search application.

LDAP Authentication

  • Entering more than 124 characters for a native user password results in an erroneous rejection. PR771505
  • In previous versions of SBR Carrier in Solaris, LDAP used the Mozilla libraries for LDAP communication. When LDAP is used, this requires the Cert7.db and Key3.db files as the certificate store for trusted root certificates. Starting with SBR Carrier version 7.4.0 Linux and 7.5.0 Solaris, SBR Carrier uses the OpenLDAP libraries to process LDAP requests. For SBR to process LDAP requests, you must configure OpenLDAP to accept the server certificate.
  • When you have a large number of LDAP connections configured, SBR Carrier may hang or take several minutes to shut down, and the sbrd script may display a shutdown failure message in the terminal. PR847961

SBRC Core

  • Sessions are not handled correctly when the length of Acct-Session-Id is greater than 24 octets. For a workaround, see the PR record. PR719218
  • Profile name and response attributes are not returned by the SQLAUTH plug-in if binding order is not sequential. PR861700
  • The User Concurrency table does not display proxy realm names. PR857901
  • The Inbound-from-Proxy control point is called after, not before, the inbound filters are applied. PR889762
  • In the rfc4679.dct file, the names of the Agent-Circuit-Id and Agent-Remote-Id attributes are not defined as mentioned by RFC 4679. Instead, the names are respectively mentioned as DSL-Agent-Circuit-Id and DSL-Agent-Remote-Id.
  • Response for the SendRoutingInfoForLCS message from the HLR or HSS may not be received by authGateway if the HLR or HSS sends the message with the routing indicator in CalledPartyAddress set to “Route based on SSN”. For a workaround, see the PR record. PR987162
  • Enhanced performance counters initialize peak-rate counter to total-requests counter's value when a HUP signal is sent. PR1052592
  • If you have already added the <ANY> RADIUS client or a RADIUS Client with an IPv6 address, you cannot configure another RADIUS Client with an IPv6 address. For a workaround, see the PR record. PR1072032
  • In CST restoration blocking mode (CSTRestorationBlock = 0), SBR Carrier may core while restoring HST files under load. PR1232558
  • When the Framed-IPv6-Address attribute is configured in both the user and profile return lists, the IPv6 addresses in both the return lists are returned if the FramedIPv6AddressHint parameter is set to no. For a workaround, see the PR record. PR1303671
  • SBR Carrier cores when the HST file size exceeds the system RAM limit. For a workaround, see the PR record. PR1306886
  • In Web GUI, the Location Group pane displays only the first 50 RADIUS clients and includes non-location group clients. For a workaround, see the PR record. PR1237011
  • In Web GUI, an IP pool is unable to be created with empty address ranges for DHCP. For a workaround, see the PR record. PR1309088

SSR

  • In the WiMAX device scenario, the session table is getting updated abnormally if the OuterNAIPlusMAC parameter is set to ON. Accounting-Start fails to match the phantom session if the GenerateUniqueId parameter in the sessionTable.ini file is set to outernai-plus-mac. PR849401

SIM Authentication

  • The authGateway and GWrelay processes must be restarted whenever SBR restarts. This is applicable only on a Linux platform. PR1011144

Logging

  • Detailed EAP logging is supported only for TLS protocol version 1.0, and not for versions 1.1 or 1.2. PR1219412
  • The KPI/High-Challenge-Objects-Since-Reset statistics logged in the statistics log file may display an additional count. PR1219732
  • Transaction IDs are not logged for accounting packets when a Class attribute is not present in the packet. PR917748

Geo-Redundancy

  • When the Geo-redundancy feature is enabled, SBR Carrier on the receiving server fails to restart under load. PR1070836
  • Garbage values are displayed on the replica for NAS-Port attribute when the attribute is not present in the access request. PR1070837
  • Geo-redundancy server populates some CST fields with NULL values. PR1308295

    Caution:

    If you are using the Geo-redundancy feature, we recommend that you do not upgrade to Release 8.4.0. This issue will be resolved in a future patch.

Separate Session Database Process

  • When you upgrade SBR Carrier from releases earlier than 7.6.0, SBR Carrier automatically converts the standalone session store file (radads.hst) to a new format. This conversion delays the SBR startup for the first time after the upgrade. The approximate time taken for converting the 1-GB persistent session store file (radads.hst) to a new format (radadscst.hst) is 8–10 minutes.

3GPP AAA Module

  • The 3GPP AAA module does not initiate subscriber de-registration in the HSS. Subscriber de-registration is performed when SBR Carrier receives an HSS Registration-Termination-Request.
  • The Diameter redirection indication is supported only over the SWx reference point. The redirection indication information in an AA-Answer message, received by a proxy server from SBR Carrier over the SWd reference point, is returned to the client without attempting to forward the request to the Redirect-Host. That is, only routing rules configured by a system administrator are enforced.
  • The Redirect-Host-Usage value included in a Multimedia-Authentication-Answer message and received over the SWx reference points is ignored. The value is assumed to be DONT_CACHE.
  • In the SBR Diameter Administrator, the Permanent Failures, Transient Failures, and Protocol Errors statistics are updated based on Result-Code attribute values (not based on Diameter Experimental-Result-Code attribute values).
  • SBR Carrier fails to generate CoA/DM messages when a request is sent for RADIUS to Diameter conversion. PR1053462
  • Diameter packets are not routed to the HSS based on the IMSI prefix routing rule.

Modified: 2017-09-27