NINO means: Nino Is Not Openview. NINO is a Network Management Solution, a web application to monitor your network devices and network traffic from a web browser. NINO is opensource and may be distributed like Perl, Linux etc. Go to: general description of NINO
|
On the left side the main menu can be used to navigate. Just click the function you want.
In this example the functions are TOP and INFO, this will navigate to the top of this document or to the info page. NINO uses this kind of menu's.
|
The main screen looks like this:
There are several ways to display a device: via menu MAP, DEVICE or DEVICES.
Use menu DEVICES to browse all devices and groups. Open a folder and all devices in that group will be displayed. Click on the host link to display a device.
Click on to edit the device or group properties. Open the device in the browser for monitoring details, events and plugins. Open
to view monitoring statistics.
Click on
to view the events with the highest severity status of this device.
Click on
to open the plugins folder. The Hostmeter plugin can be started from here. Hostmeter will show all system statistics in one dashboard view.
Browser | ![]() | Name | Location | Severity | |
---|---|---|---|---|---|
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() ![]() | ![]() | ams3rt10 | ams_pop03 |
| |
![]() ![]() ![]() | ![]() | ams3rt11 | ams_pop03 |
| |
![]() ![]() ![]() | ![]() | ams3rt12 | ams_pop03 |
| |
![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() ![]() ![]() ![]() | |||||
![]() ![]() ![]() ![]() ![]() ![]() ![]() | |||||
![]() ![]() ![]() ![]() | |||||
![]() ![]() ![]() | ![]() | ams3rt13 | ams_pop03 |
| |
![]() ![]() ![]() | ![]() | ams3rt14 | ams_pop03 |
| |
![]() ![]() ![]() | ![]() | ams3rt15 | ams_pop03 |
| |
![]() ![]() ![]() | ![]() | mdmpool1 | ldn-pop01 |
| |
![]() ![]() ![]() | ![]() | sw406_rt | ldn-pop01 |
| |
![]() ![]() ![]() | ![]() | mnl99 | Manila |
| |
![]() ![]() ![]() | ![]() | us843_rt05 | - |
| |
![]() ![]() ![]() | ![]() | us281_rt12 | Jersey |
| |
![]() ![]() ![]() | ![]() | dv9_rt161 | - |
| |
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() | |
|
A brief description of the buttons used in the device browser can be found in the table below.
Button | Description |
10.1.1.12 | Display device (19" rack view) |
![]() |
Configure monitoring preset, preset group or monitoring configuration for a device |
![]() |
Open monitoring preset group |
![]() |
Open monitoring statistics |
![]() |
Plot a graph of this monitoring item |
![]() |
Modify device properties or add/delete a device |
![]() |
Open plugins such as Hostmeter |
![]() |
Show events for this device |
To display a new device, click on the menu DEVICE. This function will show the screen below. Enter the hostname or IP address and snmp community string to view a device. Enter more hostnames (comma seperated) to display more devices. The default community string is public. Select Device View in the option-menu and press the GO button to display the device.
The checkbox All devices will show a list of devices. Just click on the underlined device to view that device. To view all devices, select or deselect the View checkbox and click Apply to view all. Note: please be patient, it takes time to get all snmp data to view all devices.
The device is displayed as a semi 19'' device. The standard RFC1213-MIB-II is used to display all interfaces. This will make NINO a universal device browser. Click on a button or interface to view more information.
![]() |
![]() |
![]() | |||||||||
![]() |
|
![]() | |||||||||
![]() |
![]() |
![]() |
The functions are listed below:
Button | Description |
![]() |
Show device information |
![]() |
Show realtime network traffic (IfOctets) |
![]() |
Add or delete a device |
![]() |
Show device routing table |
The color definitions are listed below:
Interface Color | Admin status | Oper status |
![]() |
UP | UP |
![]() |
UP | DOWN |
![]() |
DOWN | DOWN |
![]() |
UP | Testing/Dormant |
![]() |
DOWN | UP |
The interface definitions are listed below:
Interface | Description |
![]() |
Ethernet |
![]() |
Token Ring |
![]() |
Fiber, FDDI, Shortwave Gigabit Eth. |
![]() |
Serial, X25, lapb, T1, E1, T3 |
![]() |
WAN, Frame Relay |
![]() |
ISDN |
![]() |
PPP, SLIP |
![]() |
Loopback |
![]() |
Unknown, other |
By clicking on a function button or interface, the screens below will appear. Some screens provide edit functions, to alter system name, contact or location. Interfaces can also be disabled or enabled. Edit functions use snmpset and need a write community string.
The interface information contains the status, description, network traffic (IfOctets), interface errors, unicast, non-unicast packets and discards.
Please notice that the values shown are snmp counters. These counters will increase. Press the
button to display realtime network traffic in Bit/s.
The snmp counters are equal to the counters displayed at Cisco's show interface command.
The interface can be disabled or enabled using the checkbox. This action is done using snmpset.
The device information contains system name, uptime, contact and location. This information may be edited and will be stored using snmpset.
This is an example of a routing table (part of it).
Network | Mask | Next Hop | Metric | Age | Protocol | Interface |
---|---|---|---|---|---|---|
10.1.0.0 | 255.255.0.0 | 10.211.0.1 | 1777920 | 1398270 | IGRP | - |
10.4.0.8 | 255.255.255.252 | 10.211.0.1 | 1787648 | 3283066 | IGRP | - |
10.5.1.0 | 255.255.255.0 | 10.211.0.1 | 41561856 | 22894 | IGRP | - |
10.57.39.126 | 255.255.255.255 | 10.200.0.1 | 41561856 | 187 | IGRP | - |
10.95.1.0 | 255.255.255.0 | 10.211.0.1 | 6561536 | 791847 | IGRP | - |
10.95.2.0 | 255.255.255.0 | 10.211.0.1 | 6561536 | 791847 | IGRP | - |
10.101.0.0 | 255.255.0.0 | 10.101.0.1 | 0 | 0 | Local | TokenRing4/0 |
10.102.0.0 | 255.255.0.0 | 10.101.0.40 | 281856 | 1398273 | IGRP | - |
10.105.8.0 | 255.255.255.0 | 10.105.8.254 | 0 | 0 | Local | Ethernet5/0 |
10.105.9.0 | 255.255.255.0 | 10.105.9.254 | 0 | 0 | Local | Ethernet5/1 |
10.105.10.0 | 255.255.255.0 | 10.105.9.2 | 5537536 | 613945 | IGRP | - |
10.145.2.0 | 255.255.255.0 | 10.218.0.2 | 5537536 | 4294967 | IGRP | - |
10.145.3.0 | 255.255.255.0 | 10.220.0.2 | 5537536 | 4294967 | IGRP | - |
10.145.4.0 | 255.255.255.0 | 10.221.0.2 | 5537536 | 4294967 | IGRP | - |
10.145.5.0 | 255.255.255.0 | 10.222.0.2 | 5537536 | 3696446 | IGRP | - |
10.145.6.0 | 255.255.255.0 | 10.223.0.2 | 5537536 | 4294967 | IGRP | - |
10.145.7.0 | 255.255.255.0 | 10.224.0.2 | 5537536 | 613938 | IGRP | - |
10.145.8.0 | 255.255.255.0 | 10.225.0.2 | 5537536 | 4294967 | IGRP | - |
10.148.0.0 | 255.255.0.0 | 10.105.9.2 | 281856 | 1398273 | IGRP | - |
10.200.0.0 | 255.255.0.0 | 10.200.0.2 | 0 | 0 | Local | Serial8/3 |
10.201.0.0 | 255.255.0.0 | 10.211.0.1 | 2273792 | 1398273 | IGRP | - |
10.202.0.0 | 255.255.0.0 | 10.200.0.1 | 6023936 | 1398273 | IGRP | - |
10.203.0.0 | 255.255.0.0 | 10.200.0.1 | 6023936 | 1316298 | IGRP | - |
10.204.0.0 | 255.255.0.0 | 10.211.0.1 | 6023936 | 637613 | IGRP | - |
10.205.0.0 | 255.255.0.0 | 10.211.0.1 | 6023936 | 1398273 | IGRP | - |
10.207.0.0 | 255.255.0.0 | 10.211.0.1 | 6023936 | 1398273 | IGRP | - |
10.211.0.0 | 255.255.0.0 | 10.211.0.2 | 0 | 0 | Local | Serial9/4 |
10.212.0.0 | 255.255.0.0 | 10.211.0.1 | 2273792 | 4294967 | IGRP | - |
10.217.0.0 | 255.255.0.0 | 10.217.0.1 | 0 | 0 | Local | Serial8/5 |
10.218.0.0 | 255.255.0.0 | 10.218.0.1 | 0 | 0 | Local | Serial8/6 |
10.220.0.0 | 255.255.0.0 | 10.220.0.1 | 0 | 0 | Local | Serial8/0 |
10.221.0.0 | 255.255.0.0 | 10.221.0.1 | 0 | 0 | Local | Serial8/1 |
10.222.0.0 | 255.255.0.0 | 10.222.0.1 | 0 | 0 | Local | Serial8/2 |
10.223.0.0 | 255.255.0.0 | 10.223.0.1 | 0 | 0 | Local | Serial9/1 |
10.224.0.0 | 255.255.0.0 | 10.224.0.1 | 0 | 0 | Local | Serial9/0 |
10.225.0.0 | 255.255.255.252 | 10.225.0.1 | 0 | 0 | Local | Serial9/3 |
10.226.0.0 | 255.255.255.0 | 10.105.9.2 | 40537856 | 1398274 | IGRP | - |
10.233.0.0 | 255.255.0.0 | 10.211.0.1 | 6535936 | 791848 | IGRP | - |
10.234.0.0 | 255.255.0.0 | 10.211.0.1 | 6535936 | 791848 | IGRP | - |
10.250.0.0 | 255.255.255.0 | 10.250.0.1 | 0 | 0 | Local | Dialer1 |
10.250.1.0 | 255.255.255.0 | 10.250.0.2 | 0 | 12 | Local | TokenRing4/0 |
10.254.5.0 | 255.255.255.0 | 10.200.0.1 | 1915648 | 1398273 | IGRP | - |
10.254.52.0 | 255.255.255.0 | 10.211.0.1 | 2427648 | 791848 | IGRP | - |
10.255.1.0 | 255.255.255.0 | 10.211.0.1 | 0 | 12 | Local | TokenRing4/0 |
89.0.0.0 | 255.0.0.0 | 10.105.9.2 | 281856 | 1398274 | IGRP | - |
141.128.224.0 | 255.255.255.0 | 10.105.9.2 | 40537856 | 1398274 | IGRP | - |
In the DEVICES menu or in the device display a device may be added or deleted. Click on to edit the device properties.
Click on
to view the events with the highest severity status of this device.
Click on
to open the Hostmeter screen. Hostmeter will show all system statistics in one dashboard view.
Browser | ![]() | Name | Location | Severity | |
---|---|---|---|---|---|
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() ![]() | ![]() | ams3rt10 | ams_pop03 |
| |
![]() ![]() ![]() | ![]() | ams3rt11 | ams_pop03 |
| |
![]() ![]() ![]() | ![]() | ams3rt12 | ams_pop03 |
| |
![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() | |||||
![]() ![]() ![]() ![]() | |||||
![]() ![]() ![]() ![]() | |||||
![]() ![]() ![]() | ![]() | ams3rt13 | ams_pop03 |
| |
![]() ![]() ![]() | ![]() | ams3rt14 | ams_pop03 |
| |
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() | |
|
Clicking the button will display this screen.
Just fill in the form and submit changes. Changes are applied to NINO only and will not affect the device.
If the device is new, the monitoring preset groups will be auto-discovered. If the device is a server, also the most important host processes will be detected and monitored. In the next screen this may be changed and saved. Click on All presets to setup individual monitoring presets for this device. A preset group is a group of monitoring presets. A monitoring preset is used to collect monitoring data, such as network traffic or CPU utilization.
NINO uses monitoring to collect data or get status info. Monitoring can be done realtime on the fly or in the background using Collect Monitoring Statistics. The NINO monitoring toolkit has several components:
Monitor Presets are used to measure all kinds of values, such as network traffic (IfOctets), Errors, HTTP Get reponse times, SMTP status and more. Monitor Presets can be customized and added. Monitoring groups can be created to group a logical set of hosts with monitored interfaces. Groups can be used in reporting, monitor status and realtime view. Status Monitoring can be enabled to send SNMP traps if hosts do not respond. The Node Up/Down events will be stored in the eventlog database. Using event actions, e-mail or SMS notification can be configured.
How do I monitor ?
The basic steps to monitor a device are very simple. Select in the main menu the DEVICES function.
Open the group and the device you want to monitor. Click on the button next to Monitor to setup monitoring for this host.
Browser | ![]() | Name | Location | Severity | |
---|---|---|---|---|---|
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() ![]() | ![]() | ams3rt10 | ams_pop03 |
| |
![]() ![]() ![]() | ![]() | ams3rt11 | ams_pop03 |
| |
![]() ![]() ![]() | ![]() | ams3rt12 | ams_pop03 |
| |
![]() ![]() ![]() ![]() | ![]() | ||||
![]() ![]() ![]() ![]() | |||||
![]() ![]() ![]() ![]() | |||||
![]() ![]() ![]() ![]() | |||||
![]() ![]() ![]() | ![]() | ams3rt13 | ams_pop03 |
| |
![]() ![]() ![]() | ![]() | ams3rt14 | ams_pop03 |
| |
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() | |
| |||
![]() ![]() | |
|
In this screen the preset groups are displayed. The easiest way to setup monitoring for this host is auto-discovery using the Discover button. For advanced monitoring other preset groups or individual monitoring presets can be enabled for a device. Click on the All Presets link to get a list of all presets. Check the presets in the Monitor colum to monitor the device with selected presets. Check the presets in the Status colum enable status monitoring. With status monitoring alarms are send to the eventlog. Default the uptime is checked to monitor the status of a device. If a device does not respond, the device is reported down with a Node Down event. The HostProcs preset is used to monitor server processes. If a process is down, this will be reported in the eventlog. Preset groups are groups of presets to make monitoring easier to use. Click on the preset group link to edit a preset group.
Select in the main menu the DEVICES function.
Then click on a host. The host will appear in a semi 19" rack device view. Click the button in the device view to view the realtime monitoring. A graph of all monitoring during last hours on that device will be plotted.
The screen will be refreshed every minute.
The monitor screen can be used to view graphs, configure monitoring presets and preset groups.
Select in the main menu the MONITOR function.
The monitor screen will display a preset group browser. Opening a preset group will show inidividual monitoring presets.
In the example below the preset group Host contains the monitoring presets Disks, HostCPU, IfErrors and IfOctets.
Opening a monitoring preset will show all devices that are monitored with that preset. Opening a device will show all
monitored objects, such as interfaces or disk partitions. Click on the button
to plot a graph. Click on the host link to edit graph settings and plot a graph.
Click on the
icon to apply the preset to multiple hosts or edit the monitoring preset.
The monitor group view will display the status of monitoring presets combined in a group. These groups can be configured using the Edit button and used for reporting.
To view all monitoring presets, click on All.
The Status button will show the realtime status of a monitoring group using meters and bars.
Select in the main menu the MONITOR function.
The monitoring browser screen will be displayed.
Then open the preset group and open the preset.
Select the host link to customize graph settings or select the button to view the last hours of the graph.
The next step is to select the interfaces to plot. Default the actual network traffic,
this is the Collect radio button is selected. Select Trend to plot average traffic per day. Click Apply to plot the graph.
Select the Report radiobutton and choose a monitoring group to add the interfaces to a monitoring group.
The monitoring groups can be used again to plot graphs in reports and templates.
The network traffic from the selected interfaces will be plotted in a graph. Move with pressed mouse button in the graph area or scale area to zoom or move the plotted data. Click on the sum button to display the sum of all data in a graph. All data is stacked on top of eachother. Click on the fill button to display a filled or line graph. The Report link will plot a minimal report. The Data link will open the raw data, e.g. exporting to Excel.
Select in the main menu the DEVICES function.
The device browser screen will be displayed.
Then open monitoring on a device and click on the preset group where the preset is located.
Click on the properties icon of the monitoring preset.
Checking the hosts using the checkbox will activate the monitoring preset for all selected hosts in the list.
Click Apply to submit. All checked hosts are now monitored. If the device list is very long use the search function.
Click on the Configure preset link to configure the preset.
Select in the main menu the DEVICES function.
The device browser screen will be displayed.
Then open monitoring on a device and click on the preset group properties icon.
Checking the hosts using the checkbox will activate the monitoring preset for all selected hosts in the list.
Click Apply to submit. All checked hosts are now monitored. Click on the Edit presets in preset group link to configure a preset group.
The preset group is a logical group of related monitoring presets, such as the Windows or Network preset group.
Select in the main menu the DEVICES function.
The Preset Groups have icons.
Click on the Properties
button and on the Edit presets in preset group link to configure the preset group.
A monitoring preset is a dataset of monitoring properties. A preset can be a dataset to monitor network traffic, disks, CPU or whatever you want to monitor. NINO can use SNMP, WMI, TCP, HTTP or using free commands to monitor devices. NINO provides also tools to monitor TCP and HTTP response in ms.
There are several kinds of monitoring:One example is the monitoring of network traffic. The IfOctets preset contains the OID's of incoming (snmp oid => .1.3.6.1.2.1.2.2.1.10.interfaceIndex - IfInOctets) and outgoing (snmp oid => .1.3.6.1.2.1.2.2.1.16.interfaceIndex - IfOutOctets) traffic. Also the value description (Bit/s) and description OID to display interface names (e.g. eth0) is defined in the preset. In general the next items can be defined in the preset parameters:
Service response monitoring is used to monitor HTTP or TCP services. FTP, mail and web response can be monitored in a detailed way. Network and DNS delays are measured and also application response with the HTTP fetch time. Using this tool it is possible to troubleshoot performance issues, detect network or DNS problems and see how your web application performs. Click on menu TOOLS and click on the Service Response link.
Service Response: |
|
http://www.cnn.com | ||
Total: | 1066.2 ms | Save as preset: ![]() | ||
![]() | 122.056 ms | Time to resolve hostname to ip: 64.236.16.116 | ||
![]() | 169.273 ms | Time to setup network connection | ||
![]() | 107.971 ms | Application response | ||
![]() | 666.9 ms | Time to fetch content data |
Content: |
Service response can also be used to monitor values from a web based application. Example: application writes to HTML page. This page can be used as input for NINO.
Variable | Value |
Web users: | 122 |
CPU: | 12.5 % |
Cache: | 876 MB |
Select servcice web variables to edit the variables you want to monitor. NINO will use a search string and capture the next word. So in this example the variable / search string Web users: will have result: 122. Click on the Save button to create a monitoring preset. Using this feature NINO is able to log, create graphs and reports using web pages as input.
Example: The Apache server-status page can be monitored using Service response - web variables.
The network traffic is monitored to read snmp counters from a device interface. But there is more: not only the interface traffic can be monitored, but also the errors, Frame Relay per DLCI, IP traffic or any other traffic can be monitored. The only restriction is the support of snmp from the device.
Description of snmp counters:SNMP Preset | Description | Value |
IfOctets | Interface traffic in octets | 8 bits |
FrOctets | FrameRelay traffic in octets | 8 bits |
IfErrors | Interface Errors | Errors |
Unicast | Interface unicast packets | Packets |
NUnicast | Interface Non Unicast packets | Packets |
The interface information screen will show snmp counters. NINO will use a formula to convert Octets/s into Bit/s in the monitoring graph or in realtime monitoring screens. How does it work ? Every interval the snmp counters are read form a device. To get the monitoring data, you'll need two counters and the time interval in seconds. These values are computed into a Value/S. The Octet values are converted in Bit/s. Example:
Time | IN Octets counter | OUT Octets counter |
t=0 seconds | 3241004 | 2541164 |
t=10 seconds | 3294511 | 2611541 |
The total IN octets in 10 seconds: 3294511 - 3241004 = 53507 The total OUT octets in 10 seconds: 2611541 - 2541164 = 70377 Total IN + OUT octets in 10 seconds: 53507 + 70377 = 123884 Formula: (Octet = 8 bit) network traffic = ( 8 * Octets ) / (tend - tstart) in Bit/s Total: (8 * 123884) / 10 = 99107 Bit/s
This formula needs to be entered in the preset configuration screen. The formula uses standard calculus notation as input and has some pre-defined functions. The formula field may be left empty if no formula is used.
Counter32( host:port:snmp_oid ) : 32 bit counter function to calculate new value - old value the host and port must be left empty if no specific host or port is defined other than default. duration : duration in seconds, new timestamp - old timestamp from logfile * / + - ( ) : standard calculus symbols Example IfOctets: 8 * (counter32(::.1.3.6.1.2.1.2.2.1.10) + counter32(::.1.3.6.1.2.1.2.2.1.16)) / duration
Click on menu MONITOR, browse a preset from the screen and click on the icon.
Click on the Configure preset link to edit the preset. Create a new preset by changing the preset name.
This example shows the network traffic IfOctets preset. The total network traffic needs to be calculated using formula below. The IfInOctets and IfOutOctets are added and a Bit to Byte conversion is calculated. Because IfInOctets and IfOutOctets are counter-values, the counter32 function is used to substract new value - old value.
This example shows the Load15 preset. The average system Load of the last 15 minutes is monitored with this preset. The threshold levels are set to trigger alerts in the eventlog.
Optional threshold levels can be defined to trigger alerts if the threshold levels are exceeded. Each threshold has a Lower limit and Upper limit and a SNMP trap OID. If the monitoring data enters the range between the lower or upper limit a SNMP trap will be send. The alert will appear in the eventlog, including a link to plot a graph.
The alerts also need to be configured in the eventlog. For each threshold an event must be defined with the right severity level. Also event recovery must be configured to clear the high severity status if the level is back to normal again. Optional event actions can be configured to send e-mail alerts or escalation events. An escalation event could be triggered if the monitoring data exceeded the threshold limit (minor event A) and does not recover in 15 minutes (critical event B). Common sense is to configure e-mail notification only on escalation events to prevent spam. The "threshold" events should be configured to send escalation and recovery events or else it will not work.
The threshold name, lower limit, upper limit and SNMP trap OID must be filled in. Optional filters, such as the colum in the monitoring data file or hosts can be filled in to send alerts only if applicable. Escalation events must be configured in the EVENTS editor.
By default NINO has several monitoring queues to handle monitoring. Each queue can be configured with a cycle duration in seconds. The services process will control all monitoring queues, such as manual stop or start, automatic restart if the queue is down or hanging.
It is possible to create new monitoring queues and alter cycle times. Also test queues can be defined to test new monitoring presets or realtime troubleshooting with a cycle refresh of 10 seconds.
Select in the main menu the TOOLS function. The next options are available.
Devices & Groups |
---|
New device |
Device type |
New group |
Group Properties |
Discover IP range |
Discover network |
Discover using seed file |
SNMP & WMI Tools |
---|
Device |
Scan MAC address / hosts |
SNMP Walk |
SNMP Trap send |
Search MIB database |
MIB Browser |
Import MIB files |
WMI Browser |
Service Response |
Select in the main menu the TOOLS function. Click on the link Discover IP range. Fill in the start IP address and the end IP address of the IP range. The alternative community string can be used for devices using another community string than the default public. Example:
The scan will be scheduled at once and the results are stored in a scan report in the report directory. This report auto-refreshes to view the status. Hostname, IP and network information is stored the database and summarized in the report.
Select in the main menu the TOOLS function. Click on the link Discover network. Fill in the default gateway IP address and the maximum nodes to be scanned in a subnet. The alternative community string can be used for devices using another community string than the default public. Example:
The scan will be scheduled at once and the results are stored in a scan report in the report directory. This report auto-refreshes to view the status. Hostname, IP and network information is stored the database and summarized in the report.
Select in the main menu the TOOLS function. Click on the link Discover using seed file. Upload the seed file containing hostnames or IP addresses you want to discover. The alternative community string can be used for devices using another community string than the default public. Example:
The scan will be scheduled at once and the results are stored in a scan report in the report directory. This report auto-refreshes to view the status. Hostname, IP and network information is stored the database and summarized in the report.
Select in the main menu the TOOLS function. Click on the link snmpwalk. Fill in the hostname, community string and the OID. Default UDP port 161 is used, but when using Oracle OEM, port 1161 is used for the native agent. Applications like ATG Dynamo use udp 8870, 8871 etc. to read out session information and Java free memory.
Select in the main menu the TOOLS function. Click on the link MIB Browser. The next browser screen will show all information of the loaded MIBs. It is required to import MIB files first. MIB files are located in the docroot/mibs directory. The MIB information is stored in the MySQL database. From the MIB browser it is easy to test SNMP queries and create monitoring presets. Select a MIB to view information. Click on the OID to perform a SNMP walk. Apply will create a monitoring preset using the MIB information.
The Windows Management Instrumentation (WMI) can be used to get windows information. However it is required to setup a windows administrative account and password in NINO. This is done in menu ADMIN, SECURITY. To browse WMI, select in the main menu the TOOLS function. Click on the link WMI Browser. Fill in the hostname and optional a search string to find WMI classes. Then a list of WMI classes will be displayed. Select a class to get all information from that class on the selected host. It is also possible to create monitoring presets from here. Just click on a class element you want to monitor, the monitoring preset edit screen will appaer to make changes.
The reporting toolkit is build on several components:
The first step is to create a HTML template suited for your situation. The next step is to use inline script functions to create graphs and event database info. The next step is to define monitoring groups, this is a group of hosts with monitored interfaces. Such a group can be selected when creating a report, so only the monitoring results of that group are displayed in the graphs.
How do I use templates ?Report HTML templates are used for reporting and the template function. Using inline Perl scripting, standard NINO functions can be embedded in the report. When generating a report the inline script functions are executed, so a database table or monitoring graph is displayed inside the report. This is a list of NINO functions:
Select menu TEMPLATES and click on to edit a template.
Just enter HTML and copy - paste functions in the textarea. Use the Save button to save the template.
To use the template function, click on the template filename link. The template function can process templates on the fly
using the group Default. Becasue no day or month info is entered all data is used.
Select in the main menu the REPORT function. This screen will appear. NINO will generate a HTML report of the monitoring results and event database information. Default a network traffic report is generated using the monitoring data. To customize your reports, please select HTML templates with inline scripting.
To make a report, select a template and define the startdate until enddate the report should be. All monitoring collect or trend data, database eventlog and userlog data from the startdate until the enddate will be used. The monitoring data defined in the selected group are plotted in a graph (using graph width and height input in pixels). Click on Edit to modify groups.
To create or edit monitoring groups, click on Edit and the screen below can be used to enter a device,
monitor preset, interface and a description. All host/preset/interfaces in this group will be used in a report.
To add an interface, click on ,
select a device and interface using the MONITOR function. In the last
screen select the radio button Report to add the interface in the report list.
The Default group is used for automatic reporting and the template function.
Enter another group name to create a new group.
Go to menu ADMIN and click on FILEMGR to manage NINO files. The file manager enables you to view, download, upload and delete files. This can be used to view and manage report files, view or delete raw monitoring data, upload your own alert sounds or upload images to create new device types.
How do I configure SNMP on cisco IOS ?A cisco router or switch must be configured to enable SNMP. Cisco IOS commands can be used in the example below.
To start a session, login and go to enable mode. Configure SNMP: login ena conf t snmp-server community my_write_string RW snmp-server community my_read_string RO snmp-server contact my_contact snmp-server host my_nino_host trap public snmp Configure extended interface description: conf t interface Serial0 Description my_link_to_NewYork_modem808756309 CTRL-Z