Conference noted::atm

>>    any plan to add more than one session on Telnet server on G/S ATM ?

I doubt it.  Some management settings are protected against concurrent access
by locks, but I wouldn't be surprised if a lot of the software just <assumes>
there will never be more than one manager.

For that matter, I'm not sure that the software is entirely safe with regards
to simultaneous requests from OBM and SNMP.

    
      ok for one session , but any plans to add to settable timer control
       for telnet connection ?
    
      JYP

    I don't know.  You're the first one who's asked!

    
     may be it's good to be the first !!
    
     could you check if something is possible to add some paremeters
     in next version ?
    
     JYP

Re: Telnet Session.

   As Tom responded switch supports one session, no plans currently to
   add more than one seesion.

re: sorry system is engaged.

   The TCP timer to check in-activity is currently at 20 minutes.  Thus
   if you had a telnet session, and then physically disconnected cable to 
   switch, the local console would be active after 20 minutes.

   Other situations such as the host system still active but process killed
   etc. would remove the telent connection quickly (the remote host responds to
   tcp).

   If you have xterm on a host, and killed the term, the host system is still
   maintaining connection -- "the ps aux"  will show the process.  In this 
   case you would have to kill the process on host which kills the telnet
   connection.

   Could you explain the problem on 2.1.1 :

     Is this as:

       o No Telnet sessions active, the host system did not have a telnet
         connection to GS/ATM.
       o switch upgraded to 2.1.1
       o when telnet attempted to GS/ATM after 2.1.1 loaded, it says
         "sorry this system is engaged"
   
       If the scenario is as above, it is not expected behavior;
   
   Could you check that no telent process to the switch active ?
   Wait for 20 mins, and see if you could telnet. 
   ( Note if the host system is up, and reachable on net with switch, then telnet will maintain 
    connection even if no user activity).

 re: Reducing timers / user control of timer..

   We will look into this.

/Kumar

    
     thanks for your reply,
    
     i don't know how to show or kill a process under WNT or Windows 95
     i'm using MultiChassis manager under it i can do a telnet session
     on G/S , but if i disconnected the cable or exit from Multichassis
     without logoff on G/S then i can obtain  the error message "system
     engaged" when i try to do another telnet connection.
     
     i should be great to have a selectable timer for timeout of telnet
    session...
    
     thanks for your feedback
    
      Jean-Yves

    Don't mean to stick my nose in but surely the telnet session will 
    eventually time out, if one of the hosts disappears.
    
    Steven 
    

In article <[email protected]>, [email protected] (Like a thief in the night) writes:
> Title: Sorry, System Engaged !!
 
>     Don't mean to stick my nose in but surely the telnet session will 
>     eventually time out, if one of the hosts disappears.

There is probably a FAQ entry someplace that covers this.  The buzz-word
is "keep alive".

Consider what happens if the connection is idle.  The only way to
discover that the other end has gone away without telling you is to
send a packet that generates a response - and retransmit until you get
the response or timeout.

Some people think those packets are unreasonable clutter on the network.

Some people want to leave telnet connections open for days.  They will
be mostly idle.  They think it is stupid to close a telnet connection
just because the keep-alive didn't get through because of a temporary
routing flap while the human was off doing something else and the
connection was idle.

Some people want keep-alives so that the system will discover abandoned
connections.  That's the case you are expecting.

[posted by Notes-News gateway]

 thanks all for your comments,

  a selectable timer should be great to bypass this problem or may
  be simultaneous support of 2 telnet sessions too ..

 JYP