Is there an update to tr-4068? Moreover looking for VMware 6x, NFS, jumbo frames info. If 4068 is best, I can use that.
Steve
Hi Steve TR-4333 is the Web Client version, with additional updates.
Share and enjoy!
Peter
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Klise, Steve Sent: Thursday, December 17, 2015 9:42 AM To: toasters@teaparty.net Subject: VMware on CDOT 8.3.x
Is there an update to tr-4068? Moreover looking for VMware 6x, NFS, jumbo frames info. If 4068 is best, I can use that.
Steve
Thanks for the microsecond response!!
Steve From: "Learmonth, Peter" <Peter.Learmonth@netapp.commailto:Peter.Learmonth@netapp.com> Date: Thursday, December 17, 2015 at 9:43 AM To: "Klise, Steve" <Steve.Klise@wwt.commailto:Steve.Klise@wwt.com>, "toasters@teaparty.netmailto:toasters@teaparty.net" <toasters@teaparty.netmailto:toasters@teaparty.net> Subject: RE: VMware on CDOT 8.3.x
Hi Steve TR-4333 is the Web Client version, with additional updates.
Share and enjoy!
Peter
From: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Klise, Steve Sent: Thursday, December 17, 2015 9:42 AM To: toasters@teaparty.netmailto:toasters@teaparty.net Subject: VMware on CDOT 8.3.x
Is there an update to tr-4068? Moreover looking for VMware 6x, NFS, jumbo frames info. If 4068 is best, I can use that.
Steve
Forgot to add: While it still primarily addresses vSphere 5.5, there isn’t a whole lot that changed as far as storage, except VVols, which is TR-4400.
One thing that will go in the next version of these docs is that we’re dropping the best practice of a LIF per NFS datastore. Those who saw Eric and I present at Insight got a heads up. This does not mean tearing apart what people have already deployed and remounting most of your datastores on fewer IP addresses. That would be disruptive. What it means is as you deploy new datastores in existing environments, use the existing LIFs/IPs. For new deployments, we recommend at least one LIF per node per SVM serving NFS datastores. Depending on network design especially with IP hash and link aggregation, you may want multiple (2 to 4) LIFs per node for better link utilization with datastores mounted spread across those IPs.
Peter
From: Klise, Steve [mailto:Steve.Klise@wwt.com] Sent: Thursday, December 17, 2015 9:45 AM To: Learmonth, Peter; toasters@teaparty.net Subject: Re: VMware on CDOT 8.3.x
Thanks for the microsecond response!!
Steve From: "Learmonth, Peter" <Peter.Learmonth@netapp.commailto:Peter.Learmonth@netapp.com> Date: Thursday, December 17, 2015 at 9:43 AM To: "Klise, Steve" <Steve.Klise@wwt.commailto:Steve.Klise@wwt.com>, "toasters@teaparty.netmailto:toasters@teaparty.net" <toasters@teaparty.netmailto:toasters@teaparty.net> Subject: RE: VMware on CDOT 8.3.x
Hi Steve TR-4333 is the Web Client version, with additional updates.
Share and enjoy!
Peter
From: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Klise, Steve Sent: Thursday, December 17, 2015 9:42 AM To: toasters@teaparty.netmailto:toasters@teaparty.net Subject: VMware on CDOT 8.3.x
Is there an update to tr-4068? Moreover looking for VMware 6x, NFS, jumbo frames info. If 4068 is best, I can use that.
Steve
Do you know if this is still an issue with Nexus? I almost choked when I saw it.
http://blog.scottlowe.org/2009/11/09/enabling-jumbo-frames-on-a-nexus-5000/ "if you upgrade NX-OS from 4.0 to 4.1, then your jumbo frames configuration will go away, and you’ll need to enter the commands for version 4.1 in order to enable jumbo frame support again. This little gotcha caused me quite a headache when my NFS-based datastores suddenly went offline after the NX-OS upgrade.”
From: "Learmonth, Peter" <Peter.Learmonth@netapp.commailto:Peter.Learmonth@netapp.com> Date: Thursday, December 17, 2015 at 9:55 AM To: "Klise, Steve" <Steve.Klise@wwt.commailto:Steve.Klise@wwt.com>, "toasters@teaparty.netmailto:toasters@teaparty.net" <toasters@teaparty.netmailto:toasters@teaparty.net> Subject: RE: VMware on CDOT 8.3.x
Forgot to add: While it still primarily addresses vSphere 5.5, there isn’t a whole lot that changed as far as storage, except VVols, which is TR-4400.
One thing that will go in the next version of these docs is that we’re dropping the best practice of a LIF per NFS datastore. Those who saw Eric and I present at Insight got a heads up. This does not mean tearing apart what people have already deployed and remounting most of your datastores on fewer IP addresses. That would be disruptive. What it means is as you deploy new datastores in existing environments, use the existing LIFs/IPs. For new deployments, we recommend at least one LIF per node per SVM serving NFS datastores. Depending on network design especially with IP hash and link aggregation, you may want multiple (2 to 4) LIFs per node for better link utilization with datastores mounted spread across those IPs.
Peter
From: Klise, Steve [mailto:Steve.Klise@wwt.com] Sent: Thursday, December 17, 2015 9:45 AM To: Learmonth, Peter; toasters@teaparty.netmailto:toasters@teaparty.net Subject: Re: VMware on CDOT 8.3.x
Thanks for the microsecond response!!
Steve From: "Learmonth, Peter" <Peter.Learmonth@netapp.commailto:Peter.Learmonth@netapp.com> Date: Thursday, December 17, 2015 at 9:43 AM To: "Klise, Steve" <Steve.Klise@wwt.commailto:Steve.Klise@wwt.com>, "toasters@teaparty.netmailto:toasters@teaparty.net" <toasters@teaparty.netmailto:toasters@teaparty.net> Subject: RE: VMware on CDOT 8.3.x
Hi Steve TR-4333 is the Web Client version, with additional updates.
Share and enjoy!
Peter
From:toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Klise, Steve Sent: Thursday, December 17, 2015 9:42 AM To: toasters@teaparty.netmailto:toasters@teaparty.net Subject: VMware on CDOT 8.3.x
Is there an update to tr-4068? Moreover looking for VMware 6x, NFS, jumbo frames info. If 4068 is best, I can use that.
Steve
2009? I would hope most are no longer running switch code from 2009. I think the perferred code these days is at least something on 5.x and even 7.x on newer models.
--tmac
*Tim McCarthy* *Principal Consultant*
On Thu, Dec 17, 2015 at 1:27 PM, Klise, Steve Steve.Klise@wwt.com wrote:
Do you know if this is still an issue with Nexus? I almost choked when I saw it.
http://blog.scottlowe.org/2009/11/09/enabling-jumbo-frames-on-a-nexus-5000 / "if you upgrade NX-OS from 4.0 to 4.1, then your jumbo frames configuration will go away, and you’ll need to enter the commands for version 4.1 in order to enable jumbo frame support again. This little gotcha caused me quite a headache when my NFS-based datastores suddenly went offline after the NX-OS upgrade.”
From: "Learmonth, Peter" Peter.Learmonth@netapp.com Date: Thursday, December 17, 2015 at 9:55 AM
To: "Klise, Steve" Steve.Klise@wwt.com, "toasters@teaparty.net" < toasters@teaparty.net> Subject: RE: VMware on CDOT 8.3.x
Forgot to add:
While it still primarily addresses vSphere 5.5, there isn’t a whole lot that changed as far as storage, except VVols, which is TR-4400.
One thing that will go in the next version of these docs is that we’re dropping the best practice of a LIF per NFS datastore. Those who saw Eric and I present at Insight got a heads up. This does not mean tearing apart what people have already deployed and remounting most of your datastores on fewer IP addresses. That would be disruptive. What it means is as you deploy new datastores in existing environments, use the existing LIFs/IPs. For new deployments, we recommend at least one LIF per node per SVM serving NFS datastores. Depending on network design especially with IP hash and link aggregation, you may want multiple (2 to 4) LIFs per node for better link utilization with datastores mounted spread across those IPs.
Peter
*From:* Klise, Steve [mailto:Steve.Klise@wwt.com Steve.Klise@wwt.com] *Sent:* Thursday, December 17, 2015 9:45 AM *To:* Learmonth, Peter; toasters@teaparty.net *Subject:* Re: VMware on CDOT 8.3.x
Thanks for the microsecond response!!
Steve
*From: *"Learmonth, Peter" Peter.Learmonth@netapp.com
*Date: *Thursday, December 17, 2015 at 9:43 AM *To: *"Klise, Steve" Steve.Klise@wwt.com, "toasters@teaparty.net" < toasters@teaparty.net> *Subject: *RE: VMware on CDOT 8.3.x
Hi Steve
TR-4333 is the Web Client version, with additional updates.
Share and enjoy!
Peter
*From:*toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net toasters-bounces@teaparty.net] *On Behalf Of *Klise, Steve *Sent:* Thursday, December 17, 2015 9:42 AM *To:* toasters@teaparty.net *Subject:* VMware on CDOT 8.3.x
Is there an update to tr-4068? Moreover looking for VMware 6x, NFS, jumbo frames info. If 4068 is best, I can use that.
Steve
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Beats me on that one, but I did have something similar. I was setting up FCoE on a Nexus, and created the jumbo policy for FCoE class. The commands I entered created it as the only policy class, clobbering the MTU 9000 policy I had for the NFS stuff. All the NFS datastores went offline. I have some notes on that somewhere and I know I presented it at Insight last year or year before in the 7 Deadly Sins session.
Peter
From: tmac [mailto:tmacmd@gmail.com] Sent: Thursday, December 17, 2015 10:33 AM To: NGC-steve.klise-wwt.com Cc: Learmonth, Peter; toasters@teaparty.net Subject: Re: VMware on CDOT 8.3.x
2009? I would hope most are no longer running switch code from 2009. I think the perferred code these days is at least something on 5.x and even 7.x on newer models.
--tmac
Tim McCarthy Principal Consultant
On Thu, Dec 17, 2015 at 1:27 PM, Klise, Steve <Steve.Klise@wwt.commailto:Steve.Klise@wwt.com> wrote: Do you know if this is still an issue with Nexus? I almost choked when I saw it.
http://blog.scottlowe.org/2009/11/09/enabling-jumbo-frames-on-a-nexus-5000/ "if you upgrade NX-OS from 4.0 to 4.1, then your jumbo frames configuration will go away, and you’ll need to enter the commands for version 4.1 in order to enable jumbo frame support again. This little gotcha caused me quite a headache when my NFS-based datastores suddenly went offline after the NX-OS upgrade.”
From: "Learmonth, Peter" <Peter.Learmonth@netapp.commailto:Peter.Learmonth@netapp.com> Date: Thursday, December 17, 2015 at 9:55 AM
To: "Klise, Steve" <Steve.Klise@wwt.commailto:Steve.Klise@wwt.com>, "toasters@teaparty.netmailto:toasters@teaparty.net" <toasters@teaparty.netmailto:toasters@teaparty.net> Subject: RE: VMware on CDOT 8.3.x
Forgot to add: While it still primarily addresses vSphere 5.5, there isn’t a whole lot that changed as far as storage, except VVols, which is TR-4400.
One thing that will go in the next version of these docs is that we’re dropping the best practice of a LIF per NFS datastore. Those who saw Eric and I present at Insight got a heads up. This does not mean tearing apart what people have already deployed and remounting most of your datastores on fewer IP addresses. That would be disruptive. What it means is as you deploy new datastores in existing environments, use the existing LIFs/IPs. For new deployments, we recommend at least one LIF per node per SVM serving NFS datastores. Depending on network design especially with IP hash and link aggregation, you may want multiple (2 to 4) LIFs per node for better link utilization with datastores mounted spread across those IPs.
Peter
From: Klise, Steve [mailto:Steve.Klise@wwt.com] Sent: Thursday, December 17, 2015 9:45 AM To: Learmonth, Peter; toasters@teaparty.netmailto:toasters@teaparty.net Subject: Re: VMware on CDOT 8.3.x
Thanks for the microsecond response!!
Steve From: "Learmonth, Peter" <Peter.Learmonth@netapp.commailto:Peter.Learmonth@netapp.com> Date: Thursday, December 17, 2015 at 9:43 AM To: "Klise, Steve" <Steve.Klise@wwt.commailto:Steve.Klise@wwt.com>, "toasters@teaparty.netmailto:toasters@teaparty.net" <toasters@teaparty.netmailto:toasters@teaparty.net> Subject: RE: VMware on CDOT 8.3.x
Hi Steve TR-4333 is the Web Client version, with additional updates.
Share and enjoy!
Peter
From:toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Klise, Steve Sent: Thursday, December 17, 2015 9:42 AM To: toasters@teaparty.netmailto:toasters@teaparty.net Subject: VMware on CDOT 8.3.x
Is there an update to tr-4068? Moreover looking for VMware 6x, NFS, jumbo frames info. If 4068 is best, I can use that.
Steve
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
-
Klise, Steve -
Learmonth, Peter -
tmac