Steel-Belted Radius Carrier runs its own SNMP agent, but other SNMP agents run on most servers. In general, only one application can use a socket port; they are not shared resources.
During installation, the configure script prompts you for SNMP setup information, including an opportunity to specify a port other than the default 161 port that is usually in use by the Solaris SNMP agent.
If you already provided an alternate port during that setup step, you can skip the following procedure about how to change the port number, but remember to set your MIB browser to listen on the port you specified.
If you know that other agents already use port 161 but you did not specify an alternate during installation, change the Steel-Belted Radius Carrier port assignment by editing both radiusdir /snmp/conf/jnprsnmpd.conf and radiusdir /snmp/bin/testagent.sh. Remember to check your MIB browser to determine whether it also needs adjustment to communicate with the SBR Carrier server.
To change the port, edit the SBR Carrier SNMP configuration files listed in Table 22:
Table 22: SNMP Configuration Files
Stores settings for the Steel-Belted Radius Carrier SNMP agent.
Test script that verifies the Steel-Belted Radius Carrier SNMP agent is operating correctly.
Edit radiusdir /snmp/conf/jnprsnmpd.conf to change the port number.
The jnprsnmpd.conf file is self-documenting. For more information, see the section on SNMP Configuration Overview in the SBR Carrier Reference Guide.
The jnprsnmpd.conf file is very sensitive to stray white space and the order in which sections and parameters appear. Mistakes in this file can disable SNMP.
Make sure to make a backup copy of the file before making any changes.
While editing the file, do not to make any unnecessary changes. Follow the embedded examples as closely as possible.
When specifying networks, as in 172.28.68.0/24 in the com2sec mynetwork 172.28.68.0/24 public line, the trailing 32-x bits of the IP address must be zero as specified by the trailing /x notation. For example, 32-24=8 bits in this case.
Make the same port number change in radiusdir /snmp/bin/testagent.sh script, which is used to test the agent.
After making the change, restart either the Steel-Belted Radius Carrier server process or just its SNMP daemon.
If necessary, set up your SNMP browser to listen on the new port.
To verify that the jnprsnmpd SNMP agent functions, run the radiusdir /snmp/bin/testagent.sh script.
Refer to the SBR Carrier Administration and Configuration Guide for more information about configuring the SBR SNMP agent.