Comtrol eCos User Manual

Page 625

Advertising
background image

Chapter 47. SNMP for eCos

the associated maximum values.

If any of the MAX1,

MAX5, or MAX15 values are unspecified, they default

to a value of DEFMAXLOADAVE.

file FILE [MAXSIZE]

Monitors

file sizes and makes sure they don’t grow

beyond a certain size.

MAXSIZE defaults

to

infi-

nite

if

not specified, and only monitors the size

without reporting errors about it.

Errors

Any errors in obtaining the above information are reported

via

the

1.3.6.1.4.1.2021.101.100

flag

and

the

1.3.6.1.4.1.2021.101.101 text-string description.

SMUX SUB-AGENTS

To enable and SMUX based sub-agent, such as gated, use the

smuxpeer configuration entry

smuxpeer OID PASS

For gated a sensible entry might be

.1.3.6.1.4.1.4.1.3 secret

ACCESS CONTROL

snmpd

supports the View-Based Access Control Model (vacm)

as defined in RFC 2275.

To this end,

it

recognizes

the

following

keywords

in

the

configuration file: com2sec,

group, access, and view

as

well

as

some

easier-to-use

wrapper

directives:

rocommunity,

rwcommunity,

rouser,

rwuser.

rocommunity COMMUNITY [SOURCE] [OID]

rwcommunity COMMUNITY [SOURCE] [OID]

These create read-only and

read-write

communities

that

can

be used to access the agent.

They are a

quick method of using the following com2sec, group,

access,

and view directive lines.

They are not as

efficient either, as groups aren’t created

so

the

tables

are possibly larger.

In other words: don’t

use these if you have complex situations to set up.

The

format

of the SOURCE is token is described in

the com2sec directive section below.

The OID token

restricts

access

for that community to everything

below that given OID.

rouser USER [noauth|auth|priv] [OID]

rwuser USER [noauth|auth|priv] [OID]

Creates a

SNMPv3

USM

user

in

the

VACM

access

configuration

tables.

Again,

its more efficient

(and powerful) to use the combined com2sec,

group,

access, and view directives instead.

521

Advertising