(234020) Fixes the problem of configuration information not being written to /usr/agent/config/agt/snmpd.cnf.
(237458) Fixes the problem of incorrect processor and memory entries in the device table when Quads are renamed or swapped out.
(240541) Fixes the problem of an excessive number of "No swap device path???" errors being recorded in the VCS logs.
(238633) Fixes the problem of no processor table entries and of segmentation faults.
(236614) Provides an ifNumber.0 error fix for ptxagt.
(234685) Provides a new 1.3-based snmpdm that resolves potential problems with overlapping queries.
The number that appears in parentheses in problem report titles is the internal number assigned to the report. These problems will be corrected in a future release unless otherwise noted.
The variable hrFSBootable should report on whether the system can be booted from this filesystem. DYNIX/ptx doesn't capture this information in a usable way, so the variable is always assigned the value false.
Workaround. None.
If BMC/PATROL is started before ptx/AGENT, it can open UDP port 161 and prevent ptx/AGENT from opening it.
Workaround. Start ptx/AGENT first.
RAID disk health status is incorrectly reported to CommandPoint Monitor V1.0 by ptx/AGENT.
Workaround. None.
Uploading is currently done at 100 values/second for a Symmetry system. This is not very fast when you are trying to upload a lot of information about a system.
Workaround. None.
ptx/AGENT is not able to find out if the Fibre Channel Bridge is offline.
Workaround. None.
The system call which the agent invokes to get the information, incorrectly reports SCSI ID's for Pbays as 16.
Workaround. None.
The snmpdm process sets up a UDP socket that never gets read from (typically file descriptor 6). As this socket is not part of the standard poll list, UDP error messages can stack up and ultimately starve the system of 64-byte streams buffers. This problem appears only in a few versions of TCP/IP.
Workaround. The problem occurs if traps are not configured correctly. To fix the problem, configure the agent to specify a proper trap host to receive the traps generated by agent.
When the DASS shuts down, the agent appears to hang.
Workaround. None. ptx/AGENT appears to hang for approximately two or three minutes and then returns to normal.