FSPM communicates with the Pilot using secure encrypted messages. The SAN host where the FSPM is installed requires a TCP/IP connection for communication with Oracle FS System Manager (GUI) or Pillar Axiom Storage Services Manager (GUI).
The network configuration must enable the SAN host to connect to a Pillar Axiom storage system using TCP port 26004 or an Oracle FS System using TCP port 26012. These ports are used to connect control path to the Pilot management Ethernet interfaces.
Network firewalls may be running on the host or in the network between the host and the Pilot. Firewall settings can block access to ports 26004 or 26012. Changes to the firewall settings can block a port that was previously open.
To resolve the blocked port, first determine if TCP port 26004 on a Pillar Axiom storage system or TCP port 26012 on an Oracle FS System is open and not blocked. You can test connectivity from the host to the system by using the telnet command to access the Pillar Axiom storage system or the Oracle FS System. No data is returned if you can successfully access the system; the port is open and not blocked. If you successfully access the Pillar Axiom storage system or the Oracle FS System with the telnet command, quit or escape from the telnet session.
To access the Pillar Axiom storage system or the Oracle FS System with telnet, you need the IP or DNS name of the Pillar Axiom storage system or Oracle FS System.
Here is an example of the command for the Pillar Axiom storage system port:
telnet axiom_ip_or_dns_name 26004
Here is an example of the command for the Oracle FS System port:
telnet oraclefs_ip_or_dns_name 26012
If the telnet command fails then unblock TCP port 26004 on a Pillar Axiom storage system or TCP port 26012 on an Oracle FS System After unblocking the TCP port, verify that the TCP port is open using the telnet command.