a2A5328-4gmPRO which was a candidate of a new TCam didn't work via pylon-camera-server due to a compatible issue of a SDF version and had limitation for a full-spec operation in the CAM network due to the traffic issue (klog#36390).
acA4112-8gm which works with a compatible version of SDK was installed as an alternative candidate (klog#36510).
It was able to work with pylon-camera-server.
On the other hand, there is still limitation for a full-spec operation in the CAM network though a traffic requirement of this camera is slightly lower than a2A5328-4gmPRO.
So we need to consider well that limited specifications are enough or not for TCam purposes.

-----
Though acA4112-8gm has 4096x3000 resolution as a full-specification, pylon-camera-server hung up with that resolution due a packet loss issue. So I reduced a resolution as 2048x1500 (1/2 scaling from a full-spec), then it was able to launched via pylon-camera-server.

Points to note and considerations are as follows:
1) I haven't checked an impact on the existing GigE camera system though a traffic with operating that resolution is too large for the CAM network. So more scaling (1/4 = 1024x750 or 1/8 = 512x375) is probably required for actual operation in the CAM network.

2) pylon-camera-server can be used only 'Mono8' format. Configuration file accepts various video formats in GStreamer such as Gray8, Gray12_LE, etc. and pylon-camera-server can receive various capture format such as Mono8, Mono12, etc. But an implementation of internal buffers are hard-coded as 1-Byte. So 8-bit format is actually available. When a format with more than 8bit, pylon-camera-server hangs up by inconsistency of a packet format.

3) Though a configuration file of pylon-camera-server has "width/height" parameters, they are for the resolution of a broadcast for downstream (client workstations). So a resolution of camera operation itself must be changed by a external script before launching pylon-camera-server.

4) Taking snapshot via pylon-camera-server is done with a resolution for the broadcast to the downstream. For this reason, when we want to change the resolution between broadcasted movies and taken snapshots, pylon-camera-server must be stopped via systemd during snapshot processes.

From these notes, we concluded that we need to confirm that Mono8 and limited resolution less than or equal to 1024x750 are enough or not if a new TCam rides on the current TCam network without any infrastructure and software upgrades.