Re: Segmentation Offload - Need to Disable Again
We haven't enabled it yet! I don't like being woken in the middle of the night because every lpar that's using specific osa-ports is unreachable. Once was enough! -- Maarten -Oorspronkelijk bericht- Van: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Namens Mark Zelden Verzonden: donderdag 25 september 2008 21:54 Aan: IBM-MAIN@BAMA.UA.EDU Onderwerp: Segmentation Offload - Need to Disable Again I just was sent this: Mark - ATTENTION: The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it. Messages and attachments are scanned for all viruses known. If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain. Always scan attachments before opening them. - -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Segmentation Offload - Need to Disable Again
I just was sent this: === "We have had two customers report failures while running Large Send after installing the latest code levels on Driver 67 and 73 OSA Express2 EC streams. Once again this failure causes the OSA to lose communications with the network interface card which results is the same messages as we have become used to seeing with previous Large Send problems. With initial reports of this problem, it is aparent that it is much easier to hit this problem than the previous The new problem is reproducible in our lab, a fix has been created and tested. I do not have a target date for MCL releases to the field at this point." The following is from the TDR: TEXT: OSA Express 2 Segmentation offload problem A new microcode bug was found on Segmentation off-load feature, using OSA Express 2 1 gigabit card. This problem is found at our current latest microcode level in driver 55, 67 and 73. This TDR overrides TDR H186550. The problem surfaces as an OSPF Adjacency error after an EZZ4310I ERROR: CODE=80100040 REPORTED ON DEVICE . DIAGNOSTIC CODE: 03 We have determined that the cause of this error. It is improper handling of a four byte or less frame marked large send by the host. A fix is currently in test. This TDR will be updated with the fix levels, as soon as they are known. PE recommendation is to disable segmentation off-load feature until a fix is available. === Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
