mktop not giving node records

[Stephen Miller]

Hey,

I am running rancid against several Juniper routers and am getting the diffs. I
have tried mktop against the groups but only get the edge records in the .top
file. At the top of the .top file there is "node:::::::" and then the edge
records. I have uncommented the node_id lines but still don't get
anything....what else should I check?

thanks,
Steve

[Joe Abley]

Post by Stephen Miller
I am running rancid against several Juniper routers and am getting the diffs. I
have tried mktop against the groups but only get the edge records in the .top
file. At the top of the .top file there is "node:::::::" and then the edge
records. I have uncommented the node_id lines but still don't get
anything....what else should I check?

How exactly did you run mktop?

[Stephen Miller]

like this:

cat /usr/local/rancid/core/configs/*.in | ./mktop > net.top

and like this:

./mktop /usr/local/rancid/core/configs/*.in > net1.top


same out output for both....

node::::::




---------- Original Message -----------
From: Joe Abley <***@isc.org>
To: "Stephen Miller" <***@smiller.org>
Cc: ***@isc.org
Sent: Wed, 23 Apr 2003 01:26:42 -0400
Subject: Re: mktop not giving node records

Post by Joe Abley

Post by Stephen Miller
I am running rancid against several Juniper routers and am getting the diffs. I
have tried mktop against the groups but only get the edge records in the .top
file. At the top of the .top file there is "node:::::::" and then the edge
records. I have uncommented the node_id lines but still don't get
anything....what else should I check?

How exactly did you run mktop?

------- End of Original Message -------

[Joe Abley]

Post by Stephen Miller
cat /usr/local/rancid/core/configs/*.in | ./mktop > net.top
./mktop /usr/local/rancid/core/configs/*.in > net1.top
same out output for both....

Mmmm. I think that files named "*.in" in the configs directory are
transient files that rancid uses while it grabs new state from the
network, and subsequently renames to their non-.in counterparts. You
may find that those files are either not always there, or you have some
stale, maybe truncated "*.in" files lying about.

Try running mktop like this and see what you get:

./mktop $(awk -F: '/:up:/ { printf
"/usr/local/rancid/core/configs/%s\n", $1; }' \
/usr/local/rancid/core/router.db) >net2.top

(if you're a csh person you'll need to use back-ticks instead of the
$() notation). That expression should spit out a list of config files
corresponding to devices in the "core" group which are up, which should
contain reasonable food for mktop.


Joe

[Stephen Miller]

actually the reason I use the *.in (.in being the TLD for the
hostnames...calccrc1.rdn.ric.net.in) is that mktop stops when it hits the CVS
directory in the configs directory and then creates and empty .top file.

tried the command and it just hung...I think it's also getting stopped by the
CVS directory but there error is not coming to the terminal.

Has the CVS directory always been in the rancid/group/ directory?

thanks,
Steve

---------- Original Message -----------
From: Joe Abley <***@isc.org>
To: "Stephen Miller" <***@smiller.org>
Cc: ***@isc.org
Sent: Wed, 23 Apr 2003 01:59:54 -0400
Subject: Re: mktop not giving node records

Post by Joe Abley

Post by Stephen Miller
cat /usr/local/rancid/core/configs/*.in | ./mktop > net.top
./mktop /usr/local/rancid/core/configs/*.in > net1.top
same out output for both....

Mmmm. I think that files named "*.in" in the configs directory are
transient files that rancid uses while it grabs new state from the
network, and subsequently renames to their non-.in counterparts. You
may find that those files are either not always there, or you have
some stale, maybe truncated "*.in" files lying about.
./mktop $(awk -F: '/:up:/ { printf
"/usr/local/rancid/core/configs/%s\n", $1; }' \
/usr/local/rancid/core/router.db) >net2.top
(if you're a csh person you'll need to use back-ticks instead of the
$() notation). That expression should spit out a list of config files
corresponding to devices in the "core" group which are up, which
should contain reasonable food for mktop.
Joe

------- End of Original Message -------

[Stephen Miller]

I made the CVS directory hidden just so I could
use ./mktop /usr/local/rancid/core/configs/* > net1.top

but no help...still getting this:

node::::::
edge:10.248.0.168/30:so-1/0/2:10.248.0.169::so-0/0/0:10.248.0.170::oc3
edge:10.248.0.136/30:so-1/0/0:10.248.0.138::so-1/0/0:10.248.0.137::oc3
edge:10.248.0.120/30:so-0/0/1:10.248.0.121::so-0/0/1:10.248.0.122::oc3
edge:10.248.0.92/30:so-0/0/0:10.248.0.93::so-1/0/2:10.248.0.94::oc3
edge:10.248.0.60/30:so-0/0/0:10.248.0.61::so-0/0/1:10.248.0.62::oc3
edge:10.248.0.164/30:so-0/0/2:10.248.0.165::so-0/0/1:10.248.0.166::oc3

I am using rancid 2.2.2 if that makes a difference....

thanks,
Steve



---------- Original Message -----------
From: Joe Abley <***@isc.org>
To: "Stephen Miller" <***@smiller.org>
Cc: ***@isc.org
Sent: Wed, 23 Apr 2003 01:59:54 -0400
Subject: Re: mktop not giving node records

Post by Joe Abley

Post by Stephen Miller
cat /usr/local/rancid/core/configs/*.in | ./mktop > net.top
./mktop /usr/local/rancid/core/configs/*.in > net1.top
same out output for both....

Mmmm. I think that files named "*.in" in the configs directory are
transient files that rancid uses while it grabs new state from the
network, and subsequently renames to their non-.in counterparts. You
may find that those files are either not always there, or you have
some stale, maybe truncated "*.in" files lying about.
./mktop $(awk -F: '/:up:/ { printf
"/usr/local/rancid/core/configs/%s\n", $1; }' \
/usr/local/rancid/core/router.db) >net2.top
(if you're a csh person you'll need to use back-ticks instead of the
$() notation). That expression should spit out a list of config files
corresponding to devices in the "core" group which are up, which
should contain reasonable food for mktop.
Joe

------- End of Original Message -------