Port Troubleshooting Resolution Guide

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

Views:: 6,964

Visibility:: Public

Votes:: 5

Category:: data-ontap-8

Specialty:: hw

Last Updated:

Applies to

ONTAP Hardware
Port issues

Answer

Port Troubleshooting

This article contains a list of most of the ports troubleshooting workflows. However, it is not a comprehensive list. This can be used to narrow your search to the more commonly utilized troubleshooting KBs, broken down to a specific category

Overview:

Port Troubleshooting Resolution Guide

From the picture above, note that this controller head (which is only one example) contains a lot of different ports which can behave differently in different configurations. These can be divided into three groups:

SAS ports (marked with red circles) which are used to access the disk shelves.
Ethernet ports (marked with green circles) used for end users to access data. Some of the ports, (half green- half orange), can be configured as FC ports, but are still used for end users to access data.
Management ports (wrench port and locked wrench port) are used for monitoring and managing the system.

Depending on port configuration or hardware issue with particular port, the system can behave differently and the end result might be different.
The NetApp Hardware Universe provides excellent front and rear views of the vast majority of NetApp hardware, including controller platforms.

Errors:

The specific failure symptom can vary depending on your configuration. The system is complex. If you are unsure, contact NetApp Technical Support for assistance.

Error	Resolution
`Filer: pvif.allLinksDown:CRITICAL]: vif2: all links down`	Single VIFs flapping
`Fri Sep 05 11:02:25 GMT [xxxxx: acpa_command_thread: acp.common.message:debug]: ERROR: params: {'debug_string': 'ACPP (0xc0a80251) not ready to process the command.\n'} Fri Sep 05 11:02:34 GMT [xxxxx: oob_bootp_sender: acp.neg.socErr:err]: Socket send error while port e0e was communicating with the ACP processor (0x1c08fea9)`	ACP Connectivity Status: Partial Connectivity
`ACP not-responding`	ACP not-responding
`sas.cable.degraded:warning]: Cable attached to SAS port "x" is functioning in a degraded mode`	How to troubleshoot "Cable attached to SAS port x functions in a degraded mode" errors
`LIFs do not respond to pings`	How to troubleshoot unreachable LIFs?
`callhome.clus.net.degraded`	How to troubleshoot CLUSTER NETWORK DEGRADED error messages
`Troubleshooting LACP port channel/ interface groups`	Troubleshooting LACP port channel/ interface groups For additional Information, see KB: How to troubleshoot LACP issues with "ifconfig -v" in ONTAP 9.2+
`callhome.hm.sas.alert.major:CRITICAL]: Call home for SAS Connectivity Monitor: DualPathToDiskShelf_Alert[50:05:0c:c1:02:02:59:5d]`	Error when moving a SAS cable from one port to another on an HA pair
`[Node1: vifmgr: vifmgr.lifs.noredundancy:ALERT]: No redundancy in the failover configuration for 1 LIFs assigned to node "Node1". LIFs: Vserver1:Lif1`	EMS reports "No redundancy in the failover configuration" for one or more LIFs
`vifmgr: vifmgr.lifdown.noports: LIF Lif1`	This LIF IP address is down because there are no eligible ports capable of serving data for this LIF. To bring this LIF up so that it can serve data, enable one or more eligible ports that can host this LIF. To find the list of eligible ports for this LIF, examine the failover rules for this LIF. In addition to the ports found there, you could add a new port to the failover rule for that LIF.

Additional Information

Add your text here.