SDX 6.4.x Monitoring and Troubleshooting Guide > Using the SNMP Agent > Adding an SNMP Agent Component

Adding an SNMP Agent Component

To add a component:

1. In SDX Admin, navigate to the desired component folder. For example:

ou=Components, ou=System Management, ou=Configuration, o=Management, o=umc

2. Right-click ou=Components, and select New > Component.
3. In the New Component dialog box, enter a name or select a name from the drop-down list. Names must be no more than 50 characters.

The Component pane appears. If you selected a name from the drop-down list, the software fills in default values.

4. Use the field descriptions in Component Fields to configure the component.
5. Restart the SNMP agent to update the agent with the changes.

Component Fields

Use the fields in this section to configure SNMP components.

Technical Name

• Technical name for the component.
• Value—You can enter a value or select a value from the drop-down list. The value depends on the application type:

• For a PYTHON application type, use the path to the file that contains the Python program that is executed by the Python process as it appears on the command line of the executed Python command. (Because all Python components run in a process in which the command name is python, you must provide the path to distinguish the Python program from other Python components running on the same host.)
• For a PROCESS application type, use the executed command.
• For a JAVA application type, use the full package/class name of the class with the "main" function that appears as an argument to the Java command that starts the component. (Because all Java components run in a process in which the command name is java, you must provide the name of the main class for a Java component to distinguish it from other Java components running on the same host.)
• For CONTAINER and MGMTIF application types, the technical name of the component is not necessary and is ignored.

• Default—If you selected a name in the New Component dialog box, the software enters a technical name for you. Otherwise, there is no default.
• Example—net.juniper.smgt.gateway.nic.host.NicHost

Application Type

• The application type of the component.
• Value

• JAVA—Java process
• MGMTIF—Management interface used to monitor SDX-based components, such as subscriber portals or the Workflow application.
• PROCESS—UNIX process, such as Merit RADIUS or OpenLDAP
• PYTHON—Python process
• CONTAINER—Component that groups related components that need to be monitored as a group. In the MIB, a container component sends a trap if any of its contained components fails. See Components.

• Guidelines—A container component cannot contain another container. It can contain only Python, process, Java, or mgmtif components.
• Default—If you selected a name in the New Component dialog box, the software enters an application type for you. Otherwise, there is no default.

Polling Interval

• Length of the interval between checks by the SNMP agent that the component is running.
• Value—Number of seconds in the range 1-3600. You can enter a value or select a value from the drop-down list.
• Default—Depends on the type of component

Description

• Text description of the component.
• Value—String
• Guidelines—Optional
• Default—No value

Start Command

• Software command that starts the component.
• Value—Path and command
• Guidelines—The software must be configured to start the component with SNMP. When SNMP is used to set the administrative state of a container component, it ignores the start and stop commands of the container component. The start and stop commands of the container component are used to start and stop the whole component and are assumed to manage the starting and stopping of the processes that correspond to the subcomponents.
• Default—For most SDX components, the software enters the correct start command as long as the component is installed in the default location.
• Example—/opt/UMC/openldap/etc/ldap start

Stop Command

• Software command that stops the component.
• Value—Path and command
• Guidelines—The software must be configured to stop the component with SNMP. When SNMP is used to set the administrative state of a container component, it ignores the start and stop commands of the container component. The start and stop commands of the container component are used to start and stop the whole component and are assumed to manage the starting and stopping of the processes that correspond to the subcomponents.
• Default—For most SDX components, the software enters the correct stop command as long as the component is installed in the default location.
• Example—/opt/UMC/openldap/etc/ldap stop

Install Date

• Date component was installed.
• Value—Date in the format YYYYMMDD or YYYYMMDDhhmmssZ

• YYYYMMDD indicates the year, the month, and the day
• hhmmss indicates the hour, the minute, and the second
• Z = Coordinated Universal Time (UTC)

• Guidelines—Optional
• Default—No value

Manufacturer

• Component manufacturer.
• Value—Text name of a manufacturer
• Guidelines—Optional
• Default—If you selected a name in the New Component dialog box, the software enters a manufacturer for you. Otherwise, there is no default.

Version

• Software version of the component.
• Value—Text or integer
• Guidelines—Optional
• Default—No value

Deleted

• Specifies the availability of this entry to other SDX components connected to the directory.
• Value

• Blank—Other SDX components can access this entry in the directory.
• True—Other SDX components cannot use this entry in the directory, although the object still exists.
• False—Other SDX components can access this entry in the directory.

• Default—Blank