As one of the most important part of networking, WAN Monitoring plays a virtual role. It is known that WAN Monitoring provides:
Performance tuning which can improve service with proactively id, reduce bottlenecks, tune and optimize systems, improves QOS, optimize investments with id under/over utilized resources, and balance workloads.
Trouble shooting which can get out of crisis mode with id probs, start diagnosis/fixing before end user notices, increase reliability/availability, and allow users to accomplish work more effectively and maximize productivity.
Planning which can help you understand performance trends for planning
Expectations which can set expectations for the Distributed System (from network thru applications) and see how well they are met.
Thus, it’s high time for us to share some FAQs and examples for WAN Monitoring. Now here are the FAQs:
1. Does the network need the WAN RTT Monitor?
Cisco IP SLA based WAN Round-Trip-Time monitoring best fits your network if you
Face frequent performance issue over your MPLS-based network
Want to monitor WAN link availability and performance across remote sites
Are experiencing WAN circuit related issues
Want to get hop-wise visibility on your WAN circuits
Want to monitor the Quality-of-Service (QoS) across WAN links provided by your ISP
If your network has edge devices from Cisco with IOS, Cisco IP SLA is a cost effective monitoring solution to identify the efficiency of your WAN circuits.
2. What IOS versions or Cisco Devices support Cisco IP SLA?
3. How much Cisco IP SLA loads my device?
Cisco Press book was used as reference for this. The following numbers bellow presents examples on different load conditions. The tests were performed on a Cisco 7200VXR/NPE-225 with IOS 12.2(8)T5.
The WAN RTT monitoring feature is enabled by default during the first 30 days of trial period. To continue using the WAN RTT monitoring feature, you will need to get a registered license key.
5. What are the steps to get WAN links monitored using OpManager?
Step 1: Add (/ discover) the router in your LAN making sure the SNMP read and write communities are configured properly for the router.
Step 2: Configure the Cisco router to send traps to OpManager. Alerts are shown based on the traps received in OpManager. To configure OpManager server as the SNMP server receiving traps for the routers, telnet the router and type the following command:
snmp-server host traps 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 192.168.18.128 traps private rtr
Step 3: Creating the WAN Monitor
Go to the Maps tab (on from the list of Infrastructure views), click on > WAN Monitors > Settings
Select the source router from the list of routers discovered in OpManager and then select the relevant interface of the source router.
Specify the destination IP Address either by using the ‘Search’ option to pick from the discovered routers, or directly enter the IP Address and click ‘Add’ to 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.
The original material is from: www.manageengine.com/network-monitoring/wan-network-management.html