Advanced Administration - Troubleshooting - Tech

Information Management
Advanced Administration
InfoSphere Guardium Technical Document
Contents
1.OVERVIEW..........................................................................................................3
2.TECH DOC OBJECTIVES..................................................................................3

2.1Preparation Steps...........................................................................................4
2.2Debug S-TAP Log...........................................................................................5
2.3Debug Collector (CLI Window).......................................................................9
2.4Debug Collector (Web GUI)..........................................................................13
2
1. Overview
This Tech Doc will help the adminitrator the usage of some of the most important tools in
Infosphere Guardium to perform debugging and troubleshooting of its main components:
the S-TAP agent and the Collector appliance.
2. Tech Doc Objectives

This guide is divided in four sections that will cover the troubleshooting of each part of
the connection between the S-TAP agent and the Collector appliance.
3
2.1 Preparation Steps
1. In order to be able to manually stop and restart the S-TAP agent in the Dataserver
VM for the demo, you need to verify that the lines utap (s-tap) and gvsr (supervisor)
exist in the /etc/inittab file (use vi editor as Root user to add them if needed).
2. Verify there is network connectivity between the Dataserver and the Collector VMs
by executing the following commands:
◦ Ping Collector by 5 attempts: ping 10.10.9.248 -c5
◦ Verify there is a connection in port 16016: netstat -an | grep 16016
◦ Telnet test: telnet 10.10.9.248 16016
◦
4
2.2 Debug S-TAP Log
1. Edit the file /usr/local/guardium/modules/STAP/current/guard_tap.ini (use vi
editor as Root user).
2. Change the parameter tap_debug_output level from 0 to 4 and save the file .
3. Open another Xterm window and set the log mode to display the output of S-TAP in
file /tmp/guard_stap.stderr.txt by executing the following command:
◦ tail -f /tmp/guard_stap.stderr.txt
4. Stop both daemons S-TAP (utap) and SUPERVISOR (gsvr), comment both lines
with a # character at the beginning of each line in /etc/inittab file. (use vi editor as Root
user).
5. Save the /etc/inittab file and stop both daemons by executing the command
◦ init q.
5
6. Make sure that both daemons are down and no process is returned, execute the
command:
◦ ps -ef | grep -e stap -e supervisor.
7. Uncomment both lines (utap and gsvr) again in the /etc/inittab file.
8. Save the changes and restart both daemons by executing the command
◦ init q.
9. Go back to the Xterm window with the output of S-TAP and verify that the
process/daemon is starting in the log.
6
10. Open a new Xterm window and connect to db2 by issuing some SQL statements:
◦ db2 connect to ORD_IP user guard using password
◦ db2 "SELECT count(*) FROM SHIP_TO"
11. Verify the SQL statement appears in the Xterm window in the S-TAP output log.
12. Change the parameter tap_debug_output level back from 4 to 0 and save the file
/usr/local/guardium/modules/STAP/current/guard_tap.ini (use vi editor as Root
user)
7
13. Stop both daemons S-TAP (utap) and SUPERVISOR (gsvr), comment both lines
with a # character at the beginning of each line in /etc/inittab file.
14. Save the changes and stop both daemons by executing the command
◦ init q.
15. Make sure that both daemons are down and no process is returned, execute the
command:
◦ ps -ef | grep -e stap -e supervisor.
16. Uncomment both lines again in the /etc/inittab file.
17. Save the changes and restart both daemons by executing the command
◦ init q.
8
2.3 Debug Collector (CLI Window)
1. Establish a console connection to the Collector VM and execute the IPTraf tool.
2. In the IPTraf menu, choose Detailed Interface Statistics.
3. Verify that there is incoming traffic from the Dataserver VM into the Collector VM.
9
4. Exit the IPTraf tool after you are sure that there is data being received into the
Collector.
5. In the same CLI session, now execute the DIAG tool.
6. In the DIAG main menu, choose System Interactive Queries.
7. In the Interactive Queries menu, choose SLON Utility.
10
8. The SLON utility will analyze data packages based on some parameters.
If sending SLON to the R&D for support purposes, make sure start a new database
session otherwise the SLON is going to be worthless.
9. Enter all the parameters required by the SLON Utility.
10. Start the SLON Utility to start gathering and analyzing data packages arriving from
the Dataserver VM.
11. While the SLON Utility is running, go to the Dataserver VM and open a new Xterm
window, connect to db2 and issue some SQL statements:
◦ db2 connect to ORD_IP user guard using password
◦ db2 "SELECT count(*) FROM SHIP_TO"
11
12. Once the SLON Utility finishes, you are presented with a message to export and
package all the output log files.
13. To export and package the output files, without exiting the DIAG tool, go back to the
main menu options and choose Output Management.
14. In the Option Management menu, choose End and Pack Current Session.
15. Exit the DIAG tool menu and execute the FILESERVER utility.
12
2.4 Debug Collector (Web GUI)
1. Open a web browser window, enter the url http://10.10.9.248/ and select the option
Sqlguard Logs.
2. In the files list, look for the compressed SLON Utility output log file and download it,
the name would be something like /diag/depot/diag_session_6_4_1201.tgz.
3. Inside the compressed file there is the output file named apks.txt<DATE in format
DD-MONTH-YYYY_HH.MM.SS> that shows the content of the packages captured and
analyzed by the SLON Utility (In this demo, the SQL statements executed before)
13
4. Open a firefox session and login with user poc.
5. Finally, the confirmation that the SQL statement has arrived to the Collector can be
reviewed in the SQL Trace report.
14
© Copyright IBM Corporation 2011
© Copyright IBM Corporation 2011

All Rights Reserved.
IBM Canada
8200 Warden Avenue
Markham, ON
L6G 1C7
Canada
IBM, the IBM logo, ibm.com and Tivoli are trademarks or

registered trademarks of International Business Machines
Corporation in the United States, other countries, or both. If
these and other IBM trademarked terms are marked on their
first occurrence in this information with a trademark symbol
(® or ™), these symbols indicate U.S. registered or common
law trademarks owned by IBM at the time this information
was published. Such trademarks may also be registered or
common law trademarks in other countries. A current list of
IBM trademarks is available on the Web at “Copyright and
trademark information” at ibm.com/legal/copytrade.shtml
Other company, product and service names may be

trademarks or service marks of others.
References in this publication to IBM products and services

do not imply that IBM intends to make them available in all
countries in which IBM operates.
No part of this document may be reproduced or transmitted

in any form without written permission from IBM
Corporation.
Product data has been reviewed for accuracy as of the date

of initial publication. Product data is subject to change
15
without notice. Any statements regarding IBM’s future
direction and intent are subject to change or withdrawal
without notice, and represent goals and objectives only.
THE INFORMATION PROVIDED IN THIS DOCUMENT IS

DISTRIBUTED “AS IS” WITHOUT ANY WARRANTY,
EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY
DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NON-
INFRINGEMENT.
IBM products are warranted according to the terms and

conditions of the agreements (e.g. IBM Customer
Agreement, Statement of Limited Warranty, International
Program License Agreement, etc.) under which they are
provided.
16

Advanced Administration - Troubleshooting - Tech

Uploaded by

Copyright:

Available Formats

Advanced Administration - Troubleshooting - Tech

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Advanced Administration - Troubleshooting - Tech

Uploaded by

Copyright:

Available Formats

Information Management

2.TECH DOC OBJECTIVES..................................................................................3

2. Tech Doc Objectives

16. Uncomment both lines again in the /etc/inittab file.

2. In the IPTraf menu, choose Detailed Interface Statistics.

5. In the same CLI session, now execute the DIAG tool.

6. In the DIAG main menu, choose System Interactive Queries.

7. In the Interactive Queries menu, choose SLON Utility.

9. Enter all the parameters required by the SLON Utility.

© Copyright IBM Corporation 2011

IBM, the IBM logo, ibm.com and Tivoli are trademarks or

Other company, product and service names may be

References in this publication to IBM products and services

No part of this document may be reproduced or transmitted

Product data has been reviewed for accuracy as of the date

THE INFORMATION PROVIDED IN THIS DOCUMENT IS

IBM products are warranted according to the terms and

You might also like