[c-nsp] ISIS Route Flapping Issue

[David Jacobs]

Hello Peter, thank you for your reply, I changed my NET address back to the
original and reloaded and I tried to dig up more data on this
FYI This is what my config looks like on this box.
router isis
 net 49.0001.0001.5011.1565.00
 is-type level-2-only
 metric-style wide
 spf-interval 30
 log-adjacency-changes
 redistribute connected
 redistribute static ip


>
> >What did the box itself have in its routing table at this time? How does
> >the box lift the host prefix into IS-IS? Does a "debug isis rib
> >resdistribution" give any clues?
>

Here is a summary of what is in the routing table now...

router1#sh ip route summary
IP routing table name is Default-IP-Routing-Table(0)
Route Source    Networks    Subnets     Overhead    Memory (bytes)
connected       0           4           256         608
static          1           6           448         1064
isis            144         6179        732864      961096
  Level 1: 0 Level 2: 6323

"debug isis rib redis" doesnt seem to lend any clues unfortunately.  I did
find something odd, although

When I did a "sh clns interface"   I am seeing the "circuit ID:" of the
neighboring core routers in the Circuit ID field

GigabitEthernet5/0/0 is up, line protocol is up
    Level-2 Metric: 99999, Priority: 64, Circuit ID: Name of Neighboring
Router1

 GigabitEthernet6/0/0 is up, line protocol is up
    Level-2 Metric: 99999, Priority: 64, Circuit ID: Name of Neighboring
Router2

but when I do this from all other routers, the Circuit ID is the local
hostname of the router. Not sure if that has anything to do with it or not.


When I do a "sh spf-log" this is the message I keep seeing

On Cisco

00:24:50      72    109      8      router1.00-00  TLVCONTENT
00:24:20      72    109      8      router1.00-00  TLVCONTENT
00:23:50      76    109      8      router1.00-00  TLVCONTENT
00:23:20      64    109      8      router1.00-00  TLVCONTENT
00:22:50      76    109      8      router1.00-00  TLVCONTENT
00:22:20      72    109      8      router1.00-00  TLVCONTENT
00:21:50      72    109      8      router1.00-00  TLVCONTENT
00:21:20      72    109      8      router1.00-00  TLVCONTENT
00:20:50      72    109      8      router1.00-00  TLVCONTENT
00:20:19      72    108      7      router1.00-00  TLVCONTENT
00:19:49      72    108      8      router1.00-00  TLVCONTENT
00:19:19      68    108      8      router1.00-00  TLVCONTENT

and on Foundry

 1m55s    450ms    78    6     router1.00-00       Area Address TLV Change

 2m26s    450ms    39    17    router1.00-00      Area Address TLV Change

 2m56s    450ms    39    17    router1.00-00      Area Address TLV Change

 3m27s    450ms    39    13    router1.00-00      Area Address TLV Change

 3m57s    450ms    39    18    router1.00-00      Area Address TLV Change



>
>
> >Brand new 7500 hardware? Where? ;-)


By new I mean just purchased from somewhere, right out of the box in that
new (never been crinkled) static wrap and never used by us before =)

>
>
>
> >A shot in the dark, but you wouldn't happen to have another box with the
> >same NET on your network?
>
> I thought of that as well, But I compared all of the other NET address's
> and they are pretty unique. And correct me if i'm wrong, but if there was
> another router running ISIS with the same NET address wouldn't it come up
> with an error like..


%CLNS-4-BADPACKET: ISIS: LAN L2 hello, Duplicate system
ID detected from (duplicate NET address)

I forget if there is a command to view all NET address's in the database

Thanks again for all of the help