[BGPCEP-273] The "net" IS-IS node attribute is not filled by BGP-LS topo provider Created: 25/Aug/15  Updated: 03/Mar/19  Resolved: 30/Sep/15

Status: Resolved
Project: bgpcep
Component/s: BGP
Affects Version/s: Bugzilla Migration
Fix Version/s: Bugzilla Migration

Type: Improvement
Reporter: Giles Heron Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All



 Description   

In the OSPF case the link-state node-id includes the field "area=xxx"

There is no such field in the IS-IS case.

The IS-IS link-state route does, however, contain an area ID.

Area IDs have a slightly different meaning in OSPF and ISIS. However:

1) without an area-id we can't support the multi-area case where one L1L2 router subtends multiple L1 areas.

2) if we add this we will also be able to support the multi-process case where there are multiple L1s or L2s on the same router (since each L1 or L2 will have a different area ID).



 Comments   
Comment by Milos Fabian [ 28/Sep/15 ]

In a case of link-state IS-IS node attribute, the area-id attribute is not exported in IS-IS topology. Fix BGP-LS topology provider to fill in this attribute as a "net" (iso-net-id).

Comment by Milos Fabian [ 29/Sep/15 ]

Be: https://git.opendaylight.org/gerrit/#/c/27526
Li: https://git.opendaylight.org/gerrit/#/c/27607

Generated at Wed Feb 07 19:12:33 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.