Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Tracing VPLS Traffic and Operations

date_range 23-Nov-23

To trace VPLS traffic, include the traceoptions statement:

content_copy zoom_out_map
traceoptions {
    file filename <files number> <size size> <world-readable | no-world-readable>;
    flag flag <flag-modifier> <disable>;
}

You can include this statement at the following hierarchy levels:

  • [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls]

  • [edit routing-instances routing-instance-name protocols vpls]

The following trace flags display the operations associated with VPLS:

  • all—All VPLS tracing options

  • connections—VPLS connections (events and state changes)

  • error—Error conditions

  • nlri—VPLS advertisements received or sent using BGP

  • route—Trace-routing information

  • topology—VPLS topology changes caused by reconsideration or advertisements received from other PE routers using BGP

footer-navigation