After MPLS LDP is enabled, LSPs are automatically established. If no policy for controlling LSP establishment is configured, a large number of LSPs are established, wasting resources.
To reduce the number of LSPs, you can run the lsp-trigger { all | host | ip-prefix ip-prefix-name | none } command in the MPLS view to set a policy for LSP establishment.
If the all parameter is specified, all static and IGP routes trigger LSP establishment (not recommended). If the host parameter is specified, host IP routes with 32-bit addresses (excluding host IP routes with 32-bit interface addresses) trigger LSP establishment. If the ip-prefix parameter is specified, the IP prefix list triggers LSP establishment. If the none parameter is specified, LSP establishment is not triggered.
The lsp-trigger command configures policies only for ingress and egress LSPs on the public network and ingress and egress LSPs on the private network that are established using IGP routes. To configure a policy for triggering the transit LSP establishment, run the propagate mapping command.
If the lsp-trigger command is run on the ingress node, the ingress node uses all 32-bit routes to establish LDP LSPs. If the lsp-trigger command is run on the egress node, the egress node uses local 32-bit routes to establish LDP LSPs.
Currently, no evidence shows that the BT service reduces WLAN air interface efficiency. However, if BT users exist on the WLAN, other users feel that the network quality decreases. This is because air interface bandwidth is occupied by BT users. Therefore, user experience is poor on the WLAN with BT users.
Use a cellular channel distribution to avoid channel overlapping. For example, there are only three non-overlapping channels in the 2.4 GHz frequency band: channels 1, 6, and 11. A proper channel distribution can greatly reduce co-channel interference on a WLAN network. Follow these principles when distributing radio channels:
- Use non-overlapping channels in adjacent areas.
- Adjust APs' transmit power to avoid co-channel interference between areas.
- Use a cellular channel distribution so that channels can be multiplexed without causing overlapping coverage areas.
1. On FusionStorage, choose Resource Pool > Storage Pools.
The Storage Pools page is displayed.
2. Click Capacity Reduction.
The Capacity Reduction page is displayed
Figure 1 Capacity reduction
3. Select the servers to be removed and click Confirm.
After capacity reduction is complete, the Storage Pools page is displayed, which indicates that the FusionStorage storage pool capacity is successfully reduced.
If you have more questions, you can seek help from following ways:
