No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

TE40 Fails to Register with the Standalone SC, but Can Successfully Register with the embedded GK

Publication Date:  2019-04-26 Views:  95 Downloads:  0
Issue Description

In a dedicated network environment with SMC2.0 + Standalone SC + VP 9650 + TE endpoints, a branch TE40 fails to register with the standalone SC because the GK is not found. However, a TE endpoint at the headquarters can successfully register with the standalone SC.

No change is made to the SMC2.0 SC, TE endpoint, or VP9650. The service IP address of the standalone SC is correct, the license is normal, and the version configuration is correct (SC: V500R2C00SPC300; TE endpoint: V500R002C00SPC200).

Handling Process

1. The headquarters endpoint can successfully register with the standalone SC. The branch TE40 fails to register with the standalone SC, because the GK is not be found. The ping to the standalone SC fails, but the ping to the gateway of the standalone SC succeeds.


2. According to packet capture analysis for the branch TE40 and standalone SC, the TE40 sends the RRQ, but the standalone SC does not receive the request.
 The standalone SC, SMC2.0, and MCU are in the same network segment. The ping from the SMC2.0 to the IP address of the branch endpoint succeeds, and login to the branch endpoint's web interface is successful. Therefore, the user believes that there is no network problem between the headquarters and the branch endpoint.


3. The branch TE40 can successfully register with the SMC2.0's embedded SC. It is suspected that the standalone SC is faulty.


4. Log in to the standalone SC through SSH. A ping to the branch TE40 fails. Run dis sys to check the configuration of the standalone SC. It is found that the LAN2 port is configured with an IP address but is not connected to a network cable. The configuration of default routing port is empty.


Run the following command to manually configure the default route port, and then perform a restart. The problem is solved.

system-view sys-config network-config default-route lan lan1

After the default routing port is configured, a ping from the SC to the branch endpoint is successful, and the branch endpoint can successfully register with the standalone SC.

The reason is that the branch and headquarters are not in the same IP network segment. If the default routing port is not configured on the standalone SC, registration can succeed within the same network segment but will fail across different network segments.

Root Cause
Run system-view sys-config network-config default-route lan lan1 to manually configure the default routing port and then perform a restart. The problem is solved.

END