Lsm Reader For Mac

11-05-2021
 |  [RAND-100] - Comments

Contents

Xamarin.Forms provides the ability to develop a cross-platform application that can target different devices. When you create an Xamarin.Forms solution, it consists of a shared Forms project in combination with separate projects for targeting iOS and Android. NIS-Elements Viewer. NIS-Elements Viewer is a free standalone program to view image files and datasets. It offers the same powerful view and image selection modes as the NIS-Elements core packages: Volume View with 3D Rendering, Tile View for Time, Z and Multipoint datasets, and Slice View for Z and Time datasets.

Introduction

This document describes Virtual Private LAN Service (VPLS) Label Switched Multicast (LSM) for the Aggregation Services Router (ASR) 9000 Series that run Cisco IOS® XR software.

Prerequisites

Requirements

There are no specific requirements for this document.

Lsm File Mac

Components Used

This document is not restricted to specific software and hardware versions.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

VPLS Label Switched Multicast (LSM) Overview

VPLS emulates LAN services across a Multiprotocol Label Switching (MPLS) core. A full mesh of point-to-point (P2P) pseudowires (PWs) is set up between all of the Provider Edge (PE) routers that participate in a VPLS domain in order to provide VPLS emulation. Broadcast, multicast, and unknown unicast traffic is flooded in a VPLS domain to all PEs. Ingress replication is used in order to send that flooded traffic over each P2P PWs to all remote PE routers that are part of the same VPLS domain.

Drawbacks of Ingress Replication

  • Ingress replication is bandwidth inefficient because the same packet might be sent multiple times over the same link for each P2P PW.
  • Ingress replication can result in significant wasted link bandwidth when there is heavy broadcast and multicast VPLS traffic.
  • Ingress replication is also resource-intensive because the ingress PE router bears the full burden of the replication.

VPLS LSM Features

VPLS is a widely-deployed service provider L2VPN technology that is also used for multicast transport. Although L2 technology allows snooping to be used in order to optimize replication of multicast traffic into L2 pseudowires, the core remains agnostic to multicast traffic. As a result, multiple copies of the same flow traverse core networks. In order to mitigate this inefficiency, pair LSM with VPLS in order to introduce LSM multicast trees over the core. In Cisco IOS-XR Software Release 5.1.0, Cisco ASR 9000 Series implement VPLS LSM with point-to-multipoint traffic engineering (P2MP-TE) inclusive trees. VPLS end points are automatically discovered and P2MP-TE trees are set up with the use of Resource Reservation Protocol Traffic Engineering (RSVP-TE) without operational intervention.

  • VPLS LSM overcomes the drawbacks of ingress replication.
  • The VPLS LSM solution employs P2MP LSPs in the MPLS core in order to carry broadcast, multicast, and unknown unicast traffic for a VPLS domain.
  • P2MP LSPs allow replication in the MPLS network at the most optimal node and minimize the amount of packet replication in the network.
  • The VPLS LSM solution only sends flooded VPLS traffic over P2MP LSPs.
  • Unicast VPLS traffic is still sent over P2P PWs. Traffic sent over Access PWs continues to be sent with ingress replication.
  • P2MP PWs are unidirectional as opposed to P2P PWs, which are bidirectional.
  • The VPLS LSM solution involves the creation of a P2MP PW per VPLS domain in order to emulate a VPLS P2MP service for core PWs in the VPLS domain.
  • VPLS LSM is supported in Cisco IOS XR Release 5.1.0 and later.
Lsm reader for mac

VPLS LSM Restrictions

  • Cisco IOS-XR Release 5.1.0 VPLS LSM functionality supports only MPLS Traffic Engineering P2MP-TE trees set up with RSVP-TE.
  • A P2MP PW can be signaled with the BGP protocol only in Cisco IOS-XR Release 5.1.0. In this first phase, the remote PEs that participate in the VPLS domain are auto-discovered with BGP Auto-Discovery (BGP-AD).
  • Static LDP signaling is not supported in Cisco IOS XR Release 5.1.0.

Media Access Control (MAC) Learning

MAC learning on the Leaf PE for a frame that arrives on P2MP PW is done as if the frame is received on the P2P PW leading to the Root PE for that P2MP PW. In this image, MAC Learning on PE-2 for frames that arrive on the P2MP PW LSP rooted at PE-1 is done as if the frame arrived on the P2P PW between PE-1 and PE-2. The L2VPN control plane is responsible for programming the VPLS disposition information with P2P PW information for MAC learning on the P2MP LSP disposition.

Internet Group Management Protocol Snooping (IGMPSN) Support

Internet Group Management Protocol (IGMP) Snooping (IGMPSN) is supported on both the Head and Tail of the P2MP P-tree in a bridge domain that participates in VPLS LSM. This allows IGMPSN multicast traffic over a virtual forwarding instance (VFI) PWs to benefit from the resource optimization provided by P2MP LSPs. If IGMPSN is enabled in a bridge domain with one or more VFI PWs participating in VPLS LSM, all of the layer two (L2) multicast traffic is sent over the P2MP P-tree Head associated with the bridge domain. L2 multicast routes are used in order to forward traffic to local receivers, Ethernet Flow Points (EFPs), access PWs, and VFI PWs that do not participate in VPLS LSM.

When IGMPSN is enabled in a bridge domain that is a P2MP LSP tail, optimized disposition of L2 multicast traffic received on the P2MP LSP is done for local receivers (that is, Attachment Circuit (AC) Bridge Ports (BPs) and access PW BPs).

Note: Multicast Label Distribution Protocol (MLDP) Snooping is not supported in Cisco IOS XR Release 5.1.0.

Scale Supported

Cisco IOS XR Release 5.1.0 supports a maximum of 1000 P2MP Tunnels or 1000 P2MP PWs per Head/Tail router.

VPLS LSM Configuration

P2MP Auto Tunnel Configuration

MPLS TE Fast Reroute (FRR) Configuration

L2VPN Configuration

Sample Topology and Configuation

The P2MP tunnels are auto-discovered tunnels. Static P2MP tunnels are not supported.

Lsm Reader For Mac

Static tunnel configurations are not used. The auto P2MP tunnel configuration must be enabled on all of the PE routers and also on a P router if it acts as a bud node. A bud node is a midpoint and tailend router at the same time.

A sample topology with configuration is shown here. In this topology, P2MP PWs are created between the three PEs and a P router which acts as a bud node. All three PE routers act as Head (for ingress traffic) and Tail (for egress traffic).

PE1 Configuration

P Configuration

PE2 Configuration

PE3 Configuration

Verify - Show Commands

These show commands are useful in order to debug and verify the status of the P2MP PW and P2MP MPLS TE tunnels.

  • show l2vpn bridge-domain
  • show l2vpn bridge-domain detail
  • show mpls traffic-eng tunnels p2mp
  • show mpls forwarding labels <label> detail
  • show mpls traffic-eng tunnels p2mp tabular

Lsm Toolbox Mac

Here are some examples:

Troubleshoot VPLS LSM

Common Configuration Issues

The most common causes for P2MP problems in L2VPN are shown here.

  • The BGP configuration for LSM is exactly the same as that for BGP-AD. Make sure to export/import l2vpn vpls-vpws address family routes by configuring address-family l2vpn vpls-vpws for BGP neighbors.
  • There are MPLS and multicast configuration errors.
    MPLS Traffic Engineering must be enabled on the interfaces where the P2MP PWs passes.
  • The L2VPN configuration for LSM in Cisco IOS XR Release 5.1.0 requires that you:
    • Configure the VPN ID configuration for the VFI
    • Configure multicast P2MP for the VFI. Confgure the transport protocol and signaling protocol, as in this example configuration:

  • The LSM Head/Tail must be set properly. In Cisco IOS XR Release 5.1.0, each LSM tail is also a LSM Head and vice-versa. Because there is no explicit LSM capability exchange among routers, all routers in a LSM enabled bridge domain must participate in LSM.

L2VPN and L2FIB Show Commands and Troubleshoot

Lsm Viewer Mac

  • The L2VPN manager process (l2vpn_mgr) communicates with the MPLS Traffic Engineering (TE) control process (te_control) and requests the tunnel creation. Ensure that the te_control and l2vpn_mgr processes are in the running state with these commands:
    • show process l2vpn_mgr
    • show process te_control

  • Check that the l2vpn_mgr process has requested the tunnel creation. An entry for the tunnel should be in this show command:
  • L2VPN has to receive the tunnel information from the te_control process. Verify that this show command has non-zero details such as tunnel-id, Ext.tunnel-id, tunnel-ifh, and p2mp-id:
  • L2VPN must advertise the Provider Multicast Service Instance (PMSI) to all other PE routers. Check that l2vpn_mgr has sent the PMSI for the configured VFI. The event LSM Head: send PMSI should be present in the event history for the VFI.
  • L2VPN on the other routers should receive the PMSI that has just been sent. Ensure that LSM Tail: PMSI received is shown in the event history on the receiving side:
  • Each router is both an LSM Head and Tail and should send the PMSI and receive PMSIs from each of the other routers. The first router checked should receive PMSIs from each of the other nodes.
  • The Layer Two Forwarding Information Base (L2FIB) must receive the HEAD information from L2VPN and must download them to the linecard.
  • L2FIB must receive the TAIL information from L2VPN for each PW and must download them to the platform.