Show the graphic management interface of Enterprise routers in four rounds (1)

As we all know, enterprise-level routers are different from home broadband routers used by everyone at ordinary times. Most commands and configurations are configured in the Command Prompt window with the next command. Therefore, it is difficult to get started, generally, you need to connect to your computer through the console interface for management. However, more and more enterprise routers, especially low-end and Middle-end models, have introduced a graphical setting interface. In the graphical interface mode, we can set parameters and manage the network as if we were configuring a home Broadband Router. This change has caused more and more enterprise network administrators to discard redundant commands and the Console line. However, do you know that there are inherent defects in the graphical management interface? If you trust it too much, it may bring one or more risks to the enterprise intranet, even if a network failure occurs in the future, it cannot be quickly located and solved. Today, we invite readers to follow the author's instructions to show their true faces on the Enterprise router graphic management interface.

Integration: Graphical management default settings make network troubleshooting more difficult

As we all know, the biggest advantage of the graphic management interface is that it is simple and convenient. We can complete the access of Enterprise routers in the shortest time through functions such as setting wizard. However, the default settings of some parameters on the graphical management interface make it more difficult to troubleshoot network faults.

I have encountered the problem of configuring NBR2000 Internet cafe-level routers on the graphic management interface, and setting multiple parameters such as IP information and Internet connection on the management interface, however, during the final debugging, I found that the Network was disconnected and the client could not access the Internet smoothly. The ping detection tool finds that no matter which WAN port address of the router is pinged, The Troubleshooting is conducted on the WAN port line connection and parameter configuration. Who knows that the WAN interface settings are correct after repeated troubleshooting, the reason for ping failure is that the system automatically adds some basic access control list ACLs to the vro after the drop-down menu or setting wizard configuration in the interface by default, thus, common network detection packets including ping are automatically shielded. I used the Console line to connect to the NBR2000 vro command management interface and run the sh run Command to view the default information, after setting parameters in the graphical management interface or creating a configuration through the setup wizard, The vro itself adds multiple access control lists to shield ping packets, this is also the reason why ping detection is ineffective when the network connection fails. After a long period of investigation, I found that the Internet connection line was loose. 1)

The self-creation of the default settings in the graphical management interface makes it more troublesome for us to troubleshoot network faults. In many cases, we have to cancel these default entries and clean the network. After all, in the initial stage, we are simple and true. blindly adding multiple commands will only disrupt the idea of the network administrator.

Summary -- the graphic management interface setting is not as simple as you think. Maybe you just configure a parameter, but it will add multiple commands to you by default, therefore, if necessary, we should configure it on the command prompt interface, so what we see is actually meticulous.