Due to a disk crash, I had to reload my HP 3000 system recently. I’ve just discovered that system logging has been suspended. How do I resume system logging?
Paul Christidis replies:
The reason for the suspension of logging was most likely due to a duplicate log file name. When the SLT was created the then-current log number was recorded, and when you restarted the system from your most recent SLT it tried to open the sequentially next log file. Said file already existed.
- MOVE the existing log files to a hold area
- Determine what logfile the system resumed on
- Perform a series of SWITCHLOG commands until the logfile number advances to one more than the highest number in the hold area
- Then move the held logfiles back to the pub.sys group — replacing the ones created by the series of ‘switchlog’ commands.
Is there a way to see the IP address associated with a particular login?
Any user with SM can do the following, for example:
HPSTDIN_NETWORK_ADDR = 172.16.0.30
The command :listf ci.pub.sys,8 will list all sessions and will show their associated IP address.
I’ve got an older model HP 3000 and I'd like to start monitoring it with SNMP for things like CPU utilized, jobs running or whatever other cool stat I can SNMP-grab. The problem I have is I can’t find the MIBs for it anywhere.
Andreas Schmidt replies:
First of all, I do not recommend the use of SNMP on the 3000, for performance but also security reasons. SNMP is not the securest protocol, as you know. Nevertheless, here are some hints:
• In the group NET.SYS you will find the SNMPUDC. This should be set in any case for MANAGER.SYS or on system level.
• Having set this, a SNMPCONTROL STATUS will show you the status of the SNMP subsystem.
• SNMPCONTROL START / STOP are self-explaining.
• The MIBs specific for MPE can be found in the document HP SNMP/XL User’s Guide