Interesting, i had seen different behavior before and had this jotted down in my notes.
I'll re-verify this if this has to do something with the IOS code i was using. Thanks for correcting me. Swap #19804 On Mon, May 31, 2010 at 7:36 AM, William McCall <[email protected]> wrote: > All: > > Solution works like this and was confirmed by OP: > > Enabling the IS-IS process for CLNS on the interface allowed the > propagation of the CLNS route to the neighbor. After this, the > attached bit could be set per the route map. > > So on R5's FR int, all that is necessary is to put "clns router isis". > > As a side note, I tested another poster's theory regarding the setting > of the ATT bit when performing multiarea IS-IS and found that the L1 > areas do, in fact, receive the ATT bit even when the area with the L2 > adjacency and the one with the L1 adjacency is different. Also > confirmed that the set-attached-bit feature works under those L1 > areas. > > HTH > > -- > William McCall, CCIE #25044 > > On Sun, May 30, 2010 at 8:04 AM, selamat pagi <[email protected]> wrote: >> Hi, >> >> In my lab setup I have 3 routers connected via IS-IS >> R4 --(frame-relay) R5 --(ethernet) - R6 >> >> On R5 I have to areas, connected, however I only want to >> originate the default-route to R6 when R4 is reachable. >> I tried to use a the set-attached-bit route-map with clns filter-set, but I >> cannot control the default route as desired. >> >> Any idea how this can be solved ? >> >> thanks, ketimun >> >> *R4* >> router isis 4 >> net 49.4444.1500.0100.1001.00 >> log-adjacency-changes >> >> *R5* >> router isis 5 >> net 49.0004.1500.0100.5005.00 >> set-attached-bit route-map REAL_L2 >> log-adjacency-changes >> ! >> router isis 55 >> net 49.5555.1500.0100.5005.00 >> is-type level-1 >> >> route-map REAL_L2 permit 10 >> match clns address R4 >> >> clns filter-set R4 permit 49.4444 --> * This route is not int the clns >> route table* >> >> *R6* >> router isis 6 >> net 49.0004.1500.0100.6006.00 >> is-type level-1 >> log-adjacency-changes >> >> >> >> *R5#sh clns route* >> Codes: C - connected, S - static, d - DecnetIV >> I - ISO-IGRP, i - IS-IS, e - ES-IS >> B - BGP, b - eBGP-neighbor >> >> C 49.5555 [2/0], Local IS-IS Area >> C 49.0004 [2/0], Local IS-IS Area >> C 49.5555.1500.0100.5005.00 [1/0], Local IS-IS NET >> C 49.0004.1500.0100.5005.00 [1/0], Local IS-IS NET >> >> >> >> * >> R5#sh isis data* >> >> Area 5: >> IS-IS Level-1 Link State Database: >> LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL >> R5.00-00 * 0x00000034 0x8DB7 1153 1/0/0 >> R6.00-00 0x00000011 0xB008 1000 0/0/0 >> R6.02-00 0x0000000F 0x469E 1016 0/0/0 >> IS-IS Level-2 Link State Database: >> LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL >> R4.00-00 0x00000016 0xC0CE 1169 0/0/0 >> R4.02-00 0x00000006 0xBA97 1085 0/0/0 >> R2.00-00 0x0000001C 0x6859 693 0/0/0 >> R5.00-00 * 0x0000000D 0x3212 1171 0/0/0 >> R5.03-00 * 0x00000003 0x38A4 498 0/0/0 >> >> Area 55: >> IS-IS Level-1 Link State Database: >> LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL >> R5.00-00 * 0x00000001 0xD2A3 495 1/0/0 >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
