Differences

This shows you the differences between two versions of the page.

--- en:install_point_scat [2015/04/13 14:51] – translator1
+++ en:install_point_scat [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-SKAT connection between BRAS and NAT. You can use additional services using this connection. If you need traffic filtering only: you can connect after NAT/ edge router in the uplink break.\\
-\\
-[[micra_install|Device installation manual]]
-The typical connection diagram if bypass functionality is available:
-{{typicalschema_en.png}}
-The connection diagram without bypass functionality:
-{{schema_no_bypass_en.png}}
-The connection diagram for several SKATs "symmetric hash" to process more than 20GbE:
-{{schema_more_10gbe_en.png}}
-[[http://www.juniper.net/techpubs/en_US/junos13.1/topics/usage-guidelines/interfaces-configuring-symmetrical-load-balancing-lag-on-mx-routers.html|Juniper symmetric hash configuration details ]] \\
-[[http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/SCE_DPI.html#wp150557|CISCO configuration details]]\\
-**Note the modification in the above diagram using VLAN (Dispatch mode):**\\
-The subscriber's traffic comes to the first port of the switch. Then it goes to the second switch port and is received by DPI. Further, the processed by DPI traffic enters the third port of the switch and leaves to Internet via the fourth port.
-To support such operation, one can arrange the connections like this: the first two ports of the switch form the first VLAN and other two ports form the second VLAN. The traffic would be sent to DPI on L2 level.\\
-The diagram above has an item:[[http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/SCE_DPI.html#wp150376|Figure 5 Layer 2 Dispatch Mode]]\\
-One can configure the system in a similar way, but without port-channel: to use one port everywhere.\\
-Note that the manual uses a trunk with VLAN specification. In case you do not use a trunk please set ports into access mode.\\
-The asymmetric traffic processing method based on policy based routing. It is applicable for filtering only and we do not recommend it.
-{{schema_pbr_asym_en.png}}
-The asymmetric diagram with BGP/32 routes announcing. Applications:
-  * redirection of queries to support blocking and notifications;
-  * bonus program;
-  * caching.
-BGP/32 routes are configured by the operator.
-{{ bgp_schema1_en.png}}
-The mirrored traffic based diagram. Applications:
-  * to get real time click stream via ipfix;
-  * redirection of queries to support blocking and notifications;
-  * bonus program;
-  * caching;
-  * SORM pre-filter.
-{{ mirror-schema1_en.png}}
-The diagram with a mirrored traffic via SPAN ports to support SORM pre-filter.
-{{ sorm_span_en.png?700 |}}
-~~DISCUSSION|Please help us to improve our documentation. Let us know if you found an error or something is unclear.~~

Profile

Settings

Differences