[rancid] Rancid Reports Config Changes when none have taken place

[Shane Kavanagh]

Hi all

I am having an issue with rancid reporting changes to ports in a VLAN when
no changes have taken place.

Here is an example

- !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8
- !VLAN: Fa1/0/9, Fa1/0/10,
Fa1/0/11, Fa1/0/12, Fa1/0/13, Fa1/0/15
- !VLAN: Fa1/0/16, Gi1/0/2
+ !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8, Fa1/0/9, Fa1/0/10, Fa1/0/11,
Fa1/0/12, Fa1/0/13, Fa1/0/15, Fa1/0/16, Gi1/0/2

note that when rancid stores the information id broke it up onto 3 lines and
when it retrieves the config again it has it on one line. This does not
happen every time it retrieves the config.

Any Ideas or suggestions welcome.

Regards

Shane Kavanagh

[Shane Kavanagh]

Hi, Jose

Thanks for the input, there seems to be no pattern to the event, unless I
run rancid-run manually then I am guaranteed to get this error. however it
seems to be from missing "," (commas) in the example below after FA 1/0/8
the cisco devices reports a comma after it but the archived version does not
have this comma but then later on I get the reverse. I wonder if its the
Cisco device going different reports, however the more I look into it, the
more I can see all my devices been affected.

- !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8, Fa1/0/9, Fa1/0/10, Fa1/0/11,
Fa1/0/12, Fa1/0/13, Fa1/0/15, Fa1/0/16, Gi1/0/2
+ !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8
+ !VLAN: Fa1/0/9, Fa1/0/10,
Fa1/0/11, Fa1/0/12, Fa1/0/13, Fa1/0/15
+ !VLAN: Fa1/0/16, Gi1/0/2

I have had this issue as well and it seems like its a false positive due to
white space. When I get these, I just discard them. How often is it
happening? If it you can deal with it, I would just leave it alone. Maybe
someone else on here has had luck dealing with this.

Post by Shane Kavanagh
Hi all
I am having an issue with rancid reporting changes to ports in a VLAN when
no changes have taken place.
Here is an example
- !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8
- !VLAN: Fa1/0/9,
Fa1/0/10, Fa1/0/11, Fa1/0/12, Fa1/0/13, Fa1/0/15
- !VLAN: Fa1/0/16, Gi1/0/2
+ !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8, Fa1/0/9, Fa1/0/10, Fa1/0/11,
Fa1/0/12, Fa1/0/13, Fa1/0/15, Fa1/0/16, Gi1/0/2
note that when rancid stores the information id broke it up onto 3 lines
and when it retrieves the config again it has it on one line. This does not
happen every time it retrieves the config.
Any Ideas or suggestions welcome.
Regards
Shane Kavanagh
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss

--
It has to start somewhere, it has to start sometime. What better place
than here? What better time than now?

[john heasley]

Post by Shane Kavanagh
Hi, Jose
Thanks for the input, there seems to be no pattern to the event, unless I
run rancid-run manually then I am guaranteed to get this error. however it
seems to be from missing "," (commas) in the example below after FA 1/0/8
the cisco devices reports a comma after it but the archived version does not
have this comma but then later on I get the reverse. I wonder if its the
Cisco device going different reports, however the more I look into it, the
more I can see all my devices been affected.
- !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8, Fa1/0/9, Fa1/0/10, Fa1/0/11,
Fa1/0/12, Fa1/0/13, Fa1/0/15, Fa1/0/16, Gi1/0/2
+ !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8
+ !VLAN: Fa1/0/9, Fa1/0/10,
Fa1/0/11, Fa1/0/12, Fa1/0/13, Fa1/0/15
+ !VLAN: Fa1/0/16, Gi1/0/2

this is the stupid cisco, not rancid. you can try this hack for that
problem.

Index: bin/clogin.in
===================================================================
--- bin/clogin.in (revision 2113)
+++ bin/clogin.in (working copy)
@@ -878,6 +880,8 @@
if [ regexp -- ".*> .*enable" "$prompt" ] {
send "set length 0\r"
expect -re $prompt {}
+ send "set width 132\r"
+ expect -re $prompt {}
send "set logging session disable\r"
} else {
send "terminal length 0\r"

Post by Shane Kavanagh

I have had this issue as well and it seems like its a false positive due to
white space. When I get these, I just discard them. How often is it
happening? If it you can deal with it, I would just leave it alone. Maybe
someone else on here has had luck dealing with this.

Post by Shane Kavanagh
Hi all
I am having an issue with rancid reporting changes to ports in a VLAN when
no changes have taken place.
Here is an example
- !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8
- !VLAN: Fa1/0/9,
Fa1/0/10, Fa1/0/11, Fa1/0/12, Fa1/0/13, Fa1/0/15
- !VLAN: Fa1/0/16, Gi1/0/2
+ !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8, Fa1/0/9, Fa1/0/10, Fa1/0/11,
Fa1/0/12, Fa1/0/13, Fa1/0/15, Fa1/0/16, Gi1/0/2
note that when rancid stores the information id broke it up onto 3 lines
and when it retrieves the config again it has it on one line. This does not
happen every time it retrieves the config.
Any Ideas or suggestions welcome.
Regards
Shane Kavanagh
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss

--
It has to start somewhere, it has to start sometime. What better place
than here? What better time than now?

_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss

[Jose Madrid]

I have had this issue as well and it seems like its a false positive due to
white space. When I get these, I just discard them. How often is it
happening? If it you can deal with it, I would just leave it alone. Maybe
someone else on here has had luck dealing with this.

Post by Shane Kavanagh
Hi all
I am having an issue with rancid reporting changes to ports in a VLAN when
no changes have taken place.
Here is an example
- !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8
- !VLAN: Fa1/0/9, Fa1/0/10,
Fa1/0/11, Fa1/0/12, Fa1/0/13, Fa1/0/15
- !VLAN: Fa1/0/16, Gi1/0/2
+ !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8, Fa1/0/9, Fa1/0/10, Fa1/0/11,
Fa1/0/12, Fa1/0/13, Fa1/0/15, Fa1/0/16, Gi1/0/2
note that when rancid stores the information id broke it up onto 3 lines
and when it retrieves the config again it has it on one line. This does not
happen every time it retrieves the config.
Any Ideas or suggestions welcome.
Regards
Shane Kavanagh
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss

[Jon Peatfield]

Post by Shane Kavanagh
Hi all
I am having an issue with rancid reporting changes to ports in a VLAN when
no changes have taken place.
Here is an example
- !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8
- !VLAN: Fa1/0/9, Fa1/0/10,
Fa1/0/11, Fa1/0/12, Fa1/0/13, Fa1/0/15
- !VLAN: Fa1/0/16, Gi1/0/2
+ !VLAN: 4 server active Fa1/0/1, Fa1/0/2,
Fa1/0/4, Fa1/0/5, Fa1/0/6, Fa1/0/7, Fa1/0/8, Fa1/0/9, Fa1/0/10, Fa1/0/11,
Fa1/0/12, Fa1/0/13, Fa1/0/15, Fa1/0/16, Gi1/0/2
note that when rancid stores the information id broke it up onto 3 lines and
when it retrieves the config again it has it on one line. This does not
happen every time it retrieves the config.
Any Ideas or suggestions welcome.

I see similar formatting differences in the output from some Cisco
switches if I run rancid-run from a terminal - since the terminal width
seems to get through to the switch and IOS tries to format the lines to
look pretty.

If I always make sure that rancid-run is run without a terminal (so no
width to get passed through) then for output doesn't change.

There are some places in the code where it tried to set terminal-width 0
(or equivalent) but as far as I can tell rancid-run uses options which
don't force that.