The phenomenon of description
SMC cannot automatically find the meeting place.
Possible reasons for
There is no connection between the conference hall and SMC.
Has been added to the manageable venue or pre-release list.
There was no SNMP enabled on the venue, or the SMC address was not used as the Trap server address.
Port 162 on SMC is occupied or not opened by other programs, which makes SMC unable to listen to Trap information reported by the venue.
Position ideas and solutions
1.If both parties cannot ping each other's IP on the SMC and the venue (the venue cannot ping through the SMC if the SMC is reinforced and ICMP
is not enabled, but the venue can ping through the SMC on the SMC), then it is necessary to check whether the network connection is correct.
2.Check whether the pre-defined meeting place list and the manageable meeting place list have the meeting place; If so, you will need to delete the
The meeting cannot be detected automaticallymanageable meeting place before it can be found automatically.
3.Take VCT as an example, log in the terminal through the Web, and check whether "enable SNMP" is enabled in
[system configuration] -> [SNMP setting], as shown in the figure below. If not, set it to enable, and in the "Trap server address" list, select an address
with SMC. After setting up.
4.To find out the program that occupies the port, the method of finding is to enter the search statement in CMD: to see whether the port is
occupied: netstat -nao | findstr 162, as shown in the figure below:
5.The right-most column represents the process that occupies the port. Find the process in the task manager. If the port is not occupied by
device-service.exe, terminate the process and restart the Device Service.
6.Note: if the PID column cannot be seen in the process manager, you can click "view" -> [Select Columns...] in the menu bar. And check "PID
(Process Identifier)". If you can't see it happening, check "Show processes from all users" at the lower left corner of the task manager.
