Dell PowerConnect 6248 Configuration Guide - Page 68

sFlow Agents, To perform Packet Flow Sampling

Get Dell PowerConnect 6248 PDF manuals and user guides View all Dell PowerConnect 6248 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 68 highlights

The advantages of using sFlow are: • It is possible to monitor all ports of the switch continuously, with no impact on the distributed switching performance. • Minimal memory/CPU is required. Samples are not aggregated into a flow-table on the switch; they are forwarded immediately over the network to the sFlow collector. • System is tolerant to packet loss in the network (statistical model means loss is equivalent to slight change in sampling rate). • sFlow collector can receive data from multiple switches, providing a real-time synchronized view of the whole network. • The Collector can analyze traffic patterns based on protocols found in the headers (e.g., TCP/IP, IPX, Ethernet, AppleTalk...). This alleviates the need for a layer 2 switch to decode and understand all protocols. sFlow Agents sFlow Agents use two forms of sampling: • Statistical packet-based sampling of switched or routed Packet Flows • Time-based sampling of counters Packet Flow Sampling and Counter Sampling are performed by sFlow Instances associated with individual Data Sources within an sFlow Agent. Both types of samples are combined in sFlow datagrams. Packet Flow Sampling creates a steady, but random, stream of sFlow datagrams that are sent to the sFlow Collector. Counter samples may be taken opportunistically to fill these datagrams. To perform Packet Flow Sampling, an sFlow Sampler Instance is configured with a Sampling Rate. Packet Flow sampling results in the generation of Packet Flow Records. To perform Counter Sampling, an sFlow Poller Instance is configured with a Polling Interval. Counter Sampling results in the generation of Counter Records. sFlow Agents collect Counter Records and Packet Flow Records and send them as sFlow datagrams to sFlow Collectors. Packet Flow Sampling Packet Flow Sampling, carried out by each sFlow instance, ensures that any packet observed at a Data Source has an equal chance of being sampled, irrespective of the Packet Flow(s) to which it belongs. Packet Flow Sampling is accomplished as follows: 1. A packet arrives on an interface. 2. The Network Device makes a filtering decision to determine whether the packet should be dropped. 3. If the packet is not filtered (dropped) a destination interface is assigned by the switching/routing function. 4. A decision is made on whether or not to sample the packet. 68 Switching Configuration

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
68
Switching Configuration
The advantages of using sFlow are:
•
It is possible to monitor all ports of the switch continuously, with no impact on the distributed
switching performance.
•
Minimal memory/CPU is required. Samples are not aggregated into a flow-table on the switch; they are
forwarded immediately over the network to the sFlow collector.
•
System is tolerant to packet loss in the network (statistical model means loss is equivalent to slight
change in sampling rate).
•
sFlow collector can receive data from multiple switches, providing a real-time synchronized view of the
whole network.
•
The Collector can analyze traffic patterns based on protocols found in the headers (e.g., TCP/IP, IPX,
Ethernet, AppleTalk…). This alleviates the need for a layer 2 switch to decode and understand all
protocols.
sFlow Agents
sFlow Agents use two forms of sampling:
•
Statistical packet-based sampling of switched or routed Packet Flows
•
Time-based sampling of counters
Packet Flow Sampling and Counter Sampling are performed by sFlow Instances associated with
individual Data Sources within an sFlow Agent. Both types of samples are combined in sFlow datagrams.
Packet Flow Sampling creates a steady, but random, stream of sFlow datagrams that are sent to the sFlow
Collector. Counter samples may be taken opportunistically to fill these datagrams.
To perform Packet Flow Sampling, an sFlow Sampler Instance is configured with a Sampling Rate. Packet
Flow sampling results in the generation of Packet Flow Records. To perform Counter Sampling, an sFlow
Poller Instance is configured with a Polling Interval. Counter Sampling results in the generation of
Counter Records. sFlow Agents collect Counter Records and Packet Flow Records and send them as
sFlow datagrams to sFlow Collectors.
Packet Flow Sampling
Packet Flow Sampling, carried out by each sFlow instance, ensures that any packet observed at a Data
Source has an equal chance of being sampled, irrespective of the Packet Flow(s) to which it belongs.
Packet Flow Sampling is accomplished as follows:
1.
A packet arrives on an interface.
2.
The Network Device makes a filtering decision to determine whether the packet should be dropped.
3.
If the packet is not filtered (dropped) a destination interface is assigned by the switching/routing
function.
4.
A decision is made on whether or not to sample the packet.