Patton CopperLink CL2300, User Manual, Page: 97 / 116

Identification of a CL2300 via SNMP 97
CopperLink CL2300 User Manual 13 • SNMP Configuration
Identification of a CL2300 via SNMP
All product models have assigned sysObjectID.
Refer to the getting started guide of your product, or see the MIB definition file (.my) for sysObjectIDs.
IMPORTANT
The SNMP agent running in Trinity is SNMP version 1
(SNMPv1) and SNMP version 2 (SNMPv2) compliant.
SNMP version 3 (SNMPv3) is not currently supported.
SNMP Tools
Patton recommends the ManageEngine .
Refer to section “Using the ManageEngine SNMP Utilities” on page 102 for more detailed information on
how to use these tools.
SNMP Configuration Task List
To configure SNMP, perform the tasks described in the following sections. The tasks in the first three sections
are required; the tasks in the remaining sections are optional, but might be required for your application.
• Setting basic system information (required) (see page 97 )
• Setting access community information (required) (see page 100 )
• Setting allowed host information (required) (see page 101 )
• Specifying the default SNMP trap target (optional) (see page 101 )
• Displaying SNMP related information (optional) (see page 102 )
Setting Basic System Information
The implementation of the MIB-II system group is mandatory for all systems. By default, an SNMP agent is
configured to have a value for any of these variables and responds to get commands from a NMS.
The following MIB II panels should be set:
• sysContact
• sysLocation
• sysName
The system sysContact object is used to define the contact person, together with information on how to con-
tact that person.
Assigning explanatory location information to describe the system physical location (e.g. server room, wiring
closet, 3rd floor, etc.) is very supportive. Such an entry corresponds to the MIB II system sysLocation object.
The name used for sysName should follow the rules for ARPANET host names. Names must start with a letter,
end with a letter or digit, and have as interior characters only letters, digits, and hyphens. Names must be 63
characters or fewer. For more information, refer to RFC 1035.
This procedure describes how to set these MIB-II system group objects.