MPLS-TE with OSPF Inter-Area
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-19-2016 05:51 AM
I have a problem MPLS-TE with OSPF Inter-Area. Any one can share this problem? Is it support MPLS-TE with Multi-Area?
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-19-2016 12:58 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-19-2016 08:18 AM
If the lsp starts in one ospf area and finishes in a different one there is a bug. Bug is fixed in 21.1 and 16.2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-19-2016 08:18 AM
Hi Grosjean,
Thanks for your answer. We are not using RSVP-TE profiles. We create RSVP-TE path and just add to RSVP-TE lsp. RSVP-TE profiles didn't work with previous firmware 15.x.x versions and we get rid of using RSVP-TE profiles in our deployment.
Thanks for your answer. We are not using RSVP-TE profiles. We create RSVP-TE path and just add to RSVP-TE lsp. RSVP-TE profiles didn't work with previous firmware 15.x.x versions and we get rid of using RSVP-TE profiles in our deployment.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-19-2016 08:18 AM
just checking, did you look at 16.2 User Guide to see how the enhancement to allow path computation across areas works? Look at page 1265
Starting with ExtremeXOS 16.2, the path-computation keyword specifies computation strategy for calculating a path to the LSP destination. "full" requires the ingress node to full calculate a path to the LSP destination. "partial" allows the ingress node to calculate only part of the path to the LSP destination. In this case, it would be to the ABR, and the ABR would calculate the rest of the way (into the other area).
by default the setting is "full".
Starting with ExtremeXOS 16.2, the path-computation keyword specifies computation strategy for calculating a path to the LSP destination. "full" requires the ingress node to full calculate a path to the LSP destination. "partial" allows the ingress node to calculate only part of the path to the LSP destination. In this case, it would be to the ABR, and the ABR would calculate the rest of the way (into the other area).
by default the setting is "full".
