NetDecision Network Manager
NetDecision Network Manager allows you to perform SNMP and ICMP monitoring of IP network including ICMP (ping) and SNMP polling, SNMP traps receiving. It displays your network as multilevel graphical network topology (hierarchy).
- SNMP/ICMP polling.
- Multivendor network management (heterogeneous environment).
- Custom rules for polled data
- Custom SNMP traps handling
- Email, SMS notifications
- L2/L3 Automatic Network Discovery
- Network Topology Tree and Layer View (maps, sub-maps).
- Script-based custom actions.
- Status propagation.
- Events filters.
- Events/Alarms management. (Acknowledgment, Clear).
- Maintenance mode support. (Outage management).
- CIM-compliant network model.
- Custom MIB attributes mapped to a human readable attributes.
- Modern MS Office like ribbon-based customizable user interface.
NetDecision Network Manager is the affordable alternative to expensive and complicated high-end network management systems. Also, it"s easily configured to match your precise network environment, scalable to accommodate growth, and simple to administer.
NetDecision Network Manager delivers solutions that fit your organization"s needs. Network Manager offers a winning strategy for managing distributed multivendor networks and systems, from small workgroups to the entire enterprise. The application is designed to handle the vast array of technologies, applications, and equipment used to manage the networks of today and the networks of the future.
NetDecision Network Manager optimizes network bandwidth and computer resources. It minimizes bandwidth consumption and maximizes computer operating system resources.
NetDecision Network Manager is a solution that helps you keep your growing network up and running. With Network Manager, you can quickly create a map of your network, start monitoring, and get feedback on your network"s performance.
In NetDecision Network Manager, when you view a part of your network topology, you are actually viewing a layer. The view may be presented in a high-level layer that represents your entire network that spans the world, or in a more detailed layer of any portion of the network.
In NetDecision Network Manager you do not view a topology directly; instead, you always view the layers that comprise the topology. Layers are typically organized hierarchically to show an increasing level of detail.
A layer is a particular view of the network environment. It consists of related managed element presentations that are displayed in a single window. Each layer displays a different perspective of your topology. Network Manager creates a root layer for each topology. The root layer provides a standard, top-level layer for every topology. Layers are often organized in a hierarchical fashion for a given topology, with the root layer at the top. You can navigate among the layers of the open topology by double-clicking the mouse on explodable elements. Double-clicking on an explodable element opens a layer that displays a more detailed view. The hierarchical relationship of layers creates a parent-child relationship between them. A layer may have several child layers. The hierarchical relationship of layers enables you to view your network from a distance, or to choose a more detailed view. For example, consider a layer that contains a single element that represents an entire organization. From this high-level view of the topology, you can double-click on the element to open a child layer. The child layer may display a view of your network topology from the perspective of a particular location. From there, you can select a specific department, then a specific element. You can customize the organization of layers in a topology to suit your purposes; for example, to reflect the organization of your company.
In NetDecision Network Manager a managed element represents a particular entity or resource in a networked systems environment. A managed element might represent a physical piece of equipment on the network, the components of the device on the network, or parts of the network itself. The managed object represents the resource by modeling the characteristics (attributes) of the resource. A managed element exists on a topology by virtue of being represented by a presentation on a layer in a topology. A presentation is a graphical representation of a managed element. A single managed element can be represented by multiple presentations. Multiple presentations for the same element can exist on multiple layers of the same topology. A presentation never represents more than one object at a time. In addition to representing objects, presentations have other functions:
Presentations let you navigate through the layers of a topology. Most presentations are explodable—when you double-click on an explodable presentation, a new layer opens to let you “look inside” the object represented by the presentation.
Presentations reflect the status of the object that they represent or of objects in child layers. The mechanism is called propagation. It helps users identify problems quickly, because the status of a problematic element is propagated to the very top layer.
There are three types of managed objects in Network Manager:
The difference between physical element and logical element is that logical element can not be managed as a stand-alone object. Thus, it can be used to create geographical maps, buildings, etc. Logical element may represent a component of a physical element. Physical element has an IP address and SNMP parameters. Physical element and its components are manageable. Links connect elements.
There are four types of managed object presentations:
What user sees on the screen are presentations and not actual managed elements. Icons are images in .WMF, .BMP, .JPEG, .GIF, .PNG format. Icons are for displaying geographical maps, buildings, front panels of the hardware, etc. Graphical primitives such as rectangle, ellipse or text can be used to represent leds, displays, etc. Graphical link is a representation of a physical/logical connection between two elements.
NetDecision Network Manager receives SNMP notifications, such as traps and informs and the element status can be changed based on the information contained in PDU. There is powerful SNMP traps handling mechanism.
Events are the way to NetDecision Network manager to represent incoming SNMP notifications (traps) and assign severities to them. Once notification is received by the Network Manager, it is first passed through Notification Filters. If the notification was not filtered out, it is then mapped to an Event which is later used in Network Manager. The mapping rules are configured in Events Configuration dialog. Event contains all information from corresponding SNMP notification plus it is assigned severity and contains Event Handler name that was used in mapping.
Events are handlers for incoming SNMP notifications (traps). There are 2 ways how NetDecision Network Manager can react upon receiving SNMP notification: change the severity of a topology element specified within event configuration and execute custom script locally or on remote script server.
Events can be considered as definitions containing information on how to manage incoming notifications. In other words, events contain information on what to do when a specified notification arrives.
In order to provide the most flexible logic when analyzing and matching trap data Trap handler is built as multi-level hierarchal structure consisting of unlimited number logical operators and data comparators:
Event actions are executed using NetDecision script language which makes it highly flexible and customizable.
Configuring actions includes specifying script template to be used as action executer. Specific handler parameters are being passed to a script at runtime as script variables. These variables can be easily addressed within a script by name.
- Comparator defines what data parameter of incoming trap must be looked at in order to make a decision what action to perform next.
- Logical operator can be either "OR" or "AND". Using operators allows having complex matching criteria. For example if desired criteria consists of two required conditions that have to be TRUE in order to perform an action, you must create two different comparators and join them together using AND operator.
Network Manager provides following predefined actions:
Forward to other destination(s)
handler action allows to forward received trap to one or more
destinations. This can be useful in building distributed management
trap handler action allows to forward
received trap information to one or more
Log to a file
||Log file trap
handler action allows to append received trap information to the end of
specified log file.
Record to a database
handler action allows to store trap information in the database.
Execute external command
command trap handler action allows to execute any command or external
application passing command line parameters.
Play WAV sound
trap handler action allows to enable audible alarm upon trap receiving.
Send SysLog message
handler action allows to send out
RFC 3164 compatible
syslog messages to one or more syslog servers.
Write to Event Log
trap handler action allows to write messages to Windows Event Log on
Create task in MS Outlook
||Create task in MS Outlook
trap handler action allows the user to create task in MS Outlook
Send SMS via GSM mobile phone
||Send SMS via GSM mobile phone
trap handler action allows the user to send out mobile text message using locally connected GSM phone
Send SMS via SMPP
||Send SMS via SMPP
trap handler action allows the user to send out mobile text message directly to SMSC using SMPP protocol
trap handler action allows the user to place voice or chat message via skype
Text to speech
trap handler action allows the user to speak message using Text-To-Speech engine
trap handler action allows the user to invoke web service
handler action allows to any number of custom parameters into
a script together with SNMP PDU variable.
The element status is determined based on events that it has originated and the polling status. Each managed element has two statuses:
The status is represented by description and severity. The Network Manager colorizes the managed element presentation using severity to color mapping that is configurable by the user.
In NetDecision Network Manager events are manageable. There are three basic operations:
When technician is notified that certain event has occurred he/she can acknowledge it to let staff personal know that the event has been taken care of. When the problem is fixed so that event no longer applies, the event can be cleared out. The equipment can be put into the maintenance mode to be able to accomplish the following tasks:
The status of the device changes to MAINTENANCE ON when device is put into the maintenance mode. All events generated by equipment while in maintenance are ignored. The maintenance mode has to be turned off when the maintenance is complete.
There is an ability to filter SNMP notifications. Filtering is rules based.
Each managed element has a set of attributes. There are predefined attributes such as Name, Description, IP address, SNMP parameters, etc. and there are custom attributes that are defined by the user. You can treat attribute as a field that has name and value. There are three different types of custom attributes:
Constant attribute value is defined by the user and remains the same. MIB attribute is associated with a MIB object and gets polled. The user can define a set of rules to analyze the value of MIB attribute that is retrieved during polling and set actions to be performed when a certain condition triggers.
NetDecision Network Manager uses CIM to model devices. According to CIM model there is a containment relationship between the element and its components (cards, etc). The device can be modeled in very detailed fashion using containment relationship. Each component is presented as a logical element that does not have IP address assigned. Thus it cannot be managed as a stand-alone element. However, you can define that this element is a component of another element that has IP address assigned. When the element is a component of another element (master) it will be managed as a part of this master element. For example: a router has an interface cards. Each card can be treated as a component of a router. You can define a set of custom attributes for each interface to be mapped to a row (corresponds to a particular interface) in ifTable MIB table defined in RFC1213 (MIB-II).