FAQ: genDevConfig

  1. genDevConfig is a profile/configuration generator for new Shinken monitoring system and the older Cricket high performance monitoring tool.
  2. Err. What is Shinken?
  3. What is the difference between genRtrConfig and genDevConfig
    • Glad you asked! genDevConfig is the new name for genRtrConfig to reflect to more modular and flexible architecture of the tool. genRtrConfig has, for all intents and purposes, been replaced by genDevConfig. It is still available, but no longer supported.
    • There is no reason to continue using genRtrConfig, as the new tool, does everything the old one did and more. All this with a plugin architecture, better logging, more supported devices, streamlined code.
  4. Why should I use genDevConfig?
    • It builds the Shinken configuration files for you with intelligent defaults.
    • It ensures consistency in your meta data to facilitate searching, categorizing, processing data contained in your configuration.
    • It permits the use of dynamic assignments of configuration profiles based on configurable criteria. (Ie. Collect only gig interfaces, monitor T1 interfaces, set thresholds based on interface or device types, etc.)
    • Ability to keep your configuration data always up-to-date. Create the device once, and it is kept up to date perpetually with a companion PERL script genAutoConfig by Francois Mikus or Metagen by Mike Fisher.
  5. How do I add new devices to genDevConfig
    • Easy. Consult the genDevConfig manual, it includes a section on writing new perl modules for genDevConfig.
    • A sample perl module is part of the standard genDevConfig distribution to help get you started and the manual has a step by step walkthrough to creating your own module.
  6. Is there a list of supported devices and available genDevConfig plugin modules.
    • Yes, all devices compliant with SNMP MIB-II are supported as well as custom statistics for the devices. This list is based on the genDevConfig RC2 release, consulst the genDevConfig manual for an updated list.
    • Cisco IOS series routers (800, 1×00, 2×00, 3×00, 4500, 7xxx, 7500VIP, GSR, CRS-1)
    • Cisco IOS Catalysts (5K, with RSM/MSFC2)
    • Cisco CatOS Catalysts (4K, 5K, 6K)
    • Cisco IOS series switches (1900, 29×0, 3×50, 3×60, etc.)
    • Cisco Altiga VPN concentrators (3015, 3030, 3060)
    • Cisco PIX firewalls (Full line 501, 501E to 535, ASA, FWSM)
    • Cisco CSS 11000 load-balancer
    • Nortel Accelar switches
    • Nortel Contivity VPN concentrators
    • Avaya ES/ERS Switches and Routing Switches
    • Juniper Routers
    • Foundry ServerIron load-balancers and switches
    • Packeteer traffic shaping appliances
    • Netscreen firewalls
    • Sensatronic environmental monitors
    • Unix server hosts with the  UCD-SNMP / NetSNMP host MIB
  7. How do I get support for genDevConfig.
  8. The documentation for genDevConfig has mistakes or omissions.
    • Contact the author at f (dot) mikus (at) acktomic (dot) com so the website and or documentation can be updated.
  9. How do I submit new modules for genDevConfig
  10. I tried to hack a new module from CiscoIOS.pm and screwed it up, how do I get a new copy.
  11. genDevConfig is open-source and comes with no garanties. If you are wholely unsatistified and think it is crap, submit constructive criticism, submit a patch or simply use something else. :-)

Leave a Reply