Example 2, Example 3 – HP NonStop G-Series User Manual
Page 148
Troubleshooting
Mid-Range Silo Media Manager Installation and User’s Guide — 541530-003
C -14
Example 2
Example 2
PROBLEM:
Which PORT is the MSMM server configured to run on?
SOLUTION:
The server the NonStop S-series communicates with the silo and MSMM software is
through the use of TCP/IP port numbers. This has to be configured when the MSMM
software is installed. It can normally be anything between 4001 and 8000. It will show
up when you run a VIEW_CONFIG in your MSMM configuration menu. If you are
using MSMM Clients, make sure they use a different port number than the MSMM
Server uses [preferably at least 10 ports apart, i.e. HOST = 4001, CLIENT = 4011].
Example 3
PROBLEM:
Which TCP/IP process are you running the MSMM software on?
SOLUTION:
You can start MSMM on any TCP/IP process that you have running. TSI recommends
using a TCP/IP process other than $ZTCP0/1 on the NonStop S-Series. This is
considered an internal network that controls the internode communication on the
NonStop S-series. To see which TCP/IP processes that are running, enter the
following command from any TACL session:
STATUS *,PROG $SYSTEM.*.TCPIP
Then, put whichever process you want in the MSMM startup file as follows:
clear all
param TCPIP^PROCESS^NAME $ZB01A
delay 10 seconds
RUN $
term $ZHOME, out $ZHOME, cpu 0/
Note.
The MSMM port numbers used in your MSMM configuration do not need to be defined in the SERVICES or
PORTCONF file.
Note. MSMM will automatically add one to your port number and open this port for EMS
messaging. For example, if you have MSMM configured to run on port 4001, you will also need
port 4002 open. You will not need to configure the EMS port number, since MSMM will
automatically open it when you start the MSMM processes.
Note.
Having a delay in the MSMM startup obey file will help when establishing a connection.