NNMi 8: From words to deeds
At the beginning of last year, the 8th version of one of the best computer network management programs, Network Node Manager, was released, which, unlike previous versions, is designated as NNMi . This is not accidental, since it is a freshly written software product that incorporates the most interesting and promising from previous versions, as well as from open source software. And just recently released the 6th patch for version 8.10.
Those familiar with previous versions of the 6.x / 7.x product probably had some eclecticism. With all the stability, maturity and scalability, it combines a variety of system components written at different times, different interfaces and paradigms.
For example, the Motif ovw interface is good for monitoring bus or star topologies, with many user machines, or for building a network map, and Dynamic Views web interface is best suited for complex topologies with multiple routing and switching devices, where Networks are set, and connections do not change hourly.
')
All this leads to some confusion, and not all users confidently use one or other components optimally.
What pleased me eight? There is no eclecticism - the unity of style and architecture. The user interface is completely AJAX-based, and only allows access via a web browser. Observation of the network is more accurate than in the Extended Topology of 7, and there is no periodic full intelligence. If 7-ka required knowledge of 10 thousand configuration files, then 8-ka stores all settings in the “Configurations” tab.
In general, 8-ka professes a completely different paradigm - it focuses on incidents, and fully complies with the ITIL v3 standard, while 7-ka focuses on network maps. It can be simplified to say that the 7-ki operator launched NNM to look at the map, and the 8-ki operator - in order to check the incidents.
If the 7-ka is too “talkative”, and the operator needed to conjure up in ECS, so that the network status messages would be essentially, and still there would be a lot of them, and in 8-ke there is nothing to do - only incidents come causes and consequences within them.
In the 8th version a lot of open source software was used. Here are just a few of them: PostgreSQL , JBoss , Tomcat , Hibernate . Apparently, the product only won from this: 8-ka is much more productive than the previous version, it can handle more events per second.
During this time, 8-ka learned to work in clusters, maintain LDAP authentication, and become faster and more stable. A number of “bells and whistles” or iSPI (smart plug-ins) appeared: iron performance measurement, IP telephony, MPLS, multicast and others.
Those familiar with previous versions of the 6.x / 7.x product probably had some eclecticism. With all the stability, maturity and scalability, it combines a variety of system components written at different times, different interfaces and paradigms.
For example, the Motif ovw interface is good for monitoring bus or star topologies, with many user machines, or for building a network map, and Dynamic Views web interface is best suited for complex topologies with multiple routing and switching devices, where Networks are set, and connections do not change hourly.
')
All this leads to some confusion, and not all users confidently use one or other components optimally.
What pleased me eight? There is no eclecticism - the unity of style and architecture. The user interface is completely AJAX-based, and only allows access via a web browser. Observation of the network is more accurate than in the Extended Topology of 7, and there is no periodic full intelligence. If 7-ka required knowledge of 10 thousand configuration files, then 8-ka stores all settings in the “Configurations” tab.
In general, 8-ka professes a completely different paradigm - it focuses on incidents, and fully complies with the ITIL v3 standard, while 7-ka focuses on network maps. It can be simplified to say that the 7-ki operator launched NNM to look at the map, and the 8-ki operator - in order to check the incidents.
If the 7-ka is too “talkative”, and the operator needed to conjure up in ECS, so that the network status messages would be essentially, and still there would be a lot of them, and in 8-ke there is nothing to do - only incidents come causes and consequences within them.
In the 8th version a lot of open source software was used. Here are just a few of them: PostgreSQL , JBoss , Tomcat , Hibernate . Apparently, the product only won from this: 8-ka is much more productive than the previous version, it can handle more events per second.
During this time, 8-ka learned to work in clusters, maintain LDAP authentication, and become faster and more stable. A number of “bells and whistles” or iSPI (smart plug-ins) appeared: iron performance measurement, IP telephony, MPLS, multicast and others.
Source: https://habr.com/ru/post/77128/
All Articles