What do you do when your network fails and you can’t access it remotely?
You need to get on-site and repair the failure – and as quickly as possible! The longer the service downtime is due to a failure, the more the losses explode. It’s a network administrator’s nightmare when you can’t react quickly. Especially in an environment with a mix of equipment and manufacturers, each piece of equipment often has to be configured differently, and it’s easy to make mistakes. To solve these problems, I’ve often wondered how I could quickly recover my network in the field.
Initially, I thought about using traditional domestic and international console server solutions, but I was at a loss when I couldn’t access them remotely. I changed my mind when I encountered problems that could only be solved by traveling to the site. We realized that we needed a custom tool that could be used in the field as a last resort in addition to the console server.
The problem was that after connecting to the console port of the failed communication equipment, we had to enter the manufacturer’s console commands one by one, which was too slow, and any typo would further delay the recovery work. What solution could solve this problem?
We looked for a simpler, faster way to react in these situations, and concluded that portable equipment would be a better fit, but it wasn’t just about being portable. Since network equipment can have different setup commands and pin maps depending on the manufacturer, we realized that automated command transmission and the ability to change pin maps was essential. This led us to develop a portable serial console solution.
What are the advantages of this solution? The Bluetooth connection allows for quick wireless access to equipment, the automatic command transmission feature prevents mistakes in entering setup commands, and the pin map change feature allows for equipment from different manufacturers to be managed over a single LAN.
