HP OpenVMS Systems Documentation

After upgrading to the current version of TCP/IP Services, you must disable and then enable SNMP using the TCPIP$CONFIG configuration command procedure. When prompted for "this node" or "all nodes," select the option that reflects the previous configuration.

3.16.5 Communication Controller Data Not Fully Updated

When you upgrade TCP/IP Services and then modify an existing communication controller, programs that use the communication controller might not have access to the updated information.

To ensure that programs like the MIB browser (SNMP_REQUEST) have access to the new data about the communication controller, do the following:

1. Delete the communication controller using the TCP/IP management command DELETE COMMUNICATION_CONTROLLER.
2. Reset the communication controller by running the TCPIP$CONFIG.COM command procedure and exiting.
3. Restart the program (such as SNMP) by entering the following commands:

   $ @SYS$STARTUP:SNMP_SHUTDOWN.COM $ @SYS$STARTUP:SNMP_STARTUP.COM

4. Use the TCP/IP management command LIST COMMUNICATION_CONTROLLER to display the information.

If you use either the -l (loop mode) or -t (tree mode) flag, you cannot also specify the -m (maximum repetitions) flag or the -n (nonrepeaters) flag. The latter flags are incompatible with loop mode and tree mode.

Incorrect use of the -n and -m flags results in the following messages:

$ snmp_request mynode.co.com public getbulk -v2c -n 20 -m 10 -t 1.3.6.1.2.1
Warning: -n reset to 0 since -l or -t flag is specified.
Warning: -m reset to 1 since -l or -t flag is specified.
1.3.6.1.2.1.1.1.0 = mynode.company.com

With this version of TCP/IP Services, two subagents can have the same identifier parameter. Be aware, however, that having two subagents with the same name makes it difficult to determine the cause of problems reported in the log file.

3.16.8 eSNMP Programming and Subagent Development

The following notes pertain to eSNMP programming and subagent development.

• In the documentation, the terms extension subagent, custom subagent, and user-written subagent refer to any subagent other than the standard subagents for MIB-II and the Host Resources MIB, which are provided as part of the TCP/IP Services product.
• In the [.SNMP] subdirectory of TCPIP$EXAMPLES, files with the .C, .H, .COM, .MY, and .AWK extensions contain additional comments and documentation.
• The TCPIP$SNMP_REQUEST.EXE, TCPIP$SNMP_TRAPSND.EXE, and TCPIP$SNMP_TRAPSND.EXE programs are useful for testing during extension subagent development.
• For information about prototypes and definitions for the routines in the eSNMP API, see the TCPIP$SNMP:ESNMP.H file.

This chapter describes some of the user-visible problems corrected in this version of TCP/IP Services.

4.1 Management Command Interface Problems Fixed in This Release

The following TCP/IP Services TCP/IP management command problems are fixed in this release:

• Problems:
  • The SET CONFIGURATION ENABLE SERVICE command fails when processing node-specific or cluster-wide configuration records containing large numbers of service entries.
  • The SET CONFIGURATION ENABLE SERVICE command fails to output any error message when trying to add a service to a configuration record that already contains the maximum number of service entries.
  • The TCPIP$CONFIG.COM configuration procedure generates errors processing service lists that exceed the 1024-byte limit of DCL symbols.
  • The number (63) of service entries that can be stored in node-specific or cluster-wide configuration records is too low.
  
  Solutions:
  • In TCPIP$CONFIG.COM, routines correctly handle long enable service lists that exceed the 1024-byte limit of DCL symbols.
  • In TCPIP$UCX.EXE, the routine that signals "TOOMANYSERV" errors has been corrected.
    The maximum number of service entries has been changed from 64 to 128 when updating a configuration record that specifies a limit that is less than the current maximum.
  • In TCPIP$ACCESS_SHR.EXE, raised the maximum number of service entries supported in configuration records from 64 to 128.
  • In TCPIP$ACCESS_SHR.EXE, the largest record field in the record descriptor table uses the largest record size in the INET facility.
    This change corrects the system failure experienced when creating large service lists.
  • In TCPIP$MESSAGE.MSG, the TOOMANYSERV message has been added.
• Problem: The TCP/IP management command MOUNT generates an access violation when trying to perform a wildcarded mount operation.
  Solution: MOUNT command handling and processing has been corrected.

The following BIND/DNS problems are fixed in this release:

• Problem: A user has no way to manually flush dynamic updates with BIND Version 9.
  Solution: The rndc flush-updates command has been added to trigger the same behavior that the rndc stop command did, without actually stopping or shutting down the server.

The following FTP problems are fixed in this release:

• Problem: Seven FTP client/server problems.
  Solution: If the device for a user in the UAF is a rooted logical, that logical must be assigned systemwide with the translation attribute at least concealed, or else the cd command will fail. For example:
  • moxie$root is assigned /SYSTEM only:

    FTP> cd ~moxie 550-Failed to set default directory to MOXIE$ROOT:[user]. 550 error in directory name

  • moxie$root is assigned /SYSTEM/TRANSLATION=CONCEALED:

    FTP> cd ~moxie 250-CWD command successful. 250 New default directory is MOXIE$ROOT:[user]

  
  For systems with a version of DECC$SHR.EXE at or later than V7.2, assigning the following logical name enables recursive directory listings for the ls and dir commands:

  $ ASSIGN/SYSTEM 1 TCPIP$FTPD_DIR_RECURSIVE

  
  Turning on this flag results in the following UNIX-like behavior. Here the default directory is DEV1$:[TOPDIR] and it contains a subdirectory SUB1.DIR which contains three files:

  FTP> ls sub1 200 PORT command successful. 150 Opening data connection for sub1 (16.20.208.97,52062) DEV1$:[TOPDIR.SUB1]a.txt;1 DEV1$:[TOPDIR.SUB1]b.txt;1 DEV1$:[TOPDIR.SUB1]c.txt;1

  
  To get to the login directory of a user using ~username format, you need system privileges if username is other than that of the current user.
• Problem: There is no way to suppress the file size in the 150 opening data connection message. The new behavior affects file transfers using an older version of SmartTerm.
  Solution: A new logical, TCPIP$FTPD_NO_FILESIZE_HINT, allows users to suppress the file-size hint added to the "150 Opening data connection..." message.
• Problem: The FTP client starts up in Extended parse mode. The SHOW PROCESS/PARSE command shows that the parse style is set to Extended.
  Solution: This behavior has been correct so that traditional parsing is used by default. To change the parsing style, enter the SET PROCESS/PARSE command.

The following NFS server problems were fixed in this release:

• Problems:
  • When file names of the form string.string.nnn are created on an ODS5 volume, nnn is treated as a file version number. Viewed locally, the file appears as xxx.yyy;123 instead xxx.yyy.123;1. If the numeric part is greater than 32767, the file creation failed.
  • When creating a directory name of the form string.dir on an ODS5 volume with the typeless_directories option, the server absorbs the ".dir" part of the name. Viewed locally, the directory appears as "dirname.DIR;1" instead of "dirname.dir.DIR;1," and is displayed back to the client as "dirname" instead of "dirname.dir".
• Problem: The NFS client recieves errors -RMS-F-CRMP and -SYSTEM-F-SHMNOTCNCT after doing a SET FILE /STATISTICS command followed by an attempt to open the file using the COPY or TYPE command.
• If a UNIX client accesses a non-STREAM_LF file that was created by an OpenVMS client within the inactivity timer limit, the server does not do data conversion.

• Problem: The TELNET symbiont puts log files into SYS$SPECIFIC:[SYSEXE] even when the TCPIP$LPD_ROOT logical name is defined.
  Solution: The TCPIP$LPD_SPOOL logical name has been replaced by the TCPIP$LPD_ROOT logical name.
• Problem: Starting with TCP/IP Services V5.1, local echoing no longer occurs when you use TELNET to connect to a non-TELNET service (such as SMTP).
  Solution: The behavior used in earlier versions of TCP/IP Services has been restored.

The following SMTP problems are fixed in this release:

• Problem: The SMTP EXPN and VRFY commands are considered a security hole by many customers.
  Solution: Four new SMTP.CONFIG Allow-* options govern whether the commands are accepted or not. The *-Text options are the optional user-defined text strings to send to the client when the command is rejected. The new configuration options are:
  • Allow-EXPN
  • Allow-VRFY
  • EXPN-Used-Text
  • VRFY-Used-Text
  
  For more information see the HP TCP/IP Services for OpenVMS Management guide.
• Problem: Mail messages with lines beginning with a period (.) are delivered with an extra dot included.
  Solution: The period-removal code is restored. It applies only to mail message data received using the RFC 821 protocol over the wire and not from SFF (send-from-file).

The following SNMP problems are fixed in this release:

• Problems:
  • An attempt to send an SNMPv2 trap through TCPIP$SNMP_TRAPSND is either ignored or causes the system to fail.
  • SNMP_REQUEST -i , -r , and s options are ignored.

This chapter describes updates to the information in the TCP/IP Services for OpenVMS product documentation.

5.1 Updated Documentation

The following manuals have been updated for this version of TCP/IP Services:

• HP TCP/IP Services for OpenVMS Installation and Configuration (AA-LU49O-TE)
• HP TCP/IP Services for OpenVMS Management (AA-LU50N-TE)
• HP TCP/IP Services for OpenVMS Guide to SSH (AA-RVBUA-TE)
• HP TCP/IP Services for OpenVMS User's Guide (AA-PC27L-TE)
• HP TCP/IP Services for OpenVMS Tuning and Troubleshooting (AA-RN1VB-TE)
• HP TCP/IP Services for OpenVMS Management Command Quick Reference Card (AV-RN1WB-TE)
• HP TCP/IP Services for OpenVMS Management Command Reference (AA-PQQGI-TE)
• HP TCP/IP Services for OpenVMS UNIX Command Equivalents Reference Card (AV-RNJ4B-TE)
• HP TCP/IP Services for OpenVMS Guide to IPv6 (AV-RNJ3B-TE)

In addition, this version of TCP/IP Services includes new version of the Help files:

• HELP TCPIP_SERVICES
• TCPIP HELP
• HELP FTP
• HELP TELNET
• HELP NSLOOKUP
• HELP/MESSAGES

The following manuals are not updated for TCP/IP Services V5.4:

• Compaq TCP/IP Services for OpenVMS Sockets API and System Services Programming
• Compaq TCP/IP Services for OpenVMS SNMP Programming and Reference
• Compaq TCP/IP Services for OpenVMS ONC RPC Programming and Reference
• Compaq TCP/IP Services for OpenVMS Concepts and Planning

These manuals will be updated in a future release of TCP/IP Services. For this release, use the existing manual with the changes described in the following sections.

5.1.1 SNMP Programming and Reference Update

The following information will be added to the Compaq TCP/IP Services for OpenVMS SNMP Programming and Reference manual:

• The trap communities configured for regular SNMP through the TCPIP$CONFIG.COM command procedure, the TCP/IP management command SET CONFIG SNMP, or in the SYS$SYSDEVICE:[TCPIP$SNMP]TCPIP$VMS_SNMP_CONF.DAT file are not used to determine the trap receiver host or community name.
  The values of the -c and -h flags to the SNMP_TRAPSND utility are handled as follows:
  • If no -c (community) flag is used, the default name "public" is used in the trap.
  • If no -h (host) flag is used, the trap is sent to LOCALHOST.
• The value for the "agent address" field in the SNMPv1 trap PDU is that of the primary interface for the host on which the master agent (TCPIP$ESNMP_SERVER) is running. The value of this address can be verified as follows:
  1. Translate logical name TCPIP$INET_HOSTADDR
  2. Obtain the value of LOCALHOST using the following TCP/IP management command:

     $ TCPIP SHOW CONFIGURATION COMMUNICATION

     
     If this value is not in IP address format, determine the IP address using the following command:

     $ TCPIP SHOW HOST/LOCAL local-host-name

The information in the Compaq TCP/IP Services for OpenVMS Sockets API and System Services Programming manual will be updated as follows:

• Table 2-2 describes the default setting for the TCPIP_KEEPIDLE option incorrectly. The default setting for this option is 7200 seconds (14400 half seconds). In addition, the manual fails to mention that, in order to use the options in Table 2-2, your program must use the TCP.H file.

The HELP CC Socket_Routines information has been removed. Instead, the information about socket programming is provided when you enter the following command:

$ HELP TCPIP_SERVICES Programming_Interfaces Sockets_API

The Sockets_API HELP file has been enhanced with IPv6 information.