The easiest way to get files from the secondary SP is from Unisphere, but this only works for dump files. Any other files from the secondary SP must be collected with one of the methods that are listed in this KB.
Before you begin:
Direct access is only possible to the primary SP when connecting to a Unity array over SSH. In order to connect to the peer SP, you must SSH in to it from the primary SP (with "ssh peer," or "ssh spX," where X is the opposite from the SP you are in at the moment). This means that grabbing files from the secondary SP directly is a bit more complicated.
Method 1 (easiest):
Create a temporary network interface on the peer SP mgmt port with the integrated tool svc_network command (see svc_network -h for full details).
This must be run from the SP where you are setting management up the temporary interface. It is not necessary to create a temp interface on the primary SP under normal circumstances.
Syntax:
svc_network -i mgmt -a X.X.X.X -n Y.Y.Y.Y -g Z.Z.Z.Z (Where X.X.X.X is the temp IP, Y.Y.Y.Y is the netmask, and Z.Z.Z.Z is the default gateway. These must be provided by the Unity administrator or the network admin.)
This SP (secondary) must have a physical connection on the network port.
Once this temp IP is set up, you can ping it in the user network and be able to SSH directly in to the secondary SP (and download files directly from it).
Method 2:
Download the files directly using WinSCP by setting up a PuTTY session first and creating a "tunnel" to the secondary SP. See Dell KB article 4362:
Dell Unity: How to transfer files from the peer Storage Processor (SP) on a Unity array (Dell Correctable).
Method 3:
If the above methods are not possible, then you must copy the files from the secondary SP to the primary SP, and then download with normal tools like WinSCP from the primary SP.
Be careful as copying large files to the other SP may cause issues on that SP.
Syntax:
scp your-file peer:/home/service/user (Use /home/service for Unity OE 4.4.1 or earlier.
DO NOT use other target directories.)
Example:
service@(none) spa:~/user# scp test_file.tar peer:/home/service/user
test_file.tar
0% 318MB 112.2MB/s 00:06 ETA
50% 318MB 112.2MB/s 00:02 ETA
100% 567MB 94.5MB/s 00:06
service@(none) spa:~/user#
In this example, the file is now on SPB under /home/service.
This is a push operation, not a pull operation. The command must be run on the SP where the file is.
Always use /home/service/user (or /cores/service/user - same place) as the target location to avoid space-related issues such as Dell KB article 000022433:
Dell Unity: Writing to /tmp on Unity system causes an SP Reboot if /tmp becomes full.
For Unity OE 4.4.1 or earlier, always user /home/service
The above guidance is assuming both SPs are in normal mode. The /cores partition mounts to /mnt/cores if the SPs are in service mode.