Automatic inspection tool for network equipment (3)——Thinking about the way to log in equipment【2020-10-28】
First of all, continue today, mainly to compile the basic information interface of the network device. As you select the device in the tree list on the left, the basic information of the device is displayed in the right area. The preparation has been completed. The main workload is dragging controls, adjusting properties, alignment, and so on.
Secondly, I fell into a long time thinking today, mainly thinking about how the automatic inspection tool I wrote to log in to the network device for inspection; there are two main ways I thought of, one is to use Visual FoxPro to call Telnet control or Winsock control to log in Device, the other is to use Visual FoxPro to call SecureCRT to log in to the network device (I will introduce SecureCRT first, network engineers are very familiar with it, and its functions are very powerful. It mainly provides various ways to log in to the device, support script operation, and automatically save logs. Wait, it's very easy to use and very stable.) After repeated thinking, I finally decided to use SecureCRT to log in to the device. Let me share with you the reasons for choosing to call SecureCRT in detail. There are three main points:
1. The main consideration is the security and stability of SecureCRT. If I write the Telnet control myself, I may board the device accidentally, which poses a great security risk to the existing network equipment, and call the mature SecureCRT to log in to the device. My automatic inspection tool has become very, very safe.
2. To reduce programming costs, the function of SecureCRT is very suitable for automatic inspection. If I write it myself, it is equivalent to writing the function of SecureCRT with Visual FoxPro again, not to mention the quality of the writing, which will increase the automatic inspection tool Programming cost, why not use it if there is a ready-made one?
3. Every engineer is very familiar with SecureCRT. Calling SecureCRT can increase the friendliness of the automatic inspection tool and simulate manual operation to the greatest extent, so that the engineers feel that the automatic inspection tool is only automatically helping me complete the monotonous and repetitive work. The way of working has not changed, and it is more acceptable to everyone.
Finally, let me talk about how Visual FoxPro can call SecureCRT to complete automatic inspections. It is actually very simple. It can be achieved in two steps. The first step is to let Visual FoxPro automatically generate CRT temporary script files based on database information, and the second is to call CRT to execute. The script will do.
Today’s time is almost there, and we will finish it tomorrow.