# IS-IS Metric on Cisco IOS

**URL:** <https://forum.networklessons.com/t/is-is-metric-on-cisco-ios/1751>\
**Category:** Lessons Discussion\
**Created:** [May 24, 2017, 2:21pm UTC](https://forum.networklessons.com/t/is-is-metric-on-cisco-ios/1751 "2017-05-24T14:21:47Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![davidilles](https://cdn-forum.networklessons.com/user_avatar/forum.networklessons.com/davidilles/32/9686_2.png) [@davidilles](https://forum.networklessons.com/u/davidilles)\
**Post date:** [January 7, 2026, 12:33pm UTC](https://forum.networklessons.com/t/is-is-metric-on-cisco-ios/1751/4 "2026-01-07T12:33:53Z")

</div>

Hello, everyone.

I found something weird when labbing and I would like to confirm this. If I configure this NSAP address on one of my XE routers - `net 0002.3333.3333.3333.00`. It will advertise its Area Address like this:

![obrázok]()

I believe the IOS moves the first two zeroes that I have configured into the AFI part (since NET addresses start with XX.XXXX …).

![obrázok]()

If I configure this NSAP address on one of my neighboring XR routers - `net 0002.4444.4444.4444.00`. It will advertise its Area Address like this:

![obrázok]()

It like completely ignores the first two zeroes and moves the **02** instead into the AFI part.

![obrázok]()

My routers would not establish an L1 adjacency because of this. Is this normal behaviour? Like does XR just refuse to use 00.xxxx unless I manually tell it to?

My other question is, is it possible to fix this without completely changing the area address? It’s impossible with XR to configure the area address as `00.02`. If I do that, it just converts the 02 into 0002.

![obrázok]()

![obrázok]()

Thank you  
David

---

_[View the full topic](https://forum.networklessons.com/t/is-is-metric-on-cisco-ios/1751)._