Previous Page

Chapter 4 - Monitoring StreetTalk for Windows NT Software

Introduction

Messages

Logs

StreetTalk Naming Service
StreetTalk Security Service
StreetTalk Directory Assistance Service

Note: You cannot remotely generate a log report for StreetTalk for Windows NT services. Log files must be viewed from the StreetTalk for Windows NT server.

Event Viewer

Successfully started LaserPrinter@IS-NT-14@Servers with the print queue IBM 4019 Laser Printer.

\Device\Vns:UDP server support disabled by config.

Wrapping

Diagnostic Programs

GETARLS.EXE - StreetTalk File utility to store ARLs
GETPROCS.EXE - StreetTalk Communication debugging utility
MANLY.EXE - StreetTalk Mail debugging utility
PUTARLS.EXE - StreetTalk File utility to restore ARLs
STDACLI.EXE - STDA test utility
STANLEY.EXE - StreetTalk database analysis utility
STCLIENT.EXE - StreetTalk client utility
SVCLOG.EXE - Flushes logs and sets the log level in a service
VSANLY.EXE - StreetTalk Security Service test utility
VSCLIENT.EXE - StreetTalk Security Service client test utility
XDA.EXE - STDA data files test utility

The Registry Editor

Check on the configuration of and dependencies for the various services and processes that are necessary for Windows NT to function
Spot incorrect or conflicting entries that prevent services from starting
Give you a view of how Windows NT works and is organized, as well as which services are dependent on others starting in order for them to run.

Control Panel Applets

Devices

Table 4-1. StreetTalk for Windows NT Drivers in Devices Applet

Device Status Startup Description
StreetTalk Communications Started Manual StreetTalk communications driver.
VinesIFS Started Manual VINES Installable File System redirector for Enterprise Client for Windows NT. VinesIFS is installed only if the Enterprise Client for Windows NT is installed

Services

Note: You should always use a Banyan management tool to stop and start StreetTalk for Windows NT services. However, Banyan management tools cannot stop the StreetTalk Naming service, the StreetTalk Server Service, or the StreetTalk Security Service.

StreetTalk Server Service Control of Services

Note: Always use StreetTalk Explorer to stop and start StreetTalk for Windows NT services; do not use the Windows NT Service Control Manager.

Table 4-2. StreetTalk for Windows NT Service in Services Applet

Service Status Startup Notes
StreetTalk Started Automatic If you stop StreetTalk, all other services will not run.
StreetTalk Security Service Started Automatic If you stop the StreetTalk Security Service, all other services will not run.
StreetTalk Server Service Started Automatic If you stop the StreetTalk Server Service, all other services will not run.
StreetTalk Directory Assistance Stopped Disabled When you create and start an STDA service, the StreetTalk Name Collector Service is started. The STDA service and the Name Collector Service should always have the same status.
StreetTalk Name Collector Stopped Disabled The StreetTalk Name Collector service is the back end STDA database program responsible for rebuilding the STDA database. This service is started when you create and start an STDA service. When you stop an STDA service, this service is also stopped.
StreetTalk File Started Automatic After you create and start a StreetTalk for Windows NT file service, you can use StreetTalk Explorer to stop an individual file service. Using the Windows NT Services Manager to stop the StreetTalk File service stops all Banyan file services.
StreetTalk Print Started Automatic After you create and start a StreetTalk for Windows NT print service, you can use StreetTalk Explorer to stop an individual print service. Stopping the Windows NT service stops all Banyan print services.
StreetTalk Intelligent Messaging Stopped Disabled StreetTalk Intelligent Messaging provides mail service for clients. If you create and start the service, the Status and Startup become Started/Automatic.
StreetTalk IMAP Service Stopped Disabled Present only if you install IMS IMAP. If you create and start the service, the Status and Startup become Started/Automatic.
StreetTalk LDAP Service Stopped Disabled Present only if you install LDAP. If you create and start the service, the Status and Startup become Started/Automatic.
StreetTalk Network Management Started Automatic Present only if you install the SNM option.

If the service is started by StreetTalk Server Service, the startup value is changed to Automatic.
If the service is stopped by StreetTalk Server Service, the startup value is changed to manual. If the server is rebooted, the service comes up as Stopped.
If STDA startup values are Automatic, and StreetTalk and the StreetTalk Security Service startup values are Manual, and the server is rebooted, StreetTalk and the StreetTalk Security Service are started because STDA depends on StreetTalk and the Security Service to be running. STDA starts them if these services are not running.

Dependencies

Auto-Restarting Services

Figure 4-1. Server Service Polling Program Dialog Box

Guidelines

Always use a Banyan management tool (for example, StreetTalk Explorer or MSERVICE) to manage StreetTalk for Windows NT file, print, mail, and STDA services.
If you run the Windows NT Service Control Manager to stop and start StreetTalk for Windows NT services (including the StreetTalk Naming service and the StreetTalk Security Service), turn off auto-restart polling first. Windows NT could generate an internal error if StreetTalk Server Service tries to start a service that the Windows NT Service Control Manager is trying to stop.
Only the Windows NT Service Control Manager can stop the StreetTalk Naming service, the StreetTalk Security Service, and the StreetTalk Server Service. These services are "eternal." If you must stop them, the usual practice is to stop the three of them together. If you stop just the StreetTalk Naming service and leave its startup value as Manual, the StreetTalk Server Service tries to start it. If you stop the StreetTalk Naming service, set the startup value to Disabled or turn off auto-restart polling by setting the polling value to 0.

Network

Server

Performance Monitor

Viewing Performance Monitor Statistics

1. Run Performance Monitor from the Administrative Tools program group.

2. From the View menu, select Chart.

3. From the Edit Menu, select Add to Chart or click on the Add counter button.

4. From the Object box, select StreetTalk Communications as the object to be monitored.

5. From the Counter box, select one or more StreetTalk communications counters (for example, Sockets in use, Heap Size, and so on). To display a brief description of the counter, click Explain.

6. Click Add and then click Done to display the chart.

Statistics

Table 4-4. StreetTalk for Windows NT Protocols

Protocol Description
VINES IP VINES Internet Protocol is responsible for moving units of data called packets through the network. This protocol is also responsible for making routing decisions, which involve determining the appropriate paths packets should take to reach their destinations. A path is an interconnected pattern of data links and nodes that connects two nodes in a network.
VINES IPC VINES Interprocess Communications Protocol moves unreliable datagrams and reliable messages between transport layers on different network nodes. IPC handles reliable messages by creating a virtual connection between the IPC protocol entities on the host and destination nodes. IPC on the destination node reassembles reliable messages that consist of multiple packets and sends them to higher level processes in a single unit. IPC acknowledges these messages and guarantees that they are placed in the port queue only once.
VINES RTP VINES Routing Update Protocol distributes network topology information among servers using dynamic routing techniques. Banyan servers maintain and dynamically update a routing database that details the least-cost path for routing packets and uses a routing algorithm to resolve contention between two or more identical-cost links. Store-and-forward routing supports dynamic load balancing of redundant equal-cost paths and automatic re-routing around communication failure points. RTP also uses automatic hot backup paths whenever redundant links are available between two nodes.
VINES SPP VINES Sequenced Packet Protocol supports virtual connections for the transmission of data streams. An SPP virtual connection is an association between two transport layer ports anywhere in the network. In this way, the VINES transport layer handles multiple, simultaneous SPP virtual connections. SPP guarantees that data is delivered only once and in proper sequence.

Table 4-5. StreetTalk for Windows NT Communications Statistics

Counter Description
Sockets in use The total number of configured sockets currently in use. A socket is an object that the transport layer uses to manage the flow of data between processes. Sockets provide an interface between a process and the transport layer protocol entity.
Sockets Maximum Open The largest number of sockets that were in use at any one time since the system was booted (high-water mark).
Sockets Configured The allowable, maximum number of sockets that can be open at one time.
Socket Alloc Failures The number of times that socket allocation attempts failed since the system was last booted.
Heap Used (%) The percentage of the total communications heap size currently in use. Each packet coming into or going out of the system results in buffer usage. As soon as the system processes the packet, it releases the buffer. Since all packets are not the same size, the space that is allocated and released varies in size. Certain conditions, such as LAN noise or heavy traffic, can make buffer use jump quickly into the 90% range or higher but the percentage depends on the total heap size configured. Communications buffers that are requested, but cannot be allocated, result in drops. Communications buffer use between 20% and 35% is typical of a system that is fully loaded and very busy, but healthy. If use is 50% or more, the system may not be able to handle peak loads or transient network errors without causing drops and performance degradation.
Heap Size (KB) The amount (in kilobytes) of system memory used for network communications. You can set the total communications heap size from the Network Setup icon.
Heap Alloc Failures The number of heap allocation attempts that failed since the system was last booted. Any non-zero number indicates a possible failure to perform some network operation. If the value is non-zero, increase the heap size.
IPC Sends Total number of IPC messages sent from this system
IPC Send Errors Total number of attempts to send IPC messages that failed due to an error.
IPC Receives Total number of IPC messages received on this system.
IPC Receive Errors Total number of received IPC messages that could not be processed due to an error.
IPC Bytes Sent /sec Number of IPC bytes sent per second.
IPC Bytes Received /sec Number of IPC bytes received per second.
RTP Sends Number of RTP messages sent from this system.
RTP Receives Number of RTP messages received on this system.
RTP Updates Sent Number of update packets sent. An update can consist of one or more update packets. Just the update itself is counted, not the number of packets sent.
RTP Updates Rcvd Number of RTP update packets received. An update can consist of one or more update packets. The total number of update packets received is counted.
RTP Responses Sent Number of RTP responses sent. A response can consist of one or more update packets. Just the response itself is counted, not the number of packets sent.
RTP Responses Rcvd The number of RTP responses received. A response can consist of one or more update packets (5.5x and greater and StreetTalk for Windows NT systems) or one or more response packets (5.0x). The total number of packets received is counted.
SPP Sends Total number of SPP messages sent.
SPP Send Errors Total number of attempts to send SPP messages that failed.
SPP Receives Total number of SPP messages received on this system.
SPP Receive Errors Total number of attempts to receive SPP messages that could not be processed due to an error.
SPP Bytes Sent /sec Number of SPP bytes sent per second.
SPP Bytes Received /sec Number of SPP bytes received per second.
SPP Connections in use Current number of SPP connections in use.
SPP Max Connects The maximum number of SPP connections that were in use at one time since the system was last booted.
SPP Connections Configured The allowable maximum number of SPP connections that can be in use by processes on the system at one time. This value is set from the Network Setup icon.
SPP Disconnects Rcvd Total number of disconnect packets received. When one end of an SPP connection wants to terminate the connection, it sends a disconnect packet to the other end.
SPP Disconnects Sent Total number of disconnect packets sent. When one end of an SPP connection wants to terminate the connection, it sends a disconnect packet to the other end.
SPP Probes Rcvd Total number of probe packets received. When one end of an SPP connection misses a packet, it sends a probe packet to the other end of the connection. The other end of the connection then retransmits the missed packet along with all other packets sent after it.
SPP Probes Sent Total number of probe packets sent. When one end of an SPP connection misses a packet, it sends a probe packet to the other end of the connection. The other end of the connection then retransmits the missed packet along with all other packets sent after it.
VIP Sends Total number of packets sent over VINES IP. VIP Sends include IPC, RTP and ICP packets, packets routed from other systems, and broadcast packets.
VIP Send Errors Total number of attempts to send VIP packets that failed due to an error.
VIP Receives Total number of packets received over VINES IP. VIP Receives include IPC, SPP, RTP, and ICP packets, packets routed from other systems, and broadcast packets.
VIP Receive Errors Total number of packets received over VIP that could not be processed due to an error.
VIP Bytes Sent /sec Number of VIP bytes sent per second.
VIP Bytes Received /sec Number of VIP bytes received per second.
VIP Routed Packets Total received packets routed to another node
VIP Broadcast Packets Number of broadcast packets that the system has sent, received, and routed. The system sends broadcast packets to perform various functions that range from routing table updates to StreetTalk updates. Client workstations issue broadcasts to perform various functions, such as finding a VINES Files service or an STDA service. The system will receive or route workstation broadcasts, as well as broadcasts from other servers.

Changing Communications Settings

Note: You must reboot the StreetTalk for Windows NT server whenever you change communications settings. If you do not reboot, the new setting does not take effect.

SPP Connections

Increasing Heap Size

An Empirical Estimate

   MAX Concurrent SPP Connections X 100
+ MAX Concurrent Open Sockets X 100
------------------------------------------------------------------
= TOTAL Bytes Added to Communications Buffer

(400 X 100) + (250 X 100) = 65,000 (65 KB)

Previous PageTop Of Page