How to configure static LSPs on S series switches

9

For static LSP configuration on S series switches (except the S1700), see "CLI-based Configuration > Configuration Guide - MPLS > Static LSP Configuration > Configuration Examples > Example for Configuring Static LSPs" in S7700&S9700 V200R010C00 Product Documentation.
Configurations on different models are the same, and configurations on the S7700 and S9700 are used as examples.

Other related questions:
Static ARP configuration on S series switch
On an S series switch, except S1700, run the arp static command in the system view to configure a static ARP entry. When the outbound interface is an Ethernet interface, run the arp static ip-address mac-address interface interface-type interface-number command to configure a static ARP entry. When a VPN instance needs to be specified for the ARP entry, run the arp static ip-address mac-address vpn-instance vpn-instance-name command. To configure a short ARP entry (only contains IP address and MAC address mapping, without VLAN or outbound interface), run the arp static ip-address mac-address command. To configure a static ARP entry in which the IP address is 10.1.1.1, MAC address is 0efc-0505-86e3, VLAN ID is 10, and outbound interface is GE1/0/1, run: [HUAWEI] arp static 10.1.1.1 0efc-0505-86e3 vid 10 interface gigabitethernet 1/0/1 - To configure a static ARP entry in which the IP address is 10.1.1.1, MAC address is 0efc-0505-86e3, and VPN instance is vpn1, run: [HUAWEI] ip vpn-instance vpn1 [HUAWEI-vpn-instance-vpn1] ipv4-family [HUAWEI-vpn-instance-vpn1-af-ipv4] quit [HUAWEI-vpn-instance-vpn1] quit [HUAWEI] arp static 10.1.1.1 0efc-0505-86e3 vpn-instance vpn1

What is the difference between the static LSP bound to the tunnel and the static CR-LSP
Switches of V200R002C00 or later support the static CR-LSP. A static LSP is classified into the common LSP and static LSP bound to the tunnel. A static CR-LSP must be bound to the tunnel. A static CR-LSP requires bandwidth while a common static LSP does not require.

Method to configure static DHCP binding on S series switches
Static DHCP binding allows the switch to allocate fixed IP addresses to user terminals with fixed MAC addresses. Assume that an S series switch excluding the S1700 needs to allocate the fixed IP address of 10.10.10.10 to the client with the MAC address of dcd2-fc96-e4c0. The configuration method is as follows: - Based on the global address pool: [HUAWEI] ip pool 1 //Address segments have been configured in the address pool. [HUAWEI-ip-pool-1] static-bind ip-address 10.10.10.10 mac-address dcd2-fc96-e4c0 - Based on the interface address pool: [HUAWEI] interface vlanif 10 //An IP address has been assigned to the interface. [HUAWEI-Vlanif10] dhcp server static-bind ip-address 10.10.10.10 mac-address dcd2-fc96-e4c0 Note: The configured IP address cannot be the IP address that has been assigned. If the system displays a message indicating that the IP address has been assigned, run the reset ip pool { interface pool-name | name ip-pool-name } { start-ip-address [ end-ip-address ] | all | conflict | expired | used } command in the user view to manually reclaim IP addresses in the address pool.

How to configure floating static routes with S-series switches
When there are multiple routes to a destination, you can configure different routes with different priorities

How to reduce the number of LSPs on S series switches
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.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top