SNMP Manager Programmer's Guide

Introduction to Manager Services
SNMP Manager Programmer’s Guide–134249
1-10
Using Trap Packets
•
Requests for MIB objects under the control of subagents are passed to subagents for
processing. Some subagents perform authentication based on the community name,
IP address, and a password appended to the community name:
agent-community-string::subagent-password
•
All MIB objects under the control of the NonStop agent are accessible. Requests for
operations on objects in the zagInProfile group of the NonStop agent’s private MIB
are performed only if the Processor/Accessor ID (PAID) of the manager process is
compatible with that of the agent process. If the agent process is associated with the
super user group (user ID 255,n), the manager process must also be associated with
the super user group. If the agent process is not associated with the super user
group, the PAID of the manager process is irrelevant.
Using Trap Packets
You use a network protocol when sending and receiving traps. Figure 1-7 summarizes
how managers created using Manager Services can send and receive traps.
Managers can send BER-encoded traps to other managers using a network protocol that
the receiving managers support. Traps sent by a manager are not routed by an agent;
they go directly to another manager, which can reside on a NonStop Kernel system or on
network devices manufactured by other vendors, usually workstations referred to as
manager stations. Managers can also receive traps sent by subagents or agents.
Figure 1-8
shows how a manager can interoperate with one of the SNMP products
Tandem offers, the Trap Multiplexer. Traps emitted by a manager can be sent using a
Figure 1-7. Trap Communication Options
107
Manager
NonStop Systems Using the NonStop Kernel
IPC Protocol
Network Protocol
Legend
Local or Wide Area Network
Manager Stations
NonStop
Agent
Subagents
Manager