HP OpenVMS Systems Documentation

Compaq TCP/IP Services for OpenVMS
Release Notes

If an existing subagent does not execute properly, you may need to relink it against the current version of TCP/IP Services to produce a working image. Some subagents (such as those for OpenVMS support of Compaq Insight Manager) also require a minimum version of OpenVMS and a minimum version of TCP/IP Services.

The following general restrictions and cautions apply:

• In general, only executable images linked against the following versions of the eSNMP shareable image are upward compatible with the current version of TCP/IP Services:
  • UCX$ESNMP_SHR.EXE from TCP/IP Services Version 4.2 ECO 4
  • TCPIP$ESNMP_SHR.EXE from TCP/IP Services Version 5.0A ECO 1
  
  Images built under versions other than these can be relinked with one of the shareable images, or with TCPIP$ESNMP_SHR.EXE in the current version of TCP/IP Services.
• The underlying eSNMP API changed from DPI in Version 5.0 to AgentX in the current version of TCP/IP Services. Therefore, executable images linked against older object library versions of the API (*$ESNMP.OLB) must be relinked against either the new object library or the new shareable image. Linking against the shareable image ensures future upward compatibility and results in smaller image sizes.

  Note Although images can run without being relinked, backward compatibility is not guaranteed. These images can result in inaccurate data or run-time problems.

• Programs that rely on TCP/IP Services Version 4.2 kernel data structures or functions may run but may not return valid data. Such programs should be rewritten.
• Executable images linked against UCX$ACCESS_SHR.EXE, UCX$IPC_SHR.EXE, UCX$RPCXDR_SHR.EXE, or other older shareable images, may not run even when relinked. You may need to recompile, or rewrite and recompile, such programs.
  If you have executable images linked against versions other than those listed above and cannot relink, contact your Compaq support representative for assistance.
• If you have problems running executable images linked against TCP/IP Services Version 4.2 ECO 4 or TCP/IP Services Version 5.0A ECO 1, verify that the version of the shareable image is the latest by entering the following DCL command:

  $ DIRECTORY/DATE/PROTECTION SYS$SHARE:*$ESNMP_SHR.EXE

  
  The creation dates of the files with the prefix TCPIP$ and UCX$ should be within a few seconds of each other, and only one version of each file should exist. Make sure both images include the file protection W:RE.
  Also, you can use the following command to check the version:

  $ TCPIP SHOW VERSION/ALL

  
  The second column in the line for image TCPIP$ESNMP_SHR under the category "Network Management" displays the version. For example:

  TCPIP$ESNMP_SHR;1 V5.1-15B 23-MAY-2001 SYS$COMMON:[SYSLIB]

• Both TCP/IP Services Version 5.0A ECO 1 and TCP/IP Services Version 5.1 provide an updated version of the UCX$ESNMP_SHR.EXE shareable image to provide compatibility with subagents linked under TCP/IP Services Version 4.2 ECO 4. Do not delete this file.

• SNMP requests are not implemented for the following MIB-II group objects:

  ipRouteMetric1 - ipRouteMetric5 tcpMaxConn

• SNMP requests are not implemented for the following Host Resources MIB objects:

  hrPartitionTable hrPrinterTable hrSWInstalled hrSWInstalledTable

• SNMP set requests are not implemented for the following MIB-II group objects:

  ipDefaultTTL ipRouteAge ipRouteDest ipRouteIfIndex ipRouteMask ipRouteNextHop ipRouteType

• SNMP set requests are not implemented for the following Host Resources MIB objects:

  hrFSLastFullBackupDate hrFSLastPartialBackupDate hrStorageSize hrSWRunStatus hrSystemDate hrSystemInitialLoadDevice hrSystemInitialLoadParameters

• In the SNMP group (1.3.6.1.2.1.11), data elements noted as obsolete in RFC 1907 are not implemented.

This section describes restrictions and characteristics of SNMP. For more information, refer to the Compaq TCP/IP Services for OpenVMS SNMP Programming and Reference guide.

• The SNMP server responds correctly to SNMP requests directed to a cluster alias. Note, however, that an unexpected host might be reached when querying from a TCP/IP Services Version 4.x system that is a member of a cluster group but is not the current impersonator.
• The SNMP master agent and subagents do not start if the value of logical name TCPIP$INET_HOST does not yield the IP address of a functional interface on the host when used in a DNS query. This problem does not occur if the server host is configured correctly with a permanent network connection (for example, Ethernet or FDDI). The problem can occur when a host is connected through PPP and the IP address used for the PPP connection does not match the IP address of the TCPIP$INET_HOST logical name.
• Under certain conditions observed primarily on OpenVMS VAX systems, the master agent or subagent exits with an error from an internal select() socket call. In most circumstances, looping does not occur. You can control the number of iterations if looping occurs by defining the TCPIP$SNMP_SELECT_ERROR_LIMIT logical name.
• The MIB browser provided with TCP/IP Services (TCPIP$SNMP_REQUEST.EXE) supports getnext processing of OIDs that include the 32-bit OpenVMS process ID as a component. However, other MIB browsers might not provide this support.
  For example, the following OIDs and values are supported on OpenVMS:

  1.3.6.1.2.1.25.4.2.1.1.1321206828 = 1321206828 1.3.6.1.2.1.25.4.2.1.1.1321206829 = 1321206829 1.3.6.1.2.1.25.4.2.1.1.1321206830 = 1321206830

  
  These examples are from hrSWRunTable ; the hrSWRunPerfTable might be affected as well.
• sysObjectID is returned in the following format, as required for interoperability with Compaq Insight Manager/XE:

  1.3.6.1.2.1.1.2.0 = 1.3.6.1.4.1.36.2.15.22.1

  
  In this format, the right-hand value corresponds to:

  iso.org.dod.internet.private.enterprises.dec.ema.sysObjectIds.DEC-OpenVMS.eSNMP

• The sysORTable is implemented (see RFC 1907 for details). Elements are under OID prefix 1.3.6.1.2.1.1.9.1.
  When both the TCPIP$OS_MIBS and TCPIP$HR_MIB subagents are running, a get request on the sysORTable is as follows. Except where noted, the OIDs conform to RFC 1907:

  1.3.6.1.2.1.1.9.1.2.1 = 1.3.6.1.4.1.36.15.3.3.1.1 1.3.6.1.2.1.1.9.1.2.2 = 1.3.6.1.4.1.36.15.3.3.1.2 1.3.6.1.2.1.1.9.1.3.1 = Base o/s agent (OS_MIBS) capabilities 1.3.6.1.2.1.1.9.1.3.2 = Base o/s agent (HR_MIB) capabilities 1.3.6.1.2.1.1.9.1.4.1 = 31 = 0 d 0:0:0 1.3.6.1.2.1.1.9.1.4.2 = 36 = 0 d 0:0:0

  
  This example is from the MIB browser (TCPIP$SNMP_REQUEST.EXE).
• The hrDeviceTable now includes template devices (for example, DNFS0 for NFS and DAD0 for virtual devices).
• For network devices, only the template devices (those with unit number 0) are displayed.
• The hrDeviceTable includes all devices known to the OpenVMS host except those with the following characteristics.
  • Off-line
  • Remote
  • UCB marked delete-on-zero-reference-count
  • Mailbox device
  • Device with remote terminal (DEV$M_RTT characteristic)
  • Template terminal-class device
  • LAT device (begins with _LT)
  • Virtual terminal device ( >

    Chapter 4
    Corrections

    This chapter describes the problems corrected in this version of TCP/IP Services. It contains the following sections:

    • Section 4.1 describes software corrections in this release.
    • Section 4.2 describes customer-reported problems corrected in this release.

    4.1 Software Corrections

    The following sections describe the software corrections included in this release of TCP/IP Services, organized by component.

    4.1.1 Management Command Interface Problems Fixed in This Release

    • The ROUTE command no longer fails when the interface name is entered in lowercase letters. It is no longer necessary to put quotation marks around the interface name. The interface name is always accepted and is handled as uppercase.
    • If Ctrl/C was issued at the right moment during a SHOW HOST/NOLOCAL command, an ACCVIO error could occur.
      Also, some errno status returns were being passed back to the management command interface, which was unable to translate them.
    • The management command interface failed to consistently handle UNIX management utility commands, whether launched as a DCL command or TCP/IP management command. Sometimes it was necessary to quote lowercase characters. At other times, quotation marks were not necessary.
      When you enter DCL commands to manage TCP/IP Services, it is no longer necessary to include quotation marks around UNIX utility commands (for example, TCPIP "ifconfig -a" ). You need to enclose only uppercase options in quotation marks (for example, TCPIP ifconfig "-Q" inet ).
    • The following TCP/IP management commands have been enhanced to support BIND Version 9 (Alpha systems only):
      • The SET NAME /INITIALIZE command now reloads all BIND databases and the BIND configuration file. It requires that at least one of the following process privileges be set: BYPASS, READALL, or SYSPRV. In addition, it also requires that either TCPIP$ETC:RNDC.CONF or TCPIP$ETC:RNDC.KEY be set up to allow for secure communication between the user and the BIND server.
      • The SHOW NAME /STATISTICS command now writes statistics to the SYS$SPECIFIC:[TCPIP$BIND]TCPIP$BIND.STATS file. The command requires that at least one of the following process privileges be set: BYPASS, READALL, or SYSPRV. In addition, it also requires that either TCPIP$ETC:RNDC.CONF or TCPIP$ETC:RNDC.KEY be set up to allow for secure communication between the user and the BIND server.

    4.1.2 BIND Problems Fixed in This Release

    • The ndc commands start , stop , and restart were broken. This correction is relevant only to VAX systems. On Alpha systems, the ndc utility has been replaced by the rndc utility.
    • In some cases, with a search path defined, the nslookup utility and the TCP/IP management command SHOW HOST returned the "host-not-found" message before it exhaustsed the entire search path list.
    • TCPIP$BINDSETUP.COM did not restart BIND properly.

    4.1.3 BIND Resolver Problems Fixed in This Release

    If the BIND resolver was not enabled, applications that used IP addresses resulted in errors if the address was not defined in the local hosts database.

    4.1.4 IPC Problems Fixed in This Release

    The send() ) and recv() ) functions did not allow the use of 64-bit addresses.

    The send() ) and recv() ) functions now allow 64-bit addresses. Note that the sendto() ), sendmsg() ), recvfrom() ), and recvmsg() ) functions support only 32-bit addresses.

    This change affects Alpha systems only.

    4.1.5 SMTP Problems Fixed in This Release

    TCP/IP Services and OpenVMS version information was revealed by the SMTP software. This may be a security issue.

    The information was revealed in the following places:

    • The SMTP server's response to the initial connection from the SMTP client.
    • The Received header appended to the list of Received headers by the SMTP server.
    • The Received header inserted into the list of Received headers by the Send-From-File feature.

    To tells the SMTP software not to reveal TCP/IP Services or OpenVMS version information, set the TCPIP$SMTP_SUPPRESS_VERSION_INFO system logical name.

    To define the logical, enter the following command:

    $ DEFINE /SYSTEM TCPIP$SMTP_SUPPRESS_VERSION_INFO

    4.1.6 SNMP Problems Fixed in This Release

    The SNMP protocol has been updated with the following corrections:

    • This version of TCP/IP Services supports the AGENTX MIB. The OID root for this new MIB is:

      1.3.6.1.2.1.74

    • The Chess example is changed to use the standard OpenVMS sysObjectID , to match the one used for Compaq Insight Manager compatibility in the OS and HR MIBs. The numeric value is:

      1.3.6.1.4.1.36.2.15.22.1.

    • False duplicate error messages when the subagent image does not exit but when the subagent needs to restart (because of loss of contact with master agent) are eliminated.
    • Support is added for 32-bit subidentifiers in numeric OIDs.
    • Traps are now generated when the client makes a SET request to a server using a valid community name but when the client does not have write permission for the client host.
    • A configuration option for maximum SNMP message size has been added. The following logical names are available for restricting the size of SNMP packet size allowed by the master agent:
      • SNMP_MAX_GETSET_LEN, which specifies the size allowed from incoming GET, GETNEXT, GETBULK and SET requests.
      • SNMP_MAX_MSG_LEN, which specifies the size allowed from incoming GET, GETNEXT, GETBULK and SET requests, and also the size allowed for outgoing trap messages.
      
      To control these sizes, use the following DCL commands interactively or in a system startup file:

      $ ASSIGN /SYSTEM /EXEC size TCPIP$SNMP_MAX_GETSET_LEN $ ASSIGN /SYSTEM /EXEC size TCPIP$SNMP_MAX_MSG_LEN

      
      Compaq recommends that any changes to these sizes be made with extreme caution. The values specified for size should be between 484 and 1500.
    • On systems with a large number of ARP entries or TCP or UDP connections (on the order of 10,000), the MIB-II returns the following error message:

      Exceeded maximum kinfo call level (1000)

    ---

    Previous

    Next

    Contents