Use existing account.


Community discussion.


New users click here.


Talk With Us Live

Press Releases
Current Headlines
Historical Archive


\ RSS Feed<

June 28, 2005 Contact
Kyle Lussier
408-627-7680
klussier@autonoc.com

FOR IMMEDIATE RELEASE

AutoNOC 2.5 Debuts with Network Crawler
Technology to Help Automate Management

ATLANTA, GA, June 28, 2005 - The network just broke and the boss is getting that pulsating blood vessel on his forehead again. The phone starts ringing and your pager goes off. Panic is starting to set in and the clock is ticking. Will you find the problem in time? If you were running AutoNOC 2.5 you would have already closed the ticket.

How so? Well the latest release of AutoNOC monitors pretty close to everything happening on your network even as your network changes.

We are thrilled to announce the general availability of AutoNOC 2.5. This is the most comprehensive, reliable, feature rich release of the AutoNOC integrated network operations platform to date. The core improvements enhance AutoNOC in many ways to expand opportunities for automation, increase the network scalability, while at the same time delivering a plethora of capabilities designed to save significant labor.

Some of the highlights:

  • Network Crawler Delivers Labor Savings
    AutoNOC 2.5 now includes a background network update crawler which analyzes each device in the operations model looking for changes, new components, modified configurations, etc. As it detects these the crawler will automatically make modifications to the model design. This feature saves incredible amounts of labor adjusting the operations model with respect to network design changes. Have no worries when you add that new interface, AutoNOC will find it automatically and start monitoring it without any user intervention.

  • Targeted Network Discovery
    The reality of today's networks is that perfection in network discovery is more of a "Holy Grail" than a reality. For years we thought through the case uses of discovery and the result of this is the new Network object. Some people like to build a static hand-crafted model of their network and some people like to have everything automatically mapped. For production networks, the mix is often somewhere in between. The Network object allows the user to build a custom manual static network and also to create targeted "discovery zones" that populate folders with certain sets of objects.

  • Improved Scalability for Managing Bigger Networks
    AutoNOC 2.5 unveils a major re-design of the operations core designed to handle much larger networks. The software uses less RAM per probe, indexes have been moved to disk, memory has been trimmed, more efficient handling of pre-allocated data improved, and many other things.

  • MP Thread Scaler for High Density Managed Devices
    High density devices (such as large routers and switches with many hundreds of interfaces) require sophisticated parallel data acquisition techniques to obtain reliable high resolution operations profiles. AutoNOC's new and improved 2.5 kernel implements a truly parallel multi-processing data acquisition core capable of performing 10s of thousands of parallel SNMP walks simultaneously on entire networks at a time. In test cases, AutoNOC has been able to acquire data from single devices with 10,000 probes at as high as every 15 seconds, per device. The thread scaler allows the user to adjust how many parallel acquisition threads are available to the data core allowing fast and faster data acquisition dependent on how much CPU power the user wishes to put to the task. Note that by default AutoNOC is configured to do no thread scaling, this option can be adjusted in the acquisition service (and then the software should be restarted).

  • 64-Bit Support for Terabyte Size Historical Databases
    The 2.5 release includes vast improvements to the RDX and RDB data store capabilities including full 64-bit files, continuous linked access, reduced memory usage, and many other internal improvements.

  • Automated Restart and Automated Qualify Feedback
    Delivering maximum reliability is a key requirement in today's production data centers. This latest release includes the ability to automatically restart the AutoNOC core in the event of a system issue. Also included is an automated ability for AutoNOC to send call stack and other debugging information to support in the event of such a failure. Don't worry, this capability off by default and must manually be turned on by the user.

  • External Graph Links and Portal Construction Kit
    Users can now link to specific graphs inside AutoNOC and use them as a live part of external web portals. The same is true for a variety of other little graphing widgets and other things. This is very useful when some things should be available to external users.

  • PAM (Linux) and Windows User Authentication
    No need to create user accounts in AutoNOC by hand anymore. By default AutoNOC will authenticate against PAM on Linux and Windows and create users automatically. AutoNOC does not retain any password information, so dropping the user from PAM or Windows means they will no longer be able to logon to AutoNOC.

  • Performance Optimizations and Bug Fixes
    Additionally, the 2.5 core includes vast performance improvements, bug fixes, adjustments, and other capabilities. More than 256 tracked issues have been handled in this release.

AutoNOC 2.5 can be installed by clicking on Configure | Portal Setup | Check for Updates or by downloading and installing the software manually.

About AutoNOC LLC

AutoNOC LLC was organized in Atlanta, Georgia in 1999 by commercial software veteran Kyle Lussier to develop and market the AutoNOC core network operations platform. AutoNOC LLC is first to market with a cost effective, robust, fully integrated, Web based solution for integrated network operations. For more information, visit AutoNOC’s Web site at http://www.AutoNOC.com.


Specific Issues Resolved in this Release
Below lists the specific issues resolved in this release.

IssueID Description
11 Add Time Ranges to Analyze Tab
12 Dependent Alarms
20 HTTP_GetErrorCode(page)
30 Sets should show object types, number of probes, and other specifics.
33 POP3 Test
34 SMTP Test
44 Log template links in device template.
49 Multiple Simultaneous Links, One Interface
56 Send socket sequence, return response.
58 Add main IP address to investigate and viz.
64 Check on edit row in firewall makes duplicate.
69 Make like Smokeping
72 Add ping loss ranking default report.
74 Old Sessions Still Work on Bad License Key
79 Display multiple graphs.
84 Test Component Rule Functions
87 Remember IP address after reboot.
92 Process gone probe.
102 Reports Same Day, Time, Etc.
104 Username field auto populated w/ other usernames
106 Hystersis
110 Autocreation of Service Levels
114 Failed to bind issue on restart / upgrade
122 Add screenshots to Tickets
130 Auto-Discovery
131 SMS
134 Show X
140 Multiple users of ticketing system
148 Improve query() function in CLI
150 Ability to update/read tickets in the bug system
159 Multiple Syslog Servers in Agent
162 Latest Release Causes Significant CPU Load Increase
163 Bandwidth Usage Inaccurate
167 Re-Indexing Performed at Startup
169 Better Graphs / Multivariate (Like Cricket)
171 Better Interface Change Management
175 Baseline / Trending
176 Days, Quarterly, Annually, No Sat/Sun and Time Range
186 Process Monitor
191 Graph Grouping
192 Multiple Counters in Graphs
194 Database Abstraction Layer
203 Never Finishes Loading
204 Run Report Button on Analyse Tab
205 Impossible SNMP Data Skewing Trend Line in Graphs
208 Upgrade Problems
3492 iPlanet Mail Server Not Relaying
209 Add Alarm Dependencies Documentation
210 Changing hostname crashes autonoc server
3487 Auth Fails on iPlanet Server
3537 Direct Server Links
3543 "ANOCWEB" Crash on Windows XP
3545 Incorrect Templates Assigned to Devices
3547 Document performance/CPU configurations
3548 Sporadic Crash with Heavy GUI Usage
3557 Fix  (2147483647
3564 New Case problem/Can not log in to our autonoc
3570 Crash
3572 Lost Current.rdb on Upgrade
3573 Fails to Upgrade
3575 GUI Crash on Multiple Logons
3576 Interface Speed Reading from SNMP
3578 Additional email address
3579 Device description displayed in hex
3580 Warning Message
3582 Get List of Devices with A Specific Port Open
3595 Report Removal Causes Crash
3590 Network Object
3598 Iterative Processor
3805 AutoNOC Crashes when Changing Device Template.
3754 Crash During Discovery
3611 Add New Multicast Probes, Fix Old Ones
3612 Link to Ice Graphs from Pulse Graphs
3613 Improper Reporting of space on /tmp?
3615 Show Same Probe from Similar Components
3616 Pulse Graph Jumps to Detail Graph
3623 Tooltips Do Not Work
3624 Alarm Page Tooltip "Reset Alarm" Wrong Text
3625 Tacacs+ Authentication support
3626 On the fly Switching of Graph Type on Investigate
3627 Zooming in Beyond 30 Mins Needs Hashes
3628 Failed to Send / Close out on Web Server
3637 Vendor supplied MIBs are not imported into Autonoc
3638 Delete is Slow
3648 IETF Counters Showing Zero Every-Other Polling Interval with 10 minute interval
3655 Odd cases in graph zooms shown incorrect.
3653 Wrong Units on Graphs
3654 Support 64-Bit Bit Counters
3658 External Path Access to Graphs & Data
3660 % Idle Time Probe Expression Incorrect
3662 AutoNOC 2.4.3 slows to a crawl and becomes unusable
3664 Free PDU Called Twice?
3665 Storage/% Disk Idle Time probe service level order incorrect
3666 Problems with 2.4.100
3667 Reports display when disabled
3668 Add Regular Expression Support to Interpreter
3670 Interface type filtering criteria doesn't work.
3671 Allow Display of Folders in Investigate
3673 Finish Up - Post Crash
3677 Modify IFType 131
3678 Interface Utilization not Valid, Traffic in/out (non-cisco) HC not valid
3679 AutoNOC Daemon Stops Running
3680 Complete Implementation of Network Object
3681 Complete Dev/Info and Auto-Manager
3682 CSV Files Not Loading
3683 HC Bit not Set, Various 64-bit Bugs
3685 Crash
3686 Duplicate IDs
3687 Find Similar Interfaces rather than just Get
3688 Visualization Image Export
3693 Add Start-Up Auto-Fire Switch
3694 Acquisition Wrong Value on First Poll
3695 Slow Discovery on Port Scans during Re-Discover
3696 Removal of States Doesn't Clear & Re-Eval Last SLA
3697 Y-Scale Values Truncated
3698 Licensing Warning Shows 0 days, but 2 After
3700 Broadcast Out / Broadcast In non-hc probes
3701 Add Stop Discovery Button.
3703 Adding Agent PW's Adds blank to SNMP.
3707 Network Doesn't Delete Objects
3708 Discovery Doesn't Setup Links
3709 Service Levels not Updating After Discovery
3710 Automated Re-Firing of Discovery
3711 NewItemAdded Filler Folders Leaked
3714 Duplicate IDs All over the Place
3716 Old Interface still Reporting Data
3718 Support Customer 'X' Allowed Discovery Techniques
3736 Improve SYSNAME Support in Discovery
3737 Support Local Linux/Windows box Authentication
3743 Direct Links to Graphs with Export for Tickets
3751 Write Model on Manual Change
3752 User Experience Crash During Folder Move
3753 New Item Tracing Issue
3755 Alternative ifAlias Name OID
3756 Wrong device template duplicated.
3757 Large Model Crashes on Loading
3758 Support for SNMP Bulk Get
3759 Set Not Working as Should
3761 Upgrade to HTTP/1.1
3762 Lost Histories when Moving Objects Around.
3764 Crash on Item Clicked Dialog Gen (Device Interface)
3766 Zoom to ~ sub 2min stops showing data in 2.5006b
3771 Negate Criteria
3777 New Flags on Linux Build Don't Work
3778 Crash & No Log File on 8x3
3779 Clicked on Discover Now Should be Fast
3782 Exception in Discovery Service
3785 Rename Object
3786 Deleted devices show up in Visualize
3791 Incorrect Return Code for CD
3792 DiscoverDevice Doesn't
3793 SetVariable Doesn't Exist?
3794 Add Mkdir folder equivalent.
3795 Adjust sysDescr for Catalyst/Cisco Big Devices
3796 Don't Discover Down Interfaces
3798 Grace Period Before Auto-Modeler Deletes
3799 Graph Y-Axis on <1 is Wrong
3800 Slow De-Duplicator of Drop-Down Lists in GUI
3801 Wait State on Probes Not Being Reset
3802 Persistence Bad Block Corruption Causing Crash
3803 Toggle Drop Domain Names from Devices
3806 Add Marker to GUI when Device Discovering
3807 One Hour Quick Graph
3808 Modify SLA for Multicast
3809 Deleting Probes/Templates Doesn't Decrease Wait Counter
3810 AutoNOC Deleting When it Shouldn't
3811 Fix "Heavy Traffic" Bug on Discovery
3813 Network Re-Discovery Destroys Histories
3814 Local _IO_vfscanf Crash Replication in Cache/Stack Maintenance
3784 Various crashes on RH Boxes inside Memory Allocation calls
3815 Crash in Post Frame Receivers
3816 Globally Readable by Default
3820 Probes Added to Root Directory?
3821 Parsing Assertion
3822 Multi-Crash
3823 Some Interfaces Stopping Data Collection
3825 Off by 10X
3826 SNMPTableIndexify
3827 Transfer To Count Assertion
3828 AddIndexBlock_NoLock_ and _IO_vscanf
3830 Interfaces Not Being Dropped
3832 Utilization Computations Incorrect
3833 Remove 5000 line item Limit
3835 Modify In Receive / Out Datagrams
3829 Change Graph Type Ignored
3838 Bug
3840 Discovery Star Doesn't Show Immediately
3841 Clear Full Cache for IP on Discovery
3842 Drop ifAlias and proprietary name from Discovery Name
3861 Windows Agent 1.5 CPU % Processor Time reporting nearly 100%
3862 Crash on Model Writing.
3863 Crash on Submit in GUI
3846 (itm->GetChild()==__null)||(itm->GetChild()==children).
3847 IsWaitSolve Tripping
3848 Top-Level GUI to Slow on Seattle
3849 Try to discover Avaya P550 Cajun kills AutoNOC 2.4.35
3850 Discovery Performance Poor When Moving Devices
3853 No Connections Show in Visualize
3855 Disconnected Devices Still Posting Values
3856 Get Prior State Returns No State
3857 !m_ReadingCount
3858 Delete with Data
3859 _IO_vscanf File Duplicate Lock Conflict with Linux Kernel
3860 Bad Block
3865 Overlay Not Working
3866 Receiver Frame Goes Bad Before Finishing Posting
3870 Using Too Much CPU
3868 ASSERT Tripping on Apply Update
3869 Acquisition Freezes
3872 Set Telnet Probe to 60 mins and test make sure it works.
3873 Initial Discovery Uses Too Much RAM
3874 Add PPS Probe
3875 Port Channel Interfaces Still have Weird Values
3879 Manual Discovery / Incremental bug?
3878 Grace Period Not Working Right
3882 /Users 2005 / 5000
3881 Calculation Error with Congestion Probe
3883 Sort on Alarm Level Wacky
3884 Various Probe Modifications
3885 Memory Utilization Grows Slowly
3888 User Can't Start Software Using Normal Scripts
3893 Gaps on RDB Maintenance
3897 Dots Graph Broken
3895 Crashing on Discovering a Windows Server
3900 Full Recoil & Rebuild Not Working
3902 Two Devices Started Reporting 0Bps
3903 Folder Criteria needs to allow inside folder and show all folders
3905 Add Device, Component, Probe Text to Graphs
3906 CRC Error In has Negatives
3907 GUI Not Allowing Clicks on Some Interfaces
3909 Modify Probe Templates to Be able to Drop Collisions for VirtInts
3911 Discovery will sometimes put categories in root
3912 Derive proper names for catalyst 6x00 temperature probes
3913 External Graph Link Broken in 25-107-rc5
3916 Some Letters Unreadable
3917 SNMP_GetRowCount Failing
3920 User Reporting Inconsistent Discovery on Two Identical Hardware Platforms
3921 Report Set Not Being Used for Some Reason
3922 Current Value Obscured by Peak Line
3925 Errors In and Errors Out have swapped oids
3926 Device 'X'  is showing errors in where there are none
3927 User Experienced Failed Recoiling
3929 Path Links Not Clickable on Investigate
3930 Graph Lettering Missing Symbols
3932 Add Type-Specific Expression to all Criteria
3934 Data Gaps above 2G on some Ten gig ints
3937 Devices / Descriptions not Properly Discovered [2.5.111]
3938 Case Issues with Discovery on Same Device
3945 Data in graphs will disappear.
3946 Data Disappears During
3951 Probe Poll Notification Caused Crash
3952 Can not Change Polling IP of Device by Editing Variable
3954 Modify PPP Interface to Ignore State on Oper
3957 Alarm Min. Firing Interval
3958 Add Device Failure Probe
3960 Related Probes Link Not visible to Standard Users

 

(C) 2007 - All Rights Reserved - AutoNOC LLC
      Call me!