Set basic parameters, such as Network Type, Protocol Type, and Signaling Type

Major Parameter Settings

Network Type l Full-mesh: All NEs are fully meshed.

l Hub-spoke: Spoke sites are fully meshed to hub sites.

NOTE

When you set Network Type to Hub-Spoke for a tunnel, NE Role must be set to Hub for at least one NE on the tunnel.

l Ring: NEs are bidirectionally connected in a ring.

Protocol Type MPLS: If all NEs that a tunnel passes through support MPLS, set Protocol Type to MPLS.

NOTE

Protocol Type can be set to MPLS only.

Signaling Type l RSVP TE: You need to specify only the source and sink nodes for an RSVP TE tunnel. The MPLS protocol automatically calculates a route for the tunnel. In addition, you can specify constraint nodes to plan a specific route for the tunnel. You can configure QoS and FRR protection for an RSVP TE tunnel. An RSVP tunnel is more flexible and safer than an LDP tunnel.

l LDP: You need to specify only the source and sink nodes for an LDP tunnel. The LDP protocol automatically calculates a route for the tunnel. LDP tunnels can run on any network that supports MPLS.

l Static CR: A static Constraint-based Routing (CR) tunnel is created with certain constraints. The mechanism for creating and managing those constraints is called CR.

l Static: Every NE that a static tunnel passes through must be manually specified.

NOTE

Routers do not support LDP tunnels.

Backup Type Key tunnels on the network require that backup CR-LSPs be configured for primary CR-LSPs.

l Hot standby: A backup CR-LSP is created immediately after a primary CR-LSP is set up. If the primary CR-LSP fails, services are switched to the backup CR-LSP. If the primary CR-LSP recovers, services are switched back to the primary CR-LSP.

l Cold standby: A backup CR-LSP is created after a primary CR-LSP fails. If the primary CR-LSP fails, services are switched to the backup CR-LSP. If the primary CR-LSP recovers, services are switched back to the primary CR-LSP.

l Disabled: A backup CR-LSP is not configured.

Major Parameter Settings

Configure BFD Configure BFD when creating a tunnel.

l Disabled l Static BFD l Dynamic BFD

When Protection Type is set to Hot standby, this parameter is automatically set to Tunnel BFD Type STATIC. When configuring static BFD, you can also configure BFD for TE and BFD for LSP.

When configuring dynamic BFD, you can configure only BFD for LSP.

l BFD for TE: Millisecond-level fault detection and service protection are achieved when the primary tunnel does not function properly.

l BFD for LSP: Millisecond-level fault detection and service protection are achieved when the primary CR-LSP does not function properly.

NOTE

The BFD for TE detection period must be three times longer than the BFD for LSP detection period. Therefore, the value of MinRescSendInt for BFD for LSP must be less than that for BFD for TE.

Template Using Template to configure tunnel details is recommended.

Step 3 Configure the tunnel list and NE list. Select the source and sink NEs of the tunnel by double-clicking them in the physical topology. Then set the roles of the NEs in the NE Role column.

You can also use the following methods to select source and sink NEs:

l Method 1: Select the desired NE in the physical topology, right-click, and choose Add from the shortcut menu.

l Method 2:

1. Click Add and choose NE. In the Select NE dialog box, select the desired NEs.

2. Click OK.

NOTE

When you set Network Type to Ring, you can click Up or Down to adjust the position of the NE in the NE list.

Step 4 Optional: Configure route constraints for the tunnel.

NOTE

If explicit or excluded NEs or interfaces for the tunnel to be created are required, configure route constraints.

Otherwise. select only the source and sink NEs for the tunnel.

l Click Add on the right of Route Constraint. Then select the displayed entry and click Configure to set Interface IP Address and Restriction Type.

l If Network Type is set to Hub-Spoke, the following method can be used: Right-click the NE in the Main Topology and choose Set Explicit Restriction > NE/Interface from the shortcut menu. Configured route constraints are displayed on the Route Constraint tab.

NOTE

l In consideration of tunnel scalability (adding nodes to tunnels), setting Restriction Type to Loosely include is recommended.

l If creating an explicit path fails, modify the path information as prompted and create the path again.

Parameter Description

Loosely include A tunnel must pass through the interfaces of route restriction objects.

In addition, the actual route of the tunnel must pass through the objects in the same sequence as the objects are listed in the explicit path table.

For this restriction type, the interface of a route restriction object can be reached through multiple hops.

Strictly include A tunnel must pass through the interfaces of route restriction objects.

In addition, the actual route of the tunnel must pass through the objects in the same sequence as the objects are listed in the route restriction table. For this restriction type, the interface of a route restriction object must be reached through one hop.

Exclude A tunnel does not pass through the interfaces of route restriction objects.