Pillar Axiom: Axiom Path Manager Showing As Not Communicating Or Not Registered For Some Hosts

Asset ID:	1-72-1468807.1
Update Date:	2014-12-04
Keywords:

Solution Type Problem Resolution Sure

Solution 1468807.1 : Pillar Axiom: Axiom Path Manager Showing As Not Communicating Or Not Registered For Some Hosts

Applies to:

Pillar Axiom 500 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 600 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Symptoms

After patching the server, APM is showing as "Not Communicating"

Cause

I do not see any compatibility issues

This can be due to the network port being blocked by a firewall or router, the APM service not running, or APM became corrupt.

APM needs to connect to TCP port 26004 on the Pilot to register.
Tip: To check network connectivity on R4, issue a simple pdscli or axiomcli request from the host to the Pillar Axiom storage system. Both pdscli and
axiomcli use the same port and protocols as those used by APM.

Example: pdscli sub -u administrator -H axiom_ip_or_dns_name GetAllSlammers <-- slammer details will be displayed if the communication is enabled

Refer to Pillar Axiom CLI Reference Guide for pdscli for more details (available from the Support tab of the axiom GUI, click on Technical Documentation.

For R5, axiomcli uses a different port to communicate to the Axiom (port 26008) so this check is not applicable. From the host with APM communication issues, try:

telnet axiom_ip_or_dns_name 26004

Solution

network port 26004 was blocked

Attachments

This solution has no attachment