Patch-ID# 105589-02 Keywords: SNMP na.ping libnetmgt trap pdu v2mib2schema schema mib core filters Synopsis: Solstice Site/SunNet/Domain Manager 2.3 Rev B: SNMPv2, ping, v2mib2schema Date: Jul/24/98 Solaris Release: 1.1.x SunOS Release: 4.1.x Unbundled Product: Solstice Domain/Site/SunNet Manager Unbundled Release: 2.3p3 Relevant Architectures: sparc BugId's fixed with this patch: 4108616 4056549 4104045 4076886 4093971 4150594 4150596 4150604 4150597 Changes incorporated in this version: 4056549 4104045 4076886 4093971 4150594 4150596 4150604 4150597 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: 104020-03 Obsoleted by: Files included with this patch: $SNMHOME/lib/libnetmgt.so.3.0 $SNMHOME/agents/na.ping $SNMHOME/agents/na.snmp-trap $SNMHOME/5.x/agents/na.ping $SNMHOME/5.x/agents/na.snmp-trap $SNMHOME/5.x/lib/libnetmgt.so.3 $SNMHOME/x86/agents/na.ping $SNMHOME/x86/agents/na.snmp-trap $SNMHOME/x86/lib/libnetmgt.so.3 $SNMHOME/bin/snm_cmd $SNMHOME/bin/v2mib2schema $SNMHOME/man/man1/v2mib2schema.1 Problem Description: 4150594 Netmgt library functions need to support SNMP calls with long argument lists to generate larger PDU lengths. 4150596 Na.snm-trap needs to support SNMPv2C style traps. 4150604 Add -Q flag to snm_cmd to stop na.ping poll after event occurs. 4150597 Added support for additional SNMPv2 constructs to v2mib2schema. 4056549 When na.snmp-trap is used with host filters in the snmp.traps file, it will core dump under heavy load. 4104045 The problem is that we are receiving rsrb traps from our Cisco routers which have an enterprise number of 1.3.6.1.4.1.9.9.29. Our snmp.traps file contains an entry for this enterprise that is located prior to the cisco-general enterprise 1.3.6.1.4.1.9 in the file. 4076886 SNMPv2 mibs cause the v2mib2schema converter to fail. It creates partial schema files (without most of the definitions), or produces errors and no schema file at all. 4093971 Description information for specific attributes is not transferred to the resulting schema file. The same description is used for each attribute and table in the entire schema file. (from 105589-01) 4108616 After sending a event request to a proxy system which is not reachable (over a routing system) at this time you get the error message "RPC timed out: no response from portmapper on -retrying" From this point the request state in event summary is "awaiting activation" and all following quick dumps (i.e. snmp-mibII.ifStatus.4) on devices or systems which are reachable shows: Error: Request snmp-mibII.ifStatus.4: API error: Remote procedure call failed: Cannot send request: RPC: Can't encode arguments Patch Installation Instructions: -------------------------------- Refer to the Install.info file for instructions on using the generic 'installpatch' and 'backoutpatch' scripts provided with each patch. Any other special or non-generic installation instructions should be described below as special instructions. Special Install Instructions: ----------------------------- The patch 104020-03 (SNM 23 Patch 3) must be applied as a prerequisite to this patch.