COMNET III

Chapter 10. Setup Commands
10.6 Setup Counts Report
SETUP COMMANDS: SETUP COUNTS
REPLICATION 1 FROM 0.0 TO 300.0 SECONDS
ORIGIN / SETUP COMMAND NAME:
NUMBER OF SESSIONS
DESTINATION LIST TRIED SETUP RETRY BLOCK DISCON RERTD
_________________________________ _______ _______ _____ _____ _____ _____
Application Workstation / cmd Local Setup:
Application Server 27 25 0 0 0 0
The Setup Counts Report presents summary statistics for setup commands on the number
of attempts to set up a session, the number of attempts that succeeded, the number of retries
to set up a session based upon initial failures, the number of sessions attempted that were
blocked, the number of sessions attempted that were disconnected, and the number of sessions
that were rerouted due to being blocked.
Sessions Tried
Sessions Setup
Sessions Retried
Sessions Blocked
Sessions Disconnected
Sessions Rerouted
The number of attempts to set up a session by the respective setup
command. As the simulation executes, applications which call the session
setup command try to execute it. The attempt to set up a particular session
will succeed or fail depending upon network conditions. For instance,
route availability inside hop and session limits, buffer availability, etc.
The number of session setup attempts which succeeded.
The number of retried sessions. If a setup attempt fails, the session may
be retried later depending on the settings you have entered.
The number of blocked sessions. The session setup attempt may block due
to insufficient buffer space on routing nodes, or no route being available
inside the hop limit, or no route being available because at least 1 link on all
routes is at its session limit, or nodes/links have failed and no route is available.
The number of disconnected sessions. A session in progress may be
disconnected because a node or link through which it is routed fails. The
session may optionally be rerouted if this happens.
The number of sessions rerouted following disconnection.
151