Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:dpi:bras_bng:cli:bras_l2_vlan_ctl:start [2023/10/18 09:18] – elena.krasnobryzh | en:dpi:bras_bng:cli:bras_l2_vlan_ctl:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== fdpi_ctrl commands ====== | ||
- | {{indexmenu_n> | ||
- | |||
- | The FastDPI BRAS stores in its internal UDR database additional subscriber IP address properties: | ||
- | * MAC address | ||
- | * VLAN tags | ||
- | |||
- | In addition, there is one more feature in the fastDPI BRAS that is not stored in UDR, but presents only in memory as a state of the DHCP session (see [[en: | ||
- | |||
- | When the BRAS operates normally it retrieves the values of these properties from the DHCP traffic and stores it. But a situation could arise where the values of these properties may be misleading, for example, when the fastDPI is rebooted, when a new subscriber is added, or when the network segment topology is changed (when the VLAN tags are changed), etc. | ||
- | In all these cases, you may need to manually modify the UDR database using the fdpi_ctrl utility. | ||
- | |||
- | The command to set the IP address properties: | ||
- | <code bash> | ||
- | fdpi_ctrl load --ip_prop --ip 10.20.30.40 --mac a0: | ||
- | </ | ||
- | |||
- | This command sets the following properties for the IP address 10.20.30.40: | ||
- | * '' | ||
- | * '' | ||
- | * '' | ||
- | * -1 – status is unknown | ||
- | * 0 – session is active | ||
- | * 1 – session is terminated | ||
- | |||
- | Here the '' | ||
- | You can set either all the properties at once or only those you want to modify, for example, changing the MAC address bound to the the IP address looks like this: | ||
- | < | ||
- | fdpi_ctrl load --ip_prop --ip 10.20.30.40 --mac a0: | ||
- | </ | ||
- | |||
- | The command to list the IP address properties: | ||
- | < | ||
- | fdpi_ctrl list –-ip_prop –-ip 10.20.30.40 | ||
- | </ | ||
- | |||
- | To delete a property (the IP address is not completely deleted, but only its specified properties): | ||
- | < | ||
- | # To delete MAC address | ||
- | fdpi_ctrl del --ip_prop --ip 10.20.30.40 --mac | ||
- | |||
- | # To delete VLAN and MAC addresses | ||
- | fdpi_ctrl del --ip_prop --ip 10.20.30.40 --mac --vlan | ||
- | |||
- | # To delete all properties | ||
- | fdpi_ctrl clear --ip_prop --ip 10.20.30.40 | ||
- | </ | ||
- | |||
- | To specify the gateway: | ||
- | < | ||
- | # The 10.45.89.1 address will be treated by the Stingray Service Gateway as a client gateway. | ||
- | fdpi_ctrl load --ip_prop --ip=10.45.89.1 --session_status=gateway | ||
- | </ | ||
- | |||
- | If the IP address type is gateway ('' | ||
- | <code bash> | ||
- | fdpi_ctrl list --ip_prop --ip=10.45.89.1 | ||
- | ================================ | ||
- | IP=10.45.89.1 | ||
- | subnet-mask=n/ | ||
- | MAC=n/a | ||
- | VLAN=n/a | ||
- | type=Gateway | ||
- | Gateway-status=undef | ||
- | last-activity=2018/ | ||
- | iface_idx=0 | ||
- | --------------------------------- | ||
- | Result processing ip=10.45.89.1 : | ||
- | ------------------ | ||
- | 1/0/0 | ||
- | </ | ||
- | |||
- | The Stingray Service Gateway starting from version 7.5 supports commands of multiple parameters changing: | ||
- | <code bash> | ||
- | # To replace VLANs for all the IP addresses from the 10.20.30.0/ | ||
- | fdpi_ctrl load --ip_prop --cidr 10.20.30.0/ | ||
- | |||
- | # To replace VLANs for all the IP addresses from the 192.168.251.5...192.168.251.17 range | ||
- | fdpi_ctrl load --ip_prop --ip_range 192.168.251.5-192.168.251.17 --vlan 709 | ||
- | |||
- | # To delete VLAN of all IP-addresses from the subnet 10.20.31.0/ | ||
- | fdpi_ctrl del --ip_prop --cidr 10.20.31.0/ | ||
- | | ||
- | # To delete from the UDR database all the IP addresses belonging the 10.20.32.0/ | ||
- | fdpi_ctrl clear --ip_prop --cidr 10.20.32.0/ | ||
- | </ | ||
- | Note: multiple MAC address substitution is not possible, because MAC address is unique for each IP. | ||