The phenomenon of description
After adding independent GK to SMC, independent GK is not online.
Possible reasons for
1.SMC is not connected to a separate GK network or the firewall is not open to port 7000.
2.The standalone GK does not start the connection.
3.GK IP address or password configuration does not match on SMC.
Position ideas and solutions
1.If both parties cannot ping each other's IP on SMC and GK (both parties cannot ping if the SMC and GK servers are hardened and ICMP is not
enabled), Telnet is needed to check. Port 80 of Telnet SMC on GK server and port 1720 of Telnet GK on SMC are available
After success
Check whether the independent GK service is started.
2.Check whether the GK configuration file (gkcfg.ini file in the Switch System\SwitchCentre directory of GK) matches the GKM as shown in the
figure below
3.Fill in the gk-certified password at the "GK connection password", which should be consistent with the "gkm-auth-pwd" field on the GK configuration
file; Fill in the IP address of the external GK at the "IP address" (if it is an Ipv6 address, fill in the Ipv6 address), which is consistent with the address of
the "ip-management" field on the GK configuration file; Fill in the IP address of the standby GK at the standby address (which is not required), which
is the same address as the "ip-management" field on the standby GK configuration file. Also make sure that the "sm-ip" in the GK configuration file
is the SMC IP address.
Information collection
1.Log information for SMC GKM.
2.Network capture packet on SMC side.
