-
Notifications
You must be signed in to change notification settings - Fork 268
Expand file tree
/
Copy pathadm_support.xml
More file actions
2234 lines (2198 loc) · 79.2 KB
/
adm_support.xml
File metadata and controls
2234 lines (2198 loc) · 79.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0"?>
<!DOCTYPE chapter [
<!ENTITY % entities SYSTEM "generic-entities.ent">
%entities;
]>
<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:its="http://www.w3.org/2005/11/its" version="5.0" xml:id="cha-adm-support">
<title>Gathering system information for support</title>
<info>
<meta name="description" its:translate="yes">Learn about accessing detailed system information, creating problem reports, and analyzing SupportConfig output with SUSE tools</meta>
<abstract>
<para>
For a quick overview of all relevant system information of a machine,
&productname; offers the
<systemitem class="systemname">hostinfo</systemitem> package. It also helps
system administrators to check for tainted kernels (that are not supported)
or any third-party packages installed on a machine.
</para>
<para>
In case of problems, a detailed system report may be created with either
the <command>supportconfig</command> command line tool or the &yast;
<guimenu>Support</guimenu> module. Both collect information about the
system such as: current kernel version, hardware, installed packages,
partition setup, and much more. The result is a TAR archive of files. After
opening a Service Request (SR), you can upload the TAR archive to Global
Technical Support. It helps to locate the issue you reported and to
assist you in solving the problem.
</para>
<para>
Additionally, you can analyze the <command>supportconfig</command> output
for known issues to help resolve problems faster. For this purpose,
&productname; provides both an appliance and a command line tool for
<literal>Supportconfig Analysis</literal> (SCA).
</para>
</abstract>
<dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">
<dm:bugtracker/>
<dm:translation>yes</dm:translation>
</dm:docmanager>
<revhistory xml:id="rh-cha-adm-support">
<revision>
<date>2026-04-07</date>
<revdescription>
<para/>
</revdescription>
</revision>
</revhistory>
</info>
<!-- support: sitar / onstar, siga, supportconfig -->
<sect1 xml:id="sec-admsupport-hostinfo">
<title>Displaying current system information</title>
<para>
For a quick and easy overview of all relevant system information when
logging in to a server, use the package
<systemitem class="systemname">hostinfo</systemitem>. After it has been
installed on a machine, the console displays the following information to
any &rootuser; user that logs in to this machine:
</para>
<example xml:id="ex-support-hostinfo">
<title>Output of <command>hostinfo</command> when logging in as &rootuser;</title>
<screen>Welcome to SUSE Linux Enterprise Server 15 SP2 Snapshot8 (x86_64) - Kernel \r (\l).
Distribution: SUSE Linux Enterprise Server 15 SP2
Current As Of: Wed 25 Mar 2020 12:09:20 PM PDT
Hostname: localhost
Kernel Version: 5.3.18-8-default
Architecture: x86_64
Installed: Thu 19 Mar 2020 11:25:13 AM PDT
Status: Not Tainted
Last Installed Package: Wed 25 Mar 2020 11:42:24 AM PDT
Patches Needed: 0
Security: 0
3rd Party Packages: 219
Network Interfaces
eth0: &exampledomain2ip;/24 &exampledomain2ipv6;/64
Memory
Total/Free/Avail: 7.4Gi/6.4Gi/6.8Gi (91% Avail)
CPU Load Average: 7 (3%) with 2 CPUs
</screen>
</example>
<para>
In case the output shows a <literal>tainted</literal> kernel status, see
<xref linkend="sec-admsupport-kernel"/> for more details.
</para>
</sect1>
<sect1 xml:id="sec-admsupport-supportconfig">
<title>Collecting system information with supportconfig</title>
<para>
To create a TAR archive with detailed system information that you can hand
over to Global Technical Support, use either:
</para>
<itemizedlist>
<listitem>
<para>the command <command>supportconfig</command> or, </para>
</listitem>
<listitem>
<para>the &yast; <guimenu>Support</guimenu> module.</para>
</listitem>
</itemizedlist>
<para>
The command line tool is provided by the
package <systemitem>supportutils</systemitem> which is installed by default.
The &yast; <guimenu>Support</guimenu> module is also based on the command
line tool.
</para>
<para>
Depending on which packages are installed on your system, some of these
packages integrate Supportconfig plug-ins. When Supportconfig is executed,
all plug-ins are executed as well and create one or more result files for
the archive. That has the benefit that the only topics checked are those
that contain a specific plug-in for them. Supportconfig plug-ins are stored
in the directory <filename>/usr/lib/supportconfig/plugins/</filename>.
</para>
<sect2 xml:id="sec-admsupport-supportconfig-sr">
<title>Creating a service request number</title>
<para>
Supportconfig archives can be generated at any time. However, for
handing over the Supportconfig data to Global Technical Support, you need
to generate a service request number first. You need it to upload the
archive to support.
</para>
<para>
To create a service request, go to
<link xlink:href="https://scc.suse.com/support/requests"/> and follow the
instructions on the screen. Write down the service request number.
</para>
<note>
<title>Privacy statement</title>
<para>
&suse; treats system reports as confidential data. For
details about our privacy commitment, see <link xlink:href="https://www.suse.com/company/policies/privacy/"/>.
</para>
</note>
</sect2>
<sect2 xml:id="sec-admsupport-supportconfig-upload">
<title>Upload targets</title>
<para>
After having created a service request number, you can upload your
Supportconfig archives to Global Technical Support as described in
<xref linkend="pro-admsupport-submit-yast"/> or
<xref linkend="pro-admsupport-submit-cli"/>. Use one of the following
upload targets:
</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>
<!-- TODO: Fix outdated links -->
North America: FTP <link xlink:href="ftp://support-ftp.us.suse.com/incoming/"/>, FTPS <link xlink:href="ftps://support-ftp.us.suse.com/incoming/"/>
</para>
</listitem>
<listitem>
<para>
EMEA, Europe, the Middle East, and Africa: FTP
<link xlink:href="ftp://support-ftp.emea.suse.com/incoming"/>, FTPS <link xlink:href="ftps://support-ftp.emea.suse.com/incoming"/>
</para>
</listitem>
</itemizedlist>
<para>
Alternatively, you can manually attach the TAR archive to your service
request using the service request URL:
<link xlink:href="https://scc.suse.com/support/requests"/>.
</para>
</sect2>
<sect2 xml:id="sec-admsupport-yast">
<title>Creating a supportconfig archive with &yast;</title>
<para>
To use &yast; to gather your system information, proceed as follows:
<remark>2008-11-20 toms: YaST asks the user to open a URL as
root(!). This happens when the users clicks on "Open" (Open
Support Center/ This will start a browser with
Support Center Portal). I do not think we should describe this
and only *use* the above URL as a normal user for security
reasons.</remark>
</para>
<procedure>
<step>
<para>
Start &yast; and open the <guimenu>Support</guimenu> module.
</para>
<informalfigure>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="yast2_support_main.png" width="70%"/>
</imageobject>
<imageobject role="html">
<imagedata fileref="yast2_support_main.png" width="60%"/>
</imageobject>
</mediaobject>
</informalfigure>
</step>
<step>
<para>
Click <guimenu>Create report tarball</guimenu>.
</para>
</step>
<step>
<para>
In the next window, select one of the Supportconfig options from the
radio button list. <guimenu>Use Custom (Expert) Settings</guimenu> is
preselected by default. To test the report function first,
use <guimenu>Only gather a minimum amount of info</guimenu>. For
additional information on the other options, refer to the
<command>supportconfig</command> man page.
</para>
<para>
Click <guimenu>Next</guimenu>.
</para>
</step>
<step xml:id="st-supportconfig-contact">
<para>
Enter your contact information. It is saved in the
<filename>basic-environment.txt</filename> file and included in the
created archive.
</para>
</step>
<step xml:id="st-supportconfig-upload-target">
<para>
To submit the archive to Global Technical Support, provide the required <guimenu>Upload
Information</guimenu>. &yast; automatically suggests an
upload server. To modify it, refer to
<xref linkend="sec-admsupport-supportconfig-upload"/> for details of
which upload servers are available.
</para>
<para>
To submit the archive later, leave the
<guimenu>Upload Information</guimenu> empty.
</para>
</step>
<step>
<para>
Click <guimenu>Next</guimenu> to start the information collection process.
</para>
<informalfigure>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="yast2_support_conf.png" width="90%"/>
</imageobject>
<imageobject role="html">
<imagedata fileref="yast2_support_conf.png" width="80%"/>
</imageobject>
</mediaobject>
</informalfigure>
<para>
After the process is finished, click <guimenu>Next</guimenu>.
</para>
</step>
<step>
<para>
To review the collected data, select the desired file from <guimenu>File
Name</guimenu> to view its contents in &yast;. To remove a file from the
TAR archive before submitting it to support, use <guimenu>Remove from
Data</guimenu>. Press <guimenu>Next</guimenu>.
</para>
</step>
<step>
<para>
Save the TAR archive. If you started the &yast; module as &rootuser;
user, &yast; prompts to save the archive to <filename>/var/log</filename>
(otherwise, to your home directory). The file name format is
<filename>scc_<replaceable>HOST</replaceable>_<replaceable>DATE</replaceable>_<replaceable>TIME</replaceable>.tbz</filename>.
</para>
</step>
<step>
<para>
To upload the archive to support directly, make sure <guimenu>Upload log
files tarball to URL</guimenu> is activated. The <guimenu>Upload
Target</guimenu> shown here is the one that &yast; suggests in <xref linkend="st-supportconfig-upload-target"/>. To modify the upload target,
check which upload servers are available in <xref linkend="sec-admsupport-supportconfig-upload"/>.
</para>
</step>
<step>
<para>
To skip the upload, deactivate <guimenu>Upload log files
tarball to URL</guimenu>.
</para>
</step>
<step>
<para>
Confirm the changes to close the &yast; module.
</para>
</step>
</procedure>
</sect2>
<sect2 xml:id="sec-admsupport-cli">
<title>Creating a supportconfig archive from command line</title>
<para>
The following procedure shows how to create a Supportconfig archive, but
without submitting it to support directly. For uploading it, you need to
run the command with certain options as described in
<xref linkend="pro-admsupport-submit-cli"/>.
</para>
<procedure>
<step>
<para>
Open a shell and become <systemitem class="username">root</systemitem>.
</para>
</step>
<step>
<para>
Run <command>supportconfig</command>. It is enough to
run this tool without any options. However, the most common options
are displayed in the following list:
</para>
<variablelist>
<varlistentry>
<term><option>-E <replaceable>MAIL</replaceable></option></term>
<term><option>-N <replaceable>NAME</replaceable></option></term>
<term><option>-O <replaceable>COMPANY</replaceable></option></term>
<term><option>-P <replaceable>PHONE</replaceable></option></term>
<listitem>
<para>
Sets your contact data: e-mail address (<option>-E</option>), company
name (<option>-O</option>), your name (<option>-N</option>), and
your phone number (<option>-P</option>).
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-i <replaceable>KEYWORDS</replaceable></option></term>
<term><option>-F</option></term>
<listitem>
<para>
Limits the features to check. The placeholder <replaceable>KEYWORDS</replaceable>
is a comma separated list of case-sensitive keywords. Get a list
of all keywords with <command>supportconfig -F</command>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-r <replaceable>SRNUMBER</replaceable></option></term>
<listitem>
<para>
Defines your service request number when uploading the generated
TAR archive.
</para>
</listitem>
</varlistentry>
</variablelist>
</step>
<step>
<para>
Wait for the tool to complete the operation.
</para>
</step>
<step>
<para>
The default archive location is <filename>/var/log</filename>, with the
file name format being
<filename>scc_<replaceable>HOST</replaceable>_<replaceable>DATE</replaceable>_<replaceable>TIME</replaceable>.tbz</filename>
</para>
</step>
</procedure>
</sect2>
<sect2 xml:id="sec-admsupport-supportconfig-log">
<title>Understanding the output of <command>supportconfig</command></title>
<para>
Whether you run <command>supportconfig</command> through &yast; or directly,
the script gives you a summary of what it did.
</para>
<screen> Support Utilities - Supportconfig
Script Version: 3.0-98 <!--<co xml:id="co-admsupport-script-version"/>-->
Script Date: 2017 06 01<!-- <xref linkend="co-admsupport-script-version"/>-->
[...]
Gathering system information
Data Directory: /var/log/scc_d251_180201_1525 <co xml:id="co-admsupport-script-datadir"/>
Basic Server Health Check... Done <co xml:id="co-admsupport-script-done"/>
RPM Database... Done <xref linkend="co-admsupport-script-done"/>
Basic Environment... Done <xref linkend="co-admsupport-script-done"/>
System Modules... Done <xref linkend="co-admsupport-script-done"/>
[...]
File System List... Skipped <co xml:id="co-admsupport-script-skipped"/>
[...]
Command History... Excluded <co xml:id="co-admsupport-script-excluded"/>
[...]
Supportconfig Plugins: 1 <co xml:id="co-admsupport-script-plugin"/>
Plugin: pstree... Done
[...]
Creating Tar Ball
==[ DONE ]===================================================================
Log file tar ball: /var/log/scc_d251_180201_1525.txz <co xml:id="co-admsupport-script-archive"/>
Log file size: 732K
Log file md5sum: bf23e0e15e9382c49f92cbce46000d8b
=============================================================================</screen>
<calloutlist>
<!--<callout arearefs="co-admsupport-script-version">
<para>
The version and the date of the <command>supportconfig</command> command.
Higher versions can support more features.
</para>
</callout>-->
<callout arearefs="co-admsupport-script-datadir">
<para>
The temporary data directory to store the results. This directory is
archived as tar file, see <xref linkend="co-admsupport-script-archive"/>.
</para>
</callout>
<callout arearefs="co-admsupport-script-done">
<para>
The feature was enabled (either by default or selected manually) and
executed successfully. The result is stored in a file (see <xref linkend="tab-admsupport-features-and-filenames"/>).
</para>
</callout>
<callout arearefs="co-admsupport-script-skipped">
<para>
The feature was skipped because files of one or more RPM packages
were changed.
</para>
</callout>
<callout arearefs="co-admsupport-script-excluded">
<para>
The feature was excluded because it was deselected via the <option>-x</option>
option.
</para>
</callout>
<callout arearefs="co-admsupport-script-plugin">
<para>
The script found one plug-in and executes the plug-in
<command>pstree</command>. The plug-in was found in the directory
<filename class="directory">/usr/lib/supportconfig/plugins/</filename>.
See the man page for details.
</para>
</callout>
<callout arearefs="co-admsupport-script-archive">
<para>
The tar file name of the archive, by default compressed with <command>xz</command>.
</para>
</callout>
</calloutlist>
</sect2>
<sect2 xml:id="sec-admsupport-options">
<title>Common supportconfig options</title>
<para>
The <command>supportconfig</command> utility is usually called without any
options. Display a list of all options with
<command>supportconfig</command> <option>-h</option> or refer to the man
page. The following list gives a brief overview of common use cases:
</para>
<variablelist>
<varlistentry>
<term>Reducing the size of the information being gathered</term>
<listitem>
<para>
Use the minimal option (<option>-m</option>):
</para>
<screen>&prompt.sudo;supportconfig -m</screen>
</listitem>
</varlistentry>
<varlistentry>
<term>Limiting the information to a specific topic</term>
<listitem>
<para>
If you have already localized a problem <!--with the default
<command>supportconfig</command> output and have found--> that relates
to a specific area or feature set only, you should limit the collected
information to the specific area for the next
<command>supportconfig</command> run. For example, if you detected
problems with LVM and want to test a recent change that you did to the
LVM configuration. In that case it makes sense to gather the minimum
Supportconfig information around LVM only:
</para>
<screen>&prompt.sudo;supportconfig -i LVM</screen>
<para>
Additional keywords can be separated through commas. For example,
an additional disk test:
</para>
<screen>&prompt.sudo;supportconfig -i LVM,DISK</screen>
<para>
For a complete list of feature keywords that you can use for limiting
the collected information to a specific area, run:
</para>
<screen>&prompt.sudo;supportconfig -F</screen>
</listitem>
</varlistentry>
<varlistentry>
<term>Including additional contact information in the output:</term>
<listitem>
<screen>&prompt.sudo;supportconfig -E tux@example.org -N "Tux Penguin" -O<!--
--> "Penguin Inc." ...</screen>
<para>
(all in one line)
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Collecting already rotated log files</term>
<listitem>
<screen>&prompt.sudo;supportconfig -l</screen>
<para>
This is especially useful in high logging environments or after a kernel
crash when syslog rotates the log files after a reboot.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>
<sect2 xml:id="sec-admsupport-log">
<title>Overview of the archive content</title>
<para>
The TAR archive contains all the results from the features. Depending on
what you have selected (all or only a small set), the archive can contain
more or less files.
The set of features can be limited through the <option>-i</option>
option (see <xref linkend="sec-admsupport-options"/>).
</para>
<para>
To list the content of the archive, use the following <command>tar</command>
command:
</para>
<screen>&prompt.root;<command>tar</command> xf /var/log/scc_&exampleclient;_180131_1545.tbz</screen>
<para>
The following file names are always available inside the TAR archive:
</para>
<variablelist>
<title>Minimum files in archive</title>
<varlistentry>
<term><filename>basic-environment.txt</filename></term>
<listitem>
<para>Contains the date when this script was executed and system information
like version of the distribution, hypervisor information, and more.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>basic-health-check.txt</filename></term>
<listitem>
<para>
Contains basic health checks like uptime, virtual memory statistics,
free memory and hard disk, checks for zombie processes, and more.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>hardware.txt</filename></term>
<listitem>
<para>
Contains basic hardware checks like information about the CPU architecture,
list of all connected hardware, interrupts, I/O ports, kernel boot messages,
and more.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>messages.txt</filename></term>
<listitem>
<para>
Contains log messages from the system journal.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>rpm.txt</filename></term>
<listitem>
<para>Contains a list of all installed RPM packages, the name,
where they are coming from, and their versions.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>summary.xml</filename></term>
<listitem>
<para>Contains information in XML format like distribution,
the version, and product specific fragments.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>supportconfig.txt</filename></term>
<listitem>
<para>
Contains information about the <command>supportconfig</command> script
itself.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>y2log.txt</filename></term>
<listitem>
<para>
Contains &yast; specific information like specific packages, configuration
files, and log files.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
<xref linkend="tab-admsupport-features-and-filenames"/> lists all available
features and their file names. Further service packs can extend the list,
as can plug-ins.
</para>
<table xml:id="tab-admsupport-features-and-filenames">
<title>Comparison of features and file names in the TAR archive</title>
<tgroup cols="2">
<thead>
<row>
<entry>Feature</entry>
<entry>File name</entry>
</row>
</thead>
<tbody>
<row>
<entry><parameter>APPARMOR</parameter></entry>
<entry><filename>security-apparmor.txt</filename></entry>
</row>
<row>
<entry><parameter>AUDIT</parameter></entry>
<entry><filename>security-audit.txt</filename></entry>
</row>
<row>
<entry><parameter>AUTOFS</parameter></entry>
<entry><filename>fs-autofs.txt</filename></entry>
</row>
<row>
<entry><parameter>BOOT</parameter></entry>
<entry><filename>boot.txt</filename></entry>
</row>
<row>
<entry><parameter>BTRFS</parameter></entry>
<entry><filename>fs-btrfs.txt</filename></entry>
</row>
<row>
<entry><parameter>DAEMONS</parameter></entry>
<entry><filename>systemd.txt</filename></entry>
</row>
<row>
<entry><parameter>CIMOM</parameter></entry>
<entry><filename>cimom.txt</filename></entry>
</row>
<row>
<entry><parameter>CRASH</parameter></entry>
<entry><filename>crash.txt</filename></entry>
</row>
<row>
<entry><parameter>CRON</parameter></entry>
<entry><filename>cron.txt</filename></entry>
</row>
<row>
<entry><parameter>DHCP</parameter></entry>
<entry><filename>dhcp.txt</filename></entry>
</row>
<row>
<entry><parameter>DISK</parameter></entry>
<entry><filename>fs-diskio.txt</filename></entry>
</row>
<row>
<entry><parameter>DNS</parameter></entry>
<entry><filename>dns.txt</filename></entry>
</row>
<row>
<entry><parameter>DOCKER</parameter></entry>
<entry><filename>docker.txt</filename></entry>
</row>
<row>
<entry><parameter>DRBD</parameter></entry>
<entry><filename>drbd.txt</filename></entry>
</row>
<row>
<entry><parameter>ENV</parameter></entry>
<entry><filename>env.txt</filename></entry>
</row>
<row>
<entry><parameter>ETC</parameter></entry>
<entry><filename>etc.txt</filename></entry>
</row>
<row>
<entry><parameter>HA</parameter></entry>
<entry><filename>ha.txt</filename></entry>
</row>
<row>
<entry><parameter>HAPROXY</parameter></entry>
<entry><filename>haproxy.txt</filename></entry>
</row>
<row>
<entry><parameter>HISTORY</parameter></entry>
<entry><filename>shell_history.txt</filename></entry>
</row>
<row>
<entry><parameter>IB</parameter></entry>
<entry><filename>ib.txt</filename></entry>
</row>
<row>
<entry><parameter>IMAN</parameter></entry>
<entry><filename>novell-iman.txt</filename></entry>
</row>
<row>
<entry><parameter>ISCSI</parameter></entry>
<entry><filename>fs-iscsi.txt</filename></entry>
</row>
<row>
<entry><parameter>LDAP</parameter></entry>
<entry><filename>ldap.txt</filename></entry>
</row>
<row>
<entry><parameter>LIVEPATCH</parameter></entry>
<entry><filename>kernel-livepatch.txt</filename></entry>
</row>
<row>
<entry><parameter>LVM</parameter></entry>
<entry><filename>lvm.txt</filename></entry>
</row>
<row>
<entry><parameter>MEM</parameter></entry>
<entry><filename>memory.txt</filename></entry>
</row>
<row>
<entry><parameter>MOD</parameter></entry>
<entry><filename>modules.txt</filename></entry>
</row>
<row>
<entry><parameter>MPIO</parameter></entry>
<entry><filename>mpio.txt</filename></entry>
</row>
<row>
<entry><parameter>NET</parameter></entry>
<entry><filename>network-*.txt</filename></entry>
</row>
<row>
<entry><parameter>NFS</parameter></entry>
<entry><filename>nfs.txt</filename></entry>
</row>
<row>
<entry><parameter>NTP</parameter></entry>
<entry><filename>ntp.txt</filename></entry>
</row>
<row>
<entry><parameter>NVME</parameter></entry>
<entry><filename>nvme.txt</filename></entry>
</row>
<row>
<entry><parameter>OCFS2</parameter></entry>
<entry><filename>ocfs2.txt</filename></entry>
</row>
<row>
<entry><parameter>OFILES</parameter></entry>
<entry><filename>open-files.txt</filename></entry>
</row>
<row>
<entry><parameter>PRINT</parameter></entry>
<entry><filename>print.txt</filename></entry>
</row>
<row>
<entry><parameter>PROC</parameter></entry>
<entry><filename>proc.txt</filename></entry>
</row>
<row>
<entry><parameter>SAR</parameter></entry>
<entry><filename>sar.txt</filename></entry>
</row>
<row>
<entry><parameter>SLERT</parameter></entry>
<entry><filename>slert.txt</filename></entry>
</row>
<row>
<entry><parameter>SLP</parameter></entry>
<entry><filename>slp.txt</filename></entry>
</row>
<row>
<entry><parameter>SMT</parameter></entry>
<entry><filename>smt.txt</filename></entry>
</row>
<row>
<entry><parameter>SMART</parameter></entry>
<entry><filename>fs-smartmon.txt</filename></entry>
</row>
<row>
<entry><parameter>SMB</parameter></entry>
<entry><filename>samba.txt</filename></entry>
</row>
<row>
<entry><parameter>SRAID</parameter></entry>
<entry><filename>fs-softraid.txt</filename></entry>
</row>
<row>
<entry><parameter>SSH</parameter></entry>
<entry><filename>ssh.txt</filename></entry>
</row>
<row>
<entry><parameter>SSSD</parameter></entry>
<entry><filename>sssd.txt</filename></entry>
</row>
<row>
<entry><parameter>SYSCONFIG</parameter></entry>
<entry><filename>sysconfig.txt</filename></entry>
</row>
<row>
<entry><parameter>SYSFS</parameter></entry>
<entry><filename>sysfs.txt</filename></entry>
</row>
<row>
<entry><parameter>TRANSACTIONAL</parameter></entry>
<entry><filename>transactional-update.txt</filename></entry>
</row>
<row>
<entry><parameter>TUNED</parameter></entry>
<entry><filename>tuned.txt</filename></entry>
</row>
<row>
<entry><parameter>UDEV</parameter></entry>
<entry><filename>udev.txt</filename></entry>
</row>
<row>
<entry><parameter>UFILES</parameter></entry>
<entry><filename>fs-files-additional.txt</filename></entry>
</row>
<row>
<entry><parameter>UP</parameter></entry>
<entry><filename>updates.txt</filename></entry>
</row>
<row>
<entry><parameter>WEB</parameter></entry>
<entry><filename>web.txt</filename></entry>
</row>
<row>
<entry><parameter>X</parameter></entry>
<entry><filename>x.txt</filename></entry>
</row>
</tbody>
</tgroup>
</table>
<remark>toms 2018-04-05: Make the table be aware of what packages brings
what plugin?</remark>
</sect2>
</sect1>
<sect1 xml:id="sec-admsupport-submit">
<title>Submitting information to Global Technical Support</title>
<para>
Use the &yast; <guimenu>Support</guimenu> module or the
<command>supportconfig</command> command line utility to submit system
information to the Global Technical Support. When you experience a server
issue and want the support's assistance, you will need to open a service
request first. For details, see
<xref linkend="sec-admsupport-supportconfig-sr"/>.
</para>
<para>
The following examples use <replaceable>12345678901</replaceable> as a
placeholder for your service request number. Replace
<replaceable>12345678901</replaceable> with the service request number you
created in <xref linkend="sec-admsupport-supportconfig-sr"/>.
</para>
<procedure xml:id="pro-admsupport-submit-yast">
<title>Submitting information to support with &yast;</title>
<para>
The following procedure assumes that you have already created a
Supportconfig archive, but have not uploaded it yet. Make sure to have
included your contact information in the archive as described in
<xref linkend="sec-admsupport-yast"/>,
<xref linkend="st-supportconfig-contact" xrefstyle="select:label nopage"/>.
For instructions on how to generate and submit a Supportconfig archive in
one go, see <xref linkend="sec-admsupport-yast"/>.
</para>
<step>
<para>
Start &yast; and open the <guimenu>Support</guimenu> module.
</para>
</step>
<step>
<para>
Click <guimenu>Upload</guimenu>.
</para>
</step>
<step>
<para>
In <guimenu>Package with log files</guimenu> specify the path to the
existing Supportconfig archive or <guimenu>Browse</guimenu> for it.
</para>
</step>
<step xml:id="st-supportcfg-submit-upltarget">
<para>
&yast; automatically proposes an upload server. To modify it,
refer to <xref linkend="sec-admsupport-supportconfig-upload"/> for details
of which upload servers are available.
</para>
<informalfigure>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="yast2_support_conf_upload.png" width="70%"/>
</imageobject>
<imageobject role="html">
<imagedata fileref="yast2_support_conf_upload.png" width="60%"/>
</imageobject>
</mediaobject>
</informalfigure>
<para>
<remark>taroth 2014-04-11: this does not make sense to me - why does the
YaST module *not* ask for the SR number now? and lets you continue after
specifying an upload target (but no RC or customer info)? I would
expect it to *check* if an SR has been entered and otherwise show an error
message - filed http://bugzilla.suse.com/show_bug.cgi?id=880943 for this, unfortunately it
was rejected for technical reasons</remark>
Proceed with <guimenu>Next</guimenu>.
</para>
</step>
<step>
<para>
Click <guimenu>Finish</guimenu>.
</para>
</step>
</procedure>
<procedure xml:id="pro-admsupport-submit-cli">
<title>Submitting information to support from command line</title>
<para>
The following procedure assumes that you have already created a
Supportconfig archive, but have not uploaded it yet. For instructions on
how to generate and submit a Supportconfig archive in one go, see
<xref linkend="sec-admsupport-yast"/>.
</para>
<step>
<para>
Servers with Internet connectivity:
</para>
<substeps performance="required">
<step>
<para>
To use the default upload target, run:
</para>
<screen>&prompt.sudo;supportconfig -ur <replaceable>12345678901</replaceable></screen>
</step>
<step>
<para>
For the secure upload target, use the following:
</para>
<!--taroth 2014-04-04: bnc#871918-->
<screen>&prompt.sudo;supportconfig -ar <replaceable>12345678901</replaceable></screen>
</step>
</substeps>
</step>
<step>
<para>
Servers <emphasis>without</emphasis> Internet connectivity
</para>
<substeps performance="required">
<step>
<para>
Run the following:
</para>
<screen>&prompt.sudo;supportconfig -r <replaceable>12345678901</replaceable></screen>
</step>
<step>
<para>
Manually upload the
<filename>/var/log/scc_<replaceable>SR12345678901</replaceable>*tbz</filename>
archive to one of our FTP servers. Which one to use depends on your
location in the world. For an overview, see
<xref linkend="sec-admsupport-supportconfig-upload"/>.
</para>
</step>
</substeps>
</step>
<step>
<para>
After the TAR archive arrives in the incoming directory of our FTP server,
it becomes automatically attached to your service request.
</para>
</step>
</procedure>
</sect1>
<!-- taroth 2014-04-24: http://fate.suse.com/315699,
http://bugzilla.suse.com/show_bug.cgi?id=871928-->
<sect1 xml:id="sec-admsupport-sca">
<title>Analyzing system information</title>
<para>
System reports created with <command>supportconfig</command> can be analyzed
for known issues to help resolve problems faster. For this purpose,
&productname; provides both an appliance and a command line tool for
<literal>Supportconfig Analysis</literal> (SCA). The SCA appliance is a
server-side tool which is non-interactive. The SCA tool
(<command>scatool</command> provided by the package
<package>sca-server-report</package>) runs on the client-side and is
executed from command line. Both tools analyze Supportconfig archives from
affected servers. The initial server analysis takes place on the SCA
appliance or the workstation on which <command>scatool</command> is
running. No analysis cycles happen on the production server.
</para>
<para>
Both the appliance and the command line tool additionally need
product-specific patterns that enable them to analyze the Supportconfig
output for the associated products. Each pattern is a script that parses and
evaluates a Supportconfig archive for one known issue. The patterns are
available as RPM packages.
</para>
<para>
You can also develop your own patterns as briefly described in