Infinistream socket table: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
=== Procedure === | === Procedure === | ||
Log into the Infinistream and launch a localconsole session | ==== Verification ==== | ||
Log into the Infinistream and launch a localconsole session: | |||
<pre># isbin | <pre># isbin | ||
# ./localconsole | # ./localconsole | ||
</pre> | </pre> | ||
Now, enter command-line mode by typing 11 and proceed with the following command | Now, enter command-line mode by typing 11 and proceed with the following command: | ||
<pre>% get dump tables | <pre>% get dump tables | ||
</pre> | </pre> | ||
Search for the lines skt_trans and skt_table. The last column of these lines show if drops were seen. | |||
==== Altering the table configuration ==== | |||
Check the configuration of the socket table: | |||
<pre>% get skt | |||
</pre> | |||
| | ||
| | ||
Revision as of 15:15, 25 January 2023
Summary
In situations that the summary pane of a monitor show data, but drilling down towards the session pane results in "No data available" you might run into overloaded database tables. This article shows how to verify if the Infinistream is suffering from this problem.
Procedure
Verification
Log into the Infinistream and launch a localconsole session:
# isbin # ./localconsole
Now, enter command-line mode by typing 11 and proceed with the following command:
% get dump tables
Search for the lines skt_trans and skt_table. The last column of these lines show if drops were seen.
Altering the table configuration
Check the configuration of the socket table:
% get skt