Disconnecting CLI User Sessions
To forcibly disconnect a CLI user session from the Solace PubSub+ event broker, and thereby allow access to the event broker for other CLI users, enter the following command:
solace# disconnect sessionid <session-id>
Where:
<session-id> is the integer value that correlates to an existing session number, as displayed by the show session User EXEC command. The session id identifies which session to disconnect. The valid range is 1 to 8 (corresponding to up to eight active CLI user sessions).
A CLI user cannot disconnect their own sessions—a disconnect command that specifies the current session is ignored.
Example:
solace> show session Session User From Login Idle Timeout -------- ------- ---------------- ------------------- --------------- -------- 1 admin 192.168.1.246 2013-06-25 13:43:48 0d 5h 2m 0s 0 * 2 test12 192.168.1.133 2013-06-25 20:10:55 0d 0h 0m 1s 5 * indicates current session solace> enable solace# disconnect sessionid 2
When Session 2is disconnected, the following message is displayed to User test12:
Exiting due to disconnect from solace1, session 2, from 192.168.1.133
Up to eight active CLI user sessions are allowed at one time. If there are no free CLI user sessions when you attempt to log on, then the disconnect Privileged EXEC command cannot be used because no other SSH clients can log in to the SSH server. The log on fails and the error message Max CLI sessions are already active is returned.
If this occurs, use the SSH command parameter force to override and disconnect the most idle CLI user session (for example, ssh soladmin@solace1 force). However, using the SSH force option only disconnects the most idle CLI user. You then have to log on a second time without the SSH force option to occupy the free CLI user session. Also, using the SSH force option does not force any user session out if there are free CLI sessions available.