For Managers, Proxy Managers or Enterprise Managers, the following procedure can be used to restrict the Manager, Proxy Manager or Agent that will become the other party to a communication.
Procedure
Stop the Manager service or daemon and confirm that it has stopped normally
Stop the service or daemon by referring to "A.8 How to Start and Stop Resident Processes". Also check that the relevant resident processes have stopped correctly.
Edit DSAconfiguration.txt
Windows
<Variable file storage directory>\control\DSAconfiguration.txt |
UNIX
/etc/opt/FJSVssqc/DSAconfiguration.txt |
Specify the IP addresses of the parties that will be permitted to communicate in the grant_access key in the [DsaListener] section. The following is an example:
[DsaListener] : grant_access=100.100.100.100 grant_access=100.100.100.101,100.100.100.102 : |
Point
More than one grant_access key can be specified.
IP addresses can contain wildcards, as in "grant_access=100.100.100.*, *.100.100.100".
A range of IP addresses can be specified, as in "grant_access=100.100.100.100-100.100.100.200.
Wildcards and ranges can be used together, as in "grant_access=100.100.100.*-100.100.200*".
Specify "grant_access=*" to grant access to all parties. Access will also be granted to all parties if the "grant_access" key is omitted.
Specify "grant_access=" to deny access to all parties.
Note
The communication restriction imposed by this definition also applies to definition-related communications from operation management clients. Therefore, if this server will be connected to an operation management client, do not forget to specify the IP address of the operation management client in the grant_access key.
Start the service or daemon and confirm that it operates normally
Start the service or daemon by referring to "A.8 How to Start and Stop Resident Processes". Also check that the resident processes have started correctly.
