Keywords

DCN, NE login failure
Symptom Logging in to an NE fails when configurations are deployed to the NE in DCN mode.
Problem Identification Before a user deploys configurations to the NE that needs to go online, the user logs in to the associated GNE through Telnet and runs the telnet vpn-instance __dcn_vpn__ NEIP of the NE that needs to go online command on the GNE. Then the user uses the Telnet login parameters stored on the U2000 to login in to the NE that needs to go online. In this situation, the login fails.
Problem Locating and Cause Analysis None Solution
Step 1 Check whether the NE that will go online exists in the Main Topology.
Check method: Select the NE in the DCN view and right-click it. If the NE Explorer option is displayed in the shortcut menu, the NE exists in the Main Topology. If the NE exists in the Main Topology, go to Step 2. Otherwise, go to Step 3.
Step 2 Select the NE in the Main Topology, right-click, and choose Set NE Telnet/STelnet Parameter from the shortcut menu. In the dialog box that is displayed, set correct Telnet/STelnet parameters and click Apply. Click Test. After the test succeeds, redeploy configurations. If the configurations can be properly deployed, the troubleshooting is complete. If the Telnet login password is forgotten, go to Step 4.
Step 3 Select the NE in the DCN view, right-click, and choose Set NE Telnet/STelnet Parameter from the shortcut menu. In the dialog box that is displayed, set correct Telnet/STelnet parameters and click Apply. Click Test. After the test succeeds, redeploy configurations. If the configurations can be properly deployed, the troubleshooting is complete. If the Telnet login password is forgotten, go to Step 4.
Step 4 Connect the PC to the NE through the console port and log in. Re-set Telnet login parameters for the NE and perform Step 2 or Step 3 based on the check result in Step 1. ----End