L3 network interface management

Prerequisites

Before configuring microwave backhaul L3 services, ensure that the NE mediation is configured with the SSH2 communication protocol for L3 VPN Wavence devices.

L3 global routing

The NFM-P supports the configuration of an L3 VLAN with IP/MPLS traffic for a specific Wavence device. The VLAN where the L3 global routing is enabled is unique in the network, that is, all of the IP/MPLS traffic is carried over the same VLAN.

NFM-P manages the L3 VLAN as a backhaul service; for example, discovery, creation, deletion, inventory, and fault reporting are also applicable for L3 VLAN.

The L3 VLAN ID cannot be used for L2 backhaul services.

IP network interface

The NFM-P supports the configuration and discovery of IP network interfaces assigned to Ethernet and radio ports of CorEvo, EASv2, CAHD, EAC, 1+0 radio interface, 1+1 radio interface, L1 LAG radio interface, and Ethernet LAGxcards. You can modify an already configured L3 network interface that is associated with a routing instance.

System interface

The system interface is the default network interface that is configured on the NE.

The user has to assign the address for the interface that will be used for other functionality, such as Static LSP and Static label maps.

Static route

The NFM-P supports the manual configuration of static routes for Wavence devices. The static route configuration requires the system IP address of the node within the network and the next-hop interface IP address through which it is connected. Each node will have the static route information of all the nodes.

MPLS initialization and label distribution

The NFM-P supports the manual initialization of the MPLS (Multi-Protocol Label Switching) at the Wavence device by configuring the following:

NFM-P displays the MPLS objects as child objects of the routing instance in the network view of the navigation tree. The inventory list of the nodes where the MPLS protocol is initialized is supported at the network level. The MPLS label distribution is achieved by local configuration of the labels associated with each remote system. NFM-P displays the list of remote systems for every Wavence device having MPLS protocol enabled.

Static Label Map

MPLS static LSP feature enable the node to statically assign local labels to an IPv4 prefix. LSPs can be provisioned for these static labels by specifying the next-hop information that is required to forward the packets containing static label.

Static LSP

Wavence can be used to support L3 IPv4 data routing services using the capabilities of the MPLS networking using LSPs. L3 IPv4 data plane routing and static LSPs are required in Wavence to support static LSP. These enable the user to create and configure static IP routes by creating network interfaces. The MPLS static LSP feature enables the product to statically assign local labels to an IPv4 prefix. All the IPv4 Data Plane and MPLS (LSP and L3VPN) related configuration in the Wavence will be static configuration provisioned by the operator or user and by the NMS or Carrier SDN controller.

Swap and Pop operations can be created either using the static label maps from MPLS interface properties window or while configuring the static LSP paths.

Segment Routing Traffic Engineering LSP

Segment Routing Traffic Engineering (SR-TE) LSPs forward traffic along a network chain different than the one at the lowest cost, for the purposes of network optimization. BE SPF might not consider the convergences of several LSP via the same set of links, creating congestion. By the same token, some links might be under utilized since they are not involved in the SPF. Via the joint usage of BE and TE LSPs, a centralized SDN controller can optimize the network usage balancing flows across them.

For information about configuring SR-TE LSPs, see the NSP Classic Management User Guide. For considerations when using SR-TE with Wavence, see Wavence VPRN service — considerations/limitations.

SDP tunnel

The Service Distribution Point (SDP) is a logical representation of the transport tunnel that is used to deliver the service data to the egress PE. For Wavence NEs, the transport tunnel to be associated with the SDP is the static LSP able to reach the PE (or P node able to reach the PE). An SDP is locally unique within the NE and represented by an SDP ID. The same SDP ID can appear on other NEs. An SDP uses the system IP address to identify the far-end NE.

The SDP provides the binding between the service labels and the transport tunnel. To make a VPRN service to use an SDP for distribution, the service should be joined to the SDP using SDP binding, that is, spoke-SDP.

The operational and administrative states of the SDP control the state of the VPRN services bound to the SDP. The operational state of SDP is a result of the operational state of the underlying static LSP.

Black-hole routes

The black-hole feature configures a static route in the routing table (VRF), which drops all the traffic matching with this destination system IP address. A black-hole route can be created with the intended destination IP address whose next hop is 0.0.0.0, by default.

VPRN ping

The VPRN ping OAM diagnostic test determines the existence of the far-end egress point of the service. This allows testing of whether a specific destination can be reached. VPRN pings can be sent in-band or out-of-band. When a VPRN ping test packet is sent, a reply is generated if the targeted prefix is reachable over a VPRN SAP or VPRN spoke interface; otherwise the test packet is dropped in CPM. This also applies in the case of a routed VPLS interface. See To create and run a VPRN Ping test from a service manager form and To create and run a VPRN Ping test on a SAP.

See the NSP Classic Management User Guide for information about configuring and using STM tests.