Re: [Veritas-bu] Blocksize problem after upgrading EMC powerpath ( UPDATE)

2006-01-19 Thread william . d . brown
I spoke to a colleague who deals with Windows, and he tells me that there 
is an option that can be set with the SP to not over-write OEM drivers, 
which we use.  Otherwise we found some of our HP servers with onboard RAID 
cannot be booted.

So I suggest, check that out and make whoever is doing your SP1 patching 
do so too.

William D L Brown




[EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
19-Jan-2006 12:56
 
To
[EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu
cc
[EMAIL PROTECTED]
Subject
Re: [Veritas-bu] Blocksize problem after upgrading EMC powerpath ( UPDATE)






I have tried, but it seems that the emulex driver detects that SP1 is 
installed and then create the emulexhbaapi.dll in system32. I'm also 
afraid 
that the next windows update will overwrite hbaapi.dll if isn't the 
microsoft 
one.

Regards
Michael

On Thu, 19 Jan 2006 09:59:14 +, william.d.brown wrote
> Well at a guess I would re-apply the Emulex driver to the HBAs.  Go 
> into device manager, right click on the HBA, and ask to Update 
> Driver.   If you tell it to look in /windows/system32 for the driver 
> it may find it, without you needing the CD.   Excuse me being a bit 
> vague, I have not tried it.  You can also check if you look at the 
> Driver Details tab just which files & driver it is using, I guess 
> you will see it using hbaapi.dll.  At least you will be able to see 
> if you succeed in changing it.
> 
> William D L Brown
> 
> [EMAIL PROTECTED] 
> Sent by: [EMAIL PROTECTED]
> 18-Jan-2006 15:56
> 
> To
> veritas-bu@mailman.eng.auburn.edu
> cc
> 
> Subject
> [Veritas-bu] Blocksize problem after upgrading EMC powerpath ( UPDATE)
> 
> Hello All
> 
> I have now by trial and error figured out that it wasn't EMC 
> powerpath, but Windows 2003 SP1 which puts a microsoft hbaapi.dll 
> into system32 in place of the emulex one.
> 
> At the moment there's hbaapi.dll (from microsoft, 64Kb limit) and 
> emulexhbaapi.dll (at least 256kb) in system32 on the servers in 
question.
> 
> Now I just need to figure how to get the tape drivers to use the 
> emulexhbaapi.dll, any ideas ?
> 
> Regards
> Michael
> 
> --
> Cybercity Webhosting (http://www.cybercity.dk)
> 
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


--
Cybercity Webhosting (http://www.cybercity.dk)

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu




___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Blocksize problem after upgrading EMC powerpath ( UPDATE)

2006-01-19 Thread ida3248b
I have tried, but it seems that the emulex driver detects that SP1 is 
installed and then create the emulexhbaapi.dll in system32. I'm also afraid 
that the next windows update will overwrite hbaapi.dll if isn't the microsoft 
one.

Regards
Michael

On Thu, 19 Jan 2006 09:59:14 +, william.d.brown wrote
> Well at a guess I would re-apply the Emulex driver to the HBAs.  Go 
> into device manager, right click on the HBA, and ask to Update 
> Driver.   If you tell it to look in /windows/system32 for the driver 
> it may find it, without you needing the CD.   Excuse me being a bit 
> vague, I have not tried it.  You can also check if you look at the 
> Driver Details tab just which files & driver it is using, I guess 
> you will see it using hbaapi.dll.  At least you will be able to see 
> if you succeed in changing it.
> 
> William D L Brown
> 
> [EMAIL PROTECTED] 
> Sent by: [EMAIL PROTECTED]
> 18-Jan-2006 15:56
> 
> To
> veritas-bu@mailman.eng.auburn.edu
> cc
> 
> Subject
> [Veritas-bu] Blocksize problem after upgrading EMC powerpath ( UPDATE)
> 
> Hello All
> 
> I have now by trial and error figured out that it wasn't EMC 
> powerpath, but Windows 2003 SP1 which puts a microsoft hbaapi.dll 
> into system32 in place of the emulex one.
> 
> At the moment there's hbaapi.dll (from microsoft, 64Kb limit) and 
> emulexhbaapi.dll (at least 256kb) in system32 on the servers in question.
> 
> Now I just need to figure how to get the tape drivers to use the 
> emulexhbaapi.dll, any ideas ?
> 
> Regards
> Michael
> 
> --
> Cybercity Webhosting (http://www.cybercity.dk)
> 
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


--
Cybercity Webhosting (http://www.cybercity.dk)

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Blocksize problem after upgrading EMC powerpath ( UPDATE)

2006-01-19 Thread william . d . brown
Well at a guess I would re-apply the Emulex driver to the HBAs.  Go into 
device manager, right click on the HBA, and ask to Update Driver.   If you 
tell it to look in /windows/system32 for the driver it may find it, 
without you needing the CD.   Excuse me being a bit vague, I have not 
tried it.  You can also check if you look at the Driver Details tab just 
which files & driver it is using, I guess you will see it using 
hbaapi.dll.  At least you will be able to see if you succeed in changing 
it.

William D L Brown




[EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
18-Jan-2006 15:56
 
To
veritas-bu@mailman.eng.auburn.edu
cc

Subject
[Veritas-bu] Blocksize problem after upgrading EMC powerpath ( UPDATE)






Hello All

I have now by trial and error figured out that it wasn't EMC powerpath, 
but 
Windows 2003 SP1 which puts a microsoft hbaapi.dll into system32 in place 
of 
the emulex one.

At the moment there's hbaapi.dll (from microsoft, 64Kb limit) and 
emulexhbaapi.dll (at least 256kb) in system32 on the servers in question.

Now I just need to figure how to get the tape drivers to use the 
emulexhbaapi.dll, any ideas ?


Regards
Michael

--
Cybercity Webhosting (http://www.cybercity.dk)

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu




___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Blocksize problem after upgrading EMC powerpath (UPDATE)

2006-01-18 Thread ida3248b
Hello All

I have now by trial and error figured out that it wasn't EMC powerpath, but 
Windows 2003 SP1 which puts a microsoft hbaapi.dll into system32 in place of 
the emulex one.

At the moment there's hbaapi.dll (from microsoft, 64Kb limit) and 
emulexhbaapi.dll (at least 256kb) in system32 on the servers in question.

Now I just need to figure how to get the tape drivers to use the 
emulexhbaapi.dll, any ideas ?


Regards
Michael

--
Cybercity Webhosting (http://www.cybercity.dk)

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Blocksize problem after upgrading EMC powerpath

2005-11-22 Thread ida3248b
Thanks

But we haven't done anything about block size to the registry before.
I have opened a case with DELL (Where we have EMC support) to get this solved.

Regards
Michael

On Mon, 21 Nov 2005 13:04:48 +, william.d.brown wrote
> Windows registry at a guess.
> 
> \HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\elx{something}
\Parameters\Device
> 
> maximum_sglist is the parameter.
> 
> William D L Brown
> 
> [EMAIL PROTECTED] 
> Sent by: [EMAIL PROTECTED]
> 21-Nov-2005 08:49
> 
> To
> veritas-bu@mailman.eng.auburn.edu
> cc
> 
> Subject
> [Veritas-bu] Blocksize problem after upgrading EMC powerpath
> 
> Hello All
> 
> After upgrading EMC powerpath to 4.4.1 on the Windows 2003 backup 
> server, I get the following error on my LTO2 drives:
> 
> Error bptm(pid=9660) The tape device at index -1 has a maximum block 
> size of 65536 bytes, a buffer size of 262144 cannot be used
> 
> I have checked that the tape drivers support blocks greater than 
> 65536 
> (Actually we been running with 262144 since june)
> 
> Any ideas about were to change this 64Kb limit ?
> 
> The backup are using Emulex L982 HBA's
> 
> Regards
> Michael
> 
> --
> Cybercity Webhosting (http://www.cybercity.dk)
> 
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


--
Cybercity Webhosting (http://www.cybercity.dk)

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Blocksize problem after upgrading EMC powerpath

2005-11-21 Thread william . d . brown
Windows registry at a guess. 

\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\elx{something}\Parameters\Device

maximum_sglist is the parameter.


William D L Brown




[EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
21-Nov-2005 08:49
 
To
veritas-bu@mailman.eng.auburn.edu
cc

Subject
[Veritas-bu] Blocksize problem after upgrading EMC powerpath






Hello All

After upgrading EMC powerpath to 4.4.1 on the Windows 2003 backup server, 
I 
get the following error on my LTO2 drives:

Error bptm(pid=9660) The tape device at index -1 has a maximum block size 
of 
65536 bytes, a buffer size of 262144 cannot be used

I have checked that the tape drivers support blocks greater than 65536 
(Actually we been running with 262144 since june)

Any ideas about were to change this 64Kb limit ?

The backup are using Emulex L982 HBA's

Regards
Michael

--
Cybercity Webhosting (http://www.cybercity.dk)

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu




___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Blocksize problem after upgrading EMC powerpath

2005-11-21 Thread ida3248b
Hello All

After upgrading EMC powerpath to 4.4.1 on the Windows 2003 backup server, I 
get the following error on my LTO2 drives:

Error bptm(pid=9660) The tape device at index -1 has a maximum block size of 
65536 bytes, a buffer size of 262144 cannot be used

I have checked that the tape drivers support blocks greater than 65536 
(Actually we been running with 262144 since june)

Any ideas about were to change this 64Kb limit ?

The backup are using Emulex L982 HBA's

Regards
Michael

--
Cybercity Webhosting (http://www.cybercity.dk)

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu