All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
Hello,
We have been using telnet redirection for a while now.
The problem we are trying to address by implementing this will come
clear as you read this but mostly we were trying to address a performance issue
(i.e. load balancing users).
First of all there is something background explanation needed. When a
PC connects to Meditech there are 2 things to keep in mind:
1. The workstation IP address (or DNS name) in the workstation
setup will connect you to the Meditech server indicated.
2. The OPS device setup entry which dictates which server you are
to use is which server will service your requests.
Once you are logged into Meditech, we all know that Meditech will
connect you to other Meditech servers as needed and your master session (see 2
above) will switch from master to slave as your machine focus changes to
different segments.
Now the above may sound simple but it can have dire implications for
performance if the following caveats are not kept in mind.
1. The IP defined in the workstation will ALWAYS be the machine
your workstation connects to - it does not move to the Meditech machine you are
currently working on.
2. The OPS device setup server will ALWAYS be the machine that is
your main server - it does not move to the Meditech machine you are currently
working on.
What that means is as follows:
1. The machine that your workstation connects is the ONLY machine
that can talk with your PC. All Data goes out that server's NIC.
2. The machine that has your master session is the only one that
can talk to the other segments and is your way out of the Meditech system
(before it goes to the workstation connector).
And is best described by an example.
- Lets say that you have your workstation defined to communicate
with machine A.
- Lets further say that you have your OPS device session setup to
the B machine.
- Lets further say that you work in the LAB, which is on the D
machine.
This means that the information has to travel from the D machine to the
B machine and then to the A machine before it gets back to your machine. You
are now involving 3 (THREE!!!) meditech servers to do your work and each takes
a small performance hit processing your Ethernet data. Multiply this by
thousands of users and you have a serious problem.
The answer therefore is simple. Ensure that all your users are
connecting to the proper machines and have the proper segments setup - ideally
they all match and your users use that Meditech machine only.
Sound easy? well, we found that the workstation setup and segment setup easily
diverge as instructions are forgotten or skipped. While you can't solve the
issue with users running apps and switching focus after they are logged in you
can ensure that, as much as possible, the workstation and segment match.
That is where telnet redirection comes in. it will ensure that the two
match by actually modifying the workstation machine connect parameters to match
what the OPS entries say. Thereby eliminating a large part of the possible data
flow problems and therefore performance problems.
So Telnet redirection is a good thing. (unless you already have a good
system in place where you ensure that the workstation and ops entry match).
To turn it on is easy but I would follow the steps next as they ensure
a smooth transition while allowing you to test it. The main item to keep in
mind is that a * (star) in the segment field in the OPS device setup will cause
the telnet redirect to ignore that entry. We therefore converted all of our OPS
entries first to have the *. Then we enabled telnet redirect. Then we tested it
so we understood it and then we started to convert other PC's to segments we
needed them to be on.
We did have to change a few registry keys (as we have our machines
locked down) but in the end it works very well. If someone logs onto a machine
that has the workstation settings set wrong, it will modify them.
Please note that there is a message that pops up when it goes to change
the workstation that requires you to restart the workstation but that only
happens when it changes it, for most users only once.
I hope that makes sense and if you have any more questions please do not
hesitate to ask.
Gary Gevaert
Senior Technical Analyst
Niagara Health System - Shaver Site
DataCentre Building
541 Glenridge Avenue
St. Catharines, Ontario L2T 4C2
www.niagarahealth.on.ca
Please Note New number !
905-378-4647
Extension 44806
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bingham, Jim
Sent: March 20,2006 11:46 AM
To: [EMAIL PROTECTED]
Subject: [MEDITECH-L] Telnet Redirection:
All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
Has anyone Enabled Telnet Redirection? If so, what exactly happened on
the users end?
Thanks
Jim Bingham
Network Administrator
Anne Arundel Medical Center
W-443-481-5206
mailto:[EMAIL PROTECTED]
----------------------------------------------------------------------
This message [including any attachments] contains information intended for a
specific individual[s] and purpose that may be confidential or otherwise
legally protected from disclosure. Any review, use, distribution, disclosure of
contents, or copying of the message is strictly prohibited. If you have
received this transmission in error, please reply to the sender indicating this
error and delete the transmission from your system immediately without copying
or disclosing the information.
_______________________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l
Confidentiality Notice: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
_______________________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l
