Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring the SNMP Agent

 

All SNMP files are installed on all Steel-Belted Radius Carrier servers, but installers have the option not to activate SNMP during the initial server configuration. If SNMP is not configured during server installation, you can activate it by rerunning the Steel-Belted Radius Carrier configuration script file, taking care not to change any other system parameters.

The files listed in Table 58 control SNMP.

Table 58: SNMP Configuration Files

Filename

Function

jnprsnmpd.conf

Stores settings for the Steel-Belted Radius Carrier SNMP agent.

testagent.sh

Test script that verifies the Steel-Belted Radius Carrier SNMP agent is operating correctly.

To change the current SNMP configuration edit radiusdir/snmp/install/jnprsnmpd.conf to reflect the network environment.

The file is self-documenting. For more information about the jnprsnmpd.conf file, see the SBR Carrier Reference Guide.

Caution

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 make any unnecessary changes and follow the embedded examples as closely as possible.

  • When specifying networks as in 172.28.68.0/24 in the line “com2sec mynetwork 172.28.68.0/24 public” make sure the trailing 32-x bits of the IP address is zero as specified by the trailing /x notation; for example, 32-24=8 bits in this case.

To verify that the jnprsnmpd SNMP agent functions, run the radiusdir/snmp/bin/testagent.sh script.

If the SNMP environment has been changed to use a port other than the default SNMP port, 161, be sure to specify that port number in the testagent.sh file.

Note

Steel-Belted Radius Carrier runs its own SNMP agent, but on most servers, additional SNMP agents are also in operation. In general, only one application can use a socket port; they are not shared resources. This means that SBR Carrier SNMP agent may conflict with Solaris SNMP or any other SNMP agent that uses socket port 161, the default SNMP port.

If you know that other agents already use port 161, change the Steel-Belted Radius Carrier port assignment by editing both radiusdir/snmp/install/init.jnprsnmpd and radiusdir/snmp/bin/testagent.sh. Remember to check your MIB browser to determine whether it also needs a corresponding port adjustment to communicate with the SBR Carrier server.