User's Manual

4.2 Using an External SNMP Manager

4.2.1 Access to SNMP Agent

The SNMP agent, by default, is not configured to interact with any other external SNMP manager for security

reasons. If an external SNMP manager is desired, the file /etc/snmp/snmpd.conf must be modified to include

the host IP address of the SNMP manager.

Example of /etc/snmp/snmpd.conf

####

# First, map the community name (COMMUNITY) into a security name

# (local and mynetwork, depending on where the request is coming

# from):

# sec.name source community

com2sec local localhost public

com2sec server 192.168.169.171 public

com2sec theworld default public

####

# Second, map the security names into group names:

# sec.model sec.name

group MyRWGroup any local

group MySVGroup any server

group MyROGroup any theworld

####

# Third, create a view for us to let the groups have rights to:

# incl/excl subtree mask

view all included .1 80

# Finally, grant the 2 groups access to the 1 view with different

# write permissions:

# context sec.model sec.level prefix read write notif

access MyROGroup "" any noauth 0 none none none

access MySVGroup "" any noauth 0 all all none

access MyRWGroup "" any noauth 0 all all none

To allow a SNMP host to interact with AMU SNMP agent, the IP address 192.168.169.171 shall be replaced

with another the SNMP manager host IP address.

4.2.2 Manipulating AMU MIBs

There are a few important concepts that an external SNMP manager needs to know in order to manage AMU

properly:

1) Server Discovery Object

• The SNMP GET operation has to be performed

i. If it is the first time for the SNMP session to communicate with the agent.

ii. If number of AirEZY servers managed by the AMU has changed.