cookie=0x0, duration=204.729s, table=0, n_packets=0, n_bytes=0, priority=500 actions=netflow
Switch flow count: 1
Device# show openflow switch 100 controllers
Fri Jan 25 14:29:28.660 UTC
Logical Openflow Switch [100]:
Controller [tcp:10.0.1.2:6633]
role : Other
connected : Yes
state : ACTIVE
sec_since_connect : 487
Usecase for Layer2
The Scenario: Enterprise Data Center needs to perform data backup to multiple other backup sites based on
the Traffic flow. The Main DC is in Vlan 100 and Backup sites are at VLAN 1000,1001,1002. These Sites
are interconnected through L2VPN.
The Solution: Openflow, we can match any Layer 2 header field (in this example we have taken priority bits)
and steer the traffic to go on any L2 interconnect and also rewrite the VLANs appropriately.
Usecase for Layer3
The Scenario: Three different flows from 3 different sites connected to PE1 are trying to send 350 mbps of
traffic each to PE2. The bandwidth of the shortest link, Path-2 (between PE1 and PE2) is only 1 Gigabit.
Hence Path-2 gets congested as soon as the third site begins to send traffic.
The Solution: Openflow controller can be used to install rules on PE1:
•
Match on Flow 1 (destined to Video server) and redirect traffic to Path-2
•
Match on Flow 2 (destined to Web server) and redirect traffic to Path-1
•
Match on Flow 3 (destined to File transfer server) and redirect traffic to Path-3
The Inference: Effectively utilizing the network bandwidth by redirecting destination specific traffic using
OpenFlow rules.
Cisco ASR 9000 Series Aggregation Services Router System Management Configuration Guide, Release 5.1.x
299
Implementing Open Flow Agent
Usecase for Layer2