6.1.4 Post-installation setup

For operation of the Agent, the following port number is necessary for transmissions with the Manager.

Service name	Port number / Protocol name	Sender	Receiver
sscruisera	4917/tcp	Manager	Agent

Include the following details in the /etc/services file, and declare usage of the port number. In cases where there is no description in the /etc/services file, agent booting will be from 4917 port number.

#Service name   Port number/protocol name
sscruisera      4917/tcp

Information

When a port number is already in use, please select a vacant port number. In this case, with regards to other ETERNUS SF Storage Cruiser Manager with the same port number configuration, perform the same configuration changes.

6.1.4.2 Agent admin LAN IP address configuration

Configure agent admin LAN IP addresses using the following procedure.

It is necessary to stop the agents to perform the configuration of agent admin LAN IP addresses.
When an agent is operating, input the following command and stop the agent.
```
# /opt/FJSVssage/bin/pstorageagt
```
Configure the admin LAN IP address on the agent.
```
# /opt/FJSVssage/bin/setagtip -i admin_LAN_IP_address
```
Point
About admin_LAN_IP_address
Specify the IP address of the server node, which is used for communication with the admin server. This is used as the start IP address in order to communicate with the admin server (Manager) via the correct LAN.
- If the managed server node has a single IP address, enter this IP address as the agent admin LAN IP address
- If the managed server node has more than one IP address, enter the start IP address of the server node based on the administrative server LAN IP address.
  For example:
  Manager IP: 10.10.10.xx
  Agent has more than 1 IP like this:
  10.10.10.yy
  192.168.1.zz
  In this case, please input "10.10.10.yy".
- If the managed server node is under firewall or IP of the managed server node is converted by NAT, enter the IP address used for communication between ETERNUS SF Storage Cruiser Manager to the managed server node.

6.1.4.3 SNIA HBA API library installation and configuration

When managing a RAID unit with ETERNUS SF Storage Cruiser it is necessary to install and configure the SNIA HBA API library distributed by the HBA vender.

Please refer to "B.1 SNIA HBA API library installation for Solaris", and install the SNIA HBA API library.

6.1.4.4 Updating Correlation.ini file

When a SUN HBA is in use, you must update the correlation.ini file that sets the details of the Agent using the following procedure:

# cp -p /etc/opt/FJSVssage/Correlation.ini /etc/opt/FJSVssage/Correlation.ini.org
# cp -p /etc/opt/FJSVssage/Correlation.ini.sun /etc/opt/FJSVssage/Correlation.ini

The SUN HBAs are as follows:

SE0X7F21F, SE0X7F22F, XSEFC401AF, XSEFC402AF
HBA that its name starts by SG-XPCI