From: Paresh Khatri (Paresh.Khatri@aapt.com.au)
Date: Mon Dec 12 2005 - 07:39:27 GMT-3
Actually Arun, I still think my initial post was correct...the command reference for this feature indicates that the route-map can only be used for matching on CLNS routes, and not IP routes.
Here's a quote from it:
"The route map can specify one or more CLNS routes. If at least one of the match address route-map clauses matches a route in the L2 CLNS routing table, and if all other requirements for setting the attached-bit are met, the L1L2 router will continue to set the attached-bit in its L1 LSP. If the requirements are not met or no match address route-map clauses match a route in the L2 CLNS routing table, the attached-bit will not be set."
Regards,
Paresh.
-----Original Message-----
From: Arun Arumuganainar [mailto:aarumuga@hotmail.com]
Sent: Mon 12/12/2005 9:16 PM
To: Andrew Lissitz (alissitz); Paresh Khatri; comserv@groupstudy.com; ccielab@groupstudy.com
Cc:
Subject: Re: ISIS - set-attached-bit and set-overload-bit
Hi Andrew ,
Paresh is almost correct .We do not have full flexibility for setting the
ATT bit .
But times are changing and features gets added up !!! Check this out !!!
This is one of the feature that are used to optimize L1-Routing . After
introduction of this feature , network admins can influence ATT bit setting
using "ser-attached-bit Route-map " command .
FYI : You should be using 12.2(4)T or Later ..
Pls. refer to the CCO Link
http://www.cisco.com/en/US/products/ps6599/products_white_paper09186a00804fa
7a0.shtml
or In case you have access Cisco Bug tracking tool . You can also check out
Bug ID : CSCdp64489 .
Pls. Note : Even after this feature we can arbitarly set att bit in IOS .
Your L1/L2 router still need to have visibility to atleast one area other
than its own !!!
Thanks and Regards
Arun
----- Original Message -----
From: "Andrew Lissitz (alissitz)" <alissitz@cisco.com>
To: "Paresh Khatri" <Paresh.Khatri@aapt.com.au>; <comserv@groupstudy.com>;
<ccielab@groupstudy.com>
Sent: Thursday, December 08, 2005 10:56 AM
Subject: RE: ISIS - set-attached-bit and set-overload-bit
> Paresh you rock! I am going to try this now, thanks
>
>
> -----Original Message-----
> From: Paresh Khatri [mailto:Paresh.Khatri@aapt.com.au]
> Sent: Thursday, December 08, 2005 12:23 AM
> To: Andrew Lissitz (alissitz); comserv@groupstudy.com;
ccielab@groupstudy.com
> Subject: RE: ISIS - set-attached-bit and set-overload-bit
>
> Hi Andrew,
>
> I don't believe that you can use the 'set-attached-bit' command when using
ISIS for routing IP; while the ATT bit is also used by IP, you can only set
it via this command when routing CLNS via ISIS.
>
> As for the second command, one possible way a question could require you
to use this is: configure your interior routers so that they do not
advertise themselves as available for transit routing until BGP has
converged on these routers. Or: configure your interior routers so that
they do advertise themselves as available for transit routing until 2
minutes after the IGP routing process has started.
>
> Here's my little summary of how you can use the set-overload-bit command:
>
> set-overload-bit
> ' immediately and unconditionally sets the overload bit
>
> set-overload-bit on-startup <seconds>
> ' sets the overload bit on startup for the specified number of seconds
(from 5 to 86400)
>
> set-overload-bit on-startup <seconds> suppress interlevel
> ' sets the overload bit on startup for the specified number of seconds
(from 5 to 86400). Suppresses advertisement of any inter-level routes while
the overload bit is set.
>
> set-overload-bit on-startup <seconds> suppress external
> ' sets the overload bit on startup for the specified number of seconds
(from 5 to 86400). Suppresses advertisement of any redistributed routes
while the overload bit is set.
>
> set-overload-bit on-startup <seconds> suppress interlevel external
> ' sets the overload bit on startup for the specified number of seconds
(from 5 to 86400). Suppresses advertisement of any inter-level or external
routes while the overload bit is set.
>
> set-overload-bit on-startup wait-for-bgp
> ' sets the overload bit on startup. It's cleared on receiving a signal
from BGP or after 10 minutes, whichever comes first.
>
> set-overload-bit on-startup wait-for-bgp suppress interlevel
> ' sets the overload bit on startup. It's cleared on receiving a signal
from BGP or after 10 minutes, whichever comes first. Suppresses
advertisement of any inter-level routes while the overload bit is set.
>
> set-overload-bit on-startup wait-for-bgp suppress external
> ' sets the overload bit on startup. It's cleared on receiving a signal
from BGP or after 10 minutes, whichever comes first. Suppresses
advertisement of any redistributed routes while the overload bit is set.
>
> set-overload-bit on-startup wait-for-bgp suppress interlevel external
> ' sets the overload bit on startup. It's cleared on receiving a signal
from BGP or after 10 minutes, whichever comes first. Suppresses
advertisement of any inter-level or external routes while the overload bit
is set.
>
> set-overload-bit suppress interlevel
> ' immediately and unconditionally sets the overload bit. Suppresses
advertisement of any inter-level routes while the overload bit is set.
>
> set-overload-bit suppress external
> ' immediately and unconditionally sets the overload bit. Suppresses
advertisement of any external routes while the overload bit is set.
>
> set-overload-bit suppress interlevel external
> ' immediately and unconditionally sets the overload bit. Suppresses
advertisement of any inter-level or redistributed routes while the overload
bit is set.
>
> HTH,
> Paresh.
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Andrew Lissitz (alissitz)
> Sent: Thursday, 08 December 2005 03:01 PM
> To: comserv@groupstudy.com; ccielab@groupstudy.com
> Subject: ISIS - set-attached-bit and set-overload-bit
>
>
> Hello group,
>
> I am trying to think of a scenario / question that may cause me to think
of this feature.
>
> pe1(config)#router isis
> pe1(config-router)#?
> set-attached-bit Conditionally advertise us as attached to L2
> set-overload-bit Signal other routers not to use us in SPF
> pe1(config-router)#
>
> My lab:
>
> R1 <---> R2 (My lab follows the 'KISS' design guide)
>
> Has anyone used these features and or can think of a question / scenario
that would cause me to look at this feature for the solution. I am really
trying to think of how a question / scenario could be written.
> Kindest regards group,
>
> Andrew
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> This communication, including any attachments, is confidential. If you are
not the intended recipient, you should not read it - please contact me
immediately, destroy it, and do not copy or use any part of this
communication or disclose anything about it.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _____________________________________________________________________
> Subscription information: http://www.groupstudy.com/list/comserv.html
>
This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it.
This archive was generated by hypermail 2.1.4 : Mon Jan 09 2006 - 07:07:51 GMT-3