ADSM-L

[no subject]

2015-10-04 18:03:48
Thanks for the info, Roger --- we had opted for a Cisco router when this
project was first started, and I had serious doubts whether this chassis
and its token ring blades could handle the traffic (especially since the
world seemed to be running ADSM through an IBM 3172 or 2216). Seeing that
you've utilized a Bay Networks solution (which was something we did
consider as well, by the way, but the mechanism we were reviewing was still
in beta) has given me some hope that our decision wasn't entirely without
merit. I'm still battling, however, for ATM and a non-shared environment on
the network.

C.L.Cannam




Roger Nadler <Roger_Nadler AT SONYMUSIC DOT COM> on 11/20/97 09:11:40 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Cindy Cannam)
Subject:  Re: adsm and network considerations






What we have done is connect out RS6000 F50 ADSM Server to a Bay Networks
Centillion 100 Token Ring Switch. All of our client are also connected
directly to the switched. On clients such as Novell we can do a load
balance and connect two nic's directly to the switch. The backplane of the
switch is ATM. All the connections are virtual and thereby we can take up
all of the bandwidth on each connection.....


 (Embedded
 image moved   CCannam AT GENAM DOT COM
 to file:      11/20/97 09:41 AM
 PIC17522.PCX)



Please respond to ADSM-L AT VM.MARIST DOT EDU
To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Roger Nadler)
Subject:  adsm and network considerations



Has anyone tried to "route" ADSM network traffic to and from specific NICs
on individual clients? We're thinking that our backup and restore processes
might run more quickly if the data were pushed through one wire on the
network (unfortunately a 16 non-switched token ring NIC right now, but soon
to be upgraded to 100Mb Ethernet), with restore data running through
another NIC (same token ring config) from the same client but a different
connection on our router chassis. In theory, this may work, but I've not
seen any information concerning this type of set-up in any ADSM
documentation.
This truly may be something for the network folks to puzzle over (they live
for this, don't they?). The NICs are PCI, and we're running TCP/IP on both
server and clients, with MVS as the ADSM server.
Has anyone tried something like this? I'm interested in hearing whether
this is even something that can be pursued in real life....
C.L.Cannam
General American Life Ins. Co.
St. Louis, MO





<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Unknown <=