Sun Fire V20z Server
 
Sun Fire V40z Server
 

GCS>Sun Microsystems>Servers>x64 Servers
 

This procedure will not work if the main console for the platform is directed to the rear system serial port.
1.To check the direction of the console perform the following check.
Login to the Service Processor and issue the command:
platform get console
If this reports the following then the rear serial port is being used,and this procedure will not work.
Rear Panel
Platform COMA
If this reports the following then the SOL option is being used and the procedure will work.(Please note the speed and log values may be different.)
Rear Panel Console Redirection Speed Pruning Log Trigger
SP Console Enabled             9600  No      244 KB
2.Setup the remote server to run SP based diagnostics ,this procedure is fully documented in Sun Fire V20z and Sun Fire V40z Servers--Installation Guide.It is only necessary to unpack the NSV package,the diagnostics do not need to loaded or started.
3.When the NSV package has been unpacked in the previous procedure it will have created a directory named "logs" within the top level of the NSV directory
In this example the NSV package has been unpacked in the directory /nsv_files of the remote server
# ls /nsv_files
diags                   nsv_V2.4.0.12.zip       update_server
docs                    processRules.xml        V2.4.0.12_manifest.xml
logs                    scripts
manifest_template2.xsl  snmp
#
Change the permissions of the logs directory
# chmod 777 logs
4.Mount the remote directory on the SP.This example uses the same directory as before.
$ sp add mount -r ip_addr_of_remote_server:/nsv_files -l /mnt
5.Check the files can be seen by the SP on the mount point
$ ls /mnt
V2.4.0.12_manifest.xml  diags  docs  logs  manifest_template2.xsl  nsv_V2.4.0.12.zip  processRules.xml  scripts  snmp  update_server
$
6.reboot the SP,this will not effect the running of the platform.
$ sp reboot
7.Restart the console from the SP and type some commands to test logging is functioning.
$ platform console
[Enter `^Ec?' for help]
#
# ls /usr
8.To check logging is working to the remote server.Change directory on the remote server to the logs directory.There will now be a new directory within this which contains the name or ethernet address of the SP.
If the SP has been given a name this will be displayed as a directory.If the SP has not been named the directory will be the ethernet address of the SP.
# ls logs
tools           v20z-test_system-sp
#
Change directory to the SP name in this example v20z-test_system-sp
# ls v20z-test_system-sp
console    event.log
#
The console file contains the log.
The file event.log is a perl copy of the System Event Log (SEL).To view this use the viewer script in the tools directory.
# perl /nsv_files/logs/tools Viewer.pl --file /nsv_files/logs/v20z-test_system-sp/event.log

This solution has no attachment