Rick, Thanks for the reply. I passed your comments to my SAN guy and he said:
*Earth is connected to HHIsilon and it is running 8.1.0.4 **All the others are connected to ISPIsilon and it is running 8.0.0.4* *I'm pretty sure all the Cisco switchports are LACP and Isilon networking is configured for LACP. Can that person elaborate on that bug?* On Wed, Sep 5, 2018 at 12:00 PM Rhodes, Richard L. < rrho...@firstenergycorp.com> wrote: > We run our Isilon systems (OneFS 8.0.0.6) with active/passive failover. > When we put them in OneFS had a bug with LACP and wouldn't work, forcing us > to go active/passive. Due to other problems, we just discussed with them > converting from active/passive to LACP, but EMC said there is still a bug > in LACP support. > > Rick > > > > -----Original Message----- > From: ADSM: Dist Stor Manager <ADSM-L@VM.MARIST.EDU> On Behalf Of Zoltan > Forray > Sent: Wednesday, September 5, 2018 9:03 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [EXTERNAL] Re: nfstimeout on server ISILON storage > > A pair of 10G links bonded - CISCO switches. > > On Tue, Sep 4, 2018 at 7:54 PM Skylar Thompson <skyl...@uw.edu> wrote: > > > Quick question - what's the data link protocol (Ethernet, IB, etc.) and > > link rate > > that you're using? > > > > On Tue, Sep 04, 2018 at 02:05:33PM -0400, Zoltan Forray wrote: > > > We are still fighting issues with ISILON storage. Our current issue is > > with > > > NFS timeouts for the storage a server is using. We see message like > > these > > > in the server /var/log > > > > > > Sep 4 13:21:49 earth kernel: nfs: server > hhisilonnfs23.rams.adp.vcu.edu > > > not responding, still trying > > > Sep 4 13:21:49 earth kernel: nfs: server > hhisilonnfs23.rams.adp.vcu.edu > > > not responding, still trying > > > Sep 4 13:21:49 earth kernel: nfs: server > hhisilonnfs23.rams.adp.vcu.edu > > > not responding, still trying > > > Sep 4 13:21:49 earth kernel: nfs: server > hhisilonnfs23.rams.adp.vcu.edu > > > not responding, still trying > > > Sep 4 13:22:14 earth kernel: nfs: server > hhisilonnfs23.rams.adp.vcu.edu > > > not responding, still trying > > > Sep 4 13:22:15 earth kernel: nfs: server > hhisilonnfs23.rams.adp.vcu.edu > > > not responding, still trying > > > Sep 4 13:22:16 earth kernel: nfs: server > hhisilonnfs23.rams.adp.vcu.edu > > OK > > > Sep 4 13:22:16 earth kernel: nfs: server > hhisilonnfs23.rams.adp.vcu.edu > > OK > > > Sep 4 13:22:16 earth kernel: nfs: server > hhisilonnfs23.rams.adp.vcu.edu > > OK > > > > > > OS folks say the NFS mount is setup as IBM recommends in various > > documents. > > > So they asked us to implement the nfstimeout option from this document > ( > > > > > > https://www.ibm.com/support/knowledgecenter/en/SSGSG7_7.1.0/com.ibm.itsm.client.doc/r_opt_nfstimeout.html > > ). > > > Yes I realize it is primarily for a client backup of an NFS mount, but > > the > > > statement: > > > > > > Supported Clients This option is for all UNIX and Linux clients. *The > > > server can also define this option*. > > > > > > throws us - kind-of implying I can use this from the server > perspective? > > > But I can't find any documentation to support using it from the server. > > > > > > For you Linux guru's - this is what the mount says: > > > > > > hhisilonnfs23.rams.adp.vcu.edu:/ifs/NFS/TSM on /tsmnfs type nfs > > > > > > (rw,relatime,sync,vers=3,rsize=131072,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.19.12,mountvers=3,mountport=300,mountproto=udp,local_lock=none,addr=192.168.19.12) > > > > > > Any thoughts? Suggestion? Are we simply expecting too much from NFS? > > > > > > My OS person also asks why ISP is so slow to write to NFS? When they > > did a > > > test copy of a large file to the NFS mount, they were getting upwards > of > > 8G/s > > > vs 1.5-3G/s when TSM/ISP writes to it (via EMC monitoring tools). > > > > > > -- > > > *Zoltan Forray* > > > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > > > Xymon Monitor Administrator > > > VMware Administrator > > > Virginia Commonwealth University > > > UCC/Office of Technology Services > > > www.ucc.vcu.edu > > > zfor...@vcu.edu - 804-828-4807 > > > Don't be a phishing victim - VCU and other reputable organizations will > > > never use email to request that you reply with your password, social > > > security number or confidential personal information. For more details > > > visit http://phishing.vcu.edu/ > > > > -- > > -- Skylar Thompson (skyl...@u.washington.edu) > > -- Genome Sciences Department, System Administrator > > -- Foege Building S046, (206)-685-7354 > > -- University of Washington School of Medicine > > > > > -- > *Zoltan Forray* > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > Xymon Monitor Administrator > VMware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > www.ucc.vcu.edu > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://phishing.vcu.edu/ > > ------------------------------------------------------------------------------ > > The information contained in this message is intended only for the > personal and confidential use of the recipient(s) named above. If the > reader of this message is not the intended recipient or an agent > responsible for delivering it to the intended recipient, you are hereby > notified that you have received this document in error and that any review, > dissemination, distribution, or copying of this message is strictly > prohibited. If you have received this communication in error, please notify > us immediately, and delete the original message. > -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/
