Cisco SGE2000 Configuration Guide - Page 30

Asymmetric Routing Topology, Asymmetric Routing and Other Service Control Capabilities

Page 30 highlights

Information About Topology Considerations Chapter 3 Information About Topology Asymmetric Routing Topology In some Service Control deployments, asymmetrical routing occurs between potential service control insertion points. Asymmetrical routing can cause a situation in which the two directions of a bi-directional flow pass through different SCE platforms, resulting in each SCE platform seeing only one direction of the flow (either the inbound traffic or the outbound traffic). This problem is typically solved by connecting the two SCE platforms in cascade mode (or through an MGSCP cluster), thereby making sure that both directions of a flow run through the same SCE platform. However, this is sometimes not feasible, due to the fact that the SCE platforms sharing the split flow are geographically remote (especially common upon peering insertion). In this type of scenario, the asymmetric routing solution enables the SCE platform to handle such traffic, allowing SCA BB to classify traffic based on a single direction and to apply basic reporting and global control features to uni-directional traffic. Asymmetric Routing and Other Service Control Capabilities Asymmetric routing can be combined with most other Service Control capabilities, however there are some exceptions. Service Control capabilities that cannot be used in an asymmetric routing topology include the following: • Subscriber redirect • Subscriber notification • Any kind of subscriber integration, including MPLS VPN. (Use subscriber-less mode or anonymous subscriber mode instead) • Classical open flow mode , including the following: - Flow-open-mode classical explicitly enabled (ROOT level configuration) - VAS traffic forwarding mode enabled - Analysis layer transport mode enabled (ROOT level configuration) - 'no TCP bypass-establishment' mode enabled (ROOT level configuration) - A traffic rule is configured for certain flows to use the classical open flow mode (ROOT level configuration) Information About Physical Topologies Following are descriptions of a number of physical topologies that the SCE 2000 supports. • Information About Inline SCE 2000 Topologies • Single Link: Receive-only Topology • Dual Link: Receive-Only Topology Information About Inline SCE 2000 Topologies A single SCE 2000 supports both single GBE link and dual GBE link topologies. • Single Link: Inline Topology • Dual link: Inline Installation Cisco SCE 2000 4xGBE Installation and Configuration Guide 3-4 OL-7824-06

  • 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

3-4
Cisco SCE 2000 4xGBE Installation and Configuration Guide
OL-7824-06
Chapter 3
Information About Topology
Information About Topology Considerations
Asymmetric Routing Topology
In some Service Control deployments, asymmetrical routing occurs between potential service control
insertion points. Asymmetrical routing can cause a situation in which the two directions of a
bi-directional flow pass through different SCE platforms, resulting in each SCE platform seeing only one
direction of the flow (either the inbound traffic or the outbound traffic).
This problem is typically solved by connecting the two SCE platforms in cascade mode (or through an
MGSCP cluster), thereby making sure that both directions of a flow run through the same SCE platform.
However, this is sometimes not feasible, due to the fact that the SCE platforms sharing the split flow are
geographically remote (especially common upon peering insertion). In this type of scenario, the
asymmetric routing solution enables the SCE platform to handle such traffic, allowing SCA BB to
classify traffic based on a single direction and to apply basic reporting and global control features to
uni-directional traffic.
Asymmetric Routing and Other Service Control Capabilities
Asymmetric routing can be combined with most other Service Control capabilities, however there are
some exceptions.
Service Control capabilities that cannot be used in an asymmetric routing topology include the
following:
Subscriber redirect
Subscriber notification
Any kind of subscriber integration, including MPLS VPN. (Use subscriber-less mode or anonymous
subscriber mode instead)
Classical open flow mode , including the following:
Flow-open-mode classical explicitly enabled (ROOT level configuration)
VAS traffic forwarding mode enabled
Analysis layer transport mode enabled (ROOT level configuration)
‘no TCP bypass-establishment’ mode enabled (ROOT level configuration)
A traffic rule is configured for certain flows to use the classical open flow mode (ROOT level
configuration)
Information About Physical Topologies
Following are descriptions of a number of physical topologies that the
SCE 2000
supports.
Information About Inline SCE 2000 Topologies
Single Link: Receive-only Topology
Dual Link: Receive-Only Topology
Information About Inline SCE 2000 Topologies
A single
SCE 2000
supports both single GBE link and dual GBE link topologies.
Single Link: Inline Topology
Dual link: Inline Installation