4. The procedure to create the snap on an IBM SAN Volume Controller system, including the  latest statesave from each node, begins. This process might take a few minutes  (Figure 13-65). 1. Log in to the CLI and run the  svc_snap  command that matches the type of snap that is  requested by IBM Support: – Standard logs (type 1): – Standard logs plus one existing statesave (type 2): – Standard logs plus most recent statesave from each node (type 3): – Standard logs plus new statesaves: 2. We collect the type 3 (option 3) information, which is automatically uploaded to the PMR  number that is provided by IBM Support, as shown in Example 13-6. 3. If you do not want to upload automatically the snap to IBM, do not specify the  upload  pmr=ppppp,bbb,ccc  part of the commands. When the snap creation completes, it creates a  file that is named with this format: The CLI can be used to collect and upload a support package as requested by IBM Support  by performing the following steps: svc_snap upload pmr=ppppp,bbb,ccc gui1 svc_snap upload pmr=ppppp,bbb,ccc gui2 svc_snap upload pmr=ppppp,bbb,ccc gui3 svc_livedump -nodes all -yes svc_snap upload pmr=ppppp,bbb,ccc gui3 /dumps/snap.<panel_id>.YYMMDD.hhmmss.tgz It takes a few minutes for the snap file to complete, and longer if it includes statesaves.  Chapter 13. Reliability, availability, and serviceability, and monitoring and troubleshooting  759 Example 13-6 The svc_snap command ssh superuser@10.18.228.64 Password: IBM_2145:ITSO DH8_B:superuser>> svc_snap upload pmr=04923,215,616 gui3 13.9.2 Collecting logs by using the CLI Figure 13-65 Task detail window