vifmgr.lifs.noredundancy

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

vifmgr.lifs.noredundancy

TAYLOR DANIEL

Hello,

Since the dawn of its inception by another third party we have been getting these messages for both intercluster LIFs:


Filer: ntap-a

Time: Sun, Apr 16 00:15:05 2017 +0100

Severity: LOG_ALERT

Message: vifmgr.lifs.noredundancy: No redundancy in the failover configuration for 1 LIFs assigned to node “ntap-a”. LIFs:

uk:ntap_a_intercluster

Description: This message occurs when one or more logical interfaces (LIFs) are configured to use a failover policy that implies failover to one or more ports but have no failover targets beyond their home ports. If any affected home port or home node is offline or unavailable, the corresponding LIFs will be operationally down and unable to serve data.

Action: Add additional ports to the broadcast domains or failover groups used by the affected LIFs, or modify each LIF's failover policy to include one or more nodes with available failover targets. For example, the “broadcast-domain-wide”

failover policy will consider all failover targets in a LIF's failover group.

Use the “network interface show -failover” command to review the currently assigned failover targets for each LIF.

Source: vifmgr

Index: 6740328

[Note: This email message is sent using a deprecated event routing mechanism.

For information, search the knowledgebase of the NetApp support web site for "convert existing event configurations in Data ONTAP 9.0."]


This intercluster LIF is part of an IFGRP which is made up of two vlanned ports, so by definition is redundant. 

My question, is this a bug in the error reporting or is there some configuration which is not supported here? 

We have another cluster which is configured with standard vlanned ports per node as opposed to ifgrps and this doesn’t seem to complain. Just not sure if this is a problem or not, or if it’s something we can suppress?

Running FAS8040, 9.1P2.

Thanks

Dan


_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: vifmgr.lifs.noredundancy

Tim McCarthy
As long as I know I have the lacp set up properly, I ignore this error.

Ideally, it is evidently preferred to have a couple extra ports lying around to use for the inter cluster lifs. I know a lot of customers can't do that and simply reuse the ifgrp like you're doing.


Spelling errors courtesy of Swype for iOS...

Tim McCarthy, Consultant at Presidio

From: [hidden email] <[hidden email]> on behalf of TAYLOR DANIEL <[hidden email]>
Sent: Thursday, April 20, 2017 7:40:45 AM
To: toasters
Subject: vifmgr.lifs.noredundancy
 

Hello,

Since the dawn of its inception by another third party we have been getting these messages for both intercluster LIFs:


Filer: ntap-a

Time: Sun, Apr 16 00:15:05 2017 +0100

Severity: LOG_ALERT

Message: vifmgr.lifs.noredundancy: No redundancy in the failover configuration for 1 LIFs assigned to node “ntap-a”. LIFs:

uk:ntap_a_intercluster

Description: This message occurs when one or more logical interfaces (LIFs) are configured to use a failover policy that implies failover to one or more ports but have no failover targets beyond their home ports. If any affected home port or home node is offline or unavailable, the corresponding LIFs will be operationally down and unable to serve data.

Action: Add additional ports to the broadcast domains or failover groups used by the affected LIFs, or modify each LIF's failover policy to include one or more nodes with available failover targets. For example, the “broadcast-domain-wide”

failover policy will consider all failover targets in a LIF's failover group.

Use the “network interface show -failover” command to review the currently assigned failover targets for each LIF.

Source: vifmgr

Index: 6740328

[Note: This email message is sent using a deprecated event routing mechanism.

For information, search the knowledgebase of the NetApp support web site for "convert existing event configurations in Data ONTAP 9.0."]


This intercluster LIF is part of an IFGRP which is made up of two vlanned ports, so by definition is redundant. 

My question, is this a bug in the error reporting or is there some configuration which is not supported here? 

We have another cluster which is configured with standard vlanned ports per node as opposed to ifgrps and this doesn’t seem to complain. Just not sure if this is a problem or not, or if it’s something we can suppress?

Running FAS8040, 9.1P2.

Thanks

Dan


_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: vifmgr.lifs.noredundancy

Christopher S Eno
In reply to this post by TAYLOR DANIEL
Yes, very annoying.  Getting these alerts for node management lifs, snapmirror lifs (built on 4 phys ports), etc.

We're confident in our redundancy and don't want to change things just to make bogus alert emails stop.  

Wondering if there's a way in 9.1 to manage these alerts coming from the nodes.  Currently getting inundated with failed login attempt emails as infosec does their vulnerability scans. 

Sent from my iPhone

On Apr 20, 2017, at 7:40 AM, TAYLOR DANIEL <[hidden email]> wrote:

Hello,

Since the dawn of its inception by another third party we have been getting these messages for both intercluster LIFs:


Filer: ntap-a

Time: Sun, Apr 16 00:15:05 2017 +0100

Severity: LOG_ALERT

Message: vifmgr.lifs.noredundancy: No redundancy in the failover configuration for 1 LIFs assigned to node “ntap-a”. LIFs:

uk:ntap_a_intercluster

Description: This message occurs when one or more logical interfaces (LIFs) are configured to use a failover policy that implies failover to one or more ports but have no failover targets beyond their home ports. If any affected home port or home node is offline or unavailable, the corresponding LIFs will be operationally down and unable to serve data.

Action: Add additional ports to the broadcast domains or failover groups used by the affected LIFs, or modify each LIF's failover policy to include one or more nodes with available failover targets. For example, the “broadcast-domain-wide”

failover policy will consider all failover targets in a LIF's failover group.

Use the “network interface show -failover” command to review the currently assigned failover targets for each LIF.

Source: vifmgr

Index: 6740328

[Note: This email message is sent using a deprecated event routing mechanism.

For information, search the knowledgebase of the NetApp support web site for "convert existing event configurations in Data ONTAP 9.0."]


This intercluster LIF is part of an IFGRP which is made up of two vlanned ports, so by definition is redundant. 

My question, is this a bug in the error reporting or is there some configuration which is not supported here? 

We have another cluster which is configured with standard vlanned ports per node as opposed to ifgrps and this doesn’t seem to complain. Just not sure if this is a problem or not, or if it’s something we can suppress?

Running FAS8040, 9.1P2.

Thanks

Dan

_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters

_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: vifmgr.lifs.noredundancy

André M. Clark
For intercluster and node management LIFs, if you're not setting up redundant ports, which most don't, simply modify the failover-policy for those LIFs to disabled and the alerts will stop.

Sent from BlueMail
On Apr 20, 2017, at 07:20, "s.eno" <[hidden email]> wrote:
Yes, very annoying.  Getting these alerts for node management lifs, snapmirror lifs (built on 4 phys ports), etc.

We're confident in our redundancy and don't want to change things just to make bogus alert emails stop.  

Wondering if there's a way in 9.1 to manage these alerts coming from the nodes.  Currently getting inundated with failed login attempt emails as infosec does their vulnerability scans. 

Sent from my iPhone

On Apr 20, 2017, at 7:40 AM, TAYLOR DANIEL <[hidden email]> wrote:

Hello,

Since the dawn of its inception by another third party we have been getting these messages for both intercluster LIFs:


Filer: ntap-a

Time: Sun, Apr 16 00:15:05 2017 +0100

Severity: LOG_ALERT

Message: vifmgr.lifs.noredundancy: No redundancy in the failover configuration for 1 LIFs assigned to node “ntap-a”. LIFs:

uk:ntap_a_intercluster

Description: This message occurs when one or more logical interfaces (LIFs) are configured to use a failover policy that implies failover to one or more ports but have no failover targets beyond their home ports. If any affected home port or home node is offline or unavailable, the corresponding LIFs will be operationally down and unable to serve data.

Action: Add additional ports to the broadcast domains or failover groups used by the affected LIFs, or modify each LIF's failover policy to include one or more nodes with available failover targets. For example, the “broadcast-domain-wide”

failover policy will consider all failover targets in a LIF's failover group.

Use the “network interface show -failover” command to review the currently assigned failover targets for each LIF.

Source: vifmgr

Index: 6740328

[Note: This email message is sent using a deprecated event routing mechanism.

For information, search the knowledgebase of the NetApp support web site for "convert existing event configurations in Data ONTAP 9.0."]


This intercluster LIF is part of an IFGRP which is made up of two vlanned ports, so by definition is redundant. 

My question, is this a bug in the error reporting or is there some configuration which is not supported here? 

We have another cluster which is configured with standard vlanned ports per node as opposed to ifgrps and this doesn’t seem to complain. Just not sure if this is a problem or not, or if it’s something we can suppress?

Running FAS8040, 9.1P2.

Thanks

Dan

_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters


Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters

_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Re: vifmgr.lifs.noredundancy

Weber, Mark A

And to stop the failed login alerts add a filter:

event filter create -filter-name <filter-name>

event filter rule add -filter-name <filter-name> -type exclude -message-name security.invalid.login -position 1

event notification modify -ID <id of the whatever you are using> -filter-name <filter-name>

 

m

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of André M. Clark
Sent: Thursday, April 20, 2017 9:11 AM
To: s.eno <[hidden email]>
Cc: [hidden email]
Subject: Re: vifmgr.lifs.noredundancy

 

For intercluster and node management LIFs, if you're not setting up redundant ports, which most don't, simply modify the failover-policy for those LIFs to disabled and the alerts will stop.

Sent from BlueMail

On Apr 20, 2017, at 07:20, "s.eno" <[hidden email]> wrote:

Yes, very annoying.  Getting these alerts for node management lifs, snapmirror lifs (built on 4 phys ports), etc.

 

We're confident in our redundancy and don't want to change things just to make bogus alert emails stop.  

 

Wondering if there's a way in 9.1 to manage these alerts coming from the nodes.  Currently getting inundated with failed login attempt emails as infosec does their vulnerability scans. 

Sent from my iPhone


On Apr 20, 2017, at 7:40 AM, TAYLOR DANIEL <[hidden email]> wrote:

Hello,

Since the dawn of its inception by another third party we have been getting these messages for both intercluster LIFs:

 

Filer: ntap-a

Time: Sun, Apr 16 00:15:05 2017 +0100

Severity: LOG_ALERT

Message: vifmgr.lifs.noredundancy: No redundancy in the failover configuration for 1 LIFs assigned to node “ntap-a”. LIFs:

uk:ntap_a_intercluster

Description: This message occurs when one or more logical interfaces (LIFs) are configured to use a failover policy that implies failover to one or more ports but have no failover targets beyond their home ports. If any affected home port or home node is offline or unavailable, the corresponding LIFs will be operationally down and unable to serve data.

Action: Add additional ports to the broadcast domains or failover groups used by the affected LIFs, or modify each LIF's failover policy to include one or more nodes with available failover targets. For example, the “broadcast-domain-wide”

failover policy will consider all failover targets in a LIF's failover group.

Use the “network interface show -failover” command to review the currently assigned failover targets for each LIF.

Source: vifmgr

Index: 6740328

[Note: This email message is sent using a deprecated event routing mechanism.

For information, search the knowledgebase of the NetApp support web site for "convert existing event configurations in Data ONTAP 9.0."]

 

This intercluster LIF is part of an IFGRP which is made up of two vlanned ports, so by definition is redundant. 

My question, is this a bug in the error reporting or is there some configuration which is not supported here? 

We have another cluster which is configured with standard vlanned ports per node as opposed to ifgrps and this doesn’t seem to complain. Just not sure if this is a problem or not, or if it’s something we can suppress?

Running FAS8040, 9.1P2.

Thanks

Dan

_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters



Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters

_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: vifmgr.lifs.noredundancy

TAYLOR DANIEL
In reply to this post by André M. Clark

Hi André,

Thanks.  That actually makes perfect sense.

Dan


On 20 April 2017 at 15:10 "André M. Clark" <[hidden email]> wrote:

For intercluster and node management LIFs, if you're not setting up redundant ports, which most don't, simply modify the failover-policy for those LIFs to disabled and the alerts will stop.

Sent from BlueMail
On Apr 20, 2017, at 07:20, "s.eno" <[hidden email]> wrote:
Yes, very annoying.  Getting these alerts for node management lifs, snapmirror lifs (built on 4 phys ports), etc.

We're confident in our redundancy and don't want to change things just to make bogus alert emails stop.  

Wondering if there's a way in 9.1 to manage these alerts coming from the nodes.  Currently getting inundated with failed login attempt emails as infosec does their vulnerability scans. 

Sent from my iPhone

On Apr 20, 2017, at 7:40 AM, TAYLOR DANIEL <[hidden email]> wrote:

Hello,

Since the dawn of its inception by another third party we have been getting these messages for both intercluster LIFs:


Filer: ntap-a

Time: Sun, Apr 16 00:15:05 2017 +0100

Severity: LOG_ALERT

Message: vifmgr.lifs.noredundancy: No redundancy in the failover configuration for 1 LIFs assigned to node “ntap-a”. LIFs:

uk:ntap_a_intercluster

Description: This message occurs when one or more logical interfaces (LIFs) are configured to use a failover policy that implies failover to one or more ports but have no failover targets beyond their home ports. If any affected home port or home node is offline or unavailable, the corresponding LIFs will be operationally down and unable to serve data.

Action: Add additional ports to the broadcast domains or failover groups used by the affected LIFs, or modify each LIF's failover policy to include one or more nodes with available failover targets. For example, the “broadcast-domain-wide”

failover policy will consider all failover targets in a LIF's failover group.

Use the “network interface show -failover” command to review the currently assigned failover targets for each LIF.

Source: vifmgr

Index: 6740328

[Note: This email message is sent using a deprecated event routing mechanism.

For information, search the knowledgebase of the NetApp support web site for "convert existing event configurations in Data ONTAP 9.0."]


This intercluster LIF is part of an IFGRP which is made up of two vlanned ports, so by definition is redundant. 

My question, is this a bug in the error reporting or is there some configuration which is not supported here? 

We have another cluster which is configured with standard vlanned ports per node as opposed to ifgrps and this doesn’t seem to complain. Just not sure if this is a problem or not, or if it’s something we can suppress?

Running FAS8040, 9.1P2.

Thanks

Dan

_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters


Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters


 


_______________________________________________
Toasters mailing list
[hidden email]
http://www.teaparty.net/mailman/listinfo/toasters
Loading...