Patch-ID# 100770-08 Keywords: SNM JUMBO Synopsis: SunNet Manager 2.0: Jumbo Patch Date: Jul/05/94 Solaris Release: SunOS Release: 4.1.1 4.1.2 4.1.3 4.1.3C Unbundled Product: SunNet Manager Unbundled Release: 2.0 Topic: SunNet Manager 2.0 Jumbo patch, fixes variety of bugs. Patches which conflict with this patch: Architectures for which this patch is available: sparc BugId's fixed with this patch: 1094285 1094360 1094682 1095566 1096304 1096790 1096857 1096861 1100403 1101085 1101393 1101519 1101848 1103444 1103448 1103658 1103998 1104111 1104165 1104178 1104402 1104522 1088459 1091550 1092086 1093396 1098854 1100205 1103595 1108884 1109638 1110117 1110454 1110458 1110613 1110792 1111505 1112851 1113044 1113196 1113772 1114274 1114642 1115514 1115906 1117038 1119472 1119618 1120121 1120140 1121830 1123732 1125159 1118845 1120140 1107397 1125676 1132110 1135161 1135173 1136648 1140120 1140496 1145296 1143704 1146069 1143263 1146953 1132755 1143263 1156532 1155606 1151091 1156959 1157117 1162427 1149566 1152409 1152747 1153908 1156532 1156959 1165200 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Problem Description: Bug ID Problem Description ------ ------------------- 1094285 snmdb_open() exits if the database it tries to open has not been created yet 1094360 SNMP proxy fails if any host name in snmp.hosts is invalid 1094682 SNMP proxy cannot parse schemas with "map" definitions 1095566 SNMP proxy ignores changes in schema argument in event and data requests 1096304 SNMP proxy retries requests forever if the request ID in the response is wrong 1096790 multiple objects of type octet all assume value of last octet type 1096857 SNMP set operation results in incorrect data being sent in the set request 1096861 terminating SunNet Manager can leave request records in request.log 1100403 na.iostat daemon size grows at 256 bytes per request 1101085 getagents script has RELEASE variable set to Beta in SNM 2.0 FCS 1101393 sending two or more reports from the browser to the grapher can cause corrupted dates 1101519 set tool does not handle enumerating values correctly 1101848 SNMP proxy does IP address lookup for each device in snmp.hosts, resulting in inefficient performance 1103444 logger incorrectly looks for "monitor.log" instead of "monitor-log" in /etc/snm.conf 1103448 na.snmp core dumps when parsing schema on an attribute with no OID defined 1103658 the na.snmp-trap agent/daemon fails to parse some entries in the snmp hosts file 1103998 na.snmp-trap doesn't accept IP addresses as well as hostnames in snmp hosts file 1104111 a bug in snm_cmd -S (set_value) generates an "Assertion failed" message 1104165 SNMP proxy ignores vendor proxy field in the SNMP hosts file 1104178 when performing an SNMP set operation from the set tool, the SNMP proxy ignores any Vendor proxy specified in the SNMP hosts file 1104402 SNMP proxy cannot handle empty community strings 1104522 event dispatcher does not free disk space when event logfile is removed Bug reports fixed in version 2 of this patch (100770-02) Bug ID Problem Description ------ ------------------- 1088459 na.snmp ignored a valid SNMP schema 1091550 na.snmp core dumps! 1092086 quickdump fails after being out of use for approx 5-10 hours 1093396 deferred reporting does not work for hostperf, ping and SNMP proxy agents 1098854 use of the snm_db api causes snm console program to consume memory. 1100205 dump from running na.snmp with the -d 2 flag 1103595 Clicking on Save in Data Report Log window may core dump SNM console 1108884 snmdb_lock appears to adversely effect signal handling 1109638 snm_cmd can cause na.snmp to dump core 1110117 diskinfo doesn't give accurate disk used % w/ automounted filesystems 1110454 using snmdb_lock results in intermittent application crashes 1110458 the request.log file can grow without limit 1110613 many na.diskinfo processes running on client machine 1110792 snmpd seems to have a memory leak 1111505 unable to start more than 190 requests after installing the SNM 2.0 jumbo patch 1112851 Strange SNM messages in /var/adm/message 1113044 Several agents left from the day before when SNM had not run for 13 hours 1113196 na.iostat fails to collect disk information on some systems. 1113772 using snmdb_lock causes high CPU utilization 1114274 Lots of "cannot verify request" messages in /var/adm/messages 1114642 CTE Runaway na.ping agents take huge chunks of CPU and never die 1115514 na.snmp processes grab memory & hang the system 1115906 na.snmp daemon starts, grows large and never exits 1117038 one get's an "API error: Unknow error" if a requests is restarted with new param 1119472 Secure RPC and Proxy SNM agent do not work. 1119618 snmp proxy loses track of schemas in search path 1120121 na.snmp dies with segmentation violation when supplying optional OID arguments 1120140 Using secure RPC on lots of agents causes the snm console to crash. 1121830 snm console or na.snmp agent periodically times out then recovers 1123732 na.snmp core dumps while reading IP routing table 1125159 proxy goes crazy if user puts a negative timeout value in SNMP timeout field Bug reports fixed in version 3 of this patch (100770-03) 1118845 na.diskinfo agent complains about an invalid table key Bug reports fixed in version 4 of this patch (100770-04) 1120140 Using secure RPC on lots of agents causes the snm console to crash. Bug reports fixed in version 5 of this patch (100770-05) 1107397 Sun supplied agents should subtract processing time from reporting interval 1125676 snm_cmd with -g oid uses huge amount of memory 1132110 Using "Set Tool" to retrieve SNMP attribute values give extra character/garbage 1135161 activity daemon and agent fails to hand-shake, resulting in keep-alive errors 1135173 with patch 100770-02, broken pipe error has been introduced na.snmp 1136648 SNMP trap receiver is not flexible enough This patch adds a command line option (-p) to the SNMP trap receiver (na.snmp-trap). This allows the administrator to specify the port number on which it listens for incoming traps. 1140120 Agent dies if event is triggered when send once is applied 1140496 Control characters for the "ifDescr" attribute in the monitor.log file 1143704 Control characters for the "ifDescr" attribute in the event.log file 1145296 na.snmp needs to support user-defined port number This patch adds a command line option (-p) to the SNMP proxy agent (na.snmp). This allows the administrator to specify the port number to which the agent will send SNMP requests. 1146069 hostperf proxy agent can core dump under heavy load Bugs fixed in patch version 6: 1143263 using snmdb_lock results in intermittant application crashes 1146953 na.ping rpc program gets killed when used in debug mode 1132755 the event dispatcher na.event exits unexpectedly Bugs fixed in patch version 7: 1156532 when launching 100+ event requests, a few fail with API unknown host:localhost 1155606 paths specified in .SNMdefaults > 255 causes the console to crash at startup 1151091 na.ping retransmits Echo regardless it already got Echo reply 1156959 Memory management problem occures with function netmgt_set_value 1157117 API hangs when sending 30-40 requests to na.snmp agent 1162427 snm_cmd requests hang until activity log cleared 1149566 snmdb_console_save_components times out on large files 1152409 snmp proxy agent incorrectly retrieves tables when rows have missing attributes 1152747 Certain MIB IfIndex variables return fixed values 1153908 na.diskinfo produces /etc/mtab, no such file or direct. but it exists Bugs fixed in patch version 8: 1156532 re-do the fix for avoiding localhost calling gethostbyname changed Konkord to Concord for enterprises.oid forced to reload data base if SNM_NAME or USER env. variable had changed 1156959 Memory management problem occures with function netmgt_set_value 1165200 snm_cmd produces extra characters in report INSTALLATION INSTRUCTIONS Before you install the SunNet Manager 2.0 patch, you must have SunNet Manager 2.0 FCS installed and running on your system. To install this patch : 1. Close down your network management system by stopping any active requests and then exiting the SunNet Manager Console and any Partner applications you may be running. 2. Become root. 3. run "patch_install" (make sure the permission OK) 4. If you have previously run the getagents script to install the SunNet Manager agents onto other systems, you may wish to rerun getagents in order to install the updated agent binaries and libraries from this patch onto those other systems. 5. Ensure that the activity.log and request.log files are removed on each SunNet Manager system (the patch install script attempts to do this for you). These files are normally located in the /var/adm/snm directory, or in the directory identifed by your SNMDBDIR environment variable, if set. 6. Restart your SunNet Manager.