Not sure if this will show up since it was marked solved,
But, i had another question related to this.
If i have both wide-metrics-only enabled, as well as traffic-engineering disabled,
This is suppost to supress tlvs 2,22,128,134,135 from being sent.
The documentation says it will basically be a loss of isis routing information for that level.
Since i configured it on both level 1 and level 2 i shouldn't see those tlvs, or supposidly anything.
Now, i do not see any routing information under the protocol isis, both the ipv4 and ipv6 table is blank.
But, if i monitor traffic on the downstream router, i still see advertisements for the ipv6 interfaces as well as the tag that is set on the export policy as seen below.
IPv6 prefix: 2001:db9::1:2/127 Metric 10 Up
IPv6 prefix: 2001:db9::1:4/127 Metric 10 Up
IPv6 prefix: 2001:db9::1:0/127 Metric 10 Up
IPv6 prefix: 2001:db9::1:6/127 Metric 10 Up
IPv6 prefix: 2001:db9::1:8/127 Metric 10 Up
IPv6 prefix: 2001:db8::/128 Metric 0 Up
6 bytes of subtlvs
Administrative tag 1: 200
IPv6 reachability TLV #236, length: 139
IPv6 prefix: 2001:db9::1:2/127, Distribution: up, Metric: 10, Internal
IPv6 prefix: 2001:db9::1:4/127, Distribution: up, Metric: 10, Internal
IPv6 prefix: 2001:db9::1:0/127, Distribution: up, Metric: 10, Internal
IPv6 prefix: 2001:db9::1:6/127, Distribution: up, Metric: 10, Internal
IPv6 prefix: 2001:db9::1:8/127, Distribution: up, Metric: 10, Internal
IPv6 prefix: 2001:db8::/128, Distribution: up, Metric: 0, Internal, sub-TLVs present (6)
32-Bit Administrative tag subTLV #1, length: 4, 0x000000c8 (=200)
Does this make sence, or maybe its a bug in junosphere? Or am i missing a small detail somewhere?