NTX_SNMP(1) — USER COMMANDS

NAME

ntx_snmp − set and display the state of the MVME339 SNMP agent

SYNOPSIS

ntx_snmp [ −d device ] [ on | off ]

AGENT INTRODUCTION

This section briefly describes the Motorola MVME339 SNMP implementation and the associated host utilities provided by Motorola. The SNMP implementation consists of an SNMP agent which executes on MVME339 intelligent communications adapters. It is important to note that the purpose of the SNMP agent is to manage the MVME339 and its associated software, not to manage the host computer. Once configured properly, the SNMP agent responds to PDUs (Protocol Data Units) received from the network. The host utilities provide a means for a Network Administrator to configure the SNMP agent with site-specific information. For detailed information on the individual host utilities, please refer to the references given below.

The SNMP agent is compliant with MIB-II (RFC 1213) and the SNMP protocol (RFC 1157).

The host must explicitly start the on-board agent with ntx_snmp on (SNMP ON). Before the host issues ntx_snmp on, the SNMP agent does not respond to any SNMP PDUs. The purpose of this is to allow the host to configure Community Profiles, and to configure which NMS(s) (Network Management Stations) have access to the agent. A community profile is a set of permissions for access to the agent’s MIB. Thus, to provide a better level of security, the host must configure this information before it issues ntx_snmp on. The ntx_nms and ntx_comun commands configure the NMSs and community profiles, respectively. However, if the Network Administrator does not require this security, the agent will use a default, “read-only” community profile. The host may issue ntx_snmp on, without issuing the other commands, to use the default community profile.

Before ntx_comun is issued, the default community profile is read-only access to the entire MIB for the community public.

The host may stop the SNMP agent by issuing ntx_snmp off (SNMP OFF). This may be useful if a configuration error has occured, an NMS is malfunctioning, or a security breach has been detected. After the Network Administrator has remedied the problem, the host may restart the SNMP agent by issuing ntx_snmp on.

Along with starting and stopping the SNMP agent and configuring community profiles, etc., the host may configure some site-specific information which the agent will hold in its MIB. The ntx_descr command performs this task.

SNMP TRAP PDUs are generated by the SNMP agent only if the host enables them. The host selectively enables the various traps and also configures which NMSs receive them with the ntx_traps command.

DESCRIPTION

Ntx_snmp turns on or off the MVME339 SNMP agent. The agent will not function until ntx_snmp on is issued. Also, ntx_snmp on may be used to resume operation of the agent after having issued ntx_snmp off.

It is useful to perform authentication-oriented MVME339 SNMP agent configuration (ntx_nms, ntx_comun) before issuing ntx_snmp on for the first time. Also, if the cold start trap (see ntx_traps) is enabled, the agent will send the trap PDU when the first ntx_snmp on is issued.

OPTIONS

−dSet the MVME339 raw device file name. This option will override the default MVME339 device name of /dev/xedt/mvme338_c0.

RETURN VALUES

If neither on or off is specified, ntx_snmp returns 0 if the agent is “on”, 1 if the agent is “off” or 2 if a failure occurs. If on or off is specified, it returns 0 for success and 2 for failure.

EXAMPLES

Turn on the MVME339 SNMP agent.

# ntx_snmp on
#
Get the current state of the agent.

# ntx_snmp
SNMP is on

FILES

/dev/xedt/mvme338_c0

Museum