Does anyone know if you can re-order the entries within a failover group? My understanding of this is that it’s an automagically created list, but I’d be real happy to find out I’m misunderstanding the docs :)
~Mark
mark.flint@sanger.ac.uk
I believe you'll have to monkey with the failover policy on your LIFs if you want to control it. When using nextavail, I don't believe you can control order. When using priority, you can IIRC.
From page 52 of the cDOT 8.2 Network Management Guide:
* -failover-policy: Enables you to specify the order in which the network ports are chosen during a LIF failover and enables you to prevent a LIF from failing over. This parameter can have one of the following values:
* nextavail (default): Enables a LIF to fail over to the next available port, preferring a port on the current node. In some instances, a LIF configured with the nextavail failover policy selects a failover port on a remote node, even though a failover port is available on the local node. No outages will be seen in the cluster, because the LIFs continue to be hosted on valid failover ports.
* priority: Enables a LIF to fail over to the first available port specified in the user-defined failover group (failover targets can be shown with the network interface show - failover command).
* disabled: Disables (prevents) a LIF from failing over.
-- Brandon Kitchen Datalink 919-606-6766 www.datalink.comhttp://www.datalink.com/ Datalink OneCall Support Phone: 800.291.3230 Follow us on: Twitterhttp://twitter.com/datalinkcorp l Bloghttp://blog.datalink.com/ l Facebookhttp://www.facebook.com/datalinkcorp
On May 28, 2015, at 10:56 AM, Mark Flint <mf1@sanger.ac.ukmailto:mf1@sanger.ac.uk> wrote:
Does anyone know if you can re-order the entries within a failover group? My understanding of this is that it’s an automagically created list, but I’d be real happy to find out I’m misunderstanding the docs :)
~Mark
mark.flint@sanger.ac.ukmailto:mark.flint@sanger.ac.uk
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
I believe Brandon is correct here, you will need to specify the order of interfaces manually if you use this option so take care when building your lists as well. Nextavail usually does the job but I have seen some instances where caution wasn't taken building the failover group and it didn't work properly. So paying all due attention to the buildout of failover groups is really important no matter which option you use here (except disabled, for obvious reasons).
Good luck!
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Brandon Kitchen Sent: Thursday, May 28, 2015 10:22 AM To: Mark Flint Cc: Toasters Subject: Re: CDOT failover groups in 8.2.1P6
I believe you'll have to monkey with the failover policy on your LIFs if you want to control it. When using nextavail, I don't believe you can control order. When using priority, you can IIRC.
From page 52 of the cDOT 8.2 Network Management Guide:
* -failover-policy: Enables you to specify the order in which the network ports are chosen during a LIF failover and enables you to prevent a LIF from failing over. This parameter can have one of the following values:
* nextavail (default): Enables a LIF to fail over to the next available port, preferring a port on the current node. In some instances, a LIF configured with the nextavail failover policy selects a failover port on a remote node, even though a failover port is available on the local node. No outages will be seen in the cluster, because the LIFs continue to be hosted on valid failover ports.
* priority: Enables a LIF to fail over to the first available port specified in the user-defined failover group (failover targets can be shown with the network interface show - failover command).
* disabled: Disables (prevents) a LIF from failing over.
-- Brandon Kitchen Datalink 919-606-6766 www.datalink.comhttp://www.datalink.com/ Datalink OneCall Support Phone: 800.291.3230 Follow us on: Twitterhttp://twitter.com/datalinkcorp l Bloghttp://blog.datalink.com/ l Facebookhttp://www.facebook.com/datalinkcorp
On May 28, 2015, at 10:56 AM, Mark Flint <mf1@sanger.ac.ukmailto:mf1@sanger.ac.uk> wrote:
Does anyone know if you can re-order the entries within a failover group? My understanding of this is that it's an automagically created list, but I'd be real happy to find out I'm misunderstanding the docs :)
~Mark
mark.flint@sanger.ac.ukmailto:mark.flint@sanger.ac.uk
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
There's probably a good reason for not going 8.3 (first major release) but it's worth mentioning Failover Groups change significantly in cDOT 8.3:
In 8.3 the choices are: system-defined local-only sfo-partner-only ipspace-wide disabled broadcast-domain-wide
Maybe worth taking a look at 8.3P1 as well???
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-groups-i... Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.
It is still totally unclear to me what happens to failover policies after update to 8.3. Are existing 8.2 failover policies retained or replaced by one of documented 8.3 failover policy?
I could not find any documentation on this.
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Martin Sent: Friday, May 29, 2015 9:17 AM To: toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
There's probably a good reason for not going 8.3 (first major release) but it's worth mentioning Failover Groups change significantly in cDOT 8.3:
In 8.3 the choices are: system-defined local-only sfo-partner-only ipspace-wide disabled broadcast-domain-wide
Maybe worth taking a look at 8.3P1 as well???
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-groups-i... Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
In our experience with 8.2/8.3 upgrades, 8.2 failover groups carry over. CDOT docs are still very incomplete.
.
On May 29, 2015, at 12:00 AM, Borzenkov, Andrei andrei.borzenkov@ts.fujitsu.com wrote:
It is still totally unclear to me what happens to failover policies after update to 8.3. Are existing 8.2 failover policies retained or replaced by one of documented 8.3 failover policy?
I could not find any documentation on this.
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Martin Sent: Friday, May 29, 2015 9:17 AM To: toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
There's probably a good reason for not going 8.3 (first major release) but it's worth mentioning Failover Groups change significantly in cDOT 8.3:
In 8.3 the choices are: system-defined local-only sfo-partner-only ipspace-wide disabled broadcast-domain-wide
Maybe worth taking a look at 8.3P1 as well???
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-groups-i... Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
I have just done some 8.2.2 upgrades to 8.3P1 and found during the upgrade broadcast domains corresponding to the various networks are created along with failover groups of the same name and the original failover groups are retained and mapped to the relevant broadcast domains.
What I am not clear on is if the failover groups are going to be legacy and how this affects intercluster replication LIFs which are local to a node.
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-groups-i... Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.
I’d guess (!) that they’ll use the local-only group, but will await your next discovery :)
~Mark
On 29 May 2015, at 09:10, Martin martin@leggatt.me.uk wrote:
I have just done some 8.2.2 upgrades to 8.3P1 and found during the upgrade broadcast domains corresponding to the various networks are created along with failover groups of the same name and the original failover groups are retained and mapped to the relevant broadcast domains.
What I am not clear on is if the failover groups are going to be legacy and how this affects intercluster replication LIFs which are local to a node.
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-groups-i... Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
It would be extremely helpful if you gave examples if configuration before and after upgrade. In particular, it is not clear to me how broadcast domains are created and how failover groups are mapped to them.
After new installation only single default broadcast domain exists, because system jas really no way to know how pirts are connected.
Thank you!
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Martin Sent: Friday, May 29, 2015 11:11 AM To: toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
I have just done some 8.2.2 upgrades to 8.3P1 and found during the upgrade broadcast domains corresponding to the various networks are created along with failover groups of the same name and the original failover groups are retained and mapped to the relevant broadcast domains.
What I am not clear on is if the failover groups are going to be legacy and how this affects intercluster replication LIFs which are local to a node.
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-groups-i... Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Have you all had a chance to review TR-4182?
http://www.netapp.com/us/media/tr-4182.pdf
- Broadcast domains are covered on page 13
- Failover groups on page 18
- 8.3 specific info on page 19
If you need clarification on anything in the doc, let me know and I can inform the author.
On 5/29/15, 4:44 AM, "Borzenkov, Andrei" andrei.borzenkov@ts.fujitsu.com wrote:
It would be extremely helpful if you gave examples if configuration before and after upgrade. In particular, it is not clear to me how broadcast domains are created and how failover groups are mapped to them.
After new installation only single default broadcast domain exists, because system jas really no way to know how pirts are connected.
Thank you!
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Martin Sent: Friday, May 29, 2015 11:11 AM To: toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
I have just done some 8.2.2 upgrades to 8.3P1 and found during the upgrade broadcast domains corresponding to the various networks are created along with failover groups of the same name and the original failover groups are retained and mapped to the relevant broadcast domains.
What I am not clear on is if the failover groups are going to be legacy and how this affects intercluster replication LIFs which are local to a node.
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-groups -in-8-2-1P6-tp26685p26692.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
It does not really explain what happens during upgrade from 8.2 to 8.3. It could be inferred that previous policies from 8.2 will remain in effect based on
--><-- "priority" and "nextavail" failover policies will no longer be exposed through the user interface. --><--
But I was rather confused when Martin said "broadcast domains corresponding to the various networks are created".
-----Original Message----- From: Parisi, Justin [mailto:Justin.Parisi@netapp.com] Sent: Friday, May 29, 2015 5:51 PM To: Borzenkov, Andrei; Martin; toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
Have you all had a chance to review TR-4182?
http://www.netapp.com/us/media/tr-4182.pdf
- Broadcast domains are covered on page 13
- Failover groups on page 18
- 8.3 specific info on page 19
If you need clarification on anything in the doc, let me know and I can inform the author.
On 5/29/15, 4:44 AM, "Borzenkov, Andrei" andrei.borzenkov@ts.fujitsu.com wrote:
It would be extremely helpful if you gave examples if configuration before and after upgrade. In particular, it is not clear to me how broadcast domains are created and how failover groups are mapped to them.
After new installation only single default broadcast domain exists, because system jas really no way to know how pirts are connected.
Thank you!
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Martin Sent: Friday, May 29, 2015 11:11 AM To: toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
I have just done some 8.2.2 upgrades to 8.3P1 and found during the upgrade broadcast domains corresponding to the various networks are created along with failover groups of the same name and the original failover groups are retained and mapped to the relevant broadcast domains.
What I am not clear on is if the failover groups are going to be legacy and how this affects intercluster replication LIFs which are local to a node.
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-gro ups -in-8-2-1P6-tp26685p26692.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Thanks for the feedback. I¹ll ping the author to get clarification and report back. :)
On 5/29/15, 11:05 AM, "Borzenkov, Andrei" andrei.borzenkov@ts.fujitsu.com wrote:
It does not really explain what happens during upgrade from 8.2 to 8.3. It could be inferred that previous policies from 8.2 will remain in effect based on
--><-- "priority" and "nextavail" failover policies will no longer be exposed through the user interface. --><--
But I was rather confused when Martin said "broadcast domains corresponding to the various networks are created".
-----Original Message----- From: Parisi, Justin [mailto:Justin.Parisi@netapp.com] Sent: Friday, May 29, 2015 5:51 PM To: Borzenkov, Andrei; Martin; toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
Have you all had a chance to review TR-4182?
http://www.netapp.com/us/media/tr-4182.pdf
Broadcast domains are covered on page 13
Failover groups on page 18
8.3 specific info on page 19
If you need clarification on anything in the doc, let me know and I can inform the author.
On 5/29/15, 4:44 AM, "Borzenkov, Andrei" andrei.borzenkov@ts.fujitsu.com wrote:
It would be extremely helpful if you gave examples if configuration before and after upgrade. In particular, it is not clear to me how broadcast domains are created and how failover groups are mapped to them.
After new installation only single default broadcast domain exists, because system jas really no way to know how pirts are connected.
Thank you!
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Martin Sent: Friday, May 29, 2015 11:11 AM To: toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
I have just done some 8.2.2 upgrades to 8.3P1 and found during the upgrade broadcast domains corresponding to the various networks are created along with failover groups of the same name and the original failover groups are retained and mapped to the relevant broadcast domains.
What I am not clear on is if the failover groups are going to be legacy and how this affects intercluster replication LIFs which are local to a node.
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-gro ups -in-8-2-1P6-tp26685p26692.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
After upgrade, all existing 8.2 failover groups are retained and broadcast-domain is created of the same name. So to rename you have to rename the broadcast-domain since the failover-group is tied to it. Often after 8.2 to 8.3 upgrades, I modify the failover-groups. For example, we usually have extra failover-groups for local interfaces, node management and intercluster...so after upgrade, we usually delete those individual per-node failover groups (delete the broadcast domain), then use a broadcast domain with ports on all controllers specifying a local-only policy. I like it a lot better and tend to use all broadcast-domains to manage failover-groups now... the exception to creating additional manual failover-groups is when there is a mix of 1Gb and 10Gb then we create additional for the different speeds.
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Borzenkov, Andrei Sent: Friday, May 29, 2015 8:06 AM To: Parisi, Justin; Martin; toasters@teaparty.net Subject: RE: CDOT failover groups in 8.2.1P6
It does not really explain what happens during upgrade from 8.2 to 8.3. It could be inferred that previous policies from 8.2 will remain in effect based on
--><-- "priority" and "nextavail" failover policies will no longer be exposed through the user interface. --><--
But I was rather confused when Martin said "broadcast domains corresponding to the various networks are created".
-----Original Message----- From: Parisi, Justin [mailto:Justin.Parisi@netapp.com] Sent: Friday, May 29, 2015 5:51 PM To: Borzenkov, Andrei; Martin; toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
Have you all had a chance to review TR-4182?
http://www.netapp.com/us/media/tr-4182.pdf
- Broadcast domains are covered on page 13
- Failover groups on page 18
- 8.3 specific info on page 19
If you need clarification on anything in the doc, let me know and I can inform the author.
On 5/29/15, 4:44 AM, "Borzenkov, Andrei" andrei.borzenkov@ts.fujitsu.com wrote:
It would be extremely helpful if you gave examples if configuration before and after upgrade. In particular, it is not clear to me how broadcast domains are created and how failover groups are mapped to them.
After new installation only single default broadcast domain exists, because system jas really no way to know how pirts are connected.
Thank you!
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Martin Sent: Friday, May 29, 2015 11:11 AM To: toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
I have just done some 8.2.2 upgrades to 8.3P1 and found during the upgrade broadcast domains corresponding to the various networks are created along with failover groups of the same name and the original failover groups are retained and mapped to the relevant broadcast domains.
What I am not clear on is if the failover groups are going to be legacy and how this affects intercluster replication LIFs which are local to a node.
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-gro ups -in-8-2-1P6-tp26685p26692.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
_______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
What is unclear to me - failover groups can be overlapping (if my memory serves me right, I can add port to multiple failover groups) and broadcast domains cannot. This makes it impossible in general to create broadcast domain for each failover group.
If there is requirement for failover groups being non-overlapping I cannot find it in documentation.
So I wonder how upgrade handles this situation.
-----Original Message----- From: Gelb, Scott [mailto:scott@redeight.com] Sent: Friday, May 29, 2015 10:38 PM To: Borzenkov, Andrei; Parisi, Justin; Martin; toasters@teaparty.net Subject: RE: CDOT failover groups in 8.2.1P6
After upgrade, all existing 8.2 failover groups are retained and broadcast-domain is created of the same name. So to rename you have to rename the broadcast-domain since the failover-group is tied to it. Often after 8.2 to 8.3 upgrades, I modify the failover-groups. For example, we usually have extra failover-groups for local interfaces, node management and intercluster...so after upgrade, we usually delete those individual per-node failover groups (delete the broadcast domain), then use a broadcast domain with ports on all controllers specifying a local-only policy. I like it a lot better and tend to use all broadcast-domains to manage failover-groups now... the exception to creating additional manual failover-groups is when there is a mix of 1Gb and 10Gb then we create additional for the different speeds.
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Borzenkov, Andrei Sent: Friday, May 29, 2015 8:06 AM To: Parisi, Justin; Martin; toasters@teaparty.net Subject: RE: CDOT failover groups in 8.2.1P6
It does not really explain what happens during upgrade from 8.2 to 8.3. It could be inferred that previous policies from 8.2 will remain in effect based on
--><-- "priority" and "nextavail" failover policies will no longer be exposed through the user interface. --><--
But I was rather confused when Martin said "broadcast domains corresponding to the various networks are created".
-----Original Message----- From: Parisi, Justin [mailto:Justin.Parisi@netapp.com] Sent: Friday, May 29, 2015 5:51 PM To: Borzenkov, Andrei; Martin; toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
Have you all had a chance to review TR-4182?
http://www.netapp.com/us/media/tr-4182.pdf
- Broadcast domains are covered on page 13
- Failover groups on page 18
- 8.3 specific info on page 19
If you need clarification on anything in the doc, let me know and I can inform the author.
On 5/29/15, 4:44 AM, "Borzenkov, Andrei" andrei.borzenkov@ts.fujitsu.com wrote:
It would be extremely helpful if you gave examples if configuration before and after upgrade. In particular, it is not clear to me how broadcast domains are created and how failover groups are mapped to them.
After new installation only single default broadcast domain exists, because system jas really no way to know how pirts are connected.
Thank you!
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Martin Sent: Friday, May 29, 2015 11:11 AM To: toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
I have just done some 8.2.2 upgrades to 8.3P1 and found during the upgrade broadcast domains corresponding to the various networks are created along with failover groups of the same name and the original failover groups are retained and mapped to the relevant broadcast domains.
What I am not clear on is if the failover groups are going to be legacy and how this affects intercluster replication LIFs which are local to a node.
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-gro ups -in-8-2-1P6-tp26685p26692.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
_______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
I currently have non-overlapping failover groups on 8.2.1P3 nodes, can experiment a bit if needed. I'm about to upgrade those nodes to 8.3
Vladimir
On Mon, Jun 1, 2015 at 8:45 AM, Borzenkov, Andrei andrei.borzenkov@ts.fujitsu.com wrote:
What is unclear to me - failover groups can be overlapping (if my memory serves me right, I can add port to multiple failover groups) and broadcast domains cannot. This makes it impossible in general to create broadcast domain for each failover group.
If there is requirement for failover groups being non-overlapping I cannot find it in documentation.
So I wonder how upgrade handles this situation.
I upgraded 2 clusters today with overlapping failover groups... the upgrade leaves the failover groups intact and creates a broadcast-domain (and corresponding failover-group) with all of the combined ports...but leaves the lifs as is on the prior failover-group
For example on 8.2
fg-cluster-mgmt node1:e0a,node2:e0a fg-node1-mgmt node1:e0a,node1:e0M fg-node2-mgmt node2:e0a,node2:e0M
Prior to 8.3, we didn’t have a local only policy so had e0a overlapping between all 3 failover groups. That way the local management could also use e0M as backup. The end result was a new broadcast domain with all 4 ports (e0a and e0M on each controller named 10.x.x.x), a failover-group 10.x.x.x from the broadcast-domain, then the same manual failover-groups prior to upgrade.
One other note though...after upgrade, all SVM data lifs had a failover-policy of "system-defined" after the upgrade. This allows failover to the home-node and non-sfo partner...in a 2-node cluster there is no non-sfo partner. I modified these to "broadcast-domain-wide" after upgrade. In many cases we can eliminate manual failover groups and name broadcast-domains per vlan, but in this case above with a mix of 1Gb and e0M (or if you have 10Gb and 1Gb) it makes sense to have manual failover groups so slower speed ports are not used for data.
-----Original Message----- From: vladimir.zhigulin@gmail.com [mailto:vladimir.zhigulin@gmail.com] On Behalf Of Momonth Sent: Wednesday, June 10, 2015 4:04 AM To: Borzenkov, Andrei Cc: Gelb, Scott; Parisi, Justin; Martin; toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
I currently have non-overlapping failover groups on 8.2.1P3 nodes, can experiment a bit if needed. I'm about to upgrade those nodes to 8.3
Vladimir
On Mon, Jun 1, 2015 at 8:45 AM, Borzenkov, Andrei andrei.borzenkov@ts.fujitsu.com wrote:
What is unclear to me - failover groups can be overlapping (if my memory serves me right, I can add port to multiple failover groups) and broadcast domains cannot. This makes it impossible in general to create broadcast domain for each failover group.
If there is requirement for failover groups being non-overlapping I cannot find it in documentation.
So I wonder how upgrade handles this situation.
Thank you!
Yes, that's logical and consistent.
I suspect description of system-defined failover policy in documentation is incomplete and misleading. This would imply two-node cluster needs different policy, and there is nothing anywhere about it. Also example in documentation contradicts description:
The following command displays information about the failover targets for all LIFs in a two-node cluster. The Failover Targets row shows the (prioritized) list of node-port combinations for a given LIF.
cluster1::> network interface show -failover Logical Home Failover Failover Vserver Interface Node:Port Policy Group -------- ------------- --------------------- --------------- --------- ... vs1 data1 node1:e0e system-defined bcast1 Failover Targets: node1:e0e, node1:e0f, node2:e0e, node2:e0f
I /hope/ that system-defined is intelligent enough to realize that in two-node cluster the only available failover targets are on HA partner. May be Justin can chime in...
-----Original Message----- From: Gelb, Scott [mailto:scott@redeight.com] Sent: Wednesday, July 01, 2015 11:48 PM To: momonth@gmail.com; Borzenkov, Andrei Cc: Parisi, Justin; Martin; toasters@teaparty.net Subject: RE: CDOT failover groups in 8.2.1P6
I upgraded 2 clusters today with overlapping failover groups... the upgrade leaves the failover groups intact and creates a broadcast-domain (and corresponding failover-group) with all of the combined ports...but leaves the lifs as is on the prior failover-group
For example on 8.2
fg-cluster-mgmt node1:e0a,node2:e0a fg-node1-mgmt node1:e0a,node1:e0M fg-node2-mgmt node2:e0a,node2:e0M
Prior to 8.3, we didn’t have a local only policy so had e0a overlapping between all 3 failover groups. That way the local management could also use e0M as backup. The end result was a new broadcast domain with all 4 ports (e0a and e0M on each controller named 10.x.x.x), a failover-group 10.x.x.x from the broadcast-domain, then the same manual failover-groups prior to upgrade.
One other note though...after upgrade, all SVM data lifs had a failover-policy of "system-defined" after the upgrade. This allows failover to the home-node and non-sfo partner...in a 2-node cluster there is no non-sfo partner. I modified these to "broadcast-domain-wide" after upgrade. In many cases we can eliminate manual failover groups and name broadcast-domains per vlan, but in this case above with a mix of 1Gb and e0M (or if you have 10Gb and 1Gb) it makes sense to have manual failover groups so slower speed ports are not used for data.
-----Original Message----- From: vladimir.zhigulin@gmail.com [mailto:vladimir.zhigulin@gmail.com] On Behalf Of Momonth Sent: Wednesday, June 10, 2015 4:04 AM To: Borzenkov, Andrei Cc: Gelb, Scott; Parisi, Justin; Martin; toasters@teaparty.net Subject: Re: CDOT failover groups in 8.2.1P6
I currently have non-overlapping failover groups on 8.2.1P3 nodes, can experiment a bit if needed. I'm about to upgrade those nodes to 8.3
Vladimir
On Mon, Jun 1, 2015 at 8:45 AM, Borzenkov, Andrei andrei.borzenkov@ts.fujitsu.com wrote:
What is unclear to me - failover groups can be overlapping (if my memory serves me right, I can add port to multiple failover groups) and broadcast domains cannot. This makes it impossible in general to create broadcast domain for each failover group.
If there is requirement for failover groups being non-overlapping I cannot find it in documentation.
So I wonder how upgrade handles this situation.
I’ve been looking at it for some time, just waiting for the chance to get up to 8.2.1 first, then keep the overlords happy for a week, then I should be able to roll to 8.3, but it’ll probably take about 6 months to get there.
:)
~Mark
On 29 May 2015, at 07:16, Martin martin@leggatt.me.uk wrote:
There's probably a good reason for not going 8.3 (first major release) but it's worth mentioning Failover Groups change significantly in cDOT 8.3:
In 8.3 the choices are: system-defined local-only sfo-partner-only ipspace-wide disabled broadcast-domain-wide
Maybe worth taking a look at 8.3P1 as well???
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/CDOT-failover-groups-i... Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
-
Borzenkov, Andrei -
Brandon Kitchen -
Francis Kim -
Gelb, Scott -
Mark Flint -
Martin -
Momonth -
Parisi, Justin -
Tony Bar