Microwave backhaul service configuration

Introduction

NFM-P supports the configuration of VLAN, VLL, and composite services on the Wavence devices. The VLAN and VLL services are configured using the microwave backhaul service configuration form. All the microwave backhaul services are identified by a VLAN ID and a service manager ID that are assigned at the time of service creation.

The microwave backhaul service configuration is performed as follows:

See To configure microwave backhaul services for more information about microwave backhaul service configuration.

The NSP supports Wavence service creation using intent-based service fulfillment. See Microwave backhaul service creation using NSP Intent-Based Service Fulfillment.

VLAN services

VLAN services provide the segmentation services traditionally provided by routers in LAN configurations. VLANs address issues such as scalability, security, and network management. Routers in VLAN topologies provide broadcast filtering, security, address summarization, and traffic flow management.

NFM-P supports the configuration of the following VLAN services on Wavence devices:

The configuration of dot1q and dot1ad parameters is performed at the node level in the System Settings tab of the Network Elements (Edit) form.

See To configure microwave backhaul services for more information about microwave backhaul service configuration.

VLL services

NFM-P supports the configuration of VLL services on Wavence devices. A VLL service is an L2 point-to-point service that connects backhaul adjacencies. A VLL service is completely transparent to customer or subscriber data and to control protocols. Because of this transparency, the device performs no MAC address learning in a VLL service. See To configure microwave backhaul services for more information about microwave backhaul service configuration.

Service objects

See To view the microwave backhaul service objects for more information about each of the service objects.

Manual adjacency configuration

NFM-P supports the addition of the sites and adjacencies manually when you configure a microwave backhaul service. The physical links need to be configured and Ethernet ring needs to be configured for services that include one or more rings. See To configure microwave backhaul services for more information about microwave backhaul service configuration.

Automatic adjacency configuration

NFM-P supports adding the sites and adjacencies automatically when you configure a microwave backhaul service. You can configure a service, then perform path search, complete ring, or copy service to add the sites and adjacencies automatically. The physical links need to be configured and Ethernet rings need to be configured for services that include one or more rings.

Path search

A P2MP path is populated automatically by choosing Populate Service→Search For Path menu option on the Microwave Backhaul Service (Edit) form and selecting the source and destination sites. A P2MP path is populated automatically by performing multiple path searches. The P2P path is first configured. Then, the Populate Service→Search For Path option is used multiple times to search multiple paths. Alternatively, the source and destination ports are provided during the path search operation to complete the end-to-end path.

NFM-P supports path search with mixed path types that is, a combination of VLAN and VLL paths when both VLAN and VLL are part of a microwave backhaul service. In the Microwave Backhaul Service Path Search form, the IsHeterogeneous parameter is enabled for such mixed paths. Before implementing the path search for heterogeneous services, the MAC address must be calculated and explicitly given by the user for the traffic to flow between the nodes. The path search only lists the shortest paths. See To configure microwave backhaul services for more information about microwave backhaul service configuration.

Note: During path search, the entirety of the ring is a single hop, so a "longer" ring path may be returned instead of a topologically "shorter" path.

Complete ring

You can use the complete ring function in a service that includes one or more rings, which allows you to add all of the sites and adjacencies of the Ethernet ring at the same time. Configure one ring site first, by providing a suitable adjacency and the ring pointer. Then, use the Populate Services→Complete Ring option on the Microwave Backhaul Service (Edit) form to automatically configure all of the remaining sites and adjacencies of the Ethernet ring. See To complete a ring by automatically adding the ring adjacencies for more information about how to complete a ring.

Copy services

You can copy sites from an existing microwave backhaul service into a new microwave backhaul service. A new service is first configured, and the existing microwave backhaul service is copied, to create a new microwave backhaul service. All of the sites and ports are copied from the existing microwave backhaul service except the TDM, SDH channelized, and SDH ports that cannot be reused.

Ensure that the existing microwave backhaul service and the new microwave backhaul service:

See To copy a microwave backhaul service for more information about copying a service.

Connect service

Perform the connect service operation to establish links between the service objects. The integrity of the topology is determined when all the service objects are determined and the results are displayed. The incorrect topology is identified by a selected Topology Misconfigured check box and the correct topology is indicated by a deselected Topology Misconfigured check box. NFM-P calculates the operational state after the connect operation only if the topology is correctly configured and deployed on all of the Wavence devices. See To configure microwave backhaul services for more information about microwave backhaul service configuration.

Incorrect topology

The following are the examples of scenarios that result in incorrect topology:

Deploy service

Perform the deploy operation to deploy the microwave backhaul service on the Wavence devices. The deploy operation also allows you to re-deploy failed deployments. You can skip the connect operation, and directly perform the deploy operation, if the connect operation fails even after repeated reconfigurations. NFM-P calculates the operational state only after the connect operation is performed and the topology is correctly configured.

Non-MPR sites

Deploying a microwave backhaul service does not deploy to non-MPR sites. If you add an SR or OEM site to the service, either manually, through path search, or through ring completion, the service configuration is not deployed. You need to configure the corresponding VPRN, VPLS, XC, and VLAN configurations on the non-MPR sites. While configuring such sites in backhaul service, NFM-P automatically deploys the adjacencies on the site.

Service topology map

You can open a service topology map for a microwave backhaul service by clicking Topology View on the Microwave Backhaul Service (Edit) form.

You can perform the following functions from the contextual menu in the service topology map:

Propagate microwave backhaul service names to sites

NFM-P allows you to propagate microwave backhaul service names to sites by selecting the check boxes, “Whenever a site is added to a service in the NFM-P propagate the Service Name to Site Name” and “Propagate Name and Description of Service” in the Services tab of the Administration→System Preferences→System Preferences form. See To propagate microwave backhaul service name to sites for more information about how to propagate microwave backhaul service names to sites.

Note: Propagation of name from service to service site is supported during the following tasks after the deploy function is performed:

Note: Propagation of name from service to service site is only applicable to VLAN service and not to VLL service.

If user enables this option (Administrator→System Preferences→Services) from the NFM-P GUI “Whenever a site is added to a service in the NFM-P propagate the Service Name to Site Name” then NFM-P will propagate the Service Name to Site Name while adding a new site to the existing service or while creating a new service.

If user disables this option (Administrator→System Preferences→Services) from NFM-P GUI “Whenever a site is added to a service in the NFM-P propagate the Service Name to Site Name” then NFM-P will not propagate the Service Name to Site Name during site addition to service.

If user enables this option (Administrator→System Preferences→Services) “Propagate Name and description of Service” then NFM-P will propagate the Service Name and Description of Service to Site Name and Description. This preference is applicable only for an existing service.

If user disables this option (Administrator→System Preferences→Services) “Propagate Name and description of Service” then NFM-P will not propagate Service Name and Description of Service to Site Name and Description. This preference is applicable only for an existing service.

Note: If the “Propagate Name and description of Service” system preference is enabled then NFM-P will be the master; any changes on the site’s Name from a Wavence element manager will be overridden with the Service’s Name in the NFM-P.