HP StorageWorks Scalable File Share Release Notes - Version 2.3

Documentation updates and corrections 1–27
1.8.2.8 Section 9.32.1.1 Using the remote console
Ignore the initial caution paragraph:
(sfs management tools now use the ssh protocol for all communications with the iLO, so all passwords now
travel encrypted.)
Append to the step 1 Note:
But only iLO2 Advanced have the remote console feature. If you have an iLO2 Standard, only the console
virtual serial port is available, you cannot use the --remote option.
Below that step 1 Note, add a Tip:
TIP: Use the vsp or remcons scripts as front ends to hpls_console, for the Virtual Serial Port and Remote
Console modes respectively. These scripts have a simplified command line (Example: remcons servername),
and remcons clips the output in a virtual 80x25 box. This makes the console output much more readable if you're
running from a larger terminal emulation window.
1.8.2.9 Section 9.32.2 Troubleshooting iLO access
Change the beginning of the first paragraph to:
When you use the telnet(1) or ssh(1) command to access the iLO...
1.8.2.10 Section 9.8 The scan mac command fails
The scan mac command may not scale when applied to more than 20 servers at a time. HP recommends
that you proceed by increments of 20 servers or less in such cases.
1. 8 . 2.11 Section 9.9 Setting Lustre debug level
If you want to permanently enable the Lustre debug facility, perform the following steps:
1. Set the debug level attributes as follows:
sfs> set attribute lnet.debug=-1
sfs> set attribute lnet.subsystem_debug=-1
In this example, the debug level is set to -1, which turns on all debugging. HP recommends that you
only ever enable Lustre debug under the advice of HP support as setting debug levels will impact
system performance. A debug level of 0x3f0400 rather than -1 is generally advised by HP support.
2. To bring the change into effect, use one of the following options:
Stop all of the file systems by entering the stop filesystem filesystem_name command for each file
system, then start the file systems again by entering the start filesystem
filesystem_name command for each file system.
Alternatively, if you do not want to stop the file systems, enter the following commands on the
MDS server and on each Object Storage Server:
# echo -1 > /proc/sys/lnet/debug
# echo -1 > /proc/sys/lnet/debug# echo -1 > /proc/sys/lnet/subsystem_debug
1.8.2.12 Section 9.34 Troubleshooting failed SFS20 arrays
With the release of SFS20 firmware Version 2.02 and later, it is possible to retrieve diagnostic logs from an
SFS20 using the hpaducli command.
The command retrieves logs for all attached SFS20 units attached to the server which the command is run on.
To collate the logs into file /tmp/adu.txt run: