Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ ntx_comun(1) — Motorola System V 88k Release 4 Version 4.3

Media Vault

Software Library

Restoration Projects

Artifacts Sought

NTX_COMUN(1)  —  USER COMMANDS

NAME

ntx_comun − configure the MVME339 SNMP community profile

SYNOPSIS

ntx_comun [ −d device ] [ −f file ]
ntx_comun [ −d device ] [ [ −o objectID ] community na | ro | rw ]

DESCRIPTION

Ntx_comun configures the MVME339 SNMP community profile which consists of community names and their respective permissions for access to MIB objects. 

When the agent receives an SNMP PDU, it verifies that the community specified within the PDU has appropriate access to all of the MIB variables specified in the PDU. 

It is useful for the host to issue ntx_comun commands before issuing ntx_snmp in order to configure the community profiles before the SNMP agent begins receiving PDUs.  However, if the Network Administrator wishes to not configure community profiles (the host does not issue ntx_comun), the SNMP agent uses a default read-only community profile with the community name public. 

The host must issue ntx_comun multiple times for the same community in order to configure permissions for multiple MIB subtrees for the community. 

community is the community name.  It is normally an ASCII string which serves to identify a set of NMSs which have access to the MVME339 SNMP agent. 

Specify the access mode for the MIB variable: na (not accessible), ro (read only) or rw (read-write). 

If none of the community profile parameters are given on the command line, ntx_comun retrieves the configuration from the MVME339 and displays it on the standard output.  The output is the same format as file (given below). 

OPTIONS

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

−fRead the community profile configuration from a file and send it to the MVME339.  If file is − read from the standard input.  The input file is a list of triples, one per line.  The first item in a triple is an object identifier in dot notation form or the key word all.  The second item is the community name and the third item is the access mode, one of na, ro or rw.  The items are separated by white space.  Characters to the right of ’#’ on input lines are ignored. 

−oobjectID identifies MIB variable(s).  It may identify a leaf object, or it may identify an MIB sub-tree.  If objectID identifies a sub-tree, access refers to all elements of that tree. objectID is a “dot” notation string whose elements contain decimal strings identifying MIB nodes.  If objectID is not specified, then access permission refers to the whole MIB.  Please refer to the relavant MIB documents in order to determine the objectID for the object or sub-tree. 

EXAMPLES

Community name “public” with access denied only to ~.system.sysuptime.0:

 ntx_comun −o 1.3.6.1.2.1.1.3.0 public na
 Community with read-only access to the system group:
 ntx_comun −o 1.3.6.1.2.1.1 rosys ro
 Community with read-write access to the whole MIB:

 ntx_comun writer rw
 Community with no access at all:

 ntx_comun criminal na
 

FILES

/dev/xedt/mvme338_c0

SEE ALSO

mvme338 (7), ntx_snmp (1)
RFC 1213, Management Information Base for network management of TCP/IP-based internets:MIB-II

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026