Network and Storage Protocols

Native vlan ports show degraded after upgrade to ONTAP 9.13.1

Fredric
3,472 Views

Hi,

I have a couple of new A400 systems. After upgrading them to Ontap 9.13.1.P1 I noticed that the health was degraded on the link aggregation port and the member ports.

 

There are an KB about this, Native vlan ports show degraded after upgrade to ONTAP 9.13.1 - NetApp Knowledge Base

 

But I don't understand how to solve it, should I create a "native vlan" in the Cisco switches config for the lacp Etherchannel?

I seems to just be a cosmetic problem, I can ignore the health status (net port modify -node <node> -port <port> -ignore-health-status true)

 

This is the status today for one of a new cluster (not in production). 

Should the ifgrp ports (a0a, e0e, e0f) be in a broadcast domain? 

 

cl05::> network port ifgrp show -node cl05-01
Port Distribution Active Node IfGrp Function MAC Address Ports Ports
-------- ---------- ------------ ----------------- ------- -------------------
cl05-01 a0a ip xx:xx:xx:xx:xx:xx full e0e, e0f

 

cl05::> network port show -node cl05-01

Node: cl05-01
Speed(Mbps) Health
Port IPspace Broadcast Domain Link MTU Admin/Oper Status
--------- ------------ ---------------- ---- ---- ----------- --------
a0a Default - up 1500 -/- degraded
a0a-10 Default vlan-10 up 1500 -/- healthy
a0a-12 Default vlan-12 up 1500 -/- healthy
a0a-18 Default vlan-18 up 1500 -/- healthy
a0a-1905 Default vlan-1905 up 1500 -/- healthy
a0a-20 Default vlan-20 up 1500 -/- healthy
a0a-51 Default Default up 1500 -/- healthy
e0M Default Default up 1500 auto/1000 healthy
e0e Default - up 1500 auto/10000 degraded
e0f Default - up 1500 auto/10000 degraded
e0g Default - down 1500 auto/- -
e0h Default - down 1500 auto/- -
e3a Cluster Cluster up 9000 auto/100000
healthy
e3b Cluster Cluster up 9000 auto/100000
healthy
14 entries were displayed.

cl05::>


cl05::> network port reachability show -node cl05-01
Node Port Expected Reachability Reachability Status
--------- -------- ------------------------------------ ---------------------
cl05-01
a0a - no-reachability
a0a-10 Default:vlan-10 ok
a0a-12 Default:vlan-12 ok
a0a-18 Default:vlan-18 ok
a0a-1905 Default:vlan-1905 ok
a0a-20 Default:vlan-20 ok
a0a-51 Default:Default ok
e0M Default:Default ok
e0e - no-reachability
e0f - no-reachability
e0g - no-reachability
e0h - no-reachability
e3a Cluster:Cluster ok
e3b Cluster:Cluster ok

1 ACCEPTED SOLUTION

PetterStene
3,056 Views

It is a known bug:
NetApp Support Site - BURT - 1508111

It seems to be only cosmetic, but it also triggers an "Unhealthy" warning on the PRTG sensor for the NIC.

References:
Native VLAN ports show degraded after upgrade to ONTAP 9.13.1 - NetApp Knowledge Base
Ifgrp member ports show degraded while ifgrp shows reachable after upgrade to ONTAP 9.13.1 - NetApp Knowledge Base

Interestingly enough it is marked as fixed, but still affects the latest patches for the latest release of ONTAP.

Updated last 11-Sep-2023, so I expect NetApp to be working on this with priority. Bug is severity P2

--Petter

View solution in original post

8 REPLIES 8

PetterStene
3,057 Views

It is a known bug:
NetApp Support Site - BURT - 1508111

It seems to be only cosmetic, but it also triggers an "Unhealthy" warning on the PRTG sensor for the NIC.

References:
Native VLAN ports show degraded after upgrade to ONTAP 9.13.1 - NetApp Knowledge Base
Ifgrp member ports show degraded while ifgrp shows reachable after upgrade to ONTAP 9.13.1 - NetApp Knowledge Base

Interestingly enough it is marked as fixed, but still affects the latest patches for the latest release of ONTAP.

Updated last 11-Sep-2023, so I expect NetApp to be working on this with priority. Bug is severity P2

--Petter

Fredric
3,049 Views

Yes, you are right. Netapp support confirmed that last week. I forgot to update this thread.

According to Netapp it will be fixed in 9.14 in November.

Thanks!

 

//Fredric

toyo4
2,947 Views

I believe 9.13.1P3 will be released soon.  Does anyone have information on whether the fix for 1508111 will be included in this release or not ?

Thanks

Thomas1985
2,670 Views

No the problem is not fixed in Ontap 9.13.1P3. I updated our clusters yesterday to version 9.13.1P3 and now I have the same problems.

toyo4
2,542 Views

Thanks, Thomas1985 !

 

Fredric
2,945 Views

Hi,

Sorry, I have no information about that. 

 

toyo4
2,940 Views

Thanks,  Fredric !

 

Chandler
2,516 Views

We ran into the exact same issue.  Found that if we created a broadcast domain for each node and placed the native port inside it, the port would report Healthy and green in System Manager.  So if you want to fix it, just create 2 new broadcast domains and place the native port in them.  I found that creating just 1 new broadcast domain wouldn't work if both ports were in it.  So I created a NodeA and NodeB broadcast domain.

Public