Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:dpi:dpi_options:brass:opt_bras:bras_description:start [2020/02/05 17:38] – ↷ Page moved from en:dpi:dpi_options:base_functionality:brass:opt_bras:bras_description:start to en:dpi:dpi_options:brass:opt_bras:bras_description:start lexx26 | en:dpi:dpi_options:brass:opt_bras:bras_description:start [2020/03/18 14:59] (current) – removed lexx26 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 1 L3-connected BRAS description ====== | ||
| - | {{indexmenu_n> | ||
| - | ==== Components ==== | ||
| - | L3-connected BRAS consists of two components listed below: | ||
| - | - [[en: | ||
| - | - [[en: | ||
| - | == General description == | ||
| - | L3-Connected BRAS is designed to work in distributed L3 IP networks when subscribers are connected through the intermediate routers. This design is very common, because it allows to build a distributed network with high capabilities in redundancy and in scaling up the number of nodes. | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | The original subscriber MAC addresses are out of the BRAS scope. IP addresses are assigned to Subscribers using other devices, such as DHCP Relay switches, VPN hubs or when the Subscriber manually sets its static IP configuration. | ||
| - | |||
| - | ===== Differences and advantages as compared with traditional solutions ===== | ||
| - | There is always necessary to create logical interfaces and configure VLAN and IP settings in traditional BRAS solutions. | ||
| - | |||
| - | By contrast there is no need for such configurations when you are using the VAS Experts DPI L3-connected BRAS. Our BRAS always handles traffic dynamically. Its source of information comes from Subscriber' | ||
| - | Once the L3-connected BRAS gets traffic going from the Subscriber, it requests to the RADIUS server and expects to receive from it parameters specifying what services are available to the Subscriber. Then BRAS caches it upon receipt. | ||
| - | |||
| - | < | ||
| - | DPI-based L3-connected BRAS being utilized in a distributed network has many advantages and features over traditional solutions: | ||
| - | |||
| - | * Traffic monitoring and traffic prioritization according to applications and autonomous systems within the accessible band of each of the uplinks | ||
| - | * Limiting of the band occupied by torrent client traffic when a lack of common band arises (when torrent client tends to hog all the bandwidth) | ||
| - | * Prioritization of traffic according applications and autonomous systems as specified in the subscriber’s tariff plan (it is relevant for corporate clients, when many corporate users are working under one tariff plan and there is a need to allocate band to avoid their interference with each other) | ||
| - | * Supporting of Subscribers with an arbitrary set of IP addresses, including dynamically assigned addresses. | ||
| - | * Redirection of Subscribers to the Captive Portal in case of bills non-payment, | ||
| - | * Capability to get full NetFlow both for the entire bandwith or only for subscribers having tarif plans | ||
| - | * Support for the regulatory and law enforcement agencies requirements, | ||
| - | * Interaction with SORM (literally: ' | ||
| - | </ | ||