SNMP Agent Configuration

The Solaris SNMP master agent and other Solaris subagent(s) are optional SNMP agents which support the MIBII group and other Solaris and Sun-related MIBs.

Note When SNMP is installed as the Master Agent, it offers all the functionality that the MIB provides, but no 3rd-party MIB support (i.e., MIBII). When installed under the Solaris Master Agent, the SNMP agent performs in a subagent role.

Administering SNMP Agents as Master on the Gateserver

Step 1 Go to the Gateserver on which you would like to administer SNMP agents.

Step 2 Edit the $PARMLIB/parms/SNMP/SPsnmp.ini file.

Table 14-1: SPsnmp.ini parameters

Section Parameter Name Description Valid Values and Defaults

[Logging]

SPLogLevel

The are 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

[SPMonitoringRates]

STATENOTIFY

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, TNT

Default:

[Autorestart]

APP

Restarts the agent on a reboot.

Valid Values: On, Off

Administer SNMP as sub-agent - Using Solaris Master Agent

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 SolsticeSNMP agent.

/etc/snmp/conf/snmpdx.rscr
/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 is necessary to run to support MIB II

These resource/configuration/registration files are also available when the Solaris Solstice SNMP agent is installed. The snmpdx.rscr needs to be modified to invoke the UCD SNMP sub-agent when the SNMP master comes up. The modification can be seen later.

/etc/snmp/conf/ucd.reg

This file needs to be copied to this directory from the Sample directory. A sample of this file can be seen later in the following section.

Note The S88sp is omitted in this configuration.

Enabling Trap Messages

The uOne product provides SNMP traps to allow for timely notification of alarms. For uOne to send a trap messages to the SNMP Manager, you must enable that trap message.

Note The SNMP Manager is defined in the SPsnmp.ini file during system configuration.

To enable a trap, perform the following steps:

Step 1 Go to $PARMLIB/logs/msgformats.

Step 2 Use the Samples file to create a <filename>.trap file. You can use any name 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:

trap_name trap_number keyword

Refer to Table 14-2 for a descriptions of these parameters. Figure 14-1 provides an example of a <filename>.trap file.

Table 14-2: <filename.trap Parameter Descriptions

Parameter Description Valid Values

trap_name

The name of the trap message. Refer to the uOne Operations Manual for trap message definitions.

See Table 14-3.

trap_number

The trap message ID.

See Table 14-3.

keyword

Indicates whether or not to sent the trap message.

ON=Send the trap message

OFF=Do not send the trap message.

Parameter	Description	Valid Values
trap_name	The name of the trap message. Refer to the uOne Operations Manual for trap message definitions.	See Table 14-3.
trap_number	The trap message ID.	See Table 14-3.
keyword	Indicates whether or not to sent the trap message.	ON=Send the trap message OFF=Do not send the trap message.

Figure 14-1: A Sample <filename>.trap File

Supported Traps

You can enable any of the traps listed in Table 14-3. Refer to the uOne Operations Manual for the supported SNMP trap message definitions..
Table 14-3: Trap Message Names and IDs

Trap Name Trap ID

app_badparmlen

3098

app_badreload

3105

app_badtime

3103

app_execerr

3097

app_GenErr

1509

app_GenErr

3102

app_GenInfo

1507

app_GenInfo

3116

app_GenWarn

1508

app_GenWarn

3104

app_I_NoReStart

3115

app_imaplogin

1502

app_invalidparm

3099

app_IstaticExit

3112

app_ldapbind

1051

app_ldapopen

1050

app_maxGrpInst

3109

app_maxInst

3107

app_moreStaticInst

3106

app_noAppFound

3110

app_nopgm

3114

app_nostart

3118

app_nostart_pid

3117

app_numparm

3100

app_quiesceInst

3108

app_start

3113

app_statictime

3101

app_WstaticExit

3111

CmdGenErr

3119

com_API

3058

com_bad_len

3091

com_BadHeader

3086

com_client

3057

com_datatype

3092

com_dberror

3067

com_E_DSERV_Lkup

3088

com_errfile

3063

com_errline

3065

com_error

3093

com_errutil

3059

com_Eutilmsg

3078

com_GenErr

3095

com_GenInfo

3120

com_GenWarn

3096

com_hostinfo

3094

com_I_DSERV_Lkup

3090

com_IDumpThrd

3084

com_init

3053

com_initerr

3056

com_INodumpThrd

3085

com_invalidparm

3062

com_Iutilmsg

3080

com_log

3054

com_logwait

3055

com_netreject

3068

com_nomore

3060

com_numparm

3061

com_parmerr

3066

com_pingwarn

3069

com_rejmsgdata

3076

com_rejmsghead

3073

com_rejmsgnxt1

3074

com_rejmsgnxt2

3075

com_rxerr

3071

com_rxinfo

3070

com_ServRun

3087

com_shut

3072

com_syserr

3050

com_syserrstr

3051

com_syswarn

3052

com_threrr

3081

com_vererr

3077

com_W_DSERV_Lkup

3089

com_warnfile

3064

com_WMaxThreads

3082

com_WNoThreads

3083

com_Wutilmsg

3079

mwinotify_err

1403

mwinotify_info

1405

mwinotify_warn

1404

mwionoff_err

1303

mwionoff_info

1305

mwionoff_warn

1304

pag_connect

1503

ssio_trap_lockE

1035

tntapi_GenErr

1054

tntapi_GenInfo

1056

Tntapi_GenWarn

1055

UM_error

1503

UM_info

1505

UM_inimissing

1506

UM_noiniinsch

1507

UM_warn

1504

Trap Name	Trap ID
app_badparmlen	3098
app_badreload	3105
app_badtime	3103
app_execerr	3097
app_GenErr	1509
app_GenErr	3102
app_GenInfo	1507
app_GenInfo	3116
app_GenWarn	1508
app_GenWarn	3104
app_I_NoReStart	3115
app_imaplogin	1502
app_invalidparm	3099
app_IstaticExit	3112
app_ldapbind	1051
app_ldapopen	1050
app_maxGrpInst	3109
app_maxInst	3107
app_moreStaticInst	3106
app_noAppFound	3110
app_nopgm	3114
app_nostart	3118
app_nostart_pid	3117
app_numparm	3100
app_quiesceInst	3108
app_start	3113
app_statictime	3101
app_WstaticExit	3111
CmdGenErr	3119
com_API	3058
com_bad_len	3091
com_BadHeader	3086
com_client	3057
com_datatype	3092
com_dberror	3067
com_E_DSERV_Lkup	3088
com_errfile	3063
com_errline	3065
com_error	3093
com_errutil	3059
com_Eutilmsg	3078
com_GenErr	3095
com_GenInfo	3120
com_GenWarn	3096
com_hostinfo	3094
com_I_DSERV_Lkup	3090
com_IDumpThrd	3084
com_init	3053
com_initerr	3056
com_INodumpThrd	3085
com_invalidparm	3062
com_Iutilmsg	3080
com_log	3054
com_logwait	3055
com_netreject	3068
com_nomore	3060
com_numparm	3061
com_parmerr	3066
com_pingwarn	3069
com_rejmsgdata	3076
com_rejmsghead	3073
com_rejmsgnxt1	3074
com_rejmsgnxt2	3075
com_rxerr	3071
com_rxinfo	3070
com_ServRun	3087
com_shut	3072
com_syserr	3050
com_syserrstr	3051
com_syswarn	3052
com_threrr	3081
com_vererr	3077
com_W_DSERV_Lkup	3089
com_warnfile	3064
com_WMaxThreads	3082
com_WNoThreads	3083
com_Wutilmsg	3079
mwinotify_err	1403
mwinotify_info	1405
mwinotify_warn	1404
mwionoff_err	1303
mwionoff_info	1305
mwionoff_warn	1304
pag_connect	1503
ssio_trap_lockE	1035
tntapi_GenErr	1054
tntapi_GenInfo	1056
Tntapi_GenWarn	1055
UM_error	1503
UM_info	1505
UM_inimissing	1506
UM_noiniinsch	1507
UM_warn	1504

In addition to traps in Table 14-3, uOne provides the hard-coded traps listed in Table 14-4. You don't have to enable hard-coded traps
Table 14-4: Hard-coded SNMP Traps

Trap Name Trap ID

app_trap_coreE

1021

app_trap_startI

1010

app_trap_stopE

1020

app_trap_stopI

1011

base_trap_startI

1001

base_trap_stopI

1000

log_trap_termE

1030

snmpMmapCloseFail

10001

snmpMmapFileErr

10004

snmpMmapGenErr

10005

snmpMmapOpenFail

10000

snmpMmapReadFail

10002

snmpMmapWriteFail

10003

SP4_TNTAgentDown

2001

SP4_TNTAgentUp

2002

ssio_trap_lockE

1035

Trap Name	Trap ID
app_trap_coreE	1021
app_trap_startI	1010
app_trap_stopE	1020
app_trap_stopI	1011
base_trap_startI	1001
base_trap_stopI	1000
log_trap_termE	1030
snmpMmapCloseFail	10001
snmpMmapFileErr	10004
snmpMmapGenErr	10005
snmpMmapOpenFail	10000
snmpMmapReadFail	10002
snmpMmapWriteFail	10003
SP4_TNTAgentDown	2001
SP4_TNTAgentUp	2002
ssio_trap_lockE	1035

SNMP Security Issues

Note When ther e is no Solaris Master agent, ensure that the ucd-snmpd.conf file has been configured using the Quick Configuration tool.

The following issues surrounding the SNMP agent:

access
read
write

In order to control access of the SNMP agent in reading and writing from the SNMP agent.

Table 14-5: ucd-snmpd.conf file

Keyword Description

sysdescr

String to use for system description.

syscontact

String to use for system contact.

syslocation

String to use for system location.

system-group-read-community

Community name needed for read access to the system group.

system-group-write-community

Community name needed for write access to the system group.

read-community

Community name needed for read access to the entire MIB.

write-community

Community name needed for write access to the entire MIB. (Read access is implied.)

trap

Host names where traps should be sent. A maximum of five hosts may be listed.

trap-community

Community name to be used in traps.

kernel-file

Filename to use for kernel symbols.

managers

Hosts that can send SNMP queries. Only five hosts may be listed on any one line. This keyword may be repeated may be repeated for a total of 32 hosts.

newdevice

The following table applies for the use of a Solaris SNMP Master agent.

Section	Parameter Name	Description	Valid Values and Defaults
[Logging]
	SPLogLevel	The are 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
[SPMonitoringRates]
	STATENOTIFY	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, TNT Default:
[Autorestart]
	APP	Restarts the agent on a reboot.	Valid Values: On, Off

Keyword	Description
sysdescr	String to use for system description.
syscontact	String to use for system contact.
syslocation	String to use for system location.
system-group-read-community	Community name needed for read access to the system group.
system-group-write-community	Community name needed for write access to the system group.
read-community	Community name needed for read access to the entire MIB.
write-community	Community name needed for write access to the entire MIB. (Read access is implied.)
trap	Host names where traps should be sent. A maximum of five hosts may be listed.
trap-community	Community name to be used in traps.
kernel-file	Filename to use for kernel symbols.
managers	Hosts that can send SNMP queries. Only five hosts may be listed on any one line. This keyword may be repeated may be repeated for a total of 32 hosts.
newdevice

Table of Contents