Beruflich Dokumente
Kultur Dokumente
Enterprise Networks
Kunwadee Sripanidkulchai
Chavee Issariyapat
Koonlachat Meesublak
network. Our techniques have low data collection and processing overhead, making it suitable for real-time monitoring
and inference. We validate our approach using data collected
from a small enterprise network. We find that we are able
to capture two types of relationships between the logical and
physical network, those influenced by configuration and those
influenced by usage.
This paper is organized as follows: we begin with an
overview of a VLANs in Section II. In Section III we present
an algorithm that maps VLANs to physical interfaces in the
network. We discuss the resulting mappings in Section IV
and how they relate to VLAN configurations and usage. We
then summarize and discuss the implications of our findings
in Section V.
II. BACKGROUND
I. I NTRODUCTION
The use of Virtual Local Area Networks (VLANs) is
prevalent in enterprise networks. Virtualization provides many
benefits such as simpler IP address management, flexibility to
treat any set of hosts in disparate physical locations as a single
logical unit, and segmentation and isolation of resources.
While virtualization makes it easier for network administrators
to reason about logical groupings of entities, management
and maintenance of VLANs is still a manual and tedious
process [1]. Furthermore, virtualization abstracts away the
underlying relationship between the VLAN and its physical
instantiation which could span many physical components in
the network. These underlying relationships provide a mapping
between the logical and the physical network and are important
primitives needed to create network-wide views of traffic patterns. Given such views, one would be able to perform better
problem determination and system optimization to answer
questions such as are there VLANs that are heavy-hitters
that generate the bulk of the traffic on a physical interface,
which VLAN is the cause of the shift in traffic patterns in
the network, and are those shifts related to security events
or problems inside the network? While the use of VLANs is
wide-spread in the real world, the research community is only
beginning to look at the complexity and the rich set of research
issues caused by virtualization [2].
The goal of this paper is to be able to infer relationships
between VLANs and physical interfaces in the network. We
explore the use of standard SNMP MIB counters widely
available in equipment from all vendors. We create relationship information from these individual counters and piece
together a bigger picture of usage-based relationships in the
Fig. 1.
TABLE I
N UMBER OF VLAN S AND PHYSICAL INTERFACES ON CORE ROUTERS .
Router
Number of VLANs
Number of Physical Interfaces
R1
14
18
R2
39
11
R3
29
7
used in network monitoring tools [9] [10] also include nonuser-level traffic which may not be representative of the user
traffic patterns in which we are interested. Therefore, in this
study we use packet counters as the primary source of data.
However, octet counters are likely to be complementary and
will be considered as part of future work.
Interface counters are collected from all interfaces once a
minute over a period of 16 days in December 2007. This
polling rate generates insignificant overhead on our network
(less than 1 kbps). Although higher frequency polling may
capture more detailed network state, polling too frequently
may be error-prone because counter updates are not on the
fast path and will sometimes lag by a few seconds.
B. VLAN Mapping Algorithm
Next, we describe the analysis methodology we use to
answer our key question: is it possible map VLAN traffic
to physical interfaces with information obtained solely from
SNMP traffic counters?
1) Statistical Correlation: Intuitively, there should be some
relationship between packet counters of pairs of physically
connected interfaces. For example, packets going out of one
interface need to be forwarded in to the other interface.
To measure the extent of a relationship between a pair of
interfaces, we use Pearsons correlation coefficient. Given
sequences X and Y , the correlation coefficient r(X, Y ) is
defined as follows:
E(XY ) E(X)E(Y )
p
r(X, Y ) = p
2
E(X ) E 2 (X) E(Y 2 ) E 2 (Y )
Correlation values range from -1 to 1, and values closer
to 1 indicate strong correlation whereas values closer to 0
means that X and Y are linearly uncorrelated. A sufficient
number of points must be used in order to obtain statistically
meaningful correlation values. However, using too many points
spread over a long period may fail to capture shorter-term
dynamic behavior of network traffic. In this paper, we compute
the correlation coefficient of the number of packets seen on
an interface per minute from SNMP packet counters over a
period of 30 minutes.
To illustrate that the correlation coefficient can be used
to capture relationships, consider Figure 2(a) which depicts
the correlation coefficient between two directly connected
physical interfaces over time. The correlation coefficient is
generally high, but exhibits time-dependent behavior with
higher correlation during the day than at night.
Relationships also exist between two different VLANs on
the same router, depicted in Figure 2(b). Our hypothesis is
that if two VLANs are related in terms of usage, their packet
counts ought to be correlated as indicated by a high correlation coefficient. Such VLAN-VLAN relationships imply that
1
1
0.5
0.5
-0.5
Correlation Coefficient
Correlation Coefficient
Correlation Coefficient
0.5
-0.5
-0.5
-1
12/11
12/12
12/13
12/14
12/15
12/16
12/17
12/18
12/19
12/20
Fig. 2.
-1
12/11
12/12
12/13
12/14
12/15
12/16
12/17
12/18
12/19
12/20
VLAN 395
All VLANs on Trunk
-1
00:00 02:00 04:00 06:00 08:00 10:00 12:00 14:00 16:00 18:00 20:00 22:00 00:00 02:00
Time (December 11, 2007)
Fig. 3.
Communities of Interest.
AND
D ISCUSSION