Skip to main content

NetApp_Insight_2020.png 

NetApp Knowledgebase

Port Troubleshooting

Views:
1,055
Visibility:
Public
Votes:
0
Category:
data-ontap-8
Specialty:
hw
Last Updated:

 

Applies to

Hardware

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:

1001013-1.png

Looking at the picture above, we can see that this controller head (which is only one example) contains a lot different ports which can behave differently in different configurations. From the picture, we can see and divide them 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 a 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. Due to the complexity of the system if you are not fully sure if you are on the right way or not please contact NetApp Technical Support to assist you.

Error
" Filer: pvif.allLinksDown:CRITICAL]: vif2: all links down "
 

Resolution: Single VIFs flapping

Error
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).


Resolution: ACP Connectivity Status: Partial Connectivity

Error
ACP not-responding
Resolution: ACP not-responding

Error
sas.cable.degraded:warning]: Cable attached to SAS port "x" is functioning in a degraded mode
Resolution: Cable attached to SAS port 'x' functions in a degraded mode

Error
LIFs do not respond to pings
Resolution: LIFs do not respond to pings

Error
" callhome.clus.net.degraded "
Resolution: CLUSTER NETWORK DEGRADED

Error
Troubleshooting LACP port channel/ interface groups
Resolution: Troubleshooting LACP port channel/ interface groups

Error
" callhome.hm.sas.alert.major:CRITICAL]: Call home for SAS Connectivity Monitor: DualPathToDiskShelf_Alert[50:05:0c:c1:02:02:59:5d]. "
Resolution: Error when moving a SAS cable from one port to another on an HA pair

Error
" [Node1: vifmgr: vifmgr.lifs.noredundancy:ALERT]: No redundancy in the failover configuration for 1 LIFs assigned  to node "Node1". LIFs: Vserver1:Lif1 "
Resolution: EMS message vifmgr.lifs.noredundancy

Error
" vifmgr: vifmgr.lifdown.noports: LIF Lif1 "
Resolution: 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.