× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I do have Anynet working between LPARs, but there has been some
discussion here in the past about how long Anynet might be supported.
Regardless, I do not believe that the virtual LAN is being utilized in
this case.

Just for the record, on our 60 GB Library:
* SAVLIB to a savf takes about 3 minutes
* SAVLIB SAVACT(*LIB) to a savf takes about 8 minutes (The
library reaches the sync point in 10-15 seconds.)

* FTP of the savf to the other LPAR takes 60-75 minutes.

* SAVRSTLIB to the other LPAR takes 3-4 hours.

If I can get SAVRSTLIB to run across the VLAN in under 60 minutes I'll
be ecstatic!

Regards,

Scott Ingvaldson
Senior IBM Support Specialist
Fiserv Midwest


-----Original Message-----
From: Evan Harris [mailto:spanner@xxxxxxxxxx]
Sent: Friday, January 18, 2008 5:52 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Virtual Ethernet

Hi Scott

One of the other comments about network set up is well worth looking at.
If the FTP transfer is initiated using a name rather than an address and
the name resolves to the external address the transfer will still go
"out" over the "normal" network. If the transfer is initiated using an
address you'll also need to be sure that the address is routed over the
correct VLAN adapter.

When we wanted to use the VLAN we set up a separate name for the LPARs
in the host table so we could do the transfer by name. We also added
routing entries for the internal address to route it over the correct
adapter.

You mention that you are transferring a library via FTP. You could
consider configuring anynet between the two partitions so you can use
the SNA-based commands. I've always had better results using the SAVRST
commands to transfer libraries between machines and partitions. I prefer
the use of one command and it is more efficient storage-wise. Itusually
outperforms FTP especially when you take the save and restore time for
the FTP save file into account.

Hope this helps

Regards
Evan Harris



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ingvaldson, Scott
Sent: Saturday, 19 January 2008 10:25 a.m.
To: midrange-l@xxxxxxxxxxxx
Subject: Virtual Ethernet

I'm trying to get virtual ethernet connectivity set up between LPARs on
a 550 here. We need to do a daily transfer of a 60 GB library between
LPARs.

I created the resources and lines, gave them IP addresses,
(192.168.10.xxx) varied them on and got them talking. Unfortunately it
doesn't seem any faster than it was before.

This is the LIND on both sides:

CRTLINETH LIND(VRTETH01) RSRCNAME(CMN13) ONLINE(*YES) +
VRYWAIT(*NOWAIT) MAXCTL(40) ADPTADR(*ADPT) +
EXCHID(0569D5FF) ETHSTD(*ALL) LINESPEED(1G) DUPLEX(*FULL) +
MAXFRAME(8996) SSAP((04 1496 *SNA)(12 1496 *NONSNA)(AA +
8996 *NONSNA)(C8 1496 *HPR)) THRESHOLD(*OFF) +
GENTSTFRM(*YES) LINKSPEED(*MAX) COSTCNN(0) COSTBYTE(0) +
SECURITY(*NONSECURE) PRPDLY(*LAN) USRDFN1(128) +
USRDFN2(128) USRDFN3(128) AUTOCRTCTL(*YES) +
AUTODLTCTL(1440) CMNRCYLMT(2 5) MSGQ(*SYSVAL) +
TEXT('Virtual Ethernet')

An FTP using the new interface gave me this:
59497012608 bytes transferred in 4442.494 seconds. Transfer rate
13392.705 KB/sec.

That's 74 minutes for 60 GB, is that a reasonable speed over virtual
ethernet? I can save it to tape faster than that.

Regards,

Scott Ingvaldson
Senior IBM Support Specialist
Fiserv Midwest

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.