Discussion Groups

We faced similar issue earlier too.....looks like sessions created are not getting terminated.

Looking frward to response on this one.

Hello there,

Are users rebooting the terminals while logged in to the application?  Can you make sure to have the following parameters set on the controller.

ANSI>>Emulation Options>>

Maximum Sessions per Terminal: 1      (default is set to 4)

Close Host sessions on Terminal reset: Enable     (default is disabled)

Thanks,

Ed

Hi All

To elaborate on Ed's response

Maximum Sessions per Terminal: 1      (default is set to 4)  -  It is possible that if a session key is used that up to 4 sessions per terminal number could be created. This setting will limit sessions the controller to 1 session only

In additon changing the commserver value for " TCP Session Request Key " from 1 (the a key) to 0 to disable it will prevent a user from accidentaly getting a TCP session.

Close Host sessions on Terminal reset: Enable     (default is disabled)   -  With this enabled every time a hard init is recieved by the controller the session will be terminated.  So this should be used with caution as it could cause unexpected session termination. 

Regards

David

Hello,

Further to the reply from Ed,

1. Number of Active Terminal Session on 9510 Controller
2. Total Number of Session on 9510 Controller
3. Total Number of incoming request which are coming from the Handheld devices From DOS on the 9510, run the command "netstat -a -n" and look under the "Local Address" column for connections to the 9500 controller on port 9999
4. Total Active Session partnership in between Telnet Server and 9510 Controller. From DOS on the 9510, run the command "netstat -a -n" and look under the "Foreign Address" column for connections to the telnet server IP address on the port that it is listening on (23 usually) 

Here is an example: 

Active Connections 

  Proto  Local Address          Foreign Address        State

 TCP    10.65.3.217:1203       10.65.3.226:23         ESTABLISHED
 TCP    10.65.3.217:1204       10.65.3.226:23         ESTABLISHED
 TCP    10.65.3.217:3389       10.65.3.52:4153        ESTABLISHED
 TCP    10.65.3.217:9999       10.65.3.31:1047        ESTABLISHED
 TCP    10.65.3.217:9999       10.65.3.236:49152      ESTABLISHED

 The controller is 10.65.3.217  You can see that I have two terminals, 10.65.3.52 and 10.65.3.31 connected to it. You can also see the two sessions from the controller to the ANSI machine, 10.65.3.226. 

Regards,

Lawrence

Hi Vinay

Limiting the session per terminal number to 1 may resolve this issue however Ed has also opened ticket 186696 to work with you directly.

Regards

David

Hi All,

Thanks for your quick response on this.

We had checked the netstat Command on the communication server front while after executing the same on primary – Active Controller, its showing the aprox 200 sessions and if we are checking the current sessions it’s showing the same session number on the telnet server as well.

(10.1.15.100: is an Alias IP of Communication Server while the 10.1.1.18 is the Telnet Server used by end customer)

“Kindly let us know how we can filter the logs -  Number of sessions managed by the 9510 Controller respect to running Terminal Numbers configured on TEKTERM CLIENT, the above information is only showing the terminal number session in between Communication Server & Telnet Client,  we are not getting the Client IP or Terminal Number information here  ”

Maximum Sessions per Terminal: 1      (default is set to 4)  -  It is possible that if a session key is used that up to 4 sessions per terminal number could be created. This setting will limit sessions the controller to 1 session only

If we are changing the Session Per Terminal Value (1 to 4) means accordingly communication server is creating the session per terminal on Telnet e.g.

(If the Session per Terminal Value is 2 and we are running 4 TekTerm Client means on TELNET SERVER we will get 8 Active Session… Kindly Confirm)

Regards

Shobhit Kr Singh

Shobhit Kr Singh

“Kindly let us know how we can filter the logs -  Number of sessions managed by the 9510 Controller respect to running Terminal Numbers configured on TEKTERM CLIENT, the above information is only showing the terminal number session in between Communication Server & Telnet Client,  we are not getting the Client IP or Terminal Number information here  ”

Hi Shobhit,

Using "bcm tsts" will show you this information

See this post for a detailed description of the output

Regards,

Lawrence - AHD

Hi Everyone,

Thanks for sharing the relevent information.

We are getting the logs in Raw Data Format on Hyper-terminal, the information is not filter as per the correct schema to read.

We are running 400+ Handheld devices and if we are checking the state of  all devices running on-site, the devices state is coming on RAW DATA with bulk information.

Kindlly let us know the debug command to retrieve the all active/de-active session information respect to terminal number configured on the TEKTERM Client in tabular format or view pane format for easy understanding and analyzing.

Regards

Shobhit Kr Singh

Hello Shobhit

Please refer to the direct response sent to you on ticket 186696.  It will be more beneficial if we work this issue with you directly through the Help Desk

Regards

David