A.05.80 HP Insight Remote Support Advanced Managed Systems Configuration Guide (June 2013)

Managed Systems Configuration Guide
Chapter 14: Tru64 UNIX Server Configuration
Clear the Log with binlogd Running
For version 5.1A or higher, follow these steps on each cluster node that you want to clear:
1. Verify the binary.errlog CDSL section is complete as previously described.
2. If desired, keep any previously saved copy from being overwritten by moving it to any appropriate
name, for example:
# cd /var/cluster/members/member/adm/binlog.saved
# mv binary.errlog.saved binary.errlog.2002_06_11
3. Cause binlogd to copy and clear the original error log:
# kill -USR1 `cat /var/run/binlogd.pid`
The previous command does not kill the binlogd process. Instead, it sends a signal to binlogd
that causes it to copy /var/adm/binary.errlog to
/var/cluster/members/member/adm/binlog.saved. Then, the original
/var/adm/binary.errlog file gets recreated with only a configuration event. Note that
/var/adm/binary.errlog is a CDSL that points to
/var/cluster/members/<memb>/adm/binary.errlog.
For further details, including how to automate this kind of error log management, see the section on
Managing the Binary Error Log File in the binlogd man page.
Verify Serial Number
On GS80, GS160, and GS320 systems, verify the serial number as directed before installing ELMC on the
managed system.
Certain GS80, GS160, and GS320 systems did not have their system serial number set correctly at the
factory, and SEA rules on the CMS only function when the serial number is set correctly. Affected serial
numbers will begin with the letter “G.”
At the SRM console firmware prompt (the prompt when you first power the system on), check the serial
number with the following command:
show sys_serial_num
The serial number shown should match the actual serial number on the model/serial number tag located in
the power cabinet. If necessary, change the serial number with the following command:
set sys_serial_num
Enter the six-character serial number provided on the tag in the power cabinet.
Note: This issue also can arise when multiple AlphaServers are ordered, because the factory may
assign an identical serial number to each system. In this scenario, SEA rules do not work correctly
because they require that each AlphaServer have a unique number. If this is the case, uniquely
identify each AlphaServer by appending –1, –2, –3, and so on, to the serial numbers when you use the
set sys_serial_num command.
HP Insight Remote Support Advanced (A.05.80)Page 100 of 204