[c-nsp] ASR9k Too Frequent Update on Rancid

[Thong Hawk Yen]

Hi Andrew,

Thanks for your feedback.

Regards
Amos

-----------------------------------

Andrew Jones aj at jonesy.com.au <mailto:cisco-nsp%40puck.nether.net?Subject=Re%3A%20%5Bc-nsp%5D%20ASR9k%20Too%20Frequent%20Update%20on%20Rancid&In-Reply-To=%3Cb611a3b8a63b77a6edb9356c2d5935f0%40jonesy.com.au%3E>
Fri May 3 01:08:20 EDT 2013

  *   Previous message: [c-nsp] ASR9k Too Frequent Update on Rancid <https://puck.nether.net/pipermail/cisco-nsp/2013-May/091002.html>
  *   Next message: [c-nsp] ME3600 Configuration advice <https://puck.nether.net/pipermail/cisco-nsp/2013-May/091006.html>
  *   Messages sorted by: [ date ]<https://puck.nether.net/pipermail/cisco-nsp/2013-May/date.html#91005> [ thread ]<https://puck.nether.net/pipermail/cisco-nsp/2013-May/thread.html#91005> [ subject ]<https://puck.nether.net/pipermail/cisco-nsp/2013-May/subject.html#91005> [ author ]<https://puck.nether.net/pipermail/cisco-nsp/2013-May/author.html#91005>

________________________________

On 03.05.2013 03:11, A.L.M.Buxey at lboro.ac.uk<https://puck.nether.net/mailman/listinfo/cisco-nsp> wrote:

> Hi,

>

>> We have recently added a new ASR9k into the nerwork.  Prior to this

>> we have other routers running IOS XR namely CRS.

>> Being IOS XR the config in Rancid are the same for the CRS and also

>> the ASR9k, however the ASR9k has been "chatty" reporting changes as

>> shown below but not the CRS. Is this a common among the ASR9k or our

>> Rancid config is need some tweaking ? Any experience to rectify this ?

>

> we had a similar thing with our ASAs and an file stored on its disk -

> the file keeps

> being updated...so RANCID reports a change. we fixed this by adding

> another ignore into

> the code/script - you'll find the section relavent for you and

> similar ignore statements.



Yes, I'd look for this section in "xrrancid" in the bin directory, and

add some similar sections for the files you're seeing changed.



if ($proc =~ /ASR9K/ && /dlbg\.txt/) {

             next;

}






________________________________

CONFIDENTIALITY
-------------------------
The contents of and any attachments to this email are private and confidential. If you are not the intended recipient or addressee indicated in this message, please notify the sender of the error and destroy the email and any attachments. Please do not reproduce the contents of the email or its attachments as such reproduction is a breach of confidentiality and for which legal action including injunctive relief may be sought against you. If it is your company policy that official communications are not by email, please advise immediately. Any opinions, conclusions and other information in this message that do not relate to the official business of TIME dotCom shall be understood as neither given nor endorsed by TIME dotCom, nor shall TIME dotCom shall be liable (directly or vicariously) for such opinions, statements or communications.