The phenomenon of description
Device list interface, SMC icon gray. Use this MCU for meetings, indicating that the MCU is not online.
Possible reasons for
1.The network between SMC and MCU is disconnected.
2.The IP address of the target MCU has changed.
3.The "connection type" of an MCU is not an SMC2.0/IMS type.
4.The encryption mode configured on SMC is different from that set on MCU.
5.The connection password configured on SMC is different from that set on MCU.
6.The connection password did not match before, resulting in MCU locking, the connection is not accepted for a short time.
7.For unmanageable MCU, the device model added to SMC is inconsistent with the actual model of MCU.
8.For unmanageable MCU, the connection port configured on SMC is not consistent with the listening port of MCU.
Position ideas and solutions
1.Ping each other's IP on SMC and MCU, if neither of them is working (MCU cannot ping through SMC if SMC server is hardened and ICMP is not
enabled, but it can ping through MCU in SMC), then check whether the network connection is correct.
2.Please go to the MCU side to see if the IP address of the MCU has been changed or replaced.
3.Set the connection type to SMC2.0/IMS on MCU
4.SMC encryption mode can be directly changed when adding or modifying the MCU configuration by modifying the "connection mode",
The encryption of MCU needs to be configured using Telnet. For series 9 MCU, use the command system management-config to configure; for series
8 MCU, use the command system-view telnet-config enable-security-mode to configure.
5.Fill in the connection password again on SMC and MCU to ensure the consistency of both sides.
6.At the same time, change the connection port between SMC and MCU to a new port.
7.Ensure that the type of MCU specified on SMC is consistent with the target MCU.
8.Ensure that the listening port of MCU filled in on SMC is the same as that set up on MCU.
