Hi Mark This is pure HiperSocket setup, all internal on the same CEC, RHEL and SUSE guests talking to DB2 on zOS.
Regards Gerard Ceruti may the 'z' be with you -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: 16 October 2008 06:03 PM To: [email protected] Subject: Re: hipersocket Ceruti, Gerard G wrote: > Hi All > > When defining the QDIO CHPID in HCD is there any issue with defining a > Frame Size of 64K ?, if we leave our MTU at 8K other than the some > storage wastage are there any other issues we need to be aware of > > Regards > Gerard Ceruti > may the 'z' be with you > Hi Gerard, it works without "other" issues. But I'm curious as to why you would want to set the MTU=8K? Jumbo frames are typically set on OSA's at 8992, so unless this is strictly LPAR to LPAR on the same CEC, then "PATH MTU DISCOVERY" may be in order (or setting all IFs to the same MTU) to prevent segmentation if packets arrive from a OSA and are bound for the HiperSockets. It all depends on what packet routing you will be doing. Without knowing your OS's, applications or network topology its hard to advise..... mark ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 _____________________________________________________________________________________________________________________________________ Standard Bank email Disclaimer and confidentiality note This e-mail, its attachments and any rights attaching hereto are, unless the content clearly indicates otherwise, the property of Standard Bank Group Limited and its subsidiaries. It is confidential, private and intended for only the addressee. Should you not be the addressee and receive this e-mail by mistake, kindly notify the sender, and delete this e-mail immediately. Do not disclose or use it in any way. Views and opinions expressed in this e-mail are those of the sender unless clearly stated as those of Standard Bank Group. Standard Bank Group accepts no liability for any loss or damages howsoever incurred, or suffered, resulting, or arising, from the use of this email or its attachments. Standard Bank Group does not warrant the integrity of this e-mail nor that it is free of errors, viruses, interception or interference. Licensed divisions of the Standard Bank Group are authorised financial services providers in terms of the Financial Advisory and Intermediary Services Act, No 37 of 2002 (FAIS). For information about the Standard Bank Group visit our website http://www.standardbank.com ________________________________________________________________________________________________________________________________________
