If you’ve ever tried to interpret an A10 Networks load balancer configuration, or some Cisco Modular QoS CLI
commands, you’ll know that doing so involves following references to other parts of the configuration, inevitably ones that appear earlier in the configuration than where you are now, using a display pager which doesn’t support a back
command to scroll up a page at a time. In short, it’s a huge pain. The same applies to Cisco ACE and CSM load balancer configurations. The modularity is beautiful and logical, but it’s a massive irritation to reverse engineer.
I work regularly with A10 Networks load balancers. ACOS (the A10 OS) has a CLI and configuration format that’s very similar to Cisco IOS. Looking at a particular vPort (A10 terminology for a particular Virtual IP (VIP) and Port combination) and trying to figure out which real servers are related to it is irritating to say the least. Here’s an example of the configuration in the order it appears when you view it:
ip nat pool pool1 10.100.1.1 10.100.1.126 netmask /25 ! health monitor checkstatus method http url /status expect code 200 ! slb server server1 1.2.3.4 port Continue reading
The spectacular waterfalls of the Igazu River inspired the company’s name.
The post Worth Reading: Pre-Internet digital communications appeared first on 'net work.