Connecting eNSP to Putty and Windows PC
Hello everyone!
Today, I would like to bring a practical and useful tip for friends who are new to the Huawei world and who are looking to improve their knowledge with the eNSP simulation tool.
Objetive
The purpose of the article is to present one ways to connect your terminal used in Windows to some functional device inside the eNSP.
Connecting PuTTY to eNSP
We are going to use a Switch-S5700-28C-HI to help us with our communication example.
Step 1:
First step is to get the equipment's Local Server information.
Information can be found in the following path: Menu < Option < Server

As shown in the image above, our information is as follows: LocalServer IP: 127.0.0.1
Step 2:
Next step is to look up the COM port information that the device provides.
Right click on the desired equipment: Settings < Config < Console COM Config

Step 3:
Next step is to try the connection between PuTTY and LSW1 equipment inside the eNSP.
Open the PuTTY terminal inside your Windows computer.
Ps: I emphasize that any other terminal can be used, in the example I use PuTTY because it is open and simple to find and use.

Select the connection type "Telnet" and provide the information of Host Name "127.0.0.1" which is the IP of the Local Server and Port "2000" which is the Console COM port of the equipment we want remote access via Telnet.
Step 4:
The fourth and final step is to actually verify the connection.
Let's run the following commands in order to validate our device connectivity within the eNSP.
The first command is: "display version"
You can use the display version command to view the version of the device to determine whether the device needs to be upgraded.
The second command is: "display device"
Run the display device [ slot slot-id ] command to view component information and device status. When the Register field displays Registered and the Status field displays Normal, the card status is normal.

Conclusion:
If your connection attempt was successful and it was possible to see the equipment and send commands via the PuTTY terminal, our goal was achieved as planned.


