How to resolve ONTAP ports degraded by Layer 2 reachability

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 12,694

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: nas

Last Updated:

Applies to

ONTAP 9
Networking
Layer 2 reachability health monitor

Description

Use this resolution guide to match the observed l2_reachability symptom to the KB article that addresses that specific scenario.

From ONTAP 9.13.1 and later, ports that fail Layer 2 reachability checks can be marked as degraded. ONTAP Layer 2 reachability checks use Connectivity Fault Management (CFM) frames.

Use the table below as an index. Match the observed output or event pattern, then open the linked KB for the focused troubleshooting procedure.

Procedure

Specific symptoms	KB
::> network port show Node: node1 Port IPspace Broadcast Domain Link MTU Admin/Oper Status --------- ------------ ---------------- ---- ---- ----------- -------- a0a Default Data up 1500 -/- healthy a0a-100 Default Data up 1500 -/- degraded e0e Default - up 1500 auto/10000 healthy Symptom:* VLAN tagged port is degraded while the physical port is healthy.	VLAN tagged ports Related: Data network port degraded
`::> network port show Port IPspace Broadcast Domain Link MTU Admin/Oper Status --------- ------------ ---------------- ---- ---- ----------- -------- e0e Default vlan101 up 1500 auto/10000 healthy e0e-100 Default vlan101 up 1500 -/- degraded` Symptom:* Port is degraded after creating a VLAN interface.	After creating VLAN interface
`::> network port show Node: node1 Port IPspace Broadcast Domain Link MTU Admin/Oper Status --------- ------------ ---------------- ---- ---- ----------- -------- a0a Default Data up 1500 -/- degraded a0a-100 Default Data up 1500 -/- healthy` Symptom:* Native VLAN port is degraded after upgrading to ONTAP 9.13.1 or later.	Native VLAN ports
::> network port show Node: node1 Port IPspace Broadcast Domain Link MTU Admin/Oper Status --------- ------------ ---------------- ---- ---- ----------- -------- a0a Default Data up 1500 -/- healthy a0a-100 Default Data up 1500 -/- healthy e0e Default - up 1500 auto/10000 degraded e0f Default - up 1500 auto/10000 healthy Symptom:* Ifgrp member port is degraded while the ifgrp remains reachable after upgrading to ONTAP 9.13.1.	Ifgrp member ports degraded
`EMS: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Insufficient L2 Reachability detected from cluster port e4e on node Node-01. vifmgr: vifmgr.port.monitor.passed:notice]: The "l2_reachability" health check for port e4e (node Node-01) has passed.` Symptom: Switchless cluster reports Layer 2 reachability issues on cluster ports with ONTAP 9.13.1 or later.	Troubleshoot port reachability
Symptom: Newly configured ifgrps are degraded with `l2_reachability`. `ifgrp show` indicates partial or no port participation. The network switch shows partial or no participation for the port channel.	New ifgrps degraded
`Failed to revert data LIFS back to the node "Cluster01-01". Action: Revert all LIFs back to their home ports using "network interface revert " command.` Symptom:* ANDU enters a paused-on-error state because LIFs cannot be reverted.	ANDU paused-on-error
Symptom: Physical network port is degraded with `l2_reachability`, for example `e0d`, and the VLAN/ifgrp symptoms above do not match.	Physical port degraded
Symptom: Frequent or intermittent `l2_reachability` failures occur on `e0M` management ports.	e0M health check failures
Question: Can ONTAP prevent port status from reflecting `l2_reachability` monitor results?	Port status behavior

Procedure

Partner Notes

Additional Information

Internal Notes