Knowledge Search


×
 

[MX] Traceoptions on Dynamic LSPs do not start for existing LSP

  [KB32638] Show Article Properties


Summary:

If configuring traceoptions directly under a dynamic LSP (for example LSP template for provider tunnels w/MVPN), traceoptions will not start until that LSP is torn down and re-created.  

Symptoms:

If you have a dynamic LSP template under protocols -> mpls, and add traceoptions under the specific LSP, traceoptions are not logged for existing LSPs.  

user@router show configuration protocols mpls
label-switched-path dynamic_lsp_template {
    traceoptions {
        file LSP_TRACEOPTIONS_EXAMPLE
        flag all;
    }
    template;
    p2mp;
}

After committing traceoptions to the dynamic LSP template, you will not see entries for any currently existing LSPs.  If a new LSP is created, that LSP will start logging to the traceoptions file. 

Solution:

To get traceoptions from existing dynamic LSPs, traceoptions need to be configured under just protocols mpls and not the individual LSP. 

user@router show configuration protocols mpls​
traceoptions {
        file LSP_TRACEOPTIONS_EXAMPLE
        flag all;
    }
Related Links: