After A customer SIG system deployment, it found that B region P2P real-time sub-protocol traffic no data, check the basic configuration that is normal
It configured public IP after the redeployment of the the B region's SPS, and other communicate of SPS and the server using a private network IP, IP configuration in the SAS configuration file are also private network IP. From other private network address SPS, that can ping the server's public IP. SPS and SRS \ SAS route was reachable after modified private IP to public IP, problems resolved.
First of all, it doubt that control communication is problematic. View real-time traffic statistics, B area of had the real-time traffic of flow analysis, and therefore excluded for this reason. Then, analyze real-time P2P sub-protocol traffic sources. Tool directly obtained P2P sub protocol traffic from the SAS, check the P2P SAS configuration found that it did not associate B region, in this case, SPS of B region did not reporte P2P traffic data to the P2P SAS. B region associated with the P2P SAS, restart SAS of P2P, it found the problem persists. It confirms that the SAS had no P2P real-time traffic data.
Finally, check the SPS of B region, showsas discovery that the SPS got the address of the SAS, it cannot ping the address. The reason is that it is not interworking of SAS route after SPS redeploy.