|
|
The Solaris SNMP master agent and other Solaris subagent(s) are optional SNMP agents that support the MIB-II group and other Solaris and Sun-related MIBs.
The uOne SNMP agent and any desired 3rd party SNMP agents must be installed.
 |
Note When the uOne SNMP agent is installed as a Master Agent, it offers all the functionality that the uOne MIB provides, but no 3rd-party MIB support (i.e., MIB-II). When installed under the Solaris Master Agent, the uOne SNMP agent performs in a subagent role. |
Via FTP, copy the following mib/trap files from the gateserver to the SNMP manager and load in the order below.
amteva.txt
umGen.txt
umAppSchedule.txt
umApp.txt
umMwiFax.txt
umH323.txt
umRadRtp.txt
umMwiNotify.txt
umSCR.txt
umSMSI.txt
umSMSNotify.txt
umSnmpLog.txt
umLogMonitor.txt
umTTS.txt
umTrap.txt
umTnt.txt
umXGCP.txt
spSnmpTrap.txt
|
Note Removing the mibs/traps should be done in the opposite order. |
This file is set up during initial configuration via the quickconfig tool. The tool sets up the uOne SNMP agent to run as a master agent. If you wish to run it as a subagent, you must also follow the steps of the next section, "uOne SNMP Agent as Sub-Agent - Using the Solaris Master Agent (Optional)".
Step 2 Edit the $PARMLIB/parms/SNMP/SPsnmp.ini file.
| Section | Parameter Name | Description | Valid Values and Defaults |
[Logging] |
|
|
|
| SPLogLevel | Four logging levels of the SNMP system. | Valid Values: Error, Warning, Information, Debug Default: Error, Warning, Information |
[UM System Group] |
|
|
|
| UMSYSDESCRIBER | Identifies various aspects of the gateserver. See Samples file. | Valid gateserver information. |
| UMSYSNAME | ||
| UMSYSVERSION | ||
| UMSYSCONTACT | ||
| UMSYSLOCATION | ||
[Rollover Info] |
|
|
|
| SPLOGFILESIZE | The size (in megabytes) that a log file reaches before the agent creates a new file for logging messages. | Valid Values: 1-8 Default: 4 |
| SPLOGFILEAGE | The age (in hours) that a log file reaches before the agent creates a new file for logging messages. | Valid Values: 1-168 Default: 24 |
[TrapInfo] |
|
|
|
| MANAGERLIST | List of the SNMP Managers where traps are sent. | Valid SNMP Managers |
[TrapCommunityString] |
|
|
|
| TRAPCOMMUNITY |
| Valid Community |
[SPMonitoringRates] |
|
|
|
| Specifies the number of seconds that the SNMP agent will log the current state(s) of the managed object(s). | Valid Values: 60 - 3600 Default: 60 | |
| WATCHDOG | Specifies the number of seconds that the SNMP agent watches the current status of the ACB. | Valid Values: 15 - 300 Default: 60 |
[Objects] |
|
|
|
| MANAGEDOBJECTLIST | Specifies a list of application process(es) whose state(s) are monitored by the state-notify function. | Valid Values: APP |
[Autorestart] |
|
|
|
| APP | Restarts the agent on a reboot. | Valid Values: On, Off |
The following files should be in place:
/usr/lib/snmp/snmpdx (This is the Solaris SNMP Master Agent.)
This file comes with the Solaris Solstice SNMP agent when it is installed. This is the binary file of the Solaris Solstice SNMP agent. Additional files are:
/etc/snmp/conf/snmpdx.rsrc /etc/snmp/conf/snmpdx.reg /etc/snmp/conf/snmpd.conf /etc/snmp/conf/mibiisa.reg (See Note below.) /usr/lib/snmp/mibiisa (See Note below.)
|
Note The mibiisa files are necessary to run to support MIB-II. |
1. These resource/configuration/registration files are also available when the Solaris Solstice SNMP agent is installed. The snmpdx.rsrc needs to be modified to invoke the UCD SNMP subagent when the SNMP master comes up. The modification can be seen later.
2. Setup the following files:
a. /etc/init.d/init.snmpdx
b. /etc/snmp/conf/ucd.reg
c. $PARMLIB/SNMP/ucd-snmpd.conf
|
Note The S88sp file should be moved from /etc/rc3.d in this configuration. |
The snmpdx.rsrc file needs to be modified.
|
Note Add the lines shown in bold. |
Each section in the resource group represents the information for each SNMP subagent.
| Parameters | Description |
|---|---|
Identifies the full path file of the registration for this particular SNMP subagent. | |
Specifies how this SNMP subagent is evoked. | |
Specifies the type of this SNMP subagent | |
Specifies the full path command to start up this SNMP subagent |
The init.snmpdx file needs to be modified.
The ucd.reg file needs to be modified.
The ucd-snmpd.conf file needs to be modified.
These traps are not actually sent by the uOne SNMP agent; rather they are sent by ACB and its agents via TRAPMAN. The uOne product provides SNMP traps to allow for timely notification of alarms. For uOne to send an ACB/Agent nonhard-coded trap message to SNMP managers, you must enable that trap message.
|
Note The SNMP managers are defined in the SPsnmp.ini file during initial system configuration. |
To enable a trap, perform the following steps:
Step 2 Use the sample file to create a <filename>.trap file. You must use a name such as com.trap, <obj>.trap, or <agent>.trap for the <filename>.
Step 3 Edit or add a line for each trap message you want to enable. Each line must be in the following format:
Sofmessage_name trap_number keyword
Refer to Table 15-3 for a descriptions of these parameters. Figure 15-1 provides an example of a <filename>.trap file.
| Parameter | Description | Valid Values |
|---|---|---|
Sofmessage_name | The name of a non-debug Sof log message defined in a .src file. Refer to the .src files in the $PARMLIB/logs/msgformats directory. | See Appendix E in the Operations Manual. |
trap_number | The enterprise-specific trap ID. | See Appendix E in the Operations Manual. |
keyword | Indicates whether to send the trap message. | ON=Send the trap message OFF=Do not send the trap message. |
app_trap_startI 1010 ON
app_trap_stopI 1011 ON
app_trap_coreE 1021 ON
app_trap_stopE 1020 ON
base_trap_startI 1002 ON
base_trap_stopI 1000 ON
log_trap_termE 1030 ON
log_trap_diskE 1031 ON
ssio_trap_lockE 1035 ON
ssio_trap_fileW 1036 ON
Please refer to "Supported Traps" in the uOne Operations Manual for the supported SNMP trap ID definitions.
|
Note The SNMP tools in $PARMLIB/SNMP/bin works with the uOne SNMP agent; however, they do not support the use of symbolic names for the MIB objects in the enterprises.amteva subtree. You must therefore use OID (Object ID) numbers only for objects in that subtree when using these tools. We encourage you instead to use a commercial SNMP manager loaded with our MIB modules and/or uOne Manager to access uOne MIB objects. |
Posted: Mon Sep 25 20:22:48 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.