| Author |
Message |
Quiggley
Guest
|
 Posted:
Fri Apr 15, 2005 1:46 pm Post subject:
Links and Connection |
|
|
I have HIS2004 running on Win2003 server. It is being migrated here from NT
and SNA4.
Question is, am I supposed to have a link for every connection or should I
be able to use just a link for each NIC and point multiple connections to it?
If multiple is there a limit as to how many connections can point to a link? |
|
| Back to top |
|
 |
Charles Ezzell (MSFT)
Guest
|
| Posted:
Fri Apr 15, 2005 7:07 pm Post subject:
Re: Links and Connection |
|
|
You can have one link per connection if you want, but with the caveat that
if there is a problem with the link service, you would need to stop and
restart everything in order to "fix" it. Each connection would use different
SAP parings.
You can also have multiple links. Each link service uses ~3megs of memory,
so this needs to be taken into account.
Personally, depending on the number of connections you have, available
memory, etc, I would break things down into something manageable. IE - don't
put 15 connections onto one link service, as then you loose 15 connections
if the link service hiccups. Say do around 3-5 per link service.
That is my personal opinion, is provided "AS IS" with no warranties, and
confers no rights.
Charles
"Quiggley" <Quiggley@discussions.microsoft.com> wrote in message
news:B4848135-F229-4A27-B0E0-7C8DD8B59F1A@microsoft.com...
| Quote: | I have HIS2004 running on Win2003 server. It is being migrated here from
NT
and SNA4.
Question is, am I supposed to have a link for every connection or should I
be able to use just a link for each NIC and point multiple connections to
it?
If multiple is there a limit as to how many connections can point to a
link? |
|
|
| Back to top |
|
|
Neil Pike
Guest
|
| Posted:
Mon Apr 18, 2005 1:29 pm Post subject:
Re: Links and Connection |
|
|
Quiggley,
On DLC connections I always do a single link service (per nic) and multiple
connections. I don't recall ever having to bounce the DLC link service to fix
anything - max connections per link I have is about 12.
| Quote: | I have HIS2004 running on Win2003 server. It is being migrated here from NT
and SNA4.
Question is, am I supposed to have a link for every connection or should I
be able to use just a link for each NIC and point multiple connections to it?
If multiple is there a limit as to how many connections can point to a link?
|
Neil Pike. Protech Computing Ltd |
|
| Back to top |
|
|
Charles Ezzell (MSFT)
Guest
|
| Posted:
Wed Apr 20, 2005 4:51 am Post subject:
Re: Links and Connection |
|
|
Neil,
I just remember from a few years ago having to break the news to a customer
at 11:30pm on New Years Eve that he was going to have to bounce things for
just this reason. He had some awful number of connections off the link
service, and one went down. End of year processing was happening, jobs being
printed, and they needed to get this one back asap.
It was not pleasant <G>
Things are more robust now, which is good, but having all your eggs in one
basket scares me.
Charles
"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.000062d8.5c9c42ca@compuserve.com...
| Quote: | Quiggley,
On DLC connections I always do a single link service (per nic) and
multiple
connections. I don't recall ever having to bounce the DLC link service to
fix
anything - max connections per link I have is about 12.
I have HIS2004 running on Win2003 server. It is being migrated here
from NT
and SNA4.
Question is, am I supposed to have a link for every connection or should
I
be able to use just a link for each NIC and point multiple connections to
it?
If multiple is there a limit as to how many connections can point to a
link?
Neil Pike. Protech Computing Ltd
|
|
|
| Back to top |
|
|
lsring@hotmail.com
Guest
|
| Posted:
Wed Apr 20, 2005 10:10 pm Post subject:
RE: Links and Connection |
|
|
I tend to agree if you are going to have alot of connections they use a
couple of link services. I have up to 20 PU(s) on one link services but have
a spare nic configured with DLC so if there is a hardware problem I can
easily move the link service and the pu(s). I have not yet distributed the
PU(s) across multiple links but may in the future if needed.
"Quiggley" wrote:
| Quote: | I have HIS2004 running on Win2003 server. It is being migrated here from NT
and SNA4.
Question is, am I supposed to have a link for every connection or should I
be able to use just a link for each NIC and point multiple connections to it?
If multiple is there a limit as to how many connections can point to a link? |
|
|
| Back to top |
|
|
Neil Pike
Guest
|
| Posted:
Fri Apr 22, 2005 8:06 pm Post subject:
Re: Links and Connection |
|
|
Charles,
I don't have all my eggs in one basket, don't worry. ;-)
Though all PU's on a server are via a single link service, I have 4 servers
across two geographically distributed sites. Plus two more servers that only
do printing (and no printing on the main 4).
Only issue I ever get is a memory/resource leak with the mngcli stuff that
requires a reboot every 6 months or so (the main servers are SNA 4 still, so
when I upgrade them to HIS 2004 shortly that will hopefully resolve that one!)
| Quote: | I just remember from a few years ago having to break the news to a customer
at 11:30pm on New Years Eve that he was going to have to bounce things for
just this reason. He had some awful number of connections off the link
service, and one went down. End of year processing was happening, jobs being
printed, and they needed to get this one back asap.
It was not pleasant <G
Things are more robust now, which is good, but having all your eggs in one
basket scares me.
|
Neil Pike. Protech Computing Ltd |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in