Hi,

It is a good topic for a discussion.
If you reset all the sessions the box becomes completely disconnected from the 
core (as most likely the same amount of routes will be advertised by both RRs 
(clusters)).
If just warning is issued the box remains alive but there might be some 
unexpected states of memory rendering it unusable anyways (all kinds of weired 
issues can happen if the mem is exhausted be it just for a short interval).
However if a config mistake happens and one of the RRs (or clusters for that 
matter) starts advertising excess routes then it would be desired to reset the 
affected session(s) in which case the box remains perfectly operational using 
the sessions to remaining RRs.

In any case you should be closely monitoring the syslog messages related to 
crossing the 70% watermark so that you know you are approaching the memory 
limits of the box and there's a need to migrate some of the VRFs to other boxes 
or to add another ME to the POP.

 
adam
> -----Original Message-----
> From: cisco-nsp [mailto:[email protected]] On Behalf Of
> CiscoNSP List
> Sent: 05 March 2015 08:26
> To: [email protected]
> Subject: [c-nsp] ME3600 iBGP to RR
> 
> Hi Everyone,
> 
> Using ME3600's to terminate customer tails (VRF's and Inet), and am after
> some recommendations on a template for the RR-Client->RR
> session..ME3600 only supports 20K IPv4 routes so was going to implement
> something like:
> 
>  template peer-policy TO_RR_iBGP
>   next-hop-self
>   soft-reconfiguration inbound
>   maximum-prefix 20000 70
>   send-community both
>  exit-peer-policy
> 
> address-family ipv4
>   neighbor xxx.xxx.xxx.xxx inherit peer-policy TO_RR_iBGP
> 
> plus route-maps controlling in/out prefixes
> 
> Any other suggestions (i.e. resetting bgp session if certain threshold is hit,
> then re-establishing session after x minutes, or being more frugal on number
> of routes allowed etc) are greatly appreciated.
> 
> Cheers.
> 
> _______________________________________________
> cisco-nsp mailing list  [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
---------------------------------------------------------------------------------------
 This email has been scanned for email related threats and delivered safely by 
Mimecast.
 For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------

_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to