Re: Lanfree with AIX and W2k

MAXSGLIST should be no less than 65 (0x41) but you can up it to the top (I 
cannot recall right now was it 254 or 255). Also do not forget to increase 
the max_xfer_size parameter of 6228 HBA (fcs0, default is 0x100000 and it 
is recommended in the guides to be increased to 0x1000000). Use chdev or 
smitty. Details can be found in redbook "Using Tivoli Storage Manager in a 
SAN Environment" (SG24-6132-00).
You actual problem is that sizes do not match and one of them is too small 
(I guess the S/G list of Win STA).
The resolution might be just increase of Windows MAXSG to get it work. 
Later adjustment of AIX FC HBA setting would bring also performance.

Zlatko Krastev
IT Consultant






Markus Veit <markus.veit.mv AT BAYER-AG DOT DE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
29.10.2002 15:17
Please respond to "ADSM: Dist Stor Manager"

 
        To:     ADSM-L AT VM.MARIST DOT EDU
        cc: 
        Subject:        Lanfree with AIX and W2k


Hi all TSM SAN experts,
I am setting up a testing environment to move to Lanfree backup.
Environment:
TSM Server 5.1.5.1 AIX 4.3.3 ML 10, IBM 6228 FC HBA
TSM Storage Agent 5.1.5.1 W2k SP3, Compaq Storage Works FC HBA
TSM Baclient 5.1.1.0
Compaq FC SAN switch 2/8L
Compaq Modular Data Router connected to a IBM 3570 L180 with 4 drives.
All paths have been set up.

Now, what does work:
Normal backups from lan clients to diskpool as well as straight onto tape,
Sorage agent establishes communication with the TSM erver.
Baclient uses named pipe to communicate with storage agent.
Backup starts, Lanfree comm established, tape mounted.
Now I get this error.
ANR8939E (Session: 2040, Origin: SANAGNT)  The adapter for
                      tape drive DRIVE4 (mt0.7.0.5) cannot handle  the 
block
                      size needed to use the volume.
Help suggests that I do this, setup documentation says it should be 
greater than
41.
MAXIMUMSGLIST should be set to hex 41 to work properly with TSM.
Tried both, still the same error.
I couldn't find this error in the documentation of TSM server 5.1.
What else am I missing? Your help would be greatly appreciated.

Mit freundlichen Grüßen / Best Regards

Markus Veit