In today's fast-changing business landscape, computer networks play a vital role. No longer is business confined to the four walls of the enterprise. Large enterprises today need to pursue strategies like offshoring, outsourcing, smart-sourcing, etc. to be competitive. Implementing these strategies globalizes the nature of work, meaning work gets done across geographies and time zones. Welcome to the distributed enterprise!
Today's enterprises are pursuing some of these strategies:
Enterprise bandwidth monitoring is a core requirement today, and quite a strategic one at that.
With network domain changes sweeping enterprises these days, it falls on the network administrator to ensure a high level of WAN availability all the time. As an enterprise becomes a global presence, managing the health and performance of the entire network, including remote and branch offices, becomes a challenge.
Any degradation in network performance anywhere in the network could lead to significant productivity loss and employee frustration. It gets all the more important to be sure that no unwanted traffic, network abuse, or network attack is happening at any point in time.
The main challenges in such a scenario include:
Keeping tabs on the globally spanning network.
The only way to address these problems is by having a powerful enterprise-wide bandwidth monitoring and traffic analysis tool. With knowledge of the traffic patterns in similar departments across offices and geographies and information on what's consuming bandwidth, a network admin or CIO can enforce the appropriate policies to restrict undesired bandwidth usage—like downloading music files or watching YouTube videos during business hours.
This unified, collective view of bandwidth consumption also helps with making accurate strategic decisions on capacity planning (ordering more bandwidth). Also, having access to historic data of traffic usage pattern helps to benchmark current usage levels.
There are various types of bandwidth monitoring solutions to choose from. In general, they can be classified based on the underlying technology (data acquisition technique.
Based on data acquisition
Bandwidth monitoring solutions typically adopt one of these techniques: SNMP query, test access ports (TAPs), Switch Port Analyzer (SPAN) ports, packet sniffing, or analyzing flow exports like NetFlow, sFlow, Cflow, J-Flow, NetStream, and IPFIX.
SNMP uses SNMP queries on SNMP agents running in the network device to get information on the bandwidth usage in the network. SNMP query gives a consolidated or bulk traffic figure. So, this needs to be complemented with in-depth network traffic analysis that answers questions like who's using what bandwidth and when. However, since SNMP uses pull technology, it may end up consuming a considerable amount of your enterprise's bandwidth.
SPAN ports are designated on switches to mirror traffic received on other ports. TAPs are traffic replicators placed in between two routers, firewalls, or enterprise switches that sends a copy of all the network traffic flowing through them. SPAN and TAP ports can be used to forward network traffic to software applications or hardware probes for traffic analysis to obtain network traffic information. The downside is the cost involved in procurement, deployment, and management of these types of ports.
A packet sniffer intercepts and collects local traffic by capturing the packets from the network that the sniffer is attached to. A sniffer is used in network troubleshooting, network intrusion detection, and network usage monitoring by displaying actual traffic insights by IP address and protocol. The downside is the heavy load on the monitoring system.
Flow-based technology harnesses the information contained in flow exports like NetFlow, sFlow, Cflow, J-Flow, NetStream, and IPFIX and presents an in depth view of the traffic flow. They offer a scalable and a low cost approach to have deep insight into the network traffic based on layer 3 and layer 4 packet information. With this information, you'll know who's using what bandwidth and when.
Using the data extracted from the flows, you'll know:
This approach provides the information necessary to make capacity planning decisions, to detect any form of network abuse in monitoring QoS, and, to a certain extent, to identify security attacks.
The below table lists the flow type for the following vendors.
Type of flow | Supporting vendor devices |
NetFlow | Cisco, Enterasys, Extreme Networks, Foundry Networks, 3com, Riverbed |
sFlow | Alcatel, Extreme Networks, Foundry Networks, Hitachi, NEC, Alaxala Networks, Allied Telesis, Hewlett Packard, Comtec Systems, Force10 Networks |
Cflow and J-Flow | Juniper |
NetStream | Huawei and H3C |
IPFIX | Nortel |
Table 1: Various flows supported by vendors: Learn more
Let's look at an example of a software solution that is based on harnessing the data contained in flows to monitor an enterprise's network bandwidth.
When a global enterprise decides to use a flow-based software solution for monitoring its distributed global enterprise, the setup looks like the figure below. The software has to be deployed in each of the remote locations and the data gathered from the location is visible to the network admin at that level or location only.
The report on the bandwidth usage in each of the offices is visible only to the network administrator at that office. Here the data is in silos. For a consolidated overall view, the data available with each network admin has to be collated by the chief network administrator or CIO.
Drawback of this solution:
A distributed monitoring solution can fix the drawback in the above model. By collating data from all the distributed locations and presenting it in a unified view, it offers greater control to the chief network administrator or CIO.
Case in point: The NetFlow Analyzer Enterprise edition
Figure 3: Flow-based monitoring with distributed collection
The NetFlow Analyzer Enterprise edition is a flow-based scalable software solution from ManageEngine that's ideal for large corporations with tens of thousands of interfaces. It uses distributed collectors (shown in the diagram above), which are installed in remote offices. The remote collectors collect the flow information from all the routers in the location, process and compress the data, and send it to the central server through a secure HTTPS link. This way, the resources that are consumed are just a fraction of what would be consumed by other traffic monitoring techniques.
The central server receives the compressed data exported by all the collectors and further analyzes it for reporting. The central server is ideally located at the company's main headquarters. A chief network administrator or CIO can then access the reports generated by the central server through a web client and get a unified view of the entire network.
The NetFlow Analyzer Enterprise edition:
Take in to consideration the below key points before choosing your traffic analysis and bandwidth monitoring solution to ensure that your investment delivers the expected value.
9 key points for the CIO or network manager to consider in choosing the right solution
Seek extension of your trial license if you're still not convinced it's the right solution. A company that does not oblige to extending your license or has cumbersome procedures to do so may not be the best bet going forward.
See how active and vibrant the forums are. Forums can show how popular the product is and responsive the product teams are.
For more details on ManageEngine NetFlow Analyzer visit http://www.netflowanalyzer.com. For technical questions, contact support@netflowanalyzer.com