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] Troubleshooting SNMP polling failure on front-end servers

0

0

Article ID: KB27593 KB Last Updated: 04 Mar 2017Version: 2.0
Summary:

This article describes troubleshooting steps that should be taken when SNMP polling fails on a SBR Carrier front-end server.

Symptoms:

Information polling fails when using an SNMP manager on SBR Carrier front-end server with different SNMP MIBs.

Cause:

SBR Carrier front-end server was not listening on port default 161, as it could be conflicting with Solaris Operating system SNMP agent using the same port.

Solution:

The SBR Carrier front-end server was not listening on port 161. Port 161 was being used by a Solaris Operating system SNMP agent; this caused a conflict as the SBR SNMP agent was using the same port. A couple of options can be used to resolve the issue.

  1. To disable the solaris operating system SNMP agent so that SBR SNMP agent can use port 161

  2. To change the port used by SBR sump agent from 161 to an unused port . For example : 181

The issue was resolved after changing the port used for SNMP from 161 to another unused port on both SNMP agent and SNMP manager. SNMP polling started working.

Confirm Conflict

In order to confirm that the issue is caused by a conflicting port, execute the command ./testagent.sh from /opt/JNPRsbr/radius/snmp/bin. If the SBR Carrier SNMP agent is listening on port 161, you will see the following output:

# ./testagent.sh
SNMPv2-MIB::sysDescr.0 = STRING: SunOS SBR-ISB-FE-01 5.10 Generic_137137-09 sun4u

The following output will be displayed if the SBR SNMP agent is not listening on port 161:

# ./testagent.sh
Timeout: No Response from localhost:161.

Change Port

Test if SBR SNMP agent is capable of working if the port number is changed from default port number to an unused port. In order to do this a couple of files must be edited.

  1. Edit the testagent.sh and change the port number from 161 to an unused port.

  2. Edit the jnprsnmpd.conf and change the port number from 161 to an unused port.

  3. Restart jnprsnmpd service using the commands /etc/init.d/init.jnprsnmpd stop  and  /etc/init.d/init.jnprsnmpd start.
After making these changes, if ./testagent.sh script is executed it should display the expected output and the SNMP polling should start working on SNMP manager.

Alternatively you can also use ps -ef | grep snmp to display all the active SNMP services running on the server. 

The procedure to change the default SNMP port on Solaris OS is discussed in the following link :
http://docs.oracle.com/cd/E23823_01/html/816-5166/snmpd-1m.html









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