The phenomenon of description:
USM connection file server failed, 604 message prompt no acitve MRP found.
The analysis process：
1, execute the command PING under CGP: IPTYPE=IPV4, LOCALIP4="XXX.XXX.XXX.XXX", PEERIP4="XXX. Make sure you can PING;
2, query whether the relevant configuration on the USM is complete, the important configuration is as follows: LST FSCFG, LST
CTILNK, LST USMMEDIALOCALIP, LST USMFS, LST USMMEDIABEARIP, to ensure that the configuration is complete and correct;
3. Perform the following steps to check whether the manual mount state is normal;
1) log in LMT and perform LST VM under USM network element :; Get the virtual machine used by USM network elements;
2) perform SET SSHDCFG under CGP netelement: CFGTYPE=SERVICE_STATE, DEPLOYTYPE=VM, VMNAME="XXXX", SSHDSTAT=ON;
Command to open SSH service status;
3) DSP IPINFO: DEPLOYTYPE=VM, VMNAME="XXXXX", IPITERM=IP Command query network IP information;
4) log in omu through SSH, and then SSH to the corresponding virtual machine through internal network IP;
5) perform the mount command operations manual mount, the mount -t NFS - o soft, timeo = 1, retry = 1, proto = udp 10.10.10.112: / / share/voice/f1
In the above steps, if there is a problem in steps 1), 2), and 3), it is a configuration problem. If there is a problem in step 4), the IP should be modified.
The IP cannot be 10.10.10.* and 10.10.20. If there is a problem in step 5), it needs to be analyzed on a case-by-case basis.
Question why：
10.10.10* network segment is the IP used by USM internal modules to communicate with each other and cannot be used to communicate with the file server.
Processing steps：
Modify the IP that communicates with the file server to be non-10.10.10.10.* and 10.10.20.* IP of the network segment.
