Andrew,
Actually, this is set on the filer by using the cifs.max_mpx option. The process is documented in the IIS white paper in section 4.3.1:
http://www.netapp.com/tech_library/3078.html#4.3.1
If you still have trouble after configuring the cifs.max_mpx option, please open a call with our customer support group.
Regards,
Paul Benn
-----Original Message----- From: Andrew Smith [mailto:ajs@dca.net] Sent: Tuesday, April 17, 2001 10:58 AM To: Benn, Paul Cc: theffron@wisedata.com; 'toasters@mathworks.com ' Subject: RE: ASP caching
Paul (and others):
I've upgraded my F720 to 6.0.1R3 and I still see ASP caching happening with my two Windows 2000 / IIS 5.0 web servers. Editing an ASP script or uploading a new one has no effect - old data is still served up to http clients.
I poked around and found this:
http://support.microsoft.com/support/kb/articles/Q271/1/48.ASP
and contact Microsoft to get the Q271148 Hotfix. Installing that does not help.
Since the upgrade to 6.0.1R3 I'm also now getting these errors in my Windows syslog:
Apr 17 08:09:39 horizon w3svc[warning] The server was unable to add the virtual root '' for the directory '\filer\ibreast\nt.ibreast.com' due to the following error: The system cannot find the file specified. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
Apr 17 08:09:49 horizon w3svc[warning] The server was unable to add the virtual root '' for the directory '\filer\hummweb\hummingbirdsociety.org' due to the following error: The network BIOS command limit has been reached. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
Apr 17 08:09:49 horizon w3svc[warning] The server was unable to add the virtual root '' for the directory '\filer\templehealth\tuhscareers.dca.net' due to the following error: The network BIOS command limit has been reached. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
Apr 17 08:09:49 horizon w3svc[warning] The server was unable to add the virtual root '' for the directory '\filer\infowdl\wdl.org' due to the following error: The network BIOS command limit has been reached. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
Apr 17 08:09:49 horizon w3svc[warning] The server was unable to add the virtual root '' for the directory '\filer\pcvbweb\pcvb.dca.net' due to the following error: The network BIOS command limit has been reached. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
IIS has paths like this:
\filer\pcvbweb\pcvb.dca.net
where \filer is the filer, \pcvbweb is the CIFS shared unix home directory, and \pcvb.dca.net is a directory in the unix home directory.
Does anyone have any other ideas?
On Mon, 19 Mar 2001, Benn, Paul wrote:
Here's a tidbit from the white paper:
"Note: Selecting the "Run in separate memory space" option is generally not recommended outside of ASP development. Enabling this option causes excessive overhead by way of duplicate change/notify requests for each process on the remote machine specified in the Network Directory field. This is true not only for NetApp filers, but also for any machine that IIS accesses in this manner. IIS 5 presents a third option (now under the heading of Application Protection) called medium (pooled). Since this pools processes together rather than creating a separate process for each one, it doesn't cause as much overhead on the remote machine."
http://www.netapp.com/tech_library/3078.html
-----Original Message----- From: Andrew Smith [mailto:ajs@dca.net] Sent: Monday, March 19, 2001 12:46 PM To: theffron@wisedata.com Cc: 'toasters@mathworks.com ' Subject: Re: ASP caching
Hello,
We have worked around this by disabling ASP caching on those vhosts where it is requested. Once the customer finishes development work, we re-enabling caching to keep the load down on our filer.
The way to do this is:
- Open the Properties window of the vhost in question in the IIS manager
- Under 'Home Directory' set the Application Protection to 'High'
- Press 'Configuration' and uncheck 'Cache ISAPI applications'.
This works for us. We've found that if we disable 'Cache ISAPI applications' for the entire web server, the load on our filer and out web servers spikes way, way up. ISAPI caching dramatically increases performance. I just wish that IIS was smart enough to look at something as simple as the 'changed date' on a file to see if it should reload it into cache.
On Mon, 19 Mar 2001, Jean-Christophe Smith wrote:
We have a cluster of Windows 2000 servers running IIS 5.0, content lives
on
a NetApp F720 running OnTap Release 5.3.7R2. Our customers use FTP to
upload
their web pages.
IIS is caching ASP(active server pages), customers will make changes to their ASP files and try to view them(view IIS) and they see the older
pages.
I read about this issue entitled "5.3 Active Server Page Caching" in the NetApp document "Integrating a NetApp Filer with Microsoft IIS". I understand it is an issue with CIFS change/notify events and the way IIS
was
designed.
Does anybody know a way of fixing this? or maybe way to increase the change/notify events, or...
For now, we have to restart IIS when changes are made.
Maybe I could write a program to manually induce change/notify events?
Thanks, Jean-Christophe Smith jsmith@publichost.com VitalStream.com
Hi Paul,
Yes, I have my cifs.max_mpx set to 253.
Any other ideas?
-Andy
On Tue, 17 Apr 2001, Benn, Paul wrote:
Andrew,
Actually, this is set on the filer by using the cifs.max_mpx option. The process is documented in the IIS white paper in section 4.3.1:
http://www.netapp.com/tech_library/3078.html#4.3.1
If you still have trouble after configuring the cifs.max_mpx option, please open a call with our customer support group.
Regards,
Paul Benn
-----Original Message----- From: Andrew Smith [mailto:ajs@dca.net] Sent: Tuesday, April 17, 2001 10:58 AM To: Benn, Paul Cc: theffron@wisedata.com; 'toasters@mathworks.com ' Subject: RE: ASP caching
Paul (and others):
I've upgraded my F720 to 6.0.1R3 and I still see ASP caching happening with my two Windows 2000 / IIS 5.0 web servers. Editing an ASP script or uploading a new one has no effect - old data is still served up to http clients.
I poked around and found this:
http://support.microsoft.com/support/kb/articles/Q271/1/48.ASP
and contact Microsoft to get the Q271148 Hotfix. Installing that does not help.
Since the upgrade to 6.0.1R3 I'm also now getting these errors in my Windows syslog:
Apr 17 08:09:39 horizon w3svc[warning] The server was unable to add the virtual root '' for the directory '\filer\ibreast\nt.ibreast.com' due to the following error: The system cannot find the file specified. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
Apr 17 08:09:49 horizon w3svc[warning] The server was unable to add the virtual root '' for the directory '\filer\hummweb\hummingbirdsociety.org' due to the following error: The network BIOS command limit has been reached. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
Apr 17 08:09:49 horizon w3svc[warning] The server was unable to add the virtual root '' for the directory '\filer\templehealth\tuhscareers.dca.net' due to the following error: The network BIOS command limit has been reached. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
Apr 17 08:09:49 horizon w3svc[warning] The server was unable to add the virtual root '' for the directory '\filer\infowdl\wdl.org' due to the following error: The network BIOS command limit has been reached. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
Apr 17 08:09:49 horizon w3svc[warning] The server was unable to add the virtual root '' for the directory '\filer\pcvbweb\pcvb.dca.net' due to the following error: The network BIOS command limit has been reached. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
IIS has paths like this:
\filer\pcvbweb\pcvb.dca.net
where \filer is the filer, \pcvbweb is the CIFS shared unix home directory, and \pcvb.dca.net is a directory in the unix home directory.
Does anyone have any other ideas?
On Mon, 19 Mar 2001, Benn, Paul wrote:
Here's a tidbit from the white paper:
"Note: Selecting the "Run in separate memory space" option is generally not recommended outside of ASP development. Enabling this option causes excessive overhead by way of duplicate change/notify requests for each process on the remote machine specified in the Network Directory field. This is true not only for NetApp filers, but also for any machine that IIS accesses in this manner. IIS 5 presents a third option (now under the heading of Application Protection) called medium (pooled). Since this pools processes together rather than creating a separate process for each one, it doesn't cause as much overhead on the remote machine."
http://www.netapp.com/tech_library/3078.html
-----Original Message----- From: Andrew Smith [mailto:ajs@dca.net] Sent: Monday, March 19, 2001 12:46 PM To: theffron@wisedata.com Cc: 'toasters@mathworks.com ' Subject: Re: ASP caching
Hello,
We have worked around this by disabling ASP caching on those vhosts where it is requested. Once the customer finishes development work, we re-enabling caching to keep the load down on our filer.
The way to do this is:
- Open the Properties window of the vhost in question in the IIS manager
- Under 'Home Directory' set the Application Protection to 'High'
- Press 'Configuration' and uncheck 'Cache ISAPI applications'.
This works for us. We've found that if we disable 'Cache ISAPI applications' for the entire web server, the load on our filer and out web servers spikes way, way up. ISAPI caching dramatically increases performance. I just wish that IIS was smart enough to look at something as simple as the 'changed date' on a file to see if it should reload it into cache.
On Mon, 19 Mar 2001, Jean-Christophe Smith wrote:
We have a cluster of Windows 2000 servers running IIS 5.0, content lives
on
a NetApp F720 running OnTap Release 5.3.7R2. Our customers use FTP to
upload
their web pages.
IIS is caching ASP(active server pages), customers will make changes to their ASP files and try to view them(view IIS) and they see the older
pages.
I read about this issue entitled "5.3 Active Server Page Caching" in the NetApp document "Integrating a NetApp Filer with Microsoft IIS". I understand it is an issue with CIFS change/notify events and the way IIS
was
designed.
Does anybody know a way of fixing this? or maybe way to increase the change/notify events, or...
For now, we have to restart IIS when changes are made.
Maybe I could write a program to manually induce change/notify events?
Thanks, Jean-Christophe Smith jsmith@publichost.com VitalStream.com
-
Andrew Smith -
Benn, Paul