COMNET III
COMNET III
COMNET III
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 12. Global Setup Commands<br />
12.6 Setup Counts Report<br />
GLOBAL SETUP COMMANDS: SETUP COUNTS<br />
The Setup Counts Report presents summary statistics for global setup commands on the<br />
number of attempts to set up a session, the number of attempts that succeeded, the number<br />
of retries to set up a session based upon initial failures, the number of sessions attempted<br />
that were blocked, the number of sessions attempted that were disconnected, and the number<br />
of sessions that were rerouted due to being blocked.<br />
Sessions Tried<br />
Sessions Setup<br />
Sessions Retried<br />
Sessions Blocked<br />
Sessions Disconnected<br />
Sessions Rerouted<br />
REPLICATION 1 FROM 0.0 TO 300.0 SECONDS<br />
ORIGIN / SETUP COMMAND NAME:<br />
NUMBER OF SESSIONS<br />
DESTINATION LIST TRIED SETUP RETRY BLOCK DISCON RERTD<br />
_________________________________ _______ _______ _____ _____ _____ _____<br />
Application Workstation / src:<br />
Application Request / cmd Global Setup:<br />
Application Server 16 16 0 0 0 0<br />
The number of attempts to set up a session by respective setup command.<br />
As the simulation executes, applications which call the global session<br />
setup command are scheduled and try to execute the command. The<br />
attempt to set up a particular session will succeed or fail depending upon<br />
network conditions such as route availability inside hop and session limits,<br />
buffer availability, etc.<br />
The number of session setup attempts that succeeded.<br />
The number of sessions retried. If a setup attempt fails, the session may<br />
be retried later depending on the settings you have entered.<br />
The number of sessions blocked. The session setup attempt may block due<br />
to insufficient buffer space on routing nodes, or no route being available<br />
inside the hop limit, or no route being available because at least 1 link on all<br />
routes is at its session limit, or nodes/links have failed and no route is available.<br />
The number of disconnected sessions. A session in progress may be<br />
disconnected because a node or link through which it is routed fails. The<br />
session may optionally be rerouted, if this happens.<br />
The number of sessions rerouted following disconnection.<br />
181
Change language