All of us have faced huge performance related issues. When it comes to Siebel, things can only be called murky! The OOB solution itself puts up a few questions. I say this as per my naive understanding and experience

Sorry for being away from this blog for so long. It’s just that almost all the writers on the panel have really been too occupied with their regular jobs.

Anyways, getting the Siebel server performance out of the way, the next thing that comes to anybody’s mind is to check the performance of the physical Server Box itself. I mean the Server Operating System and the processes that it is running. This is where we can make use of the netstat utility.

netstat, or the Network Statistics as we may call it, is a simple command line utility. When used with proper parameters on the command line, it can be used to monitor:
1) Incoming Network Connections
2) Outgoing Network Connections
3) Network Interface Statistics
4) Some Network Routing information that I could see.

It is available on most of the common Operating Systems like Windows, UNIX, etc.

It is generally used to find Network Problems, and more so to find the Network Usage by the number of open Network Connections, for Performance related measurements. A typical netstat output could look like:

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    <machine_hostname>:1218      <dns_server_name>:8080  CLOSE_WAIT
  TCP    <machine_hostname>:2841     <dns_server_name>:1400  ESTABLISHED
  TCP    <machine_hostname>:4651      localhost:62514        ESTABLISHED
  TCP    <machine_hostname>:5152      localhost:3863         CLOSE_WAIT
  TCP    <machine_hostname>:62514     localhost:4651         ESTABLISHED

  etc..

A simple dos help utility look up revealed the following options to this utility on my Win XP based machine:

Displays protocol statistics and current TCP/IP network connections.

NETSTAT [-a] [-b] [-e] [-n] [-o] [-p proto] [-r] [-s] [-v] [interval]

  -a            Displays all connections and listening ports.
  -b            Displays the executable involved in creating each connection or
                listening port. In some cases well-known executables host
                multiple independent components, and in these cases the
                sequence of components involved in creating the connection
                or listening port is displayed. In this case the executable
                name is in [] at the bottom, on top is the component it called,
                and so forth until TCP/IP was reached. Note that this option
                can be time-consuming and will fail unless you have sufficient
                permissions.
  -e            Displays Ethernet statistics. This may be combined with the -s
                option.
  -n            Displays addresses and port numbers in numerical form.
  -o            Displays the owning process ID associated with each connection.
  -p proto      Shows connections for the protocol specified by proto; proto
                may be any of: TCP, UDP, TCPv6, or UDPv6.  If used with the -s
                option to display per-protocol statistics, proto may be any of:
                IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, or UDPv6.
  -r            Displays the routing table.
  -s            Displays per-protocol statistics.  By default, statistics are
                shown for IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, and UDPv6;
                the -p option may be used to specify a subset of the default.
  -v            When used in conjunction with -b, will display sequence of
                components involved in creating the connection or listening
                port for all executables.
  interval      Redisplays selected statistics, pausing interval seconds
                between each display.  Press CTRL+C to stop redisplaying
                statistics.  If omitted, netstat will print the current
                configuration information once.

Usage Example:

netstat -aon

This utility can be of immense use on analysing server performances where we are quite sure that the server is running slower than nowmal. It could possibly be running some junk tasks from the now defunct softwares that we no longer need.
Try it, and tell me what you see on your PC!

Related posts:

1. Siebel Admin – Gateway Name Server – An overview We discussed about the basic Siebel Server Architecture in our...
2. Siebel Server Architecture – an Introduction You may call this an introductory tutorial. Siebel as we...
3. Siebel Tools hangs when checking out objects Hi, Now this is strange. I had been running into...
4. Siebel Server Verification – EVT Tool Verifying the health of our Siebel Server Environment is the...
5. Siebel – Automatic User Logout Logging out a user automatically, when the user does not...