76 8600 50124h 8600 smart routers test and measurement configuration guide

76.8600-50124G 29.10.2014 Added 8615 Smart Router functionality in: • 4.1 Virtual Circuit Connectivity Verification Overview • 3 Packet Loop Test Reworked5 Ethernet Loopback.Added suppor

Test and Measurement Configuration Guide

76.8600-50124H 15.05.2015

Revision History Document No Date Description of Changes

76.8600-50124H 15.05.2015 Added 8665 Smart Router functionality in:

• 4.1 Virtual Circuit Connectivity Verification Overview

• 3 Packet Loop Test

Reworked:3.1.8 8600 NEs PLT Functionalityand3.2 PacketLoop Test Configuration Examples

Changes applied in4.1 Virtual Circuit Connectivity VerificationOverview

Updates applied in2.2 LSP Ping and Traceroute ConfigurationExamples

76.8600-50124G 29.10.2014 Added 8615 Smart Router functionality in:

• 4.1 Virtual Circuit Connectivity Verification Overview

• 3 Packet Loop Test

Reworked5 Ethernet Loopback.Added support of BGP IPv4 Label Unicast in2.1 LSP Ping andTraceroute Overview

Added BGP IPv4 Label Unicast ping and traceroute CLI syntax in

2.2 LSP Ping and Traceroute Configuration Examples.Added a note clarifying a link behavior after issuing the 'noloopback to-equipment' command in5.1.3 Equipment LoopbackOperation

Changes applied in5.2 Ethernet Loopback ConfigurationExamples

76.8600-50124F 27.05.2014 Added 8602 Smart Router functionality in:

• 4.1 Virtual Circuit Connectivity Verification Overview

• 3 Packet Loop Test

• 5 Ethernet Loopback

• 8 MAC Swap Loopback

Renewed NE PLT support table in3.1.8 8600 NEs PLTFunctionality

Added support of MAC swap loopback in 8609 Smart Router and

8611 Smart Router8 MAC Swap Loopback.Changes applied in5.1.3 Equipment Loopback Operationand

Equipment Loopback Activation

The functionality described in this document for 8615 Smart Router is also applicable to 8615 Smart Router stacked, unless otherwise stated.

© 2015 Coriant All rights reserved.

This manual is protected by U.S and international copyright laws, conventions and treaties Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws Unauthorized reproduction, modification,

distribution, display or other use of this manual may result in criminal and civil penalties.

The specifications and information regarding the products in this manual are subject to change without notice All statements, information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,

express or implied Users must take full responsibility for their application of any products.

Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Terms and Abbreviations

AC Attachment Circuit

AF Assured ForwardingAIS Alarm Indication SignalATM Asynchronous Transfer Mode

BFD Bidirectional Forwarding Detection

CC Control ChannelCDC Control and DC Power Card

CE Customer EquipmentCLI Command Line InterfaceCPU Central Processing Unit

CV Connectivity VerificationDNS Domain Name SystemELP Ethernet Link Protection

FDV Frame Delay VariationFEC Forwarding Equivalence ClassFRR Fast Re-Route

FTN Forwarding equivalence class To Next hop label forwarding entry mapICMP Internet Control Message Protocol

IETF Internet Engineering Task ForceIFC Interface Module Concentrator is the line card baseboardIFC line card The IFC line card in 8630 Smart Router and 8660 Smart Router and consists of an

IFC and up to two IFMs There are two types of IFC line cards: IFC1 and IFC2IFDV Inter-Frame Delay Variation

IP Internet Protocol

MS-PWE3 Multi-Segment PWE3MTU Maximum Transfer/Transmission Unit

NSP Native Service ProcessingNTP Network Time ProtocolOAM Operation, Administration and Maintenance

PE Provider Edge Network ElementPLT Packet Loop Test

PSN Packet Switched NetworkPWE3 Pseudowire Emulation Edge to EdgeQoS Quality of Service

RDI ATM Remote Defect IndicationRFC Request For CommentsRSVP Resource Reservation ProtocolRSVP-TE RSVP with Traffic Engineering Extensions

TX Transmit, TransmissionUDP User Datagram ProtocolVCCV Virtual Circuit Connectivity VerificationVPLS Virtual Private LAN Service

VPN Virtual Private NetworkVRF Virtual Routing and ForwardingVSI Virtual Switching Instance

Table of Contents

About This Manual 10

Objectives 10

Audience 10

8600 Smart Routers Technical Documentation 10

Interface Numbering Conventions 14

Document Conventions 14

Documentation Feedback 14

8600 Smart Routers Discontinued Products 15

1 Ping and Traceroute 16

1.1 Ping and Traceroute Overview 16

1.1.1 Introduction 16

1.1.2 Ping 16

1.1.3 Traceroute 18

1.1.4 References 19

1.2 Ping and Traceroute Configuration Examples 20

1.2.1 Ping 20

1.2.2 Traceroute 21

2 LSP Ping and Traceroute 22

2.1 LSP Ping and Traceroute Overview 22

2.1.1 Introduction 22

2.1.2 Operation 23

2.1.3 References 24

2.2 LSP Ping and Traceroute Configuration Examples 24

3.1.1 Introduction 33

3.1.2 One-Way Delay Variation Test 34

3.1.3 Round-Trip Delay Test 34

3.1.4 One-Way Delay Test 34

3.1.5 Throughput Test 34

3.1.6 One-Way Packet Loss Test 35

3.1.7 IP Addresses Configuration for PLT 35

3.1.8 8600 NEs PLT Functionality 36

3.1.9 References 37

3.2 Packet Loop Test Configuration Examples 37

3.2.1 Delay Tests 37

3.2.2 Throughput Tests 40

3.2.3 Packet Loop Test Results 43

4 Virtual Circuit Connectivity Verification 47

4.1 Virtual Circuit Connectivity Verification Overview 47

4.1.1 Control Channel Methods 47

4.1.2 Connectivity Verification 48

4.1.3 Multi-Segment PWE3 VCCV LSP Ping and Traceroute 50

4.2 VCCV References 51

4.3 VCCV Configuration Examples 51

4.3.1 VCCV BFD 52

4.3.2 VCCV LSP Ping 53

4.3.3 MS-PWE3 VCCV LSP Ping and Traceroute Configuration 54

5 Ethernet Loopback 56

5.1 Ethernet Loopback Overview 56

5.1.1 Ethernet Loopback Types 56

5.1.2 Line Loopback Operation 56

5.1.3 Equipment Loopback Operation 57

5.2 Ethernet Loopback Configuration Examples 58

5.2.1 Activating Loopback Tests 58

6 Pseudowire Loopback 61

6.1 PWE3 Loopback Overview 61

6.1.1 Theory of Operation 61

6.2 PWE3 Loopback Configuration Examples 62

6.2.1 Activating Loopback Tests 62

7 Ethernet OAM 65

8 MAC Swap Loopback 66

8.1 Overview 66 8.2 MAC Swap Loopback Configuration 66

About This Manual

This chapter discusses the objectives and intended audience of this manual, 8600 Smart Routers Test and Measurement Configuration Guide and consists of the following sections:

Audience

This manual is designed for administration personnel for configuring 8600 Smart Routers functionswith CLI On the other hand, 8000 Intelligent Network Manager provides access to equal

functionality for administration personnel with a graphical user interface

It is assumed that the readers have a basic understanding of IP networks and using ping andtraceroute programs for testing IP connectivity

8600 Smart Routers Technical Documentation

The document numbering scheme consists of the document ID, indicated by numbers, and thedocument revision, indicated by a letter The references in the Related Documentation table beloware generic and include only the document ID To make sure the references point to the latestavailable document versions, please refer to the relevant product document program on the Tellabsand Coriant Portal by navigating towww.portal.tellabs.com> Product Documentation & Software

> Data Networking > 8600 Smart Routers > Technical Documentation

Document Title Description

8600 Smart RoutersATM and TDM Configuration Guide(76.8600-50110)

Provides an overview of 8600 NEs PWE3 applications,including types, Single-Segment and Multi-Segment; PWE3Redundancy; ATM applications, including PWE3 tunnelling,Traffic Management, Fault Management OAM, protection andTDM applications as well as instructions on how to configurethem with CLI

8600 Smart RoutersBoot and Mini-ApplicationsEmbedded Software Release Notes(76.8600-50108)

Provides information related to the boot and mini-applicationssoftware of 8605 Smart Router, 8607 Smart Router, 8609Smart Router, 8611 Smart Router, 8620 Smart Router, 8630Smart Router and 8660 Smart Router as well as the installationinstructions

8600 Smart RoutersCLI Commands Manual(76.8600-50117)

Provides commands available to configure, monitor and maintain

8600 system with CLI

8600 Smart RoutersEmbedded Software Release Notes

8600 Smart Routers SR7.0 Embedded Software Release Notes(76.8670-50177) for the following products:

Provides an overview of 8600 system HW inventory, softwaremanagement, equipment protection 1+1 (CDC and SCM) as well

as instructions on how to configure them with CLI

8600 Smart RoutersEthernet Configuration Guide (76

8600-50133)

Provides an overview of 8600 system Ethernet applications,including interfaces; Ethernet forwarding (MAC Switching,Ethernet PWE3, IRB, VLAN, VPLS); Ethernet OAM; LAG;ELP as well as instructions on how to configure them with CLI

8600 Smart Routers Smart RoutersFault Management ConfigurationGuide (76.8600-50115)

Provides an overview of 8600 system fault management,including fault source, types and status as well as instructions onhow to configure it with CLI

8600 Smart RoutersFrame Relay Configuration Guide(76.8600-50120)

Provides an overview of 8600 system Frame Relay applications,including interfaces; Performance Monitoring; protection; TrafficManagement as well as instructions on how to configure themwith CLI

8600 Smart RoutersHardware Installation Guide(76.8600-40039)

Provides guidance on mechanical installation, cooling,grounding, powering, cabling, maintenance, commissioning andESW downloading

Document Title Description

8600 Smart RoutersInterface Configuration Guides The Interface Configuration Guides provides an overview of the8600 NEs interface functions, including NE supported interface

types and equipping; interface features; configuration options andoperating modes; fault management; performance monitoring;interface configuration layers and port protocols as well asinstructions on how to configure them with CLI The followinginterface configuration guides are available:

• 8600 Smart Routers Network Interfaces ConfigurationGuide (76.8600-50161) (for 8602 Smart Router, 8615 SmartRouter and 8665 Smart Router)

• 8609 Smart Router and 8611 Smart Router FP7.0 InterfaceConfiguration Guide (76.8670-50179)

• 8600 Smart Routers FP7.0 Interface Configuration Guide(76.8670-50180) (for 8630 Smart Router and 8660 SmartRouter)

8600 Smart Routers

IP Forwarding and TrafficManagement Configuration Guide(76.8600-50122)

Provides an overview of 8600 NEs IP, forwarding and trafficmanagement functionality, including: IP addressing; IP hosting(ARP, DHCP); IP routing (static); ACL; Differentiated Services(Policing, Queue Management, Shaping) as well as instructions

on how to configure them with CLI

8600 Smart RoutersManagement CommunicationsConfiguration Guide

(76.8600-50125)

Provides an overview of 8600 system managementcommunications functions, including communication protocols:BMP; FTP; RADIUS; SNMP; SSH; TELNET as well asinstructions for configuring them with CLI

8600 Smart RoutersMobile Optimization ConfigurationGuide (76.8600-50100)

Provides an overview of 8600 system Mobile Optimizationapplications as well as instructions on how to configure themwith CLI

8600 Smart RoutersMPLS Applications ConfigurationGuide (76.8600-50123)

Provides an overview of 8600 NEs MPLS applications (includingFRR (one-to-one and facility backup); LDP; protection andTraffic Engineering), MPLS-TP applications (including OAM,linear protection), S-MPLS applications as well as instructions

on how to configure them with CLI

8600 Smart RoutersPerformance Counters ReferenceGuide (76.8600-50143)

Provides an overview of 8600 system supported performancecounters

Document Title Description

8600 Smart RoutersReference Manuals The reference manuals describe the 8600 network elementfeatures including:

• NE enclosure, baseboard, power supply modules, andinterfaces in 8602 Smart Router FP7.0 Reference Manual(76.8670-40130)

• NE enclosure, baseboard, power supply modules, interfacesand physical LM types in 8609 Smart Router FP7.0 Refer-ence Manual

• NE enclosure, baseboard, power supply modules, SCMs, HMand LM types in 8611 Smart Router FP7.0 Reference Manual

• NE enclosure, baseboard, power supply modules, and terfaces in 8615 Smart Router FP7.0 Reference Manual(76.8670-40132)

in-• NE subrack, fan modules, CDCs, line cards and IFMs in 8630Smart Router FP7.0 Reference Manual

• NE subrack, fan modules, CDCs, line cards and IFMs in 8660Smart Router FP7.0 Reference Manual

• NE subrack, fan modules, line unit and switch unit in 8665Smart Router FP7.0 Reference Manual (76.8670-40128)

8600 Smart RoutersRouting Protocols ConfigurationGuide (76.8600-50121)

Provides an overview of 8600 NEs routing protocols, includingBFD; BGP; BGP MP; ECMP; IS-IS; OSPF and VRRP as well asinstructions on how to configure them with CLI

8600 Smart RoutersScalability Reference Manual(76.8600-50160)

Provide a summary of tested scalability limits of the 8600 SmartRouters

8600 Smart RoutersSNMP MIB Support(76.8600-50116)

Describes SNMP MIB support by the 8600 NEs and providesinformation on the supported objects and traps For furtherinformation on SNMP MIBs, see the related RFCs

8600 Smart RoutersStatistic Counters Reference Guide(76.8600-50142)

Provides an overview of 8600 system supported statistic counters

8600 Smart RoutersSynchronization ConfigurationGuide (76.8600-50114)

Provides an overview of 8600 NEs synchronization functionality,including physical layer Frequency Synchronization (SEC, EEC);PTP Frequency Synchronization; Phase-Time Synchronization(L2 and L3 applications) as well as instructions on how toconfigure them with CLI

8600 Smart RoutersTest and Measurement ConfigurationGuide (76.8600-50124)

Provides an overview of 8600 NEs measurement and connectivityverification tools, including Ethernet loopback; IP ping andtraceroute; MAC swap loopback; MPLS ping and traceroute;PLT; PWE3 loopback; VCCV (BFD, LSP ping) as well asinstructions on how to configure them with CLI

Interface Numbering Conventions

To be able to follow more easily the feature descriptions and configuration examples given in this

document, see also the 8600 system interface numbering and related figures described in 8600

Smart Routers CLI Commands Manual.

Document Conventions

This is a note symbol It emphasizes or supplements information in the document.

This is a caution symbol It indicates that damage to equipment is possible if the instructions are not followed.

This is a warning symbol It indicates that bodily injury is possible if the instructions are not followed.

Documentation Feedback

Please contact us to suggest improvements or to report errors in our documentation:

Email: fi-documentation@tellabs.com

8600 Smart Routers Discontinued Products

8600 Smart Routers Manufacture Discontinued (MD) notifications are available on the Tellabsand Coriant Portal,www.portal.tellabs.com > Product Documentation & Software > Data Networking > [8600 Smart Router product name] > Product Notifications.

1 Ping and Traceroute

1.1.1 Introduction

The 8600 system provides the well-known ping and traceroute tools to diagnose problems in an IPnetwork Additionally, ping and traceroute in the 8600 system have extended support for IP VPNs.Most hosts (such as ordinary PC workstations) and routers have support for ping and traceroute.Thus, these tools can be applied very easily

Ping and traceroute agents in 8600 Network Elements (NEs) support the DNS lookup Therefore,symbolic target names can be used instead of numeric addresses, if the DNS service is available

For more information on DNS, see 8600 Smart Routers CLI Commands Manual.

Because ping and traceroute do not use much network bandwidth, they can be applied also whilecustomer traffic is running

It should be noted that ping and traceroute packets are subject to any traffic restrictions in thenetwork For example, access control lists may prohibit forwarding ping or traceroute packets insome parts of the network

Ping is based on [RFC792] Ping is an application program that sends standard ICMP Echo packets

to some target IP address according to instructions from the user If the destination address isreachable, it will reply to the ping application with an Echo Reply message The ping applicationwill then report to the user whether the Echo Reply arrived, what the round-trip delay was etc Ifping succeeds, it reveals that there is a bidirectional IP level connection between the host of theping application and the destination address

If the ping message exchange succeeds, it does not reveal the route of the messages in eitherdirection (Traceroute will reveal a bit more information.) If the ping fails, the ping applicationcannot always indicate the reason for the failure

Usually, ping applications support DNS lookup, so that the user can use symbolic names (“pingwww.xyz.com”) instead of numeric IP addresses (“ping 197.23.44.2”)

Ping can be applied in numerous ways Examples are listed below See alsoFig 1

• Network operator can ping any network element.

• Any host connected to the global Internet can ping any network element whose name or address

is known

• Any host in an IP VPN can ping any other router or host in the same VPN This verifies theconnectivity inside a VPN The target of ping can be a customer device or a network element ofthe network operator

8000 Intelligent Network Manager may need to test the connectivity between endpoints neither ofwhich is the 8000 Intelligent Network Manager host For this purpose every 8600 network element

has a ping agent 8000 Intelligent Network Manager can connect the source end of the required

ping operation, ask the source end to ping another network element, and get the results back to 8000Intelligent Network Manager 8600 NE ping agent is enhanced so that it can also perform the pingmessage exchange inside any customer IP VPN For example, the network operator may wish toverify the IP VPN connectivity between two distant customer sites First the network operator mayidentify the two PE routers that are immediately connected to the customer sites, then make the one

PE router ping the other one inside the customer IP VPN A successful ping verifies that there

is not only a connection between the PEs (within the default routing plane), but the connectivityholds even inside the customer IP VPN See the figure below

Fig 1 Ping Examples

Note that the target address of ping, like any other IP address, is technically the address of aninterface, not the address of a network element This fact is relevant if the intended target of ping is arouter, which has many interfaces and thus many IP addresses A router does not reply to ping if thetarget interface is down (administratively shutdown or, e.g., cable disconnected) Thus, the results ofthe ping test may indicate a failure even if the target router replies OK, if another interface address

has been used To prevent false negatives, one should first ping a router with one of its loopback

addresses (which cannot have link failures) This rule also applies to ping inside IP VPN It may beuseful to configure a loopback address for IP VPN in a router that is used as a ping target Pinginside VPN to a loopback verifies a true connectivity to the PE router, while ping to the customerinterface address may fail depending on the link state

1.1.3 Traceroute

Traceroute is another well-known, simple and effective tool for diagnosing network problems; seealso [RFC2925] Traceroute is an application program that sends probe packets to some target IPaddress according to instructions from the user The probe message is typically a UDP message thatmay get a reply from the destination, but the real point of traceroute is that it repeats the probe withdifferent Time-To-Live (TTL) values in the probe packet It starts with TTL=1, then TTL=2 etc.until a reply is obtained from the destination or the maximum value of TTL (such as 30) is reached.Probe packets with small TTL values will not reach the destination, but intermediate routers giveICMP “TTL exceeded” replies to such messages when TTL counts down to zero By recordingthe incoming ICMP error messages, the traceroute application can report the IP addresses of allintermediate routers along the path to the destination

Fig 2 Traceroute Through MPLS

Every 8600 NE has a traceroute agent, which is similar to the ping agent This makes it easy to

perform connectivity tests between any chosen endpoints in the network 8600 NE traceroute agenthas enhanced support for IP VPNs, as the ping agent.Fig 1also applies as an example of traceroute.However, traceroute applications have certain inherent limitations:

• The data path between endpoints of traceroute may contain many diverse routers, some of whichare not 8600 NE Some routers along the path may not reply to the traceroute application asexpected.

• Any traffic, but especially VPN traffic, may go to MPLS paths Depending on the configuration

of the MPLS path, it may appear to traceroute as one single hop or as a series of small hops from

an MPLS switch to another SeeFig 2

• If the MPLS path appears as a series of short hops, the intermediate MPLS switches may stillhave difficulties in sending the ICMP message back to the traceroute application Perhaps theMPLS switch cannot reply within the appropriate IP VPN However, 8600 NEs will try to get thereply through

• Even if the traceroute application gets an ICMP message from the MPLS switch, its source IPaddress may appear confusing, because the MPLS switch often has no IP address inside the appro-priate IP VPN 8600 NEs will use an IP address from the default routing table in such situations,

as this is probably informative to the user

Note that the target address of traceroute, like any other IP address, is technically the address of aninterface, not the address of a network element This fact has the same consequences as in the case

of ping, as explained above Traceroute to a router may indicate a false negative if the traceroutetarget is an interface address and if this interface happens to have a link failure Such false negativescan be prevented by using a loopback address as target

1.2 Ping and Traceroute Configuration Examples

These chapters give instructions on how to use ping and traceroute tools

The target of the ping and traceroute can be either an IP address or, if DNS is available, a host name

The following chapters describe CLI command steps needed to use the ping tool All the examplesuseFig 1router pings router illustrations

Default Routing

Use the following command to find out whether the other router is available

Step 1 If the command is successful it means that there is a bidirectional IP level connection between the

router and the destination address 10.10.10.68

router> ping 10.10.10.68

Within IP VPN

Use the following command to find out whether the other router is available and inside the customer

IP VPN

Step 1 If the command is successful it means that there is a bidirectional IP level connection between the

router and the destination host wkst1.dl.tellabs.fi inside the customer IP VPN The ping sends 100probe packets (optional parameter)

router> ping wkst1.dl.tellabs.fi vrf customer1 packets 100

Step 1 The traceroute tool possibly shows all the intermediate routers between router1 and the destination

address 10.10.10.68 (see restrictions in chapter1.1.3 Traceroute)

router1> traceroute 10.10.10.68

Within IP VPN

Use the following command to find out which intermediate routers are between the router and thedestination address inside the customer IP VPN

Step 1 The traceroute tool possibly shows all the intermediate routers between router1 and the destination

address 10.10.10.68 (see restrictions in chapter1.1.3 Traceroute) The traceroute is done on thequality of service level of the expedited forwarding 1 (optional parameter)

router1> traceroute 10.10.10.68 vrf customer1 qos ef1

2 LSP Ping and Traceroute

2.1.1 Introduction

LSP ping and traceroute are defined by [RFC4379] LSP ping and traceroute offer connectivityverification and fault isolation services for MPLS LSPs and PWE3 circuits The 8600 NEs supportLSP ping and traceroute for:

• RSVP LSP

• LDPs with IPv4 FEC

• PWE3 circuits terminated in Multiservice interfaces

• PWE3 redundancy, where LSP ping and traceroute can be performed independently for both the

active and the standby pseudowires (please see the details in 8600 Smart Routers ATM and TDM

Configuration Guide and 8600 Smart Routers Ethernet Configuration Guide)

• VPLS mesh and spoke PWE3 circuits

• BGP IPv4 labeled unicast, please see the details in 8600 Smart Routers MPLS Applications

Con-figuration Guide

Compared to regular ping and traceroute, LSP ping offers the following additional benefits:

• LSP ping or traceroute can detect interruptions in LSP, when normal ping would pass via IP routedhops (that can occur in LDP LSPs if independent control mode is used) while LSP ping woulddetect any breaks in LSPs

• LSP ping or traceroute performs validation between label used and LSP Forwarding EquivalenceClass (FEC) This allows detection of any potential mis-merges in forwarding plane

• LSP ping and traceroute provide completed and detailed information of used path, such as labelstacks used

• LSP traceroute can be performed, even if uniform tunnel model is used (normal traceroute wouldnot see hops within LSP)

• LSP ping can be used to test PWE3 circuits In this case, LSP ping transits using VCCV controlchannel and hence tests actual PWE3 connectivity

PWE3 circuit must have VCCV CC and VCCV LSP ping configured (and in case of LDP negotiated PWE3 circuit, also signaled) before VCCV LSP ping is permitted.

• RSVP secondary LSPs can be tested while traffic is using primary LSP

• RSVP LSPs that do not carry IP traffic can be tested

RSVP LSP must have at least one map-route command before it can be tested using LSP ping or LSP traceroute.

When RSVP Fast Re-Route (FRR) is active on LSP, LSP traceroute results may vary depending

on the third party equipment The 8600 system disables by default RSVP LSP sender

validation to reduce false reports of mis-merges If FRR is not used, command “mpls ping

rsvp validate-lsp-sender” can be used to enable sender validation.

When FRR detour LSP/bypass tunnel is active:

- 1:1 detour LSPs and facility backup bypass tunnels are invisible with pipe model However there can be seen DSMAP mismatch and node terminating the active detour LSP/bypass tunnel.

- 1:1 detour LSPs and facility backup bypass tunnels are visible with uniform model and no errors should be reported However, if some third party equipment checks LSP sender, FEC stack mismatch may by generated.

If facility backup is used with link protection, using option “no-verify-if-addr” may provide

increased compatibility Bypass tunnels can be individually tested with LSP ping and traceroute Detour LSPs are not individually testable with LSP ping/traceroute.

2.1.2 Operation

LSP ping and traceroute packets are transmitted by head-end of RSVP tunnel or PWE3 circuit orLDP LSP LSP traceroute is a sub-function of LSP ping and uses LSP ping packets

LSP ping packets are normal UDP packets with the following special properties:

• IP destination address is in 127.x.x.x/8 range

• This ensures that if there is a break in LSP, IP forwarding will not forward LSP ping packetfurther

• Destination address can be varied on ping command within this range to allow testing tiple paths of ECMP LSPs and link aggregation groups LSPs tested by 8600 system cantransit LAG interfaces on other nodes and hence supports tracing of individual componentlinks

mul-• IP header of LSP ping packets contains IP router alert option, this will ensure that egress of LSPsprocesses packet instead of forwarding it out of the LSP

• IP TTL of LSP ping packets is 1 to prevent the forwarding of these packets

LSP ping packets contain FEC stack identifying LSP being pinged The information is used bytransit and egress nodes of the LSP to check for mis-merges For example when performing ping:

• RSVP LSP ping packets contain:

• RSVP LSP source and destination

Related topics:

• PWE3 types supported in the 8600 NEs, please refer to 8600 Smart Routers ATM and TDM

Con-figuration Guide and 8600 Smart Routers Ethernet ConCon-figuration Guide

• IP and traffic management, please refer to 8600 Smart Routers IP and Traffic Management

Con-figuration Guide.

• MPLS and traffic engineering, please refer to 8600 Smart Routers MPLS Applications

Configu-ration Guide.

• Routing protocols including BFD, ECMP and VRRP, please refer to 8600 Smart Routers Routing

Protocols Configuration Guide.

2.1.3 References

[RFC4379] RFC4379 (2006–02), Detecting Multi-Protocol Label Switched (MPLS) Data Plane

Failures

This chapter provides CLI examples for configuring LSP ping and LSP traceroute

The following are examples of the LSP ping command syntax with the options that are supported

Please always refer to 8600 Smart Routers CLI Commands Manual for the latest information on

available options:

mpls ping rsvp {name rsvp name {primary | secondary} | bypass rsvp name} [destination

dest–ip–address] [source source-ip-address] [ttl ttl] [qos {ef | cs7 | af11 | af12 | af13 | af21 | af22 |

af23 | af31 | af32 | af33 | af41 | af42 | af43 | be}] [timeout timeout] [packets packets] [interval

interval] [reply-mode ipv4] [size size] [copy-pad-tlv] [summary-only] [no-verify] [reply-qos {ef

| cs7 | af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be}]

mpls ping pwe3 {name pwe3–name | interface ifname} [destination dest-ip-address ] [source

source-ip-address] [ttl ttl] [qos {ef | cs7 | af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 |

af41 | af42 | af43 | be}] [timeout timeout] [packets packets] [interval interval] [reply-mode app-ch] [size size] [copy-pad-tlv] [summary-only] [no-verify] [reply-qos {ef | cs7 | af11 |

af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be}] [pwe3–destination

pwe3–dest-address] [pwe3–source pwe3–source-address]

mpls ping ldp A.B.C.D/M [destination dest-ip-address ] [source source-ip-address] [ttl ttl] [qos

{ef | cs7 | af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be}] [timeout

timeout] [packets packets] [interval interval] [reply-mode app-ch] [size size] [copy-pad-tlv]

[summary-only] [no-verify]

mpls ping bgp ipv4 labeled-unicast A.B.C.D/M [out-interface if-name ] [destination

dest-ip-address ] [source source-ip-address] [ttl ttl] [qos {ef | cs7 | af11 | af12 | af13 | af21 | af22 |

af23 | af31 | af32 | af33 | af41 | af42 | af43 | be}] [timeout timeout] [packets packets] [interval

interval] [reply-mode app-ch] [size size] [copy-pad-tlv] [summary-only] [no-verify] [reply-qos

{ef | cs7 | af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be}]

mpls ping vpls-mesh vsi-name A.B.C.D [destination dest-ip-address ] [source source-ip-address] [ttl ttl] [qos {ef | cs7 | af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be}[timeout timeout] [packets packets] [interval interval] [reply-mode app-ch] [size

size] [copy-pad-tlv] [summary-only] [no-verify] [reply-qos {ef | cs7 | af11 | af12 | af13 | af21 |

af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be}] [pwe3–destination pwe3–dest-address] [pwe3–source pwe3–source-address] ]

LSP Ping Options

copy-pad-tlv If copy-pad-tlv is given then the value of

the first octet of Pad TLV, if there is a PadTLV (see the description of size), shall be2

Value of the firstoctet is 1 (DropPad TLV)

no-verify Do not require FEC stack validation If no-verify is

not given thenthe target router

is required toverify the FECstack (the Vflag as defined

in [RFC4379] is

Parameter Description Range Default reply-mode The Reply Mode field in the MPLS header,

see [RFC4379] section 3

NOTE: “Do not reply” and “Reply… withRouter Alert” will not be supported!

RSVP: ipv4,PWE3: app-ch

only If summary-only is given then the resultsof each ping packet are not displayed, but

summary-only the summary

If summary-only

is not given thenthe results of eachping packet aredisplayed

vpls-mesh VPLS mesh peer circuit AnyLegalAddress A.B.C.D VPLS peer IP address

A.B.C.D/M FEC (Forwarding Equivalence Class) to

use in forwarding It is important to realizethat A.B.C.D/M is NOT IP address it isprefix identifying specific IPv4 FEC (that

is, net mask is mandatory) Each LDPLSP is identified by FEC These FECscorrespond to LDP FTN entries (and to a

some degree with what the show ldp fec

command displays However, only some of

the "show ldp fec" entries are programmed

to FTN table, and those correspond to realLSPs that are pinggable

Any valid FEC

if-name Name of interface to be used for outgoing

BGP multipath messages anyLegalInter- faceName

RSVP or bypass tunnel

address IP address of remote Provider Edge of thisPWE3 circuit Address is used for FEC

pwe3-dest-validation

Any IP address of PWE3 end point Address of PWE3endpoint from

local database

PWE3 tunnel pwe3-source-

address PWE3 sender’s PE address Address isused for FEC validation Address of this node

Router ID

address Source address in IP header Any existing local IP address

source-ip-For RSVP:

an outgoinginterface IPaddress, or ifnone found,router IDFor PWE3:router ID

Parameter Description Range Default

interval The interval [milliseconds] at which the

MPLS echo requests shall be sent 100 10000 ms 1000

size The desired length of the IP packet

containing an MPLS echo request Theactual packet length will be the smallestpossible length greater or equal to size,given that the packet must contain someTLV(s) such as the FEC stack, and willcontain a Pad TLV of 8+4n bytes if thelength would otherwise be smaller thansize

64 1500 bytes 64

vsi-name Name of bridge the mesh peer is attached

The following are examples of the LSP traceroute command syntax with the options that are

supported Please always refer to 8600 Smart Routers CLI Commands Manual for the latest

information on available options:

mpls traceroute rsvp {name rsvp-name {primary | secondary } | bypass rsvp-name} [destination

dest–ip–address] [source source-ip-address] [max-ttl max-ttl] [qos {ef | cs7 | af11 | af12 | af13 |

af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be}] [timeout timeout] [reply-mode

ipv4] [detail] [no-verify] [no-dsmap]

mpls traceroute pwe3 {name pwe3–name | interface ifname [destination dest-ip-address ] [source

source-ip-address] [max-ttl max-ttl] [qos {ef | cs7 | af11 | af12 | af13 | af21 | af22 | af23 | af31 |

af32 | af33 | af41 | af42 | af43 | be}] [timeout timeout] [reply-mode app-ch] [detail] [no-verify] [no-dsmap] [pwe3–destination pwe3–dest-address] [pwe3–source pwe3–source-address]} mpls traceroute ldp A.B.C.D/M [destination dest-ip-address ] [source source-ip-address] [max-ttl

max-ttl] [qos {ef | cs7 | af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 |

be}] [timeout timeout] [reply-mode ipv4] [detail]

mpls traceroute vpls-mesh vsi-name A.B.C.D [destination dest-ip-address ] [source

source-ip-address] [max-ttl max-ttl] [timeout timeout [qos {ef | cs7 | af11 | af12 | af13 | af21 | af22 |

af23 | af31 | af32 | af33 | af41 | af42 | af43 | be}] ] [reply-mode app-ch] [detail] [no-verify]

[no-dsmap] [pwe3–destination pwe3–dest-address] [pwe3–source pwe3–source-address]

mpls traceroute bgp ipv4 labeled-unicast A.B.C.D/M [out-interface if-name ] [destination

dest-ip-address ] [source source-ip-address] [max-ttl max-ttl] [qos {ef | cs7 | af11 | af12 | af13 |

af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be}] [timeout timeout] [reply-mode

app-ch] [detail] [no-verify] [no-dsmap | no-dsmap-verify]

LSP Traceroute Options

Parameter Description Range Default reply-mode MPLS echo reply mode.

ipv4 Reply via an IPv4 UDP packet

no-verify Do not require FEC stack validation

no-dsmap Do not send DSMAP TLV

nation PWE3 remote PE address for FECvalidation

pwe3–desti-pwe3–source PWE3 sender's PE address for FEC

validation

vpls-mesh Automatic VPLS mesh circuit

A.B.C.D Mesh peer destination address

A.B.C.D/M Forwarding equivalence class Used

for ping forwarding instead of tunnel orpseudowire

Any legal IPV4 address prefix Each LDP LSP

is identified

by FEC.

These FECs correspond

to LDP FTN entries.

address

dest-ip-Destination address in IP header 127.x.x.x 127.0.0.1

if-name Name of interface to be used for outgoing

BGP multipath messages

terfaceName pwe3–dest-

anyLegalIn-address

PWE3 destination IP address for FECvalidation

Known address of the other end node.

PWE3 address fromlocal database

address PWE3 sender’s PE address. Sender’s valid node

pwe3–source-address.

Router ID

address Source address in IP header. Any existing local IP

source-ip-address.

For RSVP: anoutgoing interface

IP address, or if nonefound, router IDFor PWE3: router ID

RSVP or bypass tunnel.

PWE3 circuit.

AnyExisting-2.2.1 RSVP LSP Connectivity Test

An application example of connectivity test using LSP ping is depicted in the following figure

Fig 3 LSP Ping Topology

The following example shows the results of connectivity test using LSP ping and traceroute Foradvanced tests, please refer toLSP Ping OptionsandLSP Traceroute Optionsfor a complete list ofthe options permitted for LSP ping and traceroute

2.2.2 PWE3 Connectivity Test

Fig 5 PWE3 Ping and Traceroute

PWE3 ping and traceroute use VCCV functionality Thus, an optional control-word has to beenabled for the PWE3 and also VCCV must be configured The details on how to configureVCCV are explained in4.3 VCCV Configuration Examples A connectivity test for MS-PWE3with LSP ping and traceroute is covered in4.3.3 MS-PWE3 VCCV LSP Ping and TracerouteConfiguration The following example shows the results of connectivity test for a SS-PWE3 usingPWE3 ping and traceroute

Fig 6 PWE3 Ping and Traceroute Commands Execution

2.2.3 LDP Connectivity Test

Fig 7 LDP Ping and Traceroute

The following example shows the results of connectivity test using LDP ping and trace route.Possible FEC:s can be found for example from FTN table The LDP entries with IPV4 FEC arevalid For advanced tests, please refer toLSP Ping OptionsandLSP Traceroute Optionsfor acomplete list of the options permitted for LDP ping and traceroute

2.2.4 Interrupting Connectivity Tests

8000 Intelligent Network Manager or CLI users may execute a very long running LSP ping ortraceroute tests Whenever it is desired to interrupt these tests, but without access to 8000 IntelligentNetwork Manager or to the original console where the test is running, the following commandsmay be used:

show mpls ping instances show mpls traceroute instances clear mpls ping instance

clear mpls traceroute instance

The running LSP ping or traceroute can also be interrupted from the console, where it was started

by pressing the key Ctrl-C In 8630 Smart Router and 8660 Smart Router CDC switchover willautomatically interrupt any running LSP ping or traceroute tests

3 Packet Loop Test

3.1.1 Introduction

Packet Loop Test (PLT) is a special tool in 8600 system The 8600 NEs contain specialized hardwarethat is capable of generating test packets among ordinary traffic and also intercepting such packetsfor traffic analysis purposes The PLT test packets do not interfere with ordinary end-to-end traffic,except that they consume some share of network bandwidth On the other hand, test packets behave

as ordinary traffic in the middle of the test path, and so test packet flow reveals useful informationabout real traffic behavior The word 'loop' is included in the name because some tests loop a testpacket flow back to the origin of the packet flow

The properties of the test packet flow are configurable by the user, for example:

• Size distribution of packets

in presence of IP VPN routing A customer is advised to use 8000 Intelligent Network Manager totake care of PLT details Please see3.1.7 IP Addresses Configuration for PLTfor more information

on CLI configuration examples of PLT tests

PLT tests employ IP packets, which can, by nature of IP networks, be fragmented along the path if some links have low MTU (maximum packet size) PLT test hardware cannot intercept test packets properly if the network has fragmented them For this reason, the user shall configure the size distribution of the test packets so that no test packet needs fragmentation