opmanager training
TRANSCRIPT
OpManager Training
Course Objectives
Use OpManager for effective network monitoring. At the end of this course, you will be able to
– Discover network and its resources– Monitor it’s health periodically– Identify fault early and act on it– Use periodic reports to check determine the trend
The Course Agenda
About OpManager Network Management Plan Installing Discovery and Mapping Monitoring Alerting Reporting
The Course Agenda
User Management Troubleshooting Tools Maintenance Upgrade Process Integration with ME Applications Support Process
About OpManager
An integrated network monitoring solution providing out-of-the-box support for Network Monitoring, Server management, and Application management functions
Manages devices from multiple vendorsWindows and Linux installablesPerforms Fault and Performance Monitoring Collects network data for reporting
Network Management Plan
To start with, it is a good idea to have a plan in place to manage your network using OpManager.
A plan saves time in setting up and configuring network monitoring.
Forehand information on what is to be monitored and how, helps in getting OpManager to monitor your network effectively.
Network Management Plan (Contd.)
Take stock of Inventory by Device TypeResources to be monitoredList of free ports for OpManager to useProtocol to be used – SNMP/WMI/Telnet/SSH
Network Management Plan (Contd.)
Who should be notified?Security Aspects
– Ports to be opened in Firewalls
– Different Community Strings
– Identify Hosts for accepting SNMP packets
– Windows Security Settings
Impact of OpManager on your Network (0.1 kbps traffic for 10 devices)
Installing and Setup
Installation
Before you start
Operating System can be– Windows 2000 / 2003 / XP / Vista / 2008
– Linux – Redhat 7.2 and above, Debian
Check the minimum system requirements– Processor 1.7GHz
– 40 GB free disk space (in installation dir)
– RAM - 1 GB
Installation OptionsDecide on the OSChoose the OS-specific Free or Professional
Edition
– Windows version supports Windows Event Log monitoring, Windows Service monitoring, Exchange monitoring, and Active Directory Monitoring.
– Configure Web Server Port (default is 80) during installation
– Utility to change the Web Server Port even later
Discovery &Mapping
Discovery
Module Objectives
Get OpManager to
Discover network and its devices.
Discover services in the devices
Categorize the devices
Startup Options
Automatically starts as Service in Windows– You can also start and stop from Program Files
You can start as a nohup process in Linux
Before You Start
Configure Credentials– Configure the SNMP credentials to be used during
discovery– Configure the CLI (telnet/ssh) and WMI credentials for
authenticating to Windows/Linux/Solaris devices during monitoring and data collection
Add Services to be monitoredAdd device templates for device types for discovery
Discovery
Configure auto-discovery of networksAdd more networks for discoveryAdd individual devices for discoveryConfigure Rediscovery of nodes and networksEnsure all devices in the plan are in!
Discovery Walk-through
Configure SNMP Credentials for Discovery
Discovery Walk-through
Select the TCP Services to be scanned for Monitoring during initial discovery
Discovery Walk-through
Discover a range of devices in a network
Discovery Walk-through
Check the devices discovered
Discovery Walk-through
Import Devices for Monitoring
Discovery Walk-through
Add More Networks/Devices for Discover
Maps
Add More Networks/Devices for Discover
Module Objectives
Understand the default mapsGet all the devices categorized and placed in the
right mapsCreate New Infrastructure ViewsLearn to create and use Business views to meet
specific requirementsCreate Custom DashboardsCreate CCTV views
Module Objectives (contd…)
Effective use of Device Templates for handling new device types, making bulk configuration changes
Using Interface TemplatesUsing Process Templates
Before You Start
Import the non-SNMP devices from Desktop category to the relevant categories
Change/move device categoryApply Device Template
Infrastructure Views
Understand the default Maps. The categories are:
Check if the discovered devices are properly categorized
Desktops
URL
UPS
Wireless
Domain Controller
Servers
Routers
Firewalls
Switches
Printers
Business Views
Create Business View.
Select MapsAdd Business Views to create a view.
Business Views (contd…)
Create Views for custom device typesCreate user-based views to restrict accessCreate views for devices geographically apartDraw meaningful links between devicesConfigure status inheritance for links.
A Business View screenshot follows….
Business View
New Infrastructure Views
Create new Infrastructure Views
Select Maps Add Infrastructure View
Custom DashboardsCreate Custom Dashboards and know the device performance, reports, live charts, business views etc. at a glance
CCTV ViewsView critical dashboards at regular intervals in a loop
Device Templates• OpManager comes with over 600 device templates
• The templates carry the initial configurations to classify the devices into the pre-defined categories, and to associate monitors to them.
• The device templates enables you to effect a configuration once and is applied to several devices at a time whenever there is a change
• New Device Types can automatically be placed in the default/custom infrastructure views by defining appropriate templates
Device Templates
View Templates:
Select Admin Device Templates
Device Templates
Modify Templates:
From Admin Device Templates, click on the Template name
Device Templates
Add New Device Templates for New Device Types:
From Admin Device Templates, click on New Template.
Monitoring
Module Objectives
Understand the monitoring options in OpManager to keep a check on network health
Learn to configure various monitors for snmp and non-snmp devices
Learn to create custom monitorsLearn to define thresholds for meaningful alertingAdd-on & Plug-ins
Monitoring
Before You Start
• Confirm if the device template is correctly applied• Identify and list the devices to be monitored using
SNMP /WMI /Telnet /SSH• Identify the resources to be monitored• For non-SNMP Windows devices, check if WMI
and RPC Services are enabled
Before you start
• For Linux and Solaris, check if Telnet or SSH is enabled for non-snmp monitoring.
• Identify device dependencies• Identify devices running Active Directory,
Exchange 2000/2003, and MSSQL and ensure WMI is enabled
Default Reports
CPU, Disk,Memory Utilization graphs are associated for SNMP devices
Default Reports
Detailed Device Availability Report
Default Reports
Device Response-time graphs
Default Reports
Percentage Packet-loss per device
Default Reports
Interface traffic, utilization, discards and error reports
Default Reports
Live Reports for CPU, Memory, Disk Utilization & Traffic on Interfaces
Default Reports
Load graphs for UPS
Other Default Monitors
Few Windows Services monitored automaticallyFew TCP Services Monitored by defaultActive processes listing in SNMP devices Installed Software listing in SNMP devices
Configure Monitors
Various types of Monitors include:
– Service Monitors (TCP Ports)
– Windows Service Monitors
– URL Monitors
– Performance Monitors
– Process Monitors
– Syslog Monitors
– Eventlog Monitors
Configure Monitors (contd…)
Add Global Monitors:Edit the Device Templates to configure and associate monitors for devices of the same type
Configure Monitors (contd…)
Device-level Monitors:Configure/edit/add more Monitors
Custom Monitors
Create Custom Monitors for identified resources. Add in the device template and apply template to the required devices.
Add-on Monitors
Monitor the following Services using WMI by providing the WMI credentials on the devices. Screenshots of these monitors follow.– Active Directory
– Exchange 2000 and Exchange 2003
– MSSQL Parameters
VMware server and its individual VM's availability and performance can be monitored using SNMP by providing the correct credentials.
Add-on Monitors (contd...)
Monitor Latency and Availability of WAN links with WAN RTT Monitor
Monitor Jitter, Latency, Packet Loss etc. of VoIP calls with VoIP Monitor
Monitoring Active Directory
Monitoring Exchange 2000/03
Monitoring MSSQL Parameters
Monitoring VmWare ESX– Start, Stop and Suspend virtual machines
– Configure correct SNMP Read/Write Credentials
WAN RTT Monitor
● Monitor the availability of WAN links, Round Trip Time (RTT)/Latency and the traffic
• Works with Cisco router ( IOS version 12.3 or later) with IPSLA agent enabled on it
• Performance is measured by sending simulated traffic (packets of specified size) at a specified frequency
• OpManager collects IPSLA traps for events triggered due to a connection loss or threshold violation for RTT
• Trace the fault to the exact hop using hop graph (as follows)
WAN RTT Monitor (contd...)
Hop graph
Configuring Test Parameters for WAN Monitor● Payload: Specify a value in the range of 0 to 16384.Default is 24.
• Type of Service: Specify in the range of 0 to 255, the default being 30.
• Frequency:Specify the interval in the range of 0 to 604800 msecs. The default interval is 60.
• Operation Timeout: Specify the timeout in the range of 0 to 604800000, the default being 60 msecs.
WAN RTT Monitor (contd...)
Configuring WAN Monitor• Provide the Read/Write community string on the Router.
• Alerts are received based on traps. Run the below command on the Router to configure OpManager as trap destination.
snmp-server host <opmanager server IP> traps <host community string> rtr
e.g
snmp-server host 192.168.18.128 traps private rtr
WAN RTT Monitor (contd...)
VoIP MonitorOpManager monitors the following key performance metrics of the VoIP network to determine its health.•Jitter: variation in delay between arriving packets
•Latency: time taken for the voice packets to reach the destination
•Packet Loss: data lost during transmission
•Mean Opinion Score (MOS): standard for measuring voice codecs and is measured in the scale of 1 to 5 (poor quality to perfect quality)
VoIP Monitor (contd...)Adding a Voip Monitor
Pre-requisites:
• Cisco IOS version 12.4 or later at each end
• Enable Add (/discover) the router in your LAN to OpManager. And make sure the SNMP read and write community are configured properly, for that router.
• Enable SLA responder on the destination device you wish to monitor. Connect to the Router and run the command below.
Router(config)#ip sla responder
(Note: Enter any one of the command to enable IP SLA responder as it varies according to the IOS versions.)
• Repeat the above steps for all the destination routers on which you want to monitor VoIP performance.
VoIP Monitor (contd...)Adding a VoIP Monitor• Go to Home-> VoIP Monitors->Configure VoIP Monitor-> Create
New, and enter a name for the monitor.
• Select the source router from the list of routers discovered in OpManager, and select the relevant interface.
• Specify the destination router either by using the 'Search' option to pick from the discovered routers, or use the 'Add' option to specify the IP address of the destination router and submit the details.
• You will see the summary of the monitor you are about to configure. Now click 'Apply to device' to submit the details to the device. This will take few seconds to configure.
• Refresh the page after few seconds to see the new monitor. The data will be collected every hour, from the time you have configured.
VoIP Monitor (contd...)Defining call settings
The VoIP template comes with default values. If you wish to change it, Mouse over Maps tab => VoIP Monitors => Settings => Call Settings and configure the below parameters. Port can be specified in the range of 16384 - 32766.
Destination Port - VoIP UDP port to which VoIP Monitor sends simulated traffic
Simulated VoIP Codec - The VoIP jitter codec decides the type of traffic that VoIP Monitor simulates over your network.
Operation Frequency - Its the frequency with which QoS metrics are collected by the IP SLA agent on your network to determine performance.
Operation Timeout - Time to wait for the response from the responder / destination device in msecs.
Type of service - The Type of Service octet allows you to set precedence levels for VoIP traffic of the IP SLA operations.
MOS Advantage Factor – It is the measure, on a scale of 0 to 20, of the willingness of your VoIP network users to trade call quality for convenience.
VoIP Monitor (contd...)Defining Threshold Values
• We can define a threshold template so that the VoIP performance parameters can be better suit your company SLA, based on which alerts are triggered.
• It comes with default threshold levels, If you wish to change it, Mouse over Maps tab => VoIP Monitors => Settings => Threshold Template and configure the below parameters.
• MOS Threshold: Configure the MOS threshold by specifying the upper and lower MOS range values in the range of 1 to 5.
• Jitter Threshold: Configure the jitter threshold in msecs with upper and lower threshold limits. The range is from 0 to 6000 msecs.
• Latency Threshold: Specify the delay allowed in msecs again in the range of 0 to 6000.
• Packet Loss: Specify the number of packets that can be lost in transit.
• Notification Profile: Select the required notification profile(s) in order to notify when the any threshold rule is violated.
Plug-ins● NCM – Network Change and Configuration
Management● NetFlow – Bandwidth analysis
About - NCMWith NCM plug-in● Manage & automate Network Configurations● Maintain a complete versioning for Network config.
Changes & compare between versions● Backup configurations in order to revert in case of
faulty configurations● Audit the configuration errors● Check configurations for corporate compliance
NCM – Import Devices• Import the Device
• Ensure correct credential are configured
NCM – Device Groups• Create Device Groups
• Perform bulk operations
NCM – Features• Backup the configuration of a device
• View the last 5 configuration changes
• Detect config. Changes through syslog
• Audit the operations performed on the device
• Map the port to which the device is connected using Switch Port Mapper
NCM – Upload Configuration• Upload configuration to a device
• View the difference between configuration versions
• Draft configuration
NCM – Device snapshot
NCM – Compliance•Run & Schedule Compliance check•Associate Compliance policies•Generate reports on compliance
NCM – other detailsPorts used● Syslog – 519● Web – 6060● TFTP – 69● SSHD – 22● MySQL - 13306
About - NetFlowWith NetFlow plug-in● Monitor NetFlows exported by Routers● Know time based & application based usage of a
network● Diagnose slow network performance & bandwidth
bottlenecks in just a few clicks● Prioritize business critical applications using CBQoS● Provides usage based billing options● Monitor Site to Site Traffic
NetFlow – Dashboard● Know the Top Devices/Interfaces/IP Groups by
Speed & Utilization
NetFlow – Real-time Traffic● View real-time traffic graphs for IN/OUT traffic● View graphs for required periods
NetFlow – Application Traffic
NetFlow – Top Hosts● View the Top Hosts contributing for Traffic
(similarly for Top Destinations)
NetFlow – Other Features● Configure QoS & view traffic by DSCP IN & TOS
OUT● View traffic graph by top Conversations● Configure NBAR to improve network bandwidth● With NBAR view real-time application traffic
NetFlow – other detailsPorts used● Web – 8080● NetFlow listener port - 9996● MySQL - 13306
Configure Device Dependencies
You can configure device dependencies to control status polling and prevent unnecessary status checks.
Example: If a switch is down, the devices connected to it would be status polled and will be reported as down. If dependency on the switch is configured in these devices, status polling will be stopped till the switch is up.
Configure Device Dependencies
Understand Thresholds
Thresholds are applied on network resources to calculate their performance
Can be applied based on the response time, connection time, transfer rate, resource utilization, failure counts etc.
On threshold violation, a corresponding severity status is assigned to the device and an event for that severity is generated
Rearm value is used to prevent assigning of same status to a resource every time it is tested
Configure Thresholds
Select ‘Enable Threshold’ option when adding/editing a monitor to apply threshold:
Configure Monitors (contd…)
Configure Windows event log monitoring:
• Associate default Event Log Rules
• Create New Rules
Configure Monitors (contd…)
Add Windows Services to be monitored Add other Services to be monitored
Configure Monitors (contd…)
Configuring Process Monitors: Create Process Monitor Templates Associate to the Devices
Configure Monitors (contd…)
Monitor Syslog packets:● Monitors the syslog packets such as kernel messages, system
daemons, etc. via default syslog port 514 (also customize ports)● Helps identifying unauthorized access● Know the syslog flow rate● Add new syslog Rules
Configure Monitors (contd…)
Add URL monitors for web site monitoring
Alerting
Alerting
Module Objectives
• Understand Alarms
• Learn to work with SNMP Traps• Learn to notify network fault using OpManager• Learn to log a Trouble Ticket • Know how to escalate a fault• Suppress Alarms
Before You Begin
Identify who should be notifiedHow you would like to notify? Email, SMS etc
– Note: Besides the default email-based SMS Notifications, Modem-based SMS notifications is also available as an add-on
For which alarms would you like to log a trouble ticket with ServiceDesk Plus
Would you like to run a program when there is an alarm
Understanding Alarms
Events are ‘occurances’ in a networkEvents are correlated as alarms representing a
failure/faultAlarm is generated when there is a failure ‘Event’
Understanding Alarms
A new alarm for the same resource is generated only when there is a change in the event status. That is, if the subsequent event for a resource is same as the previous status, there will not be an alarm. If the subsequent event is of a different status, a corresponding alarm is generated.
Downstream correlation is done if you have configured device dependencies
Understanding Alarms (contd…)
Alarm Types– Status-poll Alarms (device, service, interface, port
down alarms)– Threshold-based Alarms– Alarms from SNMP Traps– Windows Event Logs
Work with Alarms– Acknowledge, Suppress, Clear, Delete & Add Notes
Work with SNMP Traps
• Check ‘Unsolicited’ Traps and add Processors
• Load Traps from MIBS
• Add Custom Trap Processors
Notify Failure/Fault
• Configure and associate Notification Profiles– Email, SMS, System Command, Run a Program & Web
Alarm
Log a Trouble Ticket
• Configure Mail Server Settings
• Configure ServiceDesk Plus Server Settings• Log a trouble-ticket with ServiceDesk Plus
Escalation Alarms
Configure Alarm Escalation Rules to draw attention to an unattended fault
Alarm Suppression
• Suppress the Alarms of the required devices for a specific time interval
• Useful to prevent false alarms during known downtimes
Reporting
Module Objectives
Learn to use OpManager to get reports on health and performance of your network and its resources.
Understanding Reports
Availability DashboardsSeparate WAN Availability DashboardsSeparate Dashboard Reports for ServersCategory-wise ReportsTop N ReportsReport Presets
Understanding Reports
Peak-time ReportsBusiness View-specific reportsCustom ReportsCustom Monitor GraphsExport to PDF / XLS / HTML formatsTime Based Availability ReportsGroup Frequently accessed Reports
Network Availability Dashboards
Server Availability Dashboards
At-a-glance Report
Top N Reports
Time Based Availability Reports
Custom Reports• Create New Reports
• Copy existing report template to create new reports
User Management
Before You Begin
Only applicable for customers with multi-user licenses
Register the license Identify Users Scope
User Management
Create Users and define Scope
– Permission for full control, or read-only access
– Access to all devices or only business views Change User Password User Preferences
Rebranding
RebrandingChange OpManager Logo in Reports & Web ClientChange the Company Name & Product NameChange the Copyright info
Troubleshooting Tools
Troubleshooting Tools
Ping and Trace Route options– Check if device is reachable
MIB Browser– Check if the device responds to SNMP requests
Switch Port Mapper– Check the connectivity between devices and the
Switch ports
Troubleshooting Tools
Open Telnet & RDP sessions– Analyze the machine remotely
Maintenance
Maintenance
Schedule ReportsSchedule Device ‘Downtime’Manage/Unmanage devicesDatabase Maintenance
– Separate provisions to maintain fault and performance data
Utilities for quicker data backup and restoration
Upgrade Process
Upgrade Procedure
UpdateManager tool for smooth upgrade to latest releases.
Automatic download of upgrade packs by the Probes from the Central Server.
Upgrade Types– Service Packs– Upgrade Packs– HotFixes
Integrating with otherManageEngine Applications
Integration with Other ManageEngine Products
Ability to integrate with following ManageEngine Suite of Products:
– ServiceDesk Plus : For trouble-ticketing
– Netflow Analyzer : For detailed traffic reports
– Device Expert : For Managing Configuration
– Firewall Analyzer: For enhanced Security
Support Process
Support Process
Support Information File Tool for reduced iterations
Support Mediums– Email : [email protected]
– Forum: http://forums.opmanager.com
– Live Chat
OpManager Lounge- Contribute to enhancing OpManager
Questions & Answers
Thank You