Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[SBR] SBR Carrier not responding to RADIUS requests



Article ID: KB27846 KB Last Updated: 08 Mar 2017Version: 3.0

This article is intended to help troubleshoot times when the NAS reports that communication to SBR Carrier has been lost, or when the NAS reports that SBR Carrier has stopped responding to requests. This is not a comprehensive list of all causes, but a guide to help troubleshoot the most common reasons for this issue.



There are a few reasons why the SBR Carrier may stop responding to RADIUS requests. These include a network error causing responses or request to be dropped before they arrive at the server, or communication issues with a back end database or a proxy target.

  1. Verify that the RADIUS process is running and that the process is not out of memory or CPU time.

    To verify that the process is running:

    -bash-3.00# ps -ef |grep radius
    root 29284 1108 0 Jul 02 ? 49:25 radius sbr.xml
    root 16375 1456 0 11:23:12 pts/1 0:00 grep radius

    If you see that the RADIUS process has stopped, check to see if there were core files generated and contact JTAC for assistance.

    -bash-3.00# cd /opt/JNPRsbr/radius
    -bash-3.00# ls -l core*

    To view the CPU and memory utilization of the process:

    On Solaris:

    -bash-3.00# prstat |grep radius
    29284 root 165M 84M sleep 59 0 0:49:25 0.0% radius/71

    On Linux:

    [root@linux radius]# top |grep radius
    2154 root 20 0 663m 62m 10m S 0.3 0.5 49:54.82 radius

  2. If the RADIUS process is running and CPU/Memory utilization are not high, we need to start looking at the SBRC logs.
  3. Check to see if SBR is dropping received requests. From the RADIUS install directory, run the following command:

    < -bash-3.00# grep -i drop <date>.log

    If there are drops reported in the logs, further investigation is required, skip to step 4.

    If there are no drops reported proceed to step 3.

  4. Verify that messages leaving the NAS are being received by the SBRC server.

    Run a packet capture on the NAS while running a packet capture on the SBRC server. In the trace, verify that the Packets leaving the NAS are received by the Server.

    If any packets are not seen on both ends, the issue is in the network between the NAS and SBRC; more network troubleshooting is needed to identify where the drops are occurring

  5. Determine configuration
  6. Are you using an external authentication or accounting database?

    Are you forwarding requests to a proxy target?

    Is this server part of a cluster or is this a standalone installation?

    Proxy targets and external databases

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search