[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

2688.0. "TSAM and Emulex" by MEHR::MEHR () Fri Apr 03 1992 19:36

    
	. From note 1298 it seems that TSAM will not manage the Emulex 
	  terminal servers (or Xyplex). Please verify.


	. Management of Emulex by  TSM  was NOT supported, but it worked!
	  Would TSAM be a similar case? 
	  If not, could you please explain why, and how does it work 
	  differently from TSM (use of MOP, etc)?
	  
	. If "it might work but not supported" or "it works partially" is
    	  the answer;  has anyone seen/tested TSAM  with Emulex on any of 
    	  the Field Test site, and what are the observations?

	
	. In V1.1, it is possible to  register the Emulex Terminal Servers 
	  as Ethernet stations (what our customer has chosen to do for now). 
	  However, the server only responds to a "SHOW Characteristics"  
	  request but not "SHOW Counters" request. This is okay for now!
	  But the server is intermittently unreachable via DECmcc, when it is 
	  reachable by TSM. Has anyone seen this problem with Ethernet-AM and 
	  Emulex?? 


	. If Emulex was going to support SNMP, (I don't believe they do today, 
	  but is planned for future. Any info?)   what  would  be  a good 
	  attribute to alarm on  for reachability?
	
	  For that matter, with TSAM (not having used TSAM yet) what is a good 
	  attribute to alarm on when the goal is to monitor the reachability 
    	  of Digital Terminal Servers?
	  

Thanks,
Mahnaz

T.R Title User Personal
Name Date Lines

2688.1 Another bucket of cold water :-) TOOK::FONSECA I heard it through the Grapevine... Sun Apr 05 1992 20:12 60

T.R	Title	User	Personal Name	Date	Lines
2688.1	Another bucket of cold water :-)	TOOK::FONSECA	I heard it through the Grapevine...	`Sun Apr 05 1992 20:12`	60
	Mahnaz- I'm sure you are looking for real world info on this, and I don't want to discourage that, if there are TSAM field test sites who have had luck with foreign terminal servers I'd like to hear about it too. Speaking as the one who works on the TSAM code though, this is very unlikely. I have not ever tried, so I can not say for sure. A small experiment on you part will put the nail in the coffin though: execute the SHOW SERVER command on the terminal server in question. If you do not see the string "DECserver" followed by a legitimate digital terminal server model number, this terminal server will not be TSAM-compatible. � . Management of Emulex by TSM was NOT supported, but it worked! � Would TSAM be a similar case? � If not, could you please explain why, and how does it work � differently from TSM (use of MOP, etc)? This was an infinitly easier situation to have an unsupported interface work. Here all that had to match was a single MOP-id number. For TSAM, 50 to 100 screens of ascii text must match exactly. I hope the above thought experiment makes clear why TSAM will probably not support foriegn terminal servers. The above command is executed by TSAM every time a TSAM command is executed. Although this may sound like we went out of our way to be exclusionary, even in this small experiment, you can see that for us to find out what model of terminal server we are talking to so that we can issue the right form of commands to it, we had to look for the string "DECserver", that is the best marker for our code to find the model number. � . In V1.1, it is possible to register the Emulex Terminal Servers � as Ethernet stations (what our customer has chosen to do for now). � However, the server only responds to a "SHOW Characteristics" � request but not "SHOW Counters" request. This is okay for now! � But the server is intermittently unreachable via DECmcc, when it is � reachable by TSM. Has anyone seen this problem with Ethernet-AM and � Emulex?? Were you connected to the terminal server with TSM at the same moment that the Ethernet-AM failed to reach the server? The two use the same method to attach to the server, only one connection at a time is possible. (Even two TSM users can not connect to the same server simultaneusly.) � For that matter, with TSAM (not having used TSAM yet) what is a good � attribute to alarm on when the goal is to monitor the reachability � of Digital Terminal Servers? I plan on including a small section on this in the user's manual (or failing that, in the release notes.) Since I don't know the answer myself yet, I can not answer you here. Our writer just had a baby girl last week (congrats Rich!) so that is why I am uncertain where this info will end up. Regards, Dave

Mahnaz-

I'm sure you are looking for real world info on this, and I
don't want to discourage that, if there are TSAM field test sites
who have had luck with foreign terminal servers I'd like to
hear about it too.

Speaking as the one who works on the TSAM code though, this is
very unlikely.  I have not ever tried, so I can not say for sure.
A small experiment on you part will put the nail in the coffin though:
execute the SHOW SERVER command on the terminal server in question.
If you do not see the string "DECserver" followed by a legitimate
digital terminal server model number, this terminal server will
not be TSAM-compatible.
    
�	. Management of Emulex by  TSM  was NOT supported, but it worked!
�	  Would TSAM be a similar case? 
�	  If not, could you please explain why, and how does it work 
�	  differently from TSM (use of MOP, etc)?

This was an infinitly easier situation to have an unsupported interface
work.  Here all that had to match was a single MOP-id number.
For TSAM, 50 to 100 screens of ascii text must match exactly.

I hope the above thought experiment makes clear why TSAM will probably
not support foriegn terminal servers.  The above command is executed
by TSAM every time a TSAM command is executed.  Although this may sound
like we went out of our way to be exclusionary, even in this small
experiment, you can see that for us to find out what model of terminal
server we are talking to so that we can issue the right form of commands
to it, we had to look for the string "DECserver", that is the best marker for 
our code to find the model number.
	  
	
�	. In V1.1, it is possible to  register the Emulex Terminal Servers 
�	  as Ethernet stations (what our customer has chosen to do for now). 
�	  However, the server only responds to a "SHOW Characteristics"  
�	  request but not "SHOW Counters" request. This is okay for now!
�	  But the server is intermittently unreachable via DECmcc, when it is 
�	  reachable by TSM. Has anyone seen this problem with Ethernet-AM and 
�	  Emulex?? 

Were you connected to the terminal server with TSM at the same moment that
the Ethernet-AM failed to reach the server?  The two use the same method to
attach to the server, only one connection at a time is possible.  (Even
two TSM users can not connect to the same server simultaneusly.)


�	  For that matter, with TSAM (not having used TSAM yet) what is a good 
�	  attribute to alarm on when the goal is to monitor the reachability 
�    	  of Digital Terminal Servers?

I plan on including a small section on this in the user's manual (or failing
that, in the release notes.)  Since I don't know the answer myself yet,
I can not answer you here.  Our writer just had a baby girl last week
(congrats Rich!) so that is why I am uncertain where this info will end up.

Regards,

Dave