Оглавление
General description
According to the classic implementation, the search of an ESR to which a command for data tunnel establishment (data tunnel create) should be sent, is conducted up to the node tree beginning with a node where an AP is located. This logic requires AP and ESR to be located at the same branch of ESR object tree, and ESR to be located at the same node with AP or higher. This solution is not suitable for clients that have a part of access points grouped by clients and another part grouped by regions in its domain structure. It is not also suitable for federal clients that have division into clients (AllClients.Federal.BANK) and then into regions (BANK.Centr.Moskva).
The proposed solution gives an opportunity to configure the ESR location parameter "Domain of Station ESR" where a node where a search for an ESR (for data tunnel establishment) should be conducted can be specified. Thus, when moving up the tree from an AP to find an ESR for data tunnel establishment, EMS will be able to use this parameter to move from a federal client node to a region node containing the ESR.
| Предупреждение |
|---|
| It should be understood that a data tunnel can be established only to the ESR used for AP management tunnel. An AP decides what termination addresses should be used to establish 43-option GRE from a DHCP server when receiving a primary address - EMS configuration has no effect! Therefore, the engine to search ESR devices appropriate for data tunnel establishment assumes that ESR devices to which an access point will establish (or has already established) a management tunnel will be found as a result. |
The classic scheme of node tree search for data tunnel establishment
ESR has two options to establish data tunnels for access points:
1) data tunnels configured dynamically (locally) - in this case, all necessary information for data tunnel configuring is contained in ESR configuration, and its interaction with EMS management system is not required (this option is not considered further);
2) data tunnels configured dynamically on RADIUS server commands. In this case, it is necessary to configure interaction with the RADIUS server on ESR and complete the settings in EMS. PCRF server acts as a RADIUS server with which ESR interacts. This way to establish data tunnels will be considered further.
Establishing data tunnels to ESR is made on the PCRF command initiated by EMS and sent in the following cases:
1) initializing a new AP;
2) reinitializing of an AP;
3) moving an AP to another node;
4) changing SSID parameters linked to a domain where an AP is located;
5) removing/creating a SSID link to an AP domain;
6) changing/assigning/removing a domain shaper or SSID of an AP.
In all these cases, EMS should define ESR devices to which a command for data tunnel establishment will be sent. To use ESR for data tunnel establishment, it should be added to EMS node tree with "ESR mode" = "Station" in the tab "Access". It should not be phased out.
...
If several ESR devices appropriate for data tunnel establishment are found, the command will be sent to all of them.
Problems of defining an ESR for data tunnel establishing in a classic ESR search
Look at the scheme in Figure 3.1:
...
In the scheme for AP Alfabank-KRS-Achinks10kv_1_a8:f9:4b:12:12:10 given above, a data tunnel should be established from the node "Krasnoyarsk_Achinsk10kv" to the ESR that is located in the node "MRF_Sibir". If the classic scheme is used, the device will not be detected, and the command for data tunnel establishment will not be sent. To solve this problem, the opportunity to define ESR location in node settings has been added to SoftWLC 1.14 and EMS 3.18. ESR search logic for tunnel establishment has been also added.
The scheme of searching ESR for data tunnel establishment by location configuration in a node
In the scheme of searching ESR for data tunnel establishment by location configuration there is an opportunity to specify a domain to search an ESR in node configuration. The logic is as follows:
...
step 4: Check the node MRF_Sibir for the transition rule: not found; check the node for ESR devices appropriate for data tunnel establishment: ESR is found!
Configuring ESR location in EMS
In the example in the figure 5.1. an AP is located in the node "Alfabank-KRS-Achinsk10kv.Krasnoyarsk.Sibir.ALFA_BANK.Federal.AllClients.root". ESR devices to which it establishes GRE tunnels according to option 43 parameters assigned during getting the primary address, are located in the node "MRF_Sibir.Local.AllClients.root". Therefore, it will not be found by the AP, if the classic ESR search will be done. It is necessary to define a node on which ESR location will be configured, and from which a transition to a node containing ESR will be made.
...
| Предупреждение |
|---|
Attention!!! Reinitialization is required for all access points that are located in the configured node or in lower-level nodes after assigning/changing/deleting ESR location in "Domain of Station ESR"! |
Occupancy monitoring of the node where ESR devices for data tunnel establishment are located
To monitor occupancy of nodes where ESR devices to which access points can establish tunnels, the new tab "Wireless" accessible for any node has been implemented. All ESR devices having access points that establish tunnels on them are displayed there, starting with the selected node and then down the tree.
In the example in Figure 6.1, the root node is selected to see all ESR devices:
...
In the above figure 6.3, the following parameters are shown:
"Node ID" - object index
"Node name" - the node where an ESR device to which an AP should establish tunnels is located
"Node domain" - the domain in which ESR devices to which an AP should establish tunnels are located
"ESR list" - the list of devices that are located in the node. Several ESR devices can be located in a node, because to provide redundancy, two devices are usually used.
ESR location configuration principles
When configuring ESR location, the following principles should be adhered to:
...