About Test Server Status

The test servers keep the TAS informed of their operational state. Before performing any action that can affect the operation of the test server, look up the test server... or use the System Status window and check its status:

Ready 0/Z— The test server is currently idle and can accept test or maintenance commands. Where Z is the total number of processes.

NOTE: As or release 16, colors have been added to status. Green = #test sessions = 1, Yellow = #test sessions = 2, Orange = #test sessions > 2

Running [Nr] X/Zr — The test server is currently running one or more tests, where N is the number of test sessions, X is the number of running processes, Z is the total number of processes. An r after the number of test sessions ([Nr]) indicates Port Reservation in use and an r after the number of running processes (Zr) indicates Process Reservation in use. Maintenance activities could disturb the active operations. The TS status also indicates the mode currently running:

Status Indicator	What it means...
RUNNING [2] 1/3	2 test sessions running in unreserved mode on a TS licensed with Performance Accelerator or Extreme License.
RUNNING [3r] 1/3	3 test sessions running in reserved ports mode on a TS licensed with Performance Accelerator or Extreme License.
RUNNING [3r] 2/3r	3 test sessions running on reserved Ports + Processes mode, using 2 processes on a TS licensed with Performance Accelerator or Extreme License.
RUNNING [2] 1/1	2 test sessions running in unreserved mode on standard TS
RUNNING [3r] 1/1	3 test sessions running in reserved ports mode on a standard TS
RUNNING [1r] 1/1r	1 test session running in Reserved Ports + Reserved Processes mode on a standard TS

TROUBLESHOOT: If the status is Running [0], the test server is running a test but the TAS is not controlling the test. In this case you should recycle the test server to abort the test.

Not Ready — The test server is not responsive and cannot accept any commands. This status is normal during an upgrade or when the platform is rebooted after a configuration change. When the status is not ready, it could be due to the following states:
NOT_READY (NO COMM) — The TS is not communicating with the TAS
NOT_READY (NO COMM) — The TS is not communicating with the TAS (TAS-to-TS COMM not confirmed in 30+ seconds is displayed when active check between TAS and Test Server fails to verify connection is available)
NOT_READY (HEARTBEAT) — The TAS will set NOT_READY HEARTBEAT if no response is received within 30 seconds when active check between TAS and Test Server is checked. Note: If tests are running, they will not be aborted and the TS will stay RUNNING.
NOT_READY (NEEDS RECYCLE) — TAS is refusing to accept the status message. The TS must be recycled to force a new registration.
NOT_READY (PARTIAL TS PROCESSES) — User attempted to start a test before all TS processes were READY. For example, TS processes 1 and 2 were registered but 3 and 4 were not before a user attempted to start a test.

TROUBLESHOOT: The test server should be Ready within a minute after the platform has booted. Recycle the test server to restart the software if it has not reached the Ready state in a reasonable amount of time.

If the TS displays a NOT_READY (NO COMM) state, check why your TS is not communicating with the TAS. For example, is the TS disabled, off, in the process of rebooting, recycling, not connected to the network, is the network down, etc.
If the TS displays a NOT_READY (NEEDS RECYCLE) state, recycle your TS, as it states, if that does not fix the state, you may need to re-configure your TS.

NOTE: A TS could go into a NOT_READY (NO COMM) sub-state from the RUNNING state, if the TS stops sending messages to the TAS for any reason, e.g., TS locked up and recycled slowly dumping core.

NEEDS_LICENSE — Current License Assigned to the TS is not valid. Select a proper license from the "License selection available" or contact support for assistance.
NEEDS_UPGRADE — The test server is running, but its software is not compatible with the TAS software. The test server must be upgraded before it can accept test commands.
NOT_SUPPORTED — The test server hardware, OS, or Kernel is not supported. Check against supported list in the release notes. If after correcting and confirming TS is setup per release notes, contact support.
Invalid (see Real-Time Logs) — The TAS is rejecting the registration messages sent by the test server due to invalid IP addresses or masks used by the test server. You can search the Real-Time Logs for messages with the text "Invalid registration message received." The cause for the rejection is explained in the log message.

From the Status window click the icon to access this information "About the Test Server Status."

NOTES:

If a Test Server reports that an Ethernet interface is down, on the Test Server Administration window, the Ethernet interface name will show up in bold-red with a small down-arrow on the left side.
If you try to run a test using an Ethernet interface that is down, you'll get an error indicating that the Ethernet interface is down.
Configuring tests will not be affected by down status.
Running Tests counter now ignores COMPLETED tests.