TCPIP$UCP_HELP.HLB  —  SET  CONFIGURATION  SNMP
    Configures SNMP on an individual host.

    SET CONFIGURATION NOSNMP does not require any qualifiers.

    After making changes to the SNMP configuration, shut down and
    restart the master agent and any subagents. Issue the following
    commands:

    $ @SYS$STARTUP:TCPIP$SNMP_SHUTDOWN

    $ @SYS$STARTUP:TCPIP$SNMP_STARTUP

    Related command: SHOW CONFIGURATION SNMP

    Format

      SET CONFIGURATION [NO]SNMP  [ /[NO]ADDRESS=host ]

                                  [ /[NO]COMMUNITY="name" ]

                                  [ /[NO]CONFIRM ]

                                  [ /CONTACT=name ]

                                  [ /FLAGS=options]

                                  [ /LOCATION=options ]

                                  [ /TYPE=options ]

1  –  Restrictions

    Requires SYSPRV or BYPASS privilege.

    If you add a new community and do not specify the /TYPE
    qualifier, the value of /TYPE defaults to read only.

    If you add a new community and do not specify the /ADDRESS
    qualifier, the default address is 0.0.0.0.

2  –  Qualifiers

2.1    /ADDRESS

       /ADDRESS=(IP_address)
       /NOADDRESS=(IP_address)

    Optional. Default: 0.0.0.0

    Specifies hosts that belong to a particular community. You can
    specify multiple addresses.

    This qualifier is meaningful only if you include the /COMMUNITY
    qualifier. A remote host cannot access information from this
    host unless its address appears in one or more communities
    of type READ or WRITE. For communities of type TRAP, the
    addresses specify the hosts that receive trap messages. For more
    information, see the /TYPE qualifier.

    If you add a new community and do not specify this qualifier, the
    new entry's address is 0.0.0.0.

    If you use the /ADDRESS qualifier with a community that already
    exists, these addresses are added to the existing address list.

    /NOADDRESS deletes addresses from an existing list. If the
    deleted address is the only address listed for the community
    name, this qualifier also deletes the community.

2.2    /COMMUNITY

       /COMMUNITY="name"
       /NOCOMMUNITY="name"

    Optional. Default: To enable the standard "public" community, you
    can run the TCPIP$CONFIG procedure.

    Used with the /ADDRESS qualifier. Name of the community that the
    SNMP agent recognizes. Optionally, specify a type of access and
    a list of host addresses. Enclose the name in quotation marks
    to preserve lowercase characters. See the /TYPE and /ADDRESS
    qualifiers for more information.

    [NO]COMMUNITY="name" removes a community name.

2.3    /CONFIRM

       /CONFIRM
       /NOCONFIRM

    Optional. Default: /CONFIRM with if you use a wildcard;
    otherwise, /NOCONFIRM

    When you delete communities (with the /NOCOMMUNITY qualifier),
    first asks for your confirmation.

    If you specify the /NOCONFIRM qualifier, the operation is
    performed without asking you to confirm the request.

2.4    /CONTACT

       /CONTACT=name

    Optional. Default: None.

    Name of the system administrator (or other contact person) of the
    host on which the SNMP agent runs. The name field has a maximum
    length of 235.

2.5    /FLAGS

       /FLAGS=options

    Optional.

    The options include:

    o  SETS

       Lets the master agent process SET commands from SNMP clients.

    o  AUTHEN_TRAPS

       Lets the master agent send trap messages in response to
       unauthorized community strings from SNMP clients.

2.6    /LOCATION

       /LOCATION=options

    Optional. Default: None.

    Location of the system on which the SNMP agent runs. Maximum
    total length is 215 characters.

    The options include:

    o  [NO]FIRST=text

       Specifies the first part of the location. Maximum length of
       text is 200 characters.

    o  [NO]SECOND=text

       Specifies the last part of the location. Maximum length of
       text is 200 characters.

    If you specify two options, they are appended when sent to a
    client in response to an SNMP request for syslocation. For
    example, if FIRST is abc and SECOND is def, the value of the
    location is abcdef with no spaces. The total number of characters
    must not exceed 215.

2.7    /TYPE

       /TYPE= {[NO]READ | [NO]TRAP | [NO]WRITE}

    Optional. Default: READ.

    Sets the type of access (to your local MIB data) to allow for a
    specified community.

    o  Type READ allows the master agent to accept GET, GETNEXT, and
       GETBULK commands from clients (management stations).

    o  Type TRAP allows the local master agent to issue traps
       to members of a specified community. Members of a trap
       community receive SNMP Trap-PDUs for significant events,
       including coldStart traps when the agent is initialized, and
       authenticationFailure traps when the agent receives an SNMP
       request that specifies an unauthorized community string.

    o  Type WRITE allows the master agent to accept SET commands from
       clients (management stations).

    READ access is present by default when specifying TRAP or WRITE.
    Also, you can remove the read access without affecting the way
    the agent responds to a read request. For example:

    $ SET CONFIGURATION SNMP /COMMUNITY="name" /TYPE=NOREAD

3  –  Examples

    1.TCPIP> SET CONFIGURATION SNMP /COMMUNITY="public" -
      _TCPIP> /CONTACT="Sam Spade" -
      _TCPIP> /LOCATION=(FIRST="Falcon Building",SECOND="Los Angeles,
      California")

      Configures SNMP with the standard public community, taking the
      default type (READ) and address (0.0.0.0) for that community.
      Both contact and location are specified.

      The first and second parts of the location text are
      concatenated when displayed by an SNMP client. For example:

        Falcon BuildingLos Angeles, California

      If no update to the location text is done by an SNMP client,
      the display produced by SHOW CONFIGURATION SNMP is as follows:

        Location
        First:  Falcon Building
        Second: Los Angeles, California

      If the text is updated by an SNMP client (for example, to
      change "Falcon" to "Falconi"), the original formatting is not
      preserved and the display produced by SHOW CONFIGURATION SNMP
      is as follows:

        Location
        First:  Falconi BuildingLos Angeles, California

    2.TCPIP> SET CONFIGURATION SNMP /COMMUNITY="rw" /TYPE=WRITE -
      _TCPIP> /ADDRESS=136.20.100.10 /FLAGS=SETS

      Configures a community with only read/write access to the host
      with the address specified. Other hosts still have read access
      through the public community. Also sets the SETS flag to enable
      the SNMP agents to process write requests from SNMP clients on
      host 136.20.100.10.

    3.TCPIP> SET CONFIGURATION SNMP /NOCOMMUNITY="rw"

      Removes the rw (read/write) community (set in example 2.)

    4.TCPIP> SET CONFIGURATION SNMP /COMMUNITY="trapit" /TYPE=TRAP -
      _TCPIP> /ADDRESS=136.20.0.10

      Configures SNMP so that agents can send trap messages to the
      well-known UDP port 162 on the host identified with the address
      136.20.0.10.

    5.TCPIP> SET CONFIGURATION SNMP /FLAGS=AUTHEN_TRAPS -
      _TCPIP> /COMMUNITY="trapit2" /TYPE=TRAP -
      _TCPIP> /ADDRESS=(136.20.0.12,136.20.0.15)

      Configures SNMP with the AUTHEN_TRAPS flag so that the
      master agent sends trap messages when it detects a client
      request containing an invalid community name. Also configures
      an additional trap community. Trap messages, including
      authentication traps, go to all three addresses specified in
      the trap communities configured in this example and in example
      4.

    6.TCPIP> SET CONFIGURATION SNMP  /COMMUNITY="rw2" /TYPE=WRITE -
      _TCPIP> /ADDRESS=(136.20.0.15,136.20.0.100)

      Configures community rw2, which gives read/write access to
      two hosts. Note that one address can appear for more than one
      community, although a given address cannot be specified more
      than once for a single community.
Close Help