- Network Management
- Server Management
- Fault Management
- Network Fault Management
- IT Workflow Automation
- Email Alert
- SMS Alert
- Network Monitoring Tools
- Real Time Graph
- Switch Port Mapper
- Connect From Anywhere
- SNMP Trap Processing
- Syslog Monitoring
- Event Log Monitoring
- Threshold Based Alerting
- Integration with HelpDesk
- Advanced Alert Management
- Customizable Dashboards
- Service Level
- Network Performance Reporting
- Top N Reports
- Business Snapshot Based Reports
- Scheduled Emailing of
- Data Center Management
- Enterprise-class Scalability
- Integrations and Plug-ins
- Do it yourself deployment
- Monitor IT on the move
Monitor Your WAN
OpManager helps you stay ahead in business by ensuring that all your distributed mission critical applications are highly available. OpManager does an edge-to-edge performance monitoring of your WAN and helps in meeting the SLAs.
The WAN monitoring feature in OpManager monitors the availability of all your WAN links, the Round Trip Time (RTT) and the traffic details. Detailed WAN performance dashboard reports are provided and you can quickly navigate the dashboard to see the root cause of poor WAN availability.
- What are the prerequisites for monitoring the WAN using OpManager?
- How does OpManager monitor the WAN performance?
- How to configure WAN monitoring in OpManager?
- An example of troubleshooting a WAN problem
What are the prerequisites for monitoring the WAN using OpManager?
OpManager primarily relies on Cisco's IP-SLA for monitoring the WAN and the prerequisite therefore is, that the device should be a Cisco router and must have IPSLA agent enabled on it. OpManager uses SNMP to query the Cisco routers for the links' performance data. IPSLA familiarity is not a prerequisite. You just need to tell OpManager which links you want to monitor. OpManager provides an intuitive configuration wizard to help you configure all the IPSLA parameters for monitoring the WAN health.
How does OpManager monitor the WAN performance?
OpManager polls the routers periodically and collects and persists the data. The monitored router sends IPSLA traps for events triggered due to a connection loss, threshold violation for RTT and average payload, timeout etc. When any such failure occurs, OpManager switches from a regular Echo to a Path Echo, tracing the fault to the exact hop. This enables you to troubleshoot and get to the root of the problem much quicker, resulting in very less downtime.
Besides this intelligent monitoring of the links across each hop, OpManager also supports bulk configuration of the monitoring parameters for the links to be monitored. You will simply need to configure all the IPSLA parameters once and select all the devices (the target IPs) and apply it.
How to configure WAN monitoring in OpManager?
You can bulk-configure the links from OpManager for monitoring. When adding WAN Monitors, you can select multiple links, i.e., the target IP addresses and add them at one go to create monitors for each of the links. The intuitive SLA dashboards show the link-wise availability and over-all performance of your WAN.
Following are the steps to enable WAN monitoring in OpManager:
1. Configure the Cisco Routers to send traps to OpManager
To configure OpManager machine as the SNMP Server receiving traps for the routers, telnet the router and use the following command:
snmp-server host <opmanager server IP> traps <host community string> rtr
For instance, if the OpManager host IP Address is 192.168.18.128, and the community string is private, the command would be:
snmp-server host <opmanager server IP> traps private rtr
2. Add a WAN Monitor
- Configure the correct SNMP read and write community string in the SNMP Credentials for the device.
- From the Home tab, select Network tab to see the SLA Dashboards for the WAN.
- Click the WAN Monitor link on the right to add the monitors. Following are the fields that you need to configure:
- Name: Configure a name for you WAN Monitor.
- Description: A brief description of the monitor .
- Source: Select the source Router whose links you want to monitor.
- Target IP List: Add the target IP Address of the links. When adding the target IPs, you can bulk-select the target ip addresses and add them in groups. Click the Search button against list-box showing the target IPs. A list of available devices are shown from which you can select the specific target IPs. You can add multiple devices to monitor or alternatively, you can also group them under a 'group' name for later use.
If you know the target IP addresses, click the Quick Add option to add the IPs one by one.
- Select the interface ipaddress of the source device from which you can reach in external devices.
Click the Advanced button in the General Attributes section to configure the following two parameters.
Request Payload: You can configure to send test packets, UDP jitters, of specific size to determine the average RTT.
QoS: You can also enable QoS (Quality of Service) for the Payload by selecting the required QoS level.
Configuring thresholds for various IPSLA parameters enables pro-active monitoring of your WAN.
Rising Threshold: Specify the value in milli-seconds for the rising threshold. If the RTT (Round Trip Time) goes over the specified threshold, you will be alerted.
Falling Threshold: Specify the falling threshold too for you to be notified when the RTT falls below the specified threshold value.
Threshold Alert Options: As mentioned above, OpManager alerts you when there is a threshold violation. The alert conditions can be specified as below:
Select the option 'Immediately' to be notified as soon as a threshold violation occurs. Select 'Every ______ of _______ times' to be notified when a threshold is violated the specified number of times in a specified number of polls. For instance, you can configure to be notified when the threshold fails every 4 times out of 5 polls.
You can also be notified to be alerted when a threshold fails for a consequetive number of times by selecting 'Every __ th time'.
Or, select to be notified by specifying the average number of times a when a threshold violation occurs. For instance, an average of 10 threshold violations can trigger an alarm.
Path Echo Configuration: As advanced configuration criteria, you can also configure the number of network paths and hops for the Payload. So, whenever there is a failure, OpManager switches to Path Echo for the next 3 hours. The paths, and the hop where the failure occurs is clearly indicated. The option of switching to Path Echo only in the event of a failure not only helps in narrowing down the problem, but also proves to be a less costly operation on your network.
- Frequency: Configure the interval at which the link monitoring should be scheduled.
- Timeout: Configure the timeout interval in seconds.
- Start at: Select the start time by selecting the time from the adjacent time window. Or select 'Start now' check-box to commence immediately.
- End at: Select the end time from the time window or select 'Forever' check-box for the monitoring to continue.
The configured profiles are listed. From the list of profiles, select the notification profile to be triggered when a fault occurs. Based on the monitoring configuration and the profile selected, you will be alerted when there is a failure.
An example of troubleshooting a WAN problem
You can drill down the reports to see where the actual failure is. Under the Home tab, click the Network tab to see the Dashboard graphs for the WAN Monitors.
Let us consider an example of a multi-national bank ABN-AMRO with branches across the globe with the data-center at California. Any link failure between the data centers and the branches will hugely impact the business.
The screenshot above shows a router- California902 with the target devices at the regional branches. Let us see how a WAN administrator gets to the root of the problem.
1. The dashboard indicates the status of WAN. It shows a considerable link downtime. Click the bar in the graph indicating the downtime for that hour in the WAN Links Average Availability report. The availability trend for the past few days can also be verified by selecting the period from the top right corner of the dashboard.
2. This shows two least available links, indicating the percentage unavailability.
3. Link availability for the last 24 hours is shown here.Click the link concerned to see when the problem started.
4. Click on the specific hour to see the Hop Graph as shown below. The Hop Graph shows the link health at each Hop. You select the other paths and check the graphs too.
Now the administrator knows where the exact failure has occured and attends to it immediately. Feel free to get in touch with our technical support for any assistance in using this feature.