Skip to main content

Auralization - short wave radio for network management

Many moons ago I was reading Terry’s blog when he was at Netcordia, where he posted about auralization which reminded me about my own experiments in using voice for monitoring a network. Not strictly auralization, but stay with me. A few years ago, I created a monitoring system based on Suse and using Argus. I created a call me system using text to speech and Openh323. The voice integration was driven using an old Radvision H.323 gateway that Madge OEM'ed way back in the 90s.

What this monitoring system did was phone me at a designated number and tell me in an automated voice message what the problem was. No SMS or pager bull, just a plain voice (I could never read a SMS at 2:00am!). I also had a feedback channel via DTMF. It cost zilch and worked like a charm! The gateway was an inheritance from when Madge went titsup, the server was an old Internet caching appliance and the software was open source. My code is long lost, but the strength of using audio and voice has remained in my thoughts. Is there any software out there today that does the same thing? I also thought of doing a flight director poll. The idea would be that I call in and the system would give feedback in much the same way the flight director of an Apollo mission would have heard in Mission Control. “Backbone we are go”, Kalahari Edge, we are no go as the systems are at 90%.”, "Backup we are go." etc. Never got around to doing it as I became a manager and lost all of my ability to program. :-)
Ok, after that slight diversion back to back to Terry’s post about auralization which is the same as visualization but with sound. My idea would be the short wave radio. The short wave radio has many possible auralizations:
  • Hum variation based on network utilization.
  • Static pops based on errors
  • Feedback loop spikes based on failures
  • Morse code alerting SOS . . . - - - . . . for a major incident as an example
  • Automated tune in to weather report or traffic report, e.g. "email from the Kalahari to the outback has increased resulting in a jet steam congestion".
  • Random timed tune in to the flight director poll described above.
  • Tornado warnings based on incidents spikes at the service desk.
  • or basically any other radio-centric voice or sound effect.
There are many sources for determining sounds, including syslogs, snmp traps, netflow, icmp and ipsla. In a large network the amount of information being generated by the network and the number of issues can be relatively high and the sounds can become a trigger for proactively detecting major incidents.
However, the big thing is, does the younger generation recall short wave radio???????? I have an old 1948 Murphy, so maybe the above just appeals to me??


Popular posts from this blog

easywall - Web interface for easy use of the IPTables firewall on Linux systems written in Python3.

Firewalls are becoming increasingly important in today’s world. Hackers and automated scripts are constantly trying to invade your system and use it for Bitcoin mining, botnets or other things. To prevent these attacks, you can use a firewall on your system. IPTables is the strongest firewall in Linux because it can filter packets in the kernel before they reach the application. Using IPTables is not very easy for Linux beginners. We have created easywall - the simple IPTables web interface . The focus of the software is on easy installation and use. Access this neat software over on github: easywall

No Scrubs: The Architecture That Made Unmetered Mitigation Possible

When building a DDoS mitigation service it’s incredibly tempting to think that the solution is scrubbing centers or scrubbing servers. I, too, thought that was a good idea in the beginning, but experience has shown that there are serious pitfalls to this approach. Read the post of at Cloudflare's blog: N o Scrubs: The Architecture That Made Unmetered Mitigation Possible

Should You Buy A UniFi Dream Machine, USG, USG Pro, or Dream Machine Pro?